Billing amount processor, billing amount processing method, and billing amount processing program

Abstract

To provide a billing amount processor, a billing amount processing method, and a billing amount processing program capable of setting a monthly repayment sum on the customer side in an extreme-type loan contract, thereby shortening a repayment term and reducing a bad debt risk on the financing side.SOLUTION: A billing amount processor comprises: a monthly repayment sum setting mask in which an outstanding loan balance is associated with a monthly repayment sum and registered; a storage area for storing contract data including customer identification, the date of contract, the date of cancellation, an extreme amount, a credit limit, a credit frame, a loan interest rate, a delinquency interest rate, and the monthly repayment sum updated on the basis of the outstanding loan balance after loan transactions by referring to the monthly repayment sum setting mask, and monthly repayment sum change data which is set upon the customer's request and includes the customer identification and the monthly repayment sum after the change; and a billing amount calculation unit for comparing the monthly repayment sum in the contract data with the monthly repayment sum after the change in the monthly repayment sum change data for a target month and year and determining the higher amount as the billing amount.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, while a maximum loan contract allows customers to keep monthly repayments low, it also poses the challenge of higher interest payments due to the longer repayment period, while for moneylenders, it poses the challenge of a higher default risk due to the longer repayment period.

[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, in extreme loan contracts, allows the customer to set the monthly repayment amount, thereby shortening the repayment period while also reducing the lender's risk of default. [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 a maximum loan contract, wherein the control unit is configured to be able to access a memory area that stores: a monthly repayment amount setting master in which the loan balance and monthly repayment amount are registered in association with each other; contract data including the monthly repayment amount that is updated by referring to the monthly repayment amount setting master based on customer identification information, contract date, cancellation date, maximum amount, credit limit, loan interest rate, late interest rate, and the loan balance after the loan transaction; and monthly repayment amount change data including customer identification information and changed monthly repayment amount that is set at the request of the customer; and the device is equipped with a billing amount processing means that compares the monthly repayment amount in the contract data with the changed monthly repayment amount in the monthly repayment amount change data for a target year and month, and determines the higher amount as the billing amount.

[0007] According to one aspect of the present invention, the memory area further stores billing increase data including customer identification information, billing year and month, and increase amount, which is set at the request of the customer, and the billing amount processing means may obtain the increase amount from the billing increase data if the billing year and month matches the target year and month, and determine the billing amount as the amount obtained by adding the obtained increase amount to the determined billing amount.

[0008] In addition, according to one aspect of the present invention, the billing amount processing means may calculate the allocated principal of the determined billing amount, and if the calculated allocated principal exceeds the loan balance, may change the determined billing amount so that the principal allocated amount = the loan balance.

[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 memory area that stores: a monthly repayment amount setting master in which the loan balance and the monthly repayment amount are registered in association with each other; contract data including the monthly repayment amount that is updated by referring to the monthly repayment amount setting master based on customer identification information, contract date, cancellation date, maximum amount, credit limit, loan interest rate, late interest rate, and the loan balance after the loan transaction; and monthly repayment amount change data including customer identification information and the changed monthly repayment amount that is set at the request of the customer; and the billing amount processing step executed by the control unit is to compare the monthly repayment amount in the contract data with the changed monthly repayment amount in the monthly repayment amount change data for a target year and month, and determine the higher amount as the billing amount.

[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 memory area that stores: a monthly repayment amount setting master in which the loan balance and the monthly repayment amount are registered in association with each other; contract data including the monthly repayment amount that is updated by referring to the monthly repayment amount setting master based on customer identification information, contract date, cancellation date, maximum amount, credit limit, loan interest rate, late interest rate, and the loan balance after the loan transaction; and monthly repayment amount change data including customer identification information and the changed monthly repayment amount that is set at the request of the customer; and the billing amount processing program causes the control unit to execute a billing amount processing step that compares the monthly repayment amount in the contract data with the changed monthly repayment amount in the monthly repayment amount change data for a target year and month, and determines the higher amount as the billing amount. [Effects of the Invention]

[0011] According to the present invention, in a maximum loan contract, the customer can set the monthly repayment amount, thereby shortening the repayment period and reducing the risk of default on the lender's side. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a billing processing device according to this embodiment. [Figure 2] FIG. 2 is a diagram showing an example of the configuration of the monthly repayment amount setting master. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of the billing amount determination processing management master. [Figure 4] FIG. 4 is a diagram illustrating an example of the structure of contract data. [Figure 5] FIG. 5 is a diagram showing an example of the configuration of monthly repayment amount change data. [Figure 6] FIG. 6 is a diagram showing an example of the configuration of billing amount increase data. [Figure 7] FIG. 7 is a diagram showing an example of the structure of transaction history data. [Figure 8] FIG. 8 is a diagram showing an example of the configuration of transaction data (latest). [Figure 9] FIG. 9 is a diagram showing an example of the configuration of billing amount data. [Figure 10] FIG. 10 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 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. [Figure 14] FIG. 14 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] For example, in a maximum loan contract (sliding revolving loan with the balance at the time of borrowing), the monthly repayment amount is determined according to the loan balance at the time of final borrowing. With a maximum loan contract, customers can keep their monthly repayment amount low, but the longer repayment period comes with the issue of higher interest payments. On the other hand, for moneylenders, the longer repayment period comes with the issue of a higher risk of default.

[0016] [1-2. Solution] The present invention focuses on the fact that in conventional credit loan contracts, customers are not able to arbitrarily set the repayment amount. Therefore, in the credit loan contract, in addition to "determining the monthly repayment amount based on the loan balance at the time of final borrowing," the present invention allows customers to arbitrarily set the monthly repayment amount, thereby shortening the repayment period and reducing the risk of default.

[0017] Specifically, the present invention is configured to allow the monthly repayment amount to be set arbitrarily in response to the customer's request, and is equipped with the following functions.

[0018] (1) Customers can set their own monthly repayment amount (however, it must be greater than the repayment amount calculated based on the balance at the time of the last loan). (2) Customers can now freely set an increase in repayment amount on a monthly basis.

[0019] [1-3.Effects] According to the present invention, customers can make larger repayments when they have the financial means, reducing interest payments and shortening the repayment period. For money lenders, shortening the repayment period reduces the risk of default.

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

[0021] [2. Configuration] FIG. 1 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 credit-based 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. In FIG. 1, the billing processing device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The various units included in the billing processing device 100 are communicably connected via any communication path.

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

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

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

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

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

[0027] The invoice amount determination processing management master 106b can be configured as a table that associates and registers the management key, execution flag, agreement date, current target year and month, current billing date, previous target year and month, and previous billing date, as shown in Figure 3. 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," and previous billing date is "2023 / 10 / 09."

[0028] 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 4. The "monthly repayment amount" is updated when a loan transaction is executed, and is updated to the monthly repayment amount obtained from the monthly repayment amount setting master 106a based on the loan balance in the transaction history data of the loan transaction (after the borrowing transaction).

[0029] In the example shown in the 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." In this case of sliding revolving credit at the time of borrowing, the monthly repayment amount is reviewed at the time of the loan transaction (borrowing transaction). For example, this monthly repayment amount of "12,000" is calculated (updated) as follows: For customer number "1000001" and branch number "1," the sixth line (transaction SEQ5) of the transaction history data in Figure 7 is the most recent last borrowing (transaction content: loan), and the loan balance is "342,674." Therefore, using the loan balance "342,674" as a key, the monthly repayment amount "12,000" is obtained from the monthly repayment amount setting master 106a in Figure 2 and updated.

[0030] The monthly repayment amount change data may include the customer number, branch number, and changed monthly repayment amount, as shown in Figure 5. The "changed monthly repayment amount" can be set by the customer at their discretion. In the example shown in the figure, the first line contains the customer number "1000001," the branch number "1," and the changed monthly repayment amount "20,000."

[0031] As shown in Figure 6, the billing increase data may include the customer number, branch number, billing year and month, and increase amount. The "increase amount" can be set by the customer at their discretion. In the example shown in the figure, the first line contains the customer number "1000001," branch number "1," billing year and month "2023 / 12 / 07," and increase amount "50,000."

[0032] As shown in Figure 7, 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).

[0033] 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".

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

[0035] The billing amount data may include the customer number, branch number, billing date, and billing amount, as shown in Figure 9. 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."

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

[0037] 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, contract data, monthly repayment amount change data, billing amount increase data, transaction history data, transaction data (latest), 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, contract data, monthly repayment amount change data, billing amount increase data, transaction history data, transaction data (latest), billing amount data, etc. may also be stored in another location (for example, server 200) as long as the control unit 102 is able to access them.

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

[0039] The registration unit 102a creates contract data in response to, for example, operations performed by the 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 updates the "monthly repayment amount" in the contract data when a loan transaction is executed, and more specifically, updates the "monthly repayment amount" to the monthly repayment amount obtained from the monthly repayment amount setting master 106a based on the loan balance in the transaction history data after the loan transaction.

[0040] The optional setting unit 102b creates monthly repayment amount change data in response to instructions from the customer and stores it in the storage unit 106. Specifically, for example, the optional setting unit 102b may create the monthly repayment amount change data in response to the monthly repayment amount set by the customer on the customer's terminal, or may create the monthly repayment amount change data in response to an operation by a staff member who receives instructions from the customer to set the monthly repayment amount (for example, instructions by phone, email, etc.). In this way, the customer can set (change) the monthly repayment amount as they like.

[0041] In addition, the optional setting unit 102b creates billing amount increase data in response to instructions from the customer and stores it in the storage unit 106. Specifically, for example, the optional setting unit 102b may create the billing amount increase data in response to an increase amount set by the customer on the customer's terminal, or may create the billing amount increase data in response to an operation by a staff member who receives an instruction from the customer to set the increase amount (for example, an instruction by telephone, email, etc.). In this way, the customer can set the increase amount as they wish.

[0042] The transaction processing unit 102c 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 102c stores the latest data (record) of the transaction history data for each customer identification information (customer number, sub-number) in the storage unit 106 as transaction data (latest).

[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 102d compares the monthly repayment amount in the contract data with the changed monthly repayment amount in the monthly repayment amount change data for the specified target year and month, determines the higher amount as the billing amount, creates billing amount data for the determined billing amount, and stores it in the memory unit 106.

[0044] In this case, the billing amount calculation unit 102d may obtain the increased amount from the billing amount increase data if the billing year and month matches the target year and month, and determine the billing amount as the amount obtained by adding the obtained increased amount to the determined billing amount.

[0045] In addition, the billing amount calculation unit 102d may calculate the allocated principal of the determined billing amount, and if the calculated allocated principal exceeds the loan balance, may change the determined billing amount so that the principal allocated amount = the loan balance.

[0046] The master maintenance unit 102e 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.

[0047] The screen display control unit 102f 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.

[0048] [3. Specific Examples] 1 to 14, 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. 2 to 9.

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

[0050] In Figure 10, the billing amount calculation unit 102d 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 whether it is a business day) in the billing amount determination processing management master 106b. The billing amount calculation unit 102d 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 14(B)).

[0051] Next, the billing amount calculation unit 102d 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

[0052] Next, the billing amount calculation unit 102d determines the monthly repayment amount to be used (step S2). Specifically, the billing amount calculation unit 102d compares the monthly repayment amount in the contract data with the monthly repayment amount after the change based on the monthly repayment amount change data, and adopts the higher amount. Specifically, if the billing amount = the monthly repayment amount in the contract data ≥ the monthly repayment amount after the change based on the monthly repayment amount change data, the monthly repayment amount in the contract data is adopted. Otherwise, the monthly repayment amount after the change based on the monthly repayment amount change data is adopted.

[0053] The billing amount calculation unit 102d adds the increased amount (step S3). If there is no billing amount increase data, the process is skipped. Specifically, the billing year and month in the billing amount increase data is referenced, and the increased amount is added to the billing amount calculated in step S2, resulting in the calculation: billing amount = billing amount in step S2 + increased amount of billing amount increase data.

[0054] The billing amount calculation unit 102d checks whether the billing amount exceeds the amount due (step S4). Specifically, it calculates the allocation breakdown (appropriated principal, appropriated interest, and appropriated late fees) of the billing amount calculated up to step S3, and verifies whether the appropriated principal exceeds the loan balance in the transaction data (latest). If the verification shows that the amount does not exceed the amount due, it leaves the billing amount as is. If the amount does exceed the loan balance, it changes the billing amount by setting the amount appropriated to the principal = the loan balance, and creates billing amount data (see Figure 14(A)). Billing amount = appropriated principal + appropriated interest + appropriated late fees. The order of allocation is appropriated: appropriated late fees < appropriated interest < appropriated principal. For example, the billing amount calculation unit 102d sends the created billing amount data to the customer's terminal.

[0055] Applied interest = Loan balance x Loan interest rate x Number of days elapsed / 365 (or 366) + Carryover interest. However, the number of days elapsed = the number of days between the interest settlement date and the billing date.

[0056] Appropriated late fees = Loan balance x Late interest rate - Loan interest rate x Late days / 365 (or 366) + Carryover late fees. However, Late days = Late fee settlement date (NULL) or the number of days between the next scheduled date and the billing date.

[0057] [3-2. Sample Data] Figures 11 to 14 are diagrams showing sample data for explaining a specific example of the billing amount determination process executed by the billing amount calculation unit 102d 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 102d of the billing amount processing device 100 in this embodiment will be explained with reference to Figures 11 to 14.

[0058] (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.

[0059] 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 102d executes the billing amount determination processing for the specified current target year and month.

[0060] In the example shown in the figure, when the current target year and month "2023 / 12" is specified and the execute button is pressed, the billing amount calculation unit 102d executes the billing amount determination process for the current target year and month "2023 / 12".

[0061] 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 14(B)).

[0062] 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).

[0063] 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".

[0064] Next, the billing amount calculation unit 102d 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

[0065] In this example, the data in the second line of the transaction data (see Figure 8) 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").

[0066] (S2: Decide the monthly repayment amount to be used) S2: A specific example of determining the monthly repayment amount to use will be explained. The monthly repayment amount in the contract data is compared with the monthly repayment amount after the change in the monthly repayment amount change data, and the higher amount is adopted. Specifically, if the billing amount = monthly repayment amount in the contract data ≥ monthly repayment amount after the change in the monthly repayment amount change data, the monthly repayment amount in the contract data is adopted. In all other cases, the monthly repayment amount after the change in the monthly repayment amount change data is adopted.

[0067] In this example (customer number: 1000001, branch number: 1), the monthly repayment amount in the contract data is 12,000, and the monthly repayment amount after change in the monthly repayment amount change data is 20,000, so the larger value of "20,000" is used.

[0068] (S3: Add the increased amount) S3: A specific example of adding the increased amount is explained. The increased amount is obtained where the billing year and month in the billing amount increase data matches the current target year and month specified on the billing amount determination processing screen, and the increased amount is added to the billing amount calculated in step S2, and the calculation is: Billing amount = billing amount in step S2 + increased amount in billing amount increase data. If there is no billing amount increase data, skip.

[0069] In this example (customer number: 1000001, branch number: 1), the increase amount in the billing increase data = 50,000, and the monthly repayment amount calculated in step S2 = 20,000, so the billing amount is calculated as "70,000 (= 50,000 + 20,000)".

[0070] (S4: Check for excess invoice amount) S4: A specific example of checking whether the invoice amount exceeds the limit is explained. The allocation breakdown (appropriated principal, appropriated interest, appropriated late payment fee) of the invoice amount calculated up to step S3 is calculated, and it is verified whether the appropriated principal exceeds the loan balance in the transaction data (latest). If the verification shows that it does not exceed the limit, the invoice amount is left as is, but if it does exceed the limit, the invoice amount is changed as principal allocation amount = loan balance, and invoice amount data is created. Invoice amount = appropriated principal + appropriated interest + appropriated late payment fee. The allocations are made in the following order: appropriated late payment fee < appropriated interest < appropriated principal.

[0071] In this example (customer number: 1000001, branch number: 1), the calculation results of the allocation breakdown (appropriated principal, allocated interest, and allocated late fees) of the billed amount "70,000" calculated up to step S3 are shown in Figure 13. Specifically, the calculations are as follows:

[0072] Applied interest = loan balance (293,927) x loan interest rate (14.50000%) x number of days elapsed (17 days) / 365 (366) + carried over interest (0) = 1,985. However, number of days elapsed = number of days from interest settlement date (2023 / 11 / 20) to billing date (2023 / 12 / 07) = 17 days.

[0073] Appropriated late fees = Loan balance (293,927) x Late interest rate (18.0000%) - Loan interest rate (14.50000%) x Number of days overdue (0 days) / 365 (366) + Carryover late fees (0) = 0. However, the number of days overdue = Late fee settlement date (NULL) OR the number of days from the next scheduled date (2023 / 12 / 07) to the billing date (2023 / 12 / 07) = 0.

[0074] Since the allocated principal = 68,015 (= invoice amount (70,000) - allocated interest (1,985) - allocated late fee (0)), and the loan balance in the transaction data (latest) = 293,927, the allocated principal does not exceed the loan balance in the transaction data (latest), so the invoice amount will remain at "70,000".

[0075] For example, if the loan balance in the latest transaction data is 30,000, the allocated principal exceeds the loan balance in the latest transaction data, so the principal allocated amount = loan balance, The amount claimed is 31,985. Specifically, the principal amount applied (30,000) + interest amount applied (1,985) + late payment charge applied (0) = amount claimed (31,985).

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

[0077] As described above, according to this embodiment, there is provided a monthly repayment amount setting master 106a in which the loan balance and the monthly repayment amount are registered in association with each other, and a billing amount calculation unit 102d which compares the monthly repayment amount in the contract data with the changed monthly repayment amount set in accordance with the customer's instructions in the monthly repayment amount change data, and determines the higher amount as the billing amount.Therefore, in extreme loan contracts, by having the customer set the monthly repayment amount, it is possible to shorten the repayment period while also reducing the risk of default on the lender's side.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0091] 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]

[0092] 100 billing processing device 102 Control section 102a Registration Department 102b Optional setting section 102c Transaction Processing Unit 102d Claims calculation section 102e Master Maintenance Department 102f 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 monthly repayment amount setting master in which the loan balance and the monthly repayment amount are associated and registered; Contract data including a monthly repayment amount that is updated by referring to the monthly repayment amount setting master based on customer identification information, contract date, cancellation date, credit limit, loan interest rate, late interest rate, and loan balance after the loan transaction; Monthly repayment amount change data including customer identification information and changed monthly repayment amount, which is set at the request of the customer; The storage area storing the A billing amount processing device characterized by having a billing amount processing means that compares the monthly repayment amount of the contract data with the monthly repayment amount after the change of the monthly repayment amount change data for the target year and month, and determines the higher amount as the billing amount.

2. The storage area further includes: The billing increase data, including customer identification information, billing year and month, and increase amount, set at the request of the customer, is stored. The billing amount processing device described in claim 1, characterized in that if the billing year and month match the target year and month from the billing amount increase data, the billing amount processing means obtains the increase amount and determines the billing amount as the amount obtained by adding the obtained increase amount to the determined billing amount.

3. The billing amount processing device according to claim 1 or 2, characterized in that the billing amount processing means calculates the allocated principal of the determined billing amount, and if the calculated allocated principal exceeds the loan balance, changes the determined billing amount so that the principal allocated amount = the loan balance.

4. A billing method executed by an information processing device having a control unit, The control unit A monthly repayment amount setting master in which the loan balance and the monthly repayment amount are associated and registered; Contract data including a monthly repayment amount that is updated by referring to the monthly repayment amount setting master based on customer identification information, contract date, cancellation date, credit limit, loan interest rate, late interest rate, and loan balance after the loan transaction; Monthly repayment amount change data including customer identification information and changed monthly repayment amount, which is set at the request of the customer; The storage area storing the Executed in the control unit: A billing amount processing method characterized by including a billing amount processing step for comparing the monthly repayment amount in the contract data with the monthly repayment amount after the change in the monthly repayment amount change data for the target year and month, and determining the higher amount as the billing amount.

5. A billing amount processing program to be executed by an information processing device having a control unit, The control unit A monthly repayment amount setting master in which the loan balance and the monthly repayment amount are associated and registered; Contract data including a monthly repayment amount that is updated by referring to the monthly repayment amount setting master based on customer identification information, contract date, cancellation date, credit limit, loan interest rate, late interest rate, and loan balance after the loan transaction; Monthly repayment amount change data including customer identification information and changed monthly repayment amount, which is set at the request of the customer; The storage area storing the The control unit A billing amount processing program for executing a billing amount processing step that compares the monthly repayment amount in the contract data with the monthly repayment amount after the change in the monthly repayment amount change data for the target year and month, and determines the higher amount as the billing amount.

Images