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

Abstract

This reduces the burden on staff members who are responsible for reconciling payments. [Solution] Based on the payment data, a matching process is performed, and the balance of the accounts receivable data is automatically reconciled. At this time, the error determination unit refers to a batch payment check master table, which contains check execution flag information indicating whether manual reconciliation is required, set for each payment route and payment type, at least for each payment route indicating bank transfer or direct debit for the payment data, based on the payment route and payment type of the payment data. The unit then determines whether the payment data is payment data that requires manual reconciliation. The output control unit outputs extracted result data, including the error determination result, payment route, and payment type for each payment data, to the output target device. This clarifies which payments require manual reconciliation and makes them known to the person in charge, thereby reducing the burden of payment reconciliation work.

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] Patent Document 1 (Japanese Patent Application Laid-Open No. 2022-135330) discloses a billing reconciliation method that can easily extract billing data and payment data corresponding to the same billing recipient and enable smooth reconciliation. This billing reconciliation method is reconciliation information related to reconciliation performed for shared users who share a shared learning history, and based on the reconciliation information including the corporate number corresponding to the billing recipient of the billing data and the name of the remittance requester, it has a shared update process for updating the shared learning history. Also, at least one of a batch reconciliation process for shared users and an individual reconciliation process for shared users performs reconciliation based on a user learning history that can be updated based on the billing data, payment data, and shared learning history. Thereby, it is possible to easily extract billing data and payment data corresponding to the same billing recipient and enable smooth reconciliation.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, for example, in the claim management business of a financial institution, deposit information from customers is read as a file, grouped within the system, and automatic reconciliation processing is performed on the target claims.

[0005] However, this automated reconciliation process can actually create more work and sometimes result in incorrect amounts. Therefore, employees had to manually reconcile any incorrect payment data after the automated process had finished. As a result, the automated reconciliation process actually increased the workload for employees.

[0006] 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 can reduce the burden on personnel in charge of reconciliation work for deposits. [Means for solving the problem]

[0007] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention is a business support device that supports the settlement of deposit data by performing name matching based on deposit data and performing automatic settlement of the balance of accounts receivable data, and includes an error determination unit that refers to a batch deposit check master table, which includes check execution flag information indicating whether manual settlement work is required, set for each deposit route and deposit type, which indicates at least bank transfer deposits or account transfers of deposit data, based on the deposit route and deposit type of deposit data, and determines whether the deposit data is deposit data that requires manual settlement work, and an output control unit that outputs extracted result data including the determination result of the error determination unit, the deposit route and the deposit type for each deposit data to an output target device.

[0008] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the business support method according to the present invention is a business support method executed by a business support device that supports the settlement of deposit data by performing name matching based on deposit data and performing automatic settlement of the balance of accounts receivable data, and comprises an error determination step in which an error determination unit refers to a batch deposit check master table which includes check execution flag information indicating whether manual settlement work is required, set for each deposit route and deposit type that indicates at least bank transfer deposits or account transfers for deposit data, based on the deposit route and deposit type of deposit data, and determines whether the deposit data is deposit data that requires manual settlement work, and an output control step in which an output control unit outputs extracted result data including the determination result of the error determination step, the deposit route and the deposit type for each deposit data to an output target device.

[0009] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the business support program according to the present invention is a business support program that enables the computer of a business support device to function by performing an automatic reconciliation function that performs name matching based on payment data and automatically reconciles the balance of accounts receivable data, wherein the computer functions as an error determination unit that determines whether or not manual reconciliation is required, and an output control unit that outputs extracted result data, including the determination result of the error determination unit, the payment route and the payment type for each payment data, to an output target device. The computer refers to a batch payment check master table, which includes check execution flag information indicating whether or not manual reconciliation is required, set for each payment route and payment type, which indicates at least bank transfer or account transfer for the payment data. [Effects of the Invention]

[0010] This invention can reduce the burden on personnel responsible for reconciling payments. [Brief explanation of the drawing]

[0011] [Figure 1]Figure 1 is a block diagram showing the hardware configuration of the business support device according to the embodiment. [Figure 2] Figure 2 shows an example of a bulk payment check master table. [Figure 3] Figure 3 shows an example of a file storage unit for importing files. [Figure 4] Figure 4 shows an example of a temporary receipt data storage unit. [Figure 5] Figure 5 shows an example of a debt data storage unit. [Figure 6] Figure 6 shows an example of a billing data storage unit. [Figure 7] Figure 7 shows an example of a data storage unit for the reconciliation results. [Figure 8] Figure 8 shows an example of the bulk payment reconciliation screen. [Figure 9] Figure 9 shows an example of the temporary receipts list screen. [Figure 10] Figure 10 is a flowchart showing the flow of the first half of the bulk payment reconciliation process. [Figure 11] Figure 11 is a flowchart showing the flow of the latter half of the bulk payment reconciliation process. [Modes for carrying out the invention]

[0012] The following describes in detail, with reference to the drawings, an embodiment of the present invention applied to a business support device that assists in the reconciliation operations of financial institutions. However, the present invention is not limited to the following embodiments.

[0013] (overview) In the debt management operations of financial institutions, customer payment information is read as a file, and the system performs name matching and automatically reconciles the relevant debts. However, this automated reconciliation process can lead to unnecessary work and errors in the amounts, as illustrated below.

[0014] 1. When there are settlement claims or bad debt claims → There may be cases where you want to waive late payment damages. In such cases, you need to cancel the automatic deposit and manually perform the write-off process again, which increases the workload of the person in charge. 2. When completed by write-off → It is necessary to create a completion certificate. After the process, it is necessary to extract and check the claims that have been completed this time from the claims that have been completed, which increases the workload of the person in charge. 3. When a deposit is recorded as a result of write-off → A difference occurs between the amount deposited and the amount billed. This occurs when transactions have been made between billing and write-off, or when the operation is incorrect. Also, since it is possible that the amounts and information in the system are incorrect, the person in charge needs to investigate the cause, which increases the workload.

[0015] On the other hand, in such cases, manual write-off is performed. However, in companies that handle a large number of cases, the workload of the person in charge increases due to the increase in the number of manual write-off cases. Also, cases where manual deposit is desired differ depending on the product quality or payment route, etc., and customization is required each time.

[0016] For this reason, in the business support device of the embodiment, when the conditions are met by master setting, manual write-off is executed as an error. This enables pre-detection of operation errors and improves the efficiency of subsequent operations.

[0017] Also, in the business support device of the embodiment, by enabling the setting of whether to check for each payment route, the workload of the person in charge is reduced and the occurrence of operation errors is prevented. For example, when settlement is completed by account transfer, write-off is performed automatically, and when settlement is completed by transferred deposit, since there are often delays, write-off is performed while manually checking. As a result, it is possible to select the write-off form according to the form of settlement.

[0018] (Hardware Configuration) As shown in Figure 1, the business support device 1 of this embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 may be a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that works in cooperation with a mouse device to realize a pointing device function.

[0019] The communication interface unit 4 is connected to a network 50, such as a wide-area network like the Internet or a private network like a LAN (Local Area Network). Each customer's bank terminal device (customer bank terminal device 51) is connected to the network 50. When a customer makes a transfer or manual deposit for a claim, the customer bank terminal device 51 transmits deposit data (temporary receipt data), generated, for example, based on the format specified by the Japanese Bankers Association, to the business support device 1.

[0020] For the memory unit 2, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used. The memory unit 2 stores a business support program that can reduce the burden on the person in charge of reconciling payments.

[0021] Furthermore, this storage unit 2 is equipped with the following storage areas: a batch payment check master table 11, an import file storage unit 12, a temporary receipt data storage unit 13, a receivables data storage unit 14, an invoice data storage unit 15, and a reconciliation result data storage unit 16.

[0022] As shown in Figure 2, the batch payment check master table 11 stores check execution flag information indicating whether manual reconciliation is required for each payment route and type of payment.

[0023] Specifically, the Bulk Payment Check Master Table 11 associates the payment route "1: Bank Transfer" with a payment type where the error check type code is "1" and the error check type name is "Bad Debt," as well as a check execution flag information of "1" indicating that manual reconciliation is required. Additionally, the Bulk Payment Check Master Table 11 associates the payment route "1: Bank Transfer" with a payment type where the error check type code is "2" and the error check type name is "Fully Paid This Time," as well as a check execution flag information of "1" indicating that manual reconciliation is required. Furthermore, the Bulk Payment Check Master Table 11 associates the payment route "1: Bank Transfer" with a payment type where the error check type code is "3" and the error check type name is "Deposit Generated," as well as a check execution flag information of "1" indicating that manual reconciliation is required.

[0024] Furthermore, the Bulk Deposit Check Master Table 11 associates the "2: Account Transfer" deposit route with a deposit type where the error check type code is "1" and the error check type name is "Bad Debt," as well as a check implementation flag information of "1" indicating that manual reconciliation is required. Additionally, the Bulk Deposit Check Master Table 11 associates the "2: Account Transfer" deposit route with a deposit type where the error check type code is "2" and the error check type name is "Fully Paid This Time," as well as a check implementation flag information of "0" indicating that manual reconciliation is not required. Furthermore, the Bulk Deposit Check Master Table 11 associates the "2: Account Transfer" deposit route with a deposit type where the error check type code is "3" and the error check type name is "Deposit Generated," as well as a check implementation flag information of "1" indicating that manual reconciliation is required.

[0025] Note that the payment route, payment type, and check execution flag information set in the batch payment check master table 11 are just examples. For this reason, other payment routes may be set, for example, to "convenience store payment" indicating payment from a convenience store.

[0026] Additionally, you may set one or more types of deposits and check execution flag information as exemplified below. 1. Transactions after processing → An error will occur if transactions occur after the file has been imported. 2. Before the last charge date → If the last charge date is earlier than the provisional charge date, an error will occur. 3. Bad debt → Bad debt will result in an error. 4. No settlement balance → This is a settlement claim, and if the balance is 0 yen, an error occurs. 5. No balance → An error occurs if the balance is 0 yen. 6. Settlement claim → Error if settlement claim is used 7. Claims for which the benefit of time has been lost → Error if the claim is for which the benefit of time has been lost. 8. Debt change registration exists → An error will occur if a debt change registration has been made for the month in which the payment is to be applied. 9. Delinquent payment detected → Error if the debt is in arrears. 10. Deposit is generated → An error occurs if a deposit is generated after reconciliation. 11. If the payment is completed this time → This will result in an error.

[0027] As shown in Figure 3, the import file storage unit 12 stores the transfer deposit files and account transfer files transmitted from the customer bank terminal device 51.

[0028] As shown in Figure 4, the temporary receipt data storage unit 13 stores temporary receipt data contained in the transfer deposit file and temporary receipt data contained in the account transfer file transmitted from the customer bank terminal device 51. As shown in Figure 4, the temporary receipt data includes the temporary receipt date, deposit route (in this example, 1: transfer deposit or 2: account transfer), amount, reconciliation claim identification number (reconciliation claim ID), and file identification number. A temporary receipt identification number (temporary receipt ID) is automatically assigned and added to each temporary receipt data.

[0029] Note that the provisional receipt data is an example of payment data. The reconciliation claim ID is an identification number attached to the claim to be reconciled. By attaching the reconciliation claim ID to the provisional receipt data, the provisional receipt data and the claim data are linked, making it possible to automatically detect the claim data corresponding to the provisional receipt data and perform the reconciliation process.

[0030] As shown in Figure 5, the debt data storage unit 14 stores the debt identification number (= the reconciled debt ID mentioned above), the outstanding debt balance, and the bad debt flag information. In the example in Figure 5, the debt data with debt ID "2" and outstanding debt balance of "500,000 yen" has a bad debt flag of "1" (bad debt flag information of "1") attached to it, indicating that it is a bad debt. A bad debt flag of "0" indicates that the debt data is not a bad debt.

[0031] As shown in Figure 6, the billing data storage unit 15 stores the billing amount for each claim.

[0032] As shown in Figure 7, the reconciliation result data storage unit 16 stores a reconciliation result code, which is the result of a determination based on the batch payment check master table 11, indicating whether or not manual reconciliation processing should be performed on the temporary receipt data. The example in Figure 7 shows that for the temporary receipt data with temporary receipt ID "1" shown in Figure 4, the determination result based on the batch payment check master table 11 was that manual reconciliation processing was not required, and the automatic reconciliation processing was completed successfully, so the reconciliation result code "1: Successful Completion" was added.

[0033] Furthermore, the example in Figure 7 shows that the temporary receipt data with temporary receipt ID "2" shown in Figure 4 corresponds to "1: Fully paid this time," and therefore the judgment result based on the bulk payment check master table 11 is a result that requires manual reconciliation processing, and the reconciliation result code "9: Error" is added. This "9: Error" indicates that the automatic reconciliation process has not completed successfully (= manual reconciliation processing is required).

[0034] Furthermore, the example in Figure 7 shows that the temporary receipt data with temporary receipt ID "3" shown in Figure 4 corresponds to "1: Bad debt exists," and therefore the judgment result based on the bulk payment check master table 11 is a judgment result that requires manual reconciliation processing, and the reconciliation result code "9: Error" is added.

[0035] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the memory unit 2, and functions as an error determination unit 21, an output control unit 22, a data generation unit 23, and a memory control unit 24, as shown in Figure 1.

[0036] In this example, the error determination unit 21 to the memory control unit 24 are described as being implemented in software based on the business support program, but all or part of the error determination unit 21 to the memory control unit 24 may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0037] The error determination unit 21 refers to the batch deposit check master table 11, which contains check execution flag information indicating whether manual reconciliation is required for each deposit route and deposit type, at least for each deposit route indicating bank transfer or account transfer for the deposit data (provisional receipt data), based on the deposit route and deposit type of the deposit data. The error determination unit 21 then determines, based on the batch deposit check master table 11, whether the deposit data (provisional receipt data) is deposit data that requires manual reconciliation.

[0038] The output control unit 22 outputs extracted result data (reconciliation result data as exemplified in Figure 7) for each deposit data, including the judgment result of the error judgment unit 21, the deposit route, and the deposit type, to the output target device (see Figure 9). The output target device corresponds to, for example, the output device 7, and can be a display device, a printing device, or a speaker device. The output control unit 22 converts the extracted result data (reconciliation result data) into display information, print information, or audio information and supplies it to the corresponding device. This makes it possible to obtain display output, print output, or audio output of the extracted result data (reconciliation result data). In addition, the output target device can be the storage unit 2, an external storage device, or a server device on the network 50, and the extracted result data (reconciliation result data) may be output to or transmitted to these devices for storage.

[0039] Furthermore, the output control unit 22 selects the extracted data of payment data that requires manual reconciliation from the payment data that does not require manual reconciliation and the payment data that requires manual reconciliation, and outputs it to the output device. In other words, the output control unit 22 controls the output of only the extracted data of payment data that requires manual reconciliation to the output device 7, etc. This makes it possible to clearly identify the payment data that requires manual reconciliation to the person in charge.

[0040] (Bulk payment reconciliation operation) Next, the batch payment reconciliation operation in the business support device 1 of this embodiment will be described.

[0041] First, when the person in charge specifies batch payment reconciliation via the input device 6, the output control unit 22 displays a list of the file names of the transfer payment files and account transfer files stored in the import file storage unit 12 via the output device 7 on the batch payment reconciliation screen illustrated in Figure 8.

[0042] The person in charge selects the files to be included in the bulk payment reconciliation process (the files to be executed) from the bank transfer and direct debit files displayed on this bulk payment reconciliation screen (by checking the checkboxes). Then, the person in charge clicks the "Register" button displayed on the bulk payment reconciliation screen.

[0043] When the "Register" button displayed on the bulk payment reconciliation screen is pressed, the output control unit 22 displays the provisional receipt list screen illustrated in Figure 9 via the output device 7. This provisional receipt list screen displays input fields for search criteria, a display field for extraction results, and a "Reconcile" button to specify the start of the bulk payment reconciliation process.

[0044] The person in charge enters a reconciliation code (and, if necessary, the date of receipt) in the search criteria input field. This code specifies which reconciliation result data to display in the extracted results display field, from the reconciliation result data indicating temporary receipts for which the reconciliation process has been successfully completed (see Figure 7) and the reconciliation result data indicating temporary receipts for which manual reconciliation processing is required (see Figure 7). The example in Figure 9 shows an example where the reconciliation code "9: Error" is entered in the search criteria input field, specifying the display of only the reconciliation result data indicating temporary receipts for which manual reconciliation processing is required.

[0045] To display only the reconciliation result data for temporary receipts for which the reconciliation process has been successfully completed, enter the reconciliation code "1: Successful Completion" in the reconciliation condition input field. To display both the reconciliation result data for temporary receipts for which the reconciliation process has been successfully completed and the reconciliation result data for temporary receipts that require manual reconciliation, enter the reconciliation code "0: Both" in the reconciliation condition input field.

[0046] Next, when the person in charge enters the search criteria via the temporary receipt list screen and operates the "Reconciliation" button to specify the start of the batch payment reconciliation process, the control unit 3 executes the batch payment reconciliation process shown in Figures 10 and 11 based on the business support program stored in the memory unit 2. Note that the flowcharts in Figures 10 and 11 are a series of flowcharts, and the processes are executed sequentially from step S1.

[0047] In other words, when the "Reconciliation" button is pressed, in step S1 of the flowchart in Figure 10, the memory control unit 24 retrieves the temporary receipt data from the temporary receipt data storage unit 13 shown in Figure 4 that corresponds to the file specified as the target for execution on the batch payment reconciliation screen shown in Figure 8.

[0048] Specifically, in the example shown in Figure 8, since the bank transfer deposit file and the direct debit file are specified as execution targets, the storage control unit 24 acquires the temporary receipt data shown in Figure 4, specifically the temporary receipt data with a deposit route of "1: Bank Transfer Deposit" and the temporary receipt data with a deposit route of "2: Direct Debit".

[0049] The processes in steps S2 to S4 of the flowchart in Figure 10 and steps S5 to S11 of the flowchart in Figure 11 are processes that are repeatedly executed (looped) for each temporary receipt data.

[0050] In other words, among the temporary receipt data acquired by the memory control unit 24, the first temporary receipt data is processed using steps S2 to S11, then the second temporary receipt data is processed using steps S2 to S11, and so on, with the processing of steps S2 to S11 being repeatedly executed for each temporary receipt data.

[0051] In step S2, the error determination unit 21 determines whether the temporary receipt data is subject to a bad debt check. In this example, each temporary receipt data shown in Figure 4 is subject to a bad debt check (step S2: Yes), so the process proceeds to step S3.

[0052] If the temporary receipt data is not subject to the bad debt check (Step S2: No), the process proceeds to Step S4.

[0053] If the transaction is deemed to be subject to a bad debt check (Step S2: Yes), and the process proceeds to Step S3, the error determination unit 21 refers to the bad debt flag in the debt data storage unit 14 shown in Figure 5, based on the reconciliation debt ID of the temporary receipt data. In this example, the bad debt flag for the debt data corresponding to the reconciliation debt ID "1" in the temporary receipt data is "0". Therefore, the error determination unit 21 determines that this temporary receipt data is not a bad debt (Step S3: No), and proceeds to Step S5 in Figure 11.

[0054] In contrast, if the bad debt flag is set to "1," as is the case with the debt data corresponding to the reconciliation debt ID "2" in the provisional receipt data, the error determination unit 21 determines that the provisional receipt data is a bad debt that is subject to manual reconciliation (step S3: Yes), and proceeds to step S4.

[0055] In step S4, the data generation unit 23 refers to the batch payment check master table 11 shown in Figure 2, based on the payment route of the provisional receipt data and the type of payment for "bad debts" determined by the error determination unit 21. As shown in Figure 2, in both cases, whether the payment route of the provisional receipt data is "bank transfer" or "account transfer", the check execution flag information for the provisional receipt data for "bad debts" will be a check execution flag of "1", indicating that manual reconciliation is required.

[0056] Therefore, in step S4, the data generation unit 23 generates reconciliation result data with the reconciliation result code set to "9: Error," indicating that manual reconciliation is required, and the error check type code set to "2: Bad debt exists." The storage control unit 24 stores the generated reconciliation result data in the reconciliation result data storage unit 16. The reconciliation result data for the provisional receipt ID "3" shown in Figure 7 corresponds to the reconciliation result data with the reconciliation result code set to "9: Error" and the error check type code set to "2: Bad debt exists."

[0057] Next, when it is determined that the receivable is not a bad debt (Step S3: No), the process proceeds to Step S5 in Figure 11, where the error determination unit 21 determines whether the temporary receipt data is subject to a full repayment check this time. In this example, each temporary receipt data shown in Figure 4 is subject to a full repayment check this time (Step S5: Yes), so the process proceeds to Step S6.

[0058] If the provisional receipt data is not subject to the full repayment check this time (Step S5: No), the process will proceed to Step S8.

[0059] If the payment is deemed to be subject to a full payment check (Step S5: Yes), the process proceeds to Step S6. The error determination unit 21 then refers to the claim data storage unit 14 based on the reconciliation claim ID (=claim ID) of the provisional receipt data and the amount received. The error determination unit 21 then compares the amount received in the provisional receipt data with the outstanding claim balance stored in the claim data storage unit 14 to determine whether the payment has resulted in full payment (whether the payment is complete this time or not).

[0060] If the amount of the deposit in the provisional receipt data and the outstanding balance of the debt stored in the debt data storage unit 14 are the same amount, and the error determination unit 21 determines that the debt has been fully repaid with this deposit (Step S6: Yes), the data generation unit 23 refers to the batch deposit check master table 11 based on the type of deposit that has been fully repaid and the deposit route of the provisional receipt data.

[0061] In the example of the batch payment check master table 11 in Figure 2, if the payment route for the temporary receipt data is "1: Bank transfer," the check execution flag information corresponding to the payment type "Fully paid this time" is a check execution flag of "1," indicating that manual reconciliation is required. On the other hand, if the payment route for the temporary receipt data is "2: Account transfer," the check execution flag information corresponding to the payment type "Fully paid this time" is a check execution flag of "0," indicating that manual reconciliation is not required.

[0062] If the check execution flag information corresponding to the deposit route and deposit type of the provisional receipt data is a check execution flag of "1" indicating that manual reconciliation is required, the data generation unit 23 generates reconciliation result data in step S7 with the reconciliation result code set to "9: Error" and the error check type code set to "1: Completed this time". The storage control unit 24 stores this reconciliation result data in the reconciliation result data storage unit 16.

[0063] Among the reconciliation result data shown in Figure 7, the reconciliation result data with a provisional receipt ID of "2" is the reconciliation result data with the reconciliation result code set to "9: Error" and the error check type code set to "1: Paid in full this time".

[0064] Next, in step S6, it is determined that the current deposit does not constitute full repayment (step S6: No), and the process proceeds to step S8. At this point, the error determination unit 21 determines whether the temporary receipt data is subject to a deposit generation check. In this example, each temporary receipt data shown in Figure 4 is subject to a deposit generation check (step S8: Yes), so the process proceeds to step S9.

[0065] If the temporary receipt data is not subject to the deposit generation check (Step S8: No), the process proceeds to Step S11.

[0066] If the transaction is deemed eligible for a deposit check (Step S8: Yes), the process proceeds to Step S9. The error determination unit 21 then refers to the invoice data storage unit 15 based on the reconciliation claim ID (=claim ID) of the provisional receipt data and the amount received. The error determination unit 21 then compares the amount received in the provisional receipt data with the invoice amount stored in the invoice data storage unit 15 and determines whether a deposit has been generated (deposit amount > 0) because the amount received is greater than or equal to the invoice amount.

[0067] When it is determined that a deposit has been made because the amount received is greater than or equal to the invoiced amount (Step S9: Yes), the data generation unit 23 refers to the batch deposit check master table 11 based on the deposit type "deposit made" and the deposit route of the provisional receipt data.

[0068] In the example of the batch deposit check master table 11 in Figure 2, in both cases where the deposit route for the temporary receipt data is "1: bank transfer" and "2: direct debit," the check execution flag information corresponding to the deposit type of "deposit generated" is a check execution flag of "1," indicating that manual reconciliation is required.

[0069] If the check execution flag information corresponding to the deposit route and deposit type of the provisional receipt data is a check execution flag of "1" indicating that manual reconciliation is required, the data generation unit 23 generates reconciliation result data in step S10 with the reconciliation result code set to "9: Error" and the error check type code set to "3: Deposit Occurred". The storage control unit 24 stores this reconciliation result data in the reconciliation result data storage unit 16.

[0070] Next, if the provisional receipt data is not a "bad debt," is not "fully repaid this time," and "no deposit is generated," the data generation unit 23 refers to the debt data storage unit 14 based on the reconciliation debt ID and the amount received in the provisional receipt data, and automatically reconciles the debt balance of the corresponding debt data (automatic reconciliation function).

[0071] Then, in step S11, the data generation unit 23 generates reconciliation result data with the reconciliation result code set to "1: Successful completion" and the error check type code set to "blank". The temporary receipt ID "1" shown in Figure 7, the reconciliation result data with the reconciliation result code "1: Successful completion" and the error check type code set to "blank" corresponds to this "1: Successful completion" temporary receipt data. The storage control unit 24 stores the generated reconciliation result data in the reconciliation result data storage unit 16.

[0072] The control unit 3 repeatedly performs the processing described in steps S2 to S11 for each temporary receipt data. As a result, the settlement result data for each temporary receipt data, as illustrated in Figure 7, is stored in the settlement result data storage unit 16.

[0073] (Display operation of reconciliation result data) Next, the example in Figure 9 shows an example where the search condition "9: Error" is entered in the reconciliation code input field in order to specify that reconciliation result data requiring manual reconciliation should be displayed as a search condition. In this case, the output control unit 22 obtains the reconciliation result data for "1: Fully Paid This Time" for temporary receipt ID "2" which has the reconciliation result code "9: Error" attached, and the reconciliation result data for "2: Bad Debt Exists" for temporary receipt ID "3" which has the reconciliation result code "9: Error" attached, from the reconciliation result data shown in Figure 7.

[0074] Furthermore, the output control unit 22, based on the provisional receipt ID of the reconciliation result data that has the reconciliation result code "9: Error" attached, refers to the provisional receipt data storage unit 13 shown in Figure 4 to obtain the provisional receipt date and payment route of the provisional receipt data to which the provisional receipt ID of the reconciliation result data that has the reconciliation result code "9: Error" attached is attached.

[0075] The output control unit 22 then displays the acquired information, including the temporary receipt ID, temporary receipt date, payment route, reconciliation result code (9: error), and error check type code, in the detection result display field on the temporary receipt list screen shown in Figure 9.

[0076] This allows the person in charge to clearly identify temporary receipt data that requires manual reconciliation. The person in charge can then manually reconcile the temporary receipt data by selecting it in the display field of the detection results on the temporary receipt list screen. This allows for the completion of temporary receipt data reconciliation in a simple, accurate, and burdenless manner.

[0077] (Effects of the embodiment) As is clear from the above description, the business support device 1 of the embodiment, based on master settings, causes manual reconciliation to be performed as an error if the conditions are met. This enables the prior detection of operational errors and improves the efficiency of subsequent operations.

[0078] Furthermore, the ability to configure whether or not checks are performed for each payment route reduces the workload of staff and prevents operational errors. This prevents errors in processing amounts and avoids the inconvenience of sharing incorrect information with personal credit agencies.

[0079] Furthermore, the presence or absence of each check can be pre-configured in the master settings for each payment route. This prevents the inconvenience of having to customize the process according to the payment route for each reconciliation operation.

[0080] Furthermore, by stopping the process in advance due to an error, it becomes unnecessary to cancel automatically deposited information and manually redeposit the funds.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0098] The present invention is particularly suitable for application to the deposit reconciliation operations of the financial industry. [Explanation of symbols]

[0099] 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 11. Bulk Payment Check Master Table 12. Import File Storage Unit 13 Temporary Receipt Data Storage Unit 14. Debt Data Storage Unit 15. Billing Data Storage Unit 16. Data storage unit for reconciliation results 21 Error detection unit 22 Output control unit 23 Data Generation Unit 24 Memory Control Unit

Claims

1. A business support device that assists in the reconciliation of deposit data by performing name matching based on deposit data and automatically reconciling the balance of accounts receivable data, An error determination unit refers to a batch deposit check master table, which includes check execution flag information indicating whether manual reconciliation is required, set for each deposit route and deposit type, at least for each deposit route indicating bank transfer or account transfer of the deposit data, based on the deposit route and deposit type of the deposit data, and determines whether the deposit data is deposit data that requires manual reconciliation. An output control unit outputs extracted result data, including the judgment result of the error judgment unit, the payment route, and the type of payment for each payment data, to an output target device. A business support device characterized by having the following features.

2. The output control unit outputs the extracted data of payment data that requires manual reconciliation to the output target device, among the payment data that does not require manual reconciliation and the payment data that requires manual reconciliation. The business support device according to claim 1, characterized by the following:

3. The aforementioned types of payments are one or more of the following: bad debt, full repayment or deposit accrual, transaction after processing, prior to the last payment date, no settlement balance, no balance, settlement claim, claim for which the benefit of time has been lost, claim change registration, and delinquent payment. A business support device according to claim 1 or claim 2, characterized by the above.

4. A business support method executed by a business support device that supports the settlement of deposit data by performing name matching based on deposit data and automatically reconciling the balance of accounts receivable data, An error determination unit refers to a batch deposit check master table, which includes check execution flag information indicating whether manual reconciliation is required, set for each deposit route and deposit type, at least for each deposit route indicating bank transfer or direct debit of the deposit data, based on the deposit route and deposit type of the deposit data, and determines whether the deposit data is deposit data that requires manual reconciliation. Output control step: Outputs extracted result data, including the determination result of the error determination step, the payment route, and the type of payment for each payment data, to the output target device. A business support method characterized by having the following features.

5. A business support program that enables the computer of a business support device that supports the payment data reconciliation operation by performing name matching based on payment data and automatically reconciling the balance of accounts receivable data, The aforementioned computer, An error determination unit refers to a batch deposit check master table, which includes check execution flag information indicating whether manual reconciliation is required, set for each deposit route and deposit type, at least for each deposit route indicating bank transfer or account transfer of the deposit data, based on the deposit route and deposit type of the deposit data, and determines whether the deposit data is deposit data that requires manual reconciliation. To function as an output control unit that outputs extracted result data, including the judgment result of the error judgment unit, the payment route, and the type of payment for each payment data, to the output target device. A business support program characterized by the following:

Images