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

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 billing amount by estimated payment date, a method for calculating a billing amount by estimated payment date, and a program for calculating a billing amount by estimated payment date. [Background technology]

[0002] Patent Document 1 discloses a technology that enables taxpayers to view their own tax payment information and settle outstanding taxes through appropriation over a network (see paragraph 0006 of Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-282435 Summary of the Invention [Problem to be solved by the invention]

[0004] In industries that bill debtors for unpaid amounts (for example, financial industries such as banking, credit, and money lending), the amount of late payment charges varies depending on the date the debtor makes payment, as late payment charges vary depending on the number of days overdue.

[0005] In the past, when informing a debtor of the amount due via a demand letter, the demand letter was sent to the debtor on the assumption that a specific date after the demand letter arrives (for example, 2-3 days after the demand letter is mailed) would be the expected payment date.

[0006] However, this method has the problem that if the amount received is insufficient, the claim for the shortfall is waived and profits are forfeited, and conversely, if the amount received is excessive, the excess amount has to be returned to the debtor, resulting in an administrative burden.

[0007] Furthermore, when informing a debtor of the amount due upon inquiry, in the past, a financial institution's staff member would calculate the amount due for each scheduled payment date, which created a significant administrative burden.

[0008] To solve the above problems, a method is needed that can calculate the invoice amount for each scheduled payment date at once.If the invoice amounts for multiple scheduled payment dates can be calculated at once, the invoice amounts for multiple scheduled payment dates can be listed in a list on collection notices, and the invoice amounts for multiple scheduled payment dates can be referenced in a list when a debtor makes an inquiry.

[0009] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a billing amount calculation device for each expected payment date, a billing amount calculation method for each expected payment date, and a billing amount calculation program for each expected payment date that can calculate billing amounts for each expected payment date. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems and achieve the object, the billing amount calculation device for each scheduled payment date according to the present invention is a billing amount calculation device for each scheduled payment date that is equipped with a control unit and a memory unit and is capable of calculating the billing amount for each scheduled payment date, wherein the memory unit stores claim identification data for identifying a claim, collection schedule data including a scheduled collection date that is the scheduled date for collecting the claim, and a scheduled collection amount that is the amount of the claim that is to be collected, and contract data including the claim identification data and a late payment loss interest rate, and the control unit is equipped with collection information acquisition means that acquires the scheduled collection date and scheduled collection amount linked to specified claim identification data from the collection schedule data, late payment loss interest rate acquisition means that acquires the late payment loss interest rate linked to the specified claim identification data from the contract data, scheduled payment date acquisition means that acquires multiple scheduled payment dates based on a specified base date, and billing amount calculation means that calculates the billing amount for each scheduled payment date using the acquired scheduled collection amount, the acquired late payment loss interest rate, and the number of overdue days that is the number of days from the acquired scheduled collection date to the acquired scheduled payment date.

[0011] In addition, the billing amount calculation device for each scheduled payment date according to the present invention is characterized in that the specified debt identification data and the specified base date are specified on a dunning instruction screen, which is a screen for instructing the creation of dunning data including billing amounts for each scheduled payment date, the scheduled payment date acquisition means acquires a predetermined number of days from the specified base date as the scheduled payment date, and the control unit further comprises a dunning data generation means for generating the dunning data including the billing amounts for each scheduled payment date calculated by the billing amount calculation means.

[0012] The device for calculating a billing amount by estimated payment date according to the present invention is characterized in that the control unit further comprises a dunning letter output means for outputting a dunning letter on which the contents of the dunning data are printed.

[0013] Furthermore, in the billing amount calculation device by estimated payment date according to the present invention, the storage unit further stores a billing amount inquiry control master in which display method identification data for identifying a display method of estimated payment dates on an inquiry screen on which billing amounts by estimated payment date can be inquired, and the number of estimated payment dates to be displayed on the inquiry screen is set, and the specified bond identification data and the specified base date are those specified on the inquiry screen, and the estimated payment date acquisition means, when the display method identification data in the billing amount inquiry control master means that estimated payment dates after the specified base date are to be displayed, acquires the billing amount from the specified base date and stores the display method identification data in the billing amount inquiry control master. and if the display method identification data in the billing amount inquiry control master means that the scheduled payment dates before and after the specified base date are to be displayed, the specified base date, the number of days immediately before the specified base date that is the same as the number of items displayed in the billing amount inquiry control master, and the number of days immediately after the specified base date that is the same as the number of items displayed in the billing amount inquiry control master are obtained as the scheduled payment dates, and the control unit further comprises an inquiry screen display means for displaying the inquiry screen including the billing amounts for each scheduled payment date calculated by the billing amount calculation means.

[0014] Furthermore, the device for calculating billing amount by expected payment date according to the present invention is characterized in that the person operating the inquiry screen is a person in charge at the financial business who has received an inquiry from the debtor.

[0015] a claim information acquisition step executed by the control unit to acquire, from the collection schedule data, a scheduled collection date and a scheduled collection amount linked to designated claim identification data; a late damage interest rate acquisition step to acquire, from the contract data, a late damage interest rate linked to the designated claim identification data; a scheduled payment date acquisition step to acquire, based on a designated base date, multiple scheduled payment dates; and a claim amount calculation step to calculate, by the scheduled payment date, the scheduled payment amount, the acquired late payment interest rate, and the number of days of overdue, which is the number of days from the acquired scheduled collection date to the acquired scheduled payment date.

[0016] Furthermore, the invoice amount calculation program according to the present invention is a invoice amount calculation program by expected payment date that can calculate invoice amounts by expected payment date, to be executed by an information processing device having a control unit and a memory unit, wherein the memory unit stores debt identification data for identifying debts, collection schedule data including a scheduled collection date that is a scheduled date for collecting debts, and a scheduled collection amount that is the amount of debt that is scheduled to be collected, and contract data including the debt identification data and a late payment loss interest rate, and the program is characterized by including, to be executed by the control unit, a collection information acquisition step that acquires, from the collection schedule data, the scheduled collection date and the scheduled collection amount that are linked to specified debt identification data, a late payment loss interest rate acquisition step that acquires, from the contract data, the late payment loss interest rate that is linked to the specified debt identification data, a scheduled payment date acquisition step that acquires multiple scheduled payment dates based on a specified base date, and a invoice amount calculation step that calculates the invoice amount by expected payment date using the acquired scheduled collection amount, the acquired late payment loss interest rate, and the number of overdue days that is the number of days from the acquired scheduled collection date to the acquired scheduled payment date. [Effects of the Invention]

[0017] According to the present invention, it is possible to calculate the billing amount for each scheduled payment date. [Brief explanation of the drawings]

[0018] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a device for calculating a billing amount by expected payment date. [Figure 2] FIG. 2 is a diagram illustrating an example of collection schedule data and collection record data. [Figure 3] FIG. 3 is a diagram showing an example of the contract data and billing amount inquiry control master. [Figure 4] FIG. 4 is a diagram showing an example of correlation between each piece of data. [Figure 5] FIG. 5 is a diagram showing an example of an output instruction screen for instructing output of a demand letter. [Figure 6]FIG. 6 is a diagram showing an example of the demand letter to be output. [Figure 7] FIG. 7 is a diagram showing an example of an inquiry screen when "display from designated date onwards" is selected as the display method. [Figure 8] FIG. 8 is a diagram showing an example of an inquiry screen when "display before and after specified date" is selected as the display method. DETAILED DESCRIPTION OF THE INVENTION

[0019] The following describes in detail an embodiment of a billing amount calculation device, a billing amount calculation method, and a billing amount calculation program according to the present invention with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[0020] [1. Overview] In the financial industry (banking, credit, and money lending industries, etc.), there were two challenges in informing debtors of the amount due:

[0021] The first issue was the issue of informing the customer of the amount due in the collection letter. Because the number of days overdue varies depending on the date of payment, the amount of late payment penalties claimed also varies depending on the date of payment. For this reason, in the past, a specific date after the arrival of the collection letter (for example, 2-3 days after the collection letter was mailed) was assumed to be the date of payment, and the amount of late payment penalties was provisionally determined and notified in the collection letter.

[0022] If the amount received was insufficient, the claim for the shortfall was waived, and conversely, if the amount received was excessive, the excess amount was returned. However, in the former case, there was the issue that the benefit of the late payment penalty for the shortfall was waived, and in the latter case, there was the issue of the administrative burden involved in returning the excess amount.

[0023] In other words, in the past, invoice amounts were only notified as of one date during collection work, which resulted in excess or shortfalls occurring when payments were made on a date other than the expected date, resulting in administrative burdens.

[0024] The second issue was the issue of informing debtors of the amount due when they inquired. As mentioned above, the number of days overdue varies depending on the date of payment, and so the amount of late payment charges to be claimed also varies depending on the date of payment. For this reason, in the past, invoice amounts were inquired for each scheduled payment date of the debtor, but this sometimes made it difficult to respond to inquiries smoothly, and there was also the issue of the administrative burden involved in making inquiries.

[0025] In other words, in the past, when responding to inquiries, the invoice amount was only inquired as of one date each time, which resulted in a lot of operational effort and inefficiency when informing a debtor of the invoice amount for multiple expected payment dates.

[0026] Therefore, in this embodiment, when handling overdue receivables, it is possible to output the invoice amounts for multiple payment dates at once. This has the effect of eliminating the problems of administrative burden and losses. Specifically, it has the following two effects.

[0027] The first effect is that by the debtor making a deposit after understanding the appropriate amount due based on the date of deposit, it is possible to eliminate any excess or shortfall in the amount deposited, thereby eliminating the administrative burden of forfeiting the benefit of late payment charges for the shortfall and returning the excess amount.

[0028] The second benefit is that even if there are multiple expected payment dates, the billing amount can be efficiently notified.

[0029] In this embodiment, the following four methods are assumed as methods for notifying the billing amount for each scheduled payment date.

[0030] The first is a notice by collection letter. In this notice, a collection letter is output for receivables for which direct debit was not possible. The invoice amount for 10 days after the specified invoice date is output within the layout of the collection letter.

[0031] The second type of guidance is through a billing inquiry. In this guidance, a financial institution employee will make a billing inquiry after receiving a telephone inquiry from a debtor. The list of results of the billing inquiry will display the billing amount for the 10 days following the specified payment date (the initial display is for the day specified).

[0032] The third option is to receive information through an inquiry on the member site (website). With this option, a URL with the credit number embedded is sent to the debtor via a reminder email, etc., and the debtor can immediately inquire on their personal page on the member site (website). The amount due for the 10 days from the specified payment date is displayed (the initial display is set to the day of the payment).

[0033] The fourth method is to send reminder notices by email. In this method, the contents of the reminder notice are sent by email. The billing amount for the 10 days after the specified billing date is displayed.

[0034] The specific configuration and operation will be described below.

[0035] [2. Configuration] An example of the configuration of the billing amount calculation device 100 for each estimated payment 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 billing amount calculation device 100 for each estimated payment date.

[0036] The billing amount calculation device for each expected payment date 100 is a commercially available desktop personal computer. Note that the billing amount calculation device for each expected payment date 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0037] The billing amount calculation device for estimated payment dates 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the billing amount calculation device for estimated payment dates 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0038] The communication interface unit 104 communicably connects the billing amount calculation device for each estimated payment date 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the billing amount calculation device for each estimated payment date 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described below 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. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0040] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the 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 RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0041] The storage unit 106 includes, for example, collection schedule data 106a, collection performance data 106b, contract data 106c, billing amount inquiry control master 106d, and reminder data 106e. The correlation between each data is as shown in FIG. 4.

[0042] The collection schedule data 106a is data for managing collection schedules from debtors. 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 a collection schedule, a scheduled collection month and year which are the scheduled years and months for collecting the claim, a scheduled collection date which is the scheduled date for collecting the claim, a scheduled collection amount which is the amount of the claim to be collected, the principal in the scheduled collection amount, interest in the scheduled collection amount, fees in the scheduled collection amount, and a completion flag which is a flag for identifying whether collection of the claim has been completed.

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

[0044] The collection record data 106b is data for managing the actual collection record against the collection schedule. As shown in Fig. 2, the collection record 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 on which the claim was collected, the collection amount which is the amount of the collected claim, the principal in the collection amount, the interest in the collection amount, the commission in the collection amount, etc.

[0045] The contract data 106c is data for managing the contract contents, and includes, for example, the bond identification data (bond number), the loan interest rate, the late payment damage interest rate, and the like, as shown in FIG.

[0046] The billing amount inquiry control master 106d is a master that manages the display settings for billing amount inquiries for each process. As shown in Figure 3, the billing amount inquiry control master 106d includes, for example, process identification data (processing ID) for identifying the process for inquiring about the billing amount, display method identification data (display method code) for identifying the display method of expected payment dates on an inquiry screen that allows inquiry about billing amounts by expected payment date, the number of expected payment dates displayed on the inquiry screen, a display method changeable flag that identifies whether the operator operating the inquiry screen can change the display method or not, and a display number changeable flag that identifies whether the operator operating the inquiry screen can change the number of displayed items or not. The billing amount inquiry control master 106d can be set, for example, by a manager or a senior official at a financial institution.

[0047] As shown in Figure 3, the processing identification data (processing ID) may be, for example, a debt inquiry made by a financial institution employee upon receiving an inquiry from a debtor (ID of "1: Debt Inquiry"), or a debt inquiry made by the debtor himself / herself on a member site, etc. (ID of "2: WEB Member Inquiry").

[0048] The display method identification data (display method code), as shown in Figure 3, means displaying the expected deposit dates after the specified base date (code "1: Display the number of items to be displayed after the specified date"), or means displaying the expected deposit dates before and after the specified base date (code "2: Display the number of items to be displayed before and after the specified date").

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

[0050] As shown in Figure 3, the display count change flag is a flag (a "true" flag) that indicates that the operator operating the inquiry screen can change the display count, or a flag (a "false" flag) that indicates that the operator operating the inquiry screen cannot change the display count.

[0051] The dunning data 106e is data including the calculated billing amount for each scheduled payment date.

[0052] The control unit 102 is a CPU or the like that performs overall control of the billing amount calculation device by expected payment date 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.

[0053] The control unit 102 has, in terms of functional concept, for example: (1) a collection information acquisition unit 102a as collection information acquisition means for acquiring the scheduled collection date and scheduled collection amount linked to the specified receivable identification data from the collection schedule data; (2) a late damage interest rate acquisition unit 102b as a late damage interest rate acquisition means for acquiring the late damage interest rate linked to the specified receivable identification data from the contract data; (3) a scheduled deposit date acquisition unit 102c as a scheduled deposit date acquisition means for acquiring multiple scheduled deposit dates based on a specified base date; and (4) a collection information acquisition unit 102d as a means for acquiring the scheduled collection amount, the acquired late damage interest rate, and the acquired collection schedule. (5) a dunning data generation unit 102e as a dunning data generation means that generates the dunning data including the dunning amount for each scheduled payment date calculated by the dunning amount calculation means; (6) a dunning notice output unit 102f as a dunning notice output means that outputs a dunning notice on which the contents of the dunning data are printed; and (7) an inquiry screen display unit 102g as an inquiry screen display means that displays the inquiry screen including the dunning amount for each scheduled payment date calculated by the dunning amount calculation means.

[0054] The collection information acquisition unit 102a acquires the scheduled collection date and the scheduled collection amount linked to the specified bond number from the collection schedule data 106a (see FIG. 2).

[0055] The late payment damage interest rate acquisition unit 102b acquires the late payment damage interest rate linked to the specified bond number from the contract data 106c (see FIG. 3).

[0056] The expected deposit date acquisition unit 102c acquires a plurality of expected deposit dates based on a specified base date.

[0057] If the specified bond number and the specified base date are those specified on a dunning instruction screen (see the output instruction screen shown in FIG. 5), which is a screen for instructing the creation of dunning data 106e including the claim amount by scheduled deposit date, the scheduled deposit date acquisition unit 102c acquires a predetermined number of days from the specified base date as the scheduled deposit dates. For example, if the specified base 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 dates.

[0058] If the specified credit number and the specified base date are those specified on an inquiry screen (see the inquiry screens in Figures 7 and 8) that allows inquiries about the billing amount by expected payment date, the expected payment date acquisition unit 102c acquires the expected payment date as follows: The person operating the inquiry screen is, for example, a person in charge at a financial institution who receives an inquiry from a debtor.

[0059] That is, if the display method code (initial value) in the billing amount inquiry control master 106d is "1: Display the number of items to be displayed after the specified date," the expected payment date acquisition unit 102c acquires the number of days from the specified base date that is the same as the number of items to be displayed in the billing amount inquiry control master 106d as the expected payment date. For example, if the specified base date is "2023 / 5 / 30" and the number of items to be displayed is "10," the expected payment date acquisition unit 102c acquires "2023 / 5 / 30~2023 / 6 / 8" as the expected payment date.

[0060] In contrast, if the display method code (initial value) in the billing amount inquiry control master 106d is "2: display the number of items before and after the specified date," the expected deposit date acquisition unit 102c acquires as expected deposit dates the specified base date, the number of days immediately before the specified base date that is the same as the number of items displayed in the billing amount inquiry control master 106d, and the number of days immediately after the specified base date that is the same as the number of items displayed in the billing amount inquiry control master 106d. For example, if the specified base date is "2023 / 6 / 2" and the number of items displayed is "3," the expected deposit date acquisition unit 102c acquires "2023 / 6 / 2," "2023 / 5 / 30-2023 / 6 / 1," and "2023 / 6 / 3-2023 / 6 / 5" as expected deposit dates.

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

[0062] Specifically, the billing amount calculation unit 102d can calculate the billing amount for each scheduled payment date by adding the late payment charge to the scheduled collection amount, and the late payment charge can be calculated using the formula, for example, "scheduled collection amount x late payment charge interest rate x number of days in arrears / number of days in a year." However, the calculation formula is not limited to this.

[0063] The dunning data generating unit 102e generates dunning data 106e including the billing amounts for each scheduled payment date calculated by the billing amount calculating unit 102d.

[0064] The demand letter output unit 102f outputs a demand letter (see FIG. 6) on which the contents of the demand data 106e are printed.

[0065] The inquiry screen display unit 102g displays an inquiry screen (see the inquiry screens in FIGS. 7 and 8) including the billing amounts calculated by the billing amount calculation unit 102d for each scheduled payment date.

[0066] [3. Specific examples of processing] This section describes a specific example of the processing according to this embodiment. [3-1] describes the generation of a demand letter, and [3-2] describes the inquiry of the invoice amount. The generation of the demand letter and the inquiry of the invoice amount are assumed to be performed by a person in charge at the financial institution (hereinafter, sometimes simply referred to as "person in charge").

[0067] In this section [3. Specific example of processing], the explanation will be given on the assumption that the collection schedule data 106a is set in advance as shown in FIG. 2, and the contract data 106c and billing amount inquiry control master 106d are set in advance as shown in FIG. 3.

[0068] [3-1. Generating a reminder letter] First, the person in charge enters the information necessary to generate a reminder letter from the output instruction screen shown in Figure 5. Specifically, the date on which the reminder letter is expected to arrive to the debtor (= notification date) is entered as the billing date. In the example of Figure 5, "5 / 30 / 2023" is entered as the billing date. Additionally, in the <Range Specification> section, the person in charge of reminder, the claim number, and the number of months in arrears are entered. In the example of Figure 5, "1000-1001" is entered as the claim number. Once the information entry in <Range Specification> is complete, a list of claims to be output will be displayed by combining claim numbers and customer names, as shown in the lower part of Figure 5.

[0069] When the necessary information is entered on the output instruction screen shown in FIG. 5 and the output button is pressed, a demand letter is generated as follows.

[0070] First, the collection information acquisition unit 102a acquires a record with collection SEQ=4 from the collection schedule data 106a in Fig. 2, which has the specified bond No. "1000", a scheduled collection date that is earlier than the specified billing date "2023 / 5 / 30", and a completion flag of "0 (collection incomplete)".Then, the collection information acquisition unit 102a acquires the scheduled collection date "2023 / 5 / 26" and the scheduled collection amount "10,000 yen" from the acquired record with collection SEQ=4.

[0071] More specifically, the collection information acquisition unit 102a may calculate and acquire the planned collection amount, principal, interest, and fee by subtracting each amount in a record in the collection plan data 106a that satisfies all of the following conditions (i) to (iii) from each amount in the record in the collection performance data 106b that has the claim number and collection SEQ in that record. If the conditions described in the previous paragraph are specified, the collection information acquisition unit 102a will acquire a planned collection amount of 10,000 yen, a principal of 7,000 yen, interest of 3,000 yen, and a fee of 0 yen. (conditions) (i) Have a designated bond number. (ii) The scheduled collection date in the collection schedule data 106a is equal to or less than the specified billing date (deposit date). (iii) The completion flag in the collection schedule data 106a is 0 (collection incomplete).

[0072] Next, the late payment damage interest rate obtaining unit 102b obtains "0.14600" from the contract data 106c in FIG. 3 as the late payment damage interest rate associated with the specified bond No. "1000".

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

[0074] Next, the invoice amount calculation unit 102d calculates the invoice amount for each scheduled payment date by adding the late payment penalty to the acquired scheduled collection amount of "10,000 yen." The invoice amount calculation unit 102d calculates the late payment penalty for each scheduled payment date using the following calculation formula: (the acquired scheduled collection amount of 10,000 yen) × (the acquired late payment penalty interest rate of 0.14600) × (the number of days of overdue, which is the number of days from the acquired scheduled collection date of 2023 / 5 / 26 to the acquired scheduled payment dates of 2023 / 5 / 30 to 2023 / 6 / 8) ÷ (365 days per year). The calculation formula is specifically as follows: 5 / 30: 10,000×0.14600×4÷365=16 yen 5 / 31: 10,000×0.14600×5÷365=20 yen 6 / 1: 10,000×0.14600×6÷365=24 yen 6 / 2: 10,000×0.14600×7÷365=28 yen 6 / 3: 10,000×0.14600×8÷365=32 yen 6 / 4: 10,000×0.14600×9÷365=36 yen 6 / 5: 10,000×0.14600×10÷365=40 yen 6 / 6: 10,000×0.14600×11÷365=44 yen 6 / 7: 10,000×0.14600×12÷365=48 yen 6 / 8: 10,000×0.14600×13÷365=52 yen

[0075] Next, the dunning data generating unit 102e generates dunning data 106e including the billing amounts for each scheduled payment date calculated by the billing amount calculating unit 102d.

[0076] Finally, the dunning notice output unit 102f outputs the dunning notice shown in Fig. 6, on which the contents of the dunning data 106e (= invoice amount by expected payment date) are printed. In the dunning notice shown in Fig. 6, "May 29, 2023" in the upper right corner indicates the output date (processing date).

[0077] As explained above in section [3-1], with the billing amount calculation device 100 for each scheduled payment date according to this embodiment, the debtor can refer to the demand letter on which the billing amount for each scheduled payment date is printed, check the billing amount for each scheduled payment date at a glance, and make a payment of the appropriate amount. This eliminates shortfalls in payments, preventing financial institutions from abandoning their profits, and also reduces the administrative burden on financial institutions associated with the return of excess payments, as it eliminates excess payments.

[0078] [3-2. Inquiry about billing amount] First, the person in charge enters the necessary information on the inquiry screen for making a claim inquiry. Figure 7 shows an example of the inquiry screen when "Display after specified date" is selected as the display method. Figure 8 shows an example of the inquiry screen when "Display before and after specified date" is selected as the display method.

[0079] In the example in Figure 7, "1000" is entered as the debt number, and in the <Billing amount inquiry> section, "Display from specified date onwards" is specified as the display method, "10" is specified as the number of items to display, and "2023 / 5 / 30" is entered as the payment date.

[0080] In the example of Figure 8, "1000" is entered as the claim number, and in the <Billing amount inquiry> section, "Display around specified date" is specified as the display method, "3" is specified as the number of items to display, and "2023 / 6 / 2" is entered as the payment date.

[0081] Once this information has been entered, a list of the inquiry results will be displayed as shown in the lower part of Figures 7 and 8, with a combination of the date of deposit, day of the week, number of days overdue, amount due, principal, interest, and late payment charges.

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

[0083] The default value of the display method is displayed according to the setting of the display method code (default value) in the billing amount inquiry control master 106d. Specifically, if the display method code (default value) is set to "1: Display the number of items to be displayed after the specified date," the default value is displayed as "Display after the specified date" (checked), as shown on the inquiry screen in Figure 7. On the other hand, if the display method code (default value) is set to "2: Display the number of items to be displayed before and after the specified date," the default value is displayed as "Display before and after the specified date" (checked), as shown on the inquiry screen in Figure 8.

[0084] In addition, the input control for "Display from specified date onwards" or "Display around specified date" can also be performed by setting the display method changeable flag in the billing amount inquiry control master 106d. Specifically, if the display method changeable flag is set to "true," "Display from specified date onwards" or "Display around specified date" can be changed from its initial value. On the other hand, if the display method changeable flag is set to "false," "Display from specified date onwards" or "Display around specified date" cannot be changed from its initial value (the "Display from specified date onwards" or "Display around specified date" item itself can be hidden).

[0085] The initial value of the number of items to be displayed is displayed by setting the number of items to be displayed (initial value) in the billing amount inquiry control master 106d. The input of the number of items to be displayed can also be controlled by setting the flag for changeable number of items to be displayed in the billing amount inquiry control master 106d. Specifically, if the flag for changeable number of items to be displayed is set to "true," the number of items to be displayed can be changed from the initial value. On the other hand, if the flag for changeable number of items to be displayed is set to "false," the number of items to be displayed cannot be changed from the initial value (the item for changeable number of items to be displayed itself can be hidden).

[0086] When the necessary information has been entered on the inquiry screens shown in FIGS. 7 and 8, the results of the credit inquiry will be displayed as follows:

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

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

[0089] Next, the expected deposit date acquisition unit 102c acquires multiple expected deposit dates based on the specified deposit date, but the acquisition method differs depending on the specified display method ("display after specified date" or "display around specified date"), so the following explains each case separately.

[0090] If the specified display method is "Display from specified date onwards" (i.e., in the example of Figure 7), the expected deposit date acquisition unit 102c acquires 10 days (2023 / 5 / 30 to 2023 / 6 / 8) as expected deposit dates, which is the same number of days as the specified number of items to display, "10", from the specified deposit date, "2023 / 5 / 30".

[0091] In contrast, if the specified display method is "display around the specified date" (i.e., in the example of Figure 8), the expected deposit date acquisition unit 102c acquires as expected deposit dates the specified deposit date "2023 / 6 / 2", three days (2023 / 5 / 30 to 2023 / 6 / 1) immediately before the specified deposit date, which is the same number of days as the specified number of items to display "3", and three days (2023 / 6 / 3 to 2023 / 6 / 5) immediately after the specified deposit date, which is the same number of days as the specified number of items to display "3".

[0092] Next, the billing amount calculation unit 102d calculates the billing amount for each expected payment date by adding the late payment penalty to the acquired expected collection amount of "10,000 yen" in the same way as in [3-1]. The method for calculating the billing amount is the same as in [3-1], so a detailed explanation will be omitted.

[0093] Finally, the inquiry screen display unit 102g displays the inquiry screens of FIGS. 7 and 8, including the billing amounts calculated by the billing amount calculation unit 102d for each scheduled payment date.

[0094] As explained above in this section [3-2], according to the billing amount calculation device 100 for each scheduled payment date of this embodiment, the person in charge can efficiently respond even when the debtor inquires about the billing amount for multiple scheduled payment dates by referring to the inquiry screen that displays the billing amount for each scheduled payment date.

[0095] Furthermore, with the billing amount calculation device 100 according to this embodiment, it is possible to set the display method in accordance with the user's operation (inquiry work) and the debtor's requests based on product characteristics, etc. This allows the person in charge to, for example, estimate the date when the debtor will be able to prepare the repayment funds and check the billing amounts before and after that date.

[0096] In this section [3-2], we have explained the inquiry screen when a financial institution employee makes a debt inquiry, but the inquiry screen when a debtor himself / herself makes a debt inquiry on a member site (website) may also have a similar screen configuration.

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

[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 Goal 16 of the SDGs.

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

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

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

[0103] Furthermore, with regard to the billing amount calculation device for each estimated payment date 100, the components shown in the figure are functional concepts, and do not necessarily have to be physically configured as shown in the figure.

[0104] For example, all or any part of the processing functions of the billing amount calculation device for estimated payment dates 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 the billing amount calculation device for estimated payment dates 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0105] In addition, this computer program may be stored in an application program server connected to the billing amount calculation device for each estimated payment date 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 configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[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 billing amount calculation device for each estimated payment date 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The billing amount calculation device for each estimated payment date 100 may also be realized by installing software (including programs or data, etc.) that causes the device to perform the processing described in this embodiment.

[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 in industries that handle financial claims, and is particularly useful for financial institutions, non-banks, banks, credit companies, money lenders, and the like. [Explanation of symbols]

[0112] 100 Billing amount calculation device by expected payment date 102 Control section 102a Collection information acquisition unit 102b Late Payment Interest Rate Acquisition Department 102c Scheduled Deposit Date Acquisition Section 102d Claims calculation section 102e Dunning Data Generation Department 102f Demand letter output section 102g Inquiry screen display section 104 Communication interface unit 106 Storage section 106a Data to be collected 106b Recovery performance data 106c Contract Data 106d Billing Amount Inquiry Control Master 106e Dunning Data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A billing amount calculation device for calculating a billing amount for each scheduled payment date, the device comprising a control unit and a storage unit, The storage unit includes: collection schedule data including claim identification data for identifying the claim, a scheduled collection date which is a date on which the claim is scheduled to be collected, and a scheduled collection amount which is the amount of the claim to be collected; Contract data including credit identification data and a late payment interest rate; is stored, The control unit is a collection information acquiring means for acquiring a collection date and a collection amount associated with a designated claim identification data from the collection schedule data; a late payment loss interest rate acquisition means for acquiring a late payment loss interest rate associated with the specified credit identification data from the contract data; a scheduled deposit date acquisition means for acquiring a plurality of scheduled deposit dates based on a designated base date; a billing amount calculation means for calculating a billing amount for each scheduled payment date using the acquired scheduled collection amount, the acquired late payment interest rate, and the number of overdue days, which is the number of days from the acquired scheduled collection date to the acquired scheduled payment date; To have A billing amount calculation device for each scheduled payment date, comprising:

2. The specified claim identification data and the specified base date are specified on a dunning instruction screen, which is a screen for instructing the creation of dunning data including the billing amount by scheduled payment date, The expected deposit date acquisition means acquires a predetermined number of days from the specified base date as an expected deposit date, The control unit is dunning data generation means for generating the dunning data including the billing amount for each scheduled payment date calculated by the billing amount calculation means Further comprising:

2. The device for calculating a billing amount by estimated payment date according to claim 1.

3. The control unit is a dunning notice output means for outputting a dunning notice on which the contents of the dunning data are printed; Further comprising:

3. The device for calculating a billing amount by estimated payment date according to claim 2.

4. The storage unit includes: A billing amount inquiry control master is further stored, in which display method identification data for identifying a display method of the scheduled payment date on an inquiry screen on which the billing amount by scheduled payment date can be inquired, and the number of scheduled payment dates to be displayed on the inquiry screen are set, the specified bond identification data and the specified base date are specified on the inquiry screen, said expected payment date acquisition means, when the display method identification data in said billing amount inquiry control master means to display expected payment dates on or after said specified base date, acquires as expected payment dates the number of days from said specified base date that is equal to the number of items displayed in said billing amount inquiry control master; in contrast, when the display method identification data in said billing amount inquiry control master means to display expected payment dates before or after said specified base date, acquires as expected payment dates the specified base date, the number of days immediately before said specified base date that is equal to the number of items displayed in said billing amount inquiry control master, and the number of days immediately after said specified base date that is equal to the number of items displayed in said billing amount inquiry control master; The control unit is An inquiry screen display means for displaying the inquiry screen including the billing amount for each scheduled payment date calculated by the billing amount calculation means. Further comprising:

2. The device for calculating a billing amount by estimated payment date according to claim 1.

5. The person operating the inquiry screen is the person in charge at the financial business who received the inquiry from the debtor, 5. The device for calculating a billing amount by estimated payment date according to claim 4.

6. A method for calculating a billing amount by expected payment date, the method being executed by an information processing device having a control unit and a storage unit, and capable of calculating a billing amount by expected payment date, comprising: The storage unit includes: collection schedule data including claim identification data for identifying the claim, a scheduled collection date which is a date on which the claim is scheduled to be collected, and a scheduled collection amount which is the amount of the claim to be collected; Contract data including credit identification data and a late payment interest rate; is stored, Executed by the control unit, a collection information acquisition step of acquiring a collection date and a collection amount associated with the designated claim identification data from the collection schedule data; a late payment interest rate acquisition step of acquiring a late payment interest rate associated with the specified claim identification data from the contract data; A planned deposit date acquisition step for acquiring multiple planned deposit dates based on a specified base date; a billing amount calculation step of calculating a billing amount for each scheduled payment date using the acquired scheduled collection amount, the acquired late payment interest rate, and the number of overdue days, which is the number of days from the acquired scheduled collection date to the acquired scheduled payment date; containing, A method for calculating billing amounts by expected payment date, characterized by the above.

7. A billing amount calculation program for calculating a billing amount by expected payment date, the program being executed by an information processing device having a control unit and a storage unit, the program being capable of calculating a billing amount by expected payment date, The storage unit includes: collection schedule data including claim identification data for identifying the claim, a scheduled collection date which is a date on which the claim is scheduled to be collected, and a scheduled collection amount which is the amount of the claim to be collected; Contract data including credit identification data and a late payment interest rate; is stored, To cause the control unit to execute a collection information acquisition step of acquiring a collection date and a collection amount associated with the designated claim identification data from the collection schedule data; a late payment interest rate acquisition step of acquiring a late payment interest rate associated with the specified claim identification data from the contract data; A planned deposit date acquisition step for acquiring multiple planned deposit dates based on a specified base date; a billing amount calculation step of calculating a billing amount for each scheduled payment date using the acquired scheduled collection amount, the acquired late payment interest rate, and the number of overdue days, which is the number of days from the acquired scheduled collection date to the acquired scheduled payment date; containing, A program for calculating billing amounts by expected payment date.

Images