JP2025004845A - Apparatus for calculating billing amount by scheduled payment date, method for calculating billing amount by scheduled payment date, and program for calculating billing amount by scheduled payment date - Google Patents

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

The present invention relates to a billing amount calculation device for each scheduled payment date, a billing amount calculation method for each scheduled payment date, and a billing amount calculation program for each scheduled payment date.

Patent document 1 discloses technology that allows taxpayers to view their own tax payment information and settle outstanding taxes through appropriation over a network (see paragraph 0006 of patent document 1).

JP 2010-282435 A

Here, in industries that bill debtors for unpaid amounts (for example, financial industries such as the banking, credit and money lending industries), the amount of late fees varies depending on the date the debtor makes the payment. This is because late fees vary depending on the number of days overdue.

When informing a debtor of the amount due via a reminder letter, traditionally, a specific date after the arrival of the reminder letter (for example, 2-3 days after the reminder letter is mailed) was assumed to be the expected date of payment, and the reminder letter was sent to the debtor.

However, this method has the problem that if the amount received is insufficient, the shortfall in the claim is waived, resulting in the forfeiting of profits, and conversely, if the amount received is excessive, the excess amount must be returned to the debtor, resulting in an administrative burden.

Furthermore, when informing a debtor of the amount due upon inquiry, traditionally the financial institution's staff would calculate the amount due for each scheduled payment date, which created a problem of a large administrative burden.

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 could be calculated at once, the invoice amounts for multiple scheduled payment dates could be listed in a list on collection letters, and when a debtor inquires, the invoice amounts for multiple scheduled payment dates could be inquired in a list.

The present invention has been made in consideration of the above problems, and aims to provide a billing amount calculation device for each scheduled payment date, a billing amount calculation method for each scheduled payment date, and a billing amount calculation program for each scheduled payment date that can calculate the billing amount for each scheduled payment date.

In order to solve the above-mentioned problems and achieve the object, the billing amount calculation device according to the present invention is a billing amount calculation device for calculating billing amounts by scheduled payment date, which is equipped with a control unit and a storage unit and can calculate billing amounts by scheduled payment date. The storage unit stores debt identification data for identifying debts, scheduled collection 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 to be collected, and contract data including the debt identification data and a late payment interest rate. The control unit is equipped with a collection information acquisition means for acquiring the scheduled collection date and scheduled collection amount linked to the specified debt identification data from the scheduled collection data, a late payment interest rate acquisition means for acquiring the late payment interest rate linked to the specified debt identification data from the contract data, a scheduled payment date acquisition means for acquiring multiple scheduled payment dates based on a specified base date, and a billing amount calculation means for calculating the billing amount by scheduled payment date using the acquired scheduled collection amount, the acquired late payment 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.

The billing amount calculation device for each scheduled payment date according to the present invention is characterized in that 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 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 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.

The billing amount calculation device for each scheduled payment date according to the present invention is also characterized in that the control unit further includes a dunning letter output means for outputting a dunning letter on which the contents of the dunning data are printed.

In addition, in the billing amount calculation device 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 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 is set, and the specified claim identification data and the specified base date are specified on the inquiry screen, and the scheduled payment date acquisition means, when the display method identification data in the billing amount inquiry control master means that scheduled payment dates after the specified base date are to be displayed, acquires the billing amount inquiry control master from the specified base date. The control unit further includes 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. When the display method identification data in the billing amount inquiry control master indicates that the scheduled payment dates before and after the specified base date are to be displayed, the control unit obtains the specified base date, the number of days immediately before the specified base date that is the same as the number of days 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 days displayed in the billing amount inquiry control master, as the scheduled payment dates.

The billing amount calculation device for each scheduled payment date according to the present invention is also characterized in that the person operating the inquiry screen is a person in charge at the financial service provider who receives an inquiry from the debtor.

The method for calculating the billing amount by scheduled payment date according to the present invention is a method for calculating the billing amount by scheduled payment date, which is executed by an information processing device having a control unit and a storage unit, and which is capable of calculating the billing amount by scheduled payment date. The storage unit stores claim identification data for identifying claims, collection schedule data including a scheduled collection date that is a scheduled date for collecting claims, and a scheduled collection amount that is the amount of claims to be collected, and contract data including the claim identification data and a late payment interest rate. The method includes a collection information acquisition step executed by the control unit to acquire the scheduled collection date and the scheduled collection amount linked to the specified claim identification data from the collection schedule data, a late payment interest rate acquisition step to acquire the late payment interest rate linked to the specified claim identification data from the contract data, a scheduled payment date acquisition step to acquire multiple scheduled payment dates based on a specified base date, and a billing amount calculation step to calculate the billing amount by scheduled payment date using the acquired scheduled collection amount, the acquired late payment 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.

The billing amount calculation program according to the present invention is a billing amount calculation program for calculating a billing amount for each scheduled payment date, which is executed by an information processing device having a control unit and a storage unit, and which is capable of calculating a billing amount for each scheduled payment date. The storage unit stores claim identification data for identifying claims, collection schedule data including a scheduled collection date that is a scheduled date for collecting claims, and a scheduled collection amount that is the amount of claims to be collected, and contract data including the claim identification data and a late payment interest rate. The program is executed by the control unit and includes a collection information acquisition step for acquiring a scheduled collection date and a scheduled collection amount linked to a specified claim identification data from the collection schedule data, a late payment interest rate acquisition step for acquiring a late payment interest rate linked to the specified claim identification data from the contract data, a scheduled payment date acquisition step for acquiring multiple scheduled payment dates based on a specified base date, and a billing amount calculation step 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 that is the number of days from the acquired scheduled collection date to the acquired scheduled payment date.

The present invention has the effect of being able to calculate the billing amount for each scheduled payment date.

FIG. 1 is a block diagram showing an example of the configuration of a device for calculating a billing amount by expected payment date. FIG. 2 is a diagram showing an example of collection schedule data and collection record data. FIG. 3 is a diagram showing an example of the contract data and billing amount inquiry control master. FIG. 4 is a diagram showing an example of correlation between each piece of data. FIG. 5 is a diagram showing an example of an output instruction screen for instructing output of a reminder letter. FIG. 6 is a diagram showing an example of a reminder letter to be output. FIG. 7 is a diagram showing an example of an inquiry screen when "display from designated date onwards" is selected as the display method. FIG. 8 is a diagram showing an example of an inquiry screen when "display around a specified date" is selected as the display method.

Below, an embodiment of the billing amount calculation device for each scheduled payment date, the billing amount calculation method for each scheduled payment date, and the billing amount calculation program for each scheduled payment date according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

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

The first issue was regarding the notification of the amount to be claimed in the reminder letter. Because the number of days overdue varies depending on the date of payment, the amount of the late fee to be claimed also varies depending on the date of payment. For this reason, in the past, a specific date after the arrival of the reminder letter (for example, 2-3 days after the reminder letter was mailed) was assumed to be the date of payment, and the amount of the late fee was provisionally determined and notified in the reminder letter.

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

In other words, previously, invoice amounts were only notified as of one date during collection work, which resulted in excesses and shortfalls occurring when payments were made on a date other than the expected date of payment, creating an administrative burden.

The second issue was the problem of informing debtors of the amount due when they inquired about it. As mentioned above, the number of days overdue varies depending on the date of payment, and so the amount of late fees claimed also varies depending on the date of payment. For this reason, in the past, invoice amounts were inquired about for each scheduled date of payment from the debtor, but this sometimes meant that inquiries could not be handled smoothly, and there was also the issue of the administrative burden involved in making inquiries.

In other words, in the past, when making inquiries, the invoice amount was only inquired as of one date each time, which resulted in a lot of operational work and inefficiencies when informing a debtor of the invoice amount for multiple planned payment dates.

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

The first effect is that the debtor can eliminate any shortfall or excess in the amount of the payment by making a payment after understanding the appropriate amount due based on the date of payment, which in turn eliminates the administrative burden of forgoing the benefit of late payment charges for the shortfall and returning the excess amount.

The second benefit is that it allows you to efficiently inform the invoice amount even if there are multiple scheduled payment dates.

In this embodiment, the following four methods are assumed to provide notification of the billing amount by expected payment date.

The first type of notification is a reminder letter. This notification outputs a reminder letter for receivables for which direct debit was not possible. The billing amount for the 10 days following the specified billing date is output within the layout of the reminder letter.

The second type of guidance is through an invoice amount inquiry. In this type of guidance, a person in charge at the financial service provider will make an inquiry about the invoice amount after receiving a telephone inquiry from the debtor. The invoice amount for the 10 days following the specified date of payment will be displayed in a list of the results of the invoice amount inquiry (the initial display is specified as of the day).

The third method is to receive guidance via an inquiry on the member site (website). With this type of guidance, a URL with the claim number embedded is sent to the debtor via a reminder email or similar, and the debtor can immediately inquire on their own page on the member site (website). The amount due for the 10 days following the specified payment date is displayed (the initial display is specified on the day).

The fourth method is to send a reminder notice by email. In this method, the contents of the reminder notice are sent by email. The billing amount for the 10 days following the specified billing date is displayed.

The specific configuration and operation are explained below.

2. Configuration
An example of the configuration of the estimated payment date-based billing calculation device 100 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 estimated payment date-based billing calculation device 100.

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

The billing amount calculation device 100 for calculating a billing amount by expected date of payment comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the billing amount calculation device 100 for calculating a billing amount by expected date of payment is connected so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the billing amount calculation device by 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 by 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.

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 works with a mouse to provide 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

The memory unit 106 includes, for example, scheduled collection data 106a, actual collection 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.

Collection schedule data 106a is data that manages collection schedules from debtors. As shown in FIG. 2, collection schedule data 106a includes, for example, debt identification data (debt number) for identifying the debt, collection schedule identification data (collection SEQ) for identifying the collection schedule, the scheduled collection month and year, which is the scheduled year and month for collecting the debt, the scheduled collection date, which is the scheduled date for collecting the debt, the scheduled collection amount, which is the amount of the debt 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 debt has been completed.

The completion flag is a flag indicating that the collection of the receivable has been completed (flag of "1") or a flag indicating that the collection of the receivable 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 with collection SEQ = 1 to 3, so all of the scheduled collection amounts in the records with collection SEQ = 1 to 3 have been collected.

The collection performance data 106b is data that manages the actual collection performance against the collection schedule. As shown in FIG. 2, the collection performance 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 of the collection amount, the interest on the collection amount, the fee on the collection amount, etc.

The contract data 106c is data that manages the contents of the contract. As shown in FIG. 3, the contract data 106c includes, for example, the claim identification data (claim number), the loan interest rate, the late payment interest rate, etc.

The billing amount inquiry control master 106d is a master that manages the display settings of billing amount inquiries for each process. As shown in FIG. 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 the scheduled deposit date on the inquiry screen that allows the billing amount by scheduled deposit date to be inquired, the number of scheduled deposit dates displayed 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, and a display number changeable flag that is a flag for identifying 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 person in a position of authority at a financial institution.

As shown in FIG. 3, the processing identification data (processing ID) may be, for example, a debt inquiry made by a financial institution's staff member upon receiving an inquiry from a debtor (ID "1: debt inquiry"), or a debt inquiry made by the debtor himself on a member's website, etc. (ID "2: WEB member inquiry").

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

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

As shown in FIG. 3, the display count changeable flag is a flag indicating that the operator operating the inquiry screen can change the display count (a "true" flag), or a flag indicating that the operator operating the inquiry screen cannot change the display count (a "false" flag).

Dunning data 106e is data that includes the calculated billing amount for each scheduled payment date.

The control unit 102 is a CPU or the like that provides overall control of the billing amount calculation device for estimated payment dates 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.

The control unit 102, in terms of its functional concept, includes, for example, (1) a collection information acquisition unit 102a as a collection information acquisition means for acquiring a planned collection date and a planned collection amount linked to the specified receivable identification data from the collection schedule data, (2) a late payment loss interest rate acquisition unit 102b as a late payment loss interest rate acquisition means for acquiring a late payment loss interest rate linked to the specified receivable identification data from the contract data, (3) a planned payment date acquisition unit 102c as a planned payment date acquisition means for acquiring multiple planned payment dates based on a specified base date, and (4) a planned payment amount acquired, a late payment loss interest rate acquired, and a collection schedule for the acquired late payment loss amount. (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.

The collection information acquisition unit 102a acquires the planned collection date and planned collection amount linked to the specified claim number from the collection schedule data 106a (see Figure 2).

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

The expected deposit date acquisition unit 102c acquires multiple expected deposit dates based on a specified base date.

If the specified claim number and the specified base date are 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 billing amount by scheduled payment date, the scheduled payment date acquisition unit 102c acquires a predetermined number of days from the specified base date as the scheduled payment date. For example, if the specified base date is "2023/5/30" and the predetermined number of days is "10", the scheduled payment date acquisition unit 102c acquires "2023/5/30 - 2023/6/8" as the scheduled payment dates.

If the specified claim number and the specified base date are those specified on an inquiry screen (see the inquiry screens in Figures 7 and 8) that allows inquiry of the billing amount by expected payment date, the expected payment date acquisition unit 102c acquires the expected payment date as follows. Note that the person operating the inquiry screen is, for example, a person in charge at the financial business who receives an inquiry from the debtor.

In other words, if the display method code (initial value) in the billing amount inquiry control master 106d is "1: Display the number of items 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 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 displayed is "10," the expected payment date acquisition unit 102c acquires "2023/5/30 - 2023/6/8" as the expected payment dates.

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 payment date acquisition unit 102c acquires 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 as the expected payment dates. For example, if the specified base date is "2023/6/2" and the number of items displayed is "3," the expected payment date acquisition unit 102c acquires "2023/6/2," "2023/5/30-2023/6/1," and "2023/6/3-2023/6/5" as expected payment dates.

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

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, for example, by the formula "scheduled collection amount x late payment charge interest rate x number of days overdue / number of days per year". However, the calculation is not limited to this formula.

The dunning data generation unit 102e generates dunning data 106e including the billing amount for each scheduled payment date calculated by the billing amount calculation unit 102d.

The reminder output unit 102f outputs a reminder (see Figure 6) on which the contents of the reminder data 106e are printed.

The inquiry screen display unit 102g displays an inquiry screen (see the inquiry screens in Figures 7 and 8) that includes the billing amount for each scheduled payment date calculated by the billing amount calculation unit 102d.

3. Specific examples of processing
In this section, a specific example of the process according to this embodiment will be described. In [3-1], the generation of a demand letter will be described, and in [3-2], the inquiry of the invoice amount will be described. The generation of the demand letter and the inquiry of the invoice amount will be performed by a person in charge of the financial business (hereinafter, sometimes simply referred to as "person in charge").

In this section [3. Specific examples of processing], we will proceed on the assumption that the collection schedule data 106a is preset as shown in FIG. 2, and the contract data 106c and billing amount inquiry control master 106d are preset as shown in FIG. 3.

[3-1. Generation of reminder letters]
First, the person in charge inputs the information required to generate a reminder letter from the output instruction screen shown in FIG. 5. Specifically, the date on which the reminder letter is expected to arrive at the debtor (= notification date) is input as the billing date. In the example of FIG. 5, "5/30/2023" is input as the billing date. In addition, in the <range specification> section, the person in charge of reminder, the claim number, and the number of months overdue are input. In the example of FIG. 5, "1000-1001" is input as the claim number. Once the information input from <range specification> is completed, a list of claims to be output is displayed by combination of claim number and customer name, as shown in the lower part of FIG. 5.

When the necessary information is entered on the output instruction screen shown in Figure 5 and the output button is pressed, a reminder letter will be generated as follows.

First, the collection information acquisition unit 102a acquires a record with collection SEQ = 4 from the collection schedule data 106a in FIG. 2 as a record that has the specified claim number "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.

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 results data 106b that has the claim number and collection SEQ in the record. If the conditions described in the previous paragraph are specified, the collection information acquisition unit 102a will acquire the planned collection amount of 10,000 yen, the principal of 7,000 yen, the interest of 3,000 yen, and the fee of 0 yen.
(conditions)
(i) Have a designated claim number.
(ii) The scheduled collection date in the collection schedule data 106a is equal to or greater than the designated billing date (date of payment).
(iii) The completion flag in the collection schedule data 106a is 0 (collection incomplete).

Next, the late payment loss interest rate acquisition unit 102b acquires "0.14600" from the contract data 106c in FIG. 3 as the late payment loss interest rate associated with the specified claim number "1000."

Next, the expected payment date acquisition unit 102c acquires the expected payment dates for 10 days (2023/5/30 to 2023/6/8) from the specified billing date "2023/5/30".

Next, the billing amount calculation unit 102d calculates the billing amount for each scheduled payment date by adding the late payment charge to the acquired scheduled collection amount "10,000 yen". The billing amount calculation unit 102d calculates the late payment charge for each scheduled payment date using the formula "(the acquired scheduled collection amount 10,000 yen) x (the acquired late payment charge interest rate 0.14600) x (the number of days of overdue, which is the number of days from the acquired scheduled collection date 2023/5/26 to the acquired scheduled payment dates 2023/5/30 to 2023/6/8) ÷ (365 days per year)". The specific formula is 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 x 0.14600 x 9 ÷ 365 = 36 yen 6/5: 10,000 x 0.14600 x 10 ÷ 365 = 40 yen 6/6: 10,000 x 0.14600 x 11 ÷ 365 = 44 yen 6/7: 10,000 x 0.14600 x 12 ÷ 365 = 48 yen 6/8: 10,000 x 0.14600 x 13 ÷ 365 = 52 yen

Next, the dunning data generation unit 102e generates dunning data 106e including the billing amount for each scheduled payment date calculated by the billing amount calculation unit 102d.

Finally, the reminder output unit 102f outputs the reminder shown in FIG. 6 on which the contents of the reminder data 106e (= the billing amount by expected payment date) are printed. In the reminder shown in FIG. 6, "May 29, 2023" in the upper right corner indicates the output date (processing date).

As explained above in section [3-1], the billing amount calculation device 100 for each scheduled payment date according to this embodiment allows the debtor to check the billing amount for each scheduled payment date at a glance by referring to the reminder letter on which the billing amount for each scheduled payment date is printed, and to pay the appropriate amount. This prevents financial businesses from having to forego profits by eliminating shortfalls in payments, and also reduces the administrative burden on financial businesses associated with returning excess payments by eliminating excess payments.

[3-2. Inquiry of billing amount]
First, the person in charge inputs the necessary information on the inquiry screen for making a claim 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 before and after specified date" is selected as the display method.

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

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

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 fee.

Here, we will explain the display control of the inquiry screen based on the settings of the billing inquiry control master 106d in Figure 3.

The default display method is displayed according to the setting of the display method code (default value) in the billing 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 "Display after the specified date" item = ON (checked) is displayed as the default, as shown in the inquiry screen of 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 "Display before and after the specified date" item = ON (checked) is displayed as the default, as shown in the inquiry screen of Figure 8.

The input of "Display from specified date onwards" or "Display around specified date" can also be controlled by setting the display method changeable flag in the billing amount inquiry control master 106d. Specifically, when the display method changeable flag is set to "true", "Display from specified date onwards" or "Display around specified date" can be changed from the initial value. In contrast, when the display method changeable flag is set to "false", "Display from specified date onwards" or "Display around specified date" cannot be changed from the initial value (the "Display from specified date onwards" or "Display around specified date" items themselves can be hidden).

The initial 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 the number of items to be displayed itself can be hidden).

Once you have completed entering the necessary information on the inquiry screens shown in Figures 7 and 8, the results of the claim inquiry will be displayed as follows:

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 in [3-1], and acquires the planned collection date "2023/5/26" and the planned collection amount "10,000 yen" from the acquired record with collection SEQ = 4.

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

Next, the expected deposit date acquisition unit 102c acquires multiple expected deposit dates based on the specified deposit date. However, the acquisition method differs depending on the specified display method ("display after specified date" or "display before and after specified date"), so each case will be explained separately below.

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

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

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 manner as in [3-1]. The method of calculating the billing amount is the same as in [3-1], so a detailed explanation is omitted.

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

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

In addition, the billing amount calculation device 100 according to this embodiment can set the display method according to the user's operation (inquiry work) and the debtor's requests based on the product characteristics. 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 amount before and after that date.

In this section [3-2], we have explained the inquiry screen when a financial institution's staff member makes a credit inquiry, but the inquiry screen when a debtor himself makes a debt inquiry on a member site (website) may have a similar screen configuration.

[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 making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

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 a known method.

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

In addition, with regard to the billing amount calculation device 100 by estimated payment date, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the billing calculation device 100 for scheduled deposit dates, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the billing calculation device 100 as necessary. 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 give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the billing amount calculation device 100 by estimated payment date via any network, and all or part of it may be downloaded as needed.

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

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., 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.

The billing amount calculation device 100 for each scheduled payment date may be configured as a known information processing device such as a personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The billing amount calculation device 100 for each scheduled payment date may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful in industries that handle financial receivables, and is particularly useful for financial institutions, non-banks, banks, credit companies, and money lenders.

100 Expected payment date billing amount calculation device 102 Control unit
102a Collection information acquisition unit
102b Late damage interest rate acquisition unit
102c Scheduled deposit date acquisition unit
102d Billing amount calculation section
102e Dunning data generation unit
102f Demand letter output section
102g Inquiry screen display unit 104 Communication interface unit 106 Storage unit
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 unit 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

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 the 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: 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
a dunning data generating means for generating the dunning data including the billing amount for each scheduled payment date calculated by the billing amount calculating means;
2. The device for calculating a billing amount by estimated payment date according to claim 1. The control unit is
a dunning notice output means for outputting a dunning notice on which the contents of the dunning data are printed;
3. The device for calculating a billing amount by estimated payment date according to claim 2. 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
further comprising 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;
2. The device for calculating a billing amount by estimated payment date according to claim 1. 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. 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. 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