Account transfer management device, account transfer management method, and account transfer management program

Abstract

To provide an account transfer management device capable of flexibly coping with account transfer according to product properties and an operation method, etc. without performing customization.SOLUTION: An account transfer management device comprises a storage unit and a control unit. The storage unit stores arbitrary setting data including information indicative of whether arbitrary setting for billing at an arbitrary timing is valid or invalid per credit, and billing method data including information indicative of whether the billing method is monthly billing or unpaid premium billing per credit. The control unit determines whether arbitrary setting is valid per credit on the basis of arbitrary setting data. When it determines that arbitrary setting is invalid, the control unit determines whether the billing method is monthly billing or unpaid premium billing on the basis of the billing method data, calculates a billing amount per credit on the basis of the determination results of the billing method, and sets a billing amount for a customer on the basis of the calculation results.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an account transfer management device, an account transfer management method, and an account transfer management program. [Background technology]

[0002] BACKGROUND ART Conventionally, there is known an account transfer management device that reduces the risk of uncollected payments for product sales and the like at a business operator and the cost of requesting collection from a collection agent (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-079831 Summary of the Invention [Problem to be solved by the invention]

[0004] In the account transfer management device as described in Patent Document 1, account transfers are carried out in various modes depending on the nature of the products handled, the operating methods of each company, etc. Therefore, it may be necessary to customize the account transfer management device depending on, for example, the nature of the products, the operating methods, etc.

[0005] The present invention has been 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 respond to the characteristics of products, operation methods, etc. without the need for customization. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, 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 an 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, and 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.

[0007] In addition, the account transfer management method of the present invention is an account transfer management method executed by 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 an 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, and 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 to the customer based on the calculation result.

[0008] In addition, the account transfer management program of the present invention is an account transfer management program to be executed by an account transfer management device having a control unit and a memory unit, wherein the memory unit stores optional setting data including information indicating for each bond whether an 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, and causes the control unit to execute the following processes: a process for determining whether the optional setting is invalid for each bond based on the optional setting data; a process for determining whether the billing method is single-month billing or multiple-collection billing based on the billing method data if it is determined that the optional setting is invalid; a process for calculating the billing amount for each bond based on the result of the billing method determination; and a process for setting the billing amount for the customer based on the calculation result. [Effects of the Invention]

[0009] The present invention has the advantage of being able to flexibly respond to the characteristics of products, operation methods, etc., without customization. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing an example of an account transfer management device according to this embodiment. [Figure 2] FIG. 2 is a flowchart showing an example of the flow of processing in the account transfer management device. [Figure 3] FIG. 3 is a diagram illustrating an example of various masters stored in the storage unit. [Figure 4] FIG. 4 is a diagram illustrating an example of data stored in the storage unit. [Figure 5] FIG. 5 is a diagram showing an example of an operation screen in the account transfer management device. [Figure 6] FIG. 6 is a diagram showing an example of collection schedule data and collection record data. [Figure 7] FIG. 7 is a diagram illustrating an example of transaction history data. [Figure 8] FIG. 8 is a diagram showing an example of an operation screen in the account transfer management device. [Figure 9] FIG. 9 is a diagram showing an example of an operation screen in the account transfer management device. [Figure 10] 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. [Figure 11] FIG. 11 is a diagram showing an example of a data flow in the process of generating an account transfer request file. [Figure 12] FIG. 12 is a diagram showing an example of an operation screen in the account transfer management device. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of an account transfer management device, an account transfer management method, and an account transfer management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[0012] [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 devices constructed based on portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones or tablet personal computers.

[0013] 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. The units comprised in the account transfer management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0014] The control unit 102 is a CPU (Central Processing Unit) or the like that performs 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 an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and performs various information processing based on these stored programs. The specific processing content of the control unit 102 will be described later.

[0015] 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 a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the account transfer management device 100 and other devices so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The network 300 may also have a function of connecting the account transfer management device 100 and a 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.

[0016] 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. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0017] 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 instructions to a CPU 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.

[0018] The memory unit 106 stores various master data, including a product master data 10, an account transfer entrusted party master data 11, an account transfer management master data 12, a collection method master data 13, and an account transfer billing method master data 14. The memory unit 106 also stores the following data: credit customer linking data 20, credit information data 21, customer bank account data 22, billing method data 23, collection schedule data 24, collection performance data 25, transaction history data 26, account transfer amount optional 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 together in the specific examples of processing below.

[0019] [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 apparatus 100. Figure 2 is a flowchart showing an example of the flow of processing in the account transfer management apparatus 100.

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

[0021] FIG. 3 is a diagram showing an example of various masters stored in the storage unit 106. As shown in FIG. 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 a billing method, which will be described later. Note that although the settings for each item are determined on a product-by-product basis, they can also be changed on a receivable-by-receivable basis.

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

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

[0024] The collection method master 13 is data that associates collection method codes with names of collection methods. 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.

[0025] 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. When the direct debit billing method code is 1, it is set to single-month billing. When the direct debit billing method code is 2, it is set to multiple collection billing.

[0026] <Application input, billing method registration> After registering various master data, an application is made for a transaction that is subject to account transfer, such as a mortgage. In the application input, information such as the receivables, customer (debtor), and customer bank account that are the subject of account transfer management is input using the input device 112. In the application input, 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 memory unit 106 (step S102).

[0027] Fig. 4 is a diagram showing an example of data stored in the storage unit 106. Fig. 4 shows credit customer linking data 20, credit information data 21, and customer bank account data 22. Fig. 4 shows the relationships between the various data using a simple ER diagram. In Fig. 4, the primary key is indicated by PK, and the external reference key is indicated by FK.

[0028] 4, the bond-customer linking data 20 manages linking information between a bond and a customer (debtor). 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.

[0029] The bond information data 21 manages information on bonds (such as product codes) and includes a bond number indicating the identification number of the bond and a customer number indicating the identification number of the customer.

[0030] The customer bank account data 22 manages information about a customer's bank account. The customer bank account data 22 includes a customer number, a bank number indicating the identification number of the bank, a viewpoint number indicating the identification number of a branch in the bank, a deposit item indicating the type of deposit, an account number indicating the customer's account number, and the name of the account holder.

[0031] After inputting the application, the billing method is registered. Figure 5 is a diagram showing 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 the operation screen.

[0032] 5, when registering a billing method in the account transfer management device 100, the control unit 102 displays an 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 entrusted party 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 entrusted party code, account transfer deposit deduction flag, and account transfer billing method code corresponding to the claim number.

[0033] For example, the control unit 102 inputs the code value set in the collection method code master as the collection method code. When 1 (account transfer) is specified as the collection method code, the control unit 102 can set the account transfer entrusted party code, account transfer deposit deduction flag, and account transfer billing method code.

[0034] When registering a new billing method, the control unit 102 initially displays the account transfer entrusted party code in the product master 10. Thereafter, the control unit 102 refers to the account transfer entrusted party master 11 and sets the account transfer entrusted party code.

[0035] Furthermore, when a new billing method is registered, the control unit 102 sets the account transfer deposit deduction flag in the product master 10 to an initial display. The control unit 102 checks the flag ON (true) if the deposit is to be deducted, and checks the flag OFF (false) if the deposit is not to be deducted.

[0036] 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 to set 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, similar data can be generated for bond numbers 1000000002 and onward.

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

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

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

[0040] 6, in the collection schedule data 24, various items such as the collection sequence (collection SEQ), collection sequence, collection month and year, collection date, collection amount, principal, interest, and fees are set corresponding to the bond number. In the collection schedule data 24, values such as the collection month and year, collection date, collection amount, principal, interest, and fees are input for each collection sequence.

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

[0042] 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 all uncollected.

[0043] As shown in Figure 7, the transaction history data 26 includes items such as transaction sequence, transaction type code, transaction date, loan amount, recovery amount, and carried-over deposit. The transaction type code is, 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 item of the transaction history data 26. A blank value for each item in the transaction history data 26 indicates that no transaction has occurred.

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

[0045] 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 bond 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 billing period from the specified month onwards. The operation screen F2 also displays the billing amount as of the calculation base date. When the bond number, optional billing method code, specified year and month, and calculation base date are entered via the keyboard 112 or the like, 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 the control unit 102 does not perform any arbitrary setting (No in step S105), the control unit 102 skips step S106.

[0046] <Account transfer request> When performing an account transfer, the account transfer management device 100 generates account transfer request data 28 and account transfer requesting customer total data 29 for the entrusted party at predetermined intervals (for example, 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.

[0047] 9, when generating account transfer request data 28 in the account transfer management device 100, the control unit 102 displays an operation screen F3 on the monitor 114. The operation screen F3 displays input fields for, for example, the request year and month, the account transfer entrusted party code, etc. When the request year and month and the account transfer entrusted party 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 the account transfer request data 28 based on the various data for the corresponding month.

[0048] In the process of generating the account transfer request data 28, the control unit 102 determines whether the optional setting is valid for each bond (step S108). In step S108, the control unit 102 references the account transfer amount optional setting data 27. In step S108, if there is data in which the optional billing method code of the account transfer amount optional setting data 27 is 0 (specified month only) and the specified year and month is the month of the next account transfer, the control unit 102 sets the amount of 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. In addition, if there is data in which the optional billing method code of the account transfer amount optional setting data 27 is 1 (every time from the specified year and month onwards) and the specified year and month is equal to or less than the next month and thereafter, the control unit 102 sets the amount of 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.

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

[0050] For this reason, for example, in the data for bond number 1000000009 in the optional account transfer amount setting data 27, the specified year and month is January 2023 and the optional billing method code is 0 (only the specified month), 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.

[0051] For example, for the data of bond number 1000000010, the specified year and month is January 2023 and the optional billing method code is 1 (every time from the specified year and month 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 setting for January 2023 for this data is invalid, and that the setting for February 2023 onwards is valid.

[0052] For example, for the data of 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.

[0053] For example, for the data of 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 setting for February 2023 is invalid for the data, and that the setting for March 2023 onwards is valid.

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

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

[0056] In step S110, the control unit 102 calculates the billing amount before the deduction of the deposit. If the account transfer billing method code of the billing method data 23 is 0 (single-month billing), the control unit 102 acquires the collection schedule data 24 for which the collection year and month in the collection schedule data 24 is the month of the next account transfer, and sets the amount of the collection amount in the collection schedule data 24 as the billing amount before the deduction of the deposit. Also, if the account transfer billing method code of the billing method data 23 is 1 (concurrent collection billing), the control unit 102 acquires the collection schedule data 24 for which the collection year and month in the collection schedule data 24 is equal to or less than the month of the next account transfer, and, for the collection schedule data 24, acquires the collection record data 25 for which the claim number in the collection schedule data 24 is the same as the claim number in the collection schedule data 24 and the collection sequence in the collection record data 25 is the same as the collection sequence in the collection schedule 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 date of the account transfer request) to determine the amount to be claimed before deducting the deposit.

[0057] 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 or not to perform customer summation (step S112), and if customer summation is to be performed (Yes in step S112), 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 will be described below. Figure 10 is a diagram schematically illustrating an example of the data flow in the process of generating the account transfer request data 28 and the account transfer request customer summation data 29.

[0058] 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 deducted from the deposit, generates or updates the account transfer request data 28, and stores or updates the data 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 claimed to be the amount claimed to be the amount claimed to be the amount claimed to be deducted from the deposit, generates the account transfer request data 28, and stores or updates the data in the memory unit 106.

[0059] In step S112, the control unit 102 refers to the account transfer management master 12 and obtains a record in which the account transfer entrusted party code in the account transfer management master 12 is the account transfer entrusted party code displayed on the operation screen F3. If the billing unit code in the account transfer management master 12 is 0 (individual bond) (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 refers to the bond customer linking data 20 in the account transfer request data 28, aggregates it from bond unit to customer unit, generates account transfer request customer combined data 29, and stores or updates it in the memory unit 106 (step S113).

[0060] Each bond shown in FIG. 9 will be specifically described. For the bond specified by bond number 1000000001, 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 0 (individual bond). In this case, only the February 2023 payment will be billed individually for that bond. 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.

[0061] 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 uncollected amounts. In this case, the billing amount will be 21,800 yen.

[0062] For the bond specified by bond 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 bond). In this case, only for February 2023, the bond will be billed individually, 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 - carried over deposit 800 yen).

[0063] 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 individual billing for the claim. In this case, the billing amount will be 88,600 yen (January 44,000 yen + January late payment penalty 1,000 yen + February 43,600 yen - carried over deposit 0 yen).

[0064] For the bond specified by bond 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 total). In this case, the customer will be billed totaled for February 2023 only. In this case, the billing amount will be 54,500 yen.

[0065] 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 total). In this case, only the February 2023 amount will be billed as a combined total for the customer. There are no unpaid amounts. In this case, the billing amount will be 65,400 yen.

[0066] For the two credits with credit 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).

[0067] For the bond specified by bond 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 total). In this case, only the February 2023 amount will be billed as a total 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).

[0068] 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 total). In this case, only the February 2023 amount will be billed as a combined total 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).

[0069] For the two credits with credit 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).

[0070] The bond specified by bond number 1000000009 has optional settings (disabled), 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 bond). In this case, the bond will be billed individually for February 2023 only. The billed amount will be 98,100 yen.

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

[0072] For the bond specified by bond number 1000000011, optional settings are available (enabled), the billing method code is 0 (single month billing), the direct debit deposit deduction flag is true (yes), and the billing unit code is 0 (individual bond). 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.

[0073] 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 will be billed for January and February 2023, 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).

[0074] After generating the account transfer request data 28 and the account transfer requesting customer total data 29, the control unit 102 generates an account transfer request file 30 (step S114). Figure 11 is a diagram showing a typical 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 total data 29.

[0075] Fig. 12 is a diagram showing an example of the operation screen F4 in the account transfer management device 100. Fig. 12 shows the operation screen F4 in association with data related to operations on the operation screen. As shown in Fig. 12, when generating an account transfer request file 30 in the account transfer management device 100, the control unit 102 displays the operation screen F4 on the monitor 114. The operation screen F4 displays input fields for, for example, the request year and month, the account transfer entrusted party code, etc. When the request year and month and the account transfer entrusted party code are entered via the keyboard 112 or the like 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.

[0076] In step S114, the control unit 102 refers to the account transfer management master 12 and obtains a record in which the account transfer entrusted party code in the account transfer management master is the same as the account transfer entrusted party code on the operation screen F4. If the billing unit code in the account transfer management master 12 is 0 (individual credit), the control unit 102 generates and outputs an account transfer request file 30 based on the account transfer request data 28. Also, 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.

[0077] 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, and the memory unit 106 stores optional account transfer amount setting data 27 including information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data 23 including 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.

[0078] Furthermore, the account transfer management method according to this embodiment is an account transfer management method executed by an account transfer management device 100 equipped with a control unit 102 and a memory unit 106, and the memory unit 106 stores account transfer amount optional setting data 27 including information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data 23 including information indicating for each bond whether the billing method is single-month billing or multiple-collection billing, and 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 result of the billing method determination; and setting the amount to be billed to the customer based on the calculation result.

[0079] In addition, the account transfer management program of this embodiment is an account transfer management program to be executed by an account transfer management device 100 equipped with a control unit 102 and a memory unit 106, and the memory unit 106 stores account transfer amount optional setting data 27 including information indicating for each bond whether the optional setting for billing at any timing is valid or invalid, and billing method data 23 including information indicating for each bond whether the billing method is single-month billing or multiple-collection billing, and causes the control unit 102 to execute 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 to be charged to the customer based on the calculation result.

[0080] According to this embodiment, the billing method is determined based on the billing method data 23, whether it is a single-month billing or a combined billing, the billing amount is calculated for each receivable based on the result of the billing method determination, and the billing amount to the customer is set based on the calculation result, so that it is possible to flexibly respond to the characteristics of the product, the method of operation, etc. without customization.

[0081] In the account transfer management device 100 according to this embodiment, the billing method data 23 includes a deposit deduction flag indicating whether the setting is to deduct the deposit from the billing amount, and the control unit 102, in determining the billing method, further determines whether the setting is to deduct the deposit from the billing amount based on the deposit deduction flag. With this configuration, the billing amount can be set depending on whether the setting is to deduct the deposit from the billing amount, allowing for flexible response depending on the characteristics of the product, the method of operation, etc.

[0082] In the account transfer management device 100 according to this embodiment, the storage unit 106 stores the account transfer management master 12, which indicates the billing unit, either individual bond, where a bill is made for each bond, or total customer, where the billing amounts for each customer are added up, and when the control unit 102 calculates the billing amount for each bond, it determines whether the billing unit is individual bond or total customer, based on the account transfer management master 12, and sets the amount to be billed to the customer based on the result of the billing unit determination. With this configuration, the billing amount can be set depending on whether it is individual bond, where a bill is made for each bond, or total customer, where the billing amounts for each customer are added up, allowing for flexible response depending on the nature of the product, the method of operation, etc.

[0083] In the account transfer management device 100 according to this embodiment, the account transfer amount optional setting data 27 includes information on the optional billing amount, and when the control unit 102 determines that the optional setting is valid, it sets the billing amount to the customer based on the optional billing amount in the account transfer amount optional setting data 27. With this configuration, the billing amount can be set according to the optional setting, allowing for flexible response to the nature of the product, the method of operation, etc.

[0084] In the account transfer management device 100 according to this embodiment, when the control unit 102 sets the amount to be charged to the 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.

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

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

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

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

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

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

[0091] Furthermore, with regard to the account transfer management 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.

[0092] For example, all or any part of the processing functions of the account transfer management device 100, particularly the processing functions performed by the control unit, may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-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 account transfer management device 100 as needed. That is, a computer program for cooperating with the OS to issue instructions to the CPU and perform various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0093] In addition, this computer program may be stored in an application program server connected to the account transfer management device 100 via any network, and it is also possible to download all or part of it as needed.

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

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

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

[0097] The account transfer management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the 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) that causes the device to realize the processing described in this embodiment.

[0098] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0099] The present invention is useful in the financial industry and the like when carrying out debt collection operations and debt collection operations for various businesses. [Explanation of symbols]

[0100] 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 Direct debit billing method master 20 Credit customer linkage data, data 21 Credit Information Data 22 Customer Bank Account Data 23 Billing Method Data 24 Data to be collected 25 Recovery data 26 Transaction History Data 27 Account transfer amount optional setting data 28 Direct debit request data 29 Customer aggregate data for direct debit requests 30 Direct Debit Request File 100 Account transfer management device 102 Control section 104 Communication interface unit 106 Storage section 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. 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 debts; Remember, 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; Based on the calculation result, the amount to be charged to the customer is set. Account transfer management device.

2. The billing method data includes a deposit deduction flag indicating whether a deposit is to be deducted from the billing amount, The control unit further determines, in determining the billing method, whether or not a deposit is set to be deducted from the billing amount based on the deposit deduction flag. The account transfer management device according to claim 1.

3. 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 amount to be charged to the customer is set based on the result of the determination of the billing unit. The account transfer management device according to claim 1.

4. The optional setting data includes optional billing amount information, When the control unit determines that the optional setting is valid, the control unit sets the billing amount to the customer based on the optional billing amount in the optional setting data. The account transfer management device according to claim 1.

5. When the amount to be charged to the customer is set, the control unit generates an account transfer request file in which the customer and the amount to be charged are associated with each other, and outputs the generated account transfer request file. The account transfer management device according to claim 1.

6. 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 debts; Remember, 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; setting the amount to be charged to the customer based on the calculation result; The control unit performs How to manage direct debits.

7. 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 debts; Remember, 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; a process of setting the amount to be charged to the customer based on the calculation result; causing the control unit to execute Direct debit management program.

Images