Work support device, work support method, and work support program

Abstract

To accurately select a desired deposit file.SOLUTION: An acquisition part acquires a deposit file provided with a header record including a bank account and a date when deposit is performed by transfer or account transfer and a data record including user information for specifying a user who performs the deposit to the bank account by the transfer or the account transfer and an amount. The data generation unit refers to a storage unit in which capture information to be captured from a deposit file is set for each of a deposit route by transfer and a deposit route by account transfer, and generates capture history data including the capture information corresponding to the deposit route acquired from the deposit file. The output control unit outputs the generated capture history data to the output target device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] Patent document 1 (JP Patent Publication No. 2021-135737) discloses a deposit reconciliation processing device that can automatically sort between two patterns based on specified conditions: one in which the deposit reconciliation process is performed during deposit processing, and one in which the deposit confirmation process is performed during deposit processing and the deposit reconciliation process is performed separately.

[0003] This payment reconciliation processing device acquires payment data including billing destination data and payment amount, and if the payment data meets predetermined conditions based on the billing data, acquires confirmed payment data that makes the payment data unchangeable, and acquires reconciliation data for the confirmed payment data. This makes it possible to automatically allocate each of the above patterns. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2021-135737 Summary of the Invention [Problem to be solved by the invention]

[0005] Here, there are different types of deposit files for each deposit route, such as a bank transfer deposit details file and an account transfer reflection result file, etc. Therefore, when selecting a deposit file, if the file is selected based on the file name and the file import date and time, the wrong deposit file may be imported.

[0006] The present invention has been made in view of the above-mentioned problems, and has as its object to provide a business support device, a business support method, and a business support program that enable a desired deposit file to be accurately selected. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the objectives, the business support device of the present invention has an acquisition unit that acquires a deposit file having a header record including the bank account and date to which the deposit was made by bank transfer or direct debit, and a data record including user information and amount for identifying the user who made the deposit to the bank account by bank transfer or direct debit, a data generation unit that references a memory unit in which import information to be imported from the deposit file is set for each deposit route by bank transfer and deposit route by direct debit, and generates import history data acquired from the deposit file including import information corresponding to the deposit route, and an output control unit that outputs the generated import history data to an output target device.

[0008] In addition, in order to solve the above-mentioned problems and achieve the objective, the business support method of the present invention includes an acquisition step in which an acquisition unit acquires a deposit file having a header record including the bank account and date to which the deposit was made by bank transfer or direct debit, and a data record including user information and amount for identifying the user who made the deposit to the bank account by bank transfer or direct debit; a data generation step in which a data generation unit references a memory unit in which import information to be imported from the deposit file for the deposit route by bank transfer and the deposit route by direct debit is set, and generates import history data obtained from the deposit file including the import information corresponding to the deposit route; and an output control step in which an output control unit outputs the generated import history data to an output target device.

[0009] In addition, in order to solve the above-mentioned problems and achieve the objective, the business support program of the present invention causes a computer to function as an acquisition unit that acquires a deposit file having a header record including the bank account and date to which a deposit was made by bank transfer or direct debit, and a data record including user information and the amount for identifying the user who made the deposit to the bank account by bank transfer or direct debit; a data generation unit that references a memory unit in which import information to be imported from the deposit file is set for each deposit route by bank transfer and deposit route by direct debit, and generates import history data acquired from the deposit file including the import information corresponding to the deposit route; and an output control unit that outputs the generated import history data to an output target device. [Effects of the Invention]

[0010] The present invention allows for the precise selection of the desired deposit file. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram illustrating a hardware configuration of a task assistance device according to an embodiment. [Figure 2] FIG. 2 shows an example of the account transfer master table, the transfer deposit master table, and the update setting master table. [Figure 3] FIG. 3 is a diagram showing an example of a transfer deposit file import screen. [Figure 4] FIG. 4 is a diagram showing an example of a header record and data records included in a deposit file, which are stored in the deposit file detail data storage unit. [Figure 5] FIG. 5 is a diagram illustrating an example of the capture history data stored in the capture history data storage unit. [Figure 6] FIG. 6 is a diagram showing an example of the deposit file detail data stored in the deposit file detail data storage unit. [Figure 7] FIG. 7 is a diagram showing an example of the temporary receipt data stored in the temporary receipt data storage unit. [Figure 8]FIG. 8 is a diagram showing an example of a header record and data records generated based on the deposit file of the first transfer deposit imported. [Figure 9] FIG. 9 is a diagram showing an example of import history data generated based on the deposit file of the first imported transfer deposit. [Figure 10] FIG. 10 is a diagram showing an example of deposit file detail data generated based on the number of data records in the deposit file for the first transfer deposit and the import file ID of the import history data. [Figure 11] FIG. 11 is a diagram showing an example of temporary receipt data generated based on the temporary receipt ID in the deposit file and deposit file detail data of the first transfer deposit imported. [Figure 12] FIG. 12 is a diagram showing an example of a header record and data records generated based on the deposit file of the second transfer deposit imported. [Figure 13] FIG. 13 is a diagram showing an example of import history data generated based on the deposit file of the second imported transfer deposit. [Figure 14] FIG. 14 is a diagram showing an example of deposit file detail data generated based on the number of data records in the deposit file for the second transfer deposit imported and the imported file ID of the import history data. [Figure 15] FIG. 15 is a diagram showing an example of temporary receipt data generated based on the temporary receipt ID of the deposit file and the deposit file detail data of the second transfer deposit imported. [Figure 16] FIG. 16 is a diagram showing an example of the account transfer result file import screen. [Figure 17] FIG. 17 is a diagram showing an example of a header record and data records generated based on the imported account transfer deposit file. [Figure 18] FIG. 18 is a diagram showing an example of import history data generated based on a deposit file for account transfer. [Figure 19]FIG. 19 is a diagram showing an example of deposit file detail data generated based on the number of data records in the deposit file for account transfer and the import file ID of the import history data. [Figure 20] FIG. 20 is a diagram showing an example of temporary receipt data generated based on the temporary receipt ID of the deposit file of the account transfer and the deposit file detail data. [Figure 21] FIG. 21 is a diagram showing an example of the lump-sum payment reconciliation screen. [Figure 22] FIG. 22 is a diagram showing how the payment reconciliation process corresponding to the import file information selected on the lump-sum payment reconciliation screen is carried out. [Figure 23] FIG. 23 is a diagram showing an example of the reminder result update screen. [Figure 24] FIG. 24 is a flowchart showing the flow of the operation for importing a deposit file. [Figure 25] FIG. 25 is a diagram for explaining an example of generating a header record and a data record based on a deposit file for a transfer. [Figure 26] FIG. 26 is a diagram for explaining how to create an item list. [Figure 27] FIG. 27 is a diagram for explaining how to generate imported file information based on the update setting master table and the item list. DETAILED DESCRIPTION OF THE INVENTION

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A task support device according to an embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the following embodiment.

[0013] [Configuration of the embodiment] (Hardware configuration) 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. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 corresponds to 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 cooperates with a mouse device to realize a pointing device function.

[0014] The communication interface unit 4 is connected to a network 50, which may be a wide area network such as the Internet or a private network such as a LAN (Local Area Network). A file server device 51 and / or a file providing site terminal device 52 are connected to the network 50.

[0015] The file server device 51 and / or the file providing site terminal device 52 are the source of the deposit file, and the provided deposit file is a text file created in the Japanese Bankers Association format. A file created in this Japanese Bankers Association format consists of four different types of records (header record, data record, trailer record, and end record) per file.

[0016] The storage unit 2 may be, for example, a read-only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD). The storage unit 2 stores a business support program that enables the user to accurately select a desired deposit file.

[0017] In addition, this memory unit 2 is provided with an account transfer master table 11, a transfer deposit master table 12, an update setting master table 13, a file memory unit 14, an import history data memory unit 15, a deposit file detail data memory unit 16, a provisional receipt data memory unit 17, and an item list memory unit 18.

[0018] As shown in Figure 2(a), the account transfer master table 11 stores deposit route codes corresponding to the deposit routes for account transfers. As shown in Figure 2(b), the bank transfer deposit master table 12 stores deposit route codes corresponding to the deposit routes for bank transfers. As shown in Figure 2(c), the update setting master table 13 stores the type (item) of imported information obtained from the deposit file for each of the above-mentioned deposit routes. The numbers "0", "1", etc. shown in Figure 2(c) indicate item identification information (item ID) in the item list described below.

[0019] That is, in the item list, the import information of the deposit file is set for each item ID, which is a descending number. These item IDs correspond to the numbers set in the update setting master table 13. Therefore, by obtaining the import information of the item ID that is the same as the number set in the update setting master table 13, import history data is generated. This will be described in more detail later.

[0020] The file storage unit 14 stores a header record, an example of which is shown in FIG. 4(a), and a data record, an example of which is shown in FIG. 4(b), which are generated based on the deposit file.

[0021] The import history data storage unit 15 stores import history data that is generated by acquiring acquisition information according to the deposit route of the deposit file from the header record and data record of the deposit file.

[0022] The deposit file detail data storage unit 16 stores the deposit file detail data shown in FIG. 6, which is generated by associating the import file ID of the import history data with the number of temporary receipt IDs corresponding to the number of data records.

[0023] The provisional receipt data storage unit 17 stores provisional receipt data as illustrated in Figure 7, which is generated by associating the provisional receipt date and provisional receipt corresponding to the accounting date and transaction amount included in the data record with the provisional receipt ID.

[0024] The item list storage unit 18 stores an item list generated by acquiring acquired information (item values) corresponding to the item IDs in descending order from the header record or data record of the deposit file.

[0025] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, thereby functioning as an acquisition unit 21, a data generation unit 22, an output control unit 23, and a deposit reconciliation processing unit 24, as shown in Figure 1.

[0026] In this example, the acquisition unit 21 to the deposit reconciliation processing unit 24 are described as being realized by software based on a business support program, but all or part of the acquisition unit 21 to the deposit reconciliation processing unit 24 may also be realized by hardware. In either case, the same effects as those described below can be obtained.

[0027] The acquisition unit 21 acquires a deposit file that includes a header record including the bank account and date to which the deposit was made by bank transfer or direct debit, and a data record including user information for identifying the user who made the deposit to the bank account by bank transfer or direct debit and the amount. As an example, this deposit file can be a file created in the above-mentioned Japanese Bankers Association format.

[0028] The data generation unit 22 refers to the storage unit (update setting master table 13 in FIG. 2(c)) in which the import information to be imported from the deposit file is set for the deposit route by bank transfer and the deposit route by account transfer. Then, the data generation unit 22 generates import history data including the import information corresponding to the deposit route obtained from the deposit file (see FIG. 5).

[0029] The output control unit 23 outputs the generated capture history data to an output target device. This output target device can be a display device, a printing device, or a speaker device. The output control unit 23 converts the capture history data into display information, print information, or audio information and supplies it to each device, thereby obtaining a display output, print output, or audio output corresponding to the capture history data. The output target device can also be the storage unit 2, an external storage device, a server device on the network 50, or the like.

[0030] The data generation unit 22 generates import history data with each data piece having unique import file identification information attached (see Figure 5), and also generates provisional receipt data (see Figure 7) including the deposited amount and date corresponding to the import history data with the imported file identification information attached, based on the deposit file.

[0031] The output control unit 23 displays the import history data on the display unit (output device 7). When import history data corresponding to the deposit reconciliation process is selected via this display unit, the deposit reconciliation processing unit 24 performs the deposit reconciliation process on the temporary receipt data corresponding to the import file identification information added to the selected import history data (see Figure 22).

[0032] The data generation unit 22 also generates an item list in which the import information of a predetermined deposit file is associated and stored as an item value corresponding to each item identification information (see Fig. 26).The data generation unit 22 also references a storage unit (the update setting master table 13 in Fig. 2(c)) in which item identification information corresponding to the import information acquired in accordance with the deposit route is stored, and acquires import information corresponding to the item identification information from the item list to generate import history data (see Fig. 27).

[0033] [Operation of the embodiment] Next, we will explain the operation of the deposit reconciliation process in the business support device 1 of this embodiment configured as described above. When performing this deposit reconciliation process, first a deposit file is imported, and from this imported deposit file, acquisition information corresponding to the deposit route is selectively acquired to generate import history data. Furthermore, based on the imported deposit file, temporary receipt data including the import date and amount is generated. Then, the import history data is displayed in list form via the output device 7, and the temporary receipt data corresponding to the import history data selected by the user is reconciled, thereby performing the desired deposit reconciliation process.

[0034] (Importing deposit file) As an example, a case will be described below in which a deposit file for a bank transfer is imported twice, and then a deposit file for an account transfer is imported once.

[0035] (First import operation of the bank transfer deposit file) When importing a deposit file, the person in charge specifies the display of the transfer deposit file import screen. This causes the output control unit 23 to display the transfer deposit file import screen shown in Figure 3 via the output device 7. The person in charge specifies the deposit file to be imported on this transfer deposit file import screen and operates the import button. In the example of Figure 3, the "transfer deposit" deposit file is specified as the deposit file to be imported.

[0036] The data generation unit 22 generates a header record shown in Fig. 8(a) and a data record shown in Fig. 8(b) based on a deposit file that is imported from the file server device 51 or the file providing site terminal device 52 shown in Fig. 1 and stored in the file storage unit 14. As shown in Fig. 8(a), the header record includes the creation date, accounting date (from), and accounting date (to) of the deposit file. The header record also includes the bank code, bank name, branch code, branch name, deposit type, and account number of the bank where the transfer deposit was made.

[0037] The data record includes the accounting date, deposit / withdrawal date, receipt / payment category, transaction category, transaction amount, including the amount of other bank notes, exchange / presentation date, dishonored return date, bill / check category, bill / check number, affiliated branch number, transfer applicant code, and transfer applicant name. The example in Figure 8(b) shows a transfer of 100,000 yen from "Yamada XX" on "May 1, 2024," and also a transfer of 200,000 yen from "Tanaka XX" on the same day. Therefore, there are two data records.

[0038] Next, the data generation unit 22 refers to the account transfer master table 11 shown in Figure 2(a) or the transfer deposit master table 12 shown in Figure 2(b) based on the deposit route (bank transfer deposit or account transfer deposit) specified on the bank transfer deposit file import screen, and detects the deposit route code corresponding to the deposit route. In this example, the deposit route is "bank transfer deposit", so the data generation unit 22 detects the deposit route code of "1" by referring to the bank transfer deposit master table 12 shown in Figure 2(b).

[0039] Next, the data generating unit 22 refers to the update setting master table 13 shown in FIG. 2(c) and recognizes the capture information that is preset for the deposit route code of "1" (=preset for transfer deposits).

[0040] Then, the data generation unit 22 generates the import history data illustrated in Figure 9, which includes the import information obtained from the deposit file corresponding to the deposit route code of "1" indicated in the update setting master table 13, and stores it in the import history data storage unit 15.

[0041] In the example of Fig. 2, the acquisition information corresponding to the deposit route code of "1" is set as "acquisition date and time, file name, number of entries, amount of entries, bank code, bank name, branch code, and branch name." Therefore, as shown in Fig. 9, the data generation unit 22 generates acquisition history data including the acquisition date and time of "May 1, 2024, 15:00:00," the file name of "Transfer Deposit.txt (text)," the number of entries of "2," the amount of entries of "300,000 yen," the bank code of "9991," the bank name of "Daiichi XX Ginkou," the branch code of "991," and the branch name of "Daiichi Shiten," and adds an acquisition file ID of "1."

[0042] In addition, in this example, since there are two data records as shown in Figure 8(b), the data generation unit 22 generates deposit file detail data in which the import file ID of "1" is associated with the temporary deposit IDs of "1" and "2" as shown in Figure 10, and stores this in the deposit file detail data storage unit 16.

[0043] Furthermore, as illustrated in Figure 11, the data generation unit 22 generates suspense receipt data in which the suspense receipt ID "1" is associated with the suspense receipt of "100,000 yen" indicating the transaction amount of the first data record shown in Figure 8(b) and the accounting date of "May 1, 2024." The data generation unit 22 also generates suspense receipt data in which the suspense receipt ID "2" is associated with the suspense receipt of "200,000 yen" indicating the transaction amount of the second data record shown in Figure 8(b) and the accounting date of "May 1, 2024." The data generation unit 22 then stores each of the generated suspense receipt data in the suspense receipt data storage unit 17.

[0044] (Second import operation of the bank transfer deposit file) Next, when importing the transfer deposit file for the second time, the person in charge will specify the display of the transfer deposit file import screen, as described above. This will cause the output control unit 23 to display the transfer deposit file import screen shown in Figure 3 via the output device 7. The person in charge will specify the deposit file to be imported on this transfer deposit file import screen and operate the import button. Let's assume that the "transfer deposit" deposit file is also specified as the deposit file to be imported this second time.

[0045] The data generation unit 22 generates a header record shown in Figure 12(a) and a data record shown in Figure 12(b) based on the deposit file imported from the file server device 51 or the file providing site terminal device 52 shown in Figure 1 and stored in the file memory unit 14.

[0046] In the case of the deposit file imported the second time, as shown in Figure 12(a), the creation date and accounting date are "May 1, 2024", and it is a deposit to the "Dainishiten" bank account of "Dainishi XX Ginkou". Also, as shown in Figure 12(b), it is an example of deposits of "300,000 yen", "400,000 yen", and "500,000 yen" from "Suzuki XX", "Sato XX", and "Takahashi XX", respectively. Therefore, there are three data records.

[0047] Next, the data generation unit 22 refers to the account transfer master table 11 shown in Figure 2(a) or the transfer deposit master table 12 shown in Figure 2(b) based on the deposit route specified on the transfer deposit file import screen, and detects the deposit route code corresponding to the deposit route. In this example, the deposit route is "transfer deposit", so the data generation unit 22 detects the deposit route code of "1" by referring to the transfer deposit master table 12 shown in Figure 2(b).

[0048] Next, the data generating unit 22 refers to the update setting master table 13 shown in FIG. 2(c) and recognizes the capture information that is preset for the deposit route code of "1" (=preset for transfer deposits).

[0049] Then, the data generation unit 22 generates the import history data illustrated in Figure 13, which includes the import information obtained from the deposit file corresponding to the deposit route code of "1" indicated in the update setting master table 13, and stores it in the import history data storage unit 15.

[0050] In the example of Fig. 2, the acquisition information corresponding to the deposit route code "1" is set as "acquisition date and time, file name, number of entries, amount of entries, bank code, bank name, branch code and branch name." Therefore, as shown in Fig. 13, the data generation unit 22 generates acquisition history data including the acquisition date and time of "May 1, 2024, 15:00:00," the file name of "Transfer Deposit.txt (text)," the number of entries of "3," the amount of entries of "1.2 million yen," the bank code of "9992," the bank name of "Dainixxginkou," the branch code of "992," and the branch name of "Dainishiten," and adds an acquisition file ID of "2."

[0051] In addition, in this example, since there are three data records as shown in Figure 12(b), the data generation unit 22 generates deposit file detail data in which the import file ID of "2" is associated with the temporary deposit IDs of "3", "4", and "5", as shown in Figure 14, and stores this in the deposit file detail data storage unit 16.

[0052] The data generation unit 22 also generates suspense receipt data by associating the suspense receipt ID "3" with the suspense receipt of "300,000 yen" indicating the transaction amount of the first data record shown in FIG. 12(b) and the accounting date of "May 1, 2024." The data generation unit 22 also generates suspense receipt data by associating the suspense receipt ID "3" with the suspense receipt of "400,000 yen" indicating the transaction amount of the second data record shown in FIG. 12(b) and the accounting date of "May 1, 2024." The data generation unit 22 also generates suspense receipt data by associating the suspense receipt ID "5" with the suspense receipt of "500,000 yen" indicating the transaction amount of the third data record shown in FIG. 12(b) and the accounting date of "May 1, 2024." The data generation unit 22 then stores each of the generated suspense receipt data in the suspense receipt data storage unit 17.

[0053] (Importing of account transfer deposit file) The above explanation was an example of importing a deposit file for a bank transfer, but when importing a deposit file for an account transfer, the person in charge specifies the display of the account transfer result file import screen. This causes the output control unit 23 to display the account transfer result file import screen shown in Figure 16 via the output device 7. The person in charge specifies the agent code, settlement date, transfer year and month, transfer date, and import file on this account transfer result file import screen, and operates the import button. In the example of Figure 16, a deposit file for an account transfer from "XX agent" is specified as the deposit file to be imported.

[0054] The data generation unit 22 generates a header record shown in Fig. 17(a) and a data record shown in Fig. 17(b) based on a deposit file that is imported from the file server device 51 or the file providing site terminal device 52 shown in Fig. 1 and stored in the file storage unit 14. As shown in Fig. 17(a), the header record includes the entrustor code, entrustor name, and transfer date of the deposit file. The header record also includes the bank number, bank name, branch number, branch name, deposit type, and deposit account number of the bank that performed the transfer.

[0055] The data record includes the debit bank number, debit bank name, debit branch number, debit branch name, deposit type, account number, depositor name, billing amount, new code, trustor code, customer number, and transfer result code. The examples in Figures 17(a) and 17(b) show an example where "600,000 yen" was debited from "Yamada XX's Daiyon XX Ginkou" by "XX Agent" on "May 1, 2024." The examples in Figures 17(a) and 17(b) also show an example where "700,000 yen" was debited from "Tanaka XX's Daigo XX Ginkou" by "XX Agent" on "May 1, 2024." Therefore, there are two data records.

[0056] Next, the data generation unit 22 refers to the account transfer master table 11 shown in Figure 2(a) or the transfer deposit master table 12 shown in Figure 2(b) based on the deposit route (account transfer deposit) specified on the account transfer result file import screen, and detects the deposit route code corresponding to the deposit route. In this example, the deposit route is "account transfer deposit", so the data generation unit 22 detects the deposit route code of "2" by referring to the transfer deposit master table 12 shown in Figure 2(a).

[0057] Next, the data generation unit 22 refers to the update setting master table 13 shown in FIG. 2(c) and recognizes the import information that is preset for the deposit route code of "2" (=preset for account transfer deposits).

[0058] Then, the data generation unit 22 generates the import history data illustrated in Figure 18, which includes the import information obtained from the deposit file corresponding to the deposit route code of "2" indicated in the update setting master table 13, and stores it in the import history data storage unit 15.

[0059] In the example of Fig. 2, "acquisition date and time, file name, number of imports, amount of import, trustor code, and trustor name" are set as the acquisition information corresponding to the deposit route code of "2." Therefore, as shown in Fig. 18, the data generation unit 22 generates acquisition history data including the acquisition date and time of "May 1, 2024, 15:00:00," the file name of "Account Transfer.txt (text)," the number of imports of "2," the amount of import of "1.3 million yen," the trustor code of "1," and the trustor name of "XX Industrial Company," and adds an acquisition file ID of "3."

[0060] In addition, in this example, since there are two data records as shown in Figure 17(b), the data generation unit 22 generates deposit file detail data in which the import file ID of "3" is associated with the temporary deposit IDs of "6" and "7", as shown in Figure 19, and stores this in the deposit file detail data storage unit 16.

[0061] Furthermore, as illustrated in Figure 20, the data generation unit 22 generates suspense receipt data in which the suspense receipt ID "6" is associated with the suspense receipt of "600,000 yen" indicating the transaction amount of the first data record shown in Figure 17(b) and the accounting date of "May 1, 2024." The data generation unit 22 also generates suspense receipt data in which the suspense receipt ID "7" is associated with the suspense receipt of "700,000 yen" indicating the transaction amount of the second data record shown in Figure 17(b) and the accounting date of "May 1, 2024." The data generation unit 22 then stores each of the generated suspense receipt data in the suspense receipt data storage unit 17.

[0062] Next, by displaying a list of the import history data thus generated, the desired deposit file can be accurately selected and the required processing can be performed. For example, when performing a deposit reconciliation process, the person in charge specifies the display of the lump-sum deposit reconciliation screen.

[0063] The output control unit 23 reads out the import history data stored in the import history data storage unit 15 and displays it as a list on the lump-sum deposit reconciliation screen as import file information including the import date, file name, number of imports, import amount, bank code or entrustor code, etc., as illustrated in Figure 21.

[0064] This allows the user to accurately select the desired deposit file, and also greatly simplifies the process of selecting the desired deposit file, improving work efficiency.

[0065] In addition, although the header data of the deposit file in the Japan Bankers Association format is fixed in length, even in this case, the desired information is selectively acquired and displayed, making it easy to recognize the desired header data.

[0066] Furthermore, among the information (items) of each imported header data, the items the user needs can be displayed by setting the update setting master table 13. This prevents the inconvenience of displaying all the information in the header data and taking time to confirm the information, and allows for efficient selection of the deposit file. Furthermore, because the contents of the file (header data) can be displayed on the screen, it is possible to reduce mistakes in selecting the desired deposit file and improve the accuracy when selecting the deposit file.

[0067] Furthermore, even if the information obtained from the deposit file differs for each company or user, it can be adjusted by the master settings of the update setting master table 13, thereby reducing the effort required to customize the information obtained for each company or user.

[0068] Next, the output control unit 23 displays a check box next to each imported file information for specifying whether or not to perform payment cancellation. The person in charge enters a check mark (a tick mark) in the check box provided adjacent to the imported file information for which payment cancellation is to be performed. Figure 21 shows an example in which a check mark is entered in the check box to make the imported file information of the top record the target for payment cancellation.

[0069] When the import file information for deposit reconciliation is selected in this way and the execute button on the lump sum deposit reconciliation screen is operated, the deposit reconciliation processing unit 24 references the deposit file detail data stored in the deposit file detail data storage unit 16 based on the import file ID of the selected import file information, as shown in Figures 22(a) and 22(b), and detects the temporary receipt ID corresponding to the import file ID. In this example, temporary receipt IDs "1" and "2" are detected as temporary receipt IDs corresponding to the import file ID of "1".

[0070] Next, based on the detected temporary receipt IDs "1" and "2", the deposit reconciliation processing unit 24 references the temporary receipt data stored in the temporary receipt data storage unit 17 as shown in Figure 22(c) and performs a reconciliation process on the temporary receipt data with temporary receipt IDs "1" and "2".As an example, this reconciliation process adds information indicating that the deposit reconciliation processing unit 24 has performed the reconciliation to the temporary receipt data with temporary receipt IDs "1" and "2".

[0071] This allows you to perform the clearing process for the deposit indicated by the import file information selected on the lump sum deposit clearing screen. As mentioned above, you can accurately specify the desired import file information on the lump sum deposit clearing screen, so you can perform the clearing process accurately.

[0072] While this example describes the import of a deposit file, the file to be imported may also be a dunning result file, as shown in Figure 23. In this case, as shown in Figure 23, import information such as the import date and time, file name, number of items imported, vendor code, vendor name, and dunning period is obtained based on the header record and data record of the dunning result file. Furthermore, the above-mentioned import history data is generated based on the import information, and this import history data is displayed as a list on the dunning result update screen as imported file information, as shown in Figure 23. This makes it possible to accurately select the desired imported file information, as described above.

[0073] When the person in charge selects the desired import file information and operates the execute button on the dunning result update screen, the dunning result data stored in the dunning result data storage unit (not shown) of storage unit 2 is updated with the selected import file information. This allows the desired dunning result data to be updated accurately according to the dunning results.

[0074] (Detailed explanation of deposit file import operation) Next, the operation of importing such a deposit file will be explained in detail. Figure 24 is a flowchart showing the flow of the operation of importing a deposit file. This flowchart starts when the desired import file is specified on the transfer deposit file import screen shown in Figure 3 and the import button is operated, and the process is executed in order from step S1.

[0075] In step S1, since a deposit file for a transfer is specified, the data generating unit 22 acquires the deposit route code of "1" from the transfer master table 12 shown in FIG. 2(b).

[0076] In step S2, the data generation unit 22 refers to the update setting master table 13 shown in FIG. 2(c) based on the deposit route code "1" and acquires the import information set for the deposit route code "1".

[0077] In step S3, the acquisition unit 21 acquires the transfer deposit file stored in the file storage unit 14. Figure 25(a) shows an example of the transfer deposit file acquired from the file storage unit 14. As shown in Figure 25(a), the deposit file is created as fixed-length data based on the Japanese Bankers Association format.

[0078] The data generating unit 22 generates the header record shown in FIG. 25(b) and the data record shown in FIG. 25(c) based on this deposit file, and stores them in the file storage unit 14.

[0079] In step S4, the data generating unit 22 creates the item list shown in FIG.

[0080] This item list is composed of item IDs and item values ​​in descending order. The item values ​​for each item ID are set in advance. For example, for item ID "0", the data generation unit 22 inputs the system date and time at the time of execution as the item value. For item ID "1", the data generation unit 22 inputs the name of the import file as the item value. For item ID "2", the number of data records is input as the item value. For item ID "3", the data generation unit 22 inputs the total transaction amount of the data records as the item value.

[0081] Furthermore, for item ID "4", the data generation unit 22 inputs the creation date of the header record as the item value. For item ID "5", the data generation unit 22 inputs the accounting date (from) of the header record as the item value. For item ID "6", the data generation unit 22 inputs the accounting date (to) of the header record as the item value. For item ID "7", the data generation unit 22 inputs the bank code of the header record as the item value. For item ID "8", the data generation unit 22 inputs the bank name of the header record as the item value.

[0082] Furthermore, the data generating unit 22 inputs the branch code of the header record as the item value for the item ID "9", and inputs the branch name of the header record as the item value for the item ID "10".

[0083] Next, in step S5, the data generation unit 22 generates import file information based on the update setting master table 13 shown in Figure 27(a) and the item list shown in Figure 27(b). Specifically, as shown in Figure 27(a), the import information acquired from the update setting master table 13 based on the deposit route code is assigned a number such as "0" or "1". This number corresponds to the item ID in the item list shown in Figure 27(b). Therefore, the data generation unit 22 reads out the item value of the item ID corresponding to the number of the import information acquired from the update setting master table 13 from the item list, and generates the import file information shown in Figure 9, etc.

[0084] Next, in step S6, the data generation unit 22 updates the import history data in the import history data storage unit 15 with the generated import file information as shown in Fig. 9 etc. In addition, in step S7, the data generation unit 22 updates the deposit file detail data stored in the deposit file detail data storage unit 16 shown in Fig. 6 etc. with the import file ID and the number of data records in the generated import file information.

[0085] In addition, in step S8, the data generation unit 22 updates the suspense data stored in the suspense data storage unit 17 with the suspense ID, the transaction amount of the data record, and the accounting date.

[0086] This allows the user to display a list of the imported file information as described above, select the desired imported file information, and perform, for example, a payment reconciliation process.

[0087] (Effects of the embodiment) As is clear from the above explanation, the business support device 1 of the embodiment allows the user to check not only file attribute information such as the file name and file import date and time, but also the header data of the deposit file when selecting it. This makes it possible to accurately select the desired deposit file. Furthermore, the process of selecting the desired deposit file can be greatly simplified, improving business efficiency.

[0088] Furthermore, if the header data of the deposit information file is of a fixed length, the desired information can be selectively acquired and displayed, thereby making the displayed header data easier to recognize.

[0089] In addition, the user can set the items (items) of header data that they need to display. This allows all header data information to be displayed, preventing the inconvenience of having to spend time checking the information and enabling efficient file selection. Furthermore, because the file contents (header data) can be displayed on the screen, it is possible to reduce mistakes in selecting the desired deposit file and improve the accuracy of selecting the deposit file.

[0090] Furthermore, even if the information obtained from the deposit file differs for each company or user, it can be adjusted by the master settings in the update setting master table 13, thereby reducing the effort required to customize the information obtained for each company or user.

[0091] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of goals "8" and "9" of the SDGs.

[0092] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs goals 12, 13, and 15.

[0093] Furthermore, the present invention can contribute to strengthening control and governance, thereby contributing to the achievement of Goal 16 of the SDGs.

[0094] [Other embodiments] The present invention can be implemented in various different forms other than the above-described embodiments within the scope of the technical concept described in the claims.

[0095] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically using a known method or the like.

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

[0097] Furthermore, the components of the business support device 1 shown in the figure are conceptual functional components and do not necessarily have to have the physical configuration shown in the figure. For example, all or any part of the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0098] The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in the embodiments, and is mechanically read by the business support device 1 as needed. That is, a computer program is recorded in the storage unit 2, such as a ROM or HDD, for working with an OS (Operating System) to give instructions to a control unit 3 (CPU) and perform various processes. The computer program is loaded into RAM, expanded, and executed by the control unit 3 as appropriate.

[0099] In addition, the business support program of this business support device 1 may be stored in 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.

[0100] Furthermore, the business support program for executing the processes described in the embodiments may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0101] Here, the "recording medium" can be any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0102] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code.

[0103] It should be noted that a "program" is not necessarily limited to a single structure, but includes a structure that is distributed as multiple modules or libraries, and a structure that achieves its function by working together with other programs, such as an OS.

[0104] Furthermore, the specific configuration for reading the recording medium in the task support device 1 of the embodiment, the reading procedure, and the installation procedure after reading can be any known configuration or procedure.

[0105] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, web page files, etc. used for various processes or providing websites.

[0106] The business support device 1 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be implemented with software (including programs or data) that realizes the processes described in the embodiments.

[0107] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be selectively implemented by combining them in any way. [Industrial Applicability]

[0108] The present invention is suitable for application to, for example, debt collection operations. [Explanation of symbols]

[0109] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / Output Interface Section 6 Input Devices 7 Output Devices 11 Account Transfer Master Table 12 Transfer Master Table 13 Update Settings Master Table 14 File storage section 15. Import history data storage unit 16. Deposit file details data storage section 17. Temporary receipt data storage unit 18 Item list storage section 21 Acquisition Department 22 Data Generation Unit 23 Output control section 24 Payment reconciliation processing section

Claims

1. an acquisition unit that acquires a deposit file including a header record including the bank account and date to which the deposit was made by bank transfer or direct debit, and a data record including user information and the amount for identifying the user who made the deposit to the bank account by bank transfer or direct debit; a data generation unit that references a storage unit in which import information to be imported from the deposit file is set for the deposit route by bank transfer and the deposit route by account transfer, and generates import history data including the import information corresponding to the deposit route obtained from the deposit file; an output control unit that outputs the generated capture history data to an output target device; A business support device having the above.

2. The data generation unit generates the import history data to which unique import file identification information has been added, and generates temporary receipt data including the deposited amount and date corresponding to the import history data to which the import file identification information has been added, based on the deposit file; the output control unit displays the import history data on a display unit; a deposit reconciliation processing unit that, when the import history data corresponding to the deposit reconciliation process is selected via the display unit, performs a deposit reconciliation process on the temporary receipt data corresponding to the import file identification information added to the selected import history data; 2. The business support device according to claim 1, further comprising:

3. The data generation unit Generate an item list in which the item values ​​corresponding to each item identification information are associated with the predetermined import information of the deposit file, and stored; referencing the storage unit in which the item identification information corresponding to the import information acquired in accordance with the deposit route is stored, and acquiring the import information corresponding to the item identification information from the item list to generate the import history data; 3. The business support device according to claim 1 or 2, wherein:

4. an acquiring step in which an acquiring unit acquires a deposit file including a header record including a bank account and a date to which the deposit was made by bank transfer or direct debit, and a data record including user information and an amount for identifying the user who made the deposit to the bank account by bank transfer or direct debit; a data generation step in which a data generation unit references a storage unit in which import information to be imported from the deposit file for the deposit route by bank transfer and the deposit route by account transfer is set, and generates import history data including the import information corresponding to the deposit route obtained from the deposit file; an output control step in which an output control unit outputs the generated capture history data to an output target device; A business support method having the above.

5. Computer, an acquisition unit that acquires a deposit file including a header record including the bank account and date to which the deposit was made by bank transfer or direct debit, and a data record including user information and the amount for identifying the user who made the deposit to the bank account by bank transfer or direct debit; a data generation unit that references a storage unit in which import information to be imported from the deposit file is set for the deposit route by bank transfer and the deposit route by account transfer, and generates import history data including the import information corresponding to the deposit route obtained from the deposit file; an output control unit that outputs the generated capture history data to an output target device; A business support program that functions as a

Images