Billed amount processing device, billed amount processing method, and billed amount processing program

Abstract

To provide a billed amount processing device, a billed amount processing method, and a billed amount processing program capable of preventing the occurrence of the increasing situation of a monthly repayment amount even if the date for determining the billed amount is the same as the date of a withdrawal request in a credit limit-type financing agreement.SOLUTION: A billed amount processing device of the present embodiment comprises a first master with a registered basic date and billed amount calculation means, where the billed amount calculation means calculates the basic date using the basic date of (basic date=target year and month - one month + the basic date of the first master), extracts the records from transaction history data on the condition (transaction content={finance} and transaction date≤the calculated basic date), acquires the final transaction loan balance on the date the same as the transaction date of the extracted record, and calculates the monthly repayment amount based on the acquired loan balance.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] For example, in a maximum loan contract (a sliding revolving loan with a balance at the time of borrowing), the monthly repayment amount is determined according to the loan balance at the time of final borrowing. Conventionally, a system relating to a sliding revolving loan is disclosed in, for example, Patent Document 1. [Prior art documents] [Patent documents]

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

[0004] However, in extreme loan contracts, the monthly repayment amount is determined based on the loan balance at the time of the final borrowing. However, if the date for determining the invoice amount is the same as the date of the debit request, there is a problem in that depending on the order in which the deposit transaction and the loan transaction are processed, the monthly repayment amount may increase (a situation that is unfavorable to the customer).

[0005] The present invention has been made in consideration of the above, and aims to provide a billing amount processing device, a billing amount processing method, and a billing amount processing program that can prevent a situation in which the monthly repayment amount increases in an extreme loan contract even if the date for determining the billing amount is the same as the date of the debit request. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a billing amount processing device equipped with a control unit for calculating the billing amount for an extreme loan contract, wherein the control unit is configured to be able to access a first master in which a reference date is registered, customer identification information, a transaction SEQ, the transaction date, transaction details specifying a comprehensive contract, cancellation, loan, or deposit, and transaction history data including the loan amount, deposit amount, and loan balance, and is characterized by having a billing amount calculation means for calculating the reference date as follows: reference date = target year and month - 1 month + reference date of the first master; extracting records from the transaction history data under the condition that transaction details = "loan" and transaction date ≦ calculated reference date; obtaining the loan balance of the final transaction on the same day as the transaction date of the extracted record; and performing a billing amount determination process to calculate the monthly repayment amount based on the obtained loan balance.

[0007] According to another aspect of the present invention, the control unit is further configured to be able to access a second master in which the loan balance and the monthly repayment amount are registered in association with each other, and in the billing amount determination process, the monthly repayment amount may be obtained from the second master using the obtained loan balance as a key.

[0008] According to another aspect of the present invention, the operator may be able to arbitrarily set the date on which the billing amount determination process is to be carried out.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a billing amount processing method executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a first master in which a reference date is registered, customer identification information, a transaction SEQ, the transaction date, transaction details specifying a comprehensive contract, cancellation, loan, or deposit, and transaction history data including the loan amount, the deposit amount, and the loan balance, and is characterized by including the steps of: calculating the reference date as the reference date = target year and month - 1 month + the reference date of the first master; extracting records from the transaction history data under the conditions that transaction details = "loan" and the transaction date ≦ the calculated reference date; obtaining the loan balance of the final transaction on the same day as the transaction date of the extracted record; and performing a billing amount determination process to calculate the monthly repayment amount based on the obtained loan balance.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a billing amount processing program to be executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a first master in which a reference date is registered, customer identification information, a transaction SEQ, the transaction date, transaction details specifying a comprehensive contract, cancellation, loan, or deposit, and transaction history data including the loan amount, the deposit amount, and the loan balance, and is characterized in that the billing amount processing program causes the control unit to execute the steps of: calculating the reference date as the reference date = target year and month - 1 month + the reference date of the first master; extracting records from the transaction history data where the transaction details = "loan" and the transaction date ≦ the calculated reference date; obtaining the loan balance of the final transaction on the same day as the transaction date of the extracted record; and calculating the monthly repayment amount based on the obtained loan balance. [Effects of the Invention]

[0011] According to the present invention, in a maximum loan contract, even if the date for determining the billing amount is the same as the date of the debit billing, it is possible to prevent the occurrence of a situation in which the monthly repayment amount increases. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram for explaining a case of a transaction that is disadvantageous to the customer (increasing the monthly repayment amount). [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the billing processing device according to this embodiment. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of the monthly repayment amount setting master. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of the billing amount determination processing management master. [Figure 5] FIG. 5 is a diagram illustrating an example of the structure of contract data. [Figure 6] FIG. 6 is a diagram showing an example of the structure of transaction history data. [Figure 7]FIG. 7 is a diagram showing an example of the configuration of transaction data (latest). [Figure 8] FIG. 8 is a diagram showing an example of the configuration of billing amount data. [Figure 9] FIG. 9 is a flowchart illustrating an outline of the processing performed by the billing amount calculation unit of the billing amount processing device according to this embodiment. [Figure 10] FIG. 10 is a flowchart illustrating the details of the processing performed by the billing amount calculation unit of the billing amount processing device according to this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the billing amount calculation unit of the billing amount processing device in this embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the billing amount calculation unit of the billing amount processing device in this embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the processing of the billing amount calculation unit of the billing amount processing device in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0014] [1. Overview] The outline of the present invention will be explained in the order of [1-1. Problem], [1-2. Solution], and [1-3. Effects].

[0015] [1-1. Issues] In extreme loan contracts (sliding revolving loans with the balance at the time of borrowing), the monthly repayment amount is determined based on the loan balance at the time of the final borrowing. Moneylenders that outsource the collection of debit requests to a subcontractor cannot check the results of the debit requests in real time, but receive the results from the subcontractor the day after the debit request and process the deposit transaction.

[0016] In this way, in extreme loan contracts (sliding revolving loans based on the balance at the time of borrowing), the monthly repayment amount is determined based on the loan balance at the time of the final borrowing.However, if the date for determining the billing amount is the same as the date of the debit request, there is a problem that the customer may be disadvantaged (the monthly repayment amount may increase) depending on the order in which the deposit transaction and the loan transaction are processed.

[0017] Figure 1 is a diagram to explain a case of a transaction that is disadvantageous to the customer (increasing the monthly repayment amount). The monthly repayment amount varies depending on whether the processing of the deposit transaction on the day is carried out before or after the final loan. Here, we will explain the case where the loan balance before the transaction on November 20, 2023 is "242,674" as an example.

[0018] Figure 1(A) shows an example of a transaction on 2023 / 11 / 20 being processed in the order of (1) deposit and (2) loan. (1) "50,000" is deposited to AM, and (2) "100,000" is loaned to PM, so the post-transaction balance (final loan balance at the time of final borrowing) is "293,927," and the monthly repayment amount is "11,000" according to the monthly repayment amount setting master.

[0019] Figure 1(B) shows an example where the transaction on 2023 / 11 / 20 is processed in the order of (1) loan and (2) deposit. (1) "100,000" is loaned to AM, and (2) "50,000" is deposited to PM, so the post-transaction balance (final loan balance at the time of final borrowing) is "342,674", and the monthly repayment amount is "12,000" according to the monthly repayment amount setting master.

[0020] [1-2. Solution] In this invention, by incorporating the concept of the base date, it is possible to carry out the invoice amount determination process after all transactions for that day have been processed. Also, in this invention, if a deposit transaction occurs on the day the final loan is made, the repayment amount is calculated based on the loan balance after all transactions have been made, preventing the above-mentioned customer disadvantage from occurring. Specifically, this invention is equipped with the following two functions.

[0021] (1) Function to set the base date for determining the billing amount By setting a base date for determining the billing amount, it becomes possible to determine the billing amount as of the base date on or after the day following the base date. (2) Function to consider deposit transactions on the reference date for determining the invoice amount If a loan transaction occurs on the reference date, the amount to be claimed can be determined based on the loan balance at the EOD (End Of Day) of the reference date.

[0022] [1-3.Effects] According to the present invention, customers can calculate the repayment amount from the balance taking into account the same-day deposit (which may result in a lower monthly repayment amount). Moneylenders can prevent complaints from customers. Furthermore, according to the present invention, it is possible to arbitrarily determine the date for the operation of the billing amount determination process (improving operational flexibility).

[0023] The present invention can be widely used in the financial industry, including banking and non-banking.

[0024] [2. Configuration] FIG. 2 is a block diagram showing an example of the configuration of a billing processing device 100 according to this embodiment. The billing processing device 100 according to this embodiment can be suitably used, for example, in financial institutions that provide short-term loans. The billing processing device 100 is, for example, a commercially available desktop personal computer. Note that the billing processing device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers.

[0025] 2, the billing processing device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the billing processing device 100 is connected to each other so that they can communicate with each other via any communication path.

[0026] The communication interface unit 104 communicatively connects the bill processing device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has the function of communicating data with other devices via the communication line. Here, the network 300 has the function of communicatively connecting the bill processing device 100 with a customer terminal (not shown) and a server 200, and is, for example, the Internet or a LAN (Local Area Network). The customer terminal (not shown) is, for example, a smartphone, mobile phone, tablet, PC, etc.

[0027] 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 functions as a pointing device in cooperation with a mouse. Note that hereinafter, the output device 114 may be referred to as the monitor 114.

[0028] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0029] The storage unit 106 stores various data such as a monthly repayment amount setting master 106a (second master), a billing amount determination processing management master 106b (first master), contract data, transaction history data, transaction data (latest), billing amount data, etc. Figure 3 is a diagram showing an example of the configuration of the monthly repayment amount setting master 106a. Figure 4 is a diagram showing an example of the configuration of the billing amount determination processing management master 106b. Figure 5 is a diagram showing an example of the configuration of contract data. Figure 6 is a diagram showing an example of the configuration of transaction history data. Figure 7 is a diagram showing an example of the configuration of transaction data (latest). Figure 8 is a diagram showing an example of the configuration of billing amount data. In Figures 3 to 8, "★" indicates a key item.

[0030] The monthly repayment amount setting master 106a can be configured as a table or the like in which loan balances and monthly repayment amounts are registered in association with each other, as shown in FIG. In the example shown in the figure, when the loan balance is "0 (or greater) to 100,000," the monthly repayment amount is "4,000," when the loan balance is "100,000 (or greater) to 200,000," the monthly repayment amount is "8,000," when the loan balance is "200,000 (or greater) to 300,000," the monthly repayment amount is "11,000," when the loan balance is "300,000 (or greater) to 400,000," the monthly repayment amount is "12,000," when the loan balance is "400,000 (or greater) to 500,000," the monthly repayment amount is "14,000," when the loan balance is "500,000 (or greater) to 600,000," the monthly repayment amount is "16,000," etc.

[0031] The invoice amount determination processing management master 106b can be configured as a table or the like that associates and registers the management key, execution flag, agreement date, current target year and month, current billing date, previous target year and month, previous billing date, and base date, as shown in Figure 4. In the example shown in the figure, the management key is "1," execution flag is "0," agreement date is "7," current target year and month is "2023 / 11," current billing date is "2023 / 11 / 07," previous target year and month is "2023 / 10," previous billing date is "2023 / 10 / 09," and base date is "20."

[0032] The contract data may include customer identification information (customer number, branch number), contract date, cancellation date, credit limit, loan interest rate, late interest rate, and monthly repayment amount, as shown in Figure 5. The "monthly repayment amount" is updated when the billing amount determination process is executed, and is updated to the monthly repayment amount calculated in the billing amount determination process.

[0033] In the example shown in the same figure, the second line contains the customer number "1000001," branch number "1," contract date "2023 / 09 / 01," cancellation date "NULL," maximum amount "500,000," credit limit "500,000," loan interest rate "14.50000," late interest rate "18.00000," and monthly repayment amount "12,000."

[0034] As shown in Figure 6, the transaction history data may include customer identification information (customer number, branch number), transaction SEQ, transaction details (transaction details (e.g., comprehensive contract, cancellation, loan, or deposit), transaction date), loan / deposit amount (loan amount, deposit amount), allocation information (applied principal, applied interest, applied late fees), carryover information (carried over interest, carried over late fees, carried over deposit), and post-transaction information (interest settlement date, late fee settlement date, next scheduled date, loan balance).

[0035] In the example shown in the same figure, the 7th line contains the customer number "1000001", branch number "1", transaction sequence number "6", transaction content "deposit", transaction date "2023 / 11 / 20", deposit amount "50,000", allocated principal amount "48,747", allocated interest amount "1,253", carried over interest amount "0", carried over late fee "0", carried over deposit amount "0", interest settlement date "2023 / 11 / 20", next scheduled date "2023 / 12 / 7", and loan balance "293,927".

[0036] As shown in FIG. 7, the transaction data (latest) holds the latest transaction history data for each customer number and branch number.

[0037] The billing amount data may include the customer number, branch number, billing date, and billing amount, as shown in Figure 8. In the example shown in the figure, the first line contains the customer number "1000001," the branch number "1," the billing date "2023 / 11 / 07," and the increased amount "11,000."

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

[0039] The control unit 102 is configured to be able to access the monthly repayment amount setting master 106a, the billing amount determination processing management master 106b, the contract data, the transaction history data, the latest transaction data, the billing amount data, etc. stored in the memory unit 106. Note that the monthly repayment amount setting master 106a, the billing amount determination processing management master 106b, the contract data, the transaction history data, the latest transaction data, the billing amount data, etc. may be stored in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0040] The control unit 102 conceptually includes a registration unit 102a, a transaction processing unit 102b, a billing amount calculation unit 102c, a master maintenance unit 102d, and a screen display control unit 102e.

[0041] The registration unit 102a creates contract data in response to, for example, an operation by a person in charge on a contract input screen (not shown) displayed on the monitor 114, and stores the data in the storage unit 106. The registration unit 102a also updates the "monthly repayment amount" in the contract data when the billing amount determination process is executed, to the monthly repayment amount calculated in the billing amount determination process.

[0042] The transaction processing unit 102b creates and updates transaction history data every time there is a transaction with a customer (for example, a comprehensive contract, cancellation, loan, or deposit), and stores the data in the storage unit 106. The transaction processing unit 102b stores the latest data (record) of the transaction history data as transaction data in the storage unit 106 for each customer identification information (customer number, sub-number).

[0043] For example, in response to the operation of the person in charge on the billing amount determination processing screen (see Figure 11) displayed on the monitor 114, the billing amount calculation unit 102c calculates the base date for the specified target year and month as follows: base date = target year and month - 1 month + base date of the billing amount determination processing management master 106b; extracts records from the transaction history data where the transaction content = "loan" and the transaction date is equal to or less than the calculated base date; obtains the loan balance of the final transaction on the same day as the transaction date of the extracted record; performs billing amount determination processing to calculate the monthly repayment amount based on the obtained loan balance; creates billing amount data for the calculated monthly repayment amount; and stores it in the memory unit 106.

[0044] In the billing amount determination process, the monthly repayment amount may be obtained from the billing amount determination process management master 106b using the acquired loan balance as a key. Also, the operator (person in charge) may be able to arbitrarily set the execution date of the billing amount determination process.

[0045] The master maintenance unit 102d performs settings such as inputting, adding, changing, and updating data in the monthly repayment amount setting master 106a and the billing amount determination processing management master 106b, for example, in response to operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

[0046] The screen display control unit 102e controls the display of various screens (for example, a contract input screen, a billing amount determination processing screen, a master maintenance screen, etc.) displayed on the monitor 114 and the reception of inputs.

[0047] [3. Specific Examples] 1 to 13, a specific example of the processing of the control unit 102 of the billing processing device 100 in this embodiment will be described. The following specific example will be described using the master and data configuration examples of FIGS. 3 to 8.

[0048] [3-1. Invoice amount determination process] Fig. 9 is a diagram showing a flow for explaining an outline of the billing amount determination process executed by the billing amount calculation unit 102c of the billing amount processing device 100 in this embodiment. With reference to Fig. 9, an outline of the billing amount determination process executed by the billing amount calculation unit 102c of the billing amount processing device 100 in this embodiment will be explained.

[0049] In Figure 9, the billing amount calculation unit 102c acquires the target (step S1). Specifically, when the current target year and month are specified by the person in charge on the billing amount determination processing screen (see Figure 11), the current billing date is calculated as follows: current billing date = current target year and month specified on the billing amount determination processing screen + contract date (after determining the business day) in the billing amount determination processing management master 106b. The billing amount calculation unit 102c updates the current target year and month, current billing date, previous target year and month, and previous billing date in the billing amount determination processing management master 106b (see Figure 13(B)).

[0050] Next, the billing amount calculation unit 102c acquires the target data (contract data, transaction data (latest)) under the following conditions. Transaction data (latest) loan balance > fixed "0" And the next scheduled date of the transaction data (latest) is less than or equal to the current billing date And contract data cancellation date = NULL

[0051] The billing amount calculation unit 102c acquires the final loan transaction as of the reference date (step S2). Specifically, for the specified target year and month, the billing amount calculation unit 102c calculates the reference date as follows: Reference date = Target year and month - 1 month + Reference date of the billing amount determination process management master 106b, and extracts records from the transaction history data that satisfy the conditions: Transaction type = "Loan" and Transaction date ≤ Calculated reference date.

[0052] The billing amount calculation unit 102c determines the monthly repayment amount (step S3). Specifically, the billing amount calculation unit 102c obtains the loan balance of the final transaction on the same day as the transaction date of the record extracted in step S2, obtains the monthly repayment amount from the billing amount determination processing management master 106b using the obtained loan balance as a key, creates billing amount data for the obtained monthly repayment amount, and stores it in the storage unit 106. The billing amount calculation unit 102c may also send the created billing amount data to the customer's terminal.

[0053] [3-2. Sample data] A specific example of the billing amount determination process executed by the billing amount calculation unit 102c of the billing amount processing device 100 in this embodiment will be described with reference to Figures 10 to 13. Figure 10 is a diagram showing a flow for explaining the details of the billing amount determination process executed by the billing amount calculation unit 102c of the billing amount processing device 100 in this embodiment. Figures 11 to 13 are diagrams showing sample data for explaining a specific example of the billing amount determination process executed by the billing amount calculation unit 102c of the billing amount processing device 100 in this embodiment. A specific example of the billing amount determination process executed by the billing amount calculation unit 102c of the billing amount processing device 100 in this embodiment will be described with reference to Figures 10 to 13.

[0054] (S1: Target Acquisition) S1: Target Acquisition will be explained in detail. Figure 11 is a diagram showing an example of the billing amount determination processing screen. Figure 12(A) shows an example of billing amount data before updating, and Figure 12(B) shows an example of billing amount determination processing management master 106b before updating.

[0055] 11, the billing amount determination processing screen 400 includes an area for displaying the previous target year and month, a field for specifying the current target year and month, and an execute button. When the person in charge specifies the current target year and month and presses the execute button, the billing amount calculation unit 102c executes the billing amount determination processing for the specified current target year and month.

[0056] The example shown in the figure explains the case where the operation is performed on 2023 / 11 / 22 (after all transactions on 2023 / 11 / 20 have been performed). In this example, when the current target year and month "2023 / 12" is specified and the execute button is pressed, the billing amount calculation unit 102c executes the billing amount determination process for the current target year and month "2023 / 12". The operator can arbitrarily set the date for performing the billing amount determination process.

[0057] First, the current billing date is calculated as follows: current billing date = current target year and month specified on the billing amount determination processing screen + contract date (after determining the business day) in the billing amount determination processing management master 106b, and the current target year and month, current billing date, previous target year and month, and previous billing date in the billing amount determination processing management master 106b are updated (see Figure 13(B)).

[0058] In this example, the target year and month is specified as "2023 / 12", so the settlement date "7" is obtained from the invoice amount determination processing management master 106b and the invoice date "2023 / 12 / 07" is calculated ("2023 / 12 / 07" is a business day).

[0059] If the target year and month is "2023 / 10" this time, the settlement date in the billing amount determination processing management master 106b is "7", and "2023 / 10 / 07" is a Saturday, so the billing date will be shifted to the next business day, and will be "2023 / 10 / 09".

[0060] Next, the billing amount calculation unit 102c acquires the target data (contract data, transaction data (latest)) under the following conditions. Transaction data (latest) loan balance > fixed "0" And the next scheduled date of the transaction data (latest) is less than or equal to the current billing date And contract data cancellation date = NULL

[0061] In this example, the data in the second line of the transaction data (see Figure 7) that satisfies the above conditions (Customer Number "1000001", Branch Number "1", Transaction SEQ "6", Transaction Details "Deposit", Transaction Date "2023 / 11 / 20", Deposit Amount "50,000", Applied Principal "48,747", Applied Interest "1,253", Carried Over Interest "0", Carried Over Late Fee "0", Carried Over Deposit "0", Interest Settlement Date "2023 / 11 / 20" , next scheduled date "2023 / 12 / 7", loan balance "293,927") and the data from the second line of the contract data (customer number "1000001", branch number "1", contract date "2023 / 09 / 01", cancellation date "NULL", maximum amount "500,000", credit limit "500,000", loan interest rate "14.50000", late interest rate "18.00000", monthly repayment amount "12,000").

[0062] (S2: Obtain the final loan balance as of the reference date) S2: The final loan balance as of the reference date is acquired in detail. First, the reference date is calculated as follows: Reference date = current target year and month specified on the screen - 1 month + reference date (after business day determination) of the billing amount determination process management master 106b.

[0063] In this example, the target year and month is "2023 / 12", the base date "20" is obtained from the invoice amount determination processing management master 106b, and the base date "2023 / 11 / 20" is calculated. Note that if the target year and month is "2023 / 09" and the base date in the invoice amount determination processing management master 106b is "20", since "2023 / 08 / 20" is a Sunday, the date is shifted to the next business day, which is "2023 / 08 / 21".

[0064] Next, the billing amount calculation unit 102c obtains the latest financing transaction with a transaction date before the base date under the following conditions.

[0065] Transaction history data transaction content = "loan" And the transaction date of the transaction history data is less than or equal to the calculated base date

[0066] In this example, for the contract with customer number 1000001 and branch number 1 in the transaction history data, the record with transaction SEQ=5 is obtained (see Figure 6).

[0067] (S3: Determine monthly repayment amount) S3: Determining the monthly repayment amount will be explained in detail. The loan balance for the final transaction on the transaction date of the record obtained in S2 is obtained. In this example, for a contract with customer number: 1000001 and branch number: 1, the transaction date of the transaction obtained in S2 (transaction SEQ = 5) is "2023 / 11 / 20", so the loan balance after the final transaction on "2023 / 11 / 20" is "293,927" in SEQ = 6 (see Figure 6).

[0068] Using the acquired loan balance as a key, the monthly repayment amount is acquired from the invoice amount determination processing management master 106b, and invoice amount data for the acquired monthly repayment amount is created and stored in the memory unit 106. In this example, using the loan balance "293,927" as a key, the monthly repayment amount "11,000" is acquired from the invoice amount determination processing management master 106b. Invoice amount data for the acquired monthly repayment amount is created and stored in the memory unit 106.

[0069] FIG. 13(A) shows an example of billing amount data after updating, and FIG. 13(B) shows an example of billing amount determination processing management master 106b after updating.

[0070] In the conventional method, for a contract with customer number 1000001 and branch number 1, the monthly repayment amount is calculated based on the loan balance of 342,674, as shown in Figure 1(B), resulting in a monthly repayment amount of 12,000, which is unfavorable to the customer. In contrast, in this embodiment, as described above, the monthly repayment amount is 11,000, which does not result in a disadvantageous situation to the customer.

[0071] As explained above, according to this embodiment, there is provided the invoice amount determination processing management master 106b in which the base date is registered, and the invoice amount calculation unit 102c which performs the invoice amount determination processing, which calculates the base date as follows: base date = target year and month - 1 month + base date of the invoice amount determination processing management master 106b; extracts records from the transaction history data under the conditions that the transaction content = "loan" and the transaction date is equal to or less than the calculated base date; obtains the loan balance of the final transaction on the same day as the transaction date of the extracted record; and calculates the monthly repayment amount based on the obtained loan balance. Therefore, in extreme loan contracts, it is possible to prevent the occurrence of a situation in which the monthly repayment amount increases even if the date for determining the invoice amount is the same as the date of the debit request.

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

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

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

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

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

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

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

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

[0080] This computer program may also be stored in an application program server connected to the billing processing device 100 via any network, and all or part of it may be downloaded as needed.

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

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

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

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

[0085] 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. [Explanation of symbols]

[0086] 100 billing processing device 102 Control section 102a Registration Department 102b Transaction Processing Unit 102c Billing Amount Calculation Department 102d Master Maintenance Department 102e Screen display control unit 104 Communication interface unit 106 Storage section 106a Monthly repayment amount master 106b Invoice amount determination processing management master 108 Input / Output Interface Section 112 Input Device 114 Output Device 300 Network

Claims

1. A claim amount processing device for calculating a claim amount for an extreme loan contract, the device comprising: The control unit a first master in which a reference date is registered; Transaction history data including customer identification information, transaction SEQ, transaction date, transaction details specifying a comprehensive contract, cancellation, loan, or deposit, loan amount, deposit amount, and loan balance, It is configured to be accessible to A billing amount processing device characterized by having a billing amount calculation means that calculates a reference date as follows: reference date = target year and month - 1 month + reference date of the first master; extracts records from the transaction history data where the transaction content = "loan" and the transaction date is equal to or less than the calculated reference date; obtains the loan balance of the final transaction on the same day as the transaction date of the extracted record; and performs a billing amount determination process that calculates the monthly repayment amount based on the obtained loan balance.

2. The control unit further The system is configured to be able to access a second master in which loan balances and monthly repayment amounts are associated and registered, 2. The billing amount processing device according to claim 1, wherein in the billing amount determination process, the monthly repayment amount is obtained from the second master using the obtained loan balance as a key.

3. 3. The billing amount processing device according to claim 1, wherein an operator can arbitrarily set the date for carrying out the billing amount determination process.

4. A billing method executed by an information processing device having a control unit, The control unit a first master in which a reference date is registered; Transaction history data including customer identification information, transaction SEQ, transaction date, transaction details specifying a comprehensive contract, cancellation, loan, or deposit, loan amount, deposit amount, and loan balance, It is configured to be accessible to Executed in the control unit: A billing amount processing method characterized by including a step of calculating a reference date as follows: reference date = target year and month - 1 month + reference date of the first master; extracting records from the transaction history data where the transaction content = "loan" and the transaction date is equal to or less than the calculated reference date; obtaining the loan balance of the final transaction on the same day as the transaction date of the extracted record; and performing a billing amount determination process to calculate the monthly repayment amount based on the obtained loan balance.

5. A billing amount processing program to be executed by an information processing device having a control unit, The control unit a first master in which a reference date is registered; Transaction history data including customer identification information, transaction SEQ, transaction date, transaction details specifying a comprehensive contract, cancellation, loan, or deposit, loan amount, deposit amount, and loan balance, It is configured to be accessible to The control unit A billing amount processing program for executing a process of calculating a reference date as follows: reference date = target year and month - 1 month + reference date of the first master; extracting records from the transaction history data where the transaction content = "loan" and the transaction date is equal to or less than the calculated reference date; obtaining the loan balance of the final transaction on the same day as the transaction date of the extracted record; and calculating the monthly repayment amount based on the obtained loan balance.

Images