Deposit management device, deposit management method, and deposit management program

Abstract

To provide a payment management device, a payment management method, and a payment management program, that efficiently perform handling processing when deposits are generated in payment management work, and that can further prevent clerical errors.SOLUTION: A payment management device 100 comprises a control unit 102. The control unit 102 comprises: a payment recognition section 102a for recognizing a payment date and a paid amount from an obligor with payment obligation over multiple payment due dates; a deposit accounting section 102b which compares the paid amount obtained at the payment recognition section 102a with an amount payable at the payment date, for accounting a difference as a deposit if the paid amount exceeds the amount payable; and an appropriation unit 102c for, on a first payment due date after the date when the deposit is accounted by the deposit accounting section 102b, appropriating the deposit accounted at the timing thereof as part or all of the amount payable at the timing thereof.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a deposit management device, a deposit management method, and a deposit management program. [Background technology]

[0002] Patent document 1 describes how, when a user who has already paid for a mail order item cancels the purchase of the item, the new mail order item that the user wishes to purchase is accepted and the payment amount is automatically deducted by the amount to be refunded. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2005-316753 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the financial industry, in the case of receivables management (credit, loans, leases), when a debtor makes multiple payments on due dates, there is a task of managing the difference as a deposit when the debtor makes a payment before the due date or overpays the invoice amount. Similar tasks are also performed in the management of payments for rent and monthly tuition fees. When a deposit is made, operations are performed outside the system management or require individual responses each time, which takes time for the operator and there is a concern of clerical errors.

[0005] The technology described in Patent Document 1 is applicable when a user cancels a mail-order item purchase and wishes to make a new purchase, but cannot be applied to managing payments when a debtor makes multiple payments on due dates.

[0006] The present invention has been made in consideration of the above, and aims to provide a deposit management device, a deposit management method, and a deposit management program that can efficiently handle the process when a deposit is received in deposit management operations, and also prevent administrative errors. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the deposit management device of the present invention is a deposit management device equipped with a control unit, which is characterized in that it comprises a deposit recognition means for recognizing the date and amount of deposit from a contractor who has a payment obligation with multiple payment due dates, a deposit accounting means for comparing the deposit amount obtained by the deposit recognition means with the payment obligation amount on the deposit date, and recording the difference as a deposit if the deposit amount exceeds the payment obligation amount, and an appropriation means for appropriating the deposit recorded at that time as part or all of the payment obligation amount at that time on the first payment due date after the date on which the deposit accounting means recorded the deposit.

[0008] The deposit recording means may record the difference as a deposit when the date of payment from the contractor is the due date and the amount of the payment exceeds the amount of the obligation on the due date.

[0009] The deposit recording means may record the entire amount of the deposit as a deposit when the date of payment from the contractor is before the payment due date and no payment obligation has arisen.

[0010] The payment obligation may be divided into principal and interest, and the allocation means may allocate the deposit currently recorded on the first payment due date to the interest of the payment obligation at that time, with priority given to the application of the deposit.

[0011] In addition, the deposit management method of the present invention is a deposit management method executed by a control unit of a deposit management device equipped with a control unit, and is characterized in that it includes a deposit recognition step executed by the control unit for recognizing the date and amount of deposit from a contractor who has a payment obligation with multiple payment due dates, a deposit accounting step for comparing the deposit amount obtained in the deposit recognition step with the payment obligation amount on the deposit date, and recording the difference as a deposit if the deposit amount exceeds the payment obligation amount, and an appropriation step for appropriating the deposit recorded at that time as part or all of the payment obligation amount at that time on the first payment due date after the date on which the deposit was recorded in the deposit accounting step.

[0012] In addition, the deposit management program of the present invention is a deposit management program to be executed by a control unit of a deposit management device equipped with a control unit, and is characterized in that it causes the control unit to execute the following: a deposit recognition step for recognizing the date and amount of deposit from a contractor who has a payment obligation with multiple payment due dates, a deposit accounting step for comparing the deposit amount obtained in the deposit recognition step with the payment obligation amount on the deposit date, and recording the difference as a deposit if the deposit amount exceeds the payment obligation amount, and an appropriation step for appropriating the deposit recorded at that time as part or all of the payment obligation amount at that time on the first payment due date after the date on which the deposit was recorded in the deposit accounting step. Effect of the Invention

[0013] According to the present invention, when a deposit is received in a deposit management operation, the corresponding process can be efficiently carried out and clerical errors can be prevented. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a deposit management device 100. As shown in FIG. [Diagram 2] FIG. 2 is a diagram showing the contract data. [Diagram 3] FIG. 3 is a diagram showing repayment schedule data. [Figure 4] Figure 4 shows transaction data that is set when a debtor makes a deposit on the due date that exceeds the amount of the obligation, where (a) shows the transaction data that is set on that due date, and (b) shows the transaction data that is set on the first due date thereafter. [Diagram 5] Figure 5 shows transaction data that is set when a debtor deposits a specified amount before the payment due date when no payment obligation has arisen, where (a) shows the transaction data that is set on the deposit date, and (b) shows the transaction data that is set on the first repayment date thereafter. [Figure 6] FIG. 6 is a diagram showing a confirmation screen 400 displayed on the monitor 114 when the appropriation unit 102c is processing the appropriation of a deposit. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of a deposit management device, a deposit management method, and a deposit 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 embodiment.

[0016] [1. Configuration] An example of the configuration of the invention device according to this embodiment (including the invention device according to the present invention) will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of a deposit management device 100.

[0017] The deposit management device 100 is constructed based on a commercially available desktop personal computer. The deposit management device 100 is not limited to those 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 Assistants), smartphone, or tablet personal computer.

[0018] The deposit management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the deposit management device 100 is connected to each other so as to be able to communicate with each other via an arbitrary communication path.

[0019] The communication interface unit 104 communicably connects the deposit 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 a communication line. Here, the network 300 has a function of connecting the deposit 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.

[0020] 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 cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0021] The storage unit 106 stores various databases (hereinafter referred to as DB), tables, files, etc. The storage unit 106 records computer programs for cooperating with an OS (Operating System) to give instructions to a 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, etc.

[0022] The control unit 102 is a CPU or the like that comprehensively controls the deposit 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 based on these stored programs.

[0023] The control unit 102 conceptually comprises, functionally, a deposit recognition unit (deposit recognition means) 102a, a deposit accounting unit (deposit accounting means) 102b, an appropriation unit (appropriation means) 102c, and the like.

[0024] The storage unit 106 stores a transaction information DB 106a, a contract information DB 106b, a repayment schedule information DB 106c, and the like.

[0025] The deposit management device 100 is used, for example, in the financial industry for debt management (credit, loans, leases) and for managing deposits such as rent and monthly tuition that are not automatically debited. It is assumed that a contractor who makes a deposit has concluded a contract to pay a specified amount of payment obligation on multiple payment due dates to an administrator who manages the deposits using the deposit management device 100. In the following example, the deposit management device 100 is described as being applied to debt management. In this case, the contractor is the debtor, the administrator is the creditor and their employee, and the deposit corresponds to repayment.

[0026] Fig. 2 is a diagram showing contract data. Contract data is data created for each individual contract, and is stored in contract information DB 106b. The example shown in Fig. 2 is a contract related to product code 1000, and is contract data related to credit number 900 of a certain debtor. The product code is an identification number for each product. The credit number is a number that identifies an individual contract.

[0027] FIG. 3 is a diagram showing repayment schedule data. The repayment schedule data is created based on each credit number and stored in the repayment schedule information DB 106c. In the example shown in FIG. 3, the repayment schedule for credit number 900 is shown. This repayment schedule is determined by the product code and the debt contract contents. The repayment schedule data includes the repayment date, repayment amount, principal, interest, pre-repayment balance, and post-repayment balance. The repayment date is the payment due date, and in this case, it spans multiple times. That is, the first repayment date is May 25, 2021 (hereinafter, the same year), and the repayment date is the 25th of each month thereafter. The repayment amount is the payment obligation amount for each repayment date, and in this case, it is 100,000 yen per month. The repayment amount is divided into principal and interest, and is shown in the corresponding column. In this case, the initial principal is 60,000 yen, and is set to increase by 5,000 yen thereafter. The initial interest is 40,000 yen, and is set to decrease by 5,000 yen thereafter. The pre-repayment balance is the balance before repayment on the corresponding repayment date. Here, the initial pre-repayment balance is 1 million yen. The after-payment balance is the balance after repayment on the corresponding repayment date. The after-payment balance is the balance before repayment - principal.

[0028] A debtor who has signed a contract based on the contract data shown in FIG. 2 will make monthly repayments in accordance with the repayment schedule data shown in FIG. 3. According to this repayment schedule data, the debtor will have to deposit the amount of the obligation to be paid, shown as "repayment amount," on the payment due date, shown as "repayment date." In other words, the debtor only needs to deposit the amount of the obligation to be paid into a designated account on the payment due date, as an obligation based on the contract. However, some debtors may deposit more than the amount of the obligation to be paid on the payment due date, or may deposit a designated amount before the payment due date when the obligation to pay has not arisen (in other words, the amount of the obligation to be paid has not yet arisen). This mainly occurs with products where the repayment method is "transfer." Also, with products where the repayment method is "withdrawal," a deposit may be required in cases where an overpayment exceeds the amount of the obligation to be paid for a transfer repayment in arrears.

[0029] In these cases, the debtor will treat any deposits that exceed the payment obligation as a deposit. There are various ways to handle deposits, but in this application, the deposit management device 100 pools the deposits until the next repayment, and appropriates (deposits) when the next repayment date arrives. This type of operation is assumed to be included in advance in the contract with the creditor (for example, the contract data shown in Figure 2).

[0030] In order to realize such an operation, the deposit management device 100 has the deposit recognition unit 102a recognize the date and amount of deposit from the debtor. The deposit recognition unit 102a basically checks the presence or absence of deposits every day, or performs deposit confirmation processing in conjunction with deposit notification information from the account system.

[0031] The deposit recording unit 102b then compares the amount of the deposit obtained by the deposit recognition unit 102a with the amount of the payment obligation on the date of the deposit, and records the difference as a deposit if the amount of the deposit exceeds the amount of the payment obligation on the date of the payment. Furthermore, when the date of the deposit from the debtor is the due date and the amount of the deposit exceeds the amount of the payment obligation on the due date, the deposit recording unit 102b records the difference as a deposit. Furthermore, when the date of the deposit from the debtor is before the due date and no payment obligation has occurred, the deposit recording unit 102b records the full amount of the deposit as a deposit. The deposit recording unit 102b basically checks whether or not a deposit has been made at the time when the deposit recognition unit 102a confirms the deposit, and performs processing.

[0032] The appropriation unit 102c is a processing unit that allocates the amount received from the debtor to the principal and interest, and if there is a deposit recorded at that time, the deposit is appropriated to the principal and interest as part or all of the payment obligation at that time. The appropriation unit 102c basically performs processing on the payment due date. In other words, the appropriation unit 102c allocates the deposit to the principal and interest on the first payment due date after the day the deposit recording unit 102b recorded the deposit. The appropriation unit 102c performs allocation for multiple contracts collectively in a batch process.

[0033] [2. Specific examples of processing] Here, we will explain specific example 1 and specific example 2 of the process executed by the deposit management device 100. In each example, it is assumed that a contract based on the contract data in Fig. 2 above is concluded, and repayment is scheduled based on the repayment schedule data in Fig. 3.

[0034] (Example 1) An example will be described in which a debtor deposits more than the amount of the obligation on the due date. Figure 4 shows transaction data that is set when a debtor makes a deposit on the due date that exceeds the amount of the obligation, where (a) shows the transaction data that is set on that due date, and (b) shows the transaction data that is set on the first due date thereafter.

[0035] In this example, the balance for the claim number 900 is 1 million yen, and although monthly repayments of 100,000 yen are scheduled, a deposit of 150,000 yen was made on the due date of May 25. In other words, an overpayment of 50,000 yen has occurred.

[0036] The deposit management device 100 creates the transaction data shown in FIG. 4(a). The transaction data is recorded and managed in the transaction information DB 106a. The "DATA CLASSIFICATION" field shows the transaction details with an identification code and text information. The "TRANSACTION DATE" field is the date of deposit in this case. The "DATE ​​OF APPLICATION" field is the date on which the repayment was appropriated, which in this case is both the payment due date and the date of deposit.

[0037] As described above, the date of deposit and the amount of deposit are recognized by the deposit recognition unit 102a. Then, since the amount of deposit (150,000 yen in this case) exceeds the amount of the payment obligation on the payment due date (100,000 yen in this case), the deposit recording unit 102b records the difference of 50,000 yen as a deposit. This deposit is recorded in the "Deposit" column of the transaction data.

[0038] The appropriation unit 102c is a processing unit that appropriates the amount received from the debtor to the principal and interest as described above. In this case, since there is no deposit before May 25th and there is a deposit on May 25th that is enough to cover the payment obligation of 100,000 yen, the appropriation process is performed according to the repayment schedule (see FIG. 3). In this case, of the 100,000 yen obtained by subtracting the deposit of 50,000 yen from the received amount of 150,000 yen, 60,000 yen is applied to the "approved principal" and recorded in the corresponding column, and the remaining 40,000 yen is applied to the "approved interest" and recorded in the corresponding column. The "balance" column shows the balance after the appropriation process is performed by the appropriation unit 102c, and in this case, it is recorded as 940,000 yen, which is the balance before repayment of 1 million yen minus the appropriated principal of 60,000 yen. The next payment due date is June 25th and is recorded in the "next repayment date" column.

[0039] The next payment due date, June 25th, corresponds to the first payment due date after the deposit is recorded. On this date, the transaction data shown in Figure 4(b) is created. This transaction data is the transaction data shown in Figure 4(a) with the addition and update of information related to the transaction on June 25th (mainly the information shown in bold).

[0040] Here, it is assumed that there is no deposit from the debtor. Even if there is no deposit from the debtor, June 25th is the due date, so the appropriation unit 102c performs batch processing. Although there is no deposit from the debtor, the appropriation unit 102c appropriates the 50,000 yen of the deposit recorded at that time as part of the 100,000 yen payment obligation at that time. In this case, since the 50,000 yen of the deposit is less than the 100,000 yen payment obligation, the appropriation unit 102c prioritizes the interest of the principal and interest of the payment obligation at that time. Since the repayment schedule on June 25th (see FIG. 3) is 65,000 yen for the principal and 35,000 yen for the interest, the appropriation unit 102c allocates 35,000 yen of the 50,000 yen of the deposit to interest and allocates the remaining 15,000 yen to the principal, and records them in the corresponding columns. At this point, the deposit becomes 0 and is recorded in the corresponding column.

[0041] According to the repayment schedule, the balance on June 25th should have been 875,000 yen (see FIG. 3), but in this case the application of the deposit alone is insufficient, so the balance becomes 925,000 yen and is recorded in the specified column. Also, since the application is insufficient to cover the amount of the payment obligation, a specified reminder notice is sent to the debtor. The reminder notice may be sent automatically via the application unit 102c, or via an operator.

[0042] The transaction on June 25th was not based on a normal deposit, but on a deposit that had been previously recorded, and an identification code and textual information to that effect are recorded in the "DATA CATEGORY" column.

[0043] Furthermore, when the deposit on the due date is equal to the amount owed, the appropriation unit 102c appropriates the entire deposit to the amount owed. Furthermore, when the deposit on the due date exceeds the amount owed, the appropriation unit 102c appropriates the deposit to the amount owed and records the excess amount as a deposit. When the deposit greatly exceeds the amount owed, processing such as a notice of warning to the debtor may be performed. The notice of warning may be performed automatically via the appropriation unit 102c or via an operator.

[0044] When a payment is received from the debtor on the due date of June 25, the appropriation unit 102c may perform the appropriation process based on the total amount of the received amount and the deposit that has been recorded in advance. In this case, the transaction data may record the appropriation process based on the payment on the due date of June 25 separately from the appropriation process based on the deposit at that time, or may record them together.

[0045] The deposit appropriation process by the appropriation unit 102c is basically performed automatically as a batch process on the due date, but a confirmation screen (see FIG. 6) may be displayed on the monitor 114 for the operator to confirm as necessary.

[0046] (Example 2) An example will be described in which a debtor deposits a specified amount before the due date when no payment obligation has arisen. Figure 5 shows transaction data that is set when a debtor deposits a specified amount before the due date when no payment obligation has arisen, where (a) shows transaction data that is set on the deposit date, and (b) shows transaction data that is set on the first repayment date thereafter. The transaction data in Figures 5(a) and (b) have the same format as that shown in Figures 4(a) and (b).

[0047] In this example, the balance for claim number 900 is 1 million yen, and although the payment due date is the 25th of each month, a deposit of 100,000 yen was made on May 20th, prior to the due date. The debtor's payment obligation is to deposit the amount due on the due date, and it is considered that there is no payment obligation prior to the due date. Therefore, on May 20th, the payment date, no application is made to the principal and interest, and the balance remains at 1 million yen.

[0048] The deposit management device 100 creates transaction data as shown in Fig. 5(a). The deposit date and amount are recognized by the deposit recognition unit 102a. The deposit accounting unit 102b then accounts for the entire amount (100,000 yen in this case) as a deposit, since no payment obligation has arisen on the deposit date.

[0049] Then, on May 25th, which is the first payment due date thereafter, the transaction data shown in Figure 5(b) is created. This transaction data is the transaction data shown in Figure 5(a) with information related to the transaction on May 25th (mainly the information shown in bold) added and updated.

[0050] Here, it is assumed that no payment has been received from the debtor. Even if there is no payment from the debtor, May 25th is the due date, so the allocation unit 102c performs batch processing. Although there is no payment from the debtor, the allocation unit 102c allocates the 100,000 yen of the deposit recorded at that time as the entire payment obligation of 100,000 yen at that time. As shown in the repayment schedule data (see Figure 3), the breakdown of the allocation is 60,000 yen for the principal and 40,000 yen for interest. At this point, the deposit becomes 0 and is recorded in the relevant column. The transaction on May 25th is not an allocation based on a normal payment, but is based on a deposit that was previously recorded, and an identification code and text information to that effect are recorded in the "DATA category" column.

[0051] FIG. 6 is a diagram showing a confirmation screen 400 displayed on the monitor 114 when the appropriation unit 102c performs the deposit appropriation process. The confirmation screen 400 is common to the above-mentioned specific example 1 and specific example 2. The confirmation screen 400 is used when the appropriation unit 102c performs batch processing on the payment due date. In this screen, the product code in the contract data is specified in the product code field 401, and the next repayment date in the transaction data is specified in the next repayment date field 402. Then, the operator operates the execute button 403 to execute the automatic appropriation process. To close the screen, the close button 404 is operated. The processing progress status field 405 displays the status of the processing by the appropriation unit 102c. When there are multiple processing targets by the appropriation unit 102c, the total number and the total amount are displayed below. Note that the title "Deposit Automatic Deposit Processing" in the confirmation screen 400 indicates the appropriation process by the appropriation unit 102c.

[0052] As described above, in this embodiment, when the deposit recognition unit 102a recognizes the date of deposit and the amount of deposit, the deposit accounting unit 102b compares the amount of deposit with the amount of payment obligation, and if the amount of deposit exceeds the amount of payment obligation, the difference is recorded as a deposit. Then, on the first payment due date after the day on which the deposit accounting unit 102b recorded the deposit, the appropriation unit 102c appropriates the deposit recorded at that time as part or all of the amount of payment obligation at that time. Therefore, in the deposit management work, it is no longer necessary to carry out individual deposit processing each time a deposit is made, as was previously done, and the operator's workload is reduced and work time is shortened, while administrative errors are prevented, management accuracy is improved, and efficient system operation is possible.

[0053] [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 contributing to goals 8 and 9 of the SDGs.

[0054] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0055] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

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

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

[0059] Furthermore, with regard to the deposit management device 100, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0060] For example, the processing functions of the deposit 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 in a non-transient 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 deposit management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processing is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form a control unit.

[0061] In addition, this computer program may be stored in an application program server connected to the deposit management device 100 via any network, and it is also possible to download all or part of it as needed.

[0062] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0063] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, 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 as multiple modules or libraries, and a program that works 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, may use well-known configurations and procedures.

[0064] The various databases etc. stored in the memory unit are storage means 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 etc. used for various processes and providing websites.

[0065] The deposit 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 deposit 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.

[0066] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to 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. [Industrial Applicability]

[0067] The present invention is particularly useful in managing payments for loans, credit, leases, and the like. [Explanation of symbols]

[0068] 100 Deposit Management Device 102 Control section 102a Deposit Recognition Section 102b Deposit Accounting Department 102c Appropriation Department 104 Communication interface section 106 Storage section 106a Transaction information DB 106b Contract information DB 106c Repayment schedule information DB 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Server device 300 Network

Claims

1. A deposit management device including a control unit and a memory unit, The control unit is a payment recognition means for confirming a payment for a claim and recognizing the payment date and the payment amount; a deposit recording means for acquiring the amount of the obligation to pay of the claim on the date of the deposit from the memory unit, comparing the amount of the deposit acquired by the deposit recognition means with the amount of the obligation to pay, and recording the difference as a deposit if the amount of the deposit exceeds the amount of the obligation to pay; the claim is stored in the storage unit as a claim having a plurality of payment due dates, and an appropriation means acquires the payment due dates from the storage unit and appropriates the deposit recorded at that time as a part or all of the payment obligation amount at that time on the first payment due date after the day on which the deposit recording means recorded the deposit; Equipped with The payment obligation is divided into principal and interest, The deposit management device is characterized in that the appropriation means allocates the deposit currently recorded on the first payment due date, with priority given to the interest of the payment obligation at that time.

2. The deposit recording means records the difference as a deposit when the date of receipt of the receivable is the due date and the amount of the receipt exceeds the amount of the obligation to pay on the due date.

2. The deposit management device according to claim 1.

3. The deposit recording means records the entire amount of the deposit as a deposit when the date of receipt of the payment for the claim is before the payment due date and no payment obligation has been incurred.

2. The deposit management device according to claim 1.

4. A deposit management method executed by a control unit of a deposit management device having a control unit and a memory unit, Executed by the control unit, a receipt recognition step of confirming receipt of receivables and recognizing the receipt date and amount; a deposit recording step of acquiring the amount of the obligation to pay of the claim on the date of the deposit from the storage unit, comparing the amount of the deposit obtained in the deposit recognition step with the amount of the obligation to pay, and recording the difference as a deposit if the amount of the deposit exceeds the amount of the obligation to pay; the claim is stored in the storage unit as a claim having multiple payment due dates, and an appropriation step of acquiring the payment due dates from the storage unit and appropriating the deposit recorded at that time to the first payment due date after the day on which the deposit was recorded in the deposit recording step as a part or all of the payment obligation at that time; Including, The payment obligation is divided into principal and interest, The deposit management method is characterized in that the allocation step allocates the deposit recorded at that time to the interest of the payment obligation at that time on the first payment due date, with priority given to the interest.

5. A deposit management program for causing a control unit of a deposit management device having a control unit and a memory unit to execute the deposit management program, The control unit, a receipt recognition step of confirming receipt of receivables and recognizing the receipt date and amount; a deposit recording step of acquiring the amount of the obligation to pay of the claim on the date of the deposit from the storage unit, comparing the amount of the deposit obtained in the deposit recognition step with the amount of the obligation to pay, and recording the difference as a deposit if the amount of the deposit exceeds the amount of the obligation to pay; the claim is stored in the storage unit as a claim having multiple payment due dates, and an appropriation step of acquiring the payment due dates from the storage unit and appropriating the deposit recorded at that time to the first payment due date after the day on which the deposit was recorded in the deposit recording step as a part or all of the payment obligation at that time; Run the command, The payment obligation is divided into principal and interest, The deposit management program is characterized in that the allocation step allocates the deposit currently recorded on the first payment due date to the interest of the payment obligation at that time with priority.

Images