Credit management device, credit management method, and credit management program

Abstract

To provide a credit management device, a credit management method, and a credit management program that can automatize calculation of an uncollected late payment charge taking a rate of allocation of a late payment charge in accordance with salability and an accuracy of collecting the late payment charge into consideration.SOLUTION: Uncollected money data in which the number of overdue days of an uncollected credit and an uncollected late payment charge at a predetermined point of time are set is acquired based on a commodity master in which the presence / absence of allocation of a late payment charge and a rate of allocation of the late payment charge per commodity are set in association, a credit master in which the presence / absence of collectability of a commodity and the late payment charge per credit are set in association, collection scheduled data in which a collection scheduled date and a collection scheduled amount per credit are set in association, and collection result data in which collection date and a collection amount per credit are set in association.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] Patent Document 1 discloses a configuration in which whether or not each billing item is subject to the calculation of late payment penalties is set in the master data, and the calculation formula for late payment penalties is set in the master data, thereby calculating late payment penalties as the product of the overdue amount of the billing item subject to the calculation of late payment penalties, a fixed annual rate of late payment, and the number of excess days divided by the number of calendar days. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-61617 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention described in Patent Document 1 above has a problem in that differences in the implementation method arise depending on the marketability and the likelihood of collecting late payment charges.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a receivables management device, a receivables management method, and a receivables management program that can automate the calculation of uncollected late fees by taking into account the rate at which late fees are recorded according to the product characteristics and the probability of collecting late fees. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the receivables management device of the present invention is a receivables management device equipped with a memory unit and a control unit, wherein the memory unit comprises a product master set by linking whether or not late fees will be recorded for each product and the recording rate of the late fees, a receivables master set by linking whether or not the product and the late fees are recoverable for each receivable, collection schedule data set by linking the planned collection date and planned collection amount for each receivable, and collection performance data set by linking the collection date and collection amount for each receivable, and the control unit comprises an accounts receivable acquisition means for acquiring accounts receivable data that sets the number of days overdue and accrued late fees for the uncollected receivables at a specified point in time based on the product master, the receivables master, the collection schedule data, and the collection performance data.

[0007] In addition, in the receivables management device of the present invention, the accounts receivable acquisition means calculates the number of days in arrears from the scheduled collection date set in the collection schedule data linked to the uncollected receivables, which are the receivables excluding the receivables set in the collection performance data, to the specified point in time, and acquires the receivables data by calculating the product of the scheduled collection amount set in the collection schedule data linked to the uncollected receivables, which are linked to the product, for which the recording status is set as yes in the product master, and for which the collectibility status is set as yes in the receivables master, by the recording rate set in the product master, and the number of days in arrears as the dividend and using the number of calendar days as the divisor.

[0008] In addition, in the receivables management device of the present invention, the accounts receivable acquisition means is characterized in that it acquires the accounts receivable data, which sets the number of days overdue and the uncollected late interest for the uncollected receivables at the end of the month, based on the product master, the receivables master, the collection schedule data and the collection performance data.

[0009] In addition, in the receivables management device of the present invention, the accounts receivable acquisition means is characterized in that, when new creation is set as the execution condition for the month-end closing process on the month-end closing process screen, it sets the closing month to the month following the month in which the month-end closing process was last executed, and when an instruction to execute the month-end closing process is set, it acquires the receivables data, which sets the number of days in arrears and the uncollected late interest for the uncollected receivables at the end of the month of the closing month, based on the product master, the receivables master, the collection schedule data and the collection performance data.

[0010] In addition, in the receivables management device of the present invention, the accounts receivable acquisition means is characterized in that, when re-creation is set as the execution condition for the month-end closing process on the month-end closing process screen, it sets the year and month in which the month-end closing process was last executed as the closing year and month, and when an instruction to execute the month-end closing process is set, it acquires the receivables data, which sets the number of overdue days and the uncollected late interest for the uncollected receivables at the end of the month of the closing year and month, based on the product master, the receivables master, the collection schedule data and the collection actual data.

[0011] In addition, in the receivables management device according to the present invention, the accounts receivable acquisition means is further characterized in that, when the closing date is set, the closing date is displayed on the month-end closing processing screen.

[0012] In addition, in the debt management device of the present invention, the control unit is further characterized by having a collection registration means which, when a deposit corresponding to the planned collection amount of the debt is made on a deposit date, sets the deposit date as the collection date, and acquires the collection performance data of the debt which is set by linking the planned collection amount to the collection amount, and registers the collection performance data in the debt management storage means.

[0013] In addition, the receivables management method of the present invention is a receivables management method to be executed by a receivables management device having a memory unit and a control unit, wherein the memory unit comprises a receivables management memory means for storing a product master set by linking whether or not late fees have been recorded for each product and the recording rate of the late fees, a receivables master set by linking whether or not the product and the late fees are recoverable for each receivable, collection schedule data set by linking the planned collection date and planned collection amount for each receivable, and collection performance data set by linking the collection date and collection amount for each receivable, and is characterized by including an accounts receivable acquisition step executed by the control unit for acquiring accounts receivable data that sets the number of days overdue and accrued late fees for the uncollected receivable at a specified point in time based on the product master, the receivables master, the collection schedule data, and the collection performance data.

[0014] In addition, the receivables management program of the present invention is a receivables management program to be executed by a receivables management device having a memory unit and a control unit, wherein the memory unit comprises a product master set by linking whether or not late fees have been recorded for each product and the recording rate of the late fees, a receivables master set by linking whether or not the product and the late fees are recoverable for each receivable, collection schedule data set by linking the planned collection date and planned collection amount for each receivable, and collection performance data set by linking the collection date and collection amount for each receivable, and is characterized in that the control unit executes an accounts receivable acquisition step that acquires accounts receivable data that sets the number of days overdue and accrued late fees for the uncollected receivables at a specified point in time based on the product master, the receivables master, the collection schedule data, and the collection performance data. [Effects of the Invention]

[0015] According to the present invention, the automation of monthly calculations reduces the workload and reduces the risk of calculation errors. Furthermore, according to the present invention, the automatic calculation of uncollected late fees improves business efficiency. Furthermore, according to the present invention, the accounting that takes into account the probability of collection leads to accurate management decisions. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a claim management device according to this embodiment. [Figure 2] FIG. 2 is a diagram showing an example of a product master in this embodiment. [Figure 3] FIG. 3 is a diagram showing an example of bond data in this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of collection schedule data in this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of collection record data in this embodiment. [Figure 6] FIG. 6 is a flowchart showing an example of processing performed by the claim management device in this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the bond management process in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the bond management process in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the bond management process in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the bond management process in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0017] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0018] [1. Overview] First, an outline of the present invention will be described.

[0019] Previously, there was no standard system for recording unpaid late fees, and systems customized for each user were used. Implementation methods differed depending on the product characteristics and the likelihood of collecting late fees (for example, when actually collecting, a "contracted interest rate" that is different from the "late fee interest rate" had to be used), so in order to implement it as a standard, flexible settings were required.

[0020] Therefore, in this embodiment, (1) a setting item for whether or not to record uncollected late fees and the rate at which uncollected fees are recorded are stored in the product master, (2) a setting item for whether or not late fees are recoverable depending on the debtor's situation is stored in the receivables data, and (3) a system is provided for calculating uncollected late fees as of the end of the month based on these settings. In other words, in this embodiment, a system is provided for calculating uncollected late fees based on the merchantability and the probability of collection of late fees.

[0021] [2. Configuration] An example of the configuration of a claim management device 100 according to this embodiment will be described with reference to Fig. 1 to Fig. 5. Fig. 1 is a block diagram showing an example of the configuration of a claim management device 100 according to this embodiment.

[0022] 1, the claim management device 100 is a commercially available desktop personal computer. Note that the claim management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0023] The bond 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 bond management device 100 is connected to each other so that they can communicate with each other via any communication path.

[0024] The communication interface unit 104 communicably connects the claim 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 claim 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).

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0026] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 may 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 claim management database 106a.

[0027] The receivables management database 106a stores receivables management data. Here, the receivables management database 106a may store a product master that links the presence or absence of recording of late charges for each product and the recording rate of late charges, a receivables master that links the presence or absence of collectibility of the product and late charges for each receivable, collection schedule data that links the scheduled collection date and scheduled collection amount for each receivable, and collection performance data that links the collection date and collection amount for each receivable. The receivables management database 106a may also store receivables data and / or accounts receivable data.

[0028] An example of the product master in this embodiment will now be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the product master in this embodiment.

[0029] As shown in Fig. 2, the product master in this embodiment holds settings for each product. In this embodiment, for example, even if an employee loan is overdue, there may be cases where no damages are collected because the employee and the company are directly involved in the transaction. In such cases, the unpaid late damages accrual flag in the product master is set to "0: not accrued" because the payment is not recognized as an unpaid amount.

[0030] An example of the bond data in this embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the bond data in this embodiment.

[0031] As shown in Figure 3, the credit data in this embodiment holds the latest status for each credit. In this embodiment, if the credit is due or settled and there is little possibility of collecting late payment charges, it is not desired to recognize it as an uncollected amount, so the late payment charges uncollectible flag is set to "1: Uncollectible" and is preset so that it is automatically determined and set depending on the status of the credit.

[0032] An example of collection schedule data in this embodiment will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of collection schedule data in this embodiment.

[0033] As shown in FIG. 4, the collection schedule data in this embodiment holds a collection schedule for each debt.

[0034] An example of collection record data in this embodiment will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of collection record data in this embodiment.

[0035] As shown in FIG. 5, the collection record data in this embodiment holds the collection record for each collection schedule.

[0036] Returning to Figure 1, the control unit 102 is a CPU or the like that performs overall control of the claim 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, required data, etc., and executes various information processing based on these stored programs. Functionally, the control unit 102 is equipped with a collection registration unit 102a and an accounts receivable acquisition unit 102b.

[0037] The collection registration unit 102a acquires the collection performance data of the claim and registers the collection performance data. Here, if a deposit corresponding to the scheduled collection amount of the claim is made on the deposit date, the collection registration unit 102a may acquire the collection performance data of the claim in which the deposit date is set as the collection date and the scheduled collection amount is linked to the collection amount, and register the collection performance data in the claim management database 106a.

[0038] The accounts receivable acquiring unit 102b acquires accounts receivable data for uncollected receivables. Here, the accounts receivable acquiring unit 102b may acquire accounts receivable data that sets the number of days in arrears and late payment penalties for uncollected receivables at a predetermined time point based on the product master, the receivable master, the collection schedule data, and the collection performance data. The accounts receivable acquiring unit 102b may also acquire the accounts receivable data by calculating the number of days in arrears from the scheduled collection date set in the collection schedule data linked to uncollected receivables, which are receivables excluding those set in the collection performance data, to a predetermined time point, and by using the product of the scheduled collection amount set in the collection schedule data linked to uncollected receivables, which are linked to products set as having a recordability in the product master and for which the receivable master is set as having collectibility, by the recordability rate set in the product master, and the number of days in arrears as the dividend and the divisor as the quotient of the product of the product of the scheduled collection amount set in the collection schedule data linked to uncollected receivables, which are linked to products set as having a recordability in the product master and for which the receivable master is set as having collectibility, by the recordability rate set in the product master, and the number of days in arrears as the divisor. Furthermore, the accounts receivable acquiring unit 102b may acquire accounts receivable data that sets the number of days in arrears and late unpaid penalties for uncollected receivables at the end of the month, based on the product master, the receivable master, the scheduled collection data, and the actual collection data. Furthermore, when "new creation" is set as the execution condition for month-end closing processing on the month-end closing processing screen, the accounts receivable acquiring unit 102b may set the closing month to the month following the month in which the month-end closing processing was last executed, and when an instruction to execute month-end closing processing is set, acquire accounts receivable data that sets the number of days in arrears and late unpaid penalties for uncollected receivables at the end of the closing month, based on the product master, the receivable master, the scheduled collection data, and the actual collection data. Furthermore, when re-creation is set as an execution condition for month-end closing processing on the month-end closing processing screen, the accounts receivable acquisition unit 102b may set the closing month to the year and month in which the month-end closing processing was last executed, and when an instruction to execute month-end closing processing is set, may acquire accounts receivable data that sets the number of overdue days and uncollected late charges for uncollected receivables at the end of the month of the closing month, based on the product master, receivable master, collection schedule data, and collection performance data. Furthermore, when a closing month is set, the accounts receivable acquisition unit 102b may display the closing month on the month-end closing processing screen.

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

[0040] [Accounts Management Processing] An example of the bond management process in this embodiment will now be described with reference to Fig. 6. Fig. 6 is a flowchart showing an example of the process of the bond management device 100 in this embodiment.

[0041] As shown in Figure 6, the accounts receivable acquisition unit 102b determines whether the user has set new creation as an execution condition for the month-end closing processing via the input device 112 on the month-end closing processing screen displayed on the output device 114 (step SA-1).

[0042] If the accounts receivable obtaining unit 102b determines that new creation has been set as the execution condition for month-end closing processing on the month-end closing processing screen (step SA-1: Yes), it shifts the process to step SA-2.

[0043] Then, the accounts receivable acquisition unit 102b sets the closing month to the month following the month in which the month-end closing process was last executed, and when the user sets an instruction to execute the month-end closing process via the input device 112 on the month-end closing process screen displayed on the output device 114, it acquires accounts receivable data that sets the number of days in arrears and uncollected late fees for uncollected receivables at the end of the closing month based on the product master, receivable master, collection schedule data, and collection performance data (step SA-2), and terminates the process.

[0044] On the other hand, if the collection registration unit 102a determines that new creation is not set as the execution condition for the month-end closing processing on the month-end closing processing screen (re-creation is set) (step SA-1: No), it transitions the processing to step SA-3.

[0045] Then, the accounts receivable acquisition unit 102b sets the closing month and year to the year and month in which the month-end closing process was last performed, and when the user sets an instruction to perform the month-end closing process via the input device 112 on the month-end closing process screen displayed on the output device 114, it acquires accounts receivable data that sets the number of days in arrears and uncollected late fees for uncollected receivables at the end of the closing month and year based on the product master, receivable master, collection schedule data, and collection performance data (step SA-3), and then terminates the process.

[0046] An example of the bond management process in this embodiment will now be described with reference to Figures 7 to 10. Figures 7 to 10 are diagrams showing an example of the bond management process in this embodiment.

[0047] As shown in Figure 7, in this embodiment, if new creation is specified as the creation category on the month-end closing processing screen, the month following the month in which the previous execution was performed is displayed as the closing year and month, and if re-creation is specified as the creation category on the month-end closing processing screen, the year and month in which the previous execution was performed is displayed as the closing year and month.

[0048] In this embodiment, when the execute button is pressed as shown in FIG. 7, scheduled collection data (data meeting the extraction conditions) that is unpaid as of December 31, 2023, is extracted and registered in the month-end unpaid data, as shown in FIG. 8. Here, the extraction conditions may be that the scheduled collection date of the scheduled collection data is before the last day of the closing month on the screen, that there is no record in the actual collection data that matches the "claim number" and "collection sequence" of the scheduled collection data, or that even if there is a record that matches the "claim number" and "collection sequence" of the scheduled collection data, the collected amount in the actual collection data is less than the planned collection amount in the scheduled collection data. Also, as shown in FIG. 8, in the month-end unpaid data in this embodiment, the actual collection data shows that payment has been made in November 2023, but payment has not been made in December 2023, and therefore the data is unpaid.

[0049] 9, in this embodiment, the number of days in arrears up to December 31, 2023 is calculated. Here, as shown in FIG. 9, in the end-of-month unpaid data in this embodiment, the number of days in arrears is the number of days from the day after the scheduled collection date to the end of the month.

[0050] As shown in Figure 10, in this embodiment, for receivables for which the "uncollected late payment damages accrual flag" in the product master linked to the receivables data is "1: accrued" and the "uncollected late payment damages flag" in the receivables data is "0: collectable," uncollected late payment damages are calculated using a formula.

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

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

[0053] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

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

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

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

[0057] Furthermore, with regard to the bond management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

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

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

[0060] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "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.

[0061] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0062] The various databases stored in the memory unit 106 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 used for various processes and providing websites.

[0063] The claim 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 claim management device 100 may also be realized by installing software (including programs or data, etc.) that causes the device to perform the processing described in this embodiment.

[0064] 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 configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0065] The present invention is useful in industries such as the financial industry, including the non-banking industry. [Explanation of symbols]

[0066] 100 Debt management device 102 Control section 102a Collection Registration Department 102b Accounts Receivable Collection Department 104 Communication interface unit 106 Storage section 106a Debt Management Database 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A debt management device comprising a memory unit and a control unit, The storage unit a product master that links together whether or not late fees are recorded for each product and the recording rate of said late fees, a receivable master that links together the product and whether or not late fees are recoverable for each receivable, collection schedule data that links together the scheduled collection date and the scheduled collection amount for each receivable, and collection performance data that links together the collection date and the collection amount for each receivable; Equipped with The control unit an account receivable acquisition means for acquiring account receivable data in which the number of days overdue and uncollected late charges for the uncollected account receivable at a predetermined time are set based on the product master, the account receivable master, the collection schedule data, and the collection performance data; A debt management device comprising:

2. The receivable acquisition means The receivables management device of claim 1, characterized in that the uncollected receivables data is obtained by calculating the number of days overdue from the scheduled collection date set in the collection schedule data linked to the uncollected receivables, which are the receivables excluding the receivables set in the collection performance data, to the specified point in time, and by calculating the product of the scheduled collection amount set in the collection schedule data linked to the uncollected receivables, which are linked to the products for which the recording status is set as yes in the product master, the recording rate set in the product master, and the number of days overdue as the dividend and the divisor as the quotient when the number of calendar days is used as the divisor as the uncollected late payment damages.

3. The receivable acquisition means The receivables management device of claim 1, characterized in that the receivables data is obtained based on the product master, the receivables master, the collection schedule data and the collection performance data, and the number of days overdue for the uncollected receivables at the end of the month and the uncollected late interest charges are set.

4. The receivable acquisition means The receivables management device described in claim 3, characterized in that when ``new creation'' is set as the execution condition for month-end closing processing on the month-end closing processing screen, the closing month is set to the month following the month in which the month-end closing processing was last executed, and when an instruction to execute the month-end closing processing is set, the receivables data is obtained based on the product master, the receivables master, the collection schedule data and the collection actual data, setting the number of days overdue and the uncollected late interest for the uncollected receivables at the end of the month of the closing month.

5. The receivable acquisition means The receivables management device described in claim 3, characterized in that when re-creation is set as the execution condition for the month-end closing process on the month-end closing process screen, the month and year in which the month-end closing process was last executed is set as the closing month, and when an instruction to execute the month-end closing process is set, the receivables data is obtained based on the product master, the receivables master, the collection schedule data and the collection performance data, setting the number of days overdue and the uncollected late interest for the uncollected receivables at the end of the month and year.

6. The receivable acquisition means 6. The debt management device according to claim 4, wherein when the closing date is set, the closing date is displayed on the end-of-month closing processing screen.

7. The control unit a collection registration means for acquiring the collection record data of the receivable, which is set as the collection date and linked to the estimated collection amount as the collection amount when a deposit corresponding to the estimated collection amount of the receivable is made on the deposit date, and registering the collection record data in the receivable management storage means; 6. The claim management device according to claim 1, further comprising:

8. A claim management method to be executed by a claim management device having a memory unit and a control unit, The storage unit a product master that links together whether or not late fees are recorded for each product and the recording rate of said late fees, a receivable master that links together the product and whether or not late fees are recoverable for each receivable, collection schedule data that links together the scheduled collection date and the scheduled collection amount for each receivable, and collection performance data that links together the collection date and the collection amount for each receivable; Equipped with Executed in the control unit: an accounts receivable acquisition step of acquiring accounts receivable data in which the number of days overdue and uncollected late charges for the uncollected accounts receivable at a predetermined time are set based on the product master, the accounts receivable master, the collection schedule data, and the collection performance data; A receivables management method comprising:

9. A claim management program to be executed by a claim management device having a memory unit and a control unit, The storage unit a product master that links together whether or not late fees are recorded for each product and the recording rate of said late fees, a receivable master that links together the product and whether or not late fees are recoverable for each receivable, collection schedule data that links together the scheduled collection date and the scheduled collection amount for each receivable, and collection performance data that links together the collection date and the collection amount for each receivable; Equipped with In the control unit, an accounts receivable acquisition step of acquiring accounts receivable data in which the number of days overdue and uncollected late charges for the uncollected accounts receivable at a predetermined time are set based on the product master, the accounts receivable master, the collection schedule data, and the collection performance data; A debt management program to implement this.

Images