Credit management device, credit management method, and credit management program
The receivables management device processes contracts with different expiration methods efficiently, reducing workload and oversight by using a control unit to adjust settings for unearned interest, late payment charges, and interest rates, enabling collective term expiration handling.
Patent Information
- Application Number
- JP2024013059
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-01-31
- Publication Date
- 2025-08-13
AI Technical Summary
Existing credit management systems face high workload and risk of oversight in processing the expiration of terms for contracts with different processing requirements, as they lack a unified method to handle various collection patterns efficiently.
A receivables management device with a control unit that processes data for each contract based on a pre-set collection pattern, adjusting settings for unearned interest, late payment charges, and interest rate updates, enabling simultaneous processing of contracts with different expiration methods.
This approach reduces workload and minimizes the risk of missed processing by allowing the expiration of terms to be handled collectively, ensuring accurate and efficient management of diverse contracts.
Smart Images

Figure 2025118013000001_ABST
Abstract
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] In the credit management business, there is a process to accelerate the benefit of the term when payments are not made. Also, some companies may accelerate the benefit of the term all at once for contracts that meet certain conditions. However, in such cases, the process differs depending on the characteristics of the contracted products, so it is not possible to process everything all at once.
[0003] For example, if a mortgage loan receivable becomes due, late payment charges calculated at the original late payment interest rate can be collected thereafter. However, if a credit purchase receivable becomes due, it is known that under the Installment Sales Act, an amount greater than the late payment charges calculated at the statutory interest rate cannot be collected.
[0004] For these reasons, the process of accruing the benefit of time has been a heavy workload and involved the risk of oversight. However, until now, no system has been known that efficiently processes the benefit of time (Patent Document 1). [Prior art documents] [Patent documents]
[0005] [Patent Document 1] Japanese Patent Application Publication No. 2023-110721 Summary of the Invention [Problem to be solved by the invention]
[0006] The object of this invention is to provide a new function that enables the processing of the expiration of the term to be carried out in one go, even for products or contracts that require different processing, by switching the settings regarding the processing method for the expiration of the term for each collection pattern linked to the product or contract, thereby reducing the workload and the risk of missed processing. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems and achieve the objectives, the receivables management device of the present invention is a receivables management device equipped with a control unit, characterized in that the control unit comprises: a reception means for receiving the specification of the default date and the specification of the contract; and a processing means for updating data for each contract specified in the reception means, based on the default date and the contract specified in the reception means, in accordance with a collection pattern specified in a pre-set master.
[0008] Furthermore, in the credit management device according to the present invention, when the processing means determines that the product corresponding to the contract specified in the reception means is specified, directly or indirectly, by a master preset for each contract specified in the reception means as a product for which unearned interest after the default date should be collected, the processing means deletes all records whose scheduled collection date is after the default date specified in the reception means from the collection schedule data in which records including scheduled collection dates and scheduled collection interest are stored, and sets the total of the scheduled collection interest of the deleted records as the scheduled collection interest, and creates one record whose scheduled collection date is the default date specified in the reception means as the collection date. When it is determined that the product corresponding to the contract specified in the reception means is directly or indirectly specified by the preset master as a product for which unearned interest after the default date should not be collected, all records having a scheduled collection date after the default date specified in the reception means are deleted from the collection schedule data, and of the scheduled interest to be collected of the deleted records, the scheduled interest to be collected up to the default date specified in the reception means is set as the scheduled interest to be collected, and one record having the scheduled collection date equal to the default date specified in the reception means is newly stored in the collection schedule data.
[0009] In addition, the debt management device of the present invention is characterized in that the records stored in the collection schedule data and the newly stored records include the scheduled collection date, the scheduled collection interest, and the scheduled collection principal, and the scheduled collection principal included in one record that the processing means newly stores in the collection schedule data is the sum of the scheduled collection principal of the records to be deleted.
[0010] In addition, the claims management device of the present invention is characterized in that, when the processing means determines, for each contract specified in the reception means, based on the preset master, that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which late payment charges should be waived when the benefit of the term expires, the processing means adds late payment charges at the time of expiration of the term as waived late payment charges in the claims transaction data in which waived late payment charges and carried-over late payment charges are registered, and when the processing means determines, for each contract specified in the reception means, based on the preset master, that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which late payment charges should be carried over when the benefit of the term expires, the processing means adds late payment charges at the time of expiration of the term as carried-over late payment charges in the claims transaction data.
[0011] In addition, the claims management device of the present invention is characterized in that the records stored in the claims transaction data and the newly stored records include claim identification information, waiver of late payment charges, and carried-over late payment charges, sorted by claim identification information and by transaction; and when the processing means determines, for each contract specified in the reception means, based on a preset master, that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which late payment charges should be waived when the benefit of time has expired, it newly stores in the claims transaction data a record containing claim identification information in which the waiver of late payment charges is the amount of late payment charges when the benefit of time has expired, the carried-over late payment charges is set to zero, and the claim identification information is the claim identification information corresponding to the contract specified in the reception means; and when it determines, based on the preset master, that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which late payment charges should be carried over when the benefit of time has expired, it newly stores in the claims transaction data a record in which the waiver of late payment charges is set to zero, the carried-over late payment charges is set to the amount of late payment charges when the benefit of time has expired, and the claim identification information is the claim identification information corresponding to the contract specified in the reception means.
[0012] In addition, the claims management device of the present invention is characterized in that, when the processing means determines, for each contract specified in the reception means, based on the master data preset, that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which the late damage interest rate in the claims data should be updated to the statutory interest rate, the processing means updates the late damage interest rate corresponding to the contract specified in the reception means in the claims data in which late damage interest rates are registered by contract to the statutory interest rate, and when the processing means determines, for each contract specified in the reception means, based on the master data preset, that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which the late damage interest rate in the claims data should not be updated to the statutory interest rate, the processing means does not update the claims data but leaves it as it is.
[0013] In addition, the receivables management device of the present invention is characterized in that the processing means makes a prescribed determination based on a master using a collection pattern master that stores records including collection pattern identification information distinguished by the presence or absence of a flag specifying that unaccrued interest after the date on which the benefit of the term has expired should be collected or a flag specifying that such unaccrued interest should not be collected, the presence or absence of a flag specifying that late payment charges should be waived when the benefit of the term has expired or a flag specifying that such late payment charges should be carried forward, and the presence or absence of a flag specifying that the late payment charge interest rate in the receivables data should be updated to the statutory interest rate or a flag specifying that it should not be updated to the statutory interest rate, and a product collection pattern linking master that specifies the relationship between the collection pattern identification information and the product.
[0014] In addition, the receivables management method of the present invention is a receivables management method executed in a receivables management device equipped with a control unit, and is characterized by including a reception step executed by the control unit for accepting the designation of the expiration date and the designation of the contract, and a processing step for updating data for each contract specified in the reception step based on the expiration date and the contract specified in the reception step, in accordance with a collection pattern specified in a pre-set master.
[0015] In addition, the receivables management program of the present invention is a receivables management program to be executed by a receivables management device equipped with a control unit, and is a program for causing the control unit to execute a reception step of accepting the designation of the default date and the designation of the contract, and a processing step of updating data for each contract designated in the reception step based on the default date and the contract designated in the reception step, in accordance with a collection pattern specified in a pre-set master. [Effects of the Invention]
[0016] According to the present invention, by switching the settings regarding the processing method for when the benefit of the term expires for each collection pattern linked to a product or contract, it is possible to process the benefit of the term expires in one go even for products or contracts that require different processing, thereby reducing the workload and the risk of missing processing. [Brief explanation of the drawings]
[0017] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a PC 100 according to an embodiment. [Figure 2] FIG. 2 is a diagram showing an example of the flow of processing for forfeiting the benefit of term by the processing unit 102b in one embodiment. [Figure 3A] 3A is a diagram showing an example of a screen for accepting execution of the process for forfeiting the benefit of the term in one embodiment, showing the screen before the target item list is displayed. [Figure 3B] 3B is a diagram showing an example of a screen for accepting execution of the process for forfeiting the benefit of the term in one embodiment. FIG. 3B shows the screen after the list of applicable details is displayed. [Figure 4] FIG. 4 is a diagram illustrating an example of the master storage unit 106a according to an embodiment. [Figure 5A] 5A is a diagram showing an example of the data storage unit 106b according to an embodiment of the present invention, which shows a state before the acceleration process in the case where the product is a mortgage loan. [Figure 5B]5B is a diagram showing an example of the data storage unit 106b according to an embodiment of the present invention, which shows the state after the acceleration process in the case where the product is a mortgage loan. [Figure 6A] 6A is a diagram showing an example of the data storage unit 106b according to an embodiment of the present invention, which shows the state before the acceleration process in the case where the product is purchased on credit. [Figure 6B] 6B is a diagram showing an example of the data storage unit 106b according to an embodiment of the present invention, which shows the state after the expiry of the term when the product is purchased on credit. DETAILED DESCRIPTION OF THE INVENTION
[0018] 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.
[0019] [1. Configuration] Here, an example of the configuration of a PC (personal computer) 100 according to this embodiment, including the debt management device of the present invention, will be described with reference to Figure 1. Note that the configuration of this embodiment is merely an example, and the present invention is not limited to being realized with the configuration of this embodiment. Also, in the following description of the configuration, duplicated explanations may be omitted.
[0020] 1 is a block diagram showing an example of the configuration of a PC 100. The PC 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108, and is communicably connected to a server 200 (such as a Web server) that stores various data (for example, the data stored in the storage unit 106, which may be the data described below) via a network 300 (such as the Internet, an intranet, or a LAN (Local Area Network)).
[0021] The components of the PC 100 are communicably connected via any communication path.
[0022] The PC 100 may be a stationary type such as a desktop personal computer, or may be a portable type such as a notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.
[0023] The control unit 102 is a CPU or the like that performs overall control of the PC 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 processes based on these stored programs.
[0024] The control unit 102 conceptually includes a receiving unit 102a, a processing unit 102b, and the like.
[0025] The reception unit 102a receives the specification of the default date and the specification of the contract. The specification of the contract received by the reception unit 102a is, for example, the specification of the corresponding contract identification information. The contract identification information is information that can identify an individual contract on a contract-by-contract basis, and can be, for example, an individual code, number, ID, name, etc. that can identify the contract.
[0026] The processing unit 102b updates the data for each contract specified in the reception unit 102a in accordance with the collection pattern specified in the master data set in advance, based on the contract and the expiration date specified in the reception unit 102a.
[0027] For each contract specified in the reception unit 102a, the processing unit 102b determines, based on a preset master, whether the product corresponding to the contract specified in the reception unit 102a is directly or indirectly specified as a product for which unearned interest should be collected after the default date, or whether the product is directly or indirectly specified as a product for which unearned interest should not be collected.
[0028] If the processing unit 102b determines, based on a preset master, that the product corresponding to the contract specified in the reception unit 102a is directly or indirectly specified as a product for which unaccrued interest should be collected after the default date, the processing unit 102b deletes all records with a scheduled collection date that falls on or after the default date specified in the reception unit 102a from the collection schedule data in which records including the scheduled collection date and the scheduled collection interest are stored, and sets the scheduled collection interest to the sum of the scheduled collection interest of the deleted records, and stores a new record in the collection schedule data whose scheduled collection date is the default date specified in the reception unit 102a.
[0029] If the processing unit 102b determines that the pre-set master directly or indirectly specifies that the product corresponding to the contract specified in the reception unit 102a is a product for which unaccrued interest after the default date should not be collected, the processing unit 102b deletes from the collection schedule data all records whose scheduled collection date is after the default date specified in the reception unit 102a, and sets the scheduled collection interest of the deleted records to the scheduled collection interest up to the default date specified in the reception unit 102a, and stores a new record in the collection schedule data whose scheduled collection date is the default date specified in the reception unit 102a.
[0030] In one embodiment, the records stored in the collection schedule data and the newly stored records include the principal amount to be collected. In this embodiment, the principal amount to be collected included in one record that the processing unit 102b newly stores in the collection schedule data is the sum of the principal amounts to be collected of the records to be deleted. In one embodiment, the records stored in the collection schedule data and the newly stored records include the total amount of the principal amount to be collected and the interest amount to be collected.
[0031] In one embodiment, the records stored in the collection schedule data and the newly stored records include contract identification information. The contract identification information in one record newly stored by the processing unit 102b is the contract identification information corresponding to the contract specified by the reception unit 102a. In one embodiment, the records stored in the collection schedule data and the newly stored records include collection identification information that is individual for each record. The collection identification information may be, for example, a code, number, ID, name, etc. that is individual for each record.
[0032] For each contract specified in the reception unit 102a, the processing unit 102b determines, based on a preset master, whether the product corresponding to the contract specified in the reception unit 102a is directly or indirectly specified as a product for which late payment charges should be waived when the benefit of the term is lost, or whether the product is directly or indirectly specified as a product for which late payment charges should be carried over.
[0033] When the processing unit 102b determines, based on the preset master, that the product corresponding to the contract specified in the receiving unit 102a is directly or indirectly specified as a product for which late payment charges should be waived when the benefit of time has expired, the processing unit 102b adds the late payment charges when the benefit of time has expired as the late payment charges for waiver in the claim transaction data in which the waived late payment charges and the carried-over late payment charges are registered. In this case, more specifically, the processing unit 102b sets the waived late payment charges to the amount of the late payment charges when the benefit of time has expired, sets the carried-over late payment charges to zero, and stores a new record in the claim transaction data containing claim identification information in which the claim identification information is the claim identification information corresponding to the contract specified in the receiving unit 102a.
[0034] When the processing unit 102b determines, based on the preset master, that the product corresponding to the contract designated in the receiving means is directly or indirectly specified as a product for which late payment charges at the time of default should be carried over, the processing unit 102b adds the late payment charges at the time of default as the carried-over late payment charges in the claim transaction data in which the waived late payment charges and the carried-over late payment charges are registered. In this case, more specifically, the processing unit 102b sets the waived late payment charges to zero, sets the carried-over late payment charges to the amount of late payment charges at the time of default, and stores a new record in the claim transaction data in which the claim identification information is the claim identification information corresponding to the contract designated in the receiving unit 102a.
[0035] Records stored in the bond transaction data and newly stored records include bond identification information, waived late payment penalties, and carried-over late payment penalties for each bond identification information and for each transaction. Bond identification information is information that can identify individual bonds on a bond-by-bond basis, and can be, for example, an individual code, number, ID, name, etc. that can identify a bond. In one embodiment, records stored in the bond transaction data and newly stored records include individual transaction identification information and transaction content identification information for each record. Transaction identification information can be, for example, an individual code, number, ID, name, etc. that can identify each record. Transaction content identification information is information that can identify the transaction content, and can be, for example, an individual code, number, ID, name, etc. that can identify the transaction content.
[0036] For each contract specified in the reception unit 102a, the processing unit 102b determines, using a pre-set master, whether the product corresponding to the contract specified in the reception unit 102a is directly or indirectly specified as a product for which the late payment damage interest rate in the bond data should be updated to the statutory interest rate, or whether the product is directly or indirectly specified as a product for which the late payment damage interest rate in the bond data should not be updated to the statutory interest rate.
[0037] If the processing unit 102b determines, based on a pre-set master, that the product corresponding to the contract specified in the reception unit 102a is directly or indirectly specified as a product for which the late payment damage interest rate in the bond data should be updated to the statutory interest rate, the processing unit 102b updates the late payment damage interest rate corresponding to the contract specified in the reception unit 102a to the statutory interest rate in the bond data in which late payment damage interest rates are registered by contract.
[0038] If the processing unit 102b determines, based on the pre-set master, that the product corresponding to the contract specified in the reception unit 102a is directly or indirectly specified as a product for which the late payment damage interest rate in the bond data should not be updated to the statutory interest rate, the processing unit 102b will maintain the bond data in which the late payment damage interest rate is registered for each contract as is, without updating it.
[0039] The late payment damage interest rate for each contract registered in the claim data is included in a record stored for each contract in the claim data. In one embodiment, the record stored in the claim data includes contract identification information and claim identification information, thereby linking the contract identification information and the claim identification information.
[0040] In one embodiment, the processing unit 102b performs a determination of the specification based on the master using a collection pattern master that stores records including collection pattern identification information distinguished by the presence or absence of a flag specifying that unaccrued interest after the date of default should be collected or a flag specifying that the unaccrued interest should not be collected, the presence or absence of a flag specifying that late payment charges should be waived at the time of default or a flag specifying that the late payment charges should be carried forward, and the presence or absence of a flag specifying that the late payment charge interest rate of the receivables data should be updated to the statutory interest rate or a flag specifying that it should not be updated to the statutory interest rate, for each collection pattern, and a product collection pattern linking master that specifies the relationship between the collection pattern identification information and the product.
[0041] The product collection pattern linking master stores records including combinations of collection pattern identification information and product identification information, thereby defining the relationship between the collection pattern identification information and the product. The product identification information is information that can identify an individual product, and can be, for example, an individual code, number, ID, name, etc. that can identify the product.
[0042] In one embodiment, the product identification information is included in a record stored in the contract data together with the contract identification information, thereby linking the contract identification information to the product identification information. In addition to the contract identification information, the contract data includes customer identification information, the number of months in arrears, etc. The customer identification information is information that can identify a customer, and can be, for example, an individual code, number, ID, name, etc. that can identify a customer. In one embodiment, the collection pattern identification information is included in a record stored in the debt data, and is linked to the contract identification information and debt identification information.
[0043] The communication interface unit 104 communicably connects the PC 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line.
[0044] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. 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.
[0045] The storage unit 106 conceptually includes a master storage unit 106a, a data storage unit 106b, and the like.
[0046] The master storage unit 106a stores various masters such as a product master, a product collection pattern linking master, a collection pattern master, and a system control master. The product master stores records containing product identification information and information about products other than the product identification information. The system control master stores information such as legal interest rates.
[0047] The data storage unit 106b stores various data such as contract data, claim data, claim transaction data, collection schedule data, and collection performance data. The collection performance data is similar to the collection schedule data except that the stored records do not include a scheduled collection date, and when collection of a claim corresponding to a record stored in the collection schedule data is executed, a record corresponding to that record is stored.
[0048] An input device 400 and an output device 500 are connected to the input / output interface unit 108. The output device 400 includes display devices such as a display or projector, audio devices such as speakers, printing devices such as printers, as well as devices that allow downloading in data file format. The data file format may be a file format known in the art, such as PDF, CSV, document file, spreadsheet file, or text file. The input device 500 may include a keyboard, mouse, microphone, or a monitor that functions as a pointing device in cooperation with a mouse.
[0049] [2. Specific Examples] Hereinafter, the acceptance of the specification of the default date and the specification of the contract by the acceptance unit 102a, and the default processing by the processing unit 102b will be described in detail with reference to FIGS. 2 to 6B using a specific example.
[0050] 2 is a diagram showing an example of the flow of the process for preventing the advancement of a term by the processing unit 102b in this specific example. Each step of the flow of the process for preventing the advancement of a term shown in FIG. 2 will be described below.
[0051] After the reception unit 102a receives the specification of the default date and the specification of the contract, the processing unit 102b determines whether the product corresponding to the contract specified by the reception unit 102a is a product for which the late payment damage interest rate in the receivables data should be updated to the statutory interest rate, based on whether a flag specifying that the late payment damage interest rate should be updated to the statutory interest rate is set ("1") or not ("0") for the collection pattern code corresponding to the product (S01).
[0052] If the flag is set to "1" and the processing unit 102b determines that the product is one for which the late payment interest rate in the bond data should be updated to the statutory interest rate (S01-YES), it updates the late payment interest rate in the bond data corresponding to the contract specified in the reception unit 102a to the statutory interest rate (S02); on the other hand, if the flag is not set to "0" and the product is one for which the late payment interest rate should not be updated (S01-NO), it does not update the bond data and leaves it as it is.
[0053] Next, the processing unit 102b determines whether the product corresponding to the contract specified in the reception unit 102a is a product for which late payment charges should be waived when the benefit of the term is lost, based on whether a flag specifying that late payment charges should be waived is set ("1") or not set ("0") for the collection pattern code corresponding to the product (S03).
[0054] If the flag is set to "1" and the processing unit 102b determines that the product is one for which late payment charges should be waived when the benefit of the term expires (S03-YES), it adds the late payment charges at the time of expiration of the term as waived late payment charges in the receivables transaction data (S04B); on the other hand, if the flag is not set to "0" and the processing unit 102b determines that the product is one for which late payment charges should not be waived when the benefit of the term expires and the late payment charges should be carried forward (S03-NO), it adds the late payment charges at the time of expiration of the term as carried forward late payment charges in the receivables transaction data (S04A).
[0055] Next, the processing unit 102b determines whether the product corresponding to the contract specified in the reception unit 102a is a product for which unearned interest should be collected after the expiry date by determining whether a flag specifying that unearned interest should be collected is set ("1") or not ("0") in the collection pattern code corresponding to the product (S05).
[0056] If the flag is set to "1" and the processing unit 102b determines that the product is one for which unearned interest after the default date should be collected (S05-YES), it deletes all records whose scheduled collection date is after the default date specified by the reception unit 102a, and sets the total of the scheduled collection interest of the deleted records as the scheduled collection interest, and stores a new record whose scheduled collection date is the default date specified by the reception unit 102a in the collection schedule data (S06B). On the other hand, if the flag is not set to "0" and the unearned interest after the default date should be collected, the processing unit 102b If it is determined that the product is one for which unaccrued interest after the forfeiture date should not be collected (S05-NO), all records with a scheduled collection date after the forfeiture date specified in the reception unit 102a are deleted from the collection schedule data, and of the scheduled collection interest of the deleted records, the scheduled collection interest up to the forfeiture date specified in the reception unit 102a is set as the scheduled collection interest, and one record with the scheduled collection date set to the forfeiture date specified in the reception unit 102a is newly stored in the collection schedule data (S06A).
[0057] 3A and 3B show the execution acceptance screen for the default processing in this specific example, where Fig. 3A shows the screen before the display of a list of target details that match the specified conditions, and Fig. 3B shows the screen after the display of the list of target details. As shown in Fig. 3A and 3B, the execution acceptance screen for the default processing in this specific example includes an execution condition input field consisting of an input field for the default date, an input field for the reason code, and an input field for a summary, an input field for the product code (product identification information), an input field for the upper and lower limits of the number of months of overdue, an input field for the customer number (customer identification information), and an input field for the contract number (same as the contract ID) (contract identification information), a display button for displaying a list of target details that match the specified conditions, a button to add target details, a button to delete target details, and a target details list display field consisting of an error flag, error content, contract ID (contract identification information), customer number (customer identification information), and customer name.
[0058] The following describes the process of accepting the specification of the default date and the contract specification by the acceptance unit 102a. First, the user opens the execution acceptance screen as shown in Fig. 3A, enters the default date "2023 / 5 / 15" in the entry field for the default date on the execution acceptance screen, specifies the default date, and further enters "3" to "3" in the upper and lower limit entry field for the number of months overdue to extract appropriate targets for default, and then presses the display button.
[0059] After the user presses the display button, the reception unit 102a extracts target details that match the extraction conditions and execution conditions from the contract data and displays a list of target details in the target details list display field, as shown on the execution reception screen in Figure 3B. In Figure 3B, the target details list displays two pieces of contract information: contract information for contract ID "1000001" and contract information for contract ID "200001." After the information is displayed, the user confirms whether the contract contents in the target details list are appropriate as targets and presses the execute button. After the user presses the execute button, the reception unit 102a accepts the contract information for the two pieces of contract information displayed in the target details list display field as shown in Figure 3B, along with the specification of the forfeiture date "5 / 15 / 2023," as contract designations. Based on this, the processing unit 102b performs forfeiture processing.
[0060] The above is an example in which the processing unit 102b simultaneously performs the process of forfeiting the benefit of the term for two pieces of contract information. In the following explanation of the process of forfeiting the benefit of the term by the processing unit 102b, the first example (in which the product is a mortgage) is when only the contract information with contract ID "1000001" is displayed in the target detail list display field on the execution acceptance screen, and the second example (in which the product is a credit purchase intermediation) is when only the contract information with contract ID "100002" is displayed in the target detail list display field on the execution acceptance screen. These two examples will be explained as they have different contents recorded in the data storage unit 106b.
[0061] 4 is a diagram showing the master storage unit 106a in this specific example. As shown in FIG. 4, the master storage unit 106a in this specific example stores a product master 106aa, a product collection pattern linking master 106ab, a collection pattern master 106ac, and a system control master 106ad.
[0062] The product master 106aa in this specific example stores records for each product code, each consisting of a combination of a product code (product identification information) and a product name, and defines the relationship between the product code and the product name. The product collection pattern linking master 106ab in this specific example stores records for each product code, each consisting of a combination of a product code (product identification information) and a collection pattern code (collection pattern identification information), and defines the relationship between the product code and the collection pattern code.
[0063] The collection pattern master 106ac in this specific example stores records for each collection pattern code, which consist of a collection pattern code (collection pattern identification information), the presence or absence of a flag specifying that the late payment damage interest rate should be updated to the statutory interest rate ('1' means the flag is present, '0' means the flag is absent, and so on), the presence or absence of a flag specifying that the late payment damage should be waived, and the presence or absence of a flag specifying that unearned interest should be collected, and defines the collection pattern for each collection pattern code.The system control master 106ad in this specific example has the statutory interest rate registered.
[0064] Figures 5A, 5B, 6A, and 6B are diagrams showing data storage unit 106b in this specific example. Figure 5A shows the first example (where the product is a mortgage) of this specific example before the acceleration process, Figure 5B shows the first example after the acceleration process, Figure 6A shows the second example (where the product is a credit purchase intermediation) of this specific example before the acceleration process, and Figure 6B shows the second example after the acceleration process.
[0065] In this specific example, the data storage unit 106b stores contract data 106ba, claim data 106bb, claim transaction history data (claim transaction data) 106bc, collection schedule data 106bd, and collection performance data 106be, as shown in Figures 5A, 5B, 6A, and 6B.
[0066] In this specific example, contract data 106ba stores records for each contract ID, each consisting of a combination of contract ID (contract identification information), product code (product identification information), customer number (customer identification information), customer name, and number of months in arrears, and information about the contract is registered for each contract ID. In this specific example, receivable data 106bb stores records for each receivable ID, each consisting of a combination of receivable ID (receivable identification information), contract ID (contract identification information), collection pattern code (collection pattern identification information), and late damage interest rate, and information about the receivable is registered for each receivable ID.
[0067] In this specific example, the bond transaction history data (bond transaction data) 106bc stores records for each transaction history SEQ, each consisting of a combination of bond ID (bond identification information), transaction history SEQ (transaction identification information), transaction content code (transaction content identification information), carried over late payment penalties, and waived late payment penalties. The collection schedule data 106bd in this specific example stores records for each collection SEQ, each consisting of a combination of contract ID (contract identification information), collection SEQ (collection identification information), scheduled collection date, principal (principal to be collected), interest (interest to be collected), and the total amount of principal and interest. The collection performance data 106be in this specific example stores records for each collection SEQ, each consisting of a combination of contract ID (contract identification information), collection SEQ (collection identification information), principal (principal to be collected), and interest (interest to be collected).
[0068] (First example: when the product is a mortgage) In the first example, the contract data differs from the example described using Figures 3A and 3B. First, unlike the target detail list display field of the execution reception screen in Figure 3B, which displays one contract information, assume that only one contract information with contract ID "1000001" (customer number "A1000001", customer name "Yamada Taro") is displayed in the target detail list display field. In response to this, the user presses the execute button, and the reception unit 102a accepts the contract information's contract ID "1000001" as the contract specification along with the specification of the expiration date "5 / 15 / 2023" for the single contract information, and the processing unit 102b performs expiration processing.
[0069] The process of the processing unit 102b for expiring the benefit of the term in the first case will be described in detail below.
[0070] After the reception unit 102a accepts the specification of the expiration date "2023 / 5 / 15" and the contract specification (contract ID "1000001", customer number "A1000001", customer name "Yamada Taro"), the processing unit 102b extracts the record corresponding to the contract ID "1000001" from the contract data 106ba shown in Figure 5A based on the contract specification accepted by the reception unit 102a, and identifies the product code "0001" corresponding to the contract ID "1000001".
[0071] The processing unit 102b further extracts a record corresponding to the identified product code "0001" from the product collection pattern linking master 106ab shown in FIG. 4, and identifies the collection pattern code "10001" corresponding to the product code "0001".
[0072] The processing unit 102b further extracts a record corresponding to the identified collection pattern code "10001" from the collection pattern master 106ac shown in Fig. 4. The record of the collection pattern code "10001" extracted from the collection pattern master 106ac has three corresponding flag items, and the processing unit 102b performs processing based on these. These will be explained in order below.
[0073] First, in the record of collection pattern code "10001" extracted from the collection pattern master 106ac, as shown in Fig. 4, the flag specifying that the late damage interest rate at the time of default should be updated to the statutory interest rate is not set ("0"). Therefore, the processing unit 102b determines that the product with product code "0001" is a product for which the late damage interest rate in the bond data should not be updated to the statutory interest rate (S01-NO). Based on the determination result, the processing unit 102b does not update the bond data 106bb in Fig. 5A, but maintains the late damage interest rate of "0.14" as it is, as shown in the bond data 106bb in Fig. 5B.
[0074] Secondly, in the record of the collection pattern code "10001" extracted from the collection pattern master 106ac, the flag specifying that the late payment charge should be waived when the benefit of the term is lost is not set to "0", as shown in Fig. 4. Therefore, the processing unit 102b determines that the product with the product code "0001" is not a product for which the late payment charge should be waived, but a product for which the late payment charge should be carried over (S03-NO).
[0075] Based on the determination result, the processing unit 102b extracts a record corresponding to the contract ID "1000001" from the claim data 106bb, identifies the claim ID "2000001" corresponding to the contract ID "1000001", calculates the amount of late payment penalty at the time of forfeiture of the benefit of the term "5,615", and creates and stores a record for the claim transaction history data 106bc in Figure 5A, as shown in the bottom row of the claim transaction history data 106bc in Figure 5B, with the identified claim ID set to "2000001", the transaction history SEQ set to SEQ "4" assigned sequentially by claim ID, the transaction content code set to "1800: forfeiture of the benefit of the term", the waiver late payment penalty set to zero "0", and the carried-over late payment penalty set to the amount of late payment penalty at the time of forfeiture of the term "5,615" (S04A).
[0076] Third, in the record of the collection pattern code "10001" extracted from the collection pattern master 106ac, the flag specifying that unearned interest after the forfeiture date should be collected is not set to "0", as shown in Fig. 4. Therefore, the processing unit 102b determines that the product with the product code "0001" is a product for which unearned interest should not be collected (S05-NO).
[0077] First, the processing unit 102b deletes all records from the collection schedule data 106bd of FIG. 5A whose scheduled collection date is on or after the deadline benefit forfeiture date "2023 / 5 / 15" specified by the receiving unit 102a (i.e., records with collection SEQs "5" to "7" in the collection schedule data 106bd of FIG. 5A), as shown in the collection schedule data 106bd of FIG. 5B.
[0078] On the other hand, based on the determination result, the processing unit 102b sets the contract ID "1000001" based on the contract specification accepted by the accepting unit 102a as the contract ID for the collection schedule data 106bd of FIG. 5A, sets the sum of the principal amounts of the deleted records (i.e., the records of collection SEQs "5" to "7" in the collection schedule data 106bd of FIG. 5A) to "45,000" as the principal (14,000 + 15,000 + 16,000), and sets the sum of the principal amounts of the deleted records (i.e., the records of collection SEQs "5" to "7" in the collection schedule data 106bd of FIG. 5A) to "45,000" as the principal (14,000 + 15,000 + 16,000). The interest up to the specified forfeiture date "2023 / 5 / 15" (i.e., the interest for the record of collection SEQ "5" whose scheduled collection date in the collection schedule data 106bd of Figure 5A is "2023 / 5 / 15") is "16,000", the sum of the principal and interest is "61,000" is the total amount (45,000 + 16,000), the forfeiture date "2023 / 5 / 15" specified in the reception unit 102a is the scheduled collection date, and a new record is stored with SEQ "5" assigned as the collection SEQ (S06A).
[0079] By performing the above processing, the collection schedule data 106bd in FIG. 5A is updated to the collection schedule data 106bd as shown in FIG. 5B, and the process of expiring the benefit of the term for the contract ID "1000001" based on the contract specification accepted by the accepting unit 102a is completed.
[0080] (Second example: When the product is purchased on credit) The second example also differs in contract data from the example described using Figures 3A and 3B. First, unlike the target detail list display field of the execution reception screen in Figure 3B, which displays one contract information, assume that only one contract information with contract ID "2000001" (customer number "A2000001", customer name "Tanaka Jiro") is displayed in the target detail list display field. In response to this, the user presses the execute button, and the reception unit 102a accepts the contract information's contract ID "2000001" as the contract specification along with the specification of the expiration date "5 / 15 / 2023" for the single contract information, and the processing unit 102b performs expiration processing.
[0081] The process of the processing unit 102b for expiring the benefit of the term in the second case will be described in detail below.
[0082] After the reception unit 102a accepts the specification of the expiration date "2023 / 5 / 15" and the contract specification (contract ID "2000001", customer number "A2000001", customer name "Tanaka Jiro"), the processing unit 102b extracts the record corresponding to the contract ID "2000001" from the contract data 106ba shown in Figure 6A based on the contract specification accepted by the reception unit 102a, and identifies the product code "0002" corresponding to the contract ID "2000001".
[0083] The processing unit 102b further extracts a record corresponding to the identified product code "0002" from the product collection pattern linking master 106ab shown in FIG. 4, and identifies the collection pattern code "10002" corresponding to the product code "0002".
[0084] The processing unit 102b further extracts a record corresponding to the identified collection pattern code "10002" from the collection pattern master 106ac shown in Fig. 4. The record of the collection pattern code "10002" extracted from the collection pattern master 106ac has three corresponding flag items, and the processing unit 102b performs processing based on these. These will be explained in order below.
[0085] First, in the record of the collection pattern code "10002" extracted from the collection pattern master 106ac, as shown in Fig. 4, a flag specifying that the late damage interest rate at the time of default should be updated to the statutory interest rate is set to "1." Therefore, the processing unit 102b determines that the product with the product code "0002" is a product for which the late damage interest rate in the bond data should be updated to the statutory interest rate (S01-YES). Based on the determination result, the processing unit 102b updates the late damage interest rate "0.14" in the record of the contract ID "2000001" corresponding to the contract specified by the reception unit 102a in the bond data 106bb of Fig. 6A to the statutory interest rate "0.03" in the system control master 106ad of Fig. 4, as in the bond data 106bb of Fig. 6B (S02).
[0086] Secondly, in the record of the collection pattern code "10002" extracted from the collection pattern master 106ac, the flag specifying that the late payment charge should be waived when the benefit of the term is lost is set to "1", as shown in Fig. 4. Therefore, the processing unit 102b determines that the product with the product code "0002" is a product for which the late payment charge should be waived (S03-YES).
[0087] Based on the determination result, the processing unit 102b extracts a record corresponding to the contract ID "2000001" from the claim data 106bb, identifies the claim ID "2000001" corresponding to the contract ID "2000001", calculates the amount of late payment penalty at the time of forfeiture of the benefit of the term "5,615", and creates and stores a record for the claim transaction history data 106bc in Figure 6A, with the identified claim ID set to "2000001", the transaction history SEQ set to SEQ "4" assigned sequentially by claim ID, the transaction content code set to "1800: forfeiture of the benefit of the term", the waiver late payment penalty set to the amount of late payment penalty at the time of forfeiture of the benefit of the term "5,615", and the carried-over late payment penalty set to zero "0", as shown in the bottom row of the claim transaction history data 106bc in Figure 6B (S04B).
[0088] Third, in the record of the collection pattern code "10002" extracted from the collection pattern master 106ac, the flag specifying that unearned interest after the forfeiture date should be collected is set to "1", as shown in Fig. 4. Therefore, the processing unit 102b determines that the product with the product code "0002" is a product for which unearned interest should be collected (S05-YES).
[0089] First, the processing unit 102b deletes all records from the collection schedule data 106bd of FIG. 6A whose scheduled collection date is on or after the deadline loss date "2023 / 5 / 15" specified by the receiving unit 102a (i.e., records with collection SEQs "5" to "7" in the collection schedule data 106bd of FIG. 6A), as shown in the collection schedule data 106bd of FIG. 6B.
[0090] On the other hand, based on the determination result, the processing unit 102b sets the contract ID "2000001" based on the contract specification accepted by the accepting unit 102a as the contract ID for the collection schedule data 106bd of FIG. 6A, as shown in FIG. 6B, and sets the sum of the principal amount "45,000" and the sum of the interest amount "45,000" for the deleted records (i.e., the records of collection SEQs "5" to "7" in the collection schedule data 106bd of FIG. 6A). " are set as the principal and interest, respectively (14,000+15,000+16,000)(16,000+15,000+14,000), the sum of the principal and interest "90,000" is set as the total amount (45,000+45,000), the forfeiture date "2023 / 5 / 15" specified in the reception unit 102a is set as the scheduled collection date, and one record with SEQ "5" assigned as the collection SEQ is newly stored (S06B).
[0091] By performing the above processing, the collection schedule data 106bd in FIG. 6A is updated to the collection schedule data 106bd as shown in FIG. 6B, and the process of expiring the benefit of the term for the contract ID "2000001" based on the contract specification accepted by the accepting unit 102a is completed.
[0092] When comparing the data in data storage unit 106b shown in Figure 5B updated in the first case with the data in data storage unit 106b shown in Figure 6B updated in the second case, the difference is that the late payment loss interest rate in claim data 106bb in Figure 5B is the original annual interest rate of "0.14", while in claim data 106bb in Figure 6B it has been updated to the statutory interest rate of "0.03".
[0093] Furthermore, the difference is that in the receivables transaction history data 106bc in Figure 5B, a record has been newly stored in which the waived late payment charge is set to zero ("0") and the carried-over late payment charge is set to the amount of late payment charge at the time of loss of the benefit of the term ("5,615"), whereas in the receivables transaction history data 106bc in Figure 6B, a record has been newly stored in which the waived late payment charge is set to the amount of late payment charge at the time of loss of the benefit of the term ("5,615") and the carried-over late payment charge is set to zero ("0").
[0094] Furthermore, the difference between the scheduled collection data 106bd shown in Figure 5B and the scheduled collection data 106bd shown in Figure 6B is that a newly stored record has been created in which the interest is set to "16,000" from the scheduled collection interest of the deleted record up to the forfeiture date of the term "5 / 15 / 2023" specified in the reception unit 102a, whereas the newly stored record has been created in which the interest is set to "45,000" which is the total interest of the deleted record.
[0095] In this way, even if there are a mixture of products and contracts that require different processing when the benefit of the term expires, they can be processed in bulk depending on the settings for each collection pattern linked to each contract and each product based on the collection pattern master 106ac in Figure 4.
[0096] Therefore, according to the present invention, it is possible to reduce the workload and the risk of processing omissions.
[0097] [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 the achievement of SDGs Goals 8 and 9.
[0098] 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.
[0099] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.
[0100] 4. Other Embodiments Although the embodiments of the present invention have been described above, the present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept described in the claims.
[0101] For example, among the processes described in the above-mentioned 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.
[0102] 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 the above documents and drawings can be changed as desired unless otherwise specified.
[0103] Furthermore, with regard to the PC 100, the components shown in the drawings are functional concepts, and do not necessarily have to be physically configured as shown in the drawings.
[0104] For example, all or any part of the processing functions of each device constituting PC 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by each device 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. The computer program is executed by being loaded into RAM and works with the CPU to form the control unit.
[0105] This computer program may also be stored in an application program server connected to the PC 100 via any network, and all or part of it may be downloaded as needed.
[0106] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program first 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.
[0107] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as 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 the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.
[0108] The various databases 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 used for various processes and providing websites.
[0109] The PC 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 PC 100 may be realized by installing software (including programs, data, etc.) that causes the PC 100 to perform the processes described in this embodiment.
[0110] 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]
[0111] The present invention is useful for credit management in industries that perform overdue credit management. [Explanation of symbols]
[0112] 100 PC 102 Control section 102a Reception 102b Processing section 104 Communication interface unit 106 Storage section 106a Master storage unit 106b Data storage unit 108 Input / Output Interface Section 200 servers 300 Network 400 Input Device 500 output devices
Claims
1. A debt management device having a control unit, The control unit a receiving means for receiving a specification of a default date and a specification of a contract; and a processing means for updating data for each contract specified in the reception means in accordance with a collection pattern defined in a preset master based on the contract and the forfeiture date specified in the reception means. A debt management device characterized by:
2. The processing means For each contract specified in the acceptance means, If it is determined that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which unaccrued interest after the default date is to be collected based on the preset master, all records having a scheduled collection date that falls on or after the default date specified in the reception means are deleted from the collection schedule data in which records including scheduled collection dates and scheduled collection interest are stored, and the total of the scheduled collection interest of the deleted records is set as the scheduled collection interest, and one record having the default date specified in the reception means as the scheduled collection date is newly stored in the collection schedule data, If it is determined that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which unaccrued interest after the default date should not be collected based on the preset master, all records having a scheduled collection date after the default date specified in the reception means are deleted from the collection schedule data, and of the scheduled interest to be collected in the deleted records, the scheduled interest to be collected up to the default date specified in the reception means is set as the scheduled interest to be collected, and one record having the default date specified in the reception means as the scheduled collection date is newly stored in the collection schedule data.
2. The claim management device according to claim 1.
3. The records stored in the collection schedule data and the newly stored records include the collection schedule principal amount in addition to the collection schedule date and the collection schedule interest amount, The amount of principal to be collected included in one record that is newly stored in the collection schedule data by the processing means is the sum of the amount of principal to be collected of the records to be deleted.
3. The claim management device according to claim 2.
4. The processing means For each contract specified in the acceptance means, If it is determined that the product corresponding to the contract designated by the receiving means is directly or indirectly specified as a product for which late payment charges should be waived when the benefit of the term expires, based on the preset master, the late payment charges when the benefit of the term expires are added as the waived late payment charges in the credit transaction data in which the waived late payment charges and the carried-over late payment charges are registered, If it is determined that the product corresponding to the contract designated by the reception means is directly or indirectly specified as a product for which late payment charges at the time of default should be carried forward based on the preset master, the late payment charges at the time of default should be added to the credit transaction data as the carried-forward late payment charges.
3. The claim management device according to claim 2.
5. The records stored in the debt transaction data and the newly stored records include debt identification information, waiver late payment charges, and carryover late payment charges by debt identification information and by transaction, The processing means For each contract specified in the acceptance means, If it is determined that the product corresponding to the contract specified in the reception means is directly or indirectly specified as a product for which late payment charges should be waived when the benefit of the term expires, based on the preset master, a new record containing claim identification information is stored in the claim transaction data, in which the waived late payment charges are set to the amount of late payment charges when the benefit of the term expires, the carried-over late payment charges are set to zero, and the claim identification information is set to the claim identification information corresponding to the contract specified in the reception means, If it is determined that the product corresponding to the contract designated in the reception means is directly or indirectly specified as a product for which late payment charges should be carried forward when the benefit of the term has expired, based on the preset master, the waived late payment charges are set to zero, the carried-forward late payment charges are set to the amount of late payment charges when the benefit of the term has expired, and one record is newly stored in the credit transaction data, with the credit identification information set to the credit identification information corresponding to the contract designated in the reception means.
5. The claim management device according to claim 4.
6. The processing means For each contract specified in the acceptance means, If it is determined that the product corresponding to the contract specified in the receiving means is directly or indirectly specified as a product for which the late payment damage interest rate in the credit data should be updated to the statutory interest rate based on the preset master, the late payment damage interest rate corresponding to the contract specified in the receiving means is updated to the statutory interest rate in the credit data in which the late payment damage interest rate is registered for each contract, If it is determined that the product corresponding to the contract designated by the reception means is directly or indirectly specified as a product for which the late damage interest rate in the credit data should not be updated to the statutory interest rate based on the preset master, the credit data is not updated but is maintained as is.
5. The claim management device according to claim 4.
7. The processing means For each collection pattern, a determination of the specification based on the master is made using a collection pattern master that stores records including collection pattern identification information distinguished by the presence or absence of a flag specifying that unaccrued interest after the date of default should be collected or a flag specifying that the unaccrued interest should not be collected, a flag specifying that late charges should be waived when the benefit of the term is lost or a flag specifying that the late charges should be carried forward, and a flag specifying that the late charge interest rate in the credit data should be updated to the statutory interest rate or a flag specifying that the late charge interest rate should not be updated to the statutory interest rate, and a product collection pattern linking master that specifies the relationship between the collection pattern identification information and the product.
7. The claim management device according to claim 6.
8. A claim management method executed in a claim management device having a control unit, Executed by the control unit, a receiving step for receiving a specification of a default date and a specification of a contract; and a processing step of updating data for each contract specified in the receiving step in accordance with a collection pattern defined in a preset master based on the contract and the forfeiture date specified in the receiving step. A method for managing receivables.
9. A claim management program to be executed by a claim management device having a control unit, The control unit a receiving step for receiving a specification of a default date and a specification of a contract; a processing step of updating data for each contract specified in the receiving step in accordance with a collection pattern defined in a preset master based on the contract and the forfeiture date specified in the receiving step; A debt management program to implement.
Citation Information
Patent Citations
Automatic determination device, automatic determination method, and automatic determination program
JP2023110721A