Business assistance device, business assistance method, and business assistance program

Abstract

To reduce a burden of matching business of an invoice and a purchasing performance.SOLUTION: A coupling result data generation unit generates coupling result data containing a billing amount, a billing deadline purchasing amount, and a total purchasing amount for each commodity number from purchase data containing a commodity number and a purchasing amount of a commercial transaction customer and invoice data including a billing amount and a commodity number of a commerical trasaction customer. A payment matching comparison unit detects coupling result data of an amount in which a billing amount and a billing deadline purchasing amount are equal as one not needing correction, detects coupling result data of an amount in which a billing amount and a total purchasing amount are equal as one not needing correction, detects coupling result data of an amount in which a difference between a billing amount and a total purchasing amount is within a prescribed permission amount as one not needing correction, and detects coupling result data of an amount in which a difference between a billing amount and a total purchasing amount is outside the prescribed permission amount as one needing correction. An output control unit outputs the detection results through an external device.SELECTED DRAWING: Figure 2

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] Nowadays, when a purchaser purchases goods from a business partner, the purchaser records the purchase after verifying the goods and amount shown in the invoice data provided by the business partner against the goods and amount entered as purchase data by the purchaser.

[0003] Patent Document 1 (JP 2022-147177 A) discloses, in paragraphs 0061 to 0066, etc., a technology for matching invoice information with purchase order information, generating matching results such as "unconfirmed" and "confirmed," and storing them in a database. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2022-147177 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the invoice data provided by business partners is created using product numbers (manufacturer contract numbers) that are uniquely assigned to each product by the business partner. This means that when accounting for purchases, the person in charge must compile their own purchase records (purchased products and amounts) by manufacturer contract number and compare them with the invoice data, which is a tedious task.

[0006] The present invention has been made in consideration of the above-mentioned problems, and has an object to provide a business support device, a business support method, and a business support program that can reduce the burden of matching invoices with purchase records. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, a business support device according to the present invention includes a combined result data generation unit that generates combined result data including an invoice amount for each product number, an invoice closing date purchase amount which is the purchase amount for each product number up to the invoice closing date, and a total aggregate purchase amount which is the purchase amount including the amount for each product number after the invoice closing date, based on purchase data including a purchase date when products were purchased from a business partner, a unique product number assigned to each purchased product at the business partner, and a purchase amount of the products, and invoice data including an invoice amount from the business partner, an invoice closing date, and a unique product number assigned to each product corresponding to the invoice amount; The payment reconciliation inquiry unit has a first detection unit that detects combined result data in which the invoice amount and the invoice closing date purchase amount are the same as combined result data that does not require correction, and a second detection unit that detects combined result data in which the invoice amount and the total aggregate purchase amount are the same as combined result data that does not require correction, detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is within a specified allowable amount as combined result data that does not require correction, and detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is outside the specified allowable amount as combined result data that requires correction, and an output control unit that outputs the detection results of the first detection unit and the second detection unit via an external device.

[0008] In order to solve the above-mentioned problems and achieve the object, the business support method according to the present invention includes a combined result data generating step in which a combined result data generating unit generates combined result data including an invoice amount for each product number, an invoice closing date purchase amount which is the purchase amount for each product number up to the invoice closing date, and a total aggregated purchase amount which is the purchase amount including the amount for each product number after the invoice closing date, based on purchase data including a purchase date on which products were purchased from a commercial transaction partner, a unique product number assigned to each purchased product at the commercial transaction partner, and a purchase amount of the products, and invoice data including an invoice amount from the commercial transaction partner, an invoice closing date, and a unique product number assigned to each product corresponding to the invoice amount; The system has a payment reconciliation inquiry step including a first detection unit which detects, from the combined result data, combined result data in which the invoice amount and the invoice closing date purchase amount are the same as combined result data that does not require correction, and a second detection unit which detects combined result data in which the invoice amount and the total aggregate purchase amount are the same as combined result data that does not require correction, detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is within a specified allowable amount as combined result data that does not require correction, and detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is outside the specified allowable amount as combined result data that requires correction, and an output control step in which an output control unit outputs the detection results of the first detection unit and the second detection unit via an external device.

[0009] In order to solve the above-mentioned problems and achieve the object, a business support program according to the present invention includes a computer, a combined result data generating unit that generates combined result data including an invoice amount for each product number, an invoice closing date purchase amount which is the purchase amount for each product number up to the invoice closing date, and a total aggregate purchase amount which is the purchase amount including the amount for each product number after the invoice closing date, based on purchase data including a purchase date when products were purchased from a business partner, a unique product number assigned to each product purchased at the business partner, and a purchase amount of the products, and invoice data including an invoice amount from the business partner, an invoice closing date, and a unique product number assigned to each product corresponding to the invoice amount; The payment reconciliation inquiry unit is equipped with a first detection unit that detects, among the result data, combined result data in which the invoice amount and the invoice closing date purchase amount are the same as combined result data that does not require correction, and a second detection unit that detects combined result data in which the invoice amount and the total aggregate purchase amount are the same as combined result data that does not require correction, detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is within a specified allowable amount as combined result data that does not require correction, and detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is outside the specified allowable amount as combined result data that requires correction, and functions as an output control unit that outputs the detection results of the first detection unit and the second detection unit via an external device. Effect of the Invention

[0010] The present invention can reduce the burden of matching invoices with purchase records. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram illustrating a hardware configuration of a task support device according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing the flow of the operation of matching an invoice with a purchase record, which is executed by the business support device according to the embodiment. [Diagram 3] FIG. 3 is a diagram showing an example of purchase data generated based on purchase input on the part of the processor, which is the company. [Figure 4]FIG. 4 is a diagram showing an example of invoice data received from a manufacturer (business partner). [Diagram 5] FIG. 5 is a diagram showing an example of a payment matching inquiry screen showing the matching results of purchase data and invoice data. [Figure 6] FIG. 6 is a diagram showing how purchase summary data is generated based on purchase data. [Figure 7] FIG. 7 is a diagram showing how the combined result data is generated by combining the invoice data and the purchase summary data, and how the combined result data is stored in the combined result table in the storage unit. [Figure 8] FIG. 8 is a diagram showing the combined result data to which the difference and the verification result are added by performing a verification process on the combined result data in the third detection unit of the payment verification inquiry unit. [Figure 9] Figure 9 is a diagram showing the combined result data in which the difference and matching results have been updated by the first detection unit performing matching processing on the combined result data that has been matched by the third detection unit of the payment matching inquiry unit. [Figure 10] Figure 10 is a diagram showing the combined result data in which the difference and the matching results have been updated by the second detection unit performing matching processing on the combined result data that has been matched by the first detection unit of the payment matching inquiry unit. [Figure 11] FIG. 11 is a diagram showing purchase data manually corrected by a person in charge based on the combined result data subjected to matching processing by the second detection unit of the payment matching inquiry unit. [Figure 12] Figure 12 shows the payment reconciliation inquiry screen displaying the combined result data that has been regenerated by the first to third detection sections of the payment reconciliation inquiry unit performing reconciliation processing based on the purchase data manually corrected by the person in charge and the invoice data. [Figure 13] FIG. 13 is a diagram showing an example of the payment request input screen. [Figure 14] FIG. 14 is a diagram showing a temporary table in which difference data indicating the difference between the invoice amount and the purchase amount is generated and stored based on the regenerated merged result data. [Figure 15]FIG. 15 is a diagram showing purchase data to be combined with the difference data in the temporary table. [Figure 16] FIG. 16 is a diagram showing how the final acquired data is generated by combining the difference data and purchase data in the temporary table. [Figure 17] FIG. 17 is a diagram showing the payment request input screen on which the generated final acquired data and the consumption tax adjustment amount are displayed. [Figure 18] FIG. 18 is a diagram showing purchase data corresponding to the consumption tax adjustment amount and payment request data corresponding to the billing data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] A business support device according to an embodiment of the present invention will be described in detail below with reference to the drawings. As an example, the business support device according to this embodiment is a business support device operated by a person in charge at a processing company that operates in the steel industry. The processing company processes materials (goods) purchased from a manufacturer (=business partner). The manufacturer (=business partner) sends an invoice to the processing company for the materials (goods) delivered to the processing company. The processing company matches the invoice data of the invoice received from the manufacturer (=business partner) with the purchase data that the processing company records for purchases. The business support device according to the embodiment is a device that supports this matching work on the processing company side. Note that the present invention is not limited to the following embodiment, which is described as an example.

[0013] (overview) In the steel industry, when a processor places an order for materials, the manufacturer from which the materials will be purchased (=trading partner) and the consumer to whom the final product will be delivered are decided. At this time, many transactions occur using the manufacturer's contract number (manufacturer's contract number). In this transaction, the processor checks the invoice (issued at the closing unit) created using the manufacturer's contract number and its own purchasing record, and then pays the manufacturer for the purchased goods.

[0014] However, because processors do not record their purchases based on the manufacturer's contract number, the processor's staff had to go through the tedious task of tallying up their own company's purchasing records based on the manufacturer's contract number and then cross-checking them with invoices.

[0015] In addition, if the manufacturer's sales date and the company's purchase date differ, it can be difficult to grasp any discrepancies that may arise between the regular monthly invoice and the timing of the company's payments.

[0016] Specifically, for example, a product may be shipped from the manufacturer (sales accounting standard is shipment basis) on July 20, 2023, and purchased by your company (purchasing accounting standard is arrival basis) on July 21, 2023. In this case, the invoice issued by the manufacturer has a sales date of July 20, 2023, so your company (processor) will be billed on July 20, 2023, which is the closing date for the manufacturer.

[0017] In response to this, our company (the processor) will process the payment as if the invoice arrived by the company's closing date of the following month, August 20, 2023, because the purchase date is July 21, 2023. However, since the invoice was received from the manufacturer as an invoice dated July 20, 2023, our company will need to process it as an invoice for July 2023.

[0018] On the other hand, due to differences in the calculation method of consumption tax, there may be a discrepancy of a few yen between the invoice amount and the purchase amount. In this case, the company determines whether the difference is within the allowable range, and if it is, processes the consumption tax adjustment separately. The burden of adjusting such differences was a heavy burden on the person in charge.

[0019] For this reason, the business support device of the embodiment enables payment matching on the manufacturer contract number used by the manufacturer, which is the business partner that purchases materials (products). In other words, the contents of the invoice are imported, and the company's purchase data is automatically matched with the amount tallied on the manufacturer contract number basis, and the results can be confirmed in a list. This significantly reduces the burden of matching work on the person in charge.

[0020] Furthermore, the business support device of the embodiment allows data that is the subject of payment processing as a result of matching processing to be automatically called up at the time of processing a payment request, making confirmation easy.

[0021] In addition, the business support device of the embodiment judges whether the difference in the consumption tax amount is within the allowable range based on a threshold value. If it is within the allowable range, the business support device automatically records the difference in the consumption tax amount on the invoice when processing the payment request, thereby eliminating the need to process it on a separate invoice and improving business efficiency.

[0022] (Hardware configuration) FIG. 1 is a block diagram showing a hardware configuration of a task support device 1 according to an embodiment. As shown in FIG. 1, the task support device 1 according to 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 may be a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function. The communication interface unit 4 is connected to a network such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0023] 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 reduces the burden of matching invoices with purchase records.

[0024] The storage unit 2 also includes a join result table 11 and a temporary table 12, which are storage areas. The storage unit 2 also stores various data such as purchase data, invoice data, purchase summary data, final acquisition data, and payment request data.

[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 a data generation unit 21, a payment reconciliation inquiry unit 22, an output control unit 23, an adjustment amount calculation unit 24, and a display control unit 25, as shown in Fig. 1. The data generation unit 21 includes the functions of a combination result data generation unit 26, a difference detection unit 27, a finally acquired data generation unit 28, a purchase data generation unit 29, and a payment request data generation unit 30. The payment reconciliation inquiry unit 22 includes the functions of a first detection unit 31, a second detection unit 32, and a third detection unit 33, which respectively perform reconciliation processing of purchase data and invoice data.

[0026] The combined result data generating unit 26 of the data generating unit 21 obtains "purchase data including the purchase date when the goods were purchased from the business partner (manufacturer side), the unique product number (manufacturer contract number) assigned to each purchased product at the business partner, and the purchase amount of the goods" and "invoice data including the billing amount from the business partner, the billing closing date, and the unique product number (manufacturer contract number) assigned to each product corresponding to the billing amount." Then, based on this purchase data and invoice data, the combined result data generating unit 26 generates combined result data including the billing amount for each product number, the billing closing date purchase amount which is the purchase amount up to the billing closing date for each product number, and the total aggregate purchase amount which is the purchase amount including the amount after the billing closing date for each product number.

[0027] The payment matching inquiry unit 22 includes a first detection unit 31 and a second detection unit 32. The first detection unit 31 detects, among the combined result data, combined result data in which the invoice amount and the purchase amount on the invoice closing date are the same amount as combined result data that does not require correction. The second detection unit detects combined result data in which the invoice amount and the total aggregate purchase amount are the same amount as combined result data that does not require correction, detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is within a predetermined allowable amount as combined result data that does not require correction, and detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is outside the predetermined allowable amount as combined result data that requires correction.

[0028] The output control unit 23 outputs the detection results of the first detection unit 31 and the second detection unit 32 via an external device (output device 7). Specifically, when the external device (output device 7) is a display unit, the output control unit 23 supplies the detection results to the display unit to obtain a display output of the detection results. When the external device (output device 7) is a printing device, the output control unit 23 supplies the detection results to the printing device to obtain a print output of the detection results. When the external device (output device 7) is a speaker device, the output control unit 23 supplies the detection results to the speaker device to obtain an audio output of the detection results.

[0029] In addition, the payment reconciliation inquiry unit 22 further includes a third detection unit 33 that detects merged result data in which there is no billing closing date purchase amount and total aggregated purchase amount corresponding to the billing amount as merged result data requiring correction.

[0030] In this case, the output control unit 23 outputs the detection results of the first detection unit 31, the second detection unit 32, and the third detection unit 33 via an external device.

[0031] In addition, the combined result data generation unit 26 regenerates the above-mentioned combined result data based on the purchase data and invoice data that have been manually corrected based on the detection results of the first detection unit 31, the second detection unit 32, and the third detection unit 33 output via an external device.

[0032] Based on the regenerated combined result data, the payment matching inquiry unit 22 generates temporary data by adding the matching results indicating the need for correction detected by the first detection unit 31, the second detection unit 32, and the third detection unit 33 to the combined result data.

[0033] Based on the manually corrected purchase data and temporary data, the final acquired data generation unit 28 generates payment target data that does not include the billing closing date purchase amount or the total aggregated purchase amount of the temporary data with a detection result that requires correction as a payment target, and the final acquired data generation unit 28 generates payment target data that does include the billing closing date purchase amount or the total aggregated purchase amount of the temporary data with a detection result that does not require correction as a payment target.

[0034] The difference detection unit 27 detects the difference between the invoice amount and the purchase amount on the invoice closing date, and the difference between the invoice amount and the total total purchase amount for each product number based on the temporary data. The adjustment amount calculation unit 24 calculates the total of each detected difference as the adjustment amount. The output control unit 23 outputs the final acquired data and the adjustment amount via an external device (output device 7).

[0035] Furthermore, purchase data generation unit 29 generates purchase data with the commercial trading partner as the payee, the purchase date, and the adjustment amount as the purchase amount. Payment request data generation unit 30 generates payment request data with the commercial trading partner as the payee, including a specified payment request date, and a payment request amount obtained by adding a purchase amount equivalent to the adjustment amount to the total of all aggregated purchase amounts for each product number. Output control unit 23 outputs the purchase data including the purchase amount equivalent to the adjustment amount and the payment request data to an external device (storage unit 2 or output device 7).

[0036] (Matching of invoices and purchase records) Next, a description will be given of the operation of matching invoice supply with actual purchases in the business support device 1 of the embodiment having such a configuration. Fig. 2 is a diagram showing the flow of the operation of matching invoices with actual purchases executed in the business support device of the embodiment. The control unit 3 of the business support device 1 of the embodiment executes a business support program stored in the storage unit 2, thereby functioning as the data generation unit 21 to the third detection unit 33, and executing the purchase input process of step S1, the received invoice data import process of step S2, the payment matching inquiry process of step S3, and the payment request input process of step S4 shown in Fig. 2.

[0037] In this example, the data generating unit 21 to the third detecting unit 33 are realized as software based on the business support program, but some or all of the data generating unit 21 to the third detecting unit 33 may be realized as hardware. In either case, the same effects as those described below can be obtained.

[0038] (Step S1: Purchase input processing) First, when a processor's staff purchases materials (goods) from a manufacturer, which is a business partner, the staff inputs a purchase number indicating a unique product number assigned by the processor to the purchased goods, the product's supplier (= the payee), and the purchase date. The staff also inputs the manufacturer's contract number, which is a unique product number assigned to the product by the manufacturer, the number of units, the asset quantity, the unit price, the purchase price, the purchase consumption tax (10% as an example), and the purchase price. Based on this purchase input, the purchase data generation unit 29 of the data generation unit 21 generates purchase data as shown in FIG. 3, and stores it in the storage unit 2.

[0039] The example of purchasing data in Figure 3 shows that three products purchased on the same date of July 10, 2023 are handled by the processor under a single purchasing number, "S0001," but are handled by the manufacturer under the manufacturer contract numbers, "2GE9089," "2GE9113," and "2GE9120," respectively.

[0040] Also, the product record for "2GE8147", which corresponds to the red invoice on the fifth line in Figure 3, shows a cancellation invoice due to a change in unit price. In other words, this example shows that "1,000 kilograms" of material was purchased in the past at a unit price of "250 yen", but the unit price of this material has increased to "350 yen", so the purchase at the previous unit price of "250 yen" is being cancelled. The purchase at the new unit price of "350 yen" is newly recorded in the product record for "2GE8147" on the sixth line in Figure 3.

[0041] In this manner, the purchase data generating unit 29 generates purchase data including the manufacturer contract number.

[0042] (Step S2: Received invoice data import process) Next, the processor's staff inputs the import slip number, the invoice issuer (=business partner), the billing closing date which is the closing date of the business partner, the manufacturer's contract number, the main amount, the consumption tax amount, and the invoice amount with the consumption tax amount added to the main amount, based on the invoice for the material (product) price issued by the manufacturer as a result of the above-mentioned purchase. As a result, the data generation unit 21 generates the invoice data shown in FIG. 4 and stores it in the storage unit 2.

[0043] The example in Fig. 4 is an example of invoice data issued by "Manufacturer A" with a billing deadline of "July 20, 2023". The data generation unit 21 generates invoice data in which the invoice amount and the like are input for each manufacturer contract number of each product on the invoice.

[0044] (Step S3: Payment reconciliation processing) Next, when a payment matching inquiry is specified by the person in charge, the display control unit 25 displays a payment matching inquiry screen, as shown in Fig. 5, via the output device 7. When a "payee" and "closing date" are specified via this payment matching inquiry screen, the payment matching inquiry unit 22 tally up the purchase data shown in Fig. 3 by manufacturer contract number, and performs matching processing with the invoice data shown in Fig. 4 based on the payee and manufacturer contract number.

[0045] To explain step by step, the combined result data generation unit 26 of the data generation unit 21 aggregates the purchase data shown in Fig. 6(a) for the purchase amounts for purchase dates up to "July 20, 2023" and the purchase amounts for purchase dates on or after "July 20, 2023" by manufacturer contract number. As a result, the combined result data generation unit 26 generates purchase aggregate data including the manufacturer contract numbers, purchase amounts for purchase dates up to "July 20, 2023", and purchase amounts for purchase dates on or after "July 20, 2023", as exemplified in Fig. 6(b).

[0046] Hereinafter, the purchase amount for purchase dates up to "July 20, 2023" will be simply referred to as "Purchase amount," and the purchase amount for purchase dates on or after "July 20, 2023" will be simply referred to as "Purchase amount (total)." Additionally, the amount simply referred to as "Purchase amount" is equivalent to the "Invoice closing date purchase amount," and "Purchase amount (total)" is equivalent to the "total aggregate purchase amount."

[0047] Next, the joined result data generation unit 26 generates joined result data by combining the invoice amount of the invoice data shown in Figure 7(a) with the purchase amounts for purchase dates up to "July 20, 2023" and the purchase amounts for purchase dates after "July 20, 2023" of the above-mentioned purchase summary data shown in Figure 7(b) based on the manufacturer contract number, and stores the joined result data in the joined result table 11 shown in Figure 7(c).

[0048] (First matching process) When the combined result data is stored in the combined result table 11 in this manner, the third detection unit 33 detects, for each record of each manufacturer contract number, records for which the invoice amount and purchase amount (purchase amount for purchase dates up to July 20, 2023) have not been acquired, as shown in Fig. 8. In addition, the third detection unit 33 detects, for each record of each manufacturer contract number, records for which the invoice amount and purchase amount (total total) have not been acquired.

[0049] If both the purchase amount and purchase amount (total) of that record have been acquired (exist), the third detection unit 33 generates null data (NULL) as the difference amount and comparison result of that record, and adds this to the combined result data, as shown in Fig. 8. On the other hand, if both the purchase amount and purchase amount (total) of that record have not been acquired (do not exist), the third detection unit 33 sets the difference amount as the invoice amount, and sets the comparison result as, for example, an "X" mark, and adds this to the combined result data.

[0050] In the example of Figure 8, for records with manufacturer contract numbers "2GE8147", "2GE9089", "2GE9113", and "2GE9120", both the purchase amount and the purchase amount (total) have been acquired, so null data (NULL) has been added to the difference and the matching result. In contrast, for the record with manufacturer contract number "2GE9221", neither the purchase amount nor the purchase amount (total) have been acquired, so the invoice amount of "164,056 yen" has been added to the difference, and an "x" has been added to the matching result.

[0051] Of these, records with null data (NULL) added to the difference and matching result will be subject to the second matching process described below (will proceed to the next determination process), and records with an "X" added to the matching result will not be subject to the second matching process described below (will not proceed to the next determination process).

[0052] (Second matching process) Next, the first detection unit 31 of the payment matching inquiry unit 22 detects records of the merged result data in which the invoice amount and the purchase amount (purchase amount on purchase dates up to July 20, 2023) are the same amount, as shown in FIG. 9, for records other than those with an "X" added to the matching result in the first matching process described above. In the example of FIG. 9, the record in the first row with the manufacturer contract number "2GE8147" has an invoice amount of "77,000 yen" and a purchase amount (purchase amount on purchase dates up to July 20, 2023) of "77,000 yen", which is the same amount. Therefore, the first detection unit 31 sets the difference amount of that record to "0 yen" and marks the matching result with "◎", indicating that no correction is required.

[0053] In addition, the other records with manufacturer contract numbers "2GE9089", "2GE9113", and "2GE9120" have different invoice amounts and purchase amounts (purchase amounts for purchase dates up to July 20, 2023). Therefore, as shown in FIG. 9, the first detection unit 31 adds null data (NULL) to the difference amount and the matching result to make them the subject of the third matching process described below.

[0054] (Third matching process) Next, the second detection unit 32 of the payment matching inquiry unit 22 compares the invoice amount and the purchase amount (total tally) for the records in which null data (NULL) has been added to the difference amount and the matching result in the second matching process described above, as shown in Fig. 10. If the invoice amount and the purchase amount (total tally) are the same amount, the second detection unit 32 sets the difference amount of that record to "0 yen" and marks the matching result with "○" indicating that no correction is required. In the example of Fig. 10, the record in the third row with the manufacturer contract number "2GE9113" corresponds to this comparison result, so "0 yen" is added to the difference amount and a mark "○" is added to the matching result indicating that no correction is required.

[0055] Furthermore, if the billed amount and the purchase amount (total amount) are different amounts, the second detection unit 32 compares the difference with a predetermined threshold amount. If the difference is less than the predetermined threshold amount, the second detection unit 32 indicates that the difference is within the allowable range by marking the difference of the record as the "difference amount" and marking the comparison result with "●" indicating that no correction is required. In the example of FIG. 10, the record in the fourth row with the manufacturer contract number "2GE9120" corresponds to this comparison result, so the difference is marked with "1 yen", which is the difference amount in this case, and the comparison result is marked with "●" indicating that no correction is required.

[0056] Also, if the difference between the invoice amount and the purchase amount (total amount) is equal to or exceeds the threshold, the second detection unit 32 marks the difference for that record as "0 yen" and marks the matching result with "△" to indicate that the difference is outside the allowable range. In the example of Fig. 10, the record in the second row with the manufacturer contract number "2GE9089" corresponds to this comparison result, so the difference is marked as "0 yen" and the matching result is marked with "△" to indicate that the comparison result needs to be corrected.

[0057] (Manual correction of amount) The combined result table with such amount differences and matching results is displayed (or printed out, etc.) by the display control unit 25 via the output device 7 at a timing specified by the person in charge. By looking at the combined result table shown in the example of Figure 10, the person in charge recognizes the records of manufacturer contract numbers that require amount correction. Then, as shown in Figure 11, the person in charge manually corrects the amount of the record of the manufacturer contract number that requires amount correction.

[0058] Specifically, in the example of Figure 10, the record with manufacturer contract number "2GE9089" and the record with manufacturer contract number "2GE9221" are marked with a "△" or "X" as a comparison result. Therefore, the person in charge recognizes the record with manufacturer contract number "2GE9089" and the record with manufacturer contract number "2GE9221" as records that require the amount to be revised.

[0059] Then, as shown in Figure 11, in the case of a record with manufacturer contract number "2GE9089", the person in charge manually corrects, for example, the asset quantity from "812 kilograms" to "1,000 kilograms" and the unit price from "341 yen" to "300 yen". In addition, the person in charge manually corrects the base price to "300,000 yen", the consumption tax amount to "30,000 yen", and the purchase amount to "330,000 yen".

[0060] Similarly, for a record with manufacturer contract number "2GE9221", the person in charge manually enters the purchase amount as "164,056 yen", which is the same as the invoice amount, and manually enters "149,142 yen" as the product amount and "14,914 yen" as the consumption tax amount to correspond to this purchase amount. Also, to correspond to the purchase amount, the person in charge enters the asset quantity of "1,407 kilograms", and manually enters the default unit price (106 yen) and number of units.

[0061] The record with the manufacturer contract number "2GE9221" is a record that has not been recorded. Therefore, the person in charge assigns a new purchase number "S0005" and manually corrects the record with the manufacturer contract number "2GE9221" as shown in Figure 11.

[0062] In this way, by making manual corrections, the difference between the invoice amount and the purchase amount can be brought within a desired range.

[0063] (Re-matching process and reflected on payment matching inquiry screen) Next, the combined result data generating unit 26 regenerates the combined result data shown in Fig. 7(c) based on the manually corrected purchase data and invoice data. Then, the payment matching inquiry unit 22 performs re-matching processing in the order of the third detection unit 33, the first detection unit 31, and the second detection unit 32 based on the regenerated combined result data, detects whether corrections are necessary, and adds them to the combined result data.

[0064] At this stage, because the purchase data has been manually corrected as described above, the matching results for the records of all manufacturer contract numbers are such that no amount modification is required. The display control unit 25 displays this matching result data on the payment reconciliation inquiry screen, as shown in Figure 12. As a result, a matching result indicating that no amount modification is required is displayed for all records of the manufacturer contract numbers, and the difference is displayed as "0 yen" or an amount within the allowable range described above (in this example, "1 yen").

[0065] (Step S4: Payment request input process) Next, the business support device 1 of the embodiment can automatically create payment request data based on the purchase data and invoice data that have been adjusted to have a difference within the allowable range by the above-mentioned manual correction or the like.

[0066] In this case, by designating a payment request input, the person in charge inputs the payment request date, which is the date on which the payment request was input, and the scheduled payment date, which is the date on which the payment of the product price to the payee is scheduled based on this payment request, into the payment request input screen displayed by the display control unit 25 via the output device 7, as shown in Fig. 13. The person in charge also inputs the payee code and closing date as extraction conditions for the payee to whom payment is to be made, into this payment request input screen.

[0067] In the example of FIG. 13, the payment request date is July 25, 2023, the scheduled payment date is August 31, and the controlled party code of Manufacturer A and the closing date of July 20, 2023 are entered as extraction conditions. After entering the controlled party code and other information, the person in charge operates the "Display" button on the payment request input screen.

[0068] When the "Display" button is operated, the merged result data generating unit 26 regenerates the merged result data based on the purchase data and invoice data manually corrected as described above. The payment matching inquiry unit 22 adds the collation results indicating the need for correction detected by the first detection unit 31, the second detection unit 32, and the third detection unit 33 to the regenerated merged result data, and stores this as temporary data in the temporary table 12 as shown in Fig. 14.

[0069] Based on the manually corrected purchase data shown in Figure 15 and the temporary data shown in Figure 16(a), the final acquired data generation unit 28 generates the final acquired data illustrated in Figure 16(b), which includes payment target data (payment target flag) that makes the billing closing date purchase amount or the total aggregated purchase amount of the temporary data with detection results indicating that correction is required non-subject to payment, and payment target data (payment target flag) that makes the billing closing date purchase amount or the total aggregated purchase amount of the temporary data with detection results indicating that correction is not required subject to payment.

[0070] Based on this final acquired data, the output control unit 23 displays a list of the invoice number line number, the accounting date corresponding to the purchase date, the planned payment amount corresponding to the purchase amount and the current requested amount, and the payment target flag, etc., for each manufacturer contract number on the payment request input screen shown in Figure 17.

[0071] In addition, based on the temporary data stored in the temporary table 12 shown in Fig. 14, the difference detection unit 27 detects the difference between the purchase amount and the invoice amount for purchase dates up to "July 20, 2023", and the difference between the purchase amount (total) and the invoice amount, for each manufacturer contract number. The adjustment amount calculation unit 24 calculates the total of each detected difference as the adjustment amount. In the example of Fig. 14, the total amount of the difference is "1 yen".

[0072] The output control unit 23 displays the calculated difference of "1 yen" in the consumption tax adjustment amount display field of the payment request input screen shown in FIG.

[0073] Next, the purchase data generation unit 29 generates purchase data with maker A in this example as the payee, the purchase date, the consumption tax amount of "1 yen", and the adjustment amount of "1 yen" as the purchase amount. The output control unit 23 generates the purchase data thus generated, including the purchase amount equivalent to the adjustment amount, as shown in Fig. 18(a).

[0074] The output control unit 23 stores the generated purchase data in the storage unit 2, or displays it via the output device 7 (it may be a printout or audio output).

[0075] In addition, as shown in Figure 18 (b), the payment request data generation unit 30 generates payment request data with manufacturer A as the payee, including a specified payment request date and a payment request amount obtained by adding a purchase amount of "1 yen" equivalent to the adjustment amount to the total amount of purchase amounts (total amount) for each product number (in this example, 2,305,896 yen + 1 yen = 2,305,897 yen).

[0076] The output control unit 23 stores the generated payment request data in the storage unit 2, or displays it via the output device 7 (it may be printed out or output as audio). This makes it possible to automatically generate and record purchase data and payment request data equivalent to the consumption tax adjustment amount, and greatly reduces the workload of the person in charge.

[0077] (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.

[0078] 1. The system imports invoice data, automatically checks the company's purchasing data against the amounts tallied by manufacturer contract number, and makes it possible to check the results in a list. This significantly reduces the burden on the person in charge of the check.

[0079] 2. In addition, as a result of the matching process, data that is deemed suitable for proceeding to payment processing can be automatically called up as target data and made available for confirmation when processing the payment request.

[0080] 3. Regarding discrepancies of a few yen due to differences in consumption tax, a judgment is made based on a predetermined threshold as to whether the difference is within the allowable range, and if it is within the allowable range, the difference in consumption tax is automatically recorded on the invoice when the payment request is processed. This makes it unnecessary to process the difference on a separate invoice, significantly reducing the workload of the person in charge.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] The present invention is suitable for use in supporting accounting operations such as matching purchase data with billing data in companies and the like. [Explanation of symbols]

[0096] 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 Join result table 12 Temporary Tables 21 Data Generation Section 22 Payment Reconciliation Department 23 Output control section 24 Adjustment amount calculation section 25 Display control section 26 Join result data generation unit 27 Difference detection unit 28 Final acquisition data generation section 29 Purchase Data Generation Department 30 Payment request data generation unit 31 First detection unit 32 Second detector 33 Third detector

Claims

1. a combined result data generating unit that generates combined result data including the invoice amount for each product number, the invoice closing date purchase amount which is the purchase amount up to the invoice closing date for each product number, and a total aggregate purchase amount which is the purchase amount including the amount after the invoice closing date for each product number, based on purchase data including a purchase date when the products were purchased from a business partner, a unique product number assigned to each of the products purchased at the business partner, and a purchase amount for the products, and invoice data including an invoice amount from the business partner, an invoice closing date, and the unique product number assigned to each of the products corresponding to the invoice amount; a payment matching inquiry unit including a first detection unit which detects, from among the combined result data, combined result data in which the invoice amount and the purchase amount on the invoice closing date are the same amount as combined result data that does not require correction, and a second detection unit which detects combined result data in which the invoice amount and the total aggregate purchase amount are the same amount as combined result data that does not require correction, detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is within a predetermined allowable amount as combined result data that does not require correction, and detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is outside the predetermined allowable amount as combined result data that requires correction; an output control unit that outputs detection results of the first detection unit and the second detection unit via an external device; A business support device having the above configuration.

2. The payment matching inquiry unit further includes a third detection unit that detects the combined result data in which the invoice closing date purchase amount and the total aggregate purchase amount corresponding to the invoice amount do not exist as combined result data requiring correction, the output control unit outputs the detection results of the first detection unit, the second detection unit, and the third detection unit via an external device; 2. The business support device according to claim 1,

3. the combined result data generating unit regenerates the combined result data based on the purchase data and the invoice data manually corrected based on the detection results of the first detection unit, the second detection unit, and the third detection unit output via the external device; The payment matching inquiry unit generates temporary data by adding detection results indicating whether correction is required or not detected by the first detection unit, the second detection unit, and the third detection unit to the combined result data based on the regenerated combined result data, a final acquisition data generating unit that generates final acquisition data including payment target data that excludes the billing cut-off date purchase amount or the total aggregate purchase amount of the temporary data to which the detection result requiring correction is attached, and payment target data that excludes the billing cut-off date purchase amount or the total aggregate purchase amount of the temporary data to which the detection result requiring no correction is attached, based on the manually corrected purchase data and the temporary data; a difference detection unit for detecting, for each of the product numbers, a difference between the invoice amount and the purchase amount on the invoice closing date and a difference between the invoice amount and the total purchase amount based on the temporary data; and an adjustment amount calculation unit that calculates a total of the detected differences as an adjustment amount, the output control unit outputs the finally acquired data and the adjusted amount via the external device; 3. The business support device according to claim 2,

4. a purchase data generating unit that generates purchase data in which the commercial transaction partner is a payee, the purchase date, and the adjustment amount are a purchase amount; a payment request data generating unit that generates payment request data including a payment request amount obtained by adding the purchase amount equivalent to the adjustment amount to the total amount of the total aggregate purchase amount for each of the product numbers, the payment request data being generated for the commercial transaction partner as a payment destination, a predetermined payment request date, and the output control unit outputs the purchase data including the purchase amount corresponding to the adjustment amount and the payment request data to the external device; 4. The business support device according to claim 3,

5. a combined result data generating step in which a combined result data generating unit generates combined result data including the invoice amount for each product number, the invoice closing date purchase amount which is the purchase amount up to the invoice closing date for each product number, and a total aggregate purchase amount which is the purchase amount including the amount after the invoice closing date for each product number, based on purchase data including a purchase date on which the product was purchased from the business partner, a unique product number assigned to each of the products purchased at the business partner, and a purchase amount of the product, and based on invoice data including an invoice amount from the business partner, an invoice closing date, and a unique product number assigned to each of the products corresponding to the invoice amount; a payment matching inquiry step including a first detection unit that detects, as merged result data in which the invoice amount and the invoice closing date purchase amount are the same, a second detection unit that detects, as merged result data in which the invoice amount and the total aggregate purchase amount are the same, as merged result data in which the invoice amount and the total aggregate purchase amount are the same, detects, as merged result data in which the difference between the invoice amount and the total aggregate purchase amount is within a predetermined allowable amount, as merged result data in which the difference between the invoice amount and the total aggregate purchase amount is outside the predetermined allowable amount, as merged result data in which correction is required; and an output control step in which an output control unit outputs the detection results of the first detection unit and the second detection unit via an external device. A business support method having the above-mentioned features.

6. Computer, a combined result data generating unit that generates combined result data including the invoice amount for each product number, the invoice closing date purchase amount which is the purchase amount up to the invoice closing date for each product number, and a total aggregate purchase amount which is the purchase amount including the amount after the invoice closing date for each product number, based on purchase data including a purchase date when the products were purchased from a business partner, a unique product number assigned to each of the products purchased at the business partner, and a purchase amount for the products, and invoice data including an invoice amount from the business partner, an invoice closing date, and the unique product number assigned to each of the products corresponding to the invoice amount; a payment matching inquiry unit including a first detection unit which detects, from among the combined result data, combined result data in which the invoice amount and the purchase amount on the invoice closing date are the same amount as combined result data that does not require correction, and a second detection unit which detects combined result data in which the invoice amount and the total aggregate purchase amount are the same amount as combined result data that does not require correction, detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is within a predetermined allowable amount as combined result data that does not require correction, and detects combined result data in which the difference between the invoice amount and the total aggregate purchase amount is outside the predetermined allowable amount as combined result data that requires correction; an output control unit that outputs the detection results of the first detection unit and the second detection unit via an external device; A business support program that functions as a

Images