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

When a customer purchases a product on credit or in installments, a claim is generated for each purchase, and each claim is registered in the system. If a payment is delayed, a settlement is reached with the customer to adjust the payment amount and cycle, but rather than settling on a claim-by-claim basis, a new contract is signed on a customer-by-customer basis. In the conventional system, re-contract processing through settlement for a customer with multiple claims required the operator to perform a dummy full payment process for each claim and then re-register a new contract, which made the process complicated. In addition, for each claim, balance information etc. must be reported to an external credit agency, but because the dummy full payment process through settlement breaks the connection to external credit information for the claims, each claim had to be dealt with individually.

A patent relating to a method for managing overdue receivables has been disclosed that includes a center having multiple user terminal devices, a server that communicates with the multiple user terminal devices via a network, and a business processing unit that performs business operations related to overdue receivables, and that processes operations such as making reminder calls based on overdue data, registers deposit data, and erases overdue data (see, for example, Patent Document 1).

JP 2001-282994 A

However, Patent Document 1 does not carry out dummy repayment procedures for the debt when a settlement agreement is made due to overdue payments.

The present invention has been made in consideration of the above, and aims to provide a loan management device, a loan management method, and a loan management program that can reduce the workload when a customer who has contracted multiple loans falls behind on payments by automatically performing dummy full payment processing for each loan by registering a settlement agreement.

In order to solve the above problems and achieve the objective, the loan management device of the present invention is a loan management device equipped with a control unit, and is capable of accessing loan information data that stores data including the loan number, product name, contract date, reconstruction amount, and monthly payment amount for one or more loans contracted by the same customer, repayment schedule information data including the payment date and monthly payment amount set for each loan, and transaction information data including the customer's payment information for the loan, and the control unit is equipped with a loan information data creation means that creates the loan information data based on an operator's input, a repayment schedule information data creation means that creates the repayment schedule information data for each loan based on the loan information data, and a transaction information acquisition means that acquires information on deposits from the customer and creates the transaction information data, and the loan information data creation means creates loan information data that consolidates one or more loans of the customer into one when the loan is overdue, the repayment schedule information data creation means creates repayment schedule information data for the consolidated loan information data, and the transaction information acquisition means creates transaction information data for reconciling the multiple overdue loans.

The loan management device according to the present invention further comprises a report data creation means for creating external credit agency report data for reporting to an external credit agency regarding the customer's payments for each claim, and the report data creation means creates external credit agency report data indicating that one or more overdue claims will be transferred to a newly contracted claim after the claim information data creation means creates claim information data resulting from settlement, and reports this to the external credit agency.

The loan management method according to the present invention is a loan management method executed by a loan management device having a control unit, and is capable of accessing the following for one or more loans contracted by the same customer: loan information data storing data including the loan number, product name, contract date, reconstruction amount, and monthly payment amount; repayment schedule information data including the payment date and monthly payment amount set for each of the loans; transaction information data including the customer's payment information for the loans; and external credit agency report data for reporting the customer's payments for each of the loans to an external credit agency; and the control unit creates the loan information data based on an operator's input. It is characterized by including a creation step, a repayment schedule information data creation step for creating the repayment schedule information data for each of the claims based on the claim information data, a transaction information acquisition step for acquiring payment information from the customer and creating the transaction information data, a settlement agreement information creation step for creating claim information data that consolidates one or more claims of the customer into one when the claim becomes overdue, a settlement repayment information creation step for creating repayment schedule information data for the consolidated claim information data, and a settlement information processing step for creating transaction information data for settling multiple overdue claims.

The loan management program according to the present invention is a loan management program executed by a loan management device having a control unit, and is capable of accessing credit information data that stores data including credit number, product name, contract date, reconstruction amount, and monthly payment amount for one or more credits contracted by the same customer, repayment schedule information data including the payment date and monthly payment amount set for each credit, and transaction information data including the customer's payment information for the credit, and the control unit executes on a computer the following steps: a credit information data creation step for creating the credit information data based on an operator's input; a repayment schedule information data creation step for creating the repayment schedule information data for each credit based on the credit information data; a transaction information acquisition step for acquiring information on deposits from the customer and creating the transaction information data; a settlement contract information creation step for creating credit information data that consolidates one or more credits of the customer into one when the credit is overdue; a settlement repayment information creation step for creating repayment schedule information data for the consolidated credit information data; and a settlement information processing step for creating transaction information data for the multiple overdue credits to be settled.

According to the present invention, when a customer who has contracted one or multiple debts falls behind on payments, a settlement agreement is registered to automatically perform a dummy full payment process for each debt, thereby reducing the workload.

FIG. 1 is a diagram showing an example of the configuration of a loan management apparatus according to the present embodiment. FIG. 2 is a diagram showing an example of the claim information data 106a. FIG. 3 is a diagram showing an example of the repayment schedule information data 106b. FIG. 4 is a diagram showing an example of the transaction information data 106c. FIG. 5 is a diagram showing an example of the external credit agency report data 106d. FIG. 6 is a diagram showing an example of external credit agency report data 106d' in the case where a payment delinquency occurs. FIG. 7 is a diagram for explaining the flow of a settlement process according to the conventional method. FIG. 8 is a diagram showing an example of the claim information data 106a' and the repayment schedule information data 106b' in the case where a settlement has been made. FIG. 9 is a diagram showing an example of transaction information data 106c' in the case where a settlement has been made. FIG. 10 is a diagram showing an example of the external credit agency report data 106d when a settlement has been made. FIG. 11 is a diagram showing an example of the settlement process registration screen MA. FIG. 12 is a diagram showing an example of a payment schedule registration screen MB for the settlement process.

Below, an embodiment of the loan management device, loan management method, and loan management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[1. Configuration]
An example of the configuration of a loan management device according to the present embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a diagram showing an example of the configuration of a loan management device 100 according to the present embodiment.

The loan management device 100 is constructed based on a commercially available desktop personal computer. Note that the loan management device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, but may be constructed based on 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 of the loan management device 100 is 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 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 a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the loan management device 100 and the server device 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may be stored in the server device 200, for example.

An input device 400 and an output device 500 are connected to the input/output interface unit 108. The output device 500 may be a monitor (including a home television), a speaker, or a printer. The input device 400 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to achieve a pointing device function. In the following, the output device 500 may be referred to as the monitor 500, and the input device 400 may be referred to as the keyboard 400 or the mouse 400.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

The memory unit 106 stores, for example, claim information data 106a, repayment schedule information data 106b, transaction information data 106c, external credit agency report data 106d, etc.

As shown in FIG. 2, the credit information data 106a stores information such as credit number, product, contract date, advance amount, monthly payment amount, and first payment date, associated with the customer number.

As shown in FIG. 3, repayment schedule information data 106b stores repayment schedule information such as payment date and monthly payment amount for each claim, associated with the customer number.

As shown in FIG. 4, the transaction information data 106c stores transaction information such as bond number, transaction date (deposit date), deposit amount, outstanding balance, and full repayment category in association with a customer number.

As shown in FIG. 5, the external credit agency report data 106d stores report data such as credit number, report date, contract management category, deposit category, invoice amount, deposit amount, and credit balance, associated with the customer number.

The control unit 102 is a CPU or the like that performs overall control of the loan management device 100. The control unit 102 has an 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.

The control unit 102 conceptually includes a credit information data creation unit 102a, a repayment schedule information data creation unit 102b, a transaction information acquisition unit 102c, a report data creation unit 102d, etc.

The credit information data creation unit 102a creates credit information data 106a including credit information based on a credit contract with a customer, i.e., information such as credit number, product, contract date, advance payment amount, monthly payment amount, first payment date, etc. In addition, when a credit is overdue, the credit information data creation unit 102a creates credit information data 106a' (see FIG. 8 ) based on a settlement agreement that consolidates one or more credits of the customer into one.

The repayment schedule information data creation unit 102b creates information about the repayment schedule of the claim, i.e., repayment schedule information data 106b such as payment date and monthly payment amount. In addition, after the claim information data creation unit 102a creates new claim information data 106a' through settlement, the repayment schedule information data creation unit 102b creates repayment schedule information data 106b' (see Figure 8) for the consolidated claim information data 106a'.

The transaction information acquisition unit 102c acquires information on the receipt of payment from the customer regarding the claim, and creates transaction information data 106c based on the acquired payment information. After the claim information data creation unit 102a creates new claim information data 106a' through settlement, the transaction information acquisition unit 102c creates transaction information data 106c' (see FIG. 9 ) for settling one or more overdue claims.

The report data creation unit 102d creates external credit agency report data 106d for reporting to the external credit agency regarding the customer's payment for the claim, and reports it to the external credit agency by email, etc. In addition, after the claim information data creation unit 102a creates the claim information data 106a' resulting from the settlement, the report data creation unit 102d creates external credit agency report data 106d' (see FIG. 10 ) indicating that one or more overdue claims will be transferred to a newly contracted claim, and reports this to the external credit agency.

2. Processing
Here, a specific example of the process executed by the loan management device 100 will be described with reference to FIGS.

When a customer enters into a credit contract, such as a credit purchase or installment purchase of a product, credit information data 106a is registered for each credit. Credit information data 106a is stored for one or more credits contracted by the same customer, linked by customer number, etc. For example, as shown as an example in Figure 2, credit information data 106a is stored for credits 100-0, 100-1, and 100-2 of the same customer, linked by customer number 100.

When a credit agreement is made with a customer, repayment schedule information data 106b is created and stored for each credit, as shown in Figure 3. Repayment schedule information data 106b consists of the credit number, payment date, monthly payment amount, etc., and repayment schedule information data 106b-0, 106b-1, 106b-2 for credits 100-0, 100-1, 100-2 of the same customer are linked by customer number 100 and stored.

When a customer deposits the monthly payment amount for receivables 100-0, 100-1, and 100-2 on the payment date, transaction information data 106c is created and updated for the new deposit, as shown in FIG. 4. Transaction information data 106c updates the receivable balance each time a monthly payment amount is deposited. In addition, for receivables with remaining receivable balances, the "100" category is automatically entered as the receivable is in progress.

In addition, for each claim, external credit agency report data 106d as shown in FIG. 5 is created and updated in order to report claim information such as the claim balance to an external credit agency on a monthly basis. The external credit agency report data 106d updates the invoice amount, deposit amount, and claim balance at the time of reporting based on the transaction information data 106c. If the deposit amount matches the invoice amount, the deposit category is automatically filled in with "$", which indicates a full deposit.

When a customer makes monthly payments, transaction information data 106c and external credit agency report data 106d are created and updated monthly. On the other hand, when a payment is delayed and the payment is overdue, external credit agency report data 106d' as shown in Figure 6 is created. In the case of overdue payment, the amount of payment becomes 0 and the payment classification is entered as "A", which means not yet paid.

In the past, when a payment default occurred, the created external credit agency report data 106d' was not sent to the external credit agency, and the work of creating and reporting data for each report was performed outside the system. Also, as shown in FIG. 7, the operator creates transaction information data 106c'' for each credit, which is a dummy deposit process that sets the credit balance to zero and assumes that a dummy deposit has been made. Also, when a settlement process is performed with a customer, credit information data 106a'' with a new credit number is registered, and repayment schedule information data 106c'' is created based on credit information data 106a''. If a customer who has become delinquent has multiple credit contracts as shown in FIG. 7, it is necessary to create transaction information data 106c'' for each credit, which increases the workload. Furthermore, it is also necessary to create and report to the external credit agency that credits 100-0, 100-1, and 100-2 have been processed as dummy deposits due to delinquency and are being transferred to credit 100-3.

In this embodiment, when a debt falls into arrears and a settlement agreement is concluded, debt information data 106a' and repayment schedule information data 106b' resulting from settlement, an example of which is shown in FIG. 8, are created by inputting data into the settlement processing registration screen MA and payment schedule registration screen MB, examples of which are shown in FIG. 11 and FIG. 12, and then transaction information data 106c', shown in FIG. 9, is automatically created. In the settled transaction information data 106c', no dummy deposit processing is performed, the deposit amount is set to 0, the debt balance is set to 0, and the payment completion classification is set to 300 for settlement.

The external credit agency report data 106d' is created and reported as shown in FIG. 10, which includes data on overdue claims 100-0, 100-1, and 100-2, and data on claim 100-3 that was taken over through settlement. For claims 100-0, 100-1, and 100-2, the claim balance is set to 0, and the termination comment "73" indicating the transfer has been completed is entered, and for claim 100-3, the contract management category "21" indicating a transferred claim is entered, making it clear that claims 100-0, 100-1, and 100-2 have been taken over by the settled claim 100-3.

As described above, according to this embodiment, when a claim becomes overdue and claim information data 106a' and repayment schedule information data 106b' are created through settlement, transaction information data 106c' is automatically created for the overdue claim to be settled. In addition, external credit agency report data 106d' is transferred to a new claim for the overdue claim and is reported together with information on the settled claim, making it possible to significantly reduce the workload.

[3. 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 making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

4. Other embodiments
The present invention may be embodied 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 a known method.

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, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the loan management device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains 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 necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing 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 cooperates with the CPU to form the control unit.

This computer program may also be stored in 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-transitory computer-readable recording medium, and may also be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, 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. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration 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 configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., 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 providing websites.

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 the information processing device to which any peripheral device is connected. The loan management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize 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 can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is particularly useful in loan management in the real estate industry.

REFERENCE SIGNS LIST 100 Loan management device 102 Control unit 102a Credit information data creation unit 102b Repayment schedule information data creation unit 102c Transaction information acquisition unit 102d Report data creation unit 104 Communication interface unit 106 Storage unit 106a Credit information data 106b Repayment schedule information data 106c Transaction information data 106d External credit agency report data 108 Input/output interface unit 200 Server 300 Network 400 Input device 500 Output device

Claims (4)

A loan management device including a control unit,
Credit information data that stores data including credit number, product name, contract date, repayment amount, and monthly payment amount for one or more credits contracted by the same customer;
Repayment schedule information data including a payment date and a monthly payment amount set for each of the claims;
transaction information data including customer payment information for said receivables;
is accessible to
The control unit is
a credit information data creation means for creating the credit information data based on an input from an operator;
a repayment schedule information data creation means for creating the repayment schedule information data for each of the claims based on the claim information data;
a transaction information acquisition means for acquiring deposit information from said customer and creating said transaction information data;
Equipped with
the credit information data creation means creates credit information data that consolidates one or more credits of the customer into one when a credit is overdue,
the repayment schedule information data creation means creates repayment schedule information data from the consolidated credit information data;
The loan management device is characterized in that the transaction information acquisition means creates transaction information data for reconciling a plurality of overdue claims. a report data creating means for creating external credit agency report data for reporting to an external credit agency regarding the customer's payment for each of said claims;
The loan management device as described in claim 1, characterized in that after the claim information data creation means creates claim information data due to settlement, the report data creation means creates external credit agency report data including data on one or more overdue claims and data on new claims contracted as a result of settlement, and indicates that one or more overdue claims will be transferred to the newly contracted claims, and reports this to the external credit agency. A loan management method executed by a loan management device having a control unit,
Credit information data that stores data including credit number, product name, contract date, repayment amount, and monthly payment amount for one or more credits contracted by the same customer;
Repayment schedule information data including a payment date and a monthly payment amount set for each of the claims;
transaction information data including customer payment information for said receivables;
external credit agency reporting data for reporting customer payments per said receivables to an external credit agency;
is accessible to
The control unit is
a claim information data creation step of creating the claim information data based on an input from an operator;
a repayment schedule information data creation step of creating the repayment schedule information data for each of the claims based on the claim information data;
a transaction information acquisition step of acquiring payment information from the customer and creating the transaction information data;
a settlement agreement information creation step for creating debt information data that consolidates one or more debts of the client into one when the debt is overdue;
a reconciliation repayment information creation step for creating repayment schedule information data of the consolidated claim information data;
a deemed-payment information processing step for creating transaction information data for settling a plurality of overdue claims;
containing,
A loan management method comprising: A loan management program executed by a loan management device having a control unit,
Credit information data that stores data including credit number, product name, contract date, repayment amount, and monthly payment amount for one or more credits contracted by the same customer;
Repayment schedule information data including a payment date and a monthly payment amount set for each of the claims;
transaction information data including customer payment information for said receivables;
is accessible to
The control unit is
a claim information data creation step of creating the claim information data based on an input from an operator;
a repayment schedule information data creation step of creating the repayment schedule information data for each of the claims based on the claim information data;
a transaction information acquisition step of acquiring payment information from the customer and creating the transaction information data;
a settlement agreement information creation step for creating debt information data that consolidates one or more debts of the client into one when the debt is overdue;
a reconciliation repayment information creation step for creating repayment schedule information data of the consolidated claim information data;
a settlement information processing step for creating transaction information data for settling a plurality of overdue claims;
A loan management program characterized by being executed by a computer.

Images