JP7723027B2 - Account transfer management device, account transfer management method, and account transfer management program - Google Patents

Description

The present invention relates to an account transfer management device, an account transfer management method, and an account transfer management program.

Account transfer management devices are known that reduce the risk of unpaid receivables for product sales and other payments at businesses, as well as the costs associated with requesting collection from collection agents (see, for example, Patent Document 1).

Japanese Patent Application Laid-Open No. 2022-079831

In account transfer management devices such as those described in Patent Document 1, account transfers are carried out in various ways depending on the nature of the products handled, the management methods used by each company, etc. Therefore, it may be necessary to customize the account transfer management device depending on, for example, the nature of the products and the management methods.

The present invention was made in consideration of the above-mentioned problems, and aims to provide an account transfer management device, an account transfer management method, and an account transfer management program that can flexibly adapt to the characteristics of products, operation methods, etc., without the need for customization.

To solve the above-mentioned problems and achieve the objectives, the account transfer management device of the present invention is an account transfer management device equipped with a control unit and a memory unit, wherein the memory unit stores optional setting data including information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data including information indicating for each bond whether the billing method is single-month billing or multiple-collection billing, the control unit determines whether the optional setting is invalid for each bond based on the optional setting data, and if it determines that the optional setting is invalid, determines whether the billing method is single-month billing or multiple-collection billing based on the billing method data, calculates the billing amount for each bond based on the billing method determination result, and sets the billing amount to the customer based on the calculation result.

The account transfer management method of the present invention is executed by an account transfer management device equipped with a control unit and a memory unit. The memory unit stores optional setting data including information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data including information indicating for each bond whether the billing method is single-month billing or multiple-collection billing. The control unit performs the following steps: determining whether the optional setting is invalid for each bond based on the optional setting data; if it is determined that the optional setting is invalid, determining whether the billing method is single-month billing or multiple-collection billing based on the billing method data; calculating the billing amount for each bond based on the billing method determination result; and setting the billing amount for the customer based on the calculation result.

The account transfer management program of the present invention is an account transfer management program executed by an account transfer management device equipped with a control unit and a memory unit. The memory unit stores optional setting data including information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data including information indicating for each bond whether the billing method is single-month billing or multiple-collection billing. The control unit executes the following processes: determining whether the optional setting is invalid for each bond based on the optional setting data; if it is determined that the optional setting is invalid, determining whether the billing method is single-month billing or multiple-collection billing based on the billing method data; calculating the billing amount for each bond based on the billing method determination result; and setting the billing amount for the customer based on the calculation result.

The present invention has the advantage of being able to flexibly adapt to the characteristics of products, operating methods, etc. without the need for customization.

FIG. 1 is a block diagram showing an example of an account transfer management device according to this embodiment. FIG. 2 is a flowchart showing an example of the flow of processing in the account transfer management device. FIG. 3 is a diagram illustrating an example of various masters stored in the storage unit. FIG. 4 is a diagram illustrating an example of data stored in the storage unit. FIG. 5 is a diagram showing an example of an operation screen in the account transfer management device. FIG. 6 is a diagram showing an example of collection schedule data and collection record data. FIG. 7 is a diagram showing an example of transaction history data. FIG. 8 is a diagram showing an example of an operation screen in the account transfer management device. FIG. 9 is a diagram showing an example of an operation screen in the account transfer management device. FIG. 10 is a diagram showing an example of the data flow in the process of generating account transfer request data and account transfer request customer total data. FIG. 11 is a diagram showing an example of a data flow in the process of generating an account transfer request file. FIG. 12 is a diagram showing an example of an operation screen in the account transfer management device.

Embodiments of an account transfer management device, an account transfer management method, and an account transfer management program according to the present invention are described in detail below with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[1. Configuration]
An example of the configuration of an account transfer management device according to this embodiment will be described with reference to the drawings. The account transfer management device according to this embodiment is used for debt collection operations in the financial industry and for debt collection operations by various businesses. In such debt management and debt collection operations, account transfers are carried out in various ways and for various amounts depending on the nature of the products handled and the operating methods of each company.
Fig. 1 is a block diagram showing an example of an account transfer management device 100 according to this embodiment. The account transfer management device 100 shown in Fig. 1 is constructed based on a commercially available desktop personal computer. Note that the account transfer management device 100 is not limited to devices constructed based on stationary information processing devices such as desktop personal computers, but may also be constructed based on portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

The account transfer management 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 account transfer management device 100 is connected to each other so that they can communicate with each other via any communication path.

The control unit 102 is a CPU (Central Processing Unit) or the like that provides overall control of the account transfer management device 100. The control unit 102 performs information processing based on various data stored in the storage unit 106. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and performs various information processing based on these stored programs. The specific processing content of the control unit 102 will be described later.

The communication interface unit 104 communicatively connects the account transfer management 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 a communication line. Here, the network 300 has the function of connecting the account transfer management device 100 and other devices so that they can communicate with each other, such as the Internet or a LAN (Local Area Network). The network 300 may also have the function of connecting the account transfer management device 100 and the server 200 so that they can communicate with each other. In this case, the data stored in the memory unit 106 may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in conjunction with a mouse. Note that, below, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

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

The memory unit 106 stores various master data, including the product master data 10, the account transfer entrusted party master data 11, the account transfer management master data 12, the collection method master data 13, and the account transfer billing method master data 14. The memory unit 106 also stores the following data: debt customer linking data 20, debt information data 21, customer bank account data 22, billing method data 23, collection schedule data 24, collection performance data 25, transaction history data 26, optional account transfer amount setting data 27, account transfer request data 28, and account transfer request customer total data 29. The memory unit 106 also stores an account transfer request file 30. The various master data, data, and files of the memory unit 106 will be explained in conjunction with the specific processing examples below.

2. Specific examples of processing
Next, a detailed description will be given of a specific example of the processing executed by the control unit 102 in the account transfer management device 100. Figure 2 is a flowchart showing an example of the flow of processing in the account transfer management device 100.

<Master settings (pre-settings)>
The control unit 102 sets various masters based on input from the input device 112 and stores them in the storage unit 106 (step S101).

Figure 3 is a diagram showing an example of various masters stored in the memory unit 106. As shown in Figure 3, the product master 10 is data showing product information. The product master 10 includes a product code indicating the product's identification number, a product name indicating the product's name, an account transfer contractor code indicating the identification number of the account transfer contractor, an account transfer deposit deduction flag indicating whether the deposit will be deducted from the account transfer billing amount when the account transfer is billed, and an account transfer billing method code indicating whether the account transfer billing method is a single-month billing or a combined billing. Here, the account transfer contractor code, account transfer deposit deduction flag, and account transfer billing method code are setting items for initial display when registering the billing method, which will be described later. Note that while the settings for each item are determined on a product-by-product basis, they can also be changed on a receivable-by-receivable basis.

The account transfer trustee master data 11 is data that associates the account transfer trustee code with the name of the account transfer trustor.

The account transfer management master 12 includes the account transfer entrusted party code mentioned above, the product contract date, and a billing unit code indicating whether the billing unit is for individual receivables or for the total customer.

The collection method master 13 is data that associates collection method codes with collection method names. In this embodiment, for example, the collection method name corresponding to collection method code 1 is set to account transfer, the collection method name corresponding to collection method code 2 is set to bank transfer, and the collection method name corresponding to collection method code 3 is set to deduction.

The direct debit billing method master 14 is data that associates the direct debit billing method code, which indicates the identification number of the direct debit billing method, with the name of the direct debit billing method. For direct debit billing method code 1, it is set to single-month billing. For direct debit billing method code 2, it is set to multiple collection billing.

<Application entry, billing method registration>
After registering the various master data, an application is made for a transaction that is subject to account transfer, such as a mortgage. In the application, the input device 112 is used to input, for example, the receivables that are the subject of account transfer management, the customer (debtor), the customer's bank account, etc. In the application, the control unit 102 generates receivable-customer linking data 20, receivable information data 21, and customer bank account data 22 based on the input from the input device 112, and stores them in the storage unit 106 (step S102).

Figure 4 is a diagram showing an example of data stored in the memory unit 106. Figure 4 shows credit customer linking data 20, credit information data 21, and customer bank account data 22. Figure 4 also shows the relationships between each piece of data using a simple ER diagram. In Figure 4, the primary key is indicated by PK, and the external reference key is indicated by FK.

As shown in Figure 4, the bond-customer linking data 20 manages linking information between bonds and customers (debtors). The bond-customer linking data 20 includes a bond number indicating the identification number of the bond and a customer number indicating the identification number of the customer.

The credit information data 21 manages credit information (such as product codes). The credit information data 21 includes a credit number indicating the identification number of the credit and a customer number indicating the identification number of the customer.

Customer bank account data 22 manages information about customer bank accounts. Customer bank account data 22 includes a customer number, a bank number indicating the bank's identification number, a viewpoint number indicating the bank's branch identification number, a deposit type indicating the deposit type, an account number indicating the customer's account number, and the account holder's name.

After entering the application information, the billing method is registered. Figure 5 shows an example of the operation screen of the account transfer management device 100. Note that Figure 5 shows the operation screen in association with data related to operations on that operation screen.

As shown in FIG. 5, when registering a billing method in the account transfer management device 100, the control unit 102 displays the operation screen F1 on the monitor 114. The operation screen F1 displays input fields for, for example, the claim number, collection method code, account transfer trustee code, account transfer deposit deduction flag, account transfer billing method code, etc. When a claim number is entered using the keyboard 112 or the like, the control unit 102 references various masters and automatically enters the collection method code, account transfer trustee code, account transfer deposit deduction flag, and account transfer billing method code corresponding to the claim number.

For example, the control unit 102 inputs the code value set in the collection method code master as the collection method code. If 1 (direct debit) is specified as the collection method code, the control unit 102 can set the direct debit entrusted party code, direct debit deposit deduction flag, and direct debit billing method code.

When registering a new billing method, the control unit 102 initially displays the account transfer entrusted party code in the product master 10. The control unit 102 then references the account transfer entrusted party master 11 and sets the account transfer entrusted party code.

In addition, when registering a new billing method, the control unit 102 sets the account transfer deposit deduction flag in the product master 10 to its initial display. If the deposit will be deducted, the control unit 102 checks the box ON (true), and if the deposit will not be deducted, the control unit 102 checks the box OFF (false).

Furthermore, when registering a new billing method, the control unit 102 initially displays the direct debit billing method code from the product master 10. The control unit 102 then references the direct debit billing method master 14 and sets the direct debit billing method code. The direct debit billing method code is set to 0 for single-month billing and 1 for multiple-payment billing. After the above items have been entered, if the register button on the operation screen F1 is selected with the mouse 112 or the like, the control unit 102 generates billing method data 23 based on the input items (step S103). Figure 5 shows an example of generating data from the billing method data 23 corresponding to bond number 1000000001. By performing the same process as above, data can be generated in the same way for bond numbers 1000000002 and onwards.

<Start of trading>
After the billing method is registered, a debt collection plan is set based on the contract with the customer, and the customer makes deposits by account transfer, etc., based on the collection plan. In this case, the control unit 102 generates collection schedule data 24 that manages the collection schedule based on the collection plan, and collection performance data 25 that manages the collection performance against the collection schedule (step S104). The control unit 102 also generates transaction history data 26 that manages the transaction history, such as execution, collection, and deposit recording (step S104).

Figure 6 is a diagram showing an example of collection schedule data 24 and collection performance data 25. Figure 7 is a diagram showing an example of transaction history data 26. Figure 7 uses a simple ER diagram to show the relationship between the collection schedule data 24, collection performance data 25, and transaction history data 26 and the debt-customer linking data 20. In Figure 7, the primary key is indicated by PK, and the external reference key is indicated by FK.

Note that the following examples, including Figures 6 and 7, show data as of February 1, 2023, and illustrate a case where loan agreements for bond numbers 1000000001 to 1000000012 were executed on December 15, 2022, the first scheduled repayment date is January 26, 2023, and the second scheduled repayment date is February 27, 2023.

As shown in Figure 6, the collection schedule data 24 includes various items corresponding to the debt number, such as the collection sequence (collection SEQ), collection sequence, collection month and year, collection date, collection amount, principal, interest, and fees. In the collection schedule data 24, values such as the collection month and year, collection date, collection amount, principal, interest, and fees are entered for each collection sequence.

Collection performance data 25 is set in accordance with the collection sequence of collection schedule data 24. The collection performance data 25 includes items such as the debt number, collection sequence, transaction sequence, collection date, and collection amount. If there is a collection record in the collection sequence, a value corresponding to the collection record is entered into each item of the collection performance data 25. A blank value for each item in the collection performance data 25 indicates an uncollected state.

For example, the collection performance data 25 shown in Figure 6 indicates that the amount corresponding to collection sequence 1 of claim number 1000000001 (January 2023), the amount corresponding to collection sequence 1 of claim number 1000000004 (January 2023), the amount corresponding to collection sequence 1 of claim number 1000000010 (January 2023), and the amount corresponding to collection sequence 1 of claim number 1000000012 (January 2023) are each uncollected.

As shown in Figure 7, the transaction history data 26 includes fields such as transaction sequence, transaction type code, transaction date, loan amount, recovery amount, and carried-over deposit. Transaction type codes are, for example, 1 for contract execution, 2 for recovery, and 3 for deposit recording. When a transaction occurs in a transaction sequence, a value corresponding to the transaction content is entered into each field of the transaction history data 26. A blank value for each field in the transaction history data 26 indicates that no transaction has occurred.

<Optional settings>
In the account transfer management device 100 according to this embodiment, the account transfer amount can be set (optionally set) at any time after the transaction has started. Figure 8 is a diagram showing an example of an operation screen in the account transfer management device 100. Note that Figure 8 shows the operation screen in association with data related to operations on the operation screen.

As shown in FIG. 8, when performing optional settings in the account transfer management device 100 (Yes in step S105), the control unit 102 displays the operation screen F2 on the monitor 114. The operation screen F2 displays input fields for, for example, the claim number, optional billing method code, specified year and month, calculation base date, and optional billing amount. The optional billing method code is set to 0 for the specified month only, and 1 for every month thereafter. The operation screen F2 also displays the billing amount as of the calculation base date. When the claim number, optional billing method code, specified year and month, and calculation base date are entered via the keyboard 112, etc., the control unit 102 refers to various masters and data to calculate the billing amount as of the calculation base date, and displays it on the operation screen F2. When the optional billing amount is entered and the register button is selected, the control unit 102 generates optional account transfer amount setting data 27 and stores it in the memory unit 106 (step S106). If no optional settings are to be made (No in step S105), the control unit 102 skips step S106.

<Account transfer request>
When performing an account transfer, the account transfer management device 100 generates account transfer request data 28 and account transfer request customer total data 29 for the entrusted party at predetermined intervals (e.g., monthly). Figure 9 is a diagram showing an example of an operation screen F3 in the account transfer management device 100. Note that Figure 9 shows the operation screen F3 in association with data related to operations on that operation screen.

As shown in FIG. 9, when the control unit 102 generates account transfer request data 28 in the account transfer management device 100, it displays an operation screen F3 on the monitor 114. The operation screen F3 displays input fields for, for example, the request year and month, account transfer trustee code, etc. When the request year and month and account transfer trustee code are entered using the keyboard 112 or the like and the register button is selected (Yes in step S107), the control unit 102 generates account transfer request data 28 based on various data for the corresponding month.

In the process of generating the account transfer request data 28, the control unit 102 determines whether the optional setting is valid for each receivable (step S108). In step S108, the control unit 102 references the account transfer amount optional setting data 27. In step S108, if the optional billing method code in the account transfer amount optional setting data 27 is 0 (specified month only) and there is data in which the specified year and month is the month of the next account transfer, the control unit 102 sets the optional billing amount in the account transfer amount optional setting data 27 as the billing amount and generates or updates the account transfer request data 28. Also, if the optional billing method code in the account transfer amount optional setting data 27 is 1 (every time from the specified year and month onwards) and there is data in which the specified year and month is equal to or less than the next month and thereafter, the control unit 102 sets the optional billing amount in the account transfer amount optional setting data 27 as the billing amount and generates or updates the account transfer request data 28.

As shown in Figure 8, the optional account transfer amount setting data 27 includes the claim number, optional billing method code, specified year and month, and optional billing amount. Note that in the example of Figure 8, as mentioned above, the data is as of February 1, 2023. The first scheduled collection date is January 26, 2023, and the second scheduled collection date is February 27, 2023.

For this reason, in the optional account transfer amount setting data 27, for example, the data for bond number 1000000009 has a specified year and month of January 2023 and an optional billing method code of 0 (specified month only), so it is set for an account transfer that has already been executed. Therefore, the control unit 102 can determine that this setting is invalid.

For example, in the data for bond number 1000000010, the specified date is January 2023 and the optional billing method code is 1 (every time from the specified date onwards), so settings are made for both the account transfer that has already been made in January 2023 and the account transfer that has not yet been made from February 2023 onwards. Therefore, the control unit 102 can determine that the settings for January 2023 for this data are invalid, and that the settings for February 2023 onwards are valid.

For example, in the data for bond number 1000000011, the specified year and month is February 2023, and the optional billing method code is 0 (specified month only), so it is set only for the unexecuted year 2023. Therefore, the control unit 102 can determine that the data is valid.

For example, in the data for bond number 1000000012, the specified date is March 2023 and the optional billing method code is 1 (every time from the specified date onwards), so the setting is for unexecuted account transfers from March 2023 onwards. Therefore, the control unit 102 can determine that the settings for February 2023 are invalid for this data, and that the settings for March 2023 onwards are valid.

If it is determined that the optional setting is valid (Yes in step S108), the control unit 102 sets the optional setting invoice amount in the account transfer amount optional setting data 27 as the invoice amount (step S109).

On the other hand, if it is determined that the optional setting is invalid (No in step S108), the control unit 102 calculates the billing amount by referring to the billing method data, collection schedule data, collection performance data, transaction history data, and account transfer management master data (step S110).

In step S110, the control unit 102 calculates the billing amount before the deduction of the deposit. If the account transfer billing method code in the billing method data 23 is 0 (single-month billing), the control unit 102 obtains the scheduled collection data 24 for which the collection year and month in the scheduled collection data 24 is the month of the next account transfer, and sets the amount of the collection amount in the scheduled collection data 24 as the billing amount before the deduction of the deposit. Also, if the account transfer billing method code in the billing method data 23 is 1 (multiple collection billing), the control unit 102 obtains the scheduled collection data 24 for which the collection year and month in the scheduled collection data 24 is equal to or less than the month of the next account transfer, and, for that scheduled collection data 24, obtains the collection history data 25 for which the claim number in the collection history data 25 is the same as the claim number in the scheduled collection data 24 and the collection sequence in the scheduled collection data 24 is the same as the collection sequence in the scheduled collection data 24. In this case, the control unit 102 subtracts the total amount of collections in the collection results data 25 from the total amount of collections in the collection schedule data 24, and adds the late payment penalty (the amount as of the account transfer request date) to determine the amount to be claimed before deducting the deposit.

After calculating the billing amount before deducting the deposit, the control unit 102 deducts the deposit, sets the billing amount, and generates account transfer request data 28 (step S111). After generating the account transfer request data 28, the control unit 102 determines whether to perform customer summation (step S112). If customer summation is to be performed (Yes in step S112), the control unit 102 generates account transfer request customer summation data 29 (step S113). If customer summation is to be performed (No in step S112), the control unit 102 skips step S113. Steps S111 and S113 are described below. Figure 10 is a diagram schematically illustrating an example of the data flow in the process of generating account transfer request data 28 and account transfer request customer summation data 29.

In step S111, if the account transfer deposit deduction flag in the billing method data 23 is true (present), the control unit 102 sets the amount claimed to be the amount claimed to be the amount calculated by subtracting the carried over deposit in the transaction history data 26 (the data with the longest transaction history sequence for each bond number) from the amount claimed to be the amount before the deposit deduction, generates or updates the account transfer request data 28, generates the account transfer request data 28, and stores or updates it in the memory unit 106. Also, if the account transfer deposit deduction flag in the billing method data 23 is false (absent), the control unit 102 sets the amount claimed to be the amount before the deposit deduction, generates the account transfer request data 28, and stores or updates it in the memory unit 106.

In step S112, the control unit 102 references the account transfer management master 12 and obtains a record in which the account transfer trustee code in the account transfer management master 12 is the account transfer trustee code displayed on the operation screen F3. If the billing unit code in the account transfer management master 12 is 0 (individual credit) (No in step S112), the control unit 102 does not update the account transfer request customer combined data. On the other hand, if the billing unit code in the account transfer management master 12 is 1 (customer combined) (Yes in step S112), the control unit 102 references the credit customer linking data 20 in the account transfer request data 28, aggregates the data from credit unit to customer unit, generates account transfer request customer combined data 29, and stores or updates it in the memory unit 106 (step S113).

Each bond shown in FIG. 9 will now be described in detail.
For the claim specified by claim number 1000000001, there are no optional settings, the billing method code is 0 (single-month billing), the account transfer deposit deduction flag is false (none), and the billing unit code is 0 (individual claim). In this case, only the February 2023 amount will be billed individually for that claim. There is an uncollected amount, but since it is a single-month billing, it is not included in the bill. In this case, the billing amount will be 10,900 yen.

For the claim specified by claim number 1000000002, there are no optional settings, the billing method code is 1 (concurrent billing), the direct debit deposit deduction flag is false (none), and the billing unit code is 0 (individual claim). In this case, only the February 2023 payment will be billed individually for that claim. There are no unpaid amounts. In this case, the billing amount will be 21,800 yen.

For the claim specified by claim number 1000000003, there are no optional settings, the billing method code is 0 (single-month billing), the direct debit deposit deduction flag is true (present), and the billing unit code is 0 (individual claim). In this case, only the February 2023 amount will be billed individually for that claim, and the amount will be the amount after the deposit deduction. In this case, the billing amount will be 31,900 yen (32,700 yen - 800 yen carried over deposit).

For the claim specified by claim number 1000000004, there are no optional settings, the billing method code is 1 (concurrent billing), the direct debit deposit deduction flag is true (present), and the billing unit code is 0 (individual claim). In this case, claims will be billed for January and February 2023, with separate billings for the claim. In this case, the billing amount will be 88,600 yen (January: 44,000 yen + January: late payment interest: 1,000 yen + February: 43,600 yen - carried over deposit: 0 yen).

For the claim specified by claim number 1000000005, there are no optional settings, the billing method code is 0 (single-month billing), the direct debit deposit deduction flag is false (none), and the billing unit code is 1 (customer combined). In this case, the customer will be billed combined for February 2023 only. In this case, the billing amount will be 54,500 yen.

For the claim specified by claim number 1000000006, there are no optional settings, the billing method code is 1 (concurrent billing), the direct debit deposit deduction flag is false (none), and the billing unit code is 1 (customer combined). In this case, only the February 2023 amount will be billed as a combined bill for the customer. There are no unpaid amounts. In this case, the billing amount will be 65,400 yen.

For the two claims with claim numbers 1000000005 and 1000000006, the billing unit code in the account transfer management master 12 is data 1 (customer total). Therefore, the amounts are totaled by customer to create account transfer request customer total data 29. Specifically, the customer is customer number 2000000003, and the total billing amount is 119,900 yen (54,500 yen + 65,400 yen).

For the claim specified by claim number 1000000007, there are no optional settings, the billing method code is 0 (single-month billing), the direct debit deposit deduction flag is true (present), and the billing unit code is 1 (customer combined). In this case, only the February 2023 amount will be billed as a combined amount for the customer, with the amount after the deposit deduction. In this case, the billing amount will be 75,900 yen (76,300 yen - 400 yen carried over deposit).

For the claim specified by claim number 1000000008, there are no optional settings, the billing method code is 1 (concurrent billing), the direct debit deposit deduction flag is true (present), and the billing unit code is 1 (customer combined). In this case, only the February 2023 amount will be billed as a combined bill for the customer. There are no uncollected amounts. In this case, the billing amount will be 86,900 yen (87,200 yen - 300 yen carried over deposit).

For the two claims with claim numbers 1000000007 and 1000000008, the billing unit code in the account transfer management master 12 is data 1 (customer total). Therefore, the amounts are totaled by customer to create account transfer request customer total data 29. Specifically, the customer is customer number 2000000004, and the total billing amount is 162,800 yen (75,900 yen + 86,900 yen).

The claim specified by claim number 1000000009 has optional settings (disabled), the billing method code is 0 (single-month billing), the direct debit deposit deduction flag is false (none), and the billing unit code is 0 (individual claim). In this case, only the February 2023 payment will be billed individually for that claim. In this case, the billing amount will be 98,100 yen.

For the claim specified by claim number 1000000010, optional settings are available (enabled), the billing method code is 1 (concurrent billing), the account transfer deposit deduction flag is false (none), and the billing unit code is 0 (individual claim). In this case, regardless of the settings of the account transfer billing method code and account transfer deposit deduction flag, the optional billing amount in the account transfer amount optional setting data 27 will be used. In this case, the billing amount will be 200,000 yen.

For the claim specified by claim number 1000000011, optional settings are enabled (enabled), the billing method code is 0 (single-month billing), the direct debit deposit deduction flag is true (enabled), and the billing unit code is 0 (individual claim). In this case, regardless of the settings of the direct debit billing method code and the direct debit deposit deduction flag, the optional billing amount in the direct debit amount optional setting data 27 will be used. In this case, the billing amount will be 150,000 yen.

The claim specified by claim number 1000000012 has optional settings (disabled), the billing method code is 1 (concurrent billing), the direct debit deposit deduction flag is true (enabled), and the billing unit code is 0 (individual claim). In this case, claims for January and February 2023 will be billed separately, with separate billings for the claim. In this case, the billing amount will be 261,800 yen (January: 132,000 yen + January late payment interest: 1,000 yen + February: 130,800 yen - carried over deposit: 2,000 yen).

After generating the account transfer request data 28 and the account transfer requesting customer combined data 29, the control unit 102 generates an account transfer request file 30 (step S114). Figure 11 is a diagram showing a schematic example of the data flow in the process of generating the account transfer request file 30. In step S114, the control unit 102 generates and outputs the account transfer request file 30 based on the data finalized in the creation of the account transfer request data 28 and the account transfer requesting customer combined data 29.

Figure 12 is a diagram showing an example of the operation screen F4 in the account transfer management device 100. Note that Figure 12 shows the operation screen F4 in association with data related to operations on that operation screen. As shown in Figure 12, when the control unit 102 generates an account transfer request file 30 in the account transfer management device 100, it displays the operation screen F4 on the monitor 114. The operation screen F4 displays input fields for, for example, the request year and month, account transfer trustee code, etc. When the request year and month and account transfer trustee code are entered via the keyboard 112, etc., and the register button is selected, the control unit 102 generates the account transfer request file 30 based on the various data for the corresponding month.

In step S114, the control unit 102 references the account transfer management master 12 and obtains a record in which the account transfer trustee code in the account transfer management master is the same as the account transfer trustee code on operation screen F4. If the billing unit code in the account transfer management master 12 is 0 (individual receivable), the control unit 102 generates and outputs an account transfer request file 30 based on the account transfer request data 28. Furthermore, if the billing unit code in the account transfer management master 12 is 1 (customer combined), the control unit 102 generates and outputs an account transfer request file 30 based on the account transfer request customer combined data 29.

As described above, the account transfer management device 100 of this embodiment is an account transfer management device 100 equipped with a control unit 102 and a memory unit 106. The memory unit 106 stores optional account transfer amount setting data 27, which includes information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data 23, which includes information indicating for each bond whether the billing method is single-month billing or multiple-collection billing. The control unit 102 determines whether the optional setting is invalid for each bond based on the optional account transfer amount setting data 27, and if it determines that the optional setting is invalid, determines whether the billing method is single-month billing or multiple-collection billing based on the billing method data 23, calculates the billing amount for each bond based on the billing method determination result, and sets the amount to be billed to the customer based on the calculation result.

The account transfer management method according to this embodiment is executed by an account transfer management device 100 equipped with a control unit 102 and a memory unit 106. The memory unit 106 stores account transfer amount optional setting data 27, which includes information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data 23, which includes information indicating for each bond whether the billing method is single-month billing or multiple-collection billing. The control unit 102 performs the following steps: determining whether the optional setting is invalid for each bond based on the account transfer amount optional setting data 27; if it determines that the optional setting is invalid, determining whether the billing method is single-month billing or multiple-collection billing based on the billing method data 23; calculating the billing amount for each bond based on the billing method determination result; and setting the billing amount for the customer based on the calculation result.

The account transfer management program according to this embodiment is an account transfer management program executed by an account transfer management device 100 equipped with a control unit 102 and a memory unit 106. The memory unit 106 stores account transfer amount optional setting data 27, which includes information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data 23, which includes information indicating for each bond whether the billing method is single-month billing or multiple-collection billing. The control unit 102 executes the following processes: determining whether the optional setting is invalid for each bond based on the account transfer amount optional setting data 27; if it is determined that the optional setting is invalid, determining whether the billing method is single-month billing or multiple-collection billing based on the billing method data 23; calculating the billing amount for each bond based on the billing method determination result; and setting the billing amount for the customer based on the calculation result.

According to this embodiment, the system determines whether the billing method is a single-month billing or a combined billing based on the billing method data 23, calculates the billing amount for each receivable based on the billing method determination result, and sets the billing amount to the customer based on the calculation result. This allows for flexible response to the nature of the product, operation method, etc. without the need for customization.

In the account transfer management device 100 according to this embodiment, the billing method data 23 includes a deposit deduction flag that indicates whether the setting is to deduct the deposit from the billing amount, and the control unit 102, when determining the billing method, further determines whether the setting is to deduct the deposit from the billing amount based on the deposit deduction flag. This configuration allows the billing amount to be set depending on whether the setting is to deduct the deposit from the billing amount, enabling flexible response depending on the characteristics of the product, the method of operation, etc.

In the account transfer management device 100 according to this embodiment, the memory unit 106 stores the account transfer management master 12, which indicates the billing unit, either individual claims, where a bill is billed for each claim, or total claims, where the billing amount for each customer is totaled. When the control unit 102 calculates the billing amount for each claim, it determines whether the billing unit is individual claims or total claims, based on the account transfer management master 12, and sets the billing amount for the customer based on the result of the billing unit determination. This configuration allows the billing amount to be set depending on whether the billing amount is individual claims, where a bill is billed for each claim, or total claims, where the billing amount for each customer is totaled, allowing for flexible response depending on the nature of the product, the method of operation, etc.

In the account transfer management device 100 according to this embodiment, the account transfer amount custom setting data 27 includes information on the custom billing amount, and when the control unit 102 determines that the custom setting is valid, it sets the billing amount for the customer based on the custom billing amount in the account transfer amount custom setting data 27. This configuration allows the billing amount to be set according to the custom setting, enabling flexible response depending on the nature of the product, the method of operation, etc.

In the account transfer management device 100 according to this embodiment, when the control unit 102 sets the amount to be charged to a customer, it generates an account transfer request file 30 that associates the customer with the amount to be charged, and outputs the generated account transfer request file 30. This configuration allows for smooth account transfer requests.

[3. 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.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

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

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.

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

Furthermore, with regard to the account transfer management device 100, the components shown in the figure are functional concepts and do not necessarily have to be physically configured as shown.

For example, the processing functions of the account transfer management device 100, particularly the processing functions performed by the control unit, may be implemented in whole or in part 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 processing described in this embodiment, and is mechanically read by the account transfer management device 100 as needed. In other words, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) that works 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.

In addition, this computer program may be stored on an application program server connected to the account transfer management device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure 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 structures and procedures.

The various databases stored in the memory unit are storage devices 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 website provision.

The account transfer management device 100 may also be configured as an information processing device such as a known personal computer or workstation, or as such an information processing device to which any peripheral device is connected. The account transfer management device 100 may also be realized by installing software (including programs or data, etc.) that causes the device to perform the processing described in this embodiment.

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

The present invention is useful in the financial industry, etc., for debt collection operations and debt collection operations for various businesses.

F1, F2, F3, F4 Operation screen 10 Product master 11 Account transfer entrusted party master 12 Account transfer management master 13 Collection method master 14 Account transfer billing method master 20 Credit customer linking data, data 21 Credit information data 22 Customer bank account data 23 Billing method data 24 Collection schedule data 25 Collection performance data 26 Transaction history data 27 Account transfer amount optional setting data 28 Account transfer request data 29 Account transfer request customer total data 30 Account transfer request file 100 Account transfer management device 102 Control unit 104 Communication interface unit 106 Memory unit 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

An account transfer management device comprising a control unit and a storage unit,
The storage unit
optional setting data including information indicating whether optional setting for making a claim at any time is valid or invalid for each claim;
billing method data including information indicating whether the billing method is a single-month billing or a multiple-month billing for each of the claims;
The control unit
determining whether the optional setting is invalid for each of the claims based on the optional setting data;
If it is determined that the optional setting is invalid, it is determined whether the billing method is the single-month billing or the multiple-collection billing based on the billing method data;
Calculating the amount of claim for each claim based on the determination result of the claim method;
The account transfer management device sets the amount to be charged to the customer based on the calculation result. The billing method data includes a deposit deduction flag indicating whether a deposit is to be deducted from the billing amount,
The account transfer management device according to claim 1 , wherein the control unit, in determining the billing method, further determines whether or not the setting is such that the deposit is deducted from the billing amount, based on the deposit deduction flag. the storage unit stores an account transfer management master indicating a billing unit, which is either an individual claim invoice for each claim or a customer aggregate invoice for each customer,
When the control unit calculates the billing amount for each of the receivables, the control unit determines whether the billing unit is for each of the receivables individually or for the total of the receivables, based on the account transfer management master;
The account transfer management device according to claim 1 , wherein the amount to be charged to the customer is set based on the result of determining the billing unit. The optional setting data includes optional billing amount information,
The account transfer management device according to claim 1 , wherein the control unit, when determining that the optional setting is valid, sets the amount to be charged to the customer based on the optional billing amount in the optional setting data. The account transfer management device of claim 1, wherein the control unit, when setting the billing amount for the customer, generates an account transfer request file that associates the customer with the billing amount and outputs the generated account transfer request file. An account transfer management method executed by an account transfer management device having a control unit and a storage unit,
The storage unit
optional setting data including information indicating whether optional setting for making a claim at any time is valid or invalid for each claim;
billing method data including information indicating whether the billing method is a single-month billing or a multiple-month billing for each of the claims;
a step of determining whether the optional setting is invalid for each of the bonds based on the optional setting data;
If it is determined that the optional setting is invalid, determining whether the billing method is the single-month billing or the multiple-collection billing based on the billing method data;
calculating a claim amount for each claim based on the determination result of the claim method;
and setting the amount to be charged to the customer based on the calculation result, An account transfer management program to be executed by an account transfer management device having a control unit and a storage unit,
The storage unit
optional setting data including information indicating whether optional setting for making a claim at any time is valid or invalid for each claim;
billing method data including information indicating whether the billing method is a single-month billing or a multiple-month billing for each of the claims;
a process of determining whether the optional setting is invalid for each bond based on the optional setting data;
If it is determined that the optional setting is invalid, a process of determining whether the billing method is the single-month billing or the multiple-collection billing based on the billing method data;
A process of calculating a claim amount for each claim based on the determination result of the claim method;
and setting the amount to be charged to the customer based on the calculation result.