Business support device, business support method, and business support program

Abstract

To support a work required when re-accounting sales that have been recorded once with a time lag.SOLUTION: An acquisition unit acquires sales data of a commercial transaction object to which a unique sales number and specified sales information are added, and stores it in a storage unit. A data generation unit generates order acceptance data including the specified sales information of the sales data entered as an order acceptance. A detection unit detects, from the storage unit, sales data including the sales information of the generated order data. A red slip accounting processing unit generates sales data equivalent to a red slip for negatively accounting the sales amount indicated by the detected sales data, and stores it in the storage unit and accounts for it. This makes it possible to support a work required when re-accounting sales that have been recorded once with a time lag.SELECTED DRAWING: Figure 1

Description

Technical Field

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

Background Art

[0002] Patent Document 1 (Japanese Patent No. 6463532) discloses an internal audit support device that can efficiently analyze journal entries, display them in a way that allows easy confirmation of incorrect journal entries, and support internal audits.

[0003] This internal audit support device has a control unit that extracts corresponding information of multiple journal entry data corresponding to multiple audit items based on the input of journal entry data including information on accounting accounts, and performs analysis processing of journal entries for each audit item using the extracted information. The output unit outputs the result of the analysis processing. Then, the control unit generates display data that extracts journal entries requiring attention from the journal entry data based on changes in the attributes and contents of the journal entry data. This enables discovery of input errors in the number of digits and abnormal price transactions, and thus enables support for internal audits.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Here, there are cases where sales that have once been recorded are recorded again with a time lag. In this case, it was necessary to perform the cumbersome operation of detecting the previous sales from the sales data, generating and recording sales data with a negative amount to cancel this, and then recording sales of the same amount again.

[0006] The present invention has been made in view of the above problems, and an object thereof is to provide a business support apparatus, a business support method, and a business support program that enable support for operations required when re-recording sales that have once been recorded with a time lag.

Means for Solving the Problems

[0007] In order to solve the above problems and achieve the object, a business support apparatus according to the present invention includes an acquisition unit that acquires sales data of a commercial transaction target to which a unique sales number and predetermined sales information are added and stores the data in a storage unit, a data generation unit that generates order receiving data including predetermined sales information of the received sales data, a detection unit that detects sales data including the sales information of the generated order receiving data from the storage unit, and a red slip accounting processing unit that generates sales data corresponding to a red slip for subtracting the sales amount indicated by the detected sales data and stores and accounts for the data in the storage unit.

[0008] Also, in order to solve the above problems and achieve the object, a business support method according to the present invention includes an acquisition step in which an acquisition unit acquires sales data of a commercial transaction target to which a unique sales number and predetermined sales information are added and stores the data in a storage unit, a data generation step in which a data generation unit generates order receiving data including predetermined sales information of the received sales data, a detection step in which a detection unit detects sales data including the sales information of the generated order receiving data from the storage unit, and a red slip accounting processing step in which a red slip accounting processing unit generates sales data corresponding to a red slip for subtracting the sales amount indicated by the detected sales data and stores and accounts for the data in the storage unit.

[0009] Also, in order to solve the above-described problems and achieve the object, the business support program according to the present invention causes a computer to function as an acquisition unit that acquires sales data of a business transaction target, to which a unique sales number and predetermined sales information are added, and stores the data in a storage unit; a data generation unit that generates order receiving data including predetermined sales information of the received sales data; a detection unit that detects sales data including the sales information of the generated order receiving data from the storage unit; and a red slip accounting processing unit that generates sales data corresponding to a red slip for subtracting the sales amount indicated by the detected sales data and stores and accounts for the generated sales data in the storage unit.

Effect of the Invention

[0010] The present invention can support operations required when re-accounting sales that have been once accounted for with a time lag.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Embodiments for Carrying Out the Invention

[0012] Hereinafter, a POS (POS: Point Of Sales) system according to an embodiment to which the present invention is applied will be described in detail with reference to the drawings. Note that the present invention is not limited to the following embodiments.

[0013] (Summary) These days, there are cases where sales that have once been recorded are recorded again with a time lag. In such cases, it is necessary to detect the previous sales from the sales data, generate and record sales data with a negative amount to cancel this, and then record sales of the same amount again.

[0014] For example, for customers who come to a store, there are cases where a product that is out of stock at the store is sold on the condition that the product will be delivered to the customer's home at a later date (shipment at a later date). In this case, since the sales of the sold product are input in the POS register device, the sales information of the sold product is linked in a sales management system such as a POS system.

[0015] However, at the time when the product is sold, since the product has not been delivered to the customer, from the perspective of the revenue recognition standard, it is not preferable to record sales at this time. Therefore, it is necessary to cancel the sales and record the sales again when the product is shipped to the customer.

[0016] In such cases, when a shipment request for a product is made from the store that sold the product to the head office of the sales management system at a later date, the sales invoice of the product for which the shipment request was made, which is managed in the sales management system, is searched, and after manually deleting the sales invoice, the order invoice is manually registered. The operator had to perform such troublesome work.

[0017] Also, when manually deleting the sales invoice and registering the order invoice, differences often occur between the amount (actual amount) managed in the sales management system and the amount (amount of the order invoice) that is the result of the deletion manually input. Therefore, the operator has to check for the occurrence of differences in amounts including the order amount.

[0018] Therefore, the business support device according to the embodiment uses the "cash register number", "receipt number", "opening date", and "store number" included in the sales data as the above-described key sales information, and manages sales register data transmitted from the store side, order data generated on the head office side of the sales management system, red slip data (red slip processing management data) for sales cancellation, etc.

[0019] As a result, in the case of the above-described later shipment, it is possible to collate the data linked in the sales management system and the manually input data using a predetermined key (sales information), and automatic collation can be enabled.

[0020] In addition, the business support device according to the embodiment compares the sales data transmitted from the store terminal device with the order data registered at the head office of the sales management system, and automatically generates and records a red slip (red slip processing management data) for canceling the store's sales.

[0021] As a result, it is possible to automatically cancel the sales based on a predetermined key, prevent human errors in the sales cancellation operation, and improve the accuracy of the amount check.

[0022] Note that the timing for linking the sales data from the store in the sales management system and the timing for performing order input corresponding to the sales data on the head office side of the sales management system may be different.

[0023] (System Configuration) As shown in FIG. 1, the POS system according to the embodiment includes one or more POS register devices 49 placed on the store side and one or more store terminal devices 51. Further, this POS system includes one or more business support devices 1 on the head office side that receive and manage sales data, order slip data, etc. transmitted from the store terminal device 51 on the store side. The store terminal device 51 on the store side and the business support device 1 on the head office side are connected via a network such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0024] In addition, a manufacturer terminal device 60 that transports products is connected to the business support device 1. The manufacturer terminal device 60 transports products to customers according to a transport instruction from the business support device 1. Further, the manufacturer terminal device 60 transmits a shipping notice to the business support device 1 after transporting the products. The business support device 1 generates shipping data based on this shipping notice.

[0025] In FIG. 1, assume that a customer visited a store and wanted to purchase a desired product, but since the product was not available at the store, the customer made an appointment for the product to be transported at a later date and paid the price in advance (shipment at a later date). In this case, at the store side, the price of the product is input via the POS register device 49, and the sales data of the product is transmitted from the store terminal device 51 to the business support device 1 via the network.

[0026] Based on the sales data transmitted from the store terminal device 51, the data generation unit (reference numeral 23 in FIG. 4) of the business support device 1 generates sales data including a unique "sales number", "sales date", "customer code", "product code", "quantity sold", "unit price of sales", and "total sales amount" as shown in FIG. 2(a), and stores it in the sales data storage unit 11. Further, as shown in FIG. 2(b), the data generation unit (reference numeral 23 in FIG. 4) of the business support device 1 generates sales register data in which the "register number", "receipt number", "opening date", and "store number" included in the sales data transmitted from the store terminal device 51 are associated with the same "sales number" as the "sales number" shown in FIG. 2(a), and stores this in the sales register data storage unit 12.

[0027] The "register number", "receipt number", "opening date", and "store number", which are sales information of this sales register data, are used as keys for verification. Further, the "opening date" is the date when the POS register device was started. The total sales amount from the opening to the closing is the daily total sales amount.

[0028] In addition, based on the sales data transmitted from the store terminal device 51, the data generation unit (reference numeral 23 in FIG. 4) of the business support device 1 generates POS data including the above-described sales information (store code, opening date, cash register number, and receipt number), product code, number of sales, unit price of sales, and sales amount, as shown in FIG. 3, and stores the POS data in the POS data storage unit 13.

[0029] This POS data storage unit 13 is managed as data indicating the correct sales amount (data serving as a comparison reference) and is compared with the sales amount of the order receiving data manually input by the operator of the business support device 1. Details will be described later.

[0030] (Hardware Configuration of Business Support Device) The business support device 1 provided at the headquarters of the POS system according to such an embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5, as shown in FIG. 4. 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 corresponds. As the input device 6, in addition to a keyboard device, a mouse device, and a microphone device, a monitor device that realizes a pointing device function in cooperation with the mouse device can be used.

[0031] The communication interface unit 4 is connected to a network 50 such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network). The store terminal device 51 of each store is connected to this network 50.

[0032] As the storage unit 2, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used. The storage unit 2 stores a business support program that enables the business on the side of the business support device 1, which is necessary when re-counting the sales that have once been counted with a time lag.

[0033] Further, in this storage unit 2, a sales data storage unit 11, a sales register data storage unit 12, and a POS data storage unit 13, which are storage areas respectively, are provided. As described above, the sales data transmitted from the store terminal device 51 is stored in the sales data storage unit 11, and the sales register data including the key sales information generated based on the sales data is stored in the sales register data storage unit 12. Also, as described above, the POS data indicating the correct sales amount, which is generated based on the sales data and the sales register data, is stored in the POS data storage unit 13.

[0034] Further, in the storage unit 2, an order reception data storage unit 14, an order reception register data storage unit 15, a red transfer process management table 16, and a shipment data storage unit 17, which are storage areas respectively, are provided. Details will be described later.

[0035] (Functional Configuration of Business Support Device) Next, by executing the business support program stored in the storage unit 2, the control unit 3 functions as an acquisition unit 21, a display control unit 22, a data generation unit 23, a detection unit 24, a red transfer accounting process unit 25, a storage control unit 26, and a comparison unit 27, as shown in FIG. 4.

[0036] The acquisition unit 21 acquires the sales data of the business transaction target, to which a unique sales number and predetermined sales information (for example, store code, opening date, register number, receipt number, etc.) are added, transmitted from the store terminal device 51, and stores it in the storage unit (sales data storage unit 11).

[0037] The data generation unit 23 generates order reception data (mainly the order reception register data shown in FIG. 7(b)) including the predetermined sales information of the input order reception sales data.

[0038] The detection unit 24 detects the sales data including the sales information of the generated order reception data from the storage unit (sales data storage unit 11) (see FIG. 8).

[0039] The red entry accounting processing unit 25 generates sales data corresponding to a red slip for negative accounting of the sales amount indicated by the detected sales data, stores it in the storage unit (sales data storage unit 11), and performs accounting (see FIG. 10).

[0040] The storage unit (red slip processing management table 16 in FIG. 9) stores red slip processing management data including the sales information of the sales data that has been negatively accounted for.

[0041] The red entry accounting processing unit 25 excludes the sales data including the sales information stored in the storage unit (red slip processing management table 16 in FIG. 9) from the detection targets, and detects the sales data including the sales information not stored in the storage unit (red slip processing management table 16 in FIG. 9) from the storage unit (sales data storage unit 11).

[0042] The data generation unit 23 generates red slip processing management data including the sales information of the negatively accounted sales data and stores it in the storage unit (red slip processing management table 16 in FIG. 9) (see FIG. 11).

[0043] The detection unit 24 detects the sales data (POS data in FIG. 1) and order receiving data (order receiving data manually input by the operator: see FIG. 14) acquired by the acquisition unit 21 including the designated sales information from the storage unit (POS data storage unit 13, order receiving data storage unit 14 in FIG. 1). The comparison unit 27 compares the sales amount of the detected sales data (the sales amount serving as the comparison reference for the POS data) and the sales amount of the order receiving data (the sales amount manually input by the operator) (see FIG. 15).

[0044] When the data generation unit 23 obtains a comparison result indicating that the sales amount of the sales data (the sales amount serving as the comparison reference for the POS data) and the sales amount of the order receiving data (the sales amount manually input by the operator) are inconsistent from the comparison unit 27, it corrects the sales amount of the order receiving data to the sales amount manually corrected and input by the operator (see FIG. 16).

[0045]

[0046] ​The sales data obtained by the acquisition unit 21 (the sales data transmitted from the store terminal device 51) is sales data in a sales form (post-delivery shipment in FIG. 1) on the premise that the business transaction target (product or service) will be delivered or provided at a later date.

[0047] The data generation unit 23 generates sales data (shipment data) corresponding to the delivery or provision of the business transaction target that has been performed at a later date, and stores it in the storage unit (shipment data storage unit 17) (see FIG. 17).

[0048] (Business support processing operation) The control unit 3 of the business support device 1 functions as the acquisition unit 21 to the comparison unit 27 shown in FIG. 4 based on the business support program stored in the storage unit 2, and executes each process of steps S1 to S5 shown in FIG. 5, thereby assisting the operations required when re-recording the once-recorded sales with a time difference.

[0049] In this example, the control unit 3 realizes each function of the acquisition unit 21 to the comparison unit 27 with a software program based on the business support program. However, all or part of the acquisition unit 21 to the comparison unit 27 may be realized by hardware. In any case, the same effects as those described later can be obtained.

[0050] (Step S1: Order input processing) First, assume that the sale of a product on the premise of post-delivery shipment is performed as described above, and the sales data including the sales number, sales date, customer code, product code, sales quantity, unit sales price, and sales amount transmitted from the store terminal device 51 is acquired by the acquisition unit 21 and stored in the sales data storage unit 11. Also, based on this sales data, assume that the sales register data including the sales number and sales information (store code, opening date, register number, and receipt number) is generated by the data generation unit 23 and stored in the sales register data storage unit 12.

[0051] Also, based on sales data and sales register data, assume that the data generation unit 23 generates POS data including sales information (store code, start date, register number, and receipt number), product code, number of sales, unit price of sales, and sales amount, and stores it in the POS data storage unit 13. And assume that an order slip for products to be shipped later is acquired by the acquisition unit 21 from the store terminal device 51.

[0052] An operator of the business support device 1 at the head office manually registers order data for the sold products based on the acquired order slip data. Specifically, when an operator designates the display of the order input screen, the display control unit 22 displays the order input screen shown in FIG. 6(a) via the output device 7. The operator inputs the order date, customer code, product code, number of sales, unit price of sales, sales amount, etc. to the order input screen based on the acquired order slip. The data generation unit 23 assigns a unique order number such as "JU0001" that is automatically numbered to the order data including the order date, customer code, product code, number of sales, unit price of sales, and sales amount input via the order input screen, and stores it in the order data storage unit 14 as shown in FIG. 7(a).

[0053] Also, when the "register data" button on the order input screen shown in FIG. 6(a) is operated by the operator, the display control unit 22 displays the order register data input screen shown in FIG. 6(b) via the output device 7. The operator inputs the store code of the store that sent the order slip, the start date of the POS register device 49, the register number, and the receipt number of the receipt issued when selling the product to the order register data input screen. When this input is made, the data generation unit 23 generates order register data with the same order number such as "JU0001" as the order number attached to the related order data for the input store code, start date, register number, and receipt number, and stores it in the order register data storage unit 15 as shown in FIG. 7(b).

[0054] (Step S2: Sales cancellation process) Next, the control unit 3 automatically creates a so-called red slip for canceling the sales data generated by selling products without handing the products to the customer.

[0055] Specifically, assuming that the system date is July 30, 2023, as shown in Fig. 8(a), the detection unit 24 detects the order registration data where "(system date - 2 days) ≤ opening date ≤ (system date + 2 days)" from the order registration data storage unit 15. In the case of the example in Fig. 8(a), the order registration data with the opening date of "July 30, 2023" is detected.

[0056] Next, the detection unit 24 refers to the sales registration data storage unit 12 as shown in Fig. 8(b) using the sales information (store code, opening date, register number, and receipt number) of the detected order registration data as a key, and detects the sales registration data including the same sales information as the sales information of the detected order registration data. Then, the detection unit 24 refers to the sales data storage unit 11 as shown in Fig. 8(c) based on the sales number such as "UR0001" attached to the detected sales registration data, and detects the sales data with the sales number of "UR0001".

[0057] Next, as shown in Fig. 10(a), the red slip accounting processing unit 25 generates sales data corresponding to a so-called red slip for subtracting the sales data detected by the detection unit 24, adds a unique sales number such as "UR0003", and stores it in the sales data storage unit 11.

[0058] In addition, the red slip accounting processing unit 25 generates sales registration data with the same sales number of "UR0003" as the sales data corresponding to this red slip (store code, opening date, register number, and receipt number), and stores it in the sales registration data storage unit 12 as shown in Fig. 10(b).

[0059] Here, when the bad debt accounting processing unit 25 generates the sales register data in this way, it generates bad debt processing management data including the invoice number of the order receipt data received from the store terminal device 51 and sales information (store code, opening date, register number, and receipt number), and stores this in the bad debt processing management table 16. FIG. 9 shows the bad debt processing management table 16 in which the bad debt processing management data generated in the past is stored.

[0060] Before referring to the sales register data storage unit 12 based on the sales information (store code, opening date, register number, and receipt number) of the order receipt data, the detection unit 24 refers to the bad debt processing management table 16 based on the sales information of the order receipt data. The fact that the same sales information as the sales information of the order receipt data exists in the bad debt processing management table 16 indicates that the order invoice has been processed for bad debt. In this case, as shown in FIG. 8(b), the detection unit 24 does not perform the operation of detecting the sales register data corresponding to the sales information of the order receipt data from the sales register data storage unit 12. Thereby, it is possible to prevent the inconvenience that the bad debt processing is performed again on the order invoice for which the bad debt processing has been completed.

[0061] On the other hand, when the same sales information as the sales information of the order receipt data does not exist in the bad debt processing management table 16, the bad debt accounting processing unit 25 generates bad debt processing management data corresponding to the bad debt invoice of the sales data generated when receiving the product price from the customer, and stores this in the bad debt processing management table 16 as shown in FIG. 11. Thereby, the bad debt processing management data corresponding to the generated bad debt invoice is sequentially stored in the bad debt processing management table 16.

[0062] In this way, the business support system according to the embodiment can automatically generate and register the bad debt invoices required when re-accounting the once-accounted sales with a time lag. Therefore, it is possible to greatly reduce and support the work of the operator.

[0063] (Step S3: POS amount inquiry process) Next, the operator compares the total amount of sales data and order data with the POS data to check if there is any difference between the two amounts (POS amount inquiry process).

[0064] In this case, the operator causes the display control unit 22 to display the POS amount inquiry screen shown in Fig. 12(a), and inputs a desired start date and store code for extracting data for checking for amount discrepancies. Fig. 12(a) is an example in which "July 30, 2023 to July 31, 2023" is input as the start date, and the store code of "1011" is input.

[0065] The detection unit 24 detects the sales register data corresponding to the start date and store code input via the POS amount inquiry screen from the sales register data storage unit 12. As a result, as shown in Fig. 13(a), the sales register data with the start date of "July 30, 2023" and the store code of "1011" is detected.

[0066] Further, the detection unit 24 refers to the sales data storage unit 11 as shown in Fig. 13(b) based on the sales numbers such as "UR0001" and "UR0003" attached to the detected sales register data. Thereby, the detection unit 24 detects the sales data transmitted from the store terminal device 51 corresponding to the sales number of "UR0001", and also detects the sales data corresponding to the above-mentioned red invoice corresponding to the sales number of "UR0003".

[0067] Also, the detection unit 24 detects the order register data corresponding to the start date and store code input via the POS amount inquiry screen from the order register data storage unit 15 as shown in Fig. 14(a). Then, as shown in Fig. 14(b), the detection unit 24 detects the order data corresponding to the order number such as "JU0001" attached to the detected order register data from the order data storage unit 14. Thereby, the order data generated by the operator's manual input is detected from the order data storage unit 14.

[0068] Note that, as will be described in detail later, as shown in FIG. 14(b), each order-receiving data is added with a sales flag that is updated from "0" information to "1" information when the POS amount inquiry process has also been completed normally and the sales have been recorded. The detection unit 24 performs the above-described detection process on order-receiving data with a sales flag of "0" and for which sales recording has not been completed as a detection target.

[0069] Next, the data generation unit 23 sums (adds) the respective sales amounts of each sales data shown in FIG. 13(b) (the sales data transmitted from the store terminal device 51 and the sales data corresponding to the red invoice), and the sales amount of the order-receiving data manually input by the operator based on the order-receiving invoice shown in FIG. 14(b). Then, as shown in FIG. 15(a), the data generation unit 23 generates total amount data including sales information (store code, opening date, cash register number, and receipt number) and the total amount (sales amount), and stores it in the storage unit 2.

[0070] Also, as shown in FIG. 15(b), the acquisition unit 21 acquires POS data including the same sales information as the sales information (store code, opening date, cash register number, and receipt number) from the POS data storage unit 13, and stores it in the storage unit 2.

[0071] The comparison unit 27 compares the sales amount (recorded amount) manually input by the operator indicated by the total amount data with the reference sales amount (POS amount) stored in the POS data storage unit 13 as POS data based on the sales data transmitted from the store terminal device 51. When a comparison result indicating that the two do not match is obtained, the display control unit 22 displays detailed information including the above-described recorded amount, POS amount, and comparison result (×) on the POS amount inquiry screen as shown in FIG. 12(b). Thereby, the operator can recognize that the recorded amount and the POS amount do not match and that an input error occurred during manual input.

[0072] In this way, when it is recognized that the recorded amount and the POS amount do not match, the operator calls and displays the order data in which an input error has occurred via the display control unit 22. Then, manually, as shown in FIG. 16, the unit price of sales and the sales amount of the order data in which an input error has occurred are corrected. Thereby, the recorded amount and the POS amount can be made to match.

[0073] (Step S4: Shipping Input Process) Next, as shown in FIG. 1, when a customer who has already paid is shipped with goods, shipping notice data is transmitted from the manufacturer terminal device 60 to the business support device 1. The operator of the business support device 1 inputs the shipping date, customer code, product code, quantity shipped, and order number via a shipping input screen (not shown) based on this shipping notice data. The data generation unit 23 generates shipping data with a unique shipping number automatically assigned as shown in FIG. 17 based on this input, and stores this in the shipping data storage unit 17.

[0074] (Step S5: Batch Sales Recording Process) Finally, the data generation unit 23 detects order data corresponding to the sales data for which sales have been recorded as shown in FIG. 18(a) from the order data storage unit 14 based on the order number such as "JU0001" attached to the sales data. Then, as shown in FIG. 18(b), the data generation unit 23 updates the sales flag of the detected order data from "0" information to "1" information. Thereby, the order data can be set as having been recorded for sales.

[0075] (Effects of the Embodiment) As is clear from the above description, the business support device of the embodiment uses the "cash register number", "receipt number", "opening date", and "store number" included in the sales data as key sales information, and manages sales register data transmitted from the store side, order data generated on the head office side of the sales management system, red slip data for sales cancellation (red slip process management data), and the like.

[0076] As a result, when the payment for the purchased goods is completed first and the goods are delivered at a later date (shipment at a later date), the data linked in the sales management system and the manually entered data can be automatically collated using a predetermined key (sales information).

[0077] In addition, the business support device according to the embodiment compares the sales data transmitted from the store terminal device 51 with the order data registered at the headquarters (business support device 1) of the sales management system, and automatically generates and records a red slip (red slip processing management data) for canceling the store's sales.

[0078] As a result, sales can be automatically canceled based on a predetermined key (sales information), preventing human errors in the sales cancellation operation and improving the accuracy of amount checking.

[0079] [Contribution to the Sustainable Development Goals (SDGs) led by the United Nations] Since the present invention can contribute to improving business efficiency and making appropriate business judgments for enterprises, it can contribute to the goals "8" and "9" of the SDGs.

[0080] In addition, since the present invention can contribute to reducing waste loss and promoting paperless and digitalization, it can contribute to the goals "12", "13" and "15" of the SDGs.

[0081] In addition, since the present invention can contribute to strengthening control and governance, it can contribute to the goal "16" of the SDGs.

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

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

[0084] Also, regarding the processing procedures, control procedures, specific names, registered data of each process, information including parameters such as search conditions, screen examples, and database configurations shown in the specification or drawings, they can be arbitrarily changed unless otherwise specified.

[0085] Regarding the business support device 1, each illustrated component is a functional concept and does not necessarily have the physical configuration shown. For example, regarding the processing functions provided by the business support device 1, especially each processing function performed by the control unit 3, all or any part of them may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

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

[0087] Also, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via an arbitrary network, and all or part of it may be downloaded and executed as needed.

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

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

[0090] Also, the "program" is a data processing method described in any language or description method, and may be in the form of source code or binary code, etc.

[0091] Note that the "program" is not necessarily limited to being configured singly, and includes those that are distributedly configured as a plurality of modules or libraries and those that achieve their functions in cooperation with other separate programs typified by an OS.

[0092] In addition, for the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in the business support apparatus 1 of the embodiments, well-known configurations or procedures can be used.

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

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

[0095] Furthermore, the specific forms of distribution and integration of the devices are not limited to those illustrated, and all or part of them can be functionally or physically distributed or integrated in arbitrary units according to various additions or according to the functional load. That is, the above-described embodiments may be selectively implemented by arbitrarily combining the above-described embodiments.

Industrial Applicability

[0096] The present invention is suitable for application to accounting work in various industries such as the distribution and retail industry as an example.

Explanation of Signs

[0097] 1 Business support device 2 Storage unit 3 Control unit 4 Communication interface unit 5 Input / output interface unit 6 Input device 7 Output device 11 Sales data storage unit 12 Sales register data storage unit 13 POS data storage unit 14 Order receipt data storage unit 15 Order receipt register data storage unit 16 Red notice processing management table 17 Shipping data storage unit 21 Acquisition unit 22 Display control unit 23 Data generation unit 24 Detection unit 25 Red transfer accounting processing unit 26 Memory control unit 27 Comparison unit

Claims

1. An acquisition unit that acquires sales data of a business transaction target with a unique sales number and predetermined sales information added thereto and stores the data in a storage unit; A data generation unit that generates order data including the predetermined sales information of the input sales data; A detection unit that detects the sales data including the sales information of the generated order data from the storage unit; A debit entry processing unit that generates sales data corresponding to a debit note for subtracting the sales amount indicated by the detected sales data and stores and records the data in the storage unit; A business support device having the above.

2. The storage unit stores debit entry processing management data including the sales information of the sales data for which negative accounting has been completed; The debit entry processing unit excludes the sales data including the sales information stored in the storage unit from the detection target, and detects the sales data including the sales information not stored in the storage unit from the storage unit; The business support device according to claim 1, characterized in that.

3. The debit entry processing unit generates debit entry processing management data including the sales information of the sales data for which negative accounting has been performed and stores the data in the storage unit; The business support device according to claim 2, characterized in that.

4. The detection unit detects the sales data and the order data acquired by the acquisition unit including the designated sales information from the storage unit, The detection unit further includes a comparison unit that compares the sales amount of the detected sales data and the sales amount of the order data, When the data generation unit obtains a comparison result indicating that the sales amount of the sales data and the sales amount of the order data do not match from the comparison unit, the data generation unit corrects the sales amount of the order data to the sales amount manually corrected by the operator; The business support device according to claim 3, characterized in that.

5. The sales data acquired by the acquisition unit is sales data in a sales form on the premise that the business transaction target will be delivered or provided at a later date; The data generation unit generates sales data corresponding to the delivery or provision of the business transaction target performed at a later date and stores the data in the storage unit; The business support device according to claim 4, characterized in that.

6. An acquisition step in which an acquisition unit acquires sales data of a business transaction target with a unique sales number and predetermined sales information added thereto and stores the data in a storage unit; A data generation step in which a data generation unit generates order data including the predetermined sales information of the received sales data received and inputted; A detection step in which a detection unit detects the sales data including the sales information of the generated order data from the storage unit; A red entry accounting process step in which a red entry accounting process unit generates sales data corresponding to a red entry for negatively accounting the sales amount indicated by the detected sales data, stores the data in the storage unit, and performs the accounting; A business support method having the above.

7. A computer, An acquisition unit that acquires sales data of a business transaction target with a unique sales number and predetermined sales information added thereto and stores the data in a storage unit; A data generation unit that generates order data including the predetermined sales information of the received sales data received and inputted; A detection unit that detects the sales data including the sales information of the generated order data from the storage unit; Functioning as a red entry accounting process unit that generates sales data corresponding to a red entry for negatively accounting the sales amount indicated by the detected sales data, stores the data in the storage unit, and performs the accounting; A business support program characterized by the above.

Images