Residual value payment management device, residual value payment management method, and residual value payment management program

Abstract

The objective is to provide a residual value payment management device, a residual value payment management method, and a residual value payment management program that enable automatic determination and automatic setting of the flow after registration by pre-registering the selection results of the residual value payment method in the system. [Solution] Before the date on which the residual value is to be recovered, residual value payment data is obtained, specifying the residual value payment method as a lump sum payment, product return, or further installment payments. Based on the planned recovery data and the residual value payment data, residual value processing is performed according to the residual value payment method.

Description

Technical Field

[0001] The present invention relates to a residual value payment management device, a residual value payment management method, and a residual value payment management program.

Background Art

[0002] In Patent Document 1, at the end of the residual value setting period, the user can select one of returning the product, repaying the residual value in a lump sum, or setting a new repayment plan based on the residual value, and a residual value setting type credit system is used. A configuration for providing a residual value setting type product sales system is disclosed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the invention described in Patent Document 1, there is a problem that the automation of the management of the collection completion process of the residual value of the installment payment of the residual value credit cannot be achieved.

[0005] The present invention has been made in view of the above problems, and by registering the selection result of the residual value payment method in the system in advance, it is possible to perform processing by automatic discrimination and automatic setting for the flow after registration. The purpose is to provide a residual value payment management device, a residual value payment management method, and a residual value payment management program.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the residual value payment management device according to the present invention is a residual value payment management device comprising a storage unit and a control unit, wherein the storage unit comprises debt storage means for storing the residual value amount of the purchase price and collection schedule data for which the collection date has been set, and the control unit comprises residual value payment method acquisition means for acquiring residual value payment data for which the residual value payment method has been set before the collection date of the residual value amount, and residual value matching means for executing residual value matching processing according to the residual value payment method based on the collection schedule data and the residual value payment data.

[0007] Furthermore, in the residual value payment management device according to the present invention, the residual value payment method acquisition means is characterized in that, when acquiring application data for a residual value credit with the price of the purchased goods as the credit principal, it acquires residual value payment data in which the residual value payment method has been set.

[0008] Furthermore, in the residual value payment management device according to the present invention, the residual value payment method acquisition means is characterized in that, after the commencement of the account transfer process for residual value credit with the purchase price of the purchased goods as the credit principal, the residual value payment data in which the residual value payment method has been set is acquired within a period in which the amount of interest paid by residual value credit does not exceed the total amount of interest paid by general credit with the purchase price of the goods as the credit principal upon full repayment.

[0009] Furthermore, in the residual value payment management device according to the present invention, the recovery schedule data is further configured with a final payment flag indicating whether or not it is the final payment scheduled, and the residual value handling means, based on the recovery schedule data and the residual value payment data, executes the residual value handling process according to the residual value payment method if the final payment flag indicates that it is the final payment scheduled.

[0010] Furthermore, in the residual value payment management device according to the present invention, the residual value handling means is characterized in that, based on the recovery schedule data and the residual value payment data, if the final payment flag indicates the final recovery schedule and the residual value payment data is set to a lump-sum payment as the residual value payment method, it executes a bank transfer process for the residual value set amount, which is the residual value handling process corresponding to the lump-sum payment.

[0011] Furthermore, in the residual value payment management device according to the present invention, the residual value handling means is characterized in that, based on the scheduled recovery data and the residual value payment data, if the final payment flag indicates the scheduled recovery for the final payment and the residual value payment data has product return set as the residual value payment method, it performs a transfer process to transfer and record the residual value amount, which is the residual value handling process corresponding to the product return, to the purchased product.

[0012] Furthermore, in the residual value payment management device according to the present invention, the debt storage means further stores contract data that sets the credit product applied to the purchased product, the storage unit further includes a product master that sets the credit product and product type in association, and the residual value handling means executes a process to acquire application data for installment payments with the residual value set amount as the credit principal, which is the residual value handling process corresponding to the installment payment, when the final payment flag indicates the final payment due date, the residual value payment data is set as the residual value payment method and the product type is set as residual value installment.

[0013] Furthermore, the residual value payment management method according to the present invention is a residual value payment management method to be executed by a residual value payment management device comprising a storage unit and a control unit, wherein the storage unit comprises debt storage means for storing debt storage means that stores the residual value amount of the price of the purchased goods and collection schedule data which sets the collection date, and the method is characterized by comprising: a residual value payment method acquisition step executed by the control unit, which acquires residual value payment data which sets the residual value payment method before the collection date of the residual value amount; and a residual value response step which executes residual value response processing according to the residual value payment method based on the collection schedule data and the residual value payment data.

[0014] Furthermore, the residual value payment management program according to the present invention is a residual value payment management program to be executed by a residual value payment management device comprising a storage unit and a control unit, wherein the storage unit comprises debt storage means for storing the residual value amount of the purchase price and collection schedule data for which the collection date has been set, and the control unit is characterized in that it is made to execute a residual value payment method acquisition step for acquiring residual value payment data for which the residual value payment method has been set before the collection date of the residual value amount, and a residual value response step for executing residual value response processing according to the residual value payment method based on the collection schedule data and the residual value payment data. [Effects of the Invention]

[0015] According to the present invention, by pre-registering the selection of the residual value payment method (lump sum payment, product return, or further installment payment) in the system, subsequent processing flows can be automatically judged and set, resulting in reduced operational errors and reduced operational burden. Furthermore, according to the present invention, it is possible to strengthen control over residual value credit and improve operational efficiency. Furthermore, according to the present invention, it is possible to differentiate from other companies' SLN (solutions) by covering the operations of products with high resale value with the standard SLN (solution). Furthermore, according to the present invention, it is possible to manage the entire process from the execution of the residual value credit installment payment contract to the completion of the recovery of the residual value. Furthermore, according to the present invention, by pre-registering the residual value payment method, it is possible to automate processing and set items automatically. Furthermore, according to the present invention, from the setting by residual value payment registration, it is possible to process lump sum repayment, return, or further installment payment for the residual value according to the setting. [Brief explanation of the drawing]

[0016] [Figure 1] Figure 1 shows an example of a three-party credit agreement. [Figure 2] Figure 2 shows an example of residual value credit. [Figure 3] Figure 3 is a block diagram showing an example of the configuration of the residual value payment management device in this embodiment. [Figure 4] Figure 4 is a flowchart showing an example of the processing of the residual value payment management device in this embodiment. [Figure 5] Figure 5 is a flowchart showing an example of the residual value payment management process in this embodiment. [Figure 6] Figure 6 shows an example of the residual value payment management process in this embodiment. [Figure 7] Figure 7 shows an example of the residual value payment management process in this embodiment. [Figure 8] Figure 8 shows an example of the residual value payment management process in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 11] FIG. 11 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 12] FIG. 12 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 13] FIG. 13 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 14] FIG. 14 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 15] FIG. 15 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 16] FIG. 16 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 17] FIG. 17 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 18] FIG. 18 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 19] FIG. 19 is a diagram showing an example of the residual value payment management process in the present embodiment. [Figure 20] FIG. 20 is a diagram showing an example of the residual value payment management process in the present embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION

[0017] Embodiments of the present invention will be described in detail based on the drawings. Note that the present invention is not limited to these embodiments.

[0018] [1. Overview] First, the overview of the present invention will be described with reference to FIGS. 1 and 2. FIG. 1 is a diagram showing an example of a tripartite credit contract. FIG. 2 is a diagram showing an example of residual value credit. <00​ Traditionally, as shown in Figure 1, in the credit industry, where there is a contractual relationship between the customer, the merchant, and the credit company, one of the payment methods is the residual value setting payment method: residual value credit (a residual value is set in advance, and the difference other than the residual value is paid in installments, and after the installment payments are completed, the remaining residual value can be paid in a lump sum, by returning the product, or by making further installments).

[0020] For example, as shown in Figure 2, when using residual value credit to purchase a 5 million yen car, after paying 3 million yen in 35 equal installments, the remaining balance of 2 million yen can be paid. At this point, the following options are available: (1) Lump-sum payment: a lump-sum payment of the 2 million yen remaining balance, (2) Return of goods: payment of the 2 million yen remaining balance by returning the purchased goods (offsetting), or (3) Further installment payments: further installment payments of the 2 million yen remaining balance. Residual value credit is most commonly used for vehicle purchases, and the return of goods is executed by returning the vehicle to the participating store (dealer).

[0021] Furthermore, in the past, operations related to residual value credit were based on the selection of the residual value payment method, and subsequent processes were carried out at the operator's discretion, leading to errors. Additionally, operators had to manually input data for each process, resulting in a heavy workload for them.

[0022] Therefore, in this embodiment, by pre-registering the selection result of the residual value payment method in the system, a mechanism is provided that enables automatic judgment and automatic setting of the flow after registration.

[0023] [2. Structure] An example of the configuration of the residual value payment management device 100 according to this embodiment will be described with reference to Figure 3. Figure 3 is a block diagram showing an example of the configuration of the residual value payment management device 100 in this embodiment.

[0024] As shown in Figure 3, the residual value payment management device 100 is a commercially available desktop personal computer. However, the residual value payment management device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0025] The residual value payment management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each component of the residual value payment management device 100 is connected to communicate via any communication path.

[0026] The communication interface unit 104 connects the residual value payment management device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines. The communication interface unit 104 has the function of communicating data with other devices via communication lines. Here, the network 300 has the function of connecting the residual value payment 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).

[0027] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a touch panel), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that works in conjunction with a mouse to provide pointing device functionality. In the following, the output device 114 may be referred to as the monitor 114 or printer 114, and the input device 112 may be referred to as the keyboard 112 or mouse 112.

[0028] The storage unit 106 stores various databases, tables, and files. The storage unit 106 also stores 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 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 storage unit 106 includes a product master 106a and an accounts receivable database 106b.

[0029] Product master 106a is a master file that sets up credit products. Here, product master 106a may have credit products and product types linked together. Also, product master 106a may have a residual value flag set to indicate general credit or residual value credit.

[0030] The debt database 106b stores credit debt data. Here, the debt database 106b may also store collection schedule data, which includes the residual value set for the price of the purchased goods and the collection date. Here, the collection schedule data may have a final payment flag set to indicate whether or not it is the final payment scheduled. The debt database 106b may also store contract data, which includes the credit product applied to the purchased goods. Furthermore, the debt database 106b may also store residual value payment data, which includes residual value payment methods such as lump-sum payment, product return, or further installment payment; residual value credit application data, which uses the price of the purchased goods as the credit principal; transaction data, which links the transaction and debt status; contract modification linkage data, which links the period before and after the contract change; and account transfer request data, which links the request year and month and the transfer amount.

[0031] The control unit 102 is a CPU or the like that comprehensively controls the residual value payment management device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. Functionally, the control unit 102 comprises a credit contract setting unit 102a, a residual value payment method acquisition unit 102b, and a residual value handling unit 102c.

[0032] The credit contract setting unit 102a sets up a credit contract with the product price as the credit principal. Here, the credit contract setting unit 102a may obtain application data for a credit with the product price as the credit principal. Here, the credit contract setting unit 102a may obtain application data for a residual value credit with the purchase price of the goods as the credit principal. The credit contract setting unit 102a may also obtain collection schedule data with the residual value amount of the purchase price and the collection date set. The credit contract setting unit 102a may also obtain transaction data linked to the transaction and the debt status in accordance with the execution of the transaction. Here, the credit contract setting unit 102a may obtain transaction data linked to the contract execution and the debt status upon the arrival of the contract execution date. The credit contract setting unit 102a may also obtain contract data with the credit product applied to the purchased goods set. The credit contract setting unit 102a may also perform merchant settlement processing for the credit principal. Here, the credit contract setting unit 102a may perform a merchant settlement process for the credit principal, which involves the credit company transferring the funds to the merchant. Alternatively, the credit contract setting unit 102a may perform a credit account transfer process.

[0033] The residual value payment method acquisition unit 102b acquires residual value payment data in which a residual value payment method has been set. Here, the residual value payment method acquisition unit 102b may acquire residual value payment data in which a residual value payment method such as lump-sum payment, product return, or re-installment payment has been set before the date on which the residual value amount has been recovered. The residual value payment method acquisition unit 102b may also acquire residual value payment data in which a residual value payment method has been set when acquiring application data for residual value credit with the purchase price of the product as the credit principal. The residual value payment method acquisition unit 102b may also acquire residual value payment data in which a residual value payment method has been set within a period after the commencement of the account transfer processing for residual value credit with the purchase price of the product as the credit principal, during which the amount of interest paid by the residual value credit does not exceed the total amount of interest paid by general credit with the purchase price of the product as the credit principal at the time of full repayment.

[0034] The residual value handling unit 102c executes residual value handling processing according to the residual value payment method. Here, the residual value handling unit 102c may execute residual value handling processing according to the residual value payment method based on the recovery schedule data and the residual value payment data. Alternatively, the residual value handling unit 102c may execute residual value handling processing according to the residual value payment method if the final payment flag indicates the final recovery schedule based on the recovery schedule data and the residual value payment data. Furthermore, the residual value handling unit 102c may execute account transfer processing for the residual value amount, which is residual value handling processing according to lump-sum payment, if the final payment flag indicates the final recovery schedule and the residual value payment data has a lump-sum payment set as the residual value payment method. Furthermore, the residual value handling unit 102c may, based on the scheduled recovery data and residual value payment data, execute a transfer process to transfer the residual value amount, which is a residual value handling process corresponding to the return of the product, to the purchased product if the final payment flag indicates the scheduled recovery of the final payment and the residual value payment data has product return set as the residual value payment method. Furthermore, the residual value handling unit 102c may, based on the scheduled recovery data, residual value payment data, contract data, and product master, execute a process to acquire application data for installment payments with the residual value amount as the credit principal, which is a residual value handling process corresponding to the installment payment, if the final payment flag indicates the scheduled recovery of the final payment and the residual value payment data has re-installment payment set as the residual value payment method and the product type has residual value re-installment. Furthermore, the residual value handling unit 102c may execute a credit account transfer process.

[0035] [3. Specific examples] A specific example of this embodiment will be described with reference to Figures 4 to 20.

[0036] [Residual Value Payment Management Processing] Now, with reference to Figure 4, an example of the residual value payment management process in this embodiment will be described. Figure 4 is a flowchart showing an example of the processing of the residual value payment management device 100 in this embodiment.

[0037] As shown in Figure 4, the credit contract setting unit 102a obtains application data for residual value credit with the price of the customer's purchased goods as the credit principal, and based on the application data obtains collection schedule data with the residual value amount of the purchase price, collection date, and a final collection flag indicating whether or not the final collection is scheduled, and upon the arrival of the contract execution date, obtains transaction data linked to the contract execution and debt status, obtains contract data with the credit product applied to the purchased goods, and executes merchant settlement processing, which is the merchant settlement processing of the credit principal, by transferring the advance payment from the credit company to the merchant (step SA-1).

[0038] Then, the residual value payment method acquisition unit 102b determines whether or not it has acquired residual value payment data in which the residual value payment method selected by the customer has been set (step SA-2).

[0039] Then, if the residual value payment method acquisition unit 102b determines that it has not acquired residual value payment data for which a residual value payment method has been set (step SA-2: No), it proceeds to step SA-3.

[0040] Then, the residual value handling unit 102c determines whether the final payment flag set in the recovery schedule data indicates a final recovery schedule (step SA-3).

[0041] Then, if the residual value handling unit 102c determines that the final payment flag set in the recovery schedule data indicates the final recovery schedule (step SA-3: Yes), it notifies the person in charge of residual value credit (for example, an error notification) and terminates the process.

[0042] On the other hand, if the residual value handling unit 102c determines that the final collection flag set in the collection schedule data does not indicate a final collection schedule (step SA-3: No), it proceeds to step SA-4.

[0043] Then, the residual value handling unit 102c executes the account transfer process for the residual value credit based on the recovery schedule data and the account transfer request data (step SA-4), and moves the process to step SA-2.

[0044] On the other hand, if the residual value payment method acquisition unit 102b determines that it has acquired residual value payment data in which the residual value payment method has been set (step SA-2: Yes), it proceeds to step SA-5.

[0045] Then, the residual value handling unit 102c determines whether the final payment flag set in the recovery schedule data indicates a final recovery schedule (step SA-5).

[0046] Then, if the residual value handling unit 102c determines that the final installment flag set in the recovery schedule data does not indicate a final recovery schedule (step SA-5: No), it proceeds to step SA-6.

[0047] Then, the residual value handling unit 102c executes the account transfer process for the residual value credit based on the recovery schedule data and the account transfer request data (step SA-6), and moves the process to step SA-5.

[0048] On the other hand, if the residual value handling unit 102c determines that the final collection flag set in the collection schedule data indicates the final collection schedule (step SA-5: Yes), it proceeds to step SA-7.

[0049] Then, the residual value handling unit 102c determines, based on the residual value payment data, whether the residual value payment method is a lump-sum payment, product return, or further installment payments (step SA-7).

[0050] Then, if the residual value handling unit 102c determines that the residual value payment method is a lump-sum payment (step SA-7: lump-sum payment), it moves the process to step SA-8.

[0051] Then, the residual value handling unit 102c executes a residual value handling process corresponding to a lump-sum payment, which is a transfer of the residual value amount to the account (step SA-8), based on the planned recovery data and the account transfer request data, and terminates the process.

[0052] Furthermore, if the residual value handling unit 102c determines, based on the residual value payment data, that the residual value payment method is product return (step SA-7: product return), it proceeds to step SA-9.

[0053] Then, the residual value handling unit 102c executes a transfer process (step SA-9) to transfer the residual value amount, which is a residual value handling process corresponding to the return of the product, to the purchased product, based on the planned collection data, and terminates the process.

[0054] Furthermore, if the residual value handling unit 102c determines, based on the residual value payment data, that the residual value payment method is re-installment payment (step SA-7: re-installment payment), it proceeds to step SA-10.

[0055] Then, the residual value handling unit 102c executes the process of acquiring application data for installment payments with the residual value set amount as the credit principal, which is a residual value handling process corresponding to the re-installment payment, based on the recovery schedule data (step SA-10), and terminates the process.

[0056] Here, an example of residual value payment management processing in this embodiment will be described with reference to Figures 5 to 20. Figure 5 is a flowchart showing an example of residual value payment management processing in this embodiment. Figures 6 to 20 are diagrams showing an example of residual value payment management processing in this embodiment.

[0057] As shown in Figure 5, in this embodiment, application data received from customers is registered (for example, if a customer applies to a merchant, the merchant transmits the data to the credit company) (Step SB-1).

[0058] In other words, as shown in Figures 6 and 7, in the application registration process in this embodiment, the application data received from the customer on the application registration screen is registered in the system (if an application is made by a customer to a merchant, the merchant then transmits the data to the credit company).

[0059] Returning to Figure 5, in this embodiment, when the contract execution date arrives, the contract execution status is registered (step SB-2).

[0060] In other words, as shown in Figure 8, in the contract execution registration in this embodiment, when the contract execution date arrives, the contract execution status is registered in the contract execution registration (for example, as a daily operation, contract execution registration is performed for a receivable with a payment date of 2022 / 12 / 1). However, in this embodiment, the user may perform weekly or monthly operations.

[0061] Returning to Figure 5, in this embodiment, the advance payment is transferred from the credit company to the affiliated store, and the entire amount of the advance payment (installment payments + residual value) is also transferred for residual value credit (step SB-3).

[0062] In other words, as shown in Figure 9, in the merchant settlement process in this embodiment, the batch processing for December 2022 is executed as a monthly operation for remitting advance payments. In this embodiment, the product type code is referenced using the product code set in the contract data updated at the time of "Application Registration" as the key to reference the product master 106a.

[0063] Returning to Figure 5, in this embodiment, the request and payment processing for direct debit to the customer (debtor) is executed (step SB-4). In this embodiment, in the case of a typical credit, the contract ends when the loan is fully repaid.

[0064] In other words, as shown in Figures 10 and 11, in the direct debit request and payment processing in this embodiment, a batch process for December 2022 is executed as a monthly operation for direct debit to the customer (debtor). Here, in this embodiment, after the direct debit request, payment reconciliation may be performed based on the debit result.

[0065] Returning to Figure 5, in this embodiment, in the case of residual value credit, the residual value payment method agreed upon with the customer (debtor) is registered before the final payment is due (step SB-5).

[0066] In other words, in the residual value payment method registration in this embodiment, as shown in Figure 12, in the case of a lump-sum payment, the details of the lump-sum payment agreed with the customer on 2025 / 10 / 1 are registered on the residual value payment registration screen; as shown in Figure 13, in the case of product return, the details of the product return agreed with the customer on 2025 / 10 / 1 are registered on the residual value payment registration screen; and as shown in Figure 14, in the case of further installment payments, the details of the further installment payments agreed with the customer on 2025 / 10 / 1 are registered on the residual value payment registration screen.

[0067] Returning to Figure 5, in this embodiment, if the residual value payment method is a lump-sum payment, the final payment request and deposit process is executed for the customer (debtor) (step SB-6), and the contract is terminated upon full payment, ending the process.

[0068] In other words, as shown in Figures 15 and 16, when residual value payment method code = 1: lump-sum payment is set, in the account transfer request and payment processing in this embodiment, the December 2025 batch processing is executed as a monthly operation to request and receive the final account transfer payment from the customer (debtor), and the contract is terminated when the payment is completed. Here, in this embodiment, payment reconciliation may be performed based on the transfer result after the account transfer request.

[0069] Returning to Figure 5, in this embodiment, if the residual value payment method is the return of the goods, the return of the goods is registered (step SB-7), and the debt for the residual value is terminated by the registration of the return of the goods (contract terminated upon full payment), and the process is completed.

[0070] In other words, as shown in Figure 17, when residual value payment method code = 2: product return is set, in the residual value payment registration in this embodiment, the product return is registered on the residual value payment registration screen, and the debt for the residual value is paid off (full payment) upon product return registration, and the contract is terminated (the details are registered on 2026 / 1 / 15 upon receipt of product return from the customer). Here, in this embodiment, for accounting purposes, it is treated as a transfer between the balance and the product (asset), rather than a forfeiture (loss recording).

[0071] Returning to Figure 5, in this embodiment, if the residual value payment method is re-installment payments, the application data is registered again with the residual value as the credit principal (step SB-8).

[0072] In other words, as shown in Figure 18, when residual value payment method code = 3: re-installment payment is set, in the application registration in this embodiment, after the re-installment payment is set with the customer on 2025 / 10 / 1, the amended contract is registered on the application registration screen on 2025 / 12 / 1 in preparation for the contract execution on 2025 / 12 / 20. Here, in this embodiment, when specifying the product code on the application registration screen, if the contract change mode is selected and a product code with product type code = 1 (: new) is entered, it will be treated as an error and the input will be impossible. Also, in this embodiment, when specifying the product code, if the residual value flag of the specified debt number is 0 (: general) and a product code with product type code = 2 (: residual value re-installment) is entered, it will be treated as an error and the input will be impossible. In the example shown in Figure 18, neither condition is met, so no error occurs. Also, in the application registration screen in this embodiment, if the residual value flag is 1, it is possible to input the breakdown items (installment payment / deferred payment).

[0073] Returning to Figure 5, in this embodiment, the obligations of the original contract are offset against the claims of the re-debt contract, the contract is terminated, and the re-debt contract is registered as being in execution status (the original contract is fully paid and terminated, and the re-debt contract is in execution status) (Step SB-9).

[0074] In other words, as shown in Figure 19, in the contract execution registration in this embodiment, as a daily operation, contract execution registration is performed on the contract execution registration screen for receivables with a repayment date of 2025 / 12 / 20. Here, in this embodiment, from an accounting perspective, it is not a waiver (loss recording), but rather an offset between the balance and the receivables of the rescheduled contract, and the processing is performed on the receivables with the pre-change receivable number set in the change contract linkage data.

[0075] Returning to Figure 5, in this embodiment, since the full amount was settled at the time of the original contract, it is treated as ineligible (step SB-10), and the process ends.

[0076] In other words, as shown in Figure 20, in the merchant settlement process in this embodiment, a batch process for December 2025 is executed as a monthly operation, and in the case of re-installment payments, the full amount has already been settled at the time of the original contract, so it is not subject to this process.

[0077] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.

[0078] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0079] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0080] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0081] 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 by known methods.

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

[0083] Furthermore, with respect to the residual value payment management device 100, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0084] For example, the processing functions of the residual value payment management device 100, particularly those performed by the control unit 102, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the residual value payment management device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) records a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0085] Furthermore, this computer program may be stored on an application program server connected to the residual value payment management device 100 via any network, and it is possible to download all or part of it as needed.

[0086] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0087] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in this embodiment, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0088] The various databases stored in the memory unit 106 include 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.

[0089] Furthermore, the residual value payment management device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the residual value payment management device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment onto the device.

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

[0091] This invention is useful in industries such as the financial industry, including credit companies, which are finance-related companies of businesses that handle products with high resale value, such as automobile dealers. [Explanation of Symbols]

[0092] 100 Residual Value Payment Management System 102 Control Unit 102a Credit Agreement Setting Section 102b Residual Value Payment Method Acquisition Section 102c Residual Value Compatible Section 104 Communication Interface Section 106 Storage section 106a Product Master 106b Debt Database 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

[Claim 1] A residual value payment management device comprising a memory unit and a control unit, The aforementioned storage unit is Debt storage means for storing data on the residual value of the purchased goods and the collection date, Equipped with, The control unit, A residual value payment method acquisition means that acquires residual value payment data for which the residual value payment method has been set, prior to the recovery date of the residual value amount, A residual value matching means that performs residual value matching processing according to the residual value payment method based on the recovery schedule data and the residual value payment data, A residual value payment management device characterized by being equipped with the following features.

Images