Device for calculating billing amount by estimated payment date, method for calculating billing amount by estimated payment date, and program for calculating billing amount by estimated payment date

Abstract

To provide a billing amount by payment scheduled date calculation device, billing amount by payment scheduled date calculation method and billing amount by payment scheduled date calculation program which can calculate a billing amount by a payment scheduled date.SOLUTION: A billing amount by payment scheduled date calculation device: (1) acquires a collection scheduled date and a collection scheduled amount associated with a designated credit number from collection schedule data including the credit number, the collection scheduled date and the collection scheduled amount; (2) acquires a delay loss interest rate associated with the designated credit number from contract data including the credit number and the delay loss interest rate; (3) acquires multiple payment scheduled dates with the designated base date as the reference; and (4) calculates a billing amount by the payment scheduled date by using the acquired collection scheduled amount, the acquired delay loss interest rate and the number of delayed days being the number of days from the acquired collection scheduled date to the acquired payment scheduled date.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to a device for calculating a claim amount by scheduled payment date, a method for calculating a claim amount by scheduled payment date, and a program for calculating a claim amount by scheduled payment date.

Background Art

[0002] Patent Document 1 discloses a technique that enables a taxpayer to view their own tax payment information and settle outstanding tax payments by appropriation on a network (see paragraph 0006 of Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, in industries that bill debtors for the amount of outstanding payments (for example, the financial services industry such as the banking industry, credit industry, and lending industry), the amount of late payment damages changes depending on the date on which the debtor makes a payment. This is because the late payment damages change depending on the number of days in arrears.

[0005] When notifying the debtor of the claim amount in a demand letter, conventionally, a specific date after the arrival of the demand letter (for example, 2 to 3 days after the mailing of the demand letter) was assumed as the scheduled payment date, and the demand letter was sent to the debtor.

[0006] However, this method has a problem that if the amount of payment is insufficient, the profit will be abandoned because the shortfall will be waived, and conversely, if the amount of payment is excessive, there will be an administrative burden because the excess amount will be returned to the debtor.

[0007] In addition, when providing a claim amount guidance in response to an inquiry from a debtor, conventionally, since an operator in a financial institution calculated the claim amount by deposit scheduled date, there has been a problem of a heavy administrative burden.

[0008] In order to solve the above problems, a method capable of calculating the claim amount by deposit scheduled date at one time is required. If the claim amounts on multiple deposit scheduled dates can be calculated at one time, for a demand notice, the claim amounts on multiple deposit scheduled dates can be listed, and for an inquiry from a debtor, the claim amounts on multiple deposit scheduled dates can be queried in a list.

[0009] The present invention has been made in view of the above problems, and an object thereof is to provide a claim amount calculation device by deposit scheduled date, a claim amount calculation method by deposit scheduled date, and a claim amount calculation program by deposit scheduled date, which can calculate the claim amount by deposit scheduled date.

Means for Solving the Problems

[0010] In order to solve the above-described problems and achieve the object, a claim amount calculation device by deposit scheduled date according to the present invention is a claim amount calculation device by deposit scheduled date including a control unit and a storage unit capable of calculating a claim amount by deposit scheduled date, wherein the storage unit stores recovery schedule data including claim identification data for identifying a claim, a recovery scheduled date which is a scheduled date for recovering the claim, and a recovery scheduled amount which is an amount of the claim to be recovered, claim identification data, and a delay damage interest rate, and the control unit includes a recovery information acquisition means for acquiring a recovery scheduled date and a recovery scheduled amount associated with the specified claim identification data from the recovery schedule data, a delay damage interest rate acquisition means for acquiring a delay damage interest rate associated with the specified claim identification data from the contract data, a deposit scheduled date acquisition means for acquiring a plurality of deposit scheduled dates based on a specified reference date, and a claim amount calculation means for calculating a claim amount by deposit scheduled date using the acquired recovery scheduled amount, the acquired delay damage interest rate, and a number of days in arrears which is a number of days from the acquired recovery scheduled date to the acquired deposit scheduled date.

[0011] Further, the billing amount calculation device according to the present invention is such that the specified claim identification data and the specified reference date are specified on a reminder instruction screen which is a screen for instructing the creation of reminder data including the billing amount by payment due date, the payment due date acquisition means acquires, as the payment due date, a predetermined number of days from the specified reference date, and the control unit further includes reminder data generation means for generating the reminder data including the billing amount by payment due date calculated by the billing amount calculation means.

[0012] Further, the billing amount calculation device according to the present invention is characterized in that the control unit further includes reminder form output means for outputting a reminder form on which the content of the reminder data is printed.

[0013] In addition, the billing amount calculation device according to the present invention further stores, in the storage unit, display method identification data for identifying a display method of the payment due date on an inquiry screen where the billing amount by payment due date can be inquired, and the number of display items of the payment due date on the inquiry screen. A billing amount inquiry control master is stored. The specified claim identification data and the specified reference date are those specified on the inquiry screen. When the display method identification data in the billing amount inquiry control master means that the payment due date after the specified reference date is to be displayed, the payment due date acquisition means acquires, as the payment due date, the same number of days as the number of display items in the billing amount inquiry control master from the specified reference date. On the other hand, when the display method identification data in the billing amount inquiry control master means that the payment due date before and after the specified reference date is to be displayed, the specified reference date, the same number of days as the number of display items in the billing amount inquiry control master immediately before the specified reference date, and the same number of days as the number of display items in the billing amount inquiry control master immediately after the specified reference date are acquired as the payment due date. The control unit further includes an inquiry screen display means for displaying the inquiry screen including the billing amount by payment due date calculated by the billing amount calculation means. This is the feature.

[0014] In addition, the billing amount calculation device according to the present invention is characterized in that the person operating the inquiry screen is a person in charge in a financial institution who has received an inquiry from a debtor.

[0015] In addition, the method for calculating the claim amount by scheduled payment date according to the present invention is a method for calculating the claim amount by scheduled payment date that can be executed by an information processing apparatus including a control unit and a storage unit. The storage unit stores recovery schedule data including claim identification data for identifying a claim, a recovery scheduled date that is the scheduled date for recovering the claim, and a recovery scheduled amount that is the amount of the claim to be recovered, contract data including claim identification data and a late damage interest rate, and the control unit executes a recovery information acquisition step of acquiring the recovery scheduled date and the recovery scheduled amount associated with the specified claim identification data from the recovery schedule data, a late damage interest rate acquisition step of acquiring the late damage interest rate associated with the specified claim identification data from the contract data, a scheduled payment date acquisition step of acquiring a plurality of scheduled payment dates based on a specified reference date, and a claim amount calculation step of calculating the claim amount by scheduled payment date using the acquired recovery scheduled amount, the acquired late damage interest rate, and the number of days in arrears, which is the number of days from the acquired recovery scheduled date to the acquired scheduled payment date. This is the gist of the invention.

[0016] In addition, the billing amount calculation program by deposit scheduled date according to the present invention is a billing amount calculation program by deposit scheduled date that can calculate the billing amount by deposit scheduled date for execution on an information processing apparatus including a control unit and a storage unit. In the storage unit, there is stored recovery schedule data including claim identification data for identifying a claim, a recovery scheduled date which is a scheduled date for recovering the claim, and a recovery scheduled amount which is the amount of the claim to be recovered, contract data including claim identification data and a late payment damage interest rate, and the control unit is caused to execute a recovery information acquisition step of acquiring the recovery scheduled date and the recovery scheduled amount associated with the specified claim identification data from the recovery schedule data, a late payment damage interest rate acquisition step of acquiring the late payment damage interest rate associated with the specified claim identification data from the contract data, a deposit scheduled date acquisition step of acquiring a plurality of deposit scheduled dates based on a specified reference date, and a billing amount calculation step of calculating the billing amount by deposit scheduled date using the acquired recovery scheduled amount, the acquired late payment damage interest rate, and the number of days in arrears which is the number of days from the acquired recovery scheduled date to the acquired deposit scheduled date.

Effect of the Invention

[0017] According to the present invention, there is an effect that the billing amount by deposit scheduled date can be calculated.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

[0019] Embodiments of a billing amount calculation device, a billing amount calculation method, and a billing amount calculation program according to the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited by this embodiment.

[0020] [1. Overview] In the financial industry (banking industry, credit industry, lending industry, etc.), there were the following two problems regarding the guidance of the amount to be billed to debtors.

[0021] The first problem was related to the guidance of the amount to be billed in a demand notice. Since the number of days in arrears changes depending on the payment date, the amount of late payment damages to be billed also changes depending on the payment date. Therefore, conventionally, a specific date after the arrival of the demand notice (for example, 2 to 3 days after the mailing of the demand notice) was assumed as the payment date, the amount of late payment damages was tentatively determined, and the guidance was provided in the demand notice.

[0022] And when the payment amount was insufficient, the shortfall was waived, and conversely, when the payment amount was excessive, the excess was returned. However, in the former case, there was a problem that the profit of the late payment damages for the shortfall was waived, and in the latter case, there was a problem that an administrative burden was incurred due to the return of the excess.

[0023] In other words, conventionally, in the collection business, the amount to be billed was guided only at one date point, so when the payment was made on a date other than the assumed payment date, an over / under amount occurred and an administrative burden was imposed.

[0024] As a second problem, there was a problem regarding the guidance of the claim amount when inquiring from the debtor. As described above, since the number of days in arrears changes depending on the deposit date, the amount of liquidated damages to be claimed also changes depending on the deposit date. For this reason, conventionally, the claim amount has been inquired for each debtor's scheduled deposit date, but there has been a problem that the inquiry cannot be smoothly made in response to an inquiry, and there is also an administrative burden associated with the inquiry.

[0025] In other words, conventionally, in the inquiry operation, the claim amount was inquired only at one date point each time, so when guiding the claim amount to the debtor on multiple scheduled deposit dates, the number of operation steps increased, resulting in inefficiency.

[0026] Therefore, in the present embodiment, when dealing with overdue claims, the claim amounts on multiple deposit dates can be output at once. As a result, it is possible to eliminate the problems of administrative burden and loss. Specifically, the following two effects are achieved.

[0027] As a first effect, by the debtor making a deposit after grasping the appropriate claim amount according to the deposit date, it is possible to eliminate the excess or deficiency of the deposit amount. As a result, it is possible to eliminate the administrative burden associated with the waiver of the profit of the liquidated damages for the shortage and the return of the excess.

[0028] As a second effect, even when there are multiple scheduled deposit dates, it is possible to efficiently guide the claim amount.

[0029] Here, in the present embodiment, as a method for guiding the claim amount for each scheduled deposit date, for example, the following four methods are assumed.

[0030] The first is guidance by a demand letter. In this guidance, a demand letter is output for claims for which account transfer is not possible. Within the layout of the demand letter, the claim amounts for 10 days after the specified claim date are output.

[0031] The second is the guidance by inquiry of the claim amount. In this guidance, the person in charge at a financial institution who has received a telephone inquiry from the debtor conducts an inquiry of the claim amount. A list of the inquiry results of the claim amount shows the claim amounts for 10 days after the specified deposit date (the initial display is the specified date).

[0032] The third is the guidance by inquiry on the member site (website). In this guidance, a URL embedded with the claim No. is distributed to the debtor by a reminder email or the like, and the debtor himself / herself can immediately inquire on the my page of the member site (website). The claim amounts for 10 days after the specified deposit date are displayed (the initial display is the specified date).

[0033] The fourth is the guidance by reminder contact using email. In this guidance, the content of the reminder notice is sent by email. The claim amounts for 10 days after the specified claim date are displayed.

[0034] The following describes the specific configuration and operation.

[0035] [2. Configuration] An example of the configuration of the claim amount calculation device 100 by deposit scheduled date according to this embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram showing an example of the configuration of the claim amount calculation device 100 by deposit scheduled date.

[0036] The claim amount calculation device 100 by deposit scheduled date is a commercially available desktop personal computer. Note that the claim amount calculation device 100 by deposit scheduled date is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.

[0037] The billing amount calculation device 100 by scheduled deposit date includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the billing amount calculation device 100 by scheduled deposit date is communicably connected via an arbitrary communication path.

[0038] The communication interface unit 104 communicably connects the billing amount calculation device 100 by scheduled deposit date 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 communicably connecting the billing amount calculation device 100 by scheduled deposit date and the server 200 to each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described later may be stored in the server 200, for example.

[0039] An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Hereinafter, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

[0040] Various databases, tables, files, etc. are stored in the storage unit 106. A computer program for giving commands to the CPU (Central Processing Unit) to perform various processes in cooperation with the OS (Operating System) is recorded in the storage unit 106. As the storage unit 106, 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, and an optical disk can be used.

[0041] The memory unit 106 includes, for example, collection schedule data 106a, collection result data 106b, contract data 106c, claim amount inquiry control master 106d, and reminder data 106e. The correlation between the respective data is as shown in FIG. 4.

[0042] The collection schedule data 106a is data for managing the collection schedule from the debtor. As shown in FIG. 2, the collection schedule data 106a includes, for example, claim identification data (claim number) for identifying a claim, collection schedule identification data (collection SEQ) for identifying the collection schedule, the scheduled month and year for collecting the claim, the scheduled date for collecting the claim, the scheduled collection amount of the claim, the principal amount in the scheduled collection amount, the interest in the scheduled collection amount, the fee in the scheduled collection amount, a completion flag which is a flag for identifying whether the collection of the claim has been completed, and the like.

[0043] The completion flag is a flag indicating that the collection of the claim has been completed (flag of "1") or a flag indicating that the collection of the claim has not been completed (flag of "0"). In the example of the collection schedule data 106a in FIG. 2, since the completion flag is "1" for the records with collection SEQ = 1 to 3, all the scheduled collection amounts in the records with collection SEQ = 1 to 3 have been collected.

[0044] The collection result data 106b is data for managing the actual results of collection against the collection schedule. As shown in FIG. 2, the collection result data 106b includes, for example, the claim identification data (claim number), the collection schedule identification data (collection SEQ), the collection date which is the date when the claim was collected, the collection amount which is the amount of the claim collected, the principal amount in the collection amount, the interest in the collection amount, the fee in the collection amount, and the like.

[0045] The contract data 106c is data for managing the contract content. As shown in FIG. 3, the contract data 106c includes, for example, the claim identification data (claim number), the financing interest rate, the late payment damage interest rate, and the like.

[0046] The claim inquiry control master 106d is a master that manages the settings for displaying claim inquiries for each process. As shown in FIG. 3, the claim inquiry control master 106d includes, for example, process identification data (process ID) for identifying a process for inquiring about a claim amount, display method identification data (display method code) for identifying the display method of the scheduled payment date on an inquiry screen where the claim amount can be inquired by scheduled payment date, the number of display items of the scheduled payment date on the inquiry screen, a display method changeable flag that is a flag for identifying whether the operator operating the inquiry screen can change the display method or not, a display item changeable flag that is a flag for identifying whether the operator operating the inquiry screen can change the number of display items or not, and the like. The claim inquiry control master 106d can be set, for example, by an administrator or an officer in a financial institution.

[0047] As shown in FIG. 3, examples of the process identification data (process ID) include, for example, something that means a debt inquiry performed by a person in charge in a financial institution who has received an inquiry from a debtor (ID of "1: Claim Inquiry"), or something that means a debt inquiry performed by the debtor himself / herself on a member site or the like (ID of "2: WEB Member Inquiry").

[0048] As shown in FIG. 3, the display method identification data (display method code) means something that displays the scheduled payment date after the specified reference date (code of "1: Display the number of display items after the specified date"), or something that displays the scheduled payment date before and after the specified reference date (code of "2: Display the number of display items before and after the specified date respectively").

[0049] As shown in FIG. 3, the display method changeable flag is a flag that means a setting in which the operator operating the inquiry screen can change the display method ("true" flag), or a flag that means a setting in which the operator operating the inquiry screen cannot change the display method ("false" flag).

[0050] As shown in FIG. 3, the display number changeable flag is a flag (a "true" flag) meaning a setting in which an operator who operates the inquiry screen can change the display number, or a flag (a "false" flag) meaning a setting in which the operator who operates the inquiry screen cannot change the display number.

[0051] The reminder data 106e is data including the claimed amount by the calculated payment due date.

[0052] The control unit 102 is a CPU or the like that comprehensively controls the payment due date claimed amount calculation device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, etc., and executes various information processes based on these stored programs.

[0053] Conceptually in terms of functions, the control unit 102 includes, for example: (1) a collection information acquisition unit 102a as collection information acquisition means for acquiring a collection due date and a collection amount associated with specified claim identification data from the collection schedule data; (2) a late damage interest rate acquisition unit 102b as late damage interest rate acquisition means for acquiring a late damage interest rate associated with the specified claim identification data from the contract data; (3) a payment due date acquisition unit 102c as payment due date acquisition means for acquiring a plurality of payment due dates based on a specified reference date; (4) a claimed amount calculation unit 102d as claimed amount calculation means for calculating the claimed amount by payment due date using the acquired collection amount, the acquired late damage interest rate, and the number of days in arrears which is the number of days from the acquired collection due date to the acquired payment due date; (5) a reminder data generation unit 102e as reminder data generation means for generating the reminder data including the claimed amount by payment due date calculated by the claimed amount calculation means; (6) a reminder form output unit 102f as reminder form output means for outputting a reminder form on which the content of the reminder data is printed; and (7) an inquiry screen display unit 102g as inquiry screen display means for displaying the inquiry screen including the claimed amount by payment due date calculated by the claimed amount calculation means.

[0054] The collection information acquisition unit 102a acquires the scheduled collection date and the scheduled collection amount associated with the specified claim number from the scheduled collection data 106a (see FIG. 2).

[0055] The late damage interest rate acquisition unit 102b acquires the late damage interest rate associated with the specified claim number from the contract data 106c (see FIG. 3).

[0056] The scheduled deposit date acquisition unit 102c acquires a plurality of scheduled deposit dates based on the specified reference date.

[0057] When the specified claim number and the specified reference date are specified on a reminder instruction screen (see the output instruction screen shown in FIG. 5) for instructing the creation of reminder data 106e including the claim amount by scheduled deposit date, the scheduled deposit date acquisition unit 102c acquires the number of days corresponding to a predetermined number of days from the specified reference date as the scheduled deposit date. For example, if the specified reference date is "2023 / 5 / 30" and the predetermined number of days is "10", the scheduled deposit date acquisition unit 102c acquires "2023 / 5 / 30 to 2023 / 6 / 8" as the scheduled deposit date.

[0058] When the specified claim number and the specified reference date are specified on an inquiry screen (see the inquiry screens in FIGS. 7 and 8) where the claim amount by scheduled deposit date can be inquired, the scheduled deposit date acquisition unit 102c acquires the scheduled deposit date as follows. Note that the person operating the inquiry screen is, for example, a person in charge at a financial institution who has received an inquiry from a debtor.

[0059] That is, when the display method code (initial value) in the claim amount inquiry control master 106d is "1: Display the number of display items after the specified date", the expected payment date acquisition unit 102c acquires, from the specified reference date, the same number of days as the number of display items in the claim amount inquiry control master 106d as the expected payment date. For example, if the specified reference date is "May 30, 2023" and the number of display items is "10", the expected payment date acquisition unit 102c acquires "May 30, 2023 to June 8, 2023" as the expected payment date.

[0060] On the other hand, when the display method code (initial value) in the claim amount inquiry control master 106d is "2: Display the number of display items before and after the specified date respectively", the expected payment date acquisition unit 102c acquires the specified reference date, the same number of days as the number of display items in the claim amount inquiry control master 106d immediately before the specified reference date, and the same number of days as the number of display items in the claim amount inquiry control master 106d immediately after the specified reference date as the expected payment date. For example, if the specified reference date is "June 2, 2023" and the number of display items is "3", the expected payment date acquisition unit 102c acquires "June 2, 2023", "May 30, 2023 to June 1, 2023", and "June 3, 2023 to June 5, 2023" as the expected payment date.

[0061] The claim amount calculation unit 102d calculates the claim amount for each expected payment date using the acquired expected recovery amount, the acquired late payment damage interest rate, and the number of days in arrears, which is the number of days from the acquired expected recovery date to the acquired expected payment date.

[0062] Specifically, the claim amount calculation unit 102d can calculate the claim amount for each expected payment date by adding the late payment damage to the expected recovery amount. The late payment damage can be calculated, for example, by the formula "expected recovery amount × late payment damage interest rate × number of days in arrears ÷ number of days in a year". However, this formula is not limited.

[0063] The reminder data generation unit 102e generates reminder data 106e including the amount to be billed by payment due date calculated by the amount to be billed calculation unit 102d.

[0064] The reminder notice output unit 102f outputs a reminder notice (see FIG. 6) on which the content of the reminder data 106e is printed.

[0065] The inquiry screen display unit 102g displays an inquiry screen (see the inquiry screens in FIGS. 7 and 8) including the amount to be billed by payment due date calculated by the amount to be billed calculation unit 102d.

[0066] [3. Specific Example of Processing] In this section, a specific example of the processing according to the present embodiment will be described. In [3-1], the generation of a reminder notice will be described, and in [3-2], the inquiry of the amount to be billed will be described. The generation of a reminder notice and the inquiry of the amount to be billed are assumed to be performed by a person in charge (hereinafter sometimes simply referred to as the "person in charge") in a financial institution.

[0067] Note that in this section [3. Specific Example of Processing], it is assumed that the collection schedule data 106a has the content shown in FIG. 2, the contract data 106c and the amount to be billed inquiry control master 106d have the content shown in FIG. 3, and they are set in advance.

[0068] [3-1. Generation of Reminder Notice] First, information necessary for generating a reminder notice is input by the person in charge from the output instruction screen shown in FIG. 5. Specifically, as the billing date, the date when the reminder notice is expected to reach the debtor (= notification date) is input. In the example of FIG. 5, "2023 / 5 / 30" is input as the billing date. Also, in the <Range Specification> section, the person in charge of the reminder, the claim No., the number of overdue months, etc. are input. In the example of FIG. 5, "1000~1001" is input as the claim No. When the information input from <Range Specification> is completed, as shown in the lower part of FIG. 5, a list of claims to be output is displayed in combination with the claim No. and the customer name.

[0069] After the necessary information is input on the output instruction screen shown in FIG. 5 and the output button is pressed, a reminder is generated as follows.

[0070] First, the collection information acquisition unit 102a acquires, from the collection schedule data 106a in FIG. 2, the record with the collection SEQ = 4 as a record that has the specified claim No. "1000", has a collection schedule date before the specified claim date "2023 / 5 / 30", and has "0 (collection not completed)" as the completion flag. Then, the collection information acquisition unit 102a acquires the collection schedule date "2023 / 5 / 26" and the collection schedule amount "10,000 yen" in the acquired record with the collection SEQ = 4.

[0071] More specifically, the collection information acquisition unit 102a may calculate and acquire the collection schedule amount, principal amount, interest, and fee by subtracting the amounts in the records in the collection performance data 106b having the claim number and collection SEQ in the record from the amounts in each record in the records that satisfy all of the following conditions (i) to (iii) in the collection schedule data 106a. Assuming that the conditions described in the previous paragraph are specified, the collection information acquisition unit 102a will acquire a collection schedule amount of 10,000 yen, a principal amount of 7,000 yen, interest of 3,000 yen, and a fee of 0 yen. (Condition) (i) It has the specified claim number. (ii) The collection schedule date in the collection schedule data 106a ≤ the specified claim date (deposit date). (iii) The completion flag in the collection schedule data 106a = 0 (collection not completed).

[0072] Next, the late damage rate acquisition unit 102b acquires "0.14600" as the late damage rate associated with the specified claim No. "1000" from the contract data 106c in FIG. 3.

[0073] Next, the deposit schedule date acquisition unit 102c acquires, as the deposit schedule date, 10 days (2023 / 5 / 30 to 2023 / 6 / 8) from the specified claim date "2023 / 5 / 30".

[0074] Next, the claim amount calculation unit 102d calculates the claim amount by deposit date by adding the late payment damages to the obtained planned collection amount of "10,000 yen". The claim amount calculation unit 102d calculates the late payment damages by deposit date according to the calculation formula of "(the obtained planned collection amount of 10,000 yen) × (the obtained late payment damages interest rate of 0.14600) × (the number of days in arrears from the obtained planned collection date of May 26, 2023 to the obtained planned deposit date from May 30, 2023 to June 8, 2023) ÷ (365 days in a year)". Specifically, the calculation formula is as follows. ·May 30: 10,000 × 0.14600 × 4 ÷ 365 = 16 yen ·May 31: 10,000 × 0.14600 × 5 ÷ 365 = 20 yen ·June 1: 10,000 × 0.14600 × 6 ÷ 365 = 24 yen ·June 2: 10,000 × 0.14600 × 7 ÷ 365 = 28 yen ·June 3: 10,000 × 0.14600 × 8 ÷ 365 = 32 yen ·June 4: 10,000 × 0.14600 × 9 ÷ 365 = 36 yen ·June 5: 10,000 × 0.14600 × 10 ÷ 365 = 40 yen ·June 6: 10,000 × 0.14600 × 11 ÷ 365 = 44 yen ·June 7: 10,000 × 0.14600 × 12 ÷ 365 = 48 yen ·June 8: 10,000 × 0.14600 × 13 ÷ 365 = 52 yen

[0075] Next, the reminder data generation unit 102e generates reminder data 106e including the claim amount by deposit date calculated by the claim amount calculation unit 102d.

[0076] Finally, the reminder notice output unit 102f outputs the reminder notice shown in FIG. 6 on which the content of the reminder data 106e (= the claim amount by deposit date) is printed. In the reminder notice shown in FIG. 6, "May 29, 2023" in the upper right indicates the output date (processing date).

[0077] As described above in this item [3-1], according to the billing amount calculation device 100 according to the present embodiment, the debtor can check a list of the billing amounts by payment due date and pay an appropriate amount by referring to the reminder notice on which the billing amounts by payment due date are printed. As a result, the shortage of payments is eliminated, so that the waiver of the financial institution's profits can be prevented, and since there is no excessive payment, the administrative burden on the financial institution associated with the return work of the excessive payment can be reduced.

[0078] [3-2. Inquiry of Billing Amount] First, the necessary information is input by the person in charge from the inquiry screen for performing the creditor's rights inquiry. FIG. 7 shows an example of the inquiry screen when "display after specified date" is selected as the display method. FIG. 8 shows an example of the inquiry screen when "display around specified date" is selected as the display method.

[0079] In the example of FIG. 7, "1000" is input as the creditor's rights No., and in the <billing amount inquiry> section, "display after specified date" is specified as the display method, "10" is specified as the number of displayed items, and "2023 / 5 / 30" is input as the payment date.

[0080] In the example of FIG. 8, "1000" is input as the creditor's rights No., and in the <billing amount inquiry> section, "display around specified date" is specified as the display method, "3" is specified as the number of displayed items, and "2023 / 6 / 2" is input as the payment date.

[0081] When the input of these information is completed, as shown in the lower part of FIGS. 7 and 8, a list of the inquiry results is displayed in a combination of the payment date, day of the week, number of days in arrears, billing amount, principal amount, interest, and liquidated damages.

[0082] Here, the display control of the inquiry screen based on the settings of the billing amount inquiry control master 106d in FIG. 3 will be described.

[0083] The initial value of the display method is displayed by setting the display method code (initial value) in the claim inquiry control master 106d. Specifically, when the display method code (initial value) is set to "1: Display the number of display items after the specified date", as shown in the inquiry screen of FIG. 7, the item "Display after the specified date" = ON (checked state) is displayed as the initial value. On the other hand, when the display method code (initial value) is set to "2: Display the number of display items before and after the specified date respectively", as shown in the inquiry screen of FIG. 8, the item "Display before and after the specified date" = ON (checked state) is displayed as the initial value.

[0084] In addition, input control of "Display after the specified date" or "Display before and after the specified date" can also be performed by setting the display method changeable flag in the claim inquiry control master 106d. Specifically, when the display method changeable flag is set to "true", "Display after the specified date" or "Display before and after the specified date" can be changed from the initial value. On the other hand, when the display method changeable flag is set to "false", "Display after the specified date" or "Display before and after the specified date" cannot be changed from the initial value (the item itself of "Display after the specified date" or "Display before and after the specified date" may be hidden).

[0085] The initial value of the number of display items is displayed by setting the number of display items (initial value) in the claim inquiry control master 106d. In addition, input control of the number of display items can also be performed by setting the number of display items changeable flag in the claim inquiry control master 106d. Specifically, when the number of display items changeable flag is set to "true", the number of display items can be changed from the initial value. On the other hand, when the number of display items changeable flag is set to "false", the number of display items cannot be changed from the initial value (the item itself of the number of display items may be hidden).

[0086] When the input of the necessary information is completed on the inquiry screens shown in FIGS. 7 and 8, the result of the claim inquiry is displayed as follows.

[0087] First, the collection information acquisition unit 102a acquires the record with collection SEQ = 4 from the collection schedule data 106a in Fig. 2 in the same manner as [3-1], and acquires the scheduled collection date "2023 / 5 / 26" and the scheduled collection amount "10,000 yen" in the acquired record with collection SEQ = 4.

[0088] Next, the late damage interest rate acquisition unit 102b acquires "0.14600" as the late damage interest rate associated with the specified claim No. "1000" from the contract data 106c in Fig. 3 in the same manner as [3-1].

[0089] Next, the scheduled deposit date acquisition unit 102c acquires a plurality of scheduled deposit dates based on the specified deposit date. Since the acquisition method differs depending on the specified display method ("display after the specified date" or "display around the specified date"), the following cases will be explained separately.

[0090] When the specified display method is "display after the specified date" (i.e., in the case of the example in Fig. 7), the scheduled deposit date acquisition unit 102c acquires 10 days (2023 / 5 / 30 to 2023 / 6 / 8), which is the same number of days as the specified display count "10", from the specified deposit date "2023 / 5 / 30" as the scheduled deposit dates.

[0091] On the other hand, when the specified display method is "display around the specified date" (i.e., in the case of the example in Fig. 8), the scheduled deposit date acquisition unit 102c acquires 3 days (2023 / 5 / 30 to 2023 / 6 / 1), which is the same number of days as the specified display count "3" immediately before the specified deposit date "2023 / 6 / 2", and 3 days (2023 / 6 / 3 to 2023 / 6 / 5), which is the same number of days as the specified display count "3" immediately after the specified deposit date, as the scheduled deposit dates.

[0092] Next, the claim amount calculation unit 102d calculates the claim amount for each scheduled deposit date by adding the late damage to the acquired scheduled collection amount "10,000 yen" in the same manner as [3-1]. Since the method of calculating the claim amount is the same as that in [3-1], detailed explanation is omitted.

[0093] Finally, the inquiry screen display unit 102g displays the inquiry screens of FIGS. 7 and 8, including the amount to be billed by deposit scheduled date calculated by the amount to be billed calculation unit 102d.

[0094] As described above in this item [3-2], according to the amount to be billed calculation device 100 by deposit scheduled date according to the present embodiment, even when the person in charge is inquired about the amount to be billed for a plurality of deposit scheduled dates from the debtor, the person in charge can efficiently respond by inquiring about the inquiry screen on which the amount to be billed by deposit scheduled date is displayed.

[0095] Also, according to the amount to be billed calculation device 100 by deposit scheduled date according to the present embodiment, the display method can be set according to the operation of the user (inquiry business) and the requests of the debtor due to the product characteristics. Thereby, the person in charge can, for example, assume the date when the debtor's repayment funds can be prepared and confirm the amount to be billed before and after that date.

[0096] In addition, in this item [3-2], the inquiry screen in the case where the person in charge at a financial institution makes a claim inquiry has been described, but the inquiry screen in the case where the debtor himself / herself makes a debt inquiry on the membership site (WEB site) may have a similar screen configuration.

[0097] [4. Contribution to the Sustainable Development Goals (SDGs) Led by the United Nations] According to the present embodiment, since it can contribute to promoting business efficiency and appropriate business judgment of the enterprise, it becomes possible to contribute to Goals 8 and 9 of the SDGs.

[0098] Also, according to the present embodiment, since it can contribute to reducing waste loss and promoting paperless and digitization, it becomes possible to contribute to Goals 12, 13 and 15 of the SDGs.

[0099] Also, according to the present embodiment, since it can contribute to strengthening control and governance, it becomes possible to contribute to Goal 16 of the SDGs.

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

[0101] For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.

[0102] Also, regarding 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 the drawings, they can be arbitrarily changed unless otherwise specified.

[0103] Regarding the billing amount calculation device 100 by deposit scheduled date, each illustrated component is a functional concept and does not necessarily need to be physically configured as shown.

[0104] For example, regarding the processing functions provided by the billing amount calculation device 100 by deposit scheduled date, particularly each processing function performed by the control unit, all or any part of them may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing an information processing device to execute the processes described in this embodiment, and is mechanically read by the billing amount calculation device 100 by deposit scheduled date as needed. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM and constitutes the control unit in cooperation with the CPU.

[0105] Further, this computer program may be stored in an application program server connected to the payment schedule-based billing amount calculation device 100 via an arbitrary network, and it is also possible to download all or part of it as needed.

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

[0107] Also, the "program" is a data processing method described in any language or description method, regardless of the form such as source code or binary code. Note that the "program" is not necessarily limited to being configured singularly, and also includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with another program typified by an OS. Note that for the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in the embodiment, well-known configurations and procedures can be used.

[0108] The various databases and the like stored in the memory unit are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0109] Also, the billing amount calculation device 100 by deposit scheduled date 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 an arbitrary peripheral device is connected. Further, the billing amount calculation device 100 by deposit scheduled date may be realized by installing software (including programs or data, etc.) for realizing the processes described in this embodiment in the device.

[0110] Furthermore, the specific form of the distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the function load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0111] The present invention is useful in the industry handling financial claims, and is extremely useful particularly in financial institutions, non-banks, banks, credit traders, and money lenders.

Explanation of Signs

[0112] 100 Billing amount calculation device by deposit scheduled date 102 Control unit 102a Collection information acquisition unit 102b Delayed damage interest rate acquisition unit 102c Deposit scheduled date acquisition unit 102d Billing amount calculation unit 102e Reminder data generation unit 102f Reminder output unit 102g Inquiry screen display unit 104 Communication Interface Unit 106 Memory Unit 106a Scheduled Recovery Data 106b Actual Recovery Data 106c Contract Data 106d Invoice Inquiry Control Master 106e Reminder Data 108 Input / Output Interface Unit 112 Input Device 114 Output Device 200 Server 300 Network

Claims

1. A claim amount calculation device by due date of payment, comprising a control unit and a storage unit, capable of calculating a claim amount by due date of payment, wherein the storage unit stores recovery schedule data including claim identification data for identifying a claim, a recovery schedule date which is a scheduled date for recovering the claim, and a recovery schedule amount which is the amount of the claim to be recovered, contract data including claim identification data and a late damage interest rate, and the control unit includes a recovery information acquisition means for acquiring a recovery schedule date and a recovery schedule amount associated with the specified claim identification data from the recovery schedule data, a late damage interest rate acquisition means for acquiring a late damage interest rate associated with the specified claim identification data from the contract data, a due date of payment acquisition means for acquiring a plurality of due dates of payment based on a specified reference date, and a claim amount calculation means for calculating a claim amount by due date of payment using the acquired recovery schedule amount, the acquired late damage interest rate, and the number of days in arrears which is the number of days from the acquired recovery schedule date to the acquired due date of payment, characterized in that it comprises the above, and is a claim amount calculation device by due date of payment.

2. The specified claim identification data and the specified reference date are specified on a reminder instruction screen which is a screen for instructing the creation of reminder data including the claim amount by due date of payment, the due date of payment acquisition means acquires, as the due date of payment, a predetermined number of days from the specified reference date, and the control unit further includes a reminder data generation means for generating the reminder data including the claim amount by due date of payment calculated by the claim amount calculation means, characterized in that it comprises the above, and is the claim amount calculation device by due date of payment according to Claim 1.

3. The control unit further includes a reminder notice output means for outputting a reminder notice on which the content of the reminder data is printed, characterized in that it comprises the above, and is the claim amount calculation device by due date of payment according to Claim 2.

4. The storage unit further stores a claim inquiry control master in which display method identification data for identifying a display method of the due date of payment on an inquiry screen where the claim amount by due date of payment can be inquired and the number of display times of the due date of payment on the inquiry screen are set, and the specified claim identification data and the specified reference date are specified on the inquiry screen. ​ ​ When the deposit scheduled date acquisition means means that the display method identification data in the claim amount inquiry control master indicates the deposit scheduled date after the specified reference date, the deposit scheduled date is acquired as the same number of days as the display count in the claim amount inquiry control master from the specified reference date. On the other hand, when the display method identification data in the claim amount inquiry control master means that it indicates the deposit scheduled date before and after the specified reference date, the specified reference date, the same number of days as the display count in the claim amount inquiry control master immediately before the specified reference date, and the same number of days as the display count in the claim amount inquiry control master immediately after the specified reference date are acquired as the deposit scheduled date. The control unit A query screen display means for displaying the query screen including the claim amount by deposit scheduled date calculated by the claim amount calculation means further comprises The claim amount calculation device according to claim 1, characterized in that

5. The person who operates the query screen is a person in charge in a financial institution who has received an inquiry from a debtor. The claim amount calculation device according to claim 4, characterized in that

6. A claim amount calculation method for calculating the claim amount by deposit scheduled date, which is executed by an information processing device including a control unit and a storage unit, In the storage unit, Recovery schedule data including claim identification data for identifying a claim, a recovery scheduled date which is the scheduled date for recovering the claim, and a recovery scheduled amount which is the amount of the claim to be recovered, Contract data including claim identification data and a late payment damage rate, are stored, Executed by the control unit, A recovery information acquisition step of acquiring the recovery scheduled date and the recovery scheduled amount associated with the specified claim identification data from the recovery schedule data, A late payment damage rate acquisition step of acquiring the late payment damage rate associated with the specified claim identification data from the contract data, A deposit scheduled date acquisition step of acquiring a plurality of deposit scheduled dates based on a specified reference date, A claim amount calculation step of calculating the claim amount by deposit scheduled date using the acquired recovery scheduled amount, the acquired late payment damage rate, and the number of days in arrears which is the number of days from the acquired recovery scheduled date to the acquired deposit scheduled date, including The claim amount calculation method characterized by

7. A program for calculating the claim amount by scheduled payment date, which can be executed by an information processing apparatus including a control unit and a storage unit, wherein the storage unit stores recovery schedule data including claim identification data for identifying a claim, a recovery scheduled date which is the scheduled date for recovering the claim, and a recovery scheduled amount which is the amount of the claim to be recovered, contract data including claim identification data and a late damage interest rate, and a recovery information acquisition step for acquiring, from the recovery schedule data, a recovery scheduled date and a recovery scheduled amount associated with the specified claim identification data, for execution by the control unit; a late damage interest rate acquisition step for acquiring, from the contract data, a late damage interest rate associated with the specified claim identification data; a scheduled payment date acquisition step for acquiring a plurality of scheduled payment dates based on a specified reference date; a claim amount calculation step for calculating the claim amount by scheduled payment date using the acquired recovery scheduled amount, the acquired late damage interest rate, and the number of days in arrears which is the number of days from the acquired recovery scheduled date to the acquired scheduled payment date; and characterized by including a program for calculating the claim amount by scheduled payment date.

Images