Discrepancy management device, discrepancy management method, and discrepancy management program

Abstract

A discrepancy management device, discrepancy management method, and discrepancy management program for identifying discrepancy factors at the time of settlement. [Solution] In the discrepancy management device, the storage unit stores discrepancy data relating to discrepancies between the invoiced amount and the scheduled payment amount for each payee. The control unit includes a discrepancy data determination means (determination unit) that determines whether or not unresolved discrepancy data is stored in the storage unit at the payee each time a payment request is received, and an update unit that, if a discrepancy occurs between the invoiced amount and the scheduled payment amount in the payment request and no unresolved discrepancy data is stored in the storage unit at the payee of the payment request, generates discrepancy data relating to the discrepancy occurring between the invoiced amount and the scheduled payment amount, and updates the discrepancy data stored in the storage unit by making changes to the unresolved discrepancy data in accordance with the input processing entered by the operator at the time of the payment request, if unresolved discrepancy data is stored in the storage unit at the payee of the payment request.

Description

Technical Field

[0001] The present invention relates to a discrepancy management device, a discrepancy management method, and a discrepancy management program.

Background Art

[0002] Conventionally, in commercial transactions, a discrepancy may occur between the amount billed by the payee and the amount scheduled for payment by the company itself. For example, in Patent Document 1, when reconciling the expected collection amount of sales data and the received amount of payment data, if the discrepancy amount (difference) is not "0", based on the discrepancy reason selected by the operator, the discrepancy reason and the discrepancy amount are registered in the payment reconciliation data, and the sales data and the payment data are updated.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, for example, in the payment business to payees with a large number of traded items, there are cases where differences occur in unit price and quantity between the payee and the company itself, or cases where the company does not pay some of the contents held in the payee's invoice. There are cases where a discrepancy occurs between the billed amount and the scheduled payment amount. In such cases, it is difficult for the company to hold the unpaid amount as a debt, so it may be difficult to trace back and confirm the discrepancy factors with both companies when the accounts payable do not match at the end of the month or at the end of the period.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a discrepancy management device, a discrepancy management method, and a discrepancy management program that enable easily grasping the discrepancy factors at the time of settlement and accelerating the settlement work. [Means for solving the problem]

[0006] To solve the above-mentioned problems and achieve the objective, the discrepancy management device according to the present invention is a discrepancy management device comprising a storage unit and a control unit, wherein the storage unit includes a discrepancy data storage means for storing discrepancy data relating to discrepancies between the billed amount and the scheduled payment amount for each payee, and the control unit comprises a discrepancy data determination means for determining whether or not unresolved discrepancy data is stored in the storage unit at the payee of the payment request each time a payment request is received, and an update means for generating discrepancy data relating to the discrepancy occurring between the billed amount and the scheduled payment amount when a discrepancy occurs between the billed amount and the scheduled payment amount in the payment request and unresolved discrepancy data is not stored in the storage unit at the payee of the payment request, and updating the discrepancy data stored in the storage unit by modifying the unresolved discrepancy data in accordance with the input processing entered by the operator at the time of the payment request when unresolved discrepancy data is stored in the storage unit at the payee of the payment request.

[0007] Furthermore, the discrepancy management device according to the present invention is characterized in that the discrepancy data includes a section that holds whether or not the discrepancy has been resolved, and the update means updates the discrepancy data in accordance with the input processing from the operator regarding the section included in the discrepancy data.

[0008] Furthermore, the discrepancy management device according to the present invention further includes a section in which the discrepancy data holds the discrepancy amount between the invoiced amount and the scheduled payment amount, the control unit further includes a payment request registration means that completes the registration of the payment request on the condition that there is no difference between the added amount obtained by adding the discrepancy amount included in the discrepancy data to the invoiced amount and the scheduled payment amount, and the update means changes the numerical value of the discrepancy amount included in the discrepancy data in response to the input processing from the operator regarding the section that holds whether or not the discrepancy included in the discrepancy data has been resolved.

[0009] Furthermore, the discrepancy management device according to the present invention is characterized in that the discrepancy data determination means determines whether or not unresolved discrepancy data is stored in the storage unit at the payee of the payment request, based on the status of the category included in the discrepancy data of the payee of the payment request.

[0010] Furthermore, the discrepancy management device according to the present invention is characterized in that the control unit further comprises: a discrepancy determination means that determines whether or not a discrepancy has occurred between the billed amount and the scheduled payment amount each time a payment request is received; and a display control means that causes a discrepancy details creation screen for registering the cause of the discrepancy to be displayed on the display unit when a discrepancy has occurred or when unresolved discrepancy data is stored in the storage unit at the payee of the payment request.

[0011] Furthermore, the discrepancy management device according to the present invention is characterized in that the discrepancy data includes the cause and amount of the discrepancy between the invoiced amount and the scheduled payment amount, and the control unit further comprises output control means that outputs accounts payable balance confirmation statements including the cause and amount of the discrepancy for each payee for each accounting month.

[0012] Furthermore, the discrepancy management method according to the present invention is a discrepancy management method performed in a discrepancy management device comprising a storage unit and a control unit, wherein the storage unit stores discrepancy data relating to discrepancies between the billed amount and the scheduled payment amount, and the control unit, each time a payment request is received, includes a discrepancy data determination step of determining whether or not unresolved discrepancy data is stored in the storage unit at the payee of the payment request, and if a discrepancy occurs between the billed amount and the scheduled payment amount in the payment request and unresolved discrepancy data is not stored in the storage unit at the payee of the payment request, it generates discrepancy data relating to the discrepancy occurring between the billed amount and the scheduled payment amount, and if unresolved discrepancy data is stored in the storage unit at the payee of the payment request, it updates the discrepancy data stored in the storage unit by making changes to the unresolved discrepancy data in accordance with the input processing entered by the operator at the time of the payment request.

[0013] Furthermore, the discrepancy management program according to the present invention is a discrepancy management program to be executed by a discrepancy management device comprising a storage unit and a control unit, wherein the storage unit stores discrepancy data relating to discrepancies between the billed amount and the scheduled payment amount, and the control unit, each time a payment request is received, performs a discrepancy data determination step of determining whether or not unresolved discrepancy data is stored in the storage unit at the payee of the payment request, and if a discrepancy occurs between the billed amount and the scheduled payment amount in the payment request and unresolved discrepancy data is not stored in the storage unit at the payee of the payment request, generates discrepancy data relating to the discrepancy occurring between the billed amount and the scheduled payment amount, and if unresolved discrepancy data is stored in the storage unit at the payee of the payment request, updates the discrepancy data stored in the storage unit by making changes to the unresolved discrepancy data in accordance with the input processing entered by the operator at the time of the payment request. [Effects of the Invention]

[0014] According to the present invention, it is possible to easily identify the causes of discrepancies at the time of settlement, and this has the effect of accelerating the settlement process. [Brief explanation of the drawing]

[0015] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of a discrepancy management device according to an embodiment. [Figure 2] Figure 2 is a flowchart showing an example of processing by the discrepancy management device according to this embodiment. [Figure 3] Figure 3 shows an example of payment schedule data according to an embodiment. [Figure 4] Figure 4 shows an example of billing data according to this embodiment. [Figure 5] Figure 5 shows an example of a payment request input screen according to the embodiment. [Figure 6] Figure 6 shows an example of a screen for creating discrepancy details according to this embodiment. [Figure 7] Figure 7 is a diagram showing an example of a payment request input screen according to an embodiment. [Figure 8] Figure 8 is a diagram showing an example of payment request data according to an embodiment. [Figure 9] Figure 9 is a diagram showing an example of payment schedule data according to an embodiment. [Figure 10] Figure 10 is a diagram showing an example of difference calculation data according to an embodiment. [Figure 11] Figure 11 is a diagram showing an example of payment schedule data according to an embodiment. [Figure 12] Figure 12 is a diagram showing an example of billing data according to an embodiment. [Figure 13] Figure 13 is a diagram showing an example of a payment request input screen according to an embodiment. [Figure 14] Figure 14 is a diagram showing an example of a difference calculation details creation screen according to an embodiment. [Figure 15] Figure 15 is a diagram showing an example of difference calculation data according to an embodiment. [Figure 16] Figure 16 is a diagram showing an example of payment schedule data according to an embodiment. [Figure 17] Figure 17 is a diagram showing an example of billing data according to an embodiment. [Figure 18] Figure 18 is a diagram showing an example of a payment request input screen according to an embodiment. [Figure 19] Figure 19 is a diagram showing an example of a difference calculation details creation screen according to an embodiment. [Figure 20] Figure 20 is a diagram showing an example of a payment request input screen according to an embodiment. [Figure 21] Figure 21 is a diagram showing an example of difference calculation data according to an embodiment. [Figure 22] Figure 22 is a flowchart showing an example of processing by a difference calculation management device according to an embodiment. [Figure 23] Figure 23 is a diagram showing an example of payment schedule data according to an embodiment. [Figure 24]Figure 24 shows an example of discrepancy data according to the embodiment. [Figure 25] Figure 25 shows an example of a debt balance file according to the present invention. [Figure 26] Figure 26 shows an example of an accounts payable balance confirmation statement according to the present invention. [Figure 27] Figure 27 shows an example of payment schedule data according to an embodiment. [Figure 28] Figure 28 shows an example of billing data according to this embodiment. [Figure 29] Figure 29 shows an example of a payment request input screen according to the embodiment. [Figure 30] Figure 30 shows an example of a screen for creating discrepancy details according to the embodiment. [Figure 31] Figure 31 shows an example of discrepancy data according to the embodiment. [Figure 32] Figure 32 shows an example of an accounts payable balance confirmation statement according to the present invention. [Modes for carrying out the invention]

[0016] Embodiments of the discrepancy management device, discrepancy management method, and discrepancy management program according to the present invention will be described in detail below with reference to the drawings. However, the present invention is not limited to these embodiments.

[0017] [1. Structure] An example of the configuration of the discrepancy management device according to this embodiment will be described with reference to Figure 1. Figure 1 is a block diagram showing an example of the configuration of the discrepancy management device 100 according to this embodiment.

[0018] As shown in Figure 1, the discrepancy management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108, and is connected to a server 200 (e.g., a web server) that stores various data (for example, the data stored in the storage unit 106, which will be described later) via a network 300 (e.g., the Internet, an intranet, a LAN (Local Area Network)).

[0019] Each component of the discrepancy management device 100 is connected to communicate via any communication channel.

[0020] The discrepancy management device 100 may be a stationary device such as a desktop personal computer, or it may be a portable device such as a notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0021] The control unit 102 is a CPU or similar component that comprehensively controls the discrepancy management device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0022] Functionally, the control unit 102 includes an acquisition unit 102a, a determination unit 102b, a payment request registration unit 102c, an update unit 102d, a display control unit 102e, an output control unit 102f, and the like.

[0023] The acquisition unit 102a acquires payment schedule data and invoice data each time a payment request is received. The payment schedule data is data that associates the product name of the goods purchased from the payee with the scheduled payment amount. The scheduled payment amount is the amount obtained by multiplying the quantity purchased by the unit price for each purchased product. The invoice data is data based on the invoice received from the payee (supplier) and may include the product name, quantity, price, and invoice amount. The price of the goods is the amount obtained by multiplying the quantity by the unit price, and the invoice amount is the sum of the prices for each item.

[0024] The acquisition unit 102a acquires payment schedule data, discrepancy data, and debt balance file each time it receives settlement processing. The discrepancy data is data relating to discrepancies between the invoiced amount and the scheduled payment amount for each payee, and may include a section that holds whether the discrepancy has been resolved or not, a section that holds the amount of the discrepancy between the invoiced amount and the scheduled payment amount, and the cause and amount of the discrepancy between the invoiced amount and the scheduled payment amount. The invoiced amount is the amount based on the invoice data and is the sum of the amounts for each product. The cause and amount of the discrepancy between the invoiced amount and the scheduled payment amount are the products and amounts involved in the discrepancy within the company and the products and amounts involved in the discrepancy at the payee. The debt balance file is a file that associates the accounting year and month with the debt balance for each payee. The debt balance is the total amount of scheduled payments to the payee.

[0025] Each time a payment request is received, the determination unit 102b determines whether or not there is unresolved discrepancy data at the payee of the payment request stored in the storage unit 106. Specifically, the determination unit 102b determines whether or not there is unresolved discrepancy data at the payee of the payment request stored in the storage unit 106 based on the state of the category that holds whether or not the discrepancies included in the discrepancy data of the payee of the payment request have been resolved.

[0026] The determination unit 102b determines whether there is a discrepancy between the invoiced amount and the scheduled payment amount each time a payment request is received. Specifically, the determination unit 102b determines whether there is a difference between the scheduled payment amount included in the scheduled payment data acquired by the acquisition unit 102a and the invoiced amount included in the invoice data. Here, the determination unit 102b determines that a discrepancy has occurred if there is a difference between the scheduled payment amount and the invoiced amount.

[0027] The payment request registration unit 102c completes the registration of the payment request on the condition that there is no difference between the amount calculated by adding the discrepancy amount included in the discrepancy data to the invoiced amount and the scheduled payment amount.

[0028] The update unit 102d generates discrepancy data relating to the discrepancy between the invoiced amount and the scheduled payment amount if a discrepancy occurs between the invoiced amount and the scheduled payment amount in a payment request, and if the unresolved discrepancy data is not stored in the storage unit 106 at the payee of the payment request. If the unresolved discrepancy data is stored in the storage unit 106 at the payee of the payment request, the update unit 102d updates the discrepancy data stored in the storage unit 106 by modifying the unresolved discrepancy data according to the input processing entered by the operator when making the payment request. The update unit 102d updates the discrepancy data according to the input processing from the operator regarding the category that holds whether the discrepancy included in the discrepancy data has been resolved or not. Specifically, the update unit 102d changes the numerical value of the discrepancy amount included in the discrepancy data according to the input processing from the operator regarding the category that holds whether the discrepancy included in the discrepancy data has been resolved or not.

[0029] The display control unit 102e displays a discrepancy details creation screen on the display device of the output device 500 for registering the cause of the discrepancy if a discrepancy has occurred or if unresolved discrepancy data is stored in the storage unit 106 at the payee of the payment request. In other words, the display control unit 102e displays a discrepancy details creation screen on the display device of the output device 500 if the registration of the payment request is not completed. The discrepancy details creation screen is a screen for generating and updating discrepancy data, and includes the company's acceptance details and the payee's acceptance details, etc.

[0030] The output control unit 102f outputs accounts payable balance confirmation statements, including the cause and amount of any discrepancies, for each payee for each accounting month. Specifically, the output control unit 102f outputs accounts payable balance confirmation statements from the output device 500 based on the payment schedule data, discrepancy data, and debt balance file acquired each time a settlement process is accepted. The accounts payable balance confirmation statements are output for each payee and may include accounts payable balance, discrepancy amount, and details of the discrepancy.

[0031] The communication interface unit 104 connects the discrepancy management device 100 to the network 300 in a communicative manner via communication devices such as routers and wired or wireless communication lines such as dedicated lines. The communication interface unit 104 also has the function of communicating data with other devices via communication lines.

[0032] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0033] The storage unit 106 stores the customer master 106a, billing data 106b, payment schedule data 106c, payment request data 106d, discrepancy data 106e, and debt balance file 106f.

[0034] The billing address master 106a contains records for each supplier (payee) from which goods were purchased, associating the payee code with the scheduled payment date, and is referenced by the acquisition unit 102a. Each time a payee is added, a record is added to the billing address master 106a. Furthermore, the above records can be updated as needed.

[0035] The billing data 106b is generated based on the invoice received from the payee and stored in the storage unit 106. The billing data 106b is retrieved by the retrieval unit 102a.

[0036] The payment schedule data 106c is data based on purchase data recorded in the purchase input, and is acquired by the acquisition unit 102a when a payment request is received, updated, and stored.

[0037] The payment request data 106d contains records that associate the payment request number with the payee, payment request amount, invoice amount, etc., and is generated and stored by the payment request registration unit 102c.

[0038] The discrepancy data 106e is generated and updated by the update unit 102d.

[0039] The debt balance file 106f stores the debt balance for each payee calculated by the update unit 102d. Specifically, the update unit 102d performs an update that adds to the debt balance amount based on the payment schedule data after the payment request is registered, and an update that subtracts the amount equivalent to the payment from the debt balance amount based on the payment data created after the payment operation is executed.

[0040] The input / output interface unit 108 is connected to an input device 400 and an output device 500. The output device 500 includes display devices such as displays and projectors, sound devices such as speakers, printing devices such as printers, and devices that allow data to be downloaded in data file format. The data file format can be any file format known in this field, such as PDF, CSV, document files, spreadsheet software files, or text files. The input device 400 can include a keyboard, mouse, and microphone, as well as a monitor that works in conjunction with the mouse to provide pointing device functionality.

[0041] [2. Specific Examples] The information processing by the discrepancy management device 100 according to this embodiment will be explained below using a specific example. Here, the discrepancy management device 100 performs, for example, the process of registering a payment request to the accounting department in response to purchase input received from the sales department, and the process of issuing an accounts payable balance confirmation statement at the time of settlement. The process related to payment request registration will be explained below using Figures 2 to 21. The process related to the issuance of accounts payable balance confirmation statements will be explained using Figures 22 to 32.

[0042] Figure 2 is a flowchart showing an example of processing by the discrepancy management device according to this embodiment.

[0043] The discrepancy management device 100 receives payment requests based on purchase inputs received from the sales department (S101).

[0044] The acquisition unit 102a, in response to a payment request, obtains payment schedule data by referring to the billing destination master 106a, and also obtains billing data for the payee corresponding to the payment request (S102).

[0045] The determination unit 102b determines whether there is a difference between the payment amount included in the payment schedule data and the invoice amount included in the invoice data, and whether any unresolved discrepancies are stored in the storage unit 106 (S103, S105).

[0046] If there is no difference between the scheduled payment amount and the invoiced amount, and there are no unresolved discrepancies (S103, Yes), the payment request registration unit 102c completes the registration of the payment request (S104).

[0047] If there is a difference between the scheduled payment amount and the invoiced amount, and there is no outstanding discrepancy data (S103, No, and S105, Yes), the display control unit 102e displays an additional discrepancy details creation screen on the display device of the output device 500 and accepts input from the operator via the input device 400 (S106). The payment request registration unit 102c determines whether the input result satisfies "(invoiced amount + discrepancy amount) - scheduled payment amount = 0" (S107).

[0048] If the condition "(Invoice Amount + Discrepancy Amount) - Scheduled Payment Amount = 0" is met (S107, Yes), the update unit 102d generates discrepancy data (S108), and the payment request registration unit 102c completes the registration of the payment request (S104). If the condition "(Invoice Amount + Discrepancy Amount) - Scheduled Payment Amount = 0" is not met in the determination in S107 (S107, No), the process in S106 continues.

[0049] If there is a difference (or no difference) between the scheduled payment amount and the invoiced amount, and there is unresolved discrepancy data (S103, No, and S105, No), the display control unit 102e displays a screen for creating discrepancy details for modification on the display device of the output device 500 and accepts input from the operator via the input device 400 (S109). The payment request registration unit 102c determines whether the input result satisfies "(invoiced amount + discrepancy amount) - scheduled payment amount = 0" (S110).

[0050] If the condition "(Invoice Amount + Discrepancy Amount) - Scheduled Payment Amount = 0" is met (S110, Yes), the update unit 102d modifies the discrepancy data (S111), and the payment request registration unit 102c completes the registration of the payment request (S104). If the condition "(Invoice Amount + Discrepancy Amount) - Scheduled Payment Amount = 0" is not met in the determination in S110 (S110, No), the process in S109 continues.

[0051] As described above, the discrepancy management device 100 generates and modifies discrepancy data according to the situation, and the details of these processes will be explained using various cases as examples.

[0052] (Generating discrepancies in data) Discrepancy data is generated by the update unit 102d, for example, when a discrepancy occurs during a payment request and the corresponding discrepancy data for the payee is not stored in the storage unit 106. The following explanation will use the case of making a payment request for an invoice due at the end of January from "□△ Industries" with payee code "SI001" as an example. Figure 3 shows an example of payment schedule data according to the embodiment. Figure 4 shows an example of invoice data according to the embodiment. Figure 5 shows an example of a payment request input screen according to the embodiment.

[0053] The display control unit 102e displays the payment request input screen shown in Figure 5 on the display device of the output device 500 in response to an operation to start inputting a payment request via the input device 400. The payment request input screen includes, for example, a header screen for inputting the payee and the scheduled payment date, a purchase data selection screen for selecting purchase data, and a footer screen for displaying various amounts, as shown in Figure 5. When the operator inputs "SI001" for the payee on the header screen of the payment request input screen shown in Figure 5, the acquisition unit 102a refers to the billing address master and acquires the scheduled payment date "2024 / 1 / 31" for the payee "□△ Industries" corresponding to "SI001," and also acquires the scheduled payment data shown in Figure 3.

[0054] Here, the acquisition unit 102a determines the payment schedule data (shown in Figure 3) to be forwarded to the payment process from the purchase data by matching the purchase data recorded in the purchase input with the billing data based on the invoice received from the payee. For example, the acquisition unit 102a acquires the billing data shown in Figure 4 based on the payee entered by the operator and matches it with the purchase data. The billing data stores, for example, records consisting of a combination of "product name," "quantity," "item amount," and "total amount," as well as the total amount obtained by summing up the amounts of all products, as shown in Figure 4. The billing data shown in Figure 4 includes the item amount (total amount) of "product A" (3 units) at "165 yen," the item amount (total amount) of "product B" (2 units) at "110 yen," the item amount (total amount) of "product C" (1 unit) at "55 yen," and the sum of the item amounts (total amounts) of the three types of products at "330 yen."

[0055] The acquisition unit 102a determines whether products A to C included in the invoice data are included in the purchase data. If product C is not included in the purchase data (i.e., not purchased), the acquisition unit 102a acquires payment schedule data that includes only products A and B. For example, the payment schedule data acquired by the acquisition unit 102a stores records consisting of a combination of "payment schedule number," "purchase date," "payee," "payment schedule amount," "payment request number," "product name," and "quantity," as shown in Figure 3. The payment schedule data record shown in Figure 3 indicates, for example, that the payment schedule amount for "3 units" of "product A" purchased from payee "SI001:□△ Industries" on purchase date "2023 / 12 / 1" is "165 yen," and that it is managed with payment schedule number "SH2020000001-01." Furthermore, the payment schedule data record shown in Figure 3 indicates, for example, that the payment schedule for "2 units" of "Product B" purchased from the payee "SI001:□△ Industries" on the purchase date "2023 / 12 / 5" is "110 yen" and is managed under the payment schedule number "SH2020000001-02".

[0056] When the acquisition unit 102a acquires the payment schedule data shown in Figure 3, the display control unit 102e displays the corresponding items of the payment schedule data in each item of the purchase data selection screen, as shown in the purchase data selection screen in Figure 5. Here, as shown in Figure 5, the purchase data selection screen has a display area corresponding to each record of the payment schedule data, and each display area is associated with a payment request checkbox for specifying whether to register it as a payment request. The target to be registered as a payment request is determined when the operator checks the payment request checkbox via the input device 400.

[0057] Once the items to be registered in the payment request are determined, the display control unit 102e displays various amounts on the footer screen of the payment request input screen, as shown in Figure 5. The amount invoiced by the other party included in the footer screen is the amount registered in advance based on the invoice data. The amount to be paid this time included in the footer screen is the sum of the amounts for which the payment request checkbox has been checked among the payment schedule data displayed on the purchase data selection screen. The total amount to be paid this time is displayed in the footer screen. The discrepancy amount included in the footer screen is the discrepancy amount registered on the discrepancy details creation screen, which will be described later. The difference amount included in the footer screen is the result of the calculation "(Amount invoiced by the other party + Discrepancy amount) - Amount to be paid this time".

[0058] For example, since the total of the billing data shown in Figure 4 is "330 yen", the display control unit 102e displays "330 yen" in the "Amount Billed by the Other Party" section of the footer screen, as shown in Figure 5. Also, since the payment request checkboxes for "Product A" and "Product B" are checked on the purchase data selection screen, the display control unit 102e displays "275 yen" as the current payment amount, which is the sum of the current matching amounts for each product, "165 yen" and "110 yen". Since the current payment amount is only "275 yen", the display control unit 102e displays "275 yen" in the total. Furthermore, the display control unit 102e calculates "(330 + 0) - 275 = 55" and displays "55 yen" as the difference section of the footer screen.

[0059] Here, as shown in Figure 5, a difference of "55 yen" has occurred in this payment request, so the payment request registration unit 102c does not complete the registration of the payment request based on the payment request input shown in Figure 5. Also, since the discrepancy data for the payee "SI001: □△ Industries" is not registered in the storage unit 106, the display control unit 102e displays an additional discrepancy detail creation screen for generating discrepancy data on the display device of the output device 500. Figure 6 is a diagram showing an example of a discrepancy detail creation screen according to the embodiment. The additional discrepancy detail creation screen includes items such as "payment request number", "line number", "voucher date", "resolution category", "company inspection details", "customer inspection details", "number of discrepancies", "unit price of discrepancies", "amount of discrepancies (excluding tax)", "consumption tax on discrepancies", "amount of discrepancies", and "reason for discrepancies", as shown in Figure 6.

[0060] The discrepancy details creation screen displays each item according to the input results in the payment schedule data, invoice data, and payment request input screen. For example, since the cause of the discrepancy that occurred in the payment request input in Figure 5 is the invoice for "Product C" included in the invoice data, the discrepancy details addition input screen shown in Figure 6 displays information about "Product C" in each item of "Customer Inspection Details". In addition, based on the numerical values ​​of each item in "Customer Inspection Details", "Number of discrepancies: 1", "Discrepancy unit price: 50", "Discrepancy amount (excluding tax): -50", "Discrepancy consumption tax: -5", and "Discrepancy amount: -55" are displayed. Here, "Discrepancy amount (excluding tax)", "Discrepancy consumption tax", and "Discrepancy amount" are each given a minus sign because the payment amount this time is negative compared to the customer's invoice amount. "Reason for discrepancy" is an item entered by the operator, for example, "Uninspected goods are on the invoice, payment next time" may be entered.

[0061] The "Resolution Status" on the discrepancy details creation screen indicates whether the discrepancy cause has been resolved or not. When creating a new entry, it is set to "0: Unresolved" as shown in Figure 6. This status can be changed by the operator to "1: Resolved (Discrepancy Amount Not Reflected)" or "2: Resolved (Discrepancy Amount Reflected and Sign Determination)" when the discrepancy is resolved. This will be explained in detail later. In the example above, the case where the discrepancy cause is one product (product C) was explained, but the embodiment is not limited to this, and multiple products may be involved in the discrepancy. In such cases, discrepancy details for each product will be registered with different line numbers.

[0062] As shown in Figure 6, when a discrepancy detail is created on the additional discrepancy detail creation screen, the display control unit 102e updates the display on the payment request input screen based on the discrepancy detail. Figure 7 shows an example of the payment request input screen according to the embodiment. For example, as shown in Figure 7, the display control unit 102e inputs "Discrepancy Amount: -55" from the discrepancy detail creation screen into "Discrepancy Amount" on the payment request input screen. As a result, "(Amount billed by the other party + Discrepancy Amount) - Amount to be paid this time = (330 - 55) - 275 = 0", and the difference becomes "0 yen".

[0063] At this point, since the difference is "0", the payment request registration unit 102c generates payment request data and completes the registration of the payment request. Figure 8 is a diagram showing an example of payment request data according to the embodiment. The payment request data stores records consisting of a combination of "payment request number", "scheduled payment date", "payee", "payment request amount", and "amount invoiced by the other party", as shown in Figure 8. For a payment request with a scheduled payment date of "2024 / 1 / 31", payee of "SI001:□△ Industries", payment request amount of "275 yen", and amount invoiced by the other party of "330 yen", the payment request registration unit 102c generates payment request data with the payment request number "SI200000001" and stores it in the storage unit 106.

[0064] Furthermore, the payment request registration unit 102c registers a payment request number for the payment schedule data acquired by the acquisition unit 102a. Figure 9 is a diagram showing an example of payment schedule data according to the embodiment. Here, the payment schedule data shown in Figure 9 shows the payment schedule data shown in Figure 3 with the payment request number registered. For example, as shown in Figure 9, the payment request registration unit 102c registers the payment request number "SI200000001" for each record of the payment schedule data acquired by the acquisition unit 102a and stores it in the storage unit 106.

[0065] Once the registration of the payment request is complete, the update unit 102d generates discrepancy data based on the information entered on the discrepancy details creation screen. Figure 10 shows an example of discrepancy data according to the embodiment. The discrepancy data stores records that combine, for example, "payment request number", "line number", "payee", "resolution flag", "company slip number", "company product code", "company quantity", "other company slip number", "other company product code", "other company quantity", "other company unit price", "other company payment amount", "other company consumption tax amount", "discrepancy amount", "discrepancy amount excluding tax", and "discrepancy amount". As shown in Figure 10, the update unit 102d generates discrepancy data for the payment request number "SI200000001" based on the discrepancy detail creation screen shown in Figure 6, associating it with "Line number: 1", "Resolution flag: 0: Unresolved", "Customer product code: SH003", "Customer quantity: 1", "Customer unit price: 50", "Customer payment amount: 50", "Customer consumption tax amount: 5", "Discrepancy amount: -55", "Discrepancy amount excluding tax: -5", and "Discrepancy base amount: -50", and stores it in the storage unit 106.

[0066] As described above, the discrepancy management device 100 according to this embodiment generates and stores discrepancy data in payment requests, making it easy to identify the cause of discrepancies at the time of settlement and thus enabling the settlement process to be expedited.

[0067] (Correction of discrepancy data) Changes to discrepancy data occur when a payment request is made. The discrepancy data corresponding to the payee is stored in the storage unit 106, and the update unit 102d modifies it when the resolution flag in the discrepancy data is changed. The following explanation uses the example of making a payment request for an invoice due at the end of February from "□△ Industries" with payee code "SI001". That is, the explanation will describe the case in which the discrepancy data stored in the storage unit 106 during the generation of the above discrepancy data is changed. In this case, when changing discrepancy data, there are two cases: one where unaccepted goods (goods C) are purchased and then goods C is again included in the invoice due at the end of February received from the payee, and another where goods C is not included in the invoice due at the end of February, but payment processing is based on the invoice due at the end of January.

[0068] First, we will explain the case where product C is again included in the invoice received from the payee at the end of February. Figure 11 is a diagram showing an example of payment schedule data according to the embodiment. Figure 12 is a diagram showing an example of invoice data according to the embodiment. Figure 13 is a diagram showing an example of a payment request input screen according to the embodiment. The display control unit 102e displays the payment request input screen shown in Figure 13 on the display device of the output device 500 in response to an operation to start payment request input via the input device 400. When the operator enters "SI001" for the payee in the header screen of the payment request input screen shown in Figure 13, the acquisition unit 102a refers to the invoice master and acquires the payment schedule date "2024 / 2 / 29" for the payee "□△ Industries" corresponding to "SI001", and also acquires the payment schedule data shown in Figure 11.

[0069] Here, the acquisition unit 102a determines the payment schedule data (shown in Figure 11) to be forwarded to the payment process from the purchase data by matching the purchase data recorded in the purchase input with the billing data based on the invoice received from the payee. For example, the acquisition unit 102a acquires the billing data shown in Figure 12 based on the payee entered by the operator and matches it with the purchase data. The billing data for the invoice due at the end of February includes, for example, the itemized amount (total amount) of "1 unit" of "product C" of "55 yen", the itemized amount (total amount) of "5 units" of "product D" of "550 yen", and the sum of the itemized amounts (total amounts) of the two products, "605 yen".

[0070] The acquisition unit 102a determines whether products C and D included in the invoice data are included in the purchase data and acquires the payment schedule data shown in Figure 11. For example, the payment schedule data acquired by the acquisition unit 102a includes a record associated with "Payment Schedule Number: SH2020000002-01", "Purchase Date: 2024 / 1 / 6", "Payee: SI001: □△ Industries", "Payment Amount: 55 yen", "Product Name: Product C", and "Quantity: 1", as shown in Figure 11, and a record associated with "Payment Schedule Number: SH2020000002-02", "Purchase Date: 2024 / 1 / 9", "Payee: SI001: □△ Industries", "Payment Amount: 550 yen", "Product Name: Product D", and "Quantity: 5".

[0071] When the acquisition unit 102a acquires the payment schedule data shown in Figure 11, the display control unit 102e displays the corresponding items of the payment schedule data in each item of the purchase data selection screen, as shown in the purchase data selection screen in Figure 13. The operator determines which items to register as payment requests by checking the payment request checkbox in the display area corresponding to each record via the input device 400.

[0072] Once the items to be registered in the payment request are determined, the display control unit 102e displays various amounts in the footer screen of the payment request input screen, as shown in Figure 13. For example, since the total of the invoice data shown in Figure 12 is "605 yen", the display control unit 102e displays "605 yen" in the amount invoiced by the other party included in the footer screen, as shown in Figure 13. Also, since the payment request checkboxes for "Product C" and "Product D" have been checked on the purchase data selection screen, the display control unit 102e displays "605 yen", which is the sum of the current matching amounts for each product, "55 yen" and "550 yen", as the current payment amount. Furthermore, the display control unit 102e calculates "(605 + 0) - 605 = 0" and displays "0 yen" in the difference included in the footer screen.

[0073] Here, as shown in Figure 13, since the difference in this payment request is "0 yen", there is no error during registration. However, when the registration button is pressed, the display control unit 102e refers to the discrepancy data 106e stored in the storage unit 106 and determines whether there is any data with a resolution flag of "0: Unresolved" for the same payee. At the time of billing at the end of February, there is discrepancy data with a resolution flag of "0: Unresolved" for "Payee: SI001: □△ Industries", so the display control unit 102e displays a screen for creating a changeable discrepancy detail on the display device of the output device 500 to change the discrepancy data. Figure 14 is a diagram showing an example of a screen for creating a changeable discrepancy detail according to the embodiment. The screen for creating a changeable discrepancy detail first displays the contents of the screen that was displayed when the discrepancy data was generated (for example, the contents of the discrepancy detail creation screen shown in Figure 6).

[0074] When the operator makes a selection in the resolution category included in the displayed discrepancy details creation screen, the discrepancy details creation screen changes to the state shown in Figure 14. Specifically, as shown in Figure 14, when the operator selects "1: Resolved (No discrepancy amount reflected)" in the resolution category, it changes to "Discrepancy amount (excluding tax): 0", "Discrepancy consumption tax: 0", and "Discrepancy amount: 0". In "Reason for discrepancy", for example, the operator enters "Resolved because there were previously unbilled items on the invoice".

[0075] Thus, once the "Resolution Status" on the discrepancy details creation screen changes from "0: Unresolved" to "1: Resolved (Discrepancy Amount Not Reflected)" and the discrepancy details creation is complete, the resolution flag for "0: Unresolved" disappears, and since the difference in the payment request input is "0", the payment request registration unit 102c completes the registration of the payment request. Specifically, the payment request registration unit 102c generates payment request data with a payment request number assigned to it for a payment request with a scheduled payment date of "2024 / 2 / 29", payee of "SI001: □△ Industries", payment request amount of "605 yen", and amount billed by the other party of "605 yen", stores it in the storage unit 106, and registers the payment request number for the scheduled payment data shown in Figure 11.

[0076] Once the registration of the payment request is complete, the update unit 102d modifies the discrepancy data stored in the storage unit 106 based on the information entered on the discrepancy details creation screen. Figure 15 shows an example of discrepancy data according to the embodiment. As shown in Figure 15, the update unit 102d modifies the discrepancy data for payment request number "SI200000001" stored in the storage unit 106 by changing "Resolution Flag: 1: Resolved (Discrepancy amount not reflected)", "Discrepancy Amount: 0", "Discrepancy Amount Excluding Tax: 0", and "Discrepancy Body Amount: 0".

[0077] Next, we will explain the case where product C is not included in the invoice for the end of February, but payment processing is carried out based on the invoice for the end of January. Figure 16 is a diagram showing an example of payment schedule data according to the embodiment. Figure 17 is a diagram showing an example of invoice data according to the embodiment. Figure 18 is a diagram showing an example of a payment request input screen according to the embodiment. The display control unit 102e displays the payment request input screen shown in Figure 18 on the display device of the output device 500 in response to an operation to start payment request input via the input device 400. When the operator enters "SI001" for the payee in the header screen of the payment request input screen shown in Figure 18, the acquisition unit 102a refers to the billing address master and acquires the payment schedule date "2024 / 2 / 29" for the payee "□△ Industries" corresponding to "SI001", and also acquires the payment schedule data shown in Figure 16.

[0078] Here, the acquisition unit 102a determines the payment schedule data (shown in Figure 16) to be forwarded to the payment process from the purchase data by matching the purchase data recorded in the purchase input with the billing data based on the invoice received from the payee. For example, based on the payee entered by the operator, the acquisition unit 102a acquires the billing data shown in Figure 17 and the billing data for the end of January shown in Figure 4, and matches them with the purchase data. The billing data for the end of February includes, for example, the itemized amount (total amount) of "550 yen" for "5 units" of "product D" and the sum of the itemized amounts (total amounts) of "550 yen," as shown in Figure 17. Also, the billing data shown in Figure 4 includes the itemized amount (total amount) of "55 yen" for "1 unit" of "product C."

[0079] The acquisition unit 102a matches products C and D included in the billing data with the purchase data to obtain the payment schedule data shown in Figure 16. For example, the payment schedule data obtained by the acquisition unit 102a includes a record associated with "Payment Schedule Number: SH2020000002-01", "Purchase Date: 2024 / 1 / 6", "Payee: SI001: □△ Industries", "Payment Schedule Amount: 55 yen", "Product Name: Product C", and "Quantity: 1 unit", as shown in Figure 16, and a record associated with "Payment Schedule Number: SH2020000002-02", "Purchase Date: 2024 / 1 / 9", "Payee: SI001: □△ Industries", "Payment Schedule Amount: 550 yen", "Product Name: Product D", and "Quantity: 5 units".

[0080] When the acquisition unit 102a acquires the payment schedule data shown in Figure 16, the display control unit 102e displays the corresponding items of the payment schedule data in each item of the purchase data selection screen, as shown in the purchase data selection screen in Figure 18. The operator determines which items to register as payment requests by checking the payment request checkbox in the display area corresponding to each record via the input device 400.

[0081] Once the items to be registered in the payment request are determined, the display control unit 102e displays various amounts in the footer screen of the payment request input screen, as shown in Figure 18. For example, since the total of the billing data shown in Figure 17 is "550 yen", the display control unit 102e displays "550 yen" in the amount billed by the other party included in the footer screen, as shown in Figure 18. Also, since the payment request checkboxes for "Product C" and "Product D" have been checked on the purchase data selection screen, the display control unit 102e displays "605 yen", which is the sum of the current matching amounts for each product, "55 yen" and "550 yen", as the current payment amount. Furthermore, the display control unit 102e calculates "(550 + 0) - 605 = 0" and displays "55 yen" in the difference included in the footer screen.

[0082] Here, as shown in Figure 18, since the difference in this payment request is "55 yen", the payment request registration unit 102c does not complete the registration of the payment request. The display control unit 102e refers to the discrepancy data 106e stored in the storage unit 106 and determines whether there is any data with a resolution flag of "0: Unresolved" for the same payee in the discrepancy data. At the time of billing at the end of February, there is discrepancy data with a resolution flag of "0: Unresolved" for "Payee:SI001:□△ Industries", so the display control unit 102e displays a screen for creating a changeable discrepancy detail on the display device of the output device 500 in order to change the discrepancy data. Figure 19 is a diagram showing an example of a screen for creating a changeable discrepancy detail according to the embodiment. The screen for creating a changeable discrepancy detail first reflects the contents of the screen that was displayed when the discrepancy data was generated (for example, the contents of the discrepancy detail creation screen shown in Figure 6).

[0083] When the operator makes a selection on the displayed discrepancy details creation screen, the discrepancy details creation screen changes to the state shown in Figure 19. Specifically, as shown in Figure 19, when the operator selects "2: Resolved (Reflect discrepancy amount, reverse sign)" in the resolution category, the values ​​change to "Discrepancy amount (excluding tax): 50", "Discrepancy consumption tax: 5", and "Discrepancy amount: 55". For "Reason for discrepancy", the operator might enter, for example, "Resolved due to payment of previously unbilled items".

[0084] Thus, when the "Resolution Status" on the discrepancy details creation screen is changed from "0: Unresolved" to "2: Resolved (Discrepancy Amount Reflected, Sign Reversed)" and the discrepancy details creation is completed, the resolution flag for "0: Unresolved" disappears, and the discrepancy amount is reflected in the discrepancy amount in the payment request input. Figure 20 shows an example of the payment request input screen according to the embodiment. As shown in Figure 20, the "Discrepancy Amount: 55" that was changed in the discrepancy details creation is reflected in the discrepancy amount on the footer screen of the payment request input screen. As a result, the "Difference" calculated by the display control unit 102e becomes "(550 + 55) - 605 = 0".

[0085] Since the difference in the payment request input is "0", the payment request registration unit 102c completes the registration of the payment request. Specifically, the payment request registration unit 102c generates payment request data with a payment request number assigned to it for a payment request with a scheduled payment date of "2024 / 2 / 29", payee of "SI001:□△ Industries", payment request amount of "605 yen", and amount invoiced by the other party of "550 yen", stores it in the storage unit 106, and also registers the payment request number for the scheduled payment data shown in Figure 16.

[0086] Once the registration of the payment request is complete, the update unit 102d modifies the discrepancy data stored in the storage unit 106 based on the information entered on the discrepancy details creation screen. Figure 21 shows an example of discrepancy data according to the embodiment. As shown in Figure 21, the update unit 102d modifies the discrepancy data for payment request number "SI200000001" stored in the storage unit 106 by changing "Resolution Flag: 2: Resolved (Discrepancy Amount Reflected, Sign Reversed)", "Discrepancy Amount: 55", "Discrepancy Amount Excluding Tax: 5", and "Discrepancy Body Amount: 50".

[0087] The above describes the process of registering payment requests to the accounting department in response to purchase input received from the sales department. As described above, the discrepancy management device 100 can properly manage discrepancies for each payee by storing discrepancy data and updating the discrepancy data according to the payment status.

[0088] Next, we will explain the process by which the accounting department issues accounts payable balance confirmation statements at the time of closing. Figure 22 is a flowchart showing an example of the process by the discrepancy management device according to the embodiment.

[0089] The discrepancy management device 100 receives settlement processing from the accounting department (S201).

[0090] The acquisition unit 102a, upon receiving a settlement processing request, obtains payment schedule data by referring to the billing address master 106a, and also obtains discrepancy data and debt balance files for the payee corresponding to the payment request (S202).

[0091] The output control unit 102f generates an accounts payable balance confirmation statement including discrepancy data (S203) and outputs the generated accounts payable balance confirmation statement (S204).

[0092] As described above, the discrepancy management device 100 issues an accounts payable balance confirmation statement containing discrepancy data at the time of settlement, and the details of these processes will be explained below. The following example will be given when settlement is performed at the time of completion of payment for the January invoice to the above-mentioned payee "SI001: □△ Industries". Figure 23 is a diagram showing an example of payment schedule data according to the embodiment. Figure 24 is a diagram showing an example of discrepancy data according to the embodiment. Figure 25 is a diagram showing an example of a debt balance file according to the embodiment.

[0093] When settlement processing is received for the payee "SI001: □△ Industries" upon completion of payment for the January invoice, the acquisition unit 102a acquires the payment schedule data for the January invoice as shown in Figure 23, the discrepancy data for the January invoice as shown in Figure 24, and the outstanding debt file for the January invoice as shown in Figure 25.

[0094] As shown in Figure 23, the payment schedule data for the January invoice, at the time of payment completion, includes records for each of products A through D. For products A and B, the payment request number is stored because the payment request registration has been completed. On the other hand, for products C and D, the payment request number is not stored because the payment request registration has not been completed.

[0095] As shown in Figure 24, the discrepancy data at the time of payment completion for the January invoice contains the following information: "Resolution Flag: 0: Unresolved", "Discrepancy Amount: -55", "Discrepancy Amount Excluding Tax: -5", and "Discrepancy Base Amount: -50".

[0096] As shown in Figure 25, the debt balance file stores records that combine "payee," "accounting year and month," and "debt balance." As shown in Figure 25, the debt balance in the debt balance file at the time of payment completion for the January invoice is the sum of the planned payment amounts of "55 yen" and "550 yen" for products C and D, for which the payment request registration has not been completed, totaling "605 yen."

[0097] The output control unit 102f refers to the payment schedule data, discrepancy data, and debt balance file acquired by the acquisition unit 102a and outputs an accounts payable balance confirmation statement. Figure 26 is a diagram showing an example of an accounts payable balance confirmation statement according to the embodiment. The accounts payable balance confirmation statement output by the output control unit 102f includes "accounts payable balance," "discrepancy amount," "discrepancy details," etc., as shown in Figure 26. The "discrepancy details" show the company's acceptance details in the upper section and the payee's billing details in the lower section. Each acceptance detail includes the items "date," "voucher number," "product," "quantity," "unit," "unit price," "amount excluding tax," "consumption tax amount," "amount including tax," and "reason for discrepancy."

[0098] For example, the output control unit 102f inputs the outstanding debt of "605 yen" stored in the debt balance file shown in Figure 25 into the "Accounts Payable Balance" field of the accounts payable balance confirmation, and inputs "55" into the discrepancy amount field of the accounts payable balance confirmation based on the discrepancy amount "-55" in the discrepancy data. The output control unit 102f also inputs information into each item of the discrepancy details field of the accounts payable balance confirmation based on the information stored in the payment schedule data and the discrepancy data. Here, since the discrepancy cause in the discrepancy data for the payee "SI001: □△ Industries" at the time of payment completion for the January invoice is the invoice for product C listed on the invoice, the discrepancy details are entered only in the payee invoice details field of the accounts payable balance confirmation shown in Figure 26.

[0099] The output control unit 102f can display the accounts payable balance confirmation shown in Figure 26 on the display device of the output device 500, and can also output it to the payee in response to the operator's input. As shown in Figure 26, by outputting an accounts payable balance confirmation that includes the discrepancy amount and details of the discrepancy, it becomes possible to confirm the current outstanding debt balance with the payee, and it also becomes easier to confirm the cause of the discrepancy.

[0100] The above example describes the issuance of an accounts payable balance confirmation when the discrepancy is due to an invoice for product C listed on the invoice, but the embodiments are not limited to this. For example, an accounts payable balance confirmation can also be issued when a discrepancy occurs due to differences in unit price or quantity between the company and the payee. Figure 27 shows an example of payment schedule data according to the embodiment. Figure 28 shows an example of invoice data according to the embodiment. Figure 29 shows an example of a payment request input screen according to the embodiment.

[0101] The display control unit 102e displays the payment request input screen shown in Figure 29 on the display device of the output device 500 in response to an operation to start inputting a payment request via the input device 400. When the operator enters "SI001" for the payee on the header screen of the payment request input screen shown in Figure 29, the acquisition unit 102a refers to the billing address master and acquires the payment due date "2024 / 1 / 31" for the payee "□△ Industries" corresponding to "SI001", and also acquires the payment due date data shown in Figure 27.

[0102] Here, the acquisition unit 102a determines the payment schedule data (shown in Figure 27) to be forwarded to the payment process from the purchase data by matching the purchase data recorded in the purchase input with the billing data based on the invoice received from the payee. For example, the acquisition unit 102a acquires the billing data shown in Figure 28 based on the payee entered by the operator and matches it with the purchase data. The billing data shown in Figure 28 includes the itemized amount (total amount) of "3 units" of "product A" at "165 yen", the itemized amount (total amount) of "2 units" of "product B" at "110 yen", the itemized amount (total amount) of "1 unit" of "product C" at "77 yen", and the sum of the itemized amounts (total amounts) of the three types of products at "352 yen".

[0103] The acquisition unit 102a determines whether products A to C included in the billing data are included in the purchase data. Here, if products A to C are included in the purchase data, the acquisition unit 102a acquires the payment schedule data shown in Figure 27. Here, let's assume that the payment schedule amount for product C was registered as "55 yen" in the purchase data. In this case, the record for product C in the payment schedule data acquired by the acquisition unit 102a will have the payment schedule number "SH2020000001-03" associated with the purchase date "2023 / 12 / 5", payee "SI001:□△ Industries", payment schedule amount "55 yen", product name "product C", and quantity "1 piece", as shown in Figure 27.

[0104] When the acquisition unit 102a acquires the payment schedule data shown in Figure 27, the display control unit 102e displays the corresponding items of the payment schedule data in each item of the purchase data selection screen, as shown in the purchase data selection screen in Figure 29. The items to be registered as payment requests are determined when the operator checks the payment request checkbox via the input device 400.

[0105] Once the items to be registered in the payment request are determined, the display control unit 102e displays various amounts in the footer screen of the payment request input screen, as shown in Figure 29. For example, since the total of the billing data shown in Figure 28 is "352 yen", the display control unit 102e displays "352 yen" in the amount billed by the other party included in the footer screen, as shown in Figure 29. Also, since the payment request checkboxes for "Product A", "Product B", and "Product C" have been checked on the purchase data selection screen, the display control unit 102e displays "330 yen", which is the sum of the current matching amounts for each product: "165 yen", "110 yen", and "55 yen". Furthermore, the display control unit 102e calculates "(352 + 0) - 330 = 22" and displays "22 yen" in the difference included in the footer screen.

[0106] Here, as shown in Figure 29, a difference of "22 yen" has occurred in this payment request, so the payment request registration unit 102c does not complete the registration of the payment request based on the payment request input shown in Figure 29. Also, since the discrepancy data for the payee "SI001: □△ Industries" is not registered in the storage unit 106, the display control unit 102e displays an additional discrepancy details creation screen for generating discrepancy data on the display device of the output device 500. Figure 30 is a diagram showing an example of the discrepancy details creation screen according to the embodiment.

[0107] The discrepancy details creation screen displays each item according to the input results in the payment schedule data, invoice data, and payment request input screen. For example, in the discrepancy details creation screen shown in Figure 29, each item in "Company Inspection Details" displays information related to "Product C" from the payment schedule data shown in Figure 27, and each item in "Customer Inspection Details" displays information related to "Product C" from the invoice data shown in Figure 28. In addition, based on the values ​​in each item in "Company Inspection Details" and each item in "Customer Inspection Details," "Number of Discrepancies: 1," "Discrepancy Unit Price: 20," "Discrepancy Amount (excluding tax): -20," "Discrepancy Consumption Tax: -2," and "Discrepancy Amount: -22" are displayed.

[0108] As shown in Figure 30, when an error detail is created on the additional error detail creation screen, the update unit 102d generates error data based on the information entered on the error detail creation screen. Figure 31 shows an example of error data according to this embodiment. As shown in Figure 31, the update unit 102d generates discrepancy data for the payment request number "SI200000001" based on the discrepancy detail creation screen shown in Figure 30, associating it with "Line number: 1", "Resolution flag: 0: Unresolved", "Company slip number: SH2020000001-3", "Company product code: SH003", "Company quantity: 1", "Company unit price: 50", "Expected payment amount: 50", "Company consumption tax amount: 5", "Customer product code: SH03", "Customer quantity: 1", "Customer unit price: 70", "Expected payment amount: 70", "Customer consumption tax amount: 7", "Discrepancy unit price: -20", "Discrepancy amount: -22", "Discrepancy amount excluding tax: -2", and "Discrepancy base amount: -20", and stores it in the storage unit 106.

[0109] If the discrepancy data at the time of payment completion for the January invoice is in the state shown in Figure 31, the output control unit 102f refers to the payment schedule data shown in Figure 23, the discrepancy data shown in Figure 31, and the debt balance file shown in Figure 25, and outputs an accounts payable balance confirmation statement. Figure 32 is a diagram showing an example of an accounts payable balance confirmation statement according to this embodiment.

[0110] For example, the output control unit 102f inputs the outstanding debt of "605 yen" stored in the debt balance file shown in Figure 25 into the "Accounts Payable Balance" field of the accounts payable balance confirmation document, and inputs "22" into the discrepancy amount field of the accounts payable balance confirmation document based on the discrepancy amount of "-22" in the discrepancy data shown in Figure 31. In addition, the output control unit 102f inputs information into each item of the discrepancy details of the accounts payable balance confirmation document based on the information stored in the payment schedule data and the discrepancy data. Specifically, the output control unit 102f inputs information into the company's acceptance details in the upper section of the discrepancy details and the payee's invoice details in the lower section of the discrepancy details, respectively, based on the discrepancy data shown in Figure 31.

[0111] According to the embodiments described above, it becomes possible to easily identify discrepancies at the time of settlement and to expedite the settlement process.

[0112] [3. 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 SDGs Goals 8 and 9.

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

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

[0115] [4. Other Embodiments] Although embodiments of the present invention have been described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the embodiments described above.

[0116] For example, among the processes described in the embodiments described above, 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.

[0117] In addition, 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 the above-mentioned documents and drawings may be changed at will unless otherwise specified.

[0118] Furthermore, with respect to the discrepancy management device 100, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0119] For example, the processing functions of each device constituting the discrepancy management device 100, particularly those performed in the control unit, may be implemented in whole or in part by a CPU 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 each device as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) contains a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0120] Furthermore, this computer program may be stored on an application program server connected to the discrepancy management device 100 via any network, and it is possible to download all or part of it as needed.

[0121] Furthermore, the 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-first 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.

[0122] 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 procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0123] The various databases stored in the memory unit are storage means such as RAM, ROM, other memory devices, hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0124] Furthermore, the discrepancy management device 100 may be configured as an information processing device such as a known personal computer or workstation, or as an information processing device to which any peripheral devices are connected. Alternatively, the discrepancy management device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment onto the discrepancy management device 100.

[0125] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing 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]

[0126] This invention is useful for accounting procedures in manufacturing industries such as agricultural machinery manufacturing, heavy machinery manufacturing, and the semiconductor industry. [Explanation of symbols]

[0127] 100 Miscalculation management device 102 Control Unit 102a Acquisition Department 102b Judgment section 102c Payment Request Registration Section 102d Update Department 102e Display Control Unit 102f Output Control Unit 104 Communication Interface Section 106 Storage section 106a Billing Address Master 106b Billing Data 106c Payment Schedule Data 106d Payment Request Data 106e Data of discrepancies 106f Debt Balance File 108 Input / Output Interface Section 200 servers 300 Networks 400 Input Devices 500 Output Device

Claims

1. A discrepancy management device comprising a memory unit and a control unit, The aforementioned storage unit is A discrepancy data storage means for storing discrepancy data regarding discrepancies between the invoiced amount and the scheduled payment amount for each payee. Equipped with, The control unit, Each time a payment request is received, a determination means determines whether or not unresolved discrepancy data is stored in the storage unit at the payee of the payment request. An update means that, if a discrepancy occurs between the invoiced amount and the scheduled payment amount in the payment request, and no unresolved discrepancy data is stored in the storage unit at the payee of the payment request, generates discrepancy data relating to the discrepancy between the invoiced amount and the scheduled payment amount; and, if no unresolved discrepancy data is stored in the storage unit at the payee of the payment request, updates the discrepancy data stored in the storage unit by modifying the unresolved discrepancy data in accordance with the input processing entered by the operator at the time of the payment request. Equipped with, A discrepancy management device characterized by the following features.

2. The aforementioned discrepancy data includes a section that indicates whether or not the discrepancy has been resolved. The update means updates the discrepancy data in response to the input processing from the operator regarding the category included in the discrepancy data. The discrepancy management device according to feature 1.

3. The aforementioned discrepancy data further includes a section that holds the discrepancy amount between the invoiced amount and the scheduled payment amount, The control unit, The system further includes a payment request registration means that completes the registration of the payment request on the condition that there is no difference between the added amount obtained by adding the discrepancy amount included in the discrepancy data to the invoiced amount and the scheduled payment amount, The update means changes the numerical value of the discrepancy amount included in the discrepancy data in response to the input processing from the operator regarding the category that holds whether or not the discrepancy included in the discrepancy data has been resolved. The discrepancy management device according to feature 2.

4. The determination means determines, based on the status of the category included in the discrepancy data of the payee of the payment request, whether or not there is unresolved discrepancy data stored in the storage unit at the payee of the payment request. The discrepancy management device according to feature 2.

5. The determination means determines, each time it receives a payment request, whether or not there is a discrepancy between the invoiced amount and the scheduled payment amount. The control unit, If the aforementioned discrepancy has occurred, or if unresolved discrepancy data is stored in the storage unit at the payee of the payment request, a display control means causes the display unit to display a discrepancy details creation screen for registering the cause of the discrepancy. The discrepancy management device according to claim 1, further comprising the features described above.

6. The aforementioned discrepancy data includes the cause and amount of the discrepancy between the invoiced amount and the scheduled payment amount. The control unit, Output control means for outputting accounts payable balance confirmation statements, including the cause and amount of the discrepancy, for each payee, for each accounting month and year. The discrepancy management device according to any one of claims 1 to 5, further comprising the above.

7. A method for managing discrepancies in an accounting management device comprising a storage unit and a control unit, The aforementioned storage unit stores discrepancy data regarding the difference between the invoiced amount and the scheduled payment amount for each payee. The control unit, Each time a payment request is received, a discrepancy data determination step is performed to determine whether or not unresolved discrepancy data is stored in the storage unit at the payee of the payment request. The process includes: an update step in which, if a discrepancy occurs between the invoiced amount and the scheduled payment amount in the payment request, and no unresolved discrepancy data is stored in the storage unit at the payee of the payment request, discrepancy data relating to the discrepancy between the invoiced amount and the scheduled payment amount is generated; and, if no unresolved discrepancy data is stored in the storage unit at the payee of the payment request, an update step in which the discrepancy data stored in the storage unit is updated by modifying the unresolved discrepancy data in accordance with the input processing entered by the operator at the time of the payment request. A method for managing discrepancies characterized by the following features.

8. A discrepancy management program to be executed by a discrepancy management device comprising a memory unit and a control unit, The aforementioned storage unit stores discrepancy data regarding the difference between the invoiced amount and the scheduled payment amount for each payee. The control unit, Each time a payment request is received, a discrepancy data determination step is performed to determine whether or not unresolved discrepancy data is stored in the storage unit at the payee of the payment request. If a discrepancy occurs between the invoiced amount and the scheduled payment amount in the payment request, and no unresolved discrepancy data is stored in the storage unit at the payee of the payment request, the update step involves generating discrepancy data relating to the discrepancy between the invoiced amount and the scheduled payment amount, and if no unresolved discrepancy data is stored in the storage unit at the payee of the payment request, updating the discrepancy data stored in the storage unit by modifying the unresolved discrepancy data in accordance with the input processing entered by the operator at the time of the payment request. A discrepancy management program to be executed.

Images