Business support device, business support method, and business support program

Abstract

This can improve the collection rate of invoiced amounts and reduce the customer's fee burden. [Solution] The details data creation unit creates account transfer billing contract details data, which are account transfer billing details for each contract ID in the month of account transfer billing, based on account transfer basic data including customer ID, contract ID, product related to the contract, agent code, contract date, customer account SEQ which identifies the customer's bank account, and billing unit number which indicates the billing unit for account transfer, and contract billing data which associates the scheduled transfer date and billing amount with the contract ID. The aggregate data creation unit creates account transfer customer aggregate data, which are account transfer billing details for each billing unit number in the month of account transfer billing, based on the created account transfer billing contract details data, and aggregate the billing amounts associated with each of the multiple contract IDs that contain the same billing unit number among the account transfer billing details for each contract ID. The output control unit outputs the account transfer customer aggregate data to the output device.

Description

Technical Field

[0001] The present invention relates to a business support device, a business support method, and a business support program.

Background Art

[0002] In Patent Document 1 (Japanese Patent Application Laid-Open No. 2024-136812), after a transaction is started, it is determined whether the billing amount of account transfer can be set at an arbitrary timing, and the billing method of account transfer is determined. According to the billing method determined for each product, an account transfer management device capable of setting the billing amount for a customer is disclosed.

[0003] This account transfer management device determines whether the arbitrary setting for billing at an arbitrary timing is valid or invalid for each claim based on arbitrary setting data including information indicating whether the arbitrary setting for billing at an arbitrary timing is valid or invalid for each claim. When it is determined that the arbitrary setting is invalid, it is determined whether the billing method is monthly billing or consolidated billing for each claim based on billing method data including information indicating whether the billing method is monthly billing or consolidated billing for each claim. Then, based on the determination result of the billing method, the billing amount is calculated for each claim, and based on the calculation result, the billing amount for the customer is set. As a result, it is possible to flexibly respond according to the nature of the product, the operation method, etc. without customization.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, traditionally, the amount billed via direct debit for each customer was aggregated, resulting in a single billing statement even for products with different contract details and repayment amounts. While this reduced the direct debit fees borne by the customer, it also led to a problem where the billed amount could not be collected if the balance in the withdrawal account was insufficient, as the amount billed became larger.

[0006] On the other hand, creating a separate direct debit statement for each contract reduces the risk of not being able to collect the billed amount even if the withdrawal account has insufficient funds, but it has the problem of increasing the direct debit fees borne by the customer.

[0007] This invention has been made in view of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that improve the collection rate of billed amounts and reduce the customer's fee burden by adjusting whether or not to combine the billed amounts for direct debit related to other contracts, depending on the contract details and the scale of the repayment amount. [Means for solving the problem]

[0008] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention provides a billing statement for account transfers for each contract in the month of account transfer, based on account transfer basic data including a customer ID to identify the customer, a contract ID to identify the contract with the customer, a product code to identify the product related to the contract, a service provider code to identify the service provider that performs account transfers from the customer's bank account, the agreed date stipulated in the contract, a customer account SEQ (sequence) to identify the customer's bank account, and a billing unit number indicating the billing unit for account transfers, and contract billing data that associates the scheduled transfer date and billing amount with the contract ID, wherein the billing statement for account transfers for each contract in the month of account transfer is provided, and the contract ID is associated with the service provider code, agreed date, and billing unit number. The system includes: a detail data creation unit that creates account transfer billing contract detail data including billing details that associate unit numbers and billing amounts; a summary data creation unit that, based on the created account transfer billing contract detail data, creates account transfer customer summary data that includes at least one billing detail obtained by summing the billing amounts included in each of the multiple billing details, where there are multiple such billing details for the same billing unit number among the account transfer billing details for each contract included in the account transfer billing contract detail data; and an output control unit that outputs the account transfer customer summary data to an output target device.

[0009] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support method according to the present invention provides a detailed data creation unit that generates a detailed account transfer billing statement for each contract in the month of transfer, based on account transfer basic data including a customer ID to identify the customer, a contract ID to identify the contract with the customer, a product code to identify the product related to the contract, a service provider code to identify the service provider that performs account transfers from the customer's bank account, the agreed date stipulated in the contract, a customer account SEQ (sequence) to identify the customer's bank account, and a billing unit number indicating the billing unit for account transfers, and contract billing data that associates the scheduled transfer date and billing amount with the contract ID, wherein the contract ID is associated with the service provider code, the agreed date, the billing unit number and The system includes: a detail data creation step that creates account transfer billing contract detail data including billing details that associate the requested amounts; a summary data creation step in which a summary data creation unit creates account transfer customer summary data based on the created account transfer billing contract detail data, which includes account transfer billing details for each billing unit number in the month of transfer, and in cases where there are multiple such billing details for the same billing unit number among the account transfer billing details for each contract included in the account transfer billing contract detail data, the account transfer customer summary data which includes at least one billing detail obtained by summing the billing amounts included in each of the multiple such billing details; and an output control step in which an output control unit outputs the account transfer customer summary data to an output target device.

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support program according to the present invention uses a computer to generate a billing statement for account transfers for each contract in the month of the account transfer, based on account transfer basic data including a customer ID to identify the customer, a contract ID to identify the contract with the customer, a product code to identify the product related to the contract, a service provider code to identify the service provider that performs account transfers from the customer's bank account, the agreed date stipulated in the contract, a customer account SEQ (sequence) to identify the customer's bank account, and a billing unit number indicating the billing unit for account transfers, and contract billing data that associates the scheduled transfer date and billing amount with the contract ID, wherein the contract ID is associated with the service provider code, The system functions as a detail data creation unit that creates account transfer billing contract detail data including billing details that associate the contract date, billing unit number, and billing amount; an aggregate data creation unit that, based on the created account transfer billing contract detail data, creates account transfer customer aggregate data that includes at least one billing detail obtained by summing the billing amounts included in each of the multiple billing details, where there are multiple such billing details for the same billing unit number among the account transfer billing details for each contract included in the account transfer billing contract detail data; and an output control unit that outputs the account transfer customer aggregate data to an output target device. [Effects of the Invention]

[0011] This invention allows for adjustments to be made regarding whether or not to combine the amount of direct debit charges related to other contracts, depending on the contract details and the scale of the repayment amount. This improves the recovery rate of the amount of charges and reduces the customer's fee burden. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 is a block diagram showing the hardware configuration of a business support device according to an embodiment. [Figure 2] Figure 2 shows an example of contract data stored in the contract data storage unit. [Figure 3] Figure 3 shows an example of customer account data stored in the customer account data storage unit. [Figure 4] FIG. 4 is a diagram showing an example of basic account transfer data stored in the basic account transfer data storage unit. [Figure 5] FIG. 5 is a diagram showing an example of the numbering master before and after registration of the basic account transfer data. [Figure 6] FIG. 6 is a diagram showing an example of contract billing data stored in the contract billing data storage unit. [Figure 7] FIG. 7 is a diagram showing an example of the account transfer billing contract detail data stored in the detail data storage unit. [Figure 8] FIG. 8 is a diagram showing an example of the account transfer billing customer aggregation data stored in the aggregation data storage unit. [Figure 9] FIG. 9 is a diagram showing an example of the account transfer billing file stored in the account transfer billing file storage unit. [Figure 10] FIG. 10 is a diagram showing an example of the basic account transfer information input screen. [Figure 11] FIG. 11 is a diagram for explaining Modification Example 1 of the operation of the basic data creation unit. [Figure 12] FIG. 12 is a diagram for explaining Modification Example 2 of the operation of the basic data creation unit. [Figure 13] FIG. 13 is a diagram showing an example of the notification displayed on the basic account transfer information input screen. [Figure 14] FIG. 14 is a diagram showing an example of the account transfer billing data creation screen. [Figure 15] FIG. 15 is a diagram showing an example of the basic account transfer data stored in the basic account transfer data storage unit. [Figure 16] FIG. 16 is a diagram showing an example of the account transfer billing file creation screen.

Embodiments for Carrying Out the Invention

[0013] Hereinafter, a business support apparatus according to an embodiment to which the present invention is applied will be described in detail based on the drawings. Note that the present invention is not limited to the following embodiments.

[0014] [Configuration] (Hardware Configuration) FIG. 1 is a block diagram showing the hardware configuration of a business support device according to an embodiment. As shown in FIG. 1, the business support device 1 of the embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5.

[0015] An input device 6 and an output device 7 are connected to the input / output interface unit 5. As the output device 7, a display unit such as a monitor device (including a home TV), a printing device, or a speaker device, etc. corresponds. As the input device 6, in addition to a keyboard device, a mouse device, and a microphone device, etc., a monitor device that cooperates with the mouse device to realize a pointing device function can also be used. The communication interface unit 4 is connected to a network such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0016] As the storage unit 2, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used. In the storage unit 2, a business support program that can improve the recovery rate of the claim amount and reduce the customer's fee burden is stored.

[0017] In addition, in this storage unit 2, there are provided a contract data storage unit 21, a customer account data storage unit 22, a basic account transfer data storage unit 23, a numbering master 24, a contract billing data storage unit 25, a detail data storage unit 26, a consolidated data storage unit 27, an account transfer billing file storage unit 28, and an account transfer result storage unit 29, which are storage areas respectively.

[0018] The contract data storage unit 21 stores data that indicates information about the contract details, i.e., contract data. The contract data associates a contract ID (Identifier) ​​that identifies the contract with the customer with, for example, the contract date, the product related to the contract (e.g., product code), the contract amount, the due date, the monthly repayment amount, and the contract interest rate.

[0019] Figure 2 shows an example of contract data stored in the contract data storage unit 21. For example, as shown in Figure 2, the contract data storage unit 21 contains data indicating information about the contract, such as contract ID "2000000001", customer ID "1000000001", contract date "2024 / 07 / 15", product code "0009: Free Loan", contract amount (yen) "100,000", agreement date "25", monthly repayment amount (yen) "1,000", and contract interest rate (%) "5".

[0020] The contract data may be directly input into and stored in the business support device 1, or it may be input into a terminal device used by the customer or employee and stored in the server device 11.

[0021] The customer account data storage unit 22 stores data that indicates information about the customer's bank account, i.e., customer account data. The customer account data associates the customer ID, which identifies the customer, with, for example, the customer account SEQ (SEQ: sequence: number), bank code, branch code, deposit type, account number, and account holder's name.

[0022] Figure 3 shows an example of customer account data stored in the customer account data storage unit 22. For example, as shown in Figure 3, the customer account data storage unit 22 contains data indicating information about the customer's bank account (hereinafter also referred to as bank account information), such as customer ID "1000000001", customer account SEQ "1", bank code "1501: A Bank", branch code "009: B Branch", deposit item "1: Ordinary", account number "1234567", and account holder name "Yamada Taro".

[0023] Furthermore, if the same customer designates multiple bank accounts as direct debit accounts, the customer account data storage unit 22 stores data indicating information about each bank account. The customer account SEQ is an identifier (so-called ID) used to identify the customer's bank account information, and is automatically assigned to each bank account, including, for example, the bank code, branch code, deposit item, account number, and account holder's name.

[0024] The account transfer basic data storage unit 23 stores data indicating basic information about account transfers for each contract, i.e., account transfer basic data. The account transfer basic data associates the contract ID with, for example, an agent code that identifies the agent that handles account transfers from the customer's bank account, the contract date, customer ID, customer account SEQ, and a billing unit number that indicates the billing unit for the account transfer.

[0025] Figure 4 shows an example of the basic account transfer data stored in the account transfer basic data storage unit 23. For example, as shown in Figure 4, the account transfer basic data storage unit 23 stores data indicating basic information about account transfers for each contract, such as contract ID "2000000001", agent code "0001", contract date "25", customer ID "1000000001", customer account SEQ "1", and billing unit number "KK00000100".

[0026] The numbering master 24 is a table that describes the numbering type code and the assigned number. The numbering type code is a code that indicates the type of data used in the business support device 1. Here, we will explain using the numbering of billing unit numbers included in the account transfer basic data as an example.

[0027] Figure 5 shows an example of the numbering master 24 before and after the registration of the account transfer basic data. The numbering master 24 may be configured to increment the last number assigned to the numbering type code. For example, as shown in Figure 5(a), the numbering master 24 contains the billing unit number "KK00000099" included in the already registered account transfer basic data as the last number. However, when new account transfer basic data is created and stored in the account transfer basic data storage unit 23, as shown in Figure 5(b), the last number described in the numbering master 24 increments to "KK00000100".

[0028] The contract billing data storage unit 25 stores data related to the monthly repayment schedule date and repayment amount for each contract, in other words, the monthly scheduled account transfer date (hereinafter referred to as the transfer date) and billing amount for each contract. Figure 6 is a diagram showing an example of contract billing data stored in the contract billing data storage unit 25. For example, as shown in Figure 6, the contract billing data storage unit 25 stores contract billing data that associates the transfer date and billing amount with the contract ID.

[0029] The details data storage unit 26 stores account transfer billing contract details data, which includes account transfer billing details for each contract in the month of the account transfer billing. In these account transfer billing details for each contract, the contract ID is associated with, for example, the agent code, the contract date, the billing unit number, and the billing amount.

[0030] Figure 7 shows an example of direct debit billing contract details data stored in the details data storage unit 26. In the example in Figure 7, the direct debit billing contract details data is a table-formatted data describing the direct debit billing details for each contract with September 2024 as the transfer month and year.

[0031] The aggregated data storage unit 27 stores aggregated account transfer customer data, which includes account transfer billing details for each billing unit number in the month of transfer billing. These account transfer billing details for each billing unit number include at least one billing detail obtained by summing the billing amounts included in each of the multiple billing details for account transfers for each contract included in the account transfer billing contract details data (see Figure 7), in cases where there are multiple such billing details for the same billing unit number.

[0032] Figure 8 shows an example of aggregated customer data for direct debit billing stored in the aggregated data storage unit 27. The example in Figure 8 shows aggregated customer data for direct debit billing created based on the direct debit billing contract details data in Figure 7. For example, the direct debit billing details for contract IDs "2000000001" and "2000000002" in the first and second rows of the table in Figure 7 have the same billing unit number "KK00000100". When there are multiple billing details for the same billing unit number in this way, the billing amounts "1000" and "2000" included in these billing details are added together to create a billing detail (first row of the table in Figure 8) with a billing amount of "3000" associated with billing unit number "KK00000100".

[0033] The direct debit request file storage unit 28 stores a file for requesting an agency to handle direct debits for the month in which the direct debit is requested. For example, this file includes billing details that associate the customer account SEQ, customer bank account information, and billing amount for each billing unit number. Figure 9 shows an example of a direct debit request file stored in the direct debit request file storage unit 28.

[0034] For example, as shown in Figure 9, the direct debit billing file is a text file that contains information about the agency (in this case, agency A) along with the billing details for each billing unit number (KK00000100, KK00000200, KK00000300) included in the direct debit customer aggregate data (see Figure 8).

[0035] The account transfer result storage unit 29 stores the account transfer result file created by the agency that obtained the account transfer result from the bank and sent by the user (in this case, the business that provides the contracted goods to the customer). This file is a text file created in the Japanese Bankers Association format and consists of four different types of records (header record, data record, trailer record, and end record) in one file.

[0036] Furthermore, the storage unit 2 may also store a transfer table storage unit. For example, the transfer table storage unit stores the destination item, the source table, and the source item in association with each other.

[0037] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the storage unit 2, and functions as an acquisition unit 31, a basic data creation unit 32, a detailed data creation unit 33, a total data creation unit 34, a billing file creation unit 35, and an output control unit 36, as shown in Figure 1.

[0038] In this example, the acquisition unit 31 to the output control unit 36 ​​are described as being implemented in software based on a business support program, but all or part of the acquisition unit 31 to the output control unit 36 ​​may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0039] The acquisition unit 31 acquires instructions input to the input device 6 and information transmitted via the network from external devices (for example, terminal devices of the business operator's employees, terminal devices 10 of the service provider, server devices 11, etc.). The network has been described above, so its explanation is omitted here.

[0040] The basic data creation unit 32 creates basic account transfer data related to the customer's contract. As described above, the basic account transfer data (see Figure 4) is data that shows basic information regarding account transfers for each contract. For example, based on the basic data creation instruction acquired by the acquisition unit 31, the basic data creation unit 32 refers to the contract data storage unit 21 (see Figure 2) and the customer account data storage unit 22 (see Figure 3) in the storage unit 2 to create the basic account transfer data related to the customer's contract.

[0041] The data required to create the basic account transfer data may be data stored in the storage unit 2 (for example, contract data, customer account data, billing unit number, etc.), data entered into the input device 6, or data acquired by the acquisition unit 31 from an external device via the network.

[0042] Furthermore, regarding contract billing data (see Figure 6), for example, when the account transfer basic data created by the basic data creation unit 32 is stored in the account transfer basic data storage unit 23 within the storage unit 2, that data is reflected in the contract billing data in the contract billing data storage unit 25.

[0043] For example, when creating basic account transfer basic data, the basic data creation unit 32 uses the billing unit number for other contracts if the agent code, contract date, and customer account SEQ included in the account transfer basic data for other registered contracts for a customer match the entered agent code, contract date, and customer account SEQ.

[0044] On the other hand, if the agent code, contract date, and customer account SEQ included in the account transfer basic data related to other registered contracts do not match the entered agent code, contract date, and customer account SEQ, the basic data creation unit 32 assigns and uses a new billing unit number.

[0045] Furthermore, for example, when creating basic direct debit basic data, the basic data creation unit 32 will not register the created basic direct debit data if the agent code, contract date, and customer account SEQ included in the account direct debit basic data related to other registered contracts for a customer do not match the entered agent code, contract date, and customer account SEQ, or if the billing unit number related to the other contract is entered.

[0046] Furthermore, for example, when creating account transfer basic data, if the agent code, contract date, and customer account SEQ included in the account transfer basic data related to other registered contracts for a customer match the entered agent code, contract date, and customer account SEQ, and the billing unit number related to those other contracts is used, and the product code related to the other registered contracts differs from the entered product code, then when an instruction to register the created account transfer basic data is received, the basic data creation unit 32 outputs a confirmation notice to the output device via the output control unit 36 ​​to the output device. The specific processing performed by the basic data creation unit 32 will be described later.

[0047] The details data creation unit 33 creates account transfer request contract details data based on the account transfer basic data (Figure 7) and contract billing data (see Figure 6). As described above, the account transfer request contract details data (see Figure 7) includes the account transfer billing details for each contract in the month of transfer. For example, based on the details data creation instruction acquired by the acquisition unit 31, the details data creation unit 33 refers to the account transfer basic data storage unit 23 and the contract billing data storage unit 25 in the storage unit 2 and creates the account transfer request contract details data for the entered transfer billing month (for example, September 2024). The specific processing performed by the details data creation unit 33 will be described later.

[0048] The aggregated data creation unit 34 creates aggregated data for direct debit customers based on the direct debit billing contract details data. As described above, the aggregated data for direct debit customers (see Figure 8) includes the direct debit billing details for each billing unit number in the direct debit billing month. For example, if there are multiple billing details for the same billing unit number among the direct debit billing details for each contract included in the direct debit billing contract details data, the aggregated data creation unit 34 aggregates the billing amounts included in each of the multiple billing details and combines them into a single billing detail. The specific processing performed by the aggregated data creation unit 34 will be described later.

[0049] The billing file creation unit 35 creates a file, also known as a direct debit billing file (see Figure 9), based on the aggregated direct debit customer data, to request the agency to handle direct debits for the month in which the direct debit is billed.

[0050] The output control unit 36 ​​outputs various data and files created by the control unit 3 and stored in the storage unit 2 to the output target device. The output target device may be, for example, the output device 7 (see Figure 1), or it may be an external device that can communicate with the business support device 1 via a network.

[0051] Furthermore, the output data and files may include, for example, aggregated data for direct debit customers, direct debit billing data, and direct debit billing files, as well as contract data, customer account data, basic direct debit data, contract billing data, direct debit billing contract details data, etc.

[0052] Output restrictions may be imposed on these files as needed. For example, if the external device is a third-party terminal device 10, the output control unit 36 ​​may output only the account transfer customer aggregate data and account transfer billing data to the external device.

[0053] When the output target device is output device 7, a display device, a printing device, or a speaker device can be used as output device 7. The output control unit 36 ​​converts the data and files to be output into display information, print information, or audio information and supplies them to each device to obtain the display output, print output, or audio output corresponding to that data and files. Alternatively, the output target device may be a storage unit 2, an external storage device, or a server device 11 on a network.

[0054] [Operation] Next, the operation of the business support device 1 according to the embodiment will be described. The business support device 1 reads the registered direct debit customer aggregate data from the storage unit 2 and performs the creation and registration process of a direct debit request file. The business support device 1 also reads the registered direct debit request file from the storage unit 2, creates a direct debit request file, and outputs it to the output target device. Note that the operation of the business support device 1 is not limited to the following example.

[0055] (Registration of basic account transfer data) The business support device 1 reads pre-registered basic information such as contract data, customer account data, and account transfer basic data from the storage unit 2, and performs the creation and registration process of account transfer basic data. The following describes the registration operation of account transfer basic data.

[0056] Figure 10 shows an example of a screen for entering basic account transfer information. For example, when registering basic account transfer data, if the person in charge (i.e., the user) specifies that the screen for entering basic account transfer information should be displayed, the output control unit 36 ​​will display the screen for entering basic account transfer information via the output device 7.

[0057] The person in charge enters the contract ID "2000000001", the agent code "0001", and the customer account sequence "1" into this input screen. Once this data is entered, the basic data creation unit 32 reads the contract data corresponding to the contract ID "2000000001" stored in the contract data storage unit 21, reads the customer account data corresponding to the customer account sequence "1" stored in the customer account data storage unit 22, and reflects it on the input screen. Information regarding the agent is read from the agent master (not shown) which exists in the storage unit 2.

[0058] When this data is reflected on the input screen, the basic data creation unit 32 refers to the account transfer basic data associated with customer ID "1000000001" stored in the account transfer basic data storage unit 23 and determines whether or not there is account transfer basic data registered with the same data as the agent code, contract date, and customer account SEQ entered on the screen.

[0059] The basic data creation unit 32 assigns and displays a new billing unit number if no corresponding account transfer basic data exists, that is, if any of the above data differs from the registered data. A new billing unit number is assigned by incrementing the last number (see Figure 5(a)) described in the numbering master 24 (see Figure 5) (see Figure 5(b)).

[0060] On the other hand, if the corresponding account transfer basic data exists, the basic data creation unit 32 uses the billing unit number included in that account transfer basic data. The account transfer basic data created in this way is stored in the account transfer basic data storage unit 23 (see Figure 4), and the registration operation is completed.

[0061] (Example 1 of the registration process for basic direct debit data) Next, we will explain an example of operation (modification 1) in which, in the above example of operation, if the corresponding account transfer basic data does not exist, the person in charge enters a billing unit number that is already registered in another contract. Figure 11 is a diagram illustrating modification 1 of the operation of the basic data creation unit 32.

[0062] As shown in Figure 11, if the entered customer account SEQ differs from the customer account SEQ in the registered account transfer basic data, and the person in charge enters the billing unit number of the registered account transfer basic data, the basic data creation unit 32 instructs the output control unit 36 ​​to output a predetermined notification to the output target device (for example, output device 7).

[0063] For example, the designated notification may be a message such as "This billing unit number cannot be used for registration" or "Please check for any errors in your input," and the output format is not particularly limited. Furthermore, in addition to the above notifications, the basic data creation unit 32 may highlight the data items entered by the person in charge (in this case, billing unit number, contract ID, agent code, and customer account SEQ), or it may disable the registration button until the error is resolved. This reduces the burden on the person in charge and prevents the registration of incorrect data due to input errors.

[0064] (Modified example 2 of the registration process for basic direct debit data) Next, we will explain a modified example 2 of the operation for registering basic direct debit data. In the above example, the decision to reuse a billing unit number already registered in another contract or to assign a new one was made based on whether or not the relevant basic direct debit data exists in the basic direct debit data storage unit 23. Therefore, in modified example 2, we will explain an example of operation when the relevant basic direct debit data exists in the basic direct debit data storage unit 23, but the product code is different from the product code already registered in another contract.

[0065] Figure 12 is a diagram illustrating a modified example of the operation of the basic data creation unit 32. In the example in Figure 12, since the entered agent code, contract date, and customer account SEQ match the agent code, contract date, and customer account SEQ of the registered account transfer basic data, the basic data creation unit 32 uses the billing unit number of the registered account transfer basic data.

[0066] In this case, when the person in charge presses the registration button, the basic data creation unit 32 instructs the output control unit 36 ​​to output a predetermined notification to the output target device (for example, the output device 7). Note that the billing unit number may be one entered by the person in charge.

[0067] Figure 13 shows an example of a notification displayed on the account transfer basic information input screen. For example, as shown in Figure 13, a notification asking the person in charge to confirm whether to register the information is displayed on the input screen. In this case, the notification may also be made by voice or the product code may be highlighted. This allows the person in charge to check for errors in the input before registering the account transfer basic information, thereby reducing input errors. In addition, the highlighted items make it easier for the person in charge to recognize the items that need to be checked, reducing the burden on them and improving work efficiency.

[0068] (Creation of direct debit billing statement data) The business support device 1 reads the registered account transfer basic data and contract billing data from the storage unit 2 and performs the creation and registration process of account transfer billing contract details data. The following describes the operation of creating account transfer billing details data with reference to Figures 6, 7, and 15. Figure 15 is a diagram showing an example of account transfer basic data stored in the account transfer basic data storage unit 23.

[0069] When the acquisition unit 31 receives an instruction to create direct debit billing statement data, the statement data creation unit 33 instructs the output control unit 36 ​​to output the direct debit billing statement data creation screen. The output control unit 36 ​​displays the screen on the output target device (for example, the output device 7 as a monitoring device), and when the person in charge enters the direct debit billing month on the screen, the statement data creation unit 33 starts the following operations.

[0070] The details data creation unit 33 reads the account transfer basic data (see Figure 15) and contract billing data (see Figure 6) from the account transfer basic data storage unit 23 and the contract billing data storage unit 25 in the storage unit 2, and creates account transfer billing details data (see Figure 7) that includes billing details for account transfers for each contract in the month of transfer billing, with the contract ID associated with the agent code, contract date, billing unit number, and billing amount. When the person in charge presses the registration button displayed on the screen, the details data creation unit 33 stores the created account transfer billing details data (see Figure 7) in the details data storage unit 26.

[0071] (Creation of aggregated data for direct debit customers) The business support device 1 reads the registered direct debit billing contract details data from the storage unit 2 and performs the creation and registration of the direct debit customer aggregate data. The following describes the operation of creating the direct debit customer aggregate data with reference to Figures 3 and 7.

[0072] When the acquisition unit 31 receives an instruction to create aggregated data for direct debit customers, the aggregated data creation unit 34 instructs the output control unit 36 ​​to output the screen for creating aggregated data for direct debit customers. The output control unit 36 ​​displays the screen on the output target device (for example, the output device 7), and when the person in charge presses the execute button on the screen, the aggregated data creation unit 34 starts the following operations.

[0073] The aggregated data creation unit 34 reads the account transfer request contract details data from the details data storage unit 26 (see Figure 7) in the storage unit 2, and reads the customer account data corresponding to that data from the customer account data storage unit 22 (see Figure 3).

[0074] The aggregated data creation unit 34 determines whether there are multiple invoices for the same invoice unit number among the account transfer invoice details data for each contract included in the account transfer invoice contract details data for the month in which the transfer is billed. If the aggregated data creation unit 34 determines that there are multiple invoices for the same invoice unit number, it aggregates the invoice amounts included in each of the multiple invoices.

[0075] In the example in Figure 7, since there are two billing details for the same billing unit number "KK00000100", the aggregated data creation unit 34 adds up the billing amounts of these billing details and creates aggregated account transfer customer data (see Figure 8) that includes one billing detail associated with the billing unit number "KK00000100". Then, when the person in charge presses the registration button displayed on the screen, the aggregated data creation unit 34 stores the created aggregated account transfer customer data (see Figure 8) in the aggregated data storage unit 27.

[0076] (Creation of direct debit request file) The business support device 1 reads the registered direct debit customer aggregate data from the storage unit 2, creates direct debit request data, and performs the creation and registration process of a direct debit request file based on the created direct debit request data. The following describes the operation of creating direct debit request data with reference to Figures 14 and 16. Figure 14 is a diagram showing an example of the direct debit request data creation screen. Figure 16 is a diagram showing an example of the direct debit request file creation screen.

[0077] When the acquisition unit 31 receives the instruction from the person in charge to create a direct debit invoice file, the invoice file creation unit 35 instructs the output control unit 36 ​​to output the direct debit invoice data creation screen (see Figure 14). The output control unit 36 ​​then displays the screen on the output target device (for example, the output device 7 as a monitoring device).

[0078] When the person in charge enters the agent code "0001" and the contract date "25" on the screen and presses the execute button, the billing file creation unit 35 extracts data including the contract date "25" from the account transfer customer aggregate data (see Figure 8) stored in the aggregate data storage unit 27 and creates account transfer billing data. Once the account transfer billing data is created, it is stored, for example, in the work data storage unit (not shown) within the storage unit 2.

[0079] Once the direct debit request data is stored, the request file creation unit 35 instructs the output control unit 36 ​​to output the direct debit request file creation screen (see Figure 16). When the person in charge confirms the agent code and contract date displayed on the screen and presses the execute button, the request file creation unit 35 converts the direct debit request data into text data to create a direct debit request file and stores it in the direct debit request file storage unit 28.

[0080] [Effects of the embodiment] As is clear from the above explanation, the business support device 1 according to the embodiment can adjust whether or not to combine the amount of the account transfer billing related to other contracts depending on the contract details and the scale of the repayment amount, thereby improving the collection rate of the billing amount and reducing the customer's fee burden.

[0081] For example, according to the business support device 1 of the embodiment, when the output target device is an external device, the data and files stored in the storage unit 2 can be output via the network, thereby improving convenience and the work efficiency of the person in charge.

[0082] Furthermore, for example, according to the business support device 1 of the embodiment, when creating basic direct debit information related to a customer's contract, if the agent code, contract date, and customer account SEQ included in the registered basic direct debit information related to other contracts match the data being created, the registered billing unit number is used, allowing them to be consolidated into a single billing statement. This reduces the customer's fee burden.

[0083] Furthermore, for example, according to the business support device 1 of the embodiment, if the agent code, contract date, and customer account SEQ included in the account transfer basic information related to other registered contracts differ from the data being created, using the registered billing unit number will prevent the creation of the account transfer basic data. This reduces input errors by the person in charge and prevents the registration of incorrect data.

[0084] Furthermore, for example, according to the business support device 1 of the embodiment, when creating basic account transfer information related to a customer's contract, if the agent code, contract date, and customer account SEQ included in the account transfer basic information related to other registered contracts match the data being created, the person in charge has the opportunity to confirm whether it is acceptable to use the registered billing unit number even if the product code is different, thereby reducing input errors by the person in charge.

[0085] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving operational efficiency and promoting appropriate management decisions by companies, and therefore can contribute to SDGs Goals 8 and 9.

[0086] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0087] Furthermore, this invention can contribute to strengthening control and governance, and therefore can contribute to achieving the 16 goals of the SDGs.

[0088] [Other embodiments] The present invention can be implemented in various different forms within the scope of the technical idea described in the claims, even in embodiments other than those described above.

[0089] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually. Alternatively, all or part of the processes described as being performed manually may be performed automatically by known methods or the like.

[0090] Furthermore, unless otherwise specified, the processing procedures, control procedures, specific names, registration data for each process, information including parameters such as search conditions, screen examples, and database configuration shown in the specification or drawings can be arbitrarily changed.

[0091] Furthermore, with respect to the business support device 1, each component shown in the diagram is a functional concept and does not necessarily have to have the physical configuration shown. For example, the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be implemented in whole or in any part by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or by hardware using wired logic.

[0092] The program is recorded on a non-temporary, computer-readable recording medium containing programmed instructions for the information processing device to execute the processes described in the embodiment, and is mechanically read by the business support device 1 as needed. In other words, the storage unit 2, such as ROM or HDD, records a computer program that works in cooperation with the OS (Operating System) to give instructions to the control unit 3 (CPU) and perform various processes. This computer program is loaded into RAM, unpacked, and executed by the control unit 3 as appropriate.

[0093] Furthermore, the business support program for this business support device 1 may be stored on another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0094] Furthermore, the business support program for executing the processes described in the embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product.

[0095] Here, any "portable physical medium" can be used as the "recording medium," such as memory cards, USB (Universal Serial Bus) memory, 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 Blu-ray (Registered Trademark) Discs.

[0096] Furthermore, "program" refers to a data processing method written in any language or writing method, regardless of whether it is source code or binary code.

[0097] Furthermore, the term "program" is not necessarily limited to a single, monolithic entity, but also includes those that are distributed as multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions.

[0098] Furthermore, for the specific configuration, reading procedure, and post-reading installation procedure for the business support device 1 of the embodiment, well-known configurations or procedures can be used.

[0099] The storage unit 2 is a storage means such as memory devices like RAM and ROM, fixed disk devices like hard disks, flexible disks, and optical disks, and stores various programs, tables, databases, and web page files used for various processing or website provision.

[0100] Furthermore, the business support device 1 may be composed of a known personal computer device or an information processing device such as a workstation, or it may be composed of an information processing device to which any peripheral devices are connected. In addition, the information processing device may be implemented by implementing software (including programs or data, etc.) that realizes the processing described in the embodiment.

[0101] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing or integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above can be selectively implemented by arbitrarily combining the embodiments described above. [Industrial applicability]

[0102] This invention is particularly suitable for application in debt collection operations and the like. [Explanation of Symbols]

[0103] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input devices 7 Output device 10. Agent Terminal Device 11 Server equipment 21 Contract Data Storage Unit 22 Customer Account Data Storage Unit 23 Account Transfer Basic Data Storage Unit 24 Numbering Master 25 Contract billing data storage unit 26. Detailed Data Storage Unit 27 Combined Data Storage Unit 28 Account transfer request file storage unit 29 Account transfer result storage unit 31 Acquisition Department 32 Basic Data Creation Section 33. Detailed Data Creation Department 34. Combined Data Creation Department 35. Invoice File Creation Department 36 Output control unit

Claims

1. A detail data creation unit creates account transfer billing contract detail data for each contract in the month of transfer billing, which includes account transfer basic data including a customer ID to identify the customer, a contract ID to identify the contract with the customer, a product code to identify the product related to the contract, a service provider code to identify the service provider that performs account transfers from the customer's bank account, the agreed date stipulated in the contract, a customer account SEQ (sequence) to identify the customer's bank account, and a billing unit number indicating the billing unit of the account transfer, and contract billing data which associates the scheduled transfer date and billing amount with the contract ID, and which includes billing details for account transfers for each contract in the month of transfer billing, wherein the contract ID is associated with the service provider code, the agreed date, the billing unit number and the billing amount. A combined data creation unit creates combined account transfer customer data that, based on the created account transfer billing contract details data, includes account transfer billing details for each billing unit number in the month of the transfer billing, and in cases where there are multiple such billing details for the same billing unit number among the account transfer billing details for each contract included in the account transfer billing contract details data, the combined data includes at least one billing detail obtained by summing the billing amounts included in each of the multiple such billing details. An output control unit that outputs the aforementioned account transfer customer aggregate data to an output target device, A business support device equipped with the following features.

2. moreover, A file for requesting the agency to perform the account transfer in the month of the account transfer based on the aggregated account transfer customer data, comprising a billing file creation unit that creates an account transfer billing file for each billing unit number, which includes a billing details that associate the customer account SEQ, the customer's bank account information, and the billing amount. The output control unit outputs the account transfer request file to the output target device. The business support device according to claim 1.

3. The output control unit, If the output target device is an external device, the direct debit request file is output to the external device via the network. The business support device according to claim 2.

4. moreover, The system includes a basic data creation unit that creates basic account transfer basic data, which is data showing basic information regarding account transfers for each contract, based on contract data, which is data showing information about the customer's contract details, and customer account data, which is data showing information about the customer's bank account. A business support device according to any one of claims 1 to 3.

5. The basic data creation unit, in creating the account transfer basic data, If, with respect to the aforementioned customer, the agent code, settlement date, and customer account SEQ included in the account transfer basic data related to other registered contracts match the entered agent code, settlement date, and customer account SEQ, the billing unit number related to the other contract shall be used. If the agent code, contract date, and customer account SEQ included in the account transfer basic data related to the other registered contract do not match the entered agent code, contract date, and customer account SEQ, a new billing unit number shall be assigned and used. The business support device according to claim 4.

6. The basic data creation unit, in creating the account transfer basic data, If, with respect to the aforementioned customer, the agent code, the contract date, and the customer account SEQ included in the account transfer basic data related to the other contract already registered do not match the entered agent code, the contract date, and the customer account SEQ, then when the billing unit number related to the other contract is entered, the created account transfer basic data will not be registered. The business support device according to claim 5.

7. The basic data creation unit, in creating the account transfer basic data, If, with respect to the customer, the agent code, settlement date, and customer account SEQ included in the account transfer basic data related to the registered other contract match the entered agent code, settlement date, and customer account SEQ, and the billing unit number related to the other contract is used, and the product code related to the registered other contract differs from the entered product code, then when an instruction to register the created account transfer basic data is entered, the output control unit outputs a confirmation notice to the output target device to the user. The business support device according to claim 5.

8. A detail data creation step in which the detail data creation unit creates a detail data for account transfer billing contract detail data for each contract in the month of transfer billing, which includes a customer ID to identify the customer, a contract ID to identify the contract with the customer, a product code to identify the product related to the contract, a service provider code to identify the service provider that performs account transfers from the customer's bank account, a contract date specified in the contract, a customer account SEQ (sequence) to identify the customer's bank account, and a billing unit number indicating the billing unit of the account transfer, and contract billing data that associates the scheduled transfer date and billing amount with the contract ID, and which includes a billing detail for account transfers for each contract in the month of transfer billing, in which the service provider code, the contract date, the billing unit number and the billing amount are associated with the contract ID. The aggregated data creation unit creates aggregated account transfer customer data based on the created account transfer billing contract details data, which includes, in the case where there are multiple such billing details for the same billing unit number among the account transfer billing details for each contract included in the account transfer billing contract details data, at least one billing detail obtained by summing the billing amounts included in each of the multiple such billing details, and The output control unit performs an output control step in which it outputs the account transfer customer aggregate data to the output target device, A business support method that has the following characteristics.

9. Computers, A detail data creation unit creates account transfer billing contract detail data for each contract in the month of transfer billing, which includes account transfer basic data including a customer ID to identify the customer, a contract ID to identify the contract with the customer, a product code to identify the product related to the contract, a service provider code to identify the service provider that performs account transfers from the customer's bank account, the agreed date stipulated in the contract, a customer account SEQ (sequence) to identify the customer's bank account, and a billing unit number indicating the billing unit of the account transfer, and contract billing data which associates the scheduled transfer date and billing amount with the contract ID, and which includes billing details for account transfers for each contract in the month of transfer billing, wherein the contract ID is associated with the service provider code, the agreed date, the billing unit number and the billing amount. A combined data creation unit creates combined account transfer customer data that, based on the created account transfer billing contract details data, includes account transfer billing details for each billing unit number in the month of the transfer billing, and in cases where there are multiple such billing details for the same billing unit number among the account transfer billing details for each contract included in the account transfer billing contract details data, the combined data includes at least one billing detail obtained by summing the billing amounts included in each of the multiple such billing details. Output control unit outputs the aforementioned account transfer customer aggregate data to the output device. A business support program designed to function as such.

Images