Business support apparatus, business support method, and business support program

Abstract

To support payment operations of a person in charge by enabling collation of items of an invoice received from the supplier with items of an invoice recorded by the company based on a purchase even when the items of the invoices are different.SOLUTION: An acquisition unit acquires purchase data from suppliers and acceptance data for sold commercial transactions, which are provided to the buyer by the supplier. A corresponding item detection unit detects the items of the acceptance data that correspond to each item of the purchase data invoice specified for each supplier. A collation key generation unit generates a collation key, which is a single item or a combination of multiple items used for collation processing, based on collation key generation information predetermined for each payee. A collation processing unit performs collation processing to detect matches or mismatches of items serving as check keys detected from the purchase data based on the generated collation keys and items serving as check keys detected from acceptance data based on the generated collation keys.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] When conducting commercial transactions with suppliers, it is common to compare the inspection details received from the supplier with the purchase details recorded by your company, and then pay the supplier the amount determined through this comparison.

[0003] Patent Document 1 (JP Patent Publication No. 2022-050756A) discloses a transaction statement matching system that provides a transaction statement matching technology that reduces the human burden of matching transaction statements. This transaction statement matching system stores, for each trading partner, trading partner master information that includes at least item correspondence information between each item of trading partner statement data and each item of trading source statement data, matching key information, and matching item information.

[0004] In addition, the transaction detail matching system matches the supplier detail data and the supplier detail data included in the data to be matched, using item data of matching key items and matching items in the supplier detail data and the supplier detail data specified on the basis of item correspondence information, matching key information, and matching item information included in the supplier master information of the target supplier.

[0005] The transaction statement matching system then outputs matching result information in which the result information of the matching target data is associated with the target trading partner information, thereby reducing the human burden of matching transaction statements. [Prior art documents] [Patent documents]

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

[0007] However, there were cases where the itemized statements received from suppliers differed from the itemized statements recorded by the company based on purchases, making it difficult to match the statements.

[0008] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that can support payment operations by enabling the matching of details received from a supplier and the details recorded in-house due to purchases, even when the details are different. [Means for solving the problem]

[0009] In order to solve the above problems and achieve the object, the business support device of the present invention includes an acquisition unit that acquires purchase data indicating details of a commercial transaction object purchased by a purchaser from a supplier, and inspection data indicating details of the commercial transaction object sold to the purchaser, which is data provided to the purchaser by the supplier and is generated by the supplier when the supplier inspects the commercial transaction object sold to the purchaser, a corresponding item detection unit that detects items of the inspection data that correspond to each item of the details of the purchase data, which are predetermined for each supplier and stored in a storage unit, and a matching key generation unit that references matching key generation information that is predetermined for each payee and stored in the storage unit, and detects the details of the purchase data and the inspection data. the matching processing unit performs matching processing to detect a match or mismatch between an item serving as a check key detected from the purchase data based on the generated matching key and an item serving as a check key detected from the inspection data based on the generated matching key; a data generating unit generates matching result data including a matching result indicating a match or mismatch between the items serving as check keys detected from the inspection data based on the generated matching key; and an output control unit controls the output of the generated matching result data via an external device at a predetermined timing.

[0010] In order to solve the above-mentioned problems and achieve the object, a business support method according to the present invention includes an acquisition step in which an acquisition unit acquires purchase data indicating details of a commercial transaction object purchased by a purchaser from a supplier, and inspection data indicating details of a commercial transaction object sold to a purchaser, the inspection data being data provided to the purchaser by the supplier and generated by the supplier when the supplier inspects the commercial transaction object sold to the purchaser; a corresponding item detection step in which a corresponding item detection unit detects items of the inspection data corresponding to each item of the details of the purchase data, the corresponding item detection step being predetermined for each supplier and stored in a storage unit; and a matching key generation unit referring to matching key generation information predetermined for each payee and stored in the storage unit, and detecting the details of the purchase data and the inspection data. The method includes a matching key generating step of generating a matching key which is one item or a combination of items used in a matching process for matching data details; a matching processing step in which a matching processing unit performs a matching process to detect a match or mismatch between an item serving as a check key detected from the purchase data based on the generated matching key and an item serving as a check key detected from the inspection data based on the generated matching key; a data generating step in which a data generating unit generates matching result data including a matching result indicating a match or mismatch between the items serving as check keys as a result of the matching process; and an output control step in which an output control unit controls the output of the generated matching result data via an external device at a predetermined timing.

[0011] In order to solve the above-mentioned problems and achieve the object, a business support program according to the present invention includes an acquisition unit that acquires purchase data indicating details of a commercial transaction object purchased by a purchaser from a supplier and inspection data indicating details of the commercial transaction object sold to the purchaser, the inspection data being data provided to the purchaser by the supplier and generated by the supplier when the supplier inspects the commercial transaction object sold to the purchaser, a corresponding item detection unit that detects items of the inspection data that correspond to each item of the details of the purchase data, which are predetermined for each supplier and stored in a storage unit, and a matching key generation unit that references matching key generation information that is predetermined for each payee and stored in the storage unit, and detects items of the inspection data that correspond to each item of the details of the purchase data. the matching key generating unit generates a matching key which is one item or a combination of multiple items used in a matching process for matching the details of the purchase data and the details of the inspection data; a matching processing unit performs a matching process for detecting a match or mismatch between an item which serves as a check key detected from the purchase data based on the generated matching key and an item which serves as a check key detected from the inspection data based on the generated matching key; a data generating unit generates matching result data including a matching result indicating a match or mismatch between the items which serve as check keys as a result of the matching process; and an output control unit which controls the output of the generated matching result data via an external device at a predetermined timing. Effect of the Invention

[0012] The present invention makes it possible to compare statements even when the items of the statement received from the supplier are different from the items of the statement recorded by the company after purchase, thereby supporting the payment operations of the person in charge. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a schematic diagram showing an overall flow of a process of verifying details in a payment transaction performed by a transaction support device according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of a quotation sent from a supplier. [Diagram 3] FIG. 3 is a block diagram illustrating a hardware configuration of the task support device according to the embodiment. [Figure 4]FIG. 4 is a diagram showing an example of the import format master. [Diagram 5] FIG. 5 is a diagram showing an example of the import layout detail master. [Figure 6] FIG. 6 is a diagram illustrating an example of the mapping master. [Figure 7] FIG. 7 is a diagram illustrating an example of the payment destination master. [Figure 8] FIG. 8 is a diagram illustrating an example of the verification process master. [Figure 9] FIG. 9 is a diagram illustrating an example of the product master. [Figure 10] FIG. 10 is a diagram showing an example of the payment / inspection automatic verification screen. [Figure 11] FIG. 11 is a diagram illustrating an example of purchase data. [Figure 12] FIG. 12 is a diagram showing inspection data in which items corresponding to items of purchase data have been mapped. [Figure 13] FIG. 13 is a diagram showing an example of a collation key set according to a supplier and check keys which are items to be checked. [Figure 14] FIG. 14 is a diagram showing an example of purchase data to which a matching key generated according to a supplier is added. [Figure 15] FIG. 15 is a diagram showing an example of inspection data to which a collation key generated according to the mapped supplier item is added. [Figure 16] FIG. 16 is a diagram showing an image of the result of the first matching process. [Figure 17] FIG. 17 is a diagram showing an image of the second matching process result. [Figure 18] FIG. 18 is a diagram showing an image of the result of the third matching process. [Figure 19] FIG. 19 is a diagram showing an image of the fourth collation process result. [Figure 20] FIG. 20 is a diagram showing a part of the matching result data generated based on the results of each matching process. [Figure 21]FIG. 21 is a diagram showing a portion of purchase data following a portion of matching result data generated based on each matching process result. [Figure 22] FIG. 22 is a diagram showing a portion of the verification result data generated based on the results of each verification process, which is the subsequent inspection data. [Figure 23] FIG. 23 is a diagram showing an example of the verification manual input screen. [Figure 24] FIG. 24 is a diagram showing a part of the matching result data in which the result of manual matching input is reflected. [Diagram 25] FIG. 25 is a diagram showing an example of a matching result list generated based on the matching result data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0015] (overview) In payment operations, the payment amount is often determined by comparing the inspection details received from the other party with the purchase details recorded by the company. However, in the electrical materials wholesale industry, for example, different items are used in the company's details and those of the manufacturer, and the granularity of the details differs, making it difficult to compare the details. Also, in industries that handle a large number of products, there is the problem of needing to assign product numbers to compare the details.

[0016] The business support device of the embodiment addresses the problem of difficulty in matching details due to differences in the items and granularity to be matched between one's own company and suppliers, and the problem of the need to assign product numbers due to the large number of products, as follows.

[0017] (Complete amount verification) Quotations from manufacturers often consist of two parts: a statement and details. The statement may include the addressee, title, date, and preparer, as well as a mid-term total for each piece of equipment (lighting fixtures, intercoms, cubicles, etc.). The details include a detailed breakdown for each piece of equipment. Also, the inspection data received from the manufacturer along with the quotation may also be a lump sum amount for each piece of equipment mentioned above.

[0018] Therefore, the business support device according to the embodiment is capable of performing collation processing on a detail basis, as well as collation on a total amount basis on a facility, purchase order number, and delivery note number basis.

[0019] (Matching process for various part numbers) The company handles a large number of products, including electric wires, cables, etc., which have different model numbers for different lengths and thicknesses, making it difficult to manage all of them in master data.

[0020] For this reason, the business support device of the embodiment makes it possible to register the manufacturer model number even for purchases where miscellaneous item numbers have been entered, thereby enabling comparison processing of details using the manufacturer model number instead of the item number.

[0021] (Overview of the matching process) First, Fig. 1 shows an outline of the flow of details matching processing in a business support device according to an embodiment. As shown in Fig. 1, a quotation and an order are received from a supplier. An "equipment number" and an "order number" are written on this order. Fig. 2 shows an example of a quotation. As shown in Fig. 2, the quotation includes the quotation number, the set name of each piece of equipment, etc., and a breakdown of each piece of equipment, etc.

[0022] The company's staff returns the order form to the supplier. The supplier prepares the goods based on the returned order form and delivers them to the company together with an invoice. This invoice will state a "delivery note number." The company's staff performs purchase input processing based on the delivered goods and the invoice, and the generated purchase data is stored in the memory unit of the business support device.

[0023] The supplier also generates inspection data for the products delivered to the company. The company can obtain this inspection data by email or by downloading it from the supplier's Web (World Wide Web) site.

[0024] When the company's staff obtains the inspection data, they detect items in the inspection data that correspond to items in the purchasing data and match the items in the purchasing data with the items in the inspection data (mapping process).

[0025] Based on the mapping-processed purchasing data and inspection data, a matching key is generated by combining items preset according to the supplier. Then, the system checks check keys such as "quantity and unit price" included in the purchasing data and inspection data corresponding to the generated matching key, and generates a matching result indicating whether they match or not (payment and inspection automatic matching process).

[0026] In such an automatic payment and receipt verification process, if a verification result indicating a mismatch is obtained, a verification key corresponding to another verification process set for each supplier is generated and a verification process is performed. The operation of generating a verification key corresponding to another verification process and performing a repeated verification process is repeated the number of times equal to the number of other verification processes set for each supplier.

[0027] In this way, if a matching result indicating a match between the check keys is not obtained even after performing the matching process multiple times, the person in charge visually checks whether the purchasing data and the inspection data match or not, and manually enters the matching result (manual matching input process).

[0028] The matching results thus generated by the automatic payment and inspection matching process and the manual matching input process are compiled into a list and output as a display output or print output via an external device (matching result list output process). Based on this matching result list, for example, it is possible to check for input errors in the company's purchase data and for delivery errors from suppliers.

[0029] (Hardware configuration) Fig. 3 is a block diagram showing a hardware configuration of a task support device 1 according to an embodiment. As shown in Fig. 3, the task support device 1 according to an 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.

[0030] The communication interface unit 4 is connected to a network 50, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network). A supplier terminal device 51 is connected to the network 50. The business support device 1 can communicate with the supplier terminal device 51 via the network 50, and can obtain the inspection data described with reference to FIG. 3, etc.

[0031] A storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used as the storage unit 2. The storage unit 2 stores a business support program that supports the cross-checking process of purchasing data and inspection data.

[0032] The storage unit 2 also stores a transaction format master 11, an import layout detail master 12, a mapping master 13, a payment destination master 14, a matching process master 15, and a product master 16, which will be described later.

[0033] As shown in Fig. 4, the format for importing inspection data is set for each supplier in the transaction format master 11. The format number (format NO), format name, file format, delimiter, etc. are set in the transaction format master 11.

[0034] Format number "1" shown in Figure 4 is the setting when importing "XX Industry Inspection Data", and indicates that the inspection data will be imported in the file format of a "variable-length text file (TEXT)" and that the delimiter is a "comma". Format number "2" shown in Figure 4 is the setting when importing "XX Industry Inspection Data", and indicates that the inspection data will be imported in the file format of a "prescribed spreadsheet software".

[0035] In the import layout detail master 12, the items to be imported from the inspection data are set for each format number, as shown in Fig. 5. That is, in the case of format number "1", as shown in Fig. 5, the following items are set to be imported from the inspection data: purchase order number (column number 1), delivery note number (column number 2), inspection date (column number 3), product code (column number 4), model number (column number 5), product name (column number 6), product notes (column number 7), quantity (column number 8), unit price (column number 9), amount (column number 10), consumption tax (column number 11), and equipment identification code (column number 12). Also, in the case of format number "2", as shown in Figure 5, the following items are imported from the inspection data: serial number (column number 1), sales date (column number 2), order number (column number 3), delivery number (column number 4), classification code (column number 5), part number (column number 6), product name (column number 7), model number (column number 8), quantity (column number 9), unit price (column number 10), and amount (column number 11).

[0036] As described in detail later, detection data for the matching process is generated based on the items captured from the inspection data for each supplier in this way. A mapping order is set in the mapping master 13 to arrange the items captured from the inspection data in an order corresponding to the suppliers.

[0037] The example in Figure 6 shows that, for format number "1," the items are arranged in the following order to reconstruct the inspection data: 1: Payee code, 2: Inspection date, 3: Equipment number, 4: Purchase order number, 5: Delivery note number, 6: Part number, 7: Model number, 8: Part number name, 9: Quantity, 10: Unit price, 11: Unit price. In this case, 1: Payee code is set to use the fixed value "SIH001," and 2: Inspection date is set to obtain the inspection date (column number 3) shown in Figure 5. Also, 3: Equipment number is set to obtain the equipment identification code (column number 12) shown in Figure 5, and 4: Purchase order number is set to obtain the purchase order number (column number 1) shown in Figure 5.

[0038] Also, 5: delivery note number is set to acquire the delivery note number (column number 2) shown in Fig. 5, and 6: product number is set to acquire the product code (column number 4) shown in Fig. 5. Also, 7: model number is set to acquire the model number (column number 5) shown in Fig. 5, and 8: product number name is set to acquire the product code (column number 4) shown in Fig. 5. Also, 9: quantity is set to acquire the quantity (column number 8) shown in Fig. 5, and 10: unit price is set to acquire the unit price (column number 9) shown in Fig. 5. Also, 11: product price is set to acquire the amount (column number 10) shown in Fig. 5.

[0039] In the payment destination master 14 and the matching process master 15, a combination of items is set that generates a matching key used in one or more matching processes set for each supplier. Specifically, in the payment destination master 14, as shown in Fig. 7, one or more matching process categories are set for each supplier. In the example of Fig. 7, for the supplier of XX Industry, "STEP1-11", "STEP2-1", "STEP3-01", and "STEP4-01" are set as the matching process categories for the first to fourth matching processes, respectively.

[0040] In the matching process master 15, as shown in Fig. 8, each item to be combined to generate a matching key used in the first to fourth matching processes is set. For example, the matching process of "STEP1-11" is set to generate a matching key by combining "purchase date, purchase order number, and product number" as shown in the record in the first column of Fig. 8. Similarly, the matching process of "STEP1-12" is set to generate a matching key by combining "purchase order number, product number" as shown in the record in the second column of Fig. 8. Moreover, the matching process of "STEP2-01" is set to use "equipment number" as the matching key.

[0041] 7 is an example in which the first to fourth matching processes are set stepwise for each supplier, but only one matching process may be set, or five or more matching processes may be set. Furthermore, the number of matching processes may be variable.

[0042] Here, in the matching process master 15 shown in Fig. 8, a miscellaneous part number flag is set for each matching process, which indicates whether or not to use a "miscellaneous part number" if the "part number" cannot be identified when generating a matching key. In the example of Fig. 8, for the matching process of "STEP1-11", a miscellaneous part number flag is set to "use" the "miscellaneous part number" if the "part number" cannot be identified. Similarly, for the matching process of "STEP1-12", a miscellaneous part number flag is set to "use" the "miscellaneous part number" if the "part number" cannot be identified.

[0043] In contrast, for the matching process of "STEP2-01", the "product number" is not used to generate the matching key, so the product number flag is set to "not use" for the "product number". Similarly, for the matching process of "STEP3-01", the "product number" is not used to generate the matching key, so the product number flag is set to "not use" for the "product number".

[0044] In the product master 16, the customer part number and miscellaneous category are set for each product as shown in Fig. 9. If a customer part number exists for the product, the miscellaneous category is set to "0: normal part number", and if a customer part number does not exist, such as the product "SHO9999", the miscellaneous category is set to "1: miscellaneous part number".

[0045] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, and thereby functions as an acquisition unit 21, a corresponding item detection unit 22, a matching key generation unit 23, a display control unit 24, a matching processing unit 25, a data generation unit 26, and an output control unit 27, as shown in FIG. 3.

[0046] The acquisition unit 21 acquires purchase data indicating details of a commercial transaction object (goods or services) purchased by a purchaser (the purchaser's company) from a supplier. The acquisition unit 21 also acquires inspection data indicating details of the commercial transaction object sold to the purchaser, which is data provided to the purchaser by the supplier and is generated by the supplier inspecting the commercial transaction object sold to the purchaser.

[0047] The corresponding item detection unit 22 detects items of inspection data corresponding to each item of the purchase data details, which are predetermined for each supplier and stored in a storage unit (import layout detail master 12 in FIG. 5 and mapping master 13 in FIG. 6).

[0048] The matching key generation unit 23 refers to matching key generation information (the matching process category in FIG. 7 and the items to be combined to generate the matching key in FIG. 8) that is predetermined for each payment destination (each supplier) and stored in the memory unit (the payment destination master 14 in FIG. 7 and the matching process master 15 in FIG. 8), and generates a matching key which is one item or a combination of multiple items used in the matching process to match the details of the purchase data and the details of the inspection data.

[0049] The matching processing unit 25 performs a matching process to detect a match or mismatch between the items that serve as check keys detected from the purchase data based on the generated matching key, and the items that serve as check keys detected from the inspection data based on the generated matching key.

[0050] The data generating unit 26 generates matching result data including a matching result indicating a match or mismatch of the items serving as the check keys as a result of the matching process.

[0051] The output control unit 27 controls the output of the generated matching result data via an external device (output device 7) at a predetermined timing. For example, if the output control unit 27 is a display control unit, it displays the generated matching result data on a monitor device, which is the output device 7. If the output control unit 27 is a print control unit, it prints out the generated matching result data via a printer, which is the output device 7. If the output control unit 27 is an audio control unit, it supplies the generated matching result data to a speaker device, which is the output device 7, and obtains audio output corresponding to the matching result data.

[0052] The storage unit (payment destination master 14) also stores a plurality of pieces of matching key generation information (the matching process classification in FIG. 7 and the items to be combined to generate the matching key in FIG. 8) each of which specifies the generation of a different matching key. The storage unit also stores a set number (one or more) of matching key generation information for each supplier.

[0053] When a mismatch in the items serving as check keys is detected by the matching process, the matching key generation unit 23 generates a matching key that is specified by the matching key generation information stored in the storage unit and is different from the matching key used in the matching process in which the mismatch in the items serving as check keys was detected. The matching processing unit 25 repeatedly performs the matching process using the newly generated matching key.

[0054] Further, the storage unit (collation process master 15) stores miscellaneous product number use information (miscellaneous product number use flag) indicating whether or not a miscellaneous product number is used, in association with each piece of collation key generation information.

[0055] When the product number item is specified as the item for generating a matching key and the miscellaneous product number usage information is associated matching key generation information, the matching key generation unit 23 generates a matching key using the model number item instead of the product number.

[0056] Furthermore, when multiple values ​​of an item that is a check key corresponding to a matching key are detected from either or both of the purchase data and the inspection data, the matching processor 25 performs a matching process between a value obtained by adding the multiple values ​​detected from either data and the value of the item that is the check key of the other data. Alternatively, the matching processor 25 performs a matching process between values ​​obtained by adding the multiple values ​​detected from both data.

[0057] Furthermore, the display control unit 24 displays on the display unit (output device 7) the purchase data and the inspection data including the item that is the check key for which a mismatch has been detected in the collation process.

[0058] The data generation unit 26 generates matching result data including the manual matching results manually input by the person in charge by visually matching the purchase data and inspection data displayed on the display unit, including the check key items for which a mismatch was detected.

[0059] Furthermore, the data generating unit 26 generates matching result data including text information indicating the manual matching result and the reason for the manual matching result, both of which are manually input by the person in charge.

[0060] The data generating unit 26 generates matching result list data including the purchase data, the inspection data, and the matching result data. The output control unit 27 controls the output of the matching result list data via an external device (output device 7) at a predetermined timing.

[0061] (Operation of the embodiment) Next, the automatic payment and inspection matching process, the manual matching input process, and the matching result list output process in the business support device 1 of the embodiment having such a configuration will be described. The business support device 1 of the embodiment executes each of these processes by functioning as an acquisition unit 21, a corresponding item detection unit 22, a matching key generation unit 23, a display control unit 24, a matching processing unit 25, a data generation unit 26, and an output control unit 27 based on a business support program stored in the storage unit 2. Note that in this example, the acquisition unit 21 to the output control unit 27 are described as being realized by software based on the business support program, but some or all of the acquisition unit 21 to the output control unit 27 may be realized by hardware. In either case, the same effect as that described below can be obtained.

[0062] (Payment and receipt automatic matching process) First, the payment and receipt inspection automatic matching process will be explained. When matching purchase data and inspection data, the person in charge operates the input device 6 to specify the payment and receipt inspection automatic matching process. This specification causes the display control unit 24 to display the payment and receipt inspection automatic matching screen shown in FIG. 10 via the output device 7. The person in charge inputs the payee code and the target year and month on this payment and receipt inspection automatic matching screen to specify the "matching target". In the example of FIG. 10, "XX Industry" of the payee code of "SIH001" is specified as the payee, and "July 2023" is specified as the target year and month.

[0063] Based on the input payee code, the display control unit 24 refers to the payee master 14 shown in Fig. 7 and detects the payment closing date corresponding to the payee. In the example of Fig. 10, since the payee code of the payee is "XX Industry" of "SIH001", the payment closing date is the "31st (end of the month)" of every month as shown in Fig. 7. In this case, the display control unit 24 displays "31st" in the payment closing date display column as shown in Fig. 10.

[0064] The display control unit 24 also displays the purchase date period corresponding to the target year and month and the payment closing date. In this example, "July 2023" is specified as the target year and month, and "the 31st" is detected as the payment closing date. Therefore, the display control unit 24 displays the purchase date period of "July 1, 2023 to July 31, 2023" in the purchase date display field. Note that it is also possible to manually input a desired purchase date period.

[0065] The person in charge also selects the import format of the desired supplier in the import format selection field to specify the "received file" which is the file format to be acquired. In this case, the person in charge selects the import format of "XX Industry". By setting mapping information for each supplier in advance, it is possible to handle multiple formats.

[0066] Based on the selected import format, the display control unit 24 refers to the import format master 11 shown in FIG. 4 and detects the format number, file format, and delimiter of the selected import format.

[0067] In this example, since "XX Industry" is selected as the import format, the display control unit 24 refers to the import format master 11 shown in Fig. 4 and detects the format number of "1", the file format of "TEXT (variable length)", and the delimiter of "comma". In addition, the display control unit 24 refers to the file path master (not shown) to detect the file path indicating the storage location on the storage unit 2 for the file of the selected import format.

[0068] 10, the display control unit 24 displays the file format detected from the import format master 11 in the file format display field, and displays the delimiter detected from the import format master 11 in the delimiter display field. The display control unit 24 also displays the file path detected from the file path master (not shown) in the file path display field. The file format and delimiter can be changed manually.

[0069] Furthermore, the display control unit 24 refers to the processing history data stored in the memory unit 2, and displays the processing history of past matching processes in the processing history display field of the payment and inspection automatic matching screen, as shown in Figure 10.

[0070] The person in charge specifies the supplier and the target date to be verified and selects the import format of the receipt file, then operates the "Execute" button on the payment and inspection automatic verification screen. When the "Execute" button is operated, the acquisition unit 21 refers to the memory unit 2 and acquires purchase data and inspection data for the period corresponding to the target date and purchase date specified by the person in charge. FIG. 11 is a diagram showing an example of purchase data corresponding to the period from July 1, 2023 to July 31, 2023.

[0071] (Mapping process) On the other hand, the corresponding item detection unit 22 detects a format number based on the format name of the payee (supplier) designated by the person in charge, which is registered in the import format master 11 shown in FIG. 4. In this example, a format number of "1" corresponding to the format name of "XX Industry Inspection Data" is detected. Based on this format number of "1", the corresponding item detection unit 22 refers to the import layout detail master 12 shown in FIG. 5 and detects an item to be used for matching that corresponds to the format number of "1" among the items of the detected data. In addition, the corresponding item detection unit 22 refers to the mapping master 13 shown in FIG. 6 and detects a mapping order (arrangement order) corresponding to the format number of "1" for each item to be used for matching detected from the import layout detail master 12 shown in FIG. 5.

[0072] In this example, the items corresponding to format number "1" are set as follows, as shown in Figure 5: purchase order number, delivery note number, inspection date, product code, model number, product name, product notes, quantity, unit price, amount, consumption tax, and equipment identification code. Also, of these items, the mapping order (sorting order) corresponding to format number "1" is set to be in the order of payee code, inspection date, equipment number, purchase order number, delivery note number, product number, model number, product number name, quantity, unit price, and base amount, as shown in Figure 6.

[0073] For this reason, the corresponding item detection unit 22 generates inspection data in which each item of the acquired inspection data is arranged in the following order: payee code, inspection date, equipment number, purchase order number, delivery note number, product number, model number, product number name, quantity, unit price, and product price, as shown in Fig. 12. This allows the order of each item of the detected data to be the same as the order of each item of the purchasing data shown in Fig. 11, making it easier to match the two.

[0074] Note that such mapping (rearrangement) of the items of the inspection data may be performed by physically rearranging each item, or may be performed by temporarily assigning an order number to each item and managing the order of each item, for example.

[0075] Next, the matching key generation unit 23 refers to the payee master 14 shown in Figure 7, and detects the matching process category set for the payee specified by the person in charge. In this example, since "XX Industry" is the one specified by the person in charge, the matching key generation unit 23 refers to the payee master 14 shown in Figure 7, and recognizes that a total of four matching processes, the first to fourth matching processes, have been set for "XX Industry".

[0076] Furthermore, by referring to the payee master 14 shown in FIG. 7, the matching key generating unit 23 recognizes that the matching key used in the first matching process is the matching key for "STEP1-11".

[0077] Also, the matching key generating unit 23 recognizes items that are components of the matching key used in the first matching process by referring to the matching process master 15 shown in Fig. 8, and generates a matching key to be used in each matching process by combining the recognized items. The matching key generating unit 23 generates the matching key for the first matching process based on each item of the purchase data and also based on each item of the inspection data.

[0078] Also, the collation key generating unit 23 refers to the collation process master 15 shown in FIG. 7 to generate the collation key and to recognize whether or not a miscellaneous part number is used.

[0079] Specifically, in this example, the matching key generating unit 23 generates a matching key that combines the items "purchase date, purchase order number, and product number" as a matching key for "STEP1-11" to be used in the first matching process, as shown in the matching process master 15 in Fig. 8. Also, by referring to the matching process master 15 shown in Fig. 7, the matching key generating unit 23 recognizes the miscellaneous product number as "to be used" in the first matching process.

[0080] In this way, when a matching key for the first matching process is generated for the purchasing data and inspection data, the data generation unit 26 generates purchasing data and inspection data in which the generated matching key for the first matching process is added to the corresponding supplier's record, as shown in Figures 14 and 15.

[0081] In this example, the matching key for "STEP1-11" used in the first matching process is set to be generated by combining the items "Purchase date, purchase order number, and product number." Therefore, in the case of the purchase data shown in FIG. 14, a matching key of "20230702_CHU00101_HIN0001" is generated and added as the matching key for the record in the first column. Similarly, a matching key of "20230712_CHU00105_HIN0003" is generated and added as the matching key for the record in the third column.

[0082] Similarly, in the case of the inspection data shown in Fig. 15, a matching key of "20230702_CHU00101_HIN0001" is generated and added as the matching key for the record in the first column. Also, a matching key of "20230712_CHU00105_HIN0003" is generated and added as the matching key for the record in the third column.

[0083] On the other hand, when the "product number (client product number)" cannot be specified, as in the records in the second and fourth columns of the purchasing data in Fig. 14 and the records in the second and fourth columns of the inspection data in Fig. 15, the matching key generation unit 23 determines whether or not a miscellaneous product number is used by referring to the miscellaneous product number usage flag in the matching process master 15 shown in Fig. 8. In this example, the miscellaneous product number is set to "use" for the matching key for "STEP1-11". In this case, the matching key generation unit 23 generates a matching key using a "model number" instead of a "product number".

[0084] As a result, in the case of the purchase data shown in Figure 14, a matching key of "20230710_CHU00102_B-0001" is generated and added as the matching key for the record in the second column. Similarly, a matching key of "20230725_CHU00108_D-0001" is generated and added as the matching key for the record in the fourth column.

[0085] Similarly, in the case of the inspection data shown in Figure 15, a matching key of "20230710_CHU00102_B-0001" is generated and added as the matching key for the record in the second column. Also, a matching key of "20230725_CHU00108_D-0001" is generated and added as the matching key for the record in the fourth column.

[0086] (First matching process) Next, the matching processor 25 matches the matching key of the purchase data and the matching key of the inspection data for each record of each column, as shown in Fig. 13(a) and Fig. 13(b). It detects whether the "quantity" and "unit price" of the purchase data and the inspection data match or not, which are items that are predefined as check keys.

[0087] An image of this first matching process is shown in Figure 16. In the example of Figure 16, in the case of "XX Industry" with a payee code of "SHI001", the records in the first and second columns of the purchasing data and inspection data show that the matching keys match, and so the matching result for the first matching process is "OK (match)". In contrast, the record in the third column of the purchasing data and inspection data shows that the matching result for the first matching process is "NG (mismatch)" because the unit prices do not match (unit price difference). Moreover, the record in the fourth column of the purchasing data and inspection data shows that the matching result for the first matching process is "NG (mismatch)" because the quantities do not match (quantity difference).

[0088] Figure 16 also shows that the matching results for the first matching process for the purchase data and inspection data records for "XX Industry" with payee code "SHI002", "XX Electric" with payee code "SHI003", and "XX Electric Works" with payee code "SHI004" were "NG (mismatch)" due to a mismatch in the matching keys or a difference in quantity.

[0089] (Second matching process) Next, if the first matching process gives a matching result of "NG (mismatch)", the matching key generation unit 23 generates a matching key corresponding to the second matching process for each payee for which a second matching process subsequent to the first matching process is set in the payee master 14 shown in Figure 7. In the example of Figure 7, a second matching process is set for each payee, and the matching key used in this second matching process is set to "STEP2-01: Facility number (see Figure 8)" for each payee.

[0090] For this reason, the matching key generation unit 23 generates a matching key using the "equipment number" as the matching key for the second matching process. In this example, when the payee code is "SHI001" and "XX Industry", a matching key of "STB1001" is generated as the matching key for the second matching process of the purchase data and the inspection data. Also, when the payee code is "SHI002" and "XX Industry", matching keys of "STB2001" and "STB2002" are generated as the matching keys for the second matching process of the purchase data and the inspection data.

[0091] Furthermore, if the payee code is "XX Electrical Equipment" with "SHI003", matching keys "STB3001" and "STB3002" are generated as matching keys for the second matching process of the purchase data, and a matching key "STB3001" is generated as a matching key for the second matching process of the inspection data. Furthermore, if the payee code is "XX Electrical Works" with "SHI004", matching keys "STB4001" and "STB4002" are generated as matching keys for the second matching process of the purchase data, and a matching key "STB4001" is generated as a matching key for the second matching process of the inspection data.

[0092] Based on the generated matching key, the matching processor 25 performs a second matching process on the purchase data and inspection data, as shown in Fig. 17. In the case of "XX Industry" with a payee code of "SHI001", the processing results of the records in the first and second columns of the purchase data and inspection data in the first matching process described above were "OK (match)". Therefore, the purchase data and inspection data that were "NG (mismatch)" in the first matching process are subjected to a matching process again, and in this second matching process, the processing results of the records in the first and second columns are set to "NG (mismatch)" as shown in Fig. 17.

[0093] Also, in the case of "XX Industry" with a payee code of "SHI001", even if a matching process is performed with a matching key of "STB1001", there will be a unit price or quantity difference in the records in the third and fourth columns. Therefore, in this second matching process, the processing result of the records in the third and fourth columns will be "NG (mismatch)", as shown in Figure 17.

[0094] In the case of "XX Industry" with a payee code of "SHI002", the records in the purchasing data that correspond to the matching key "STB2001" are a record with a quantity of "10 units" and a unit price of "1,000 yen", and a record with a quantity of "20 units" and a unit price of "1,000 yen". Meanwhile, the record in the inspection data that corresponds to the matching key "STB2001" is a record with a quantity of "1 unit" and a unit price of "30,000 yen".

[0095] In this case, the matching processing unit 25 calculates the total amount of the record in which the quantity of the purchase data is "10 pieces" and the unit price is "1,000 yen", and the record in which the quantity is "20 pieces" and the unit price is "1,000 yen". In this example, it is "10,000 yen + 20,000 yen = 30,000 yen". The matching processing unit 25 uses the total amount of "30,000 yen" calculated in this way as a check key for the purchase data, and compares it with the check key of the total amount of "30,000 yen" of the record detected from the inspection data based on the matching key of "STB2001". In this case, since the two match, the matching processing unit 25 sets the matching result of the second matching process of the records of the purchase data and the inspection data detected with the matching key of "STB2001" to "OK (match)".

[0096] In other words, when multiple records corresponding to the same matching key are detected from either the purchase data or the inspection data, the matching processor 25 compares the total amount of the multiple records with the amount of one record to obtain a matching result. When multiple records are detected from both the purchase data and the inspection data, the matching processor 25 compares the total amounts of the multiple records detected to obtain a matching result.

[0097] In addition, for "XX Industry" with a payee code of "SHI002", the records in the purchasing data that correspond to the matching key "STB2002" are a record with a quantity of "30 units" and a unit price of "1,000 yen", and a record with a quantity of "40 units" and a unit price of "1,000 yen". Meanwhile, the record in the inspection data that corresponds to the matching key "STB2002" is a record with a quantity of "1 unit" and a unit price of "70,000 yen".

[0098] In this case, the matching processing unit 25 calculates the total amount of the record in which the quantity of the purchase data is "30 pieces" and the unit price is "1,000 yen", and the record in which the quantity is "40 pieces" and the unit price is "1,000 yen". In this example, it becomes "30,000 yen + 40,000 yen = 70,000 yen". The matching processing unit 25 uses the total amount of "70,000 yen" calculated in this way as a check key for the purchase data, and compares it with the check key of the total amount of "70,000 yen" of the record detected from the inspection data based on the matching key of "STB2002". In this case, since the two match, the matching processing unit 25 sets the matching result of the second matching process of the records of the purchase data and the inspection data detected with the matching key of "STB2002" to "OK (match)".

[0099] In contrast, in the case of "XX Electric" with a payee code of "SHI003", a record with a quantity of "20 units" and a unit price of "1000 yen" is detected as a record corresponding to the matching key of "STB3001" in the purchasing data. Also, a record with a quantity of "40 units" and a unit price of "1000 yen" is detected as a record corresponding to the matching key of "STB3001" in the inspection data. In this case, since there is a quantity difference between the two, the matching processing unit 25 determines the matching result of the second matching process of the records of the purchasing data and inspection data detected with the matching key of "STB3001" to be "NG (quantity difference)".

[0100] Also, in the case of "XX Electric" with a payee code of "SHI003", a record with a quantity of "20 units" and a unit price of "1,000 yen" is detected as a record corresponding to the matching key of "STB3002" in the purchase data. However, no record corresponding to the matching key of "STB3002" is detected in the inspection data. For this reason, the matching processing unit 25 determines the matching result of the second matching process of the purchase data and inspection data records detected with the matching key of "STB3002" as "NG: key mismatch".

[0101] Furthermore, in the case of "XX Electric Works" with a payee code of "SHI004", a record with a quantity of "10 units" and a unit price of "1,500 yen" is detected as a record corresponding to the matching key of "STB4001" in the purchasing data. Furthermore, a record with a quantity of "1 unit" and a unit price of "45,000 yen" is detected as a record corresponding to the matching key of "STB4001" in the inspection data. In this case, since there is a difference in quantity and unit price between the two, the matching processing unit 25 determines the matching result of the second matching process of the records of the purchasing data and inspection data detected with the matching key of "STB4001" as "NG: key mismatch".

[0102] Also, in the case of "XX Electric Works" with a payee code of "SHI004", a record with a quantity of "20 units" and a unit price of "1,500 yen" is detected as a record corresponding to the matching key of "STB4002" in the purchasing data. However, no record corresponding to the matching key of "STB4002" is detected in the inspection data. For this reason, the matching processing unit 25 determines the matching result of the second matching process of the records of the purchasing data and inspection data detected with the matching key of "STB4002" as "NG: key mismatch".

[0103] (Third verification process) Next, if the second matching process gives a matching result of "NG (mismatch)", matching key generation unit 23 generates a matching key corresponding to the third matching process for each payee for which a third matching process following the second matching process is set in payee master 14 shown in Figure 7. In the example of Figure 7, a third matching process is set for each payee, and the matching key used in this third matching process is set to "STEP3-01: Purchase order number (see Figure 8)" for each payee.

[0104] For this reason, the matching key generating unit 23 generates a matching key using the "purchase order number" as the matching key for the third matching process. In this example, when the payee code is "SHI001" for "XX Industry", matching keys "CHU00101", "CHU00102", "CHU00105", and "CHU00108" are generated as matching keys for the third matching process of the purchase data and inspection data (see the purchase order number in FIG. 14).

[0105] Furthermore, when the payee code is "XX Industry" of "SHI002", the matching keys "CHU00112" and "CHU00120" are generated as matching keys for the third matching process for the purchase data and the inspection data.

[0106] In addition, when the payee code is "XX Electrical Equipment" with "SHI003", a matching key of "CHU00131" is generated as a matching key for the third matching process of the purchase data and the inspection data.

[0107] In addition, if the payee code is "XX Electric Works" with "SHI004", the matching keys "CHU00142" and "CHU00143" are generated as the matching keys for the third matching process of the purchase data. Also, the matching key "CHU00143" is generated as the matching key for the third matching process of the inspection data.

[0108] Based on the generated matching key, the matching processor 25 performs a third matching process on the purchase data and inspection data, as shown in Fig. 18. In the case of "XX Industry" with a payee code of "SHI001", the processing results of the records in the first and second columns of the purchase data and inspection data in the first matching process described above were "OK (match)". Therefore, the purchase data and inspection data that were "NG (mismatch)" in the first matching process are subjected to a matching process again, and in this third matching process, the processing results of the records in the first and second columns are set to "NG (mismatch)" as shown in Fig. 18.

[0109] Also, in the case of "XX Industry" with a payee code of "SHI001", even if a matching process is performed with a matching key of "CHU00105" or "CHU00108", a unit price or quantity difference occurs in the records in the third and fourth columns. Therefore, in this third matching process, the processing result of the records in the third and fourth columns is "NG (mismatch)", as shown in Figure 18.

[0110] In the case of "XX Industry" with a payee code of "SHI002", the second matching process obtains a matching result of "OK (match)" for all records by matching based on the total amount described above. Therefore, in this third matching process, the matching processor 25 skips the matching process for "XX Industry" with a payee code of "SHI002" (matching process is not performed). By skipping unnecessary matching processes in this way, the time required to complete the matching process can be shortened.

[0111] For "XX Electric" with a payee code of "SHI003", two records with a quantity of "20" and a unit price of "1000 yen" are found as records corresponding to the matching key "CHU00131" in the purchasing data. Also, a record with a quantity of "40" and a unit price of "1000 yen" is found as a record corresponding to the matching key "CHU00131" in the inspection data.

[0112] In this case, the matching processing unit 25 calculates the total amount of the record in which the quantity of the purchase data is "20 pieces" and the unit price is "1000 yen", and the total amount of the record in which the quantity is "20 pieces" and the unit price is "1000 yen". In this example, it becomes "20,000 yen + 20,000 yen = 40,000 yen". The matching processing unit 25 uses the total amount of "40,000 yen" calculated in this way as the check key of the purchase data, and compares it with the check key of the total amount of "40,000 yen" of the record detected from the inspection data based on the matching key of "CHU00131". In this case, since the two match, the matching processing unit 25 sets the matching result of the third matching process of the records of the purchase data and the inspection data detected with the matching key of "CHU00131" as "OK (match)".

[0113] In the case of "XX Electric Works" with a payee code of "SHI004", a record with a quantity of "10" and a unit price of "1500 yen" is detected as a record corresponding to the matching key of "CHU00142" in the purchasing data. However, no record corresponding to the matching key of "CHU00142" is detected in the inspection data. For this reason, the matching processing unit 25 determines the matching result of the third matching process of the records of the purchasing data and inspection data detected with the matching key of "CHU00142" as "NG: key mismatch".

[0114] In addition, in the case of "XX Electric Works" with a payee code of "SHI004", a record with a quantity of "20 units" and a unit price of "1,500 yen" is detected as a record corresponding to the matching key of "CHU00143" in the purchasing data. In addition, a record with a quantity of "1 unit" and a unit price of "45,000 yen" is detected as a record corresponding to the matching key of "CHU00143" in the inspection data. However, since the two do not match, the matching processing unit 25 determines the matching result of the third matching process of the purchase data and inspection data records detected with the matching key of "CHU00143" as "NG: key mismatch". (Fourth matching process) Next, if the third matching process gives a matching result of "NG (mismatch)", matching key generation unit 23 generates a matching key corresponding to the fourth matching process for a payee for which a fourth matching process following the third matching process is set in payee master 14 shown in Figure 7. In the example of Figure 7, a fourth matching process is set for each payee, and the matching key used in this fourth matching process is set to "STEP4-01: Delivery note number (see Figure 8)" for each payee.

[0115] For this reason, the matching key generating unit 23 generates a matching key using the "delivery note number" as a matching key for the fourth matching process. In this example, when the payee code is "SHI001" for "XX Industry", matching keys "NOU00201", "NOU00202", "NOU00203", and "NOU00204" are generated as matching keys for the fourth matching process of the purchase data and inspection data (see the delivery note number in FIG. 14).

[0116] Furthermore, when the payee code is "XX Industry" of "SHI002", a matching key of "NOU00205" is generated as a matching key for the fourth matching process for the purchase data and inspection data.

[0117] In addition, for "XX Electric" with a payee code of "SHI003", matching keys "NOU00241" and "NOU00245" are generated as matching keys for the fourth matching process of the purchase data. Also, a matching key of "NOU00241" is generated as a matching key for the fourth matching process of the inspection data.

[0118] In addition, when the payee code is "XX Electric Works" with "SHI004", a matching key of "NOU00253" is generated as a matching key for the fourth matching process of the purchase data and the inspection data.

[0119] Based on the generated matching key, the matching processor 25 performs a fourth matching process on the purchase data and inspection data, as shown in Fig. 19. In the case of "XX Industry" with a payee code of "SHI001", the processing results of the records in the first and second columns of the purchase data and inspection data in the first matching process described above were "OK (match)". Therefore, the purchase data and inspection data that were "NG (mismatch)" in the first matching process are subjected to a matching process again, and in this fourth matching process, the processing results of the records in the first and second columns are set to "NG (mismatch)" as shown in Fig. 19.

[0120] Also, in the case of "XX Industry" with a payee code of "SHI001", even if matching processing is performed with a matching key of "NOU00203" or "NOU00204", a unit price difference or quantity difference occurs in the records in the third and fourth columns. Therefore, in this fourth matching process, the matching processing unit 25 sets the processing result of the records in the third and fourth columns as "NG (mismatch)" as shown in Figure 19.

[0121] In the case of "XX Industry" with a payee code of "SHI002", the second matching process obtains a matching result of "OK (match)" for all records by matching based on the total amount described above. Therefore, in this fourth matching process, the matching processor 25 skips the matching process for "XX Industry" with a payee code of "SHI002" (does not perform matching).

[0122] Similarly, in the case of "XX Electric" with a payee code of "SHI003", in the third matching process, matching based on the total amount described above gives a matching result of "OK (match)" for all records. Therefore, in this fourth matching process, matching processor 25 also skips the matching process for "XX Electric" with a payee code of "SHI003" (does not perform matching).

[0123] In the case of "XX Electric Works" with a payee code of "SHI004", a record with a quantity of "10" and a unit price of "1500 yen" is detected as a record corresponding to the matching key of "CHU00142" in the purchasing data. However, no record corresponding to the matching key of "CHU00142" is detected in the inspection data. For this reason, the matching processing unit 25 determines the matching result of the third matching process of the records of the purchasing data and inspection data detected with the matching key of "CHU00142" as "NG: key mismatch".

[0124] For "XX Electric Works" with a payee code of "SHI004", a record with a quantity of "10 units" and a unit price of "1500 yen" and a record with a quantity of "20 units" and a unit price of "1500 yen" are found as records corresponding to the matching key of "NOU00253" in the purchasing data. Also, a record with a quantity of "1 unit" and a unit price of "45,000 yen" is found as a record corresponding to the matching key of "NOU00253" in the inspection data.

[0125] In this case, the matching processing unit 25 calculates the total amount of each record of the purchase data as described above. In this example, the total amount of each record of the purchase data is "15,000 yen + 30,000 yen = 45,000 yen." The matching processing unit 25 matches the calculated total amount of each record of the purchase data with the amount of the record of the inspection data (45,000 yen). In this case, the two match, so the matching processing unit 25 sets the matching result of the fourth matching process of the records of the purchase data and inspection data detected with the matching key of "NOU00253" as "OK (match)."

[0126] When the first to fourth matching processes are completed in this manner, the data generation unit 26 generates a series of matching result data shown in Figures 20 to 22. Of these, Figure 20 is the portion corresponding to the "matching result", and in addition to the matching results of the first to fourth matching processes described above, includes the processing number, payee code, target year and month, matching period (start and end), processing user (person in charge), and processing date and time.

[0127] Figure 21 shows the portion of the matching result data that corresponds to the above-mentioned purchasing data, and includes the company's purchasing date, company's purchasing number, company's equipment number, company's purchase form number, company's delivery note number, company's product code, company's product number name, customer's product number, company's model number, company's quantity, company's unit price, and company's main product price.

[0128] Figure 22 is the portion of the matching result data that corresponds to the inspection data described above, and includes the other party's purchase date, other party's equipment number, other party's purchase order number, other party's delivery note number, other party's part number, other party's part number name, other party's model number, other party's quantity, other party's unit price, and other party's base price.

[0129] When the data generation unit 26 generates such matching result data, it stores it in the storage unit 2. The display control unit 24 reads out the matching result data from the storage unit 2 at a timing specified by the person in charge, and displays it via the output device 7. The person in charge can visually confirm the results of each matching process via the displayed matching result data (mainly the results of each matching process in FIG. 20).

[0130] (Manual verification input process) Next, the business support device 1 of the embodiment is configured to call up records for which the collation process result is "NG (mismatch)" in the above-mentioned collation process, and to allow the person in charge to visually collate the records and manually input the collation results. In this case, the person in charge performs a designation operation for the collation means input via the input device 6. When this designation operation is performed, the display control unit 24 displays a manual collation input screen, as exemplified in FIG. 23, via the output device 7.

[0131] Furthermore, the display control unit 24 refers to the matching result data shown in Figures 20 to 22 and detects records for which the matching result is "NG (mismatch)" even though the matching process was performed while changing the matching key in the first to fourth matching processes. In the case of the matching result data in Figure 20, the records in the third and fourth columns have a matching result of "NG (mismatch)" due to "unit price difference" or "quantity difference".

[0132] Therefore, the display control unit 24 inputs the processing number, target year and month, payee, and purchase date on the manual matching input screen shown in Fig. 23 based on the records for which the matching result is "NG (mismatch)". The display control unit 24 also displays the purchase date, equipment number, purchase order number, delivery note number, recipient's part number, model number, part number name, quantity, unit price, and total price of the purchase data (company's data) corresponding to the records for which the matching result is "NG (mismatch)". The display control unit 24 also displays the inspection date, equipment number, purchase order number, delivery note number, part number, model number, part number name, quantity, unit price, and total price of the inspection data (other party's data) corresponding to the records for which the matching result is "NG (mismatch)".

[0133] Furthermore, the display control unit 24 displays a check box for each record of the purchase data (the company's data) and also displays a check box for each record of the inspection data (the other party's data).

[0134] The person in charge compares the purchase data (company data) records and inspection data (other party data) records that show a matching result of "NG (mismatch)" and then checks the check boxes of the purchase data (company data) records and inspection data (other party data) records that show a matching result of "OK (match)".The example in Figure 23 shows the record in the first column of the purchase data (company data) and the record in the first column of the inspection data (other party data) where the person in charge judged the matching result to be "OK (match)", so a check mark was entered in each check box.

[0135] When a check mark is entered in this way, the display control unit 24 displays the main amount of the record of the purchase data (our own data) in which the check mark has been entered as our own amount on the verification manual input screen (in this example, 20,000 yen). The display control unit 24 also displays the main amount of the record of the inspection data (other party data) in which the check mark has been entered as our own amount on the verification manual input screen (in this example, 18,000 yen).

[0136] In addition, the person in charge can enter the reason why the result of checking the purchase data (their own data) record and the inspection data (the other party's data) record, which they have checked, is "NG (mismatch)" in the "Mismatch reason" input field. Figure 23 shows an example where the "Mismatch reason" for "Discrepancy due to rebate" has been entered by the person in charge.

[0137] This manual input screen for comparison makes it possible to settle even if the company's amount does not match the other party's amount. It also makes it possible to handle cases where rebates are received in the following month or later.

[0138] When such manual matching processing is performed, the person in charge operates the "Register" button on the manual matching input screen. When this "Register" button is operated, the data generation unit 26 generates matching result data in which manual matching result information of "OK (match)" is entered into the "manual matching" input field of the record in which the matching result has been manually set to "OK (match)", as shown in Fig. 24. Furthermore, when an "unmatch reason" has been entered, the data generation unit 26 generates matching result data in which the unmatch reason, for example, "discrepancy due to rebate", has been entered into the "manual matching unmatch reason" input field of the record in which the "unmatch reason" has been entered.

[0139] (Comparison result list output process) Once the matching result data has been generated in this way, it becomes possible to output the matching result list. Specifically, the person in charge operates the display of a matching result output screen (not shown) at the desired timing. When this display operation is performed, the display control unit 24 displays a matching result output screen (not shown) via the output device 7. The person in charge inputs and specifies the payee and the target year and month for which the matching result data is to be included in this matching result output screen.

[0140] The output control unit 27 reads out the matching result data corresponding to the specified payee and the purchase date period of the target year and month from the storage unit, and controls the output via the output device 7. If the output device 7 is a printer, the output control unit 27 supplies the matching result data to the printer. This makes it possible to obtain a printout of a matching result list corresponding to the matching result data. If the output device 7 is a display device, the output control unit 27 supplies the matching result data to the display device. This makes it possible to obtain a display output of the matching result list corresponding to the matching result data. If the output device 7 is a speaker device, the output control unit 27 supplies the matching result data to the speaker device. This makes it possible to obtain an audio output of the matching result list corresponding to the matching result data.

[0141] Figure 25 is an example of a list of matching results for XX Industry for July 2023. This is just an example, but the list of matching results displays a list of purchase data (our company), a list of inspection data (the other party), and matching results (including manual matching results and reasons for mismatch) for the specified purchase date period.

[0142] Outputting such a comparison result list can greatly assist the payment operations of the person in charge. In addition, based on this comparison result list, for example, it is possible to check for input errors in the company's purchase data and for delivery errors from suppliers.

[0143] (Effects of the embodiment) As is clear from the above description, the task support device 1 according to the embodiment can achieve the following effects.

[0144] 1. Since the system performs a mapping process to match the items of the inspection data received from the supplier with the items of the company's purchasing data, and then performs the matching process, it is possible to perform the matching process for inspection data with multiple layouts.

[0145] 2. Since the verification process can be performed on a set of inspection data, the verification rate can be improved.

[0146] 3. Since it is possible to perform matching processing using product numbers, the work of registering product master data can be reduced.

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

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

[0149] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0150] (Other embodiments) The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0151] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

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

[0153] Moreover, with regard to the task support device 1, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0154] For example, the processing functions of the business support device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium including programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support device 1 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD. This computer program is executed by being loaded into a RAM, and constitutes the control unit 3 in cooperation with the CPU.

[0155] 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 it is also possible to download all or part of it as needed.

[0156] The business support program for executing the process described in the present embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0157] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that achieves its function by working with a separate program, such as an OS. Note that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading a recording medium in the business support device 1 shown in the embodiment, as well as the installation procedure after reading.

[0158] 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, and web page files used for various processes and providing websites.

[0159] The business support device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

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

[0161] The present invention is suitable for application to payment, inspection and verification work in industries with a large number of monthly transactions, such as the electrical materials wholesale industry, the semiconductor and electronic component manufacturing industry, and wholesale to other manufacturers. [Explanation of symbols]

[0162] 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 Transaction Format Master 12 Import Layout Detail Master 13 Mapping Master 14 Payment destination master 15 Matching Processing Master 16 Product Master 21 Acquisition Department 22 Corresponding item detection section 23 Matching key generation unit 24 Display control section 25 Matching processing unit 26 Data Generation Section 27 Output control section 50 Network 51 Supplier terminal equipment

Claims

1. an acquisition unit that acquires purchase data indicating details of a commercial transaction object purchased by a purchaser from a supplier, and inspection data indicating details of the commercial transaction object sold to the purchaser, the inspection data being data provided to the purchaser by the supplier and generated by the supplier inspecting the commercial transaction object sold to the purchaser; a corresponding item detection unit that detects an item of the inspection data that corresponds to each item of the details of the purchase data, the corresponding item being predetermined for each of the suppliers and stored in a storage unit; a matching key generating unit that references matching key generating information that is predetermined for each payee and that is stored in the storage unit, and generates a matching key that is one of the items or a combination of a plurality of the items to be used in a matching process for matching the details of the purchase data and the details of the inspection data; a matching processing unit that performs a matching process to detect a match or mismatch between an item serving as a check key detected from the purchase data based on the generated matching key and an item serving as a check key detected from the inspection data based on the generated matching key; a data generating unit that generates matching result data including a matching result indicating a match or mismatch of the items serving as the check keys by the matching process; an output control unit that controls output of the generated matching result data via an external device at a predetermined timing; A business support device having the above configuration.

2. the storage unit stores a plurality of pieces of matching key generation information each of which specifies generation of a different matching key; the matching key generation unit, when a mismatch in the item serving as the check key is detected by the matching process, generates a matching key that is specified by the matching key generation information stored in the storage unit and is different from the matching key used in the matching process in which the mismatch in the item serving as the check key was detected; the matching processing unit repeatedly performs the matching process using the newly generated matching key; 2. The business support device according to claim 1,

3. The storage unit stores miscellaneous product number usage information indicating whether or not a miscellaneous product number is used, in association with each of the collation key generation information, the matching key generating unit generates the matching key by using a model number item instead of the product number item when a product number item is designated as an item for generating the matching key and the miscellaneous product number usage information is associated with the matching key generating information; 3. The business support device according to claim 2,

4. when a plurality of values ​​of the item serving as the check key corresponding to the matching key are detected from either or both of the purchase data and the inspection data, the matching processing unit performs a process of matching a value obtained by adding the plurality of values ​​detected from either one of the data with a value of the item serving as the check key of the other of the data, or performs a process of matching values ​​obtained by adding the plurality of values ​​detected from both of the data with each other; 4. The business support device according to claim 3,

5. A display control unit is further provided for displaying the purchase data and the inspection data including the check key item in which a mismatch has been detected in the matching process on a display unit, the data generating unit generates the matching result data including a manual matching result manually input by a person in charge visually matching the purchase data and the inspection data including the check key item in which a mismatch has been detected and displayed on the display unit; 5. The business support device according to claim 4,

6. the data generation unit generates the matching result data including the manual matching result and text information indicating a reason for the manual matching result, both of which are manually input by the person in charge; 6. The business support device according to claim 5,

7. the data generation unit generates matching result list data including the purchase data, the inspection data, and the matching result data; the output control unit controls output of the matching result list data via an external device at a predetermined timing; 7. The business support device according to claim 6,

8. the storage unit stores a set number of the matching key generation information for each of the suppliers; 8. The business support device according to claim 1, wherein:

9. an acquisition step in which an acquisition unit acquires purchase data indicating details of a commercial transaction object purchased by a purchaser from a supplier, and inspection data indicating details of the commercial transaction object sold to the purchaser, the inspection data being data provided to the purchaser by the supplier and generated by the supplier inspecting the commercial transaction object sold to the purchaser; a corresponding item detection step in which a corresponding item detection unit detects an item of the inspection data corresponding to each item of the details of the purchase data, the item being predetermined for each of the suppliers and stored in a storage unit; a matching key generating step in which a matching key generating unit refers to matching key generating information that is predetermined for each payee and that is stored in the storage unit, and generates a matching key that is one of the items or a combination of a plurality of the items to be used in a matching process for matching the details of the purchase data and the details of the inspection data; a matching processing step in which a matching processing unit performs a matching process to detect a match or mismatch between an item serving as a check key detected from the purchase data based on the generated matching key and an item serving as a check key detected from the inspection data based on the generated matching key; a data generating step in which a data generating unit generates matching result data including a matching result indicating a match or a mismatch of the items serving as the check keys by the matching process; an output control step in which an output control unit controls output of the generated matching result data via an external device at a predetermined timing; A business support method having the above-mentioned features.

10. Computer, an acquisition unit that acquires purchase data indicating details of a commercial transaction object purchased by a purchaser from a supplier, and inspection data indicating details of the commercial transaction object sold to the purchaser, the inspection data being data provided to the purchaser by the supplier and generated by the supplier inspecting the commercial transaction object sold to the purchaser; a corresponding item detection unit that detects an item of the inspection data that corresponds to each item of the details of the purchase data, the corresponding item being predetermined for each of the suppliers and stored in a storage unit; a matching key generating unit that references matching key generating information that is predetermined for each payee and that is stored in the storage unit, and generates a matching key that is one of the items or a combination of a plurality of the items to be used in a matching process for matching the details of the purchase data and the details of the inspection data; a matching processing unit that performs a matching process to detect a match or mismatch between an item serving as a check key detected from the purchase data based on the generated matching key and an item serving as a check key detected from the inspection data based on the generated matching key; a data generating unit that generates matching result data including a matching result indicating a match or mismatch of the items serving as the check keys by the matching process; functioning as an output control unit that controls output of the generated matching result data via an external device at a predetermined timing; A business support program that features:

Images