Business support device, business support method, and business support 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 Art

[0002] Today, a purchaser who has purchased goods from a business partner verifies by matching the goods and amounts indicated in the invoice data provided by the business partner with the goods and amounts entered as purchase data on the purchaser's side, and then performs purchase accounting.

[0003] Patent Document 1 (Japanese Patent Application Laid-Open No. 2022-147177) discloses a technique in which invoice information and order form information are matched in paragraphs 0061 to 0066 and the like, and matching results such as "uncertain" and "confirmed" are generated and stored in a database.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, the invoice data provided by the business partner is created using the product numbers (manufacturer contract numbers) uniquely assigned to each product by the business partner. Therefore, when performing purchase accounting, there is a problem that the person in charge has to perform a cumbersome task of aggregating the company's purchase results (purchased products and amounts) in units of manufacturer contract numbers and matching them with the invoice data.

[0006] The present invention has been made in view of the above problems, and an object thereof is to provide a business support device, a business support method, and a business support program capable of reducing the burden of the matching operation between invoices and purchase results.

Means for Solving the Problems

[0007] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention includes a combined result data generation unit that generates combined result data including the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total purchase amount including the purchase amount after the invoice closing date for each product number, based on purchase data including the purchase date on which goods were purchased from a trading partner, a unique product number assigned to each product purchased by the trading partner, and the purchase amount of the goods, and invoice data including the invoice amount from the trading partner, the invoice closing date, and a unique product number assigned to each product corresponding to the invoice amount, and the combined result data The system includes a payment matching inquiry unit comprising: a first detection unit that detects combined result data where the invoice amount and the purchase amount on the billing closing date are the same amount as combined result data that does not require correction; a second detection unit that detects combined result data where 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 where 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 where the difference between the invoice amount and the total aggregate purchase amount is outside a predetermined 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] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the business support method according to the present invention comprises a combined result data generation step in which a combined result data generation unit generates combined result data that includes the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total aggregate purchase amount which includes the purchase amount after the invoice closing date for each product number, based on purchase data including the purchase date on which goods were purchased from the trading partner, a unique product number assigned to each product purchased by the trading partner, and the purchase amount of the goods, and invoice data including the invoice amount from the trading partner, the invoice closing date, and a unique product number assigned to each product corresponding to the invoice amount, and a combined result data generation step in which a combined result data generation unit generates combined result data that includes the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total aggregate purchase amount which includes the purchase amount after the invoice closing date for each product number, and a payment matching inquiry unit The payment matching inquiry step includes: a first detection unit that detects combined result data where the invoice amount and the purchase amount on the billing closing date are the same amount as combined result data that does not require correction; a second detection unit that detects combined result data where 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 where 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 where the difference between the invoice amount and the total aggregate purchase amount is outside a predetermined 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] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support program according to the present invention includes a combined result data generation unit that generates combined result data including the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total purchase amount including the amount after the invoice closing date for each product number, based on purchase data including the purchase date on which goods were purchased from a trading partner, a unique product number assigned to each product purchased by the trading partner, and the purchase amount of the goods, and invoice data including the invoice amount from the trading partner, the invoice closing date, and a unique product number assigned to each product corresponding to the invoice amount, and combined result data including the invoice amount for each product number, purchase amount up to the invoice closing date for each product number, and total aggregate purchase amount including the amount after the invoice closing date for each product number, and combined The payment matching inquiry unit includes a first detection unit that detects combined result data where the invoice amount and the purchase amount on the billing closing date are the same amount as combined result data that does not require correction, and a second detection unit that detects combined result data where 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 where 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 where the difference between the invoice amount and the total aggregate purchase amount is outside a predetermined 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. [Effects of the Invention]

[0010] This invention can reduce the burden of matching invoices with purchase records. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a block diagram showing the hardware configuration of the business support device according to the embodiment. [Figure 2] Figure 2 shows the flow of the invoice and purchase record matching operation performed by the business support device of the embodiment. [Figure 3] Figure 3 shows an example of procurement data generated based on procurement input from our own processing company. [Figure 4]Figure 4 shows an example of invoice data received from the manufacturer (business partner). [Figure 5] Figure 5 shows an example of a payment matching inquiry screen that displays the matching results of purchase data and invoice data. [Figure 6] Figure 6 shows how purchase summary data is generated based on purchase data. [Figure 7] Figure 7 shows the process of generating combined data by combining invoice data and purchase summary data, and storing it in the combined results table of the storage unit. [Figure 8] Figure 8 shows the combined result data to which the difference and matching results have been added after the third detection unit of the payment matching inquiry unit has performed a matching process on the combined result data. [Figure 9] Figure 9 shows the combined result data in which the difference and matching results have been updated by the first detection unit performing a matching process on the combined result data that has been matched by the third detection unit of the payment matching inquiry unit. [Figure 10] Figure 10 shows the combined result data in which the difference and matching results have been updated by the second detection unit performing a matching process on the combined result data that has been matched by the first detection unit of the payment matching inquiry unit. [Figure 11] Figure 11 shows the purchase data that has been manually corrected by the person in charge based on the combined result data processed by the second detection unit of the payment matching inquiry unit. [Figure 12] Figure 12 shows the payment matching inquiry screen displaying the combined result data that has been regenerated by the first to third detection units of the payment matching inquiry unit, based on the purchase data manually corrected by the person in charge and the invoice data. [Figure 13] Figure 13 shows an example of a payment request input screen. [Figure 14] Figure 14 shows a temporary table that generates and stores difference data showing the difference between the invoiced amount and the purchase amount, based on the regenerated join result data. [Figure 15]FIG. 15 is a diagram showing purchase data to be combined with the difference data of the temporary table. [Figure 16] FIG. 16 is a diagram showing how final acquisition data is generated by combining the difference data of the temporary table and the purchase data. [Figure 17] FIG. 17 is a diagram showing a payment request input screen on which the generated final acquisition 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.

Embodiment for Carrying Out the Invention

[0012] Hereinafter, a business support device according to an embodiment to which the present invention is applied will be described in detail based on the drawings. Although it is an example, the business support device of this embodiment is a business support device operated by a person in charge on the processor side engaged in the steel industry etc. The processor processes the materials (goods) purchased from the manufacturer side (= business partner). The manufacturer side (= business partner) sends an invoice for the materials (goods) delivered to the processor. The processor matches the invoice data of the invoice received from the manufacturer side (= business partner) with the purchase data entered in its own company's books. The business support device of the embodiment is a device that supports the matching operation on the processor side. Note that the present invention is not limited to the following embodiments described as an example.

[0013] (Overview) In the steel industry, when a processor orders materials for purchase, the manufacturer (= business partner) that purchases the materials and the customer who receives the final product are determined. At this time, many business transactions using the manufacturer's contract number (manufacturer contract number) occur. In this business transaction, the processor checks the invoice (issued in contract units) created using the manufacturer contract number and its own purchase record, and then pays the manufacturer for the purchased goods.

[0014] However, since processing companies do not record purchases on a per-manufacturer contract number basis, processing company personnel had to perform the cumbersome task of compiling their own purchase records by manufacturer contract number and matching them with invoices.

[0015] Furthermore, when the manufacturer's sales date and our company's purchase date differed, it became difficult to track discrepancies between the regular monthly invoices and our company's payment timings.

[0016] Specifically, for example, if a product is shipped from the manufacturer (with a sales recognition basis based on shipment) on July 20, 2023, and the company's purchase (with a purchase recognition basis based on receipt) occurs on July 21, 2023, the invoice issued by the manufacturer will be dated July 20, 2023, as that is the manufacturer's closing date, and will be issued to the company (processor).

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

[0018] On the other hand, differences in how consumption tax is calculated can sometimes result in a discrepancy of a few yen between the invoice amount and the purchase amount. In this case, the company must determine whether the difference is within an acceptable range, and if it is, process the consumption tax adjustment separately. This burden of adjusting the difference was a significant burden on the person in charge.

[0019] For these reasons, the business support device of this embodiment enables payment matching on a per-manufacturer contract number basis, which is used by manufacturers who are trading partners for the procurement of materials (products). In other words, it imports the contents of invoices as data, automatically matches the company's procurement data with the amounts aggregated on a per-manufacturer contract number basis, and allows the results to be viewed in a list. This significantly reduces the workload of the person in charge of matching.

[0020] Furthermore, the business support device of this embodiment automatically retrieves the data to be processed for payment based on the matching process when processing a payment request, making verification easier.

[0021] Furthermore, the business support device of this embodiment determines, based on a threshold, whether a difference of a few yen due to the difference in consumption tax is within an acceptable range. If it is within an acceptable range, it automatically records the difference in consumption tax when processing the payment request, eliminating the need for separate processing and thus improving business efficiency.

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

[0023] For the memory unit 2, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used. The memory unit 2 stores a business support program that reduces the burden of matching invoices with purchase records.

[0024] Furthermore, the storage unit 2 is equipped with two storage areas, the combined result table 11 and the temporary table 12. The storage unit 2 also stores various types of data, such as purchase data, invoice data, purchase summary data, final acquisition data, and payment request data.

[0025] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the storage unit 2, and functions as a data generation unit 21, a payment matching inquiry unit 22, an output control unit 23, an adjustment amount calculation unit 24, and a display control unit 25, as shown in Figure 1. The data generation unit 21 includes the functions of a combined result data generation unit 26, a difference detection unit 27, a final acquired data generation unit 28, a purchase data generation unit 29, and a payment request data generation unit 30. The payment matching inquiry unit 22 includes the functions of a first detection unit 31, a second detection unit 32, and a third detection unit 33, which perform matching processing of purchase data and invoice data, respectively.

[0026] The combined result data generation unit 26 of the data generation unit 21 acquires "purchase data including the purchase date of goods purchased from the trading partner (manufacturer), the unique product number (manufacturer contract number) assigned to each purchased product at the trading partner, and the purchase price of the goods," and "invoice data including the invoice amount from the trading partner, the invoice closing date, and the unique product number (manufacturer contract number) assigned to each product corresponding to the invoice amount." Based on this purchase data and invoice data, the combined result data generation unit 26 generates combined result data including the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total aggregated purchase amount which includes the purchase amount after the invoice 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 combined result data in which the invoice amount and the purchase amount on the billing 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, and 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, while detecting combined result data in which the difference between the invoice amount and the total aggregate purchase amount is outside a 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, if 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. If 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 printed output of the detection results. Furthermore, if 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] Furthermore, the payment matching inquiry unit 22 includes a third detection unit 33 that detects combined result data for which there is no purchase amount on the billing closing date and total purchase amount corresponding to the billed amount, as combined result data that requires 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] Furthermore, the combined result data generation unit 26 regenerates the combined result data based on the manually corrected purchase data and invoice data, which are output via an external device based on the detection results of the first detection unit 31, the second detection unit 32, and the third detection unit 33.

[0032] The payment matching inquiry unit 22 generates temporary data by adding matching results indicating whether corrections are necessary, as detected by the first detection unit 31, the second detection unit 32, and the third detection unit 33, to the regenerated combined result data.

[0033] The final acquired data generation unit 28 generates final acquired data that includes payment target data, which excludes the purchase amount on the billing closing date or the total aggregate purchase amount of the temporary data that has been detected as requiring correction, based on the manually corrected purchase data and temporary data, and payment target data, which excludes the purchase amount on the billing closing date or the total aggregate purchase amount of the temporary data that has been detected as not requiring correction, from payment.

[0034] The difference detection unit 27 detects, based on temporary data, the difference between the invoiced amount and the purchase amount on the billing closing date, and the difference between the invoiced amount and the total aggregated purchase amount for each product number. The adjustment amount calculation unit 24 calculates the sum 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, the purchase data generation unit 29 generates purchase data with the trading partner as the payee, the purchase date, and the adjustment amount as the purchase amount. The payment request data generation unit 30 generates payment request data with the trading partner as the payee, a predetermined payment request date, and a payment request amount that includes the total amount of all aggregated purchase amounts for each product number plus the purchase amount equivalent to the adjustment amount. The 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 invoices with purchase records) Next, the matching operation of invoices and purchase records in the business support device 1 of the embodiment having the above configuration will be explained. Figure 2 is a diagram showing the flow of the matching operation of invoices and purchase records performed in the business support device of the embodiment. The control unit 3 of the business support device 1 of the embodiment functions as a data generation unit 21 to a third detection unit 33 by executing the business support program stored in the storage unit 2, and executes the purchase input process in step S1, the received invoice data import process in step S2, the payment matching inquiry process in step S3, and the payment request input process in step S4 shown in Figure 2.

[0037] In this example, the data generation unit 21 to the third detection unit 33 are implemented in software based on the business support program, but some or all of the data generation unit 21 to the third detection unit 33 may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0038] (Step S1: Purchase entry processing) First, when a processing company employee purchases materials (goods) from a manufacturer, their trading partner, they input the purchase number, which is a unique product number assigned by the company (processor), the supplier of the goods (=the recipient of payment), and the purchase date. The employee also inputs the manufacturer's contract number, which is a unique product number assigned by the manufacturer, the quantity, asset quantity, unit price, purchase price, purchase consumption tax amount (for example, 10%), and purchase price. Based on this purchase input, the purchase data generation unit 29 of the data generation unit 21 generates the purchase data exemplified in Figure 3 and stores it in the storage unit 2.

[0039] The example of procurement data in Figure 3 shows that three products procured on the same day, July 10, 2023, are handled by the processing company under a single procurement number, "S0001," while the manufacturers handle these three products under different manufacturer contract numbers: "2GE9089," "2GE9113," and "2GE9120."

[0040] Furthermore, the record for product "2GE8147" in the fifth row of Figure 3, which corresponds to the red slip, represents a cancellation slip due to a change in unit price. In other words, this example shows that in the past, 1,000 kilograms of material were purchased at a unit price of 250 yen, but the unit price of this material increased to 350 yen, so the previous purchase at the 250 yen unit price is being canceled. Note that the purchase at the new unit price of 350 yen is newly recorded in the record for product "2GE8147" in the sixth row of Figure 3.

[0041] The procurement data generation unit 29 generates procurement data, including the manufacturer's contract number, in this manner.

[0042] (Step S2: Importing receipt invoice data) Next, the processing company's representative inputs the import slip number, invoice issuer (= trading partner), billing closing date (which is the trading partner's closing date), the manufacturer's contract number mentioned above, the base amount, the consumption tax amount, and the total billed amount with the consumption tax added to the base amount, based on the invoice for the materials (products) issued by the manufacturer as a result of the aforementioned purchase. As a result, the data generation unit 21 generates the invoice data exemplified in Figure 4 and stores it in the storage unit 2.

[0043] The example in Figure 4 is an example of invoice data issued by "Manufacturer A" with a billing date of "July 20, 2023". The data generation unit 21 generates invoice data with the billing amount and other information entered for each manufacturer contract number of the invoiced product.

[0044] (Step S3: Payment Matching Inquiry Process) Next, when a payment matching inquiry is requested by the person in charge, the display control unit 25 displays the payment matching inquiry screen illustrated in Figure 5 via the output device 7. When the "payee" and "closing date" are specified via this payment matching inquiry screen, the payment matching inquiry unit 22 aggregates the purchase data shown in Figure 3 by manufacturer contract number and performs matching processing with the invoice data shown in Figure 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 Figure 6(a) by manufacturer contract number, including purchase amounts for purchase dates up to "July 20, 2023" and purchase amounts for purchase dates after "July 20, 2023". As a result, the combined result data generation unit 26 generates aggregated purchase data including the manufacturer contract number, purchase amounts for purchase dates up to "July 20, 2023", and purchase amounts for purchase dates after "July 20, 2023", as illustrated in Figure 6(b).

[0046] From now on, purchase amounts for purchase dates up to July 20, 2023 will simply be referred to as "Purchase Amount," and purchase amounts for purchase dates on or after July 20, 2023 will be referred to as "Purchase Amount (Total)." Furthermore, the amount simply referred to as "Purchase Amount" corresponds to the "Purchase Amount on Invoice Closing Date," and "Purchase Amount (Total)" corresponds to the "Total Purchase Amount."

[0047] Next, the combined result data generation unit 26 generates combined result data by combining the invoice amount from the billing data shown in Figure 7(a), the purchase amount from the aforementioned purchase summary data shown in Figure 7(b) for purchase dates up to "July 20, 2023", and the purchase amount for purchase dates after "July 20, 2023", based on the manufacturer contract number, and stores it in the combined result table 11 shown in Figure 7(c).

[0048] (First joint fitting) Once the combined data is stored in the combined results table 11, the third detection unit 33 detects records for each manufacturer contract number where the invoice amount and purchase amount (purchase amount for purchase dates up to July 20, 2023) have not been obtained, as shown in Figure 8. The third detection unit 33 also detects records for each manufacturer contract number where the invoice amount and purchase amount (total aggregate) have not been obtained.

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

[0050] The example in Figure 8 shows that for records with manufacturer contract numbers "2GE8147", "2GE9089", "2GE9113", and "2GE9120", both the purchase amount and the total purchase amount have been retrieved, so null data (NULL) is added to the difference and the matching result. In contrast, for the record with manufacturer contract number "2GE9221", neither the purchase amount nor the total purchase amount has been retrieved, so the invoiced amount of "164,056 yen" is added to the difference, and an "×" mark is 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 (and will proceed to the next determination process), while records with an "X" mark added to the matching result will not be subject to the second matching process described below (and will not proceed to the next determination process).

[0052] (Second joint fitting process) Next, the first detection unit 31 of the payment matching inquiry unit 22 detects records in the first matching process described above, other than those for which an "×" mark was added to the matching result, where the invoiced amount and the purchase amount (purchase amount for purchase dates up to July 20, 2023) are the same amount, as shown in Figure 9. In the example in Figure 9, the first row, the record with manufacturer contract number "2GE8147", has an invoiced amount of "77,000 yen" and a purchase amount (purchase amount for purchase dates up to July 20, 2023) of "77,000 yen", so they are the same amount. For this reason, the first detection unit 31 sets the difference in that record to "0 yen" and adds a "◎" mark to the matching result to indicate that no correction is needed.

[0053] Furthermore, for the other records, namely manufacturer contract numbers "2GE9089", "2GE9113", and "2GE9120", the invoiced amount and the purchase amount (purchase amount for purchase dates up to July 20, 2023) are different amounts. Therefore, as shown in Figure 9, the first detection unit 31 adds null data to the difference and the matching result in order to make them subject to the third matching process described below.

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

[0055] Furthermore, if the invoiced amount and the total purchase amount (total) are different, the second detection unit 32 compares the difference with a predetermined threshold amount. If the difference is less than the predetermined threshold, the second detection unit 32 indicates that the difference is within an acceptable range by setting the difference in that record as the "difference amount" and adding a "●" mark to the comparison result to indicate that no correction is needed. In the example in Figure 10, the record in the fourth row with manufacturer contract number "2GE9120" corresponds to this comparison result, so the difference amount in this case, "1 yen," is set, and a "●" mark is added to the comparison result to indicate that no correction is needed.

[0056] Furthermore, if the difference between the invoiced amount and the total purchase amount exceeds the threshold mentioned above, the second detection unit 32 indicates that the difference is outside the acceptable range by setting the difference in that record to "0 yen" and adding a "△" mark to the comparison result to indicate that correction is necessary. In the example in Figure 10, the record in the second row with manufacturer contract number "2GE9089" corresponds to this comparison result, so the difference is set to "0 yen" and a "△" mark is added to the comparison result to indicate that correction is necessary.

[0057] (Manual adjustment of the amount) The combined results table, which includes the difference and matching results, is displayed (or printed, etc.) via the output device 7 by the display control unit 25 at a timing specified by the person in charge. The person in charge identifies the manufacturer contract number records that require amount correction by looking at the combined results table illustrated in Figure 10. Then, as shown in Figure 11, they manually input the corrected amount for the manufacturer contract number records that require correction.

[0058] Specifically, in the example shown in Figure 10, the record with manufacturer contract number "2GE9089" and the record with manufacturer contract number "2GE9221" are marked with a "△" or "×" as the matching 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 correction of the amount.

[0059] Then, as shown in Figure 11, if the record has manufacturer contract number "2GE9089", the person in charge manually corrects the asset quantity from "812 kilograms" to "1000 kilograms", the unit price from "341 yen" to "300 yen", and accordingly manually corrects the base amount to "300,000 yen", the consumption tax amount to "30,000 yen", and the purchase amount to "330,000 yen".

[0060] Similarly, if the record has manufacturer contract number "2GE9221", the person in charge manually enters "164,056 yen" as the purchase amount, the same amount as the invoice amount, and then manually enters "149,142 yen" as the base amount and "14,914 yen" as the consumption tax amount to match this purchase amount. In addition, they enter the asset quantity of "1407 kilograms" to match the purchase amount, and manually enter the default unit price (106 yen) and quantity.

[0061] Note that the record with manufacturer contract number "2GE9221" is a record that was not properly accounted for. Therefore, as shown in Figure 11, the person in charge assigns a new purchase number "S0005" and manually corrects the record with manufacturer contract number "2GE9221".

[0062] In this way, by making manual adjustments, the difference between the invoiced amount and the purchase price can be set to an amount within the desired range.

[0063] (Rematching process and reflection on the payment matching inquiry screen) Next, the combined result data generation unit 26 regenerates the combined result data exemplified in Figure 7(c) based on the manually corrected purchase data and invoice data. Then, the payment matching inquiry unit 22 performs a rematching process based on the regenerated combined result data in the order of the third detection unit 33 → first detection unit 31 → second detection unit 32, detecting whether corrections are necessary and adding them to the combined result data.

[0064] At this stage, since the purchase data has been manually corrected as described above, the matching results for all manufacturer contract number records will show that no amount correction is required. The display control unit 25 displays this matching result data on the payment matching inquiry screen, as shown in Figure 12. As a result, a matching result indicating that no amount correction is required is displayed for all manufacturer contract number records, and the difference will show either "0 yen" or an amount within the above-mentioned acceptable range (in this example, "1 yen").

[0065] (Step S4: Payment Request Input Processing) 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 a difference within an acceptable range through the manual corrections described above.

[0066] In this case, by specifying payment request input, the person in charge inputs the payment request date, which is the date the payment request was made, and the scheduled payment date, which is the date on which payment for the goods to the payee is scheduled to be made, to the payment request input screen displayed by the display control unit 25 via the output device 7, as shown in Figure 13. The person in charge also inputs the payee code and closing date as criteria for extracting the payee to whom payment will be made, to this payment request input screen.

[0067] The example in Figure 13 shows a payment request date set to July 25, 2023, a scheduled payment date set to August 31, and the extraction criteria entered as the control code of manufacturer A and the closing date of July 20, 2023. After entering the control code and other information, the person in charge operates the "Display" button on the payment request input screen.

[0068] When the "Display" button is pressed, the combined result data generation unit 26 regenerates the combined result data based on the manually modified purchase data and invoice data as described above. The payment matching inquiry unit 22 then adds the matching results indicating whether modifications are necessary, as detected by the first detection unit 31, the second detection unit 32, and the third detection unit 33, to the regenerated combined result data, and stores this as temporary data in the temporary table 12 as shown in Figure 14.

[0069] The final acquired data generation unit 28 generates the final acquired data exemplified in Figure 16(b), based on the manually corrected purchase data shown in Figure 15 and the temporary data shown in Figure 16(a). This data includes payment target data (payment target flag) that excludes purchase amounts on the billing closing date or total aggregate purchase amounts in the temporary data with detection results indicating that correction is required, and payment target data (payment target flag) that includes purchase amounts on the billing closing date or total aggregate purchase amounts in the temporary data with detection results indicating that no correction is required.

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

[0071] Furthermore, the difference detection unit 27 detects the difference between the purchase price and the invoiced amount for each manufacturer contract number up to July 20, 2023, and the difference between the total purchase price and the invoiced amount, based on the temporary data stored in the temporary table 12 shown in Figure 14. The adjustment amount calculation unit 24 calculates the sum of each detected difference as the adjustment amount. In the example in Figure 14, the total 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 on the payment request input screen shown in Figure 17.

[0073] Next, the purchase data generation unit 29 generates purchase data with manufacturer A as the payee in this example, and the purchase amount being the purchase date, the consumption tax amount of "1 yen", and the adjustment amount of "1 yen". The output control unit 23 generates the purchase data shown in Figure 18(a), which includes the purchase amount corresponding to the adjustment amount.

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

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

[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 (this may be done by printing or audio output). This makes it possible to automatically generate and record purchase data and payment request data corresponding to the consumption tax adjustment amount, significantly reducing the workload of the person in charge.

[0077] (Effects of the embodiment) As is clear from the above description, the business support device 1 of the embodiment can obtain the following effects.

[0078] 1. The system imports invoice data, automatically matches it with the company's procurement data aggregated by manufacturer contract number, and allows users to view the results in a list. This significantly reduces the workload on personnel involved in the matching process.

[0079] 2. Furthermore, data that is deemed suitable for payment processing as a result of the matching process can be automatically retrieved and verified as target data during the payment request processing.

[0080] 3. For discrepancies of a few yen due to differences in consumption tax, the system will determine whether the difference is within an acceptable range based on a predetermined threshold. If it is within an acceptable range, the system will automatically record the difference in consumption tax when processing the payment request. This eliminates the need for processing on separate slips, 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 operational efficiency and promoting appropriate management decisions by companies, thereby contributing to SDG Goals 8 and 9.

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

[0083] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0084] [Other embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described 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 by known methods.

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

[0087] Furthermore, with respect to the business support device 1, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[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 implemented in whole or in any part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the business support device 1 as needed. That is, a storage unit such as ROM or HDD records a computer program that, in cooperation with the OS, gives instructions to the CPU and performs various processing. This computer program is executed by being loaded into RAM and, in cooperation with the CPU, constitutes the control unit 3.

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

[0090] Furthermore, the business support program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical Disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0091] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedure for reading the recording medium in the business support device 1 shown in the embodiment, as well as the installation procedure after reading, well-known configurations and procedures can be used.

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

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

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

[0095] The present invention is particularly suitable for supporting accounting operations such as matching purchase data with invoice data in companies and other organizations. [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 device 11. Joined Result Table 12 Temporary Table 21 Data Generation Unit 22 Payment Matching Inquiry Department 23 Output Control Unit 24 Adjustment amount calculation section 25 Display Control Unit 26 Combined Result Data Generation Unit 27 Difference detection unit 28 Final Data Generation Unit 29. Procurement Data Generation Department 30 Payment Request Data Generation Unit 31 First detection unit 32 Second detection unit 33 Third detection unit

Claims

1. A combined result data generation unit generates combined result data that includes the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total purchase amount including the purchase amount after the invoice closing date for each product number, based on purchase data including the purchase date on which goods were purchased from a trading partner, a unique product number assigned to each of the purchased goods from the trading partner, and the purchase amount of the goods, and invoice data including the invoice amount from the trading partner, the invoice closing date, and the unique product number assigned to each of the goods corresponding to the invoice amount. A payment matching inquiry unit comprising: a first detection unit that detects combined result data where the invoice amount and the purchase amount on the billing closing date are the same amount as combined result data that does not require correction; a second detection unit that detects combined result data where 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 where 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 where the difference between the invoice amount and the total aggregate purchase amount is outside a 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 device having the following features.

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. The business support device according to claim 1, characterized by the following:

3. The combined result data generation unit regenerates the 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, 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 necessary, as detected by the first detection unit, the second detection unit, and the third detection unit, to the regenerated combined result data, based on the combined result data. A final acquired data generation unit generates final acquired data that includes payment target data in which the purchase amount on the billing closing date or the total aggregate purchase amount of the temporary data with the detection result requiring correction is excluded from payment, and payment target data in which the purchase amount on the billing closing date or the total aggregate purchase amount of the temporary data with the detection result not requiring correction is subject to payment. Based on the aforementioned temporary data, a difference detection unit detects, for each product number, the difference between the invoiced amount and the purchase amount on the invoice closing date, and the difference between the invoiced amount and the total aggregated purchase amount. The system further comprises an adjustment amount calculation unit that calculates the sum of each of the detected differences as an adjustment amount, The output control unit outputs the final acquired data and the adjusted amount via the external device. The business support device according to claim 2, characterized by the following:

4. A purchase data generation unit generates purchase data with the aforementioned trading partner as the payee, the aforementioned purchase date, and the aforementioned adjustment amount as the purchase amount. The system further comprises a payment request data generation unit that generates payment request data with the aforementioned trading partner as the payee, a predetermined payment request date, and a payment request amount that includes the total amount of all aggregated purchase amounts for each of the aforementioned product numbers plus the purchase amount corresponding to the adjustment amount, 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. The business support device according to claim 3, characterized by the following:

5. The combined result data generation step involves a combined result data generation unit that generates combined result data including the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total purchase amount including the purchase amount after the invoice closing date for each product number, based on purchase data including the purchase date on which goods were purchased from a trading partner, a unique product number assigned to each of the purchased goods from the trading partner, and the purchase amount of the goods, and invoice data including the invoice amount from the trading partner, the invoice closing date, and a unique product number assigned to each of the goods corresponding to the invoice amount, and the invoice result data that generates combined result data including the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total purchase amount including the purchase amount after the invoice closing date for each product number, and the payment matching inquiry unit, among the combined result data, A payment matching inquiry step comprising: a first detection unit that detects combined result data where the invoiced amount and the purchase amount on the invoice closing date are the same amount as combined result data that does not require correction; a second detection unit that detects combined result data where the invoiced amount and the total aggregate purchase amount are the same amount as combined result data that does not require correction, detects combined result data where the difference between the invoiced 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 where the difference between the invoiced amount and the total aggregate purchase amount is outside a predetermined 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. A business support method that has the following characteristics.

6. Computers, A combined result data generation unit generates combined result data that includes the invoice amount for each product number, the purchase amount up to the invoice closing date for each product number, and the total purchase amount including the purchase amount after the invoice closing date for each product number, based on purchase data including the purchase date on which goods were purchased from a trading partner, a unique product number assigned to each of the purchased goods from the trading partner, and the purchase amount of the goods, and invoice data including the invoice amount from the trading partner, the invoice closing date, and the unique product number assigned to each of the goods corresponding to the invoice amount. A payment matching inquiry unit comprising: a first detection unit that detects combined result data where the invoice amount and the purchase amount on the billing closing date are the same amount as combined result data that does not require correction; a second detection unit that detects combined result data where 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 where 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 where the difference between the invoice amount and the total aggregate purchase amount is outside a predetermined allowable amount as combined result data that requires correction; Output control unit outputs the detection results of the first detection unit and the second detection unit via an external device. A business support program designed to function as such.

Images