Accounting system, input device, payment device and program

Abstract

To provide an accounting system that allows a clerk and a customer to divide operations to settle a transaction without generating settlement information in an input apparatus.SOLUTION: An input apparatus corrects data related to a transaction transmitted to each of a plurality of settlement apparatuses with the use of first transmission means before an input end instruction for the data related to the transaction is detected by end detection means. The input apparatus transmits data related to the transaction corrected by input-side correction means to each of the plurality of settlement apparatuses before the input end instruction is detected by the end detection means. The settlement apparatus corrects data related to a transaction stored in a settlement-side storage unit by using the data related to the transaction after the correction transmitted from the input apparatus with the use of second transmission means.SELECTED DRAWING: Figure 35

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a checkout system, an input device and a payment device of the system, and programs for the input device and the payment device. [Background technology]

[0002] In recent years, accounting systems for mass retailers that share operations between store clerks and customers have become popular. This type of accounting system separates an input device that accepts data input for each transaction of the products to be bought and sold, from a payment device that executes the transaction settlement process based on the product data input by the input device. The system is arranged so that the store clerk operates the input device and the customer operates the payment device.

[0003] In a shared payment system, the store clerk inputs product data, which reduces the time required for data input compared to a self-service payment system where the customer performs all operations themselves. However, since the customer operates the payment device, customers who are unfamiliar with the operation may have difficulty making payments. Therefore, in a shared payment system, multiple payment devices are generally assigned to one input device.

[0004] In this type of conventional accounting system, once a store clerk has finished entering all data about the products sold in a transaction with a customer into an input device, payment information is generated on the input device. The payment information includes detailed information about the products sold, such as the product code, product name, unit price, quantity, and amount, as well as total information, such as the total number of items and total amount. The payment information is then sent to an available payment device, and the store clerk guides the customer to that device. The payment device that receives the payment information becomes capable of processing the payment, and the customer operates the payment device to pay with cash, credit card, electronic money, or the like. In this way, a shared-payment accounting system settles the transaction by having the store clerk and the customer share the operations. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-242839 Summary of the Invention [Problem to be solved by the invention]

[0006] The problem that the embodiments of the present invention aim to solve is to provide an accounting system in which a store clerk and a customer can share the operations to settle a transaction without generating payment information on an input device, as well as an input device and a payment device for this system, and programs for each of the input device and the payment device. [Means for solving the problem]

[0007] In one embodiment, the accounting system connects an input device, which inputs transaction data via an input device, to a plurality of settlement devices, which settle transactions, via a communication line. The input device comprises an end detection means, a first transmission means, an input side correction means, a second transmission means, and a first notification means. The end detection means detects an instruction to end input of data related to a transaction. The first transmission means transmits the transaction data input via the input device to each of the multiple payment devices before the end detection means detects the instruction to end input of the data related to the transaction. The input side correction means corrects the transaction data transmitted by the first transmission means to each of the multiple payment devices before the end detection means detects the instruction to end input of the data related to the transaction. The second transmission means transmits the transaction data corrected by the input side correction means to each of the multiple payment devices before the end detection means detects the instruction to end input of the data related to the transaction. The first notification means notifies one of the multiple payment devices of the end of input when the end detection means detects the instruction to end input of the data related to the transaction. The settlement device comprises a settlement side storage means, a settlement side correction means, and a settlement means. The settlement side storage means stores transaction data transmitted from the input device by the first transmission means in the settlement side storage unit until the transaction is settled. The settlement side correction means corrects the transaction data stored in the settlement side storage unit with the corrected transaction data transmitted from the input device by the second transmission means. When the settlement means receives a notification of input completion from the input device when settlement is possible, it settles the transaction based on the transaction data stored in the settlement side storage unit. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram showing the general configuration of a transaction system according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing the hardware configuration of an input device incorporated in the accounting system. [Figure 3] FIG. 3 is a block diagram showing the hardware configuration of a settlement device incorporated in the transaction system. [Figure 4] FIG. 4 is a block diagram showing the main functional configuration of the processor of the input device in the first embodiment. [Figure 5] FIG. 5 is a schematic diagram showing the data structure of a detail record. [Figure 6] FIG. 6 is a schematic diagram showing the configuration of a data table included in the input device in the first embodiment. [Figure 7] FIG. 7 is a block diagram showing the main functional configuration of the processor of the settlement device in the first embodiment. [Figure 8] FIG. 8 is a schematic diagram showing the configuration of a flag memory included in the settlement device. [Figure 9] FIG. 9 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the first embodiment. [Figure 10] FIG. 10 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the first embodiment. [Figure 11] FIG. 11 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the first embodiment. [Figure 12] FIG. 12 is a flowchart showing the main steps of information processing executed by the processor of the payment device according to the payment program in the first embodiment. [Figure 13] FIG. 13 is a flowchart showing the main steps of information processing executed by the processor of the payment device according to the payment program in the first embodiment. [Figure 14] FIG. 14 shows an example of a details screen displayed on the touch panel of the input device. [Figure 15] FIG. 15 shows an example of a payment method selection screen displayed on the touch panel of the input device. [Figure 16] FIG. 16 shows an example of a payment screen displayed on the touch panel of the input device. [Figure 17] FIG. 17 is an example of a standby screen displayed on the touch panel of the settlement device. [Figure 18] FIG. 18 shows an example of a checkout screen displayed on the touch panel of the payment device. [Figure 19] FIG. 19 is a diagram illustrating a first pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 20] FIG. 20 is a diagram illustrating a second pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 21] FIG. 21 is a diagram illustrating a third pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 22] FIG. 22 is a diagram illustrating a fourth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 23] FIG. 23 is a diagram illustrating a fifth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 24]FIG. 24 is a diagram illustrating a sixth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 25] FIG. 25 is a diagram illustrating a seventh pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 26] FIG. 26 is a diagram illustrating an eighth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 27] FIG. 27 is a diagram illustrating a ninth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 28] FIG. 28 is a diagram illustrating a tenth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 29] FIG. 29 is a diagram illustrating an eleventh pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 30] FIG. 30 is a diagram illustrating a twelfth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 31] FIG. 31 is a diagram illustrating a thirteenth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 32] FIG. 32 is a diagram illustrating a fourteenth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 33] FIG. 33 is a diagram illustrating a fifteenth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 34] FIG. 34 is a diagram illustrating a sixteenth pattern of a response signal output from the settlement device in response to an operation on the input device. [Figure 35] FIG. 35 is a block diagram showing the main functional configuration of the processor of the input device in the second embodiment. [Figure 36] FIG. 36 is a block diagram showing the main functional configuration of the processor of the settlement device in the second embodiment. [Figure 37]FIG. 37 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the second embodiment. [Figure 38] FIG. 38 is a flowchart showing the main steps of information processing executed by the processor of the settlement device in accordance with the settlement program in the second embodiment. [Figure 39] FIG. 39 shows an example of a details screen displayed on the touch panel of the input device. [Figure 40] FIG. 40 shows an example of a correction screen displayed on the touch panel of the input device. [Figure 41] FIG. 41 shows an example of a correction screen displayed on the touch panel of the input device. [Figure 42] FIG. 42 shows an example of a details screen displayed on the touch panel of the input device. [Figure 43] FIG. 43 shows an example of a correction screen displayed on the touch panel of the input device. [Figure 44] FIG. 44 shows an example of a details screen displayed on the touch panel of the input device. [Figure 45] FIG. 45 is a block diagram showing the main functional configuration of the processor of the input device in the third embodiment. [Figure 46] FIG. 46 is a block diagram showing the main functional configuration of the processor of the settlement device in the third embodiment. [Figure 47] FIG. 47 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the third embodiment. [Figure 48] FIG. 48 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the third embodiment. [Figure 49] FIG. 49 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the third embodiment. [Figure 50]FIG. 50 is a flowchart showing the main steps of information processing executed by the processor of the settlement device in accordance with the settlement program in the third embodiment. [Figure 51] FIG. 51 is a flowchart showing the main steps of information processing executed by the processor of the settlement device in accordance with the settlement program in the third embodiment. [Figure 52] FIG. 52 is an example of a details screen displayed on the touch panel of the input device. [Figure 53] FIG. 53 shows an example of a payment device selection screen displayed on the touch panel of the input device. [Figure 54] FIG. 54 is an example of the second detail screen displayed on the touch panel of the input device. [Figure 55] FIG. 55 is a block diagram showing the main functional configuration of the processor of the input device in the fourth embodiment. [Figure 56] FIG. 56 is a schematic diagram showing the data structure of a detail record in the fourth embodiment. [Figure 57] FIG. 57 is a block diagram showing the main functional configuration of the processor of the settlement device in the fourth embodiment. [Figure 58] FIG. 58 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the fourth embodiment. [Figure 59] FIG. 59 is a flowchart showing the main steps of information processing executed by the processor of the input device according to the input program in the fourth embodiment. [Figure 60] FIG. 60 is a flowchart showing the main steps of information processing executed by the processor of the settlement device in accordance with the settlement program in the fourth embodiment. [Figure 61] FIG. 61 is a flowchart showing the main steps of information processing executed by the processor of the settlement device in accordance with the settlement program in the fourth embodiment. [Figure 62] FIG. 62 shows an example of a details screen displayed on the touch panel of the input device. [Figure 63]FIG. 63 shows an example of a payment completion screen displayed on the touch panel of the input device. [Figure 64] FIG. 64 shows an example of a receipt output from the settlement device. DETAILED DESCRIPTION OF THE INVENTION

[0009] Below, we will explain embodiments of a checkout system in which a store clerk and a customer share the operations to settle a transaction without generating payment information on an input device, in the order of first, second, third, and fourth embodiments. First, we will explain the schematic configuration of the checkout system, and the hardware configuration of the input device and payment device, which are common to all embodiments, using Figures 1 to 3.

[0010] Figure 1 is a schematic diagram showing the overall configuration of accounting system 1. Accounting system 1 includes an input device 11, a payment device 12, a server 13, and a network 14 connecting these. There are no particular restrictions on the type of network 14, but it is generally a wired or wireless local area network (LAN).

[0011] Input device 11 is a device configured to accept input of data on the products to be bought and sold in each transaction. Payment device 12 is a device configured to process the payment of the transaction based on the product data input by input device 11. In principle, input device 11 is operated by a store clerk 2 who plays a role called a checker. In principle, payment device 12 is operated by a consumer who purchases products at the store, a so-called customer 3. The operator of input device 11 may also be customer 3. In other words, customer 3 may operate both input device 11 and payment device 12. Similarly, the operator of payment device 12 may also be store clerk 2. In other words, store clerk 2 may operate both input device 11 and payment device 12. 1, the input device 11 is attached to a work table 4. The work table 4 has a rectangular top. By arranging multiple work tables 4 so that the longitudinal directions of the tops are approximately parallel, a passage for customers 3, a so-called checkout lane, is formed.

[0012] An input device 11 and a payment device 12 are arranged for each checkout lane in the store. One input device 11 and two or more payment devices 12 are arranged for each checkout lane. Various data signals are exchanged between the input device 11 and the payment device 12 arranged in the same checkout lane via a network 14. The data signals may be exchanged via a server 13 or without the server 13.

[0013] FIG. 1 shows an example in which one input device 11 (11-1) and two payment devices 12 (12-1, 12-2) are arranged in the first checkout lane, and one input device 11 (11-2) and two payment devices 12 (12-3, 12-4) are arranged in the second checkout lane. Although not shown, one input device 11 and two or more payment devices 12 are also arranged in other checkout lanes. The two payment devices 12 (12-1, 12-2) arranged in the first checkout lane can both process payments for transactions processed by the input device 11 (11-1) arranged in the same checkout lane. The two payment devices 12 (12-3, 12-4) arranged in the second checkout lane can both process payments for transactions processed by the input device 11 (11-2) arranged in the same checkout lane.

[0014] At least one payment device 12 arranged in one checkout lane may be capable of processing the payment of a transaction processed by an input device 11 arranged in an adjacent checkout lane. For example, in FIG. 1, payment device 12 (12-2) can process the payment of a transaction processed by not only input device 11 (11-1) but also input device 11 (11-2). Similarly, payment device 12 (12-3) can process the payment of a transaction processed by not only input device 11 (11-2) but also input device 11 (11-1). This allows the number of payment devices 12 capable of processing the payment of a transaction processed by one input device 11 to be increased without adding more payment devices 12.

[0015] Of the multiple payment devices 12 arranged in one checkout lane, one is set as a parent device and the others are set as child devices. For example, in FIG. 1, if payment device 12 (12-1) and payment device 12 (12-3) are set as parent devices, payment device 12 (12-2) and payment device 12 (12-4) are set as child devices. Incidentally, payment device 12 (12-2) of the child device monitors the status of payment device 12 (12-1) of the parent device. If payment device 12 (12-1) goes down due to a communication failure or malfunction, payment device 12 (12-2) has the function of declaring itself to be the parent device. Upon receiving this declaration, input device 11 (11-1) sets payment device 12 (12-2) as the parent device. Similarly, payment device 12 (12-4) of the child device monitors the status of payment device 12 (12-3) of the parent device. When the payment device 12 (12-3) goes down, the payment device 12 (12-4) has a function of declaring itself to be the master device. In response to this declaration, the input device 11 (11-2) sets the payment device 12 (12-4) as the master device. In the following description, when distinguishing between the payment device 12 as a master device and a slave device, the master payment device will be referred to as master device 121, and the slave payment device will be referred to as slave device 122.

[0016] The server 13 includes a product master file 131 and a sales master file 132. The product master file 131 and the sales master file 132 may be stored in a storage device built into the server 13, or may be stored in a storage device externally connected to the server 13.

[0017] The product master file 131 is a data file that stores a product record created for each product sold in a store. The product record is a data record that describes product data such as a product code, product name, unit price, and attributes.

[0018] A product code is a unique code assigned to each product to identify it. Typically, each product is provided with a barcode or two-dimensional code representing the product code. Alternatively, an RFID (Radio Frequency Identification) tag storing the product code may be attached. The input device 11 can input the product code of a product being bought and sold in a transaction by reading the barcode, two-dimensional code, or RFID tag attached to the product with a reading device.

[0019] The product name and unit price are the name of the product identified by the product code and the price per unit. The attributes are, for example, information about the tax on the product. Information about taxes includes tax rates, tax types (tax-exclusive, tax-inclusive, tax-exempt), etc.

[0020] The sales master file 132 is a data file that stores sales records created for each product sold in a store. The sales records are data records that describe sales data such as the number of sales items and sales amount in addition to the product code, product name, and unit price mentioned above. The number of sales items is the total sales quantity of products identified by the corresponding product code. The sales amount is the total sales amount of products identified by the corresponding product code.

[0021] 2 is a block diagram showing the hardware configuration of the input device 11. The input device 11 includes a processor 21, a main memory 22, an auxiliary storage device 23, a clock 24, a communication unit 25, a keyboard 26, a scanner 27, a touch panel 28, a customer display 29, and a system transmission path 30. The system transmission path 30 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 30 connects the processor 21 to each of the other components directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0022] The input device 11 constitutes a computer by connecting a processor 21, a main memory 22, an auxiliary storage device 23, a clock 24, and a communication unit 25 via a system transmission path 30. The input device 11 then connects devices such as a keyboard 26, a scanner 27, a touch panel 28, and a customer display 29 to the computer via the system transmission path 30.

[0023] The processor 21 corresponds to the central part of the computer. The processor 21 controls each part in accordance with an operating system or an application program to realize various functions of the input device 11. The processor 21 is, for example, a CPU (Central Processing Unit).

[0024] The main memory 22 corresponds to the main storage portion of the computer. The main memory 22 includes a nonvolatile memory area and a volatile memory area. The main memory 22 stores an operating system or application programs in the nonvolatile memory area. The main memory 22 may store data required for the processor 21 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is rewritten by the processor 21 as appropriate. The nonvolatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

[0025] The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 23. The auxiliary storage device 23 stores data used by the processor 21 when performing various processes, data created by the processes in the processor 21, etc. The auxiliary storage device 23 may also store the application programs described above.

[0026] The clock 24 keeps track of the date and time. The processor 21 processes the date and time kept by the clock 24 as the current date and time. The communication unit 25 is an interface for data communication between the server 13 and multiple payment devices 12 connected via the network 14. The keyboard 26 is an input device on which various keys are arranged for inputting data related to the products purchased by the customer, i.e., the purchased products. The scanner 27 is an input device for reading and inputting code symbols such as barcodes and two-dimensional codes. The touch panel 28 is a device that combines an input device and a display device. The touch panel 28 displays information to the store clerk who operates the input device 11 and accepts operational inputs by the store clerk. The customer display 29 displays information to the customer 3 whose purchased product data has been input into the input device 11.

[0027] An existing POS terminal, for example, can be used as the input device 11 having such a hardware configuration. Note that the devices connected to the input device 11 are not limited to the keyboard 26, scanner 27, touch panel 28, and customer display 29. Devices necessary for the use of the input device 11 may be added, or some devices may be omitted.

[0028] 3 is a block diagram showing the hardware configuration of the payment device 12. The payment device 12 includes a processor 31, a main memory 32, an auxiliary storage device 33, a clock 34, a communication unit 35, a change dispenser interface 36, a scanner 37, a touch panel 38, a printer 39, a terminal interface 40, and a system transmission path 41. The system transmission path 41 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 41 connects the processor 31 to each of the other components directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0029] The settlement device 12 constitutes a computer by connecting a processor 31, a main memory 32, an auxiliary storage device 33, a clock 34, and a communication unit 35 via a system transmission path 41. The settlement device 12 then connects device interfaces or devices, such as a change machine interface 36, a scanner 37, a touch panel 38, a printer 39, and a terminal interface 40, to the computer via the system transmission path 41.

[0030] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the payment device 12 in accordance with an operating system or an application program. The processor 31 is, for example, a CPU.

[0031] The main memory 32 corresponds to the main storage portion of the computer. The main memory 32 includes a nonvolatile memory area and a volatile memory area. The main memory 32 stores an operating system or application programs in the nonvolatile memory area. The main memory 32 may store data required for the processor 31 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 32 uses the volatile memory area as a work area where data is rewritten by the processor 31 as appropriate. The nonvolatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0032] The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, HDD, or SSD can be the auxiliary storage device 33. The auxiliary storage device 33 stores data used by the processor 31 when performing various processes, data created by the processes in the processor 31, etc. The auxiliary storage device 33 may also store the application programs described above.

[0033] The clock 34 keeps track of the date and time. The processor 31 processes the date and time kept by the clock 34 as the current date and time. The communication unit 35 communicates data with the server 13 or the input device 11 connected via the network 14. The change machine interface 36 constitutes an interface with an automatic change machine (not shown). The change machine interface 36 inputs amount data of coins inserted into the automatic change machine from the automatic change machine. The change machine interface 36 outputs change data from the settlement device 12 to the automatic change machine. The automatic change machine that has input the change data automatically dispenses coins equivalent to the change data as change.

[0034] The scanner 37 is an input device for reading code symbols such as barcodes and two-dimensional codes. The touch panel 38 is a device that combines an input device and a display device. The touch panel 38 displays information to the customer 3, who is the operator of the payment device 12, and accepts operational inputs from the customer 3. The printer 39 issues receipts by printing various characters or images on receipt paper.

[0035] The terminal interface 40 constitutes an interface with the cashless payment terminal 5. The cashless payment terminal 5 is an information terminal that supports cashless payments such as credit card payments, electronic money payments, and code payments. The terminal interface 40 outputs identification data of a cashless payment method selected from multiple cashless payment methods to the cashless payment terminal 5. In the cashless payment terminal 5, the transaction payment is processed using the cashless payment method identified by the identification data, and the terminal interface 40 inputs the processing result from the cashless payment terminal 5.

[0036] Incidentally, by connecting the cashless payment terminal 5 to the terminal interface 40, the payment device 12 becomes a device that supports not only cash payments but also cashless payments. In other words, a payment device 12 that does not have a cashless payment terminal 5 connected to the terminal interface 40 becomes a device that supports only cash payments.

[0037] An existing self-service POS terminal, a so-called self-checkout register, can be used as the payment device 12 having such a hardware configuration. Note that the devices connected to the payment device 12 are not limited to the scanner 37, touch panel 38, and printer 39. Devices required for the purpose of the payment device 12 may be added, or some devices may be omitted.

[0038] [First embodiment] Next, the first embodiment will be described with reference to FIGS. 4 is a block diagram showing the main functional configuration of processor 21 of input device 11. Processor 21 has functions as input-side storage means 51, detail display means 52, completion detection means 53, first transmission means 54, selection means 55, first notification means 56, second notification means 57, third notification means 58, payment destination notification means 59, and input-side deletion means 510. However, the functions of processor 21 are not limited to these.

[0039] The input storage means 51 functions to store transaction-related data input via the input device 61 in the input storage unit 63. The input storage unit 63 is a part of the storage area of ​​the main memory 22 or the auxiliary storage device 23. The transaction-related data includes, for example, the product code, quantity, discount amount, discount rate, etc., of the product sold in a transaction with a customer. When transaction-related data is input via the input device 61, such as the keyboard 26, scanner 27, or touch panel 28, the input storage means 51 creates a detail record Ra for each product sold as a single transaction based on the input data. As shown in FIG. 5, the detail record Ra is a record that describes data items such as the product code, product name, unit price, quantity, discount amount, and amount, associated with a series of record numbers. The amount is calculated by multiplying the unit price by the quantity. In other words, the detail record Ra can be said to be a record that describes transaction-related data such as the product code and quantity. The input storage means 51 stores the detail record Ra in the first transaction file 631 of the input storage unit 63.

[0040] The statement display means 52 is a function that displays transaction statement information on the display device 62 based on transaction-related data input via the input device 61. The display device 62 corresponds to both or either one of the touch panel 28 and the customer display 29. The statement display means 52 displays the screen of the display device 62 as a statement screen SAa (see FIG. 14), and displays on the statement screen SAa, statement information such as the product name, quantity, unit price, discount amount, and price of the statement record Ra stored in the first transaction file 631. A detailed explanation of the statement screen SAa will be given later.

[0041] The end detection means 53 has a function of detecting an instruction to end input of data related to a transaction. The end detection means 53 includes a first means 531 that detects an operation input to a first operator of the input device 61 as an input end instruction, and a second means 532 that detects an operation input to a second operator of the input device 61 as an input end instruction. The first operator and the second operator will be described later.

[0042] The first transmission means 54 has a function of transmitting transaction-related data input via the input device 61 to each of the multiple payment devices 12 via the communication unit 25 before the completion detection means 53 detects an instruction to complete input of the transaction-related data. The multiple payment devices 12 are payment devices 12 at which a customer 3, whose purchase data has been input via the input device 11, can make a payment. Typically, these payment devices 12 are installed in the same checkout lane as the input device 11. They may also include payment devices 12 installed in adjacent checkout lanes. Hereinafter, the multiple payment devices 12 to which transaction-related data is transmitted from the input device 11 are referred to as payment devices 120 in the same group. Each time transaction-related data is input via the input device 61, the first transmission means 54 transmits the input transaction-related data to each of the payment devices 120 in the same group.

[0043] The selection means 55 has a function of accepting a selection input of a payment method required for settling a transaction. The selection means 55 selects a payment method designated by an operation input to the input device 61 from various payment methods such as cash payment, credit card payment, electronic money payment, etc.

[0044] The first notification means 56 has a function of notifying one of the payment devices 120 in the same group of the end of input via the communication unit 25 when an instruction to end input of data related to a transaction is detected by the end detection means 53. The first notification means 56 refers to the data table 64 to determine the destination to notify of the end of input.

[0045] 6, the data table 64 stores a parent machine flag Fa in association with a payment machine ID for individually identifying payment machines 120 in the same group. The parent machine flag Fa is 1-bit data for identifying whether the payment machine 12 identified by the corresponding payment machine ID is a parent machine 121 or a child machine 122. In this embodiment, the parent machine flag Fa indicating the parent machine 121 is set to "1", and the parent machine flag Fa indicating the child machine 122 is set to "0".

[0046] When the first means 531 of the end detection means 53 detects an input end instruction, the first notification means 56 refers to the data table 64 and outputs a signal notifying the end of input to the payment device 12 set in the master device 121, i.e., the payment device 12 identified by the payment device ID whose master device flag Fa is "1". When the second means 532 of the end detection means 53 detects an input end instruction, the first notification means 56 refers to the data table 64 and outputs a signal notifying the end of input to the payment device 12 set in the slave device 122, i.e., the payment device 12 identified by the payment device ID whose master device flag Fa is "0". The first notification means 56 outputs a signal notifying the end of input together with payment method identification data that identifies the payment method selected and input by the selection means 55.

[0047] When the second notification means 57 receives a response signal indicating that payment is impossible from the payment device 12 that has been notified of the end of input by the first notification means 56, the second notification means 57 notifies the other payment devices 12 that have not notified the end of input of the end of input via the communication unit 25. For example, if the payment device 12 that has notified the end of input is the master device 121 and the second notification means 57 receives a response indicating that payment is impossible from the master device 121, the second notification means 57 refers to the data table 64 and outputs a signal indicating that input is complete to the payment device 12 set in the slave device 122, i.e., the payment device 12 identified by the payment device ID whose master device flag Fa is "0". For example, if the payment device 12 that has notified the end of input is the slave device 122 and the second notification means 57 receives a response indicating that payment is impossible from the slave device 122, the second notification means 57 refers to the data table 64 and outputs a signal indicating that input is complete to the payment device 12 set in the master device 121, i.e., the payment device 12 identified by the payment device ID whose master device flag Fa is "1".

[0048] The third notification means 58 has a function of notifying the other payment devices 12 that have not notified the end of input of the completion of payment via the communication unit 25, upon receiving a response that payment is possible from the payment device 12 that notified the end of input by the first notification means 56. For example, if the payment device 12 that notified the end of input is the master device 121 and the third notification means 58 receives a response that payment is possible from this master device 121, the third notification means 58 refers to the data table 64 and outputs a signal notifying the completion of payment to the payment device 12 set in the slave device 122, i.e., the payment device 12 identified by the payment device ID whose master device flag Fa is "0". For example, if the payment device 12 that notified the end of input is the slave device 122 and the third notification means 58 receives a response that payment is possible from this slave device 122, the third notification means 58 refers to the data table 64 and outputs a signal notifying the completion of payment to the payment device 12 set in the master device 121, i.e., the payment device 12 identified by the payment device ID whose master device flag Fa is "1".

[0049] The payment destination notifying means 59 has a function of notifying the payment device 12 as the payment destination when it receives a response that payment is possible from the payment device 12 that has been notified of the end of input by the first notifying means 56. For example, when it receives a response that payment is possible from the payment device 12 set in the master device 121, the payment destination notifying means 59 notifies the master device 121 as the payment destination. For example, when it receives a response that payment is possible from the payment device 12 set in the slave device 122, the payment destination notifying means 59 notifies the slave device 122 as the payment destination. The payment destination notifying means 59 notifies the store clerk 2 of the payment destination by displaying information that can identify the payment device 12 of the transmission destination on the touch panel 28, which is the display device 62 for the store clerk 2. The payment destination notifying means 59 may also notify the customer 3 of the payment destination by displaying information that can identify the payment device 12 of the transmission destination on the customer display 29, which is the display device 62 for the customer 3. Alternatively, the payment destination notification means 59 may notify both the store clerk 2 and the customer 3 of the payment destination by displaying information that can identify the payment device 12 of the transmission destination on both the touch panel 28 and the customer display 29.

[0050] The input-side deletion means 510 has a function of deleting data related to a transaction stored in the input-side memory unit 63 upon receiving a response signal indicating that payment is possible from the payment device 12 that has notified the end of input by the first notification means 56. Upon receiving a response indicating that payment is possible from the payment device 12, the input-side deletion means 510 deletes all detail records Ra stored in the first transaction file 631 of the input-side memory unit 63. In other words, it clears the first transaction file 631. By clearing the first transaction file 631, the input device 11 becomes able to input data related to the next transaction with the customer.

[0051] The functions of the above-mentioned input side storage means 51, detail display means 52, completion detection means 53, first transmission means 54, selection means 55, first notification means 56, second notification means 57, third notification means 58, payment destination notification means 59 and input side deletion means 510 are realized by information processing executed by the processor 21 in accordance with a program for the input device 11, a so-called input program.

[0052] The input program is a type of application program stored in the main memory 22 or the auxiliary storage device 23. There are no particular limitations on the method for installing the input program in the main memory 22 or the auxiliary storage device 23. The input program can be recorded on a removable recording medium, or the input program can be distributed by communication via the network 14 and installed in the main memory 22 or the auxiliary storage device 23. The recording medium can be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device.

[0053] 7 is a block diagram showing the main functional configuration of the processor 31 of the payment device 12. The processor 31 has functions as a payment side storage means 71, an amount display means 72, a payment response means 73, a payment means 74, and a payment side deletion means 75. However, the functions of the processor 31 are not limited to these.

[0054] The settlement side storage means 71 has a function of storing transaction-related data transmitted from the input device 11 and received via the communication unit 35 in the settlement side storage unit 81 until the transaction is settled. The settlement side storage unit 81 is part of the storage area of ​​the main memory 32 or the auxiliary storage device 33. Based on the received transaction-related data, the settlement side storage means 71 creates a detail record Ra for each product sold as one transaction. As shown in FIG. 5, the detail record Ra is a record that describes data on items such as product code, product name, unit price, quantity, discount amount, and amount, associated with a series of record numbers. In other words, the detail record Ra can be said to be a record that describes transaction-related data such as product code and quantity. The settlement side storage means 71 stores the detail record Ra in the second transaction file 811 of the settlement side storage unit 81.

[0055] The amount display means 72 has a function of displaying the payment amount of a transaction on the touch panel 38 when it receives a notification of input completion from the input device 11 when the transaction can be settled. The payment amount of the transaction is calculated from the amount of the detail record Ra stored in the second transaction file 811 and the discount amount.

[0056] The payment response means 73 has a function of responding to the input device 11 whether or not the settlement of the transaction is possible when it receives a notification of input completion from the input device 11. The payment response means 73 determines whether or not the settlement of the transaction is possible by referring to the flag memory 82. If the payment response means 73 determines that the settlement of the transaction is possible, it transmits a positive response (OK) signal to the input device 11 via the communication unit 35. If the payment response means 73 determines that the settlement of the transaction is not possible, it transmits a negative response (NG) signal to the input device 11 via the communication unit 35.

[0057] The flag memory 82 stores a connection flag Fb and a status flag Fc as shown in Fig. 8. The connection flag Fb is one-bit data for identifying whether or not a cashless payment terminal 5 is connected to the terminal interface 40. In this embodiment, the connection flag Fb is set to "1" when the cashless payment terminal 5 is connected, and the connection flag Fb is set to "0" when the cashless payment terminal 5 is not connected.

[0058] The status flag Fc is one-bit data for identifying whether the payment device 12 is on standby or in the middle of a settlement. When a standby payment device 12 outputs a signal from the input device 11 notifying the end of input, the payment device 12 enters a settlement state. When a transaction is being settled, the payment device 12 is in a state where it is unable to settle the next transaction. When the settlement process is completed in a settlement device 12 in the middle of a settlement, the payment device 12 enters a standby state. When the payment device 12 is on standby, the payment device 12 is in a state where it is able to settle the next transaction. In other words, a standby payment device 12 can be said to be a payment device in a state where it is able to settle a transaction. A settlement device 12 in the middle of a settlement can be said to be a payment device in a state where it is unable to settle a transaction. In this embodiment, the status flag Fc when on standby is set to "0", and the status flag Fc when it is in the middle of a settlement is set to "1".

[0059] When the payment response means 73 receives a signal notifying the end of input from the input device 11, it checks the status flag Fc. If the status flag Fc is "1," i.e., the payment is in progress, the payment response means 73 responds that the transaction cannot be settled by sending a negative response (NG) signal to the input device 11. If the status flag Fc is "0," i.e., the payment response means 73 is in a standby state, the payment response means 73 checks the connection flag Fb. If the connection flag Fb is "1," i.e., a cashless payment terminal 5 is connected to the payment device 12, the payment response means 73 responds that the transaction can be settled by sending a positive response (OK) signal to the input device 11. If the connection flag Fb is "0," i.e., a cashless payment terminal 5 is not connected to the payment device 12, the payment response means 73 checks the payment method identified by the payment method identification data included in the signal notifying the end of input. If the payment method is cash payment, the payment response means 73 responds that the transaction can be settled by transmitting an affirmative response (OK) signal to the input device 11. If the payment method is cashless payment such as credit card payment or electronic money payment, the payment response means 73 responds that the transaction cannot be settled by transmitting a negative response (NG) signal to the input device 11. When the payment response means 73 responds to the input device 11 that the transaction can be settled, the amount display means 72 displays the payment amount of the transaction on the touch panel 38.

[0060] The settlement means 74 has a function of settling a transaction based on the data related to the transaction stored in the settlement side memory unit 81 when it receives a signal from the input device 11 notifying that input has been completed while the transaction is ready for settlement. When the settlement means 74 receives a signal from the input device 11 notifying that input has been completed while the transaction is ready for settlement, it copies the data stored in the second transaction file 811 to the third transaction file 812 and clears the second transaction file 811. The settlement means 74 then settles the transaction based on the data stored in the third transaction file 812. By clearing the second transaction file 811, the settlement device 12 becomes able to accept data related to the transaction with the next customer.

[0061] The payment means 74 settles the transaction using the payment method identified by the payment method identification data received along with the signal notifying the end of input. For example, if the payment method identified by the payment method identification data is cash payment, the payment means 74 executes payment processing for the cash transaction via an automatic change dispenser connected to the change dispenser interface 36. If the payment method identified by the payment method identification data is credit card payment, the payment means 74 executes payment processing for the credit card transaction via the cashless payment terminal 5 connected to the terminal interface 40. If the payment method identified by the payment method identification data is electronic money payment, the payment means 74 executes payment processing for the electronic money transaction via the cashless payment terminal 5 connected to the terminal interface 40. Note that payment processing for transactions using cash, credit card, and electronic money is all well-known processing, so detailed explanation will be omitted.

[0062] The settlement-side deletion means 75 has a function of deleting data related to a transaction stored in the settlement-side memory unit 81 upon receiving a notification of the completion of a settlement from the input device 11. Receiving a notification of the completion of a settlement means that a signal notifying the completion of input has been output to other settlement devices 12 in the same group, and the input device 11 has received a signal from that settlement device 12 acknowledging that the settlement is possible. Therefore, the data related to the transaction stored in the settlement-side memory unit 81 becomes useless. Upon receiving a signal notifying the completion of a settlement from the input device 11, the settlement-side deletion means 75 deletes all detail records Ra stored in the second transaction file 811 of the settlement-side memory unit 81. In other words, it clears the second transaction file 811. As described above, clearing the second transaction file 811 enables the settlement device 12 to accept data related to the transaction with the next customer.

[0063] The functions of the above-mentioned payment side memory means 71, amount display means 72, payment response means 73, payment means 74 and payment side deletion means 75 are realized by information processing executed by the processor 21 in accordance with a program for the payment device, a so-called payment program.

[0064] The payment program is a type of application program stored in the main memory 32 or the auxiliary storage device 33. There are no particular limitations on the method for installing the payment program in the main memory 32 or the auxiliary storage device 33. The payment program can be recorded on a removable recording medium, or can be distributed by communication via the network 14 and installed in the main memory 32 or the auxiliary storage device 33. The recording medium can be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device.

[0065] Next, the content and procedures of the main information processing executed by the input device 11 and the settlement device 12 that constitute the accounting system 1 will be explained using the flowcharts in Figures 9 to 13 and the screen examples in Figures 14 to 18. Note that the content and procedures of the information processing explained below are examples. The content and procedures can be changed as appropriate as long as similar effects can be achieved. The screen examples are also examples. The content of the output text, the arrangement of images, the type and layout of software keys, etc. can be changed as appropriate.

[0066] First, the main steps of the information processing executed by the processor 21 of the input device 11 in accordance with the input program will be described with reference to the flowcharts of FIGS.

[0067] A customer 3 places the items they wish to purchase from the products displayed in the sales area into a shopping basket or the like and heads to the checkout lane. When the customer 3 arrives at the checkout lane, the store clerk 2, who acts as a checker, performs an operation to declare the start of input on the input device 11. In response to this operation, the processor 21 starts information processing according to the procedures shown in the flowcharts of Figures 9 to 11.

[0068] First, in ACT101, the processor 21 displays the screen of the touch panel 28 as the details screen SAa (see FIG. 14). Figure 14 is an example of the display of the details screen SAa. The details screen SAa is divided into a current area AAa, a details area AAb, and a total area AAc. The current area AAa displays the product name, quantity, and price of the most recent product entered as a purchased item in one transaction. The details area AAb displays the product name, quantity, unit price, discount amount, and price of the products entered as purchased items in one transaction in list format, in order of the series of record numbers. The total area AAc displays the total quantity and total price of the purchased items.

[0069] The detail screen SAa also includes software keys for a subtotal button BAa, a discount button BAb, and a discount button BAc. The subtotal button BAa is an operator for indicating that the input of purchased items in one transaction has been completed. The discount button BAb is an operator for indicating a discount on the most recent item input as a purchased item in one transaction. The discount button BAc is an operator for indicating a discount on the most recent item input as a purchased item in one transaction. Incidentally, the price of an item is discounted when the operator inputs the discount button BAb and a discount amount using the numeric keys on the keyboard 26. Similarly, the price of an item is discounted when the operator inputs the discount button BAc and a discount rate using the numeric keys on the keyboard 26.

[0070] In ACT101, the processor 21 sets the screen of the customer display 29 to a customer detail screen. The customer detail screen is the detail screen SAa from which the software key is removed.

[0071] After confirming that the details screen SAa is displayed on the touch panel 28, the store clerk 2 operates the scanner 27 to read the barcode attached to the product that the customer 3 is purchasing. By reading the barcode with the scanner 27, the product code of the purchased product is entered into the input device 11. However, some products, such as fresh food, may not have a barcode attached. If the product does not have a barcode attached, the store clerk 2 causes the touch panel 28 to display a list of products without barcodes. The store clerk then selects the product that the customer is purchasing from that list. Through this operation, the product code of the purchased product without a barcode is entered into the input device 11.

[0072] Returning to the explanation of Figure 9. After displaying the statement screen SAa, the processor 21 waits for the product code to be input in ACT 102. When the product code is input, the processor 21 proceeds from ACT 102 to ACT 103. In ACT 103, the processor 21 transmits an input event to the payment devices 120 in the same group by multicast communication. The input event includes the product code input from the scanner 27 or the touch panel 28.

[0073] The processor 21 also creates a detail record Ra as ACT104. That is, the processor 21 accesses the server 13 and acquires a product record including the input product code from the product master file 131. Then, based on the product information such as the product name and unit price described in the product record, the processor 21 creates a detail record Ra consisting of item data such as a record number r, product code, product name, unit price, quantity, discount amount, and amount. The quantity is "1". The discount amount is "0". The amount is the unit price.

[0074] In ACT105, the processor 21 stores the detail record Ra in the first transaction file 631. In ACT106, the processor 21 updates the detail screen SAa. That is, the processor 21 displays the product name, quantity, and price of the detail record Ra in the current area AAa of the detail screen SAa. At this time, if data related to the detail record Ra with the record number (r-1) one before the record number r of the detail record Ra is displayed in the current area AAa, the processor 21 displays the record number (r-1), product name, quantity, unit price, discount amount, and price of the detail record Ra in the detail area AAb. The processor 21 also displays the total quantity and total price of all the detail records Ra stored in the first transaction file 631 in the total area AAc. The processor 21 also updates the customer detail screen in the same way.

[0075] After updating the detail screen SAa, the processor 21 proceeds to ACT107. The processor 21 checks whether a product code has been entered in ACT107. If a product code has not been entered, the processor 21 proceeds from ACT107 to ACT108. The processor 21 checks whether quantity or discount data has been entered in ACT108. If quantity or discount data has not been entered, the processor 21 proceeds from ACT108 to ACT109. The processor 21 checks whether the subtotal button BAa has been entered in ACT109. If the subtotal button BAa has not been entered, the processor 21 returns from ACT109 to ACT107. After updating the detail screen SAa in this way, the processor 21 enters a standby state for the product code, quantity or discount data, and the subtotal button BAa in ACT107 to ACT109.

[0076] When a product code is input in the standby state of ACT107 to ACT109, the processor 21 returns from ACT107 to ACT103. Then, the processor 21 executes the processing of ACT103 to ACT106 in the same manner as described above. That is, the processor 21 transmits an input event to the payment devices 120 in the same group by multicast communication. The processor 21 creates a detail record Ra and stores the detail record Ra in the first transaction file 631. The processor 21 updates the detail screen SAa based on the data of the detail record Ra stored in the first transaction file 631. Thereafter, the processor 21 enters the standby state of ACT107 to ACT109.

[0077] In the standby state of ACT107 to ACT109, if a quantity is input using the numeric keypad and multiplication key on the keyboard 26, or if a discount amount or discount rate is input using the discount button BAb or discount button BAc and the numeric keypad, the processor 21 proceeds from ACT108 to ACT110. In ACT110, the processor 21 transmits an input event to the payment devices 120 in the same group by multicast communication. The input event includes the quantity, discount amount, or discount rate input from the keyboard 26.

[0078] In ACT111, the processor 21 updates the detail record Ra of the record number r stored in the first transaction file 631. Specifically, if a quantity is input, the processor 21 sets the quantity in the detail record Ra to the input value, and sets the amount to the product of the unit price and the quantity. If a discount amount is input, the processor 21 enters the discount amount in the detail record Ra and subtracts the discount amount from the amount. If a discount rate is input, the processor 21 calculates and enters the discount amount from the unit price and discount rate in the detail record Ra, and subtracts the discount amount from the amount. Then, in ACT112, the processor 21 updates the display in the current area AAa and the total area AAc of the detail screen SAa with the data in the first transaction file 631 after updating the detail record Ra. The processor 21 also updates the customer detail screen in the same way. After that, the processor 21 returns to the standby state of ACT107 to ACT109.

[0079] If the subtotal button BAa is pressed during the standby state of ACT107 to ACT109, the processor 21 proceeds from ACT109 to ACT121 in Fig. 10. In ACT121, the processor 21 displays the payment method selection screen SAb (see Fig. 15) on the screen of the touch panel 28. At this time, the customer display 29 remains on the customer registration screen.

[0080] Figure 15 is an example of the display of the payment method selection screen SAb. The payment method selection screen SAb includes a total area AAd in which the total points and total amount are displayed. The payment method selection screen SAb also includes software keys for a cash button BAd, a credit button BAe, an electronic money button BAf, and a back button BAg. The cash button BAd is an operator for selecting cash payment. The credit button BAe is an operator for selecting credit card payment. The electronic money button BAf is an operator for selecting electronic money payment. The back button BAg is an operator for instructing the user to return to the statement screen SAa.

[0081] If the customer 3 wishes to pay in cash, the clerk 2 presses the cash button BAd. If the customer 3 wishes to pay by credit card, the clerk 2 presses the credit button BAe. If the customer 3 wishes to pay by electronic money, the clerk 2 presses the electronic money button BAf. In this embodiment, the payment methods are limited to three types: cash payment, credit card payment, and electronic money payment, but it goes without saying that the payment methods are not limited to these three types. For example, cashless payment methods such as code payment may also be included.

[0082] After displaying the payment method selection screen SAb, the processor 21 waits for one of the payment methods to be selected in ACT 122. Although not shown, if the back button BAg is pressed while in the standby state of ACT 122, the processor 21 returns the screen of the touch panel 28 to the previous detail screen SAa. The processor 21 then waits for ACT 107 to ACT 109.

[0083] In the standby state of ACT122, when one of the payment methods is selected by inputting the cash button BAd, the credit button BAe, or the electronic money button BAf, the processor 21 proceeds to ACT123. The processor 21 acquires the payment type in ACT123. The payment type is payment method identification data that identifies the payment method for which selection input has been accepted. For example, when the cash button BAd is input, the processor 21 acquires the payment type "cash" as the payment method identification data. When the credit button BAe is input, the processor 21 acquires the payment type "credit" as the payment method identification data. When the electronic money button BAf is input, the processor 21 acquires the payment type "electronic money" as the payment method identification data. After acquiring the payment type, the processor 21 sets the screen of the touch panel 28 to the payment screen SAc (see FIG. 16) in ACT124.

[0084] Figure 16 is an example of the display of the payment screen SAc. The payment screen SAc includes a total area AAe that displays the total points and total amount. The payment screen SAc also includes software keys for a subtotal discount button BAh, a subtotal discount button BAi, an input completion button BAj, a busy button BAk, and a return to details button BAm. The subtotal discount button BAh is an operator for instructing a discount on the total amount. The subtotal discount button BAi is an operator for instructing a discount on the total amount. Incidentally, the total amount is discounted by pressing the subtotal discount button BAh and entering the discount amount using the numeric keys on the keyboard 26. Similarly, the total amount is discounted by pressing the subtotal discount button BAi and entering the discount rate using the numeric keys on the keyboard 26.

[0085] The input complete button BAj and the busy button BAk are both operators for instructing the completion of input of data related to a transaction. When instructing the parent device 121 of the payment devices 120 in the same group to complete input, the store clerk 2 presses the input complete button BAj alone. When instructing the child device 122 to complete input, the store clerk 2 presses the busy button BAk and then the input complete button BAj. Here, the input complete button BAj functions as a first operator. The busy button BAk functions as a second operator.

[0086] In ACT124, the processor 21 sets the screen of the customer display 29 as a customer payment screen. The customer payment screen is the payment screen SAc without the software key.

[0087] After confirming that the payment screen SAc is displayed on the touch panel 28, the store clerk 2 checks whether the base unit 121 is available. If the base unit 121 is available, the store clerk 2 presses the input completion button BAj. For example, if the previous customer is in the middle of making a payment at the base unit 121, or if a customer appears to have completed payment but is lingering next to the base unit 121 to put the change in their wallet, the store clerk 2 presses the busy button BAk and then the input completion button BAj.

[0088] Returning to the explanation of Figure 10. After displaying the payment screen SAc, the processor 21 proceeds to ACT125. In ACT125, the processor 21 resets the busy flag Fd to "0". Then, in ACT126, the processor 21 checks whether the busy button BAk has been pressed. If the busy button BAk has not been pressed, the processor 21 proceeds from ACT126 to ACT127. In ACT127, the processor 21 checks whether the input complete button BAj has been pressed. If the input complete button BAj has not been pressed, the processor 21 returns from ACT127 to ACT126. In this way, the processor 21 waits for the busy button BAk or the input complete button BAj to be pressed in ACT126 and ACT127.

[0089] If the busy button BAk is pressed during the standby state of ACT126 and ACT127, the processor 21 proceeds from ACT126 to ACT128. The processor 21 sets the busy flag Fd to "1" in ACT128. After that, the processor 21 proceeds to ACT127. The processor 21 waits for the input complete button BAj to be pressed.

[0090] When the input completion button BAj is pressed in the standby state of ACT126 and ACT127, the processor 21 proceeds from ACT127 to ACT129. The processor 21 issues a transaction number in ACT129. For example, the input device 11 is equipped with a counter for counting transaction numbers. The processor 21 counts up this counter and issues a new transaction number.

[0091] After issuing the transaction number, the processor 21 proceeds to ACT130. In ACT130, the processor 21 initializes the addition counter n to "0". Next, in ACT131, the processor 21 checks the busy flag Fd. If the busy flag Fd is "0", that is, if the input completion button BAj is pressed alone, the processor 21 proceeds from ACT131 to ACT132. In ACT132, the processor 21 determines that the master device 121 is the destination to which the completion event is to be sent.

[0092] On the other hand, if the busy flag Fd is "1", that is, if the busy button BAk is pressed and then the input complete button BAj is pressed, the processor 21 proceeds from ACT 131 to ACT 133. In ACT 133, the processor 21 counts up the addition counter n by "1". Furthermore, in ACT 134, the processor 21 determines the destination of the completion event to be the child device 122.

[0093] In this way, when the destination of the completion event is determined to be the parent device 121 in ACT 132, or when the destination of the completion event is determined to be the child device 122 in ACT 134, the processor 21 proceeds to ACT 141 in Fig. 11. The processor 21 counts up the count-up counter n by "1" in ACT 141. Therefore, when the destination of the completion event is determined to be the parent device 121, the count-up counter n becomes "1". When the destination of the completion event is determined to be the child device 122, the count-up counter n becomes "2".

[0094] After counting up the addition counter n, the processor 21 proceeds to ACT142. In ACT142, the processor 21 transmits a completion event by unicast communication to the payment device 12 determined as the destination among the payment devices 120 in the same group. That is, if the destination is determined to be the parent device 121 in ACT132, the processor 21 transmits the completion event to the payment device 12 identified by the payment device ID whose parent device flag Fa is set to "1". If the destination is determined to be the child device 122 in ACT134, the processor 21 transmits the completion event to the payment device 12 identified by the payment device ID whose parent device flag Fa is set to "0". The completion event includes the payment type acquired in ACT123 and the transaction number issued in ACT129.

[0095] After transmitting the completion event, the processor 21 proceeds to ACT143. In ACT143, the processor 21 waits for a response signal from the payment device 12. When a payment device 12 that can settle the transaction receives the completion event, a positive response (OK) signal is transmitted from the payment device 12. When a payment device 12 that cannot settle the transaction receives the completion event, a negative response (NG) signal is transmitted from the payment device 12.

[0096] When the processor 21 receives the response signal, the processor 21 proceeds from ACT143 to ACT144. In ACT144, the processor 21 determines whether the response signal is an affirmative response (OK) signal or a negative response (NG) signal. When the processor 21 receives a negative response (NG) signal, the processor 21 proceeds from ACT144 to ACT145. In ACT145, the processor 21 checks whether the count of the counting counter n has exceeded the number N of payment devices 12 in the same group. If the count of the counting counter n is "1", that is, if a completion event has been sent to the parent device 121 but a negative response (NG) signal has been returned from the parent device 121, the processor 21 proceeds from ACT145 to ACT146. In ACT146, the processor 21 determines that the destination of the completion event is the child device 122. Then, the processor 21 returns to ACT141 and executes the processes from ACT141 onwards in the same manner as described above. That is, the processor 21 further counts up the counting counter n by "1". The processor 21 also transmits a completion event to the child device 122, that is, the payment device 12 identified by the payment device ID whose parent device flag Fa is set to "0", and waits for a response signal.

[0097] On the other hand, if the count of the counting counter n is "2" in ACT 145, that is, if a completion event has been sent to the slave device 122 but a negative acknowledgement (NG) signal has been returned from the slave device 122, the processor 21 proceeds from ACT 145 to ACT 147. In ACT 147, the processor 21 displays a screen on the touch panel 28 to notify the user of a transmission error in the completion event. A resend button is displayed on this screen, so the store clerk who has confirmed the transmission error presses the resend button.

[0098] After notifying the transmission error, the processor 21 proceeds from ACT147 to ACT148. The processor 21 waits for a command to resend in ACT148. When the resend button is pressed, the processor 21 returns from ACT148 to ACT130 in Fig. 10 and executes the processes from ACT130 onwards in the same manner as described above. Therefore, in this case, the count value of the count counter n becomes "0" in ACT130, and a completion event is sent to the parent device 121.

[0099] If an affirmative response (OK) signal is received in ACT144, the processor 21 proceeds from ACT144 to ACT149. In ACT149, the processor 21 notifies the payment device 12 that is the destination of the completion event. For example, the processor 21 displays information indicating the payment device 12 that is the destination on the touch panel 28. Upon checking this display, the store clerk 2 instructs the customer 3 to make payment using the payment device 12 that is the destination. The processor 21 may also display information indicating the payment device 12 that is the destination in part of the customer payment screen displayed on the customer display 29. By doing so, the customer 3 can know which payment device 12 is available to make payment.

[0100] After notifying the destination payment device 12, the processor 21 proceeds to ACT150. In ACT150, the processor 21 transmits the deletion event by unicast communication to the payment devices 12 other than the destination payment device 12 among the payment devices 120 in the same group. That is, if the destination payment device 12 is the parent device 121, the processor 21 transmits the deletion event to the child device 122, i.e., the payment device 12 identified by the payment device ID whose parent device flag Fa is set to "0". If the destination payment device 12 is the child device 122, the processor 21 transmits the deletion event to the parent device 121, i.e., the payment device 12 identified by the payment device ID whose parent device flag Fa is set to "1".

[0101] After sending the deletion event, the processor 21 proceeds to ACT151. In ACT151, the processor 21 clears the first transaction file 631. This clearing deletes all of the detail records Ra stored in the first transaction file 631. With this, the processor 21 ends the information processing in accordance with the input program.

[0102] Here, the processor 21 realizes the function of the input side storage means 51 by processing ACT104 and ACT105. The processor 21 realizes the function of the detail display means 52 by processing ACT106. The processor 21 realizes the function of the end detection means 53 by processing ACT126 and ACT127.

[0103] Furthermore, the processor 21 realizes the function of first sending means 54 by processing ACT103 and ACT110. The processor 21 realizes the function of selection means 55 by processing ACT121 to ACT123. The processor 21 realizes the function of first notification means 56 by processing ACT130 to ACT134, ACT141 and ACT142.

[0104] Furthermore, the processor 21 realizes the function of second notification means 57 by processing ACT144 to ACT146, ACT141 and ACT142. The processor 21 realizes the function of third notification means 58 by processing ACT150. The processor 21 realizes the function of payment destination notification means 59 by processing ACT149. The processor 21 realizes the function of input side deletion means 510 by processing ACT151.

[0105] Next, the main steps of the information processing executed by the processor 31 of the settlement device 12 in accordance with the settlement program will be described with reference to the flowcharts of FIGS. When the status flag Fc is "0", that is, when the payment device 12 is in standby mode, the processor 31 starts information processing according to the procedure shown in the flowcharts of Figures 12 and 13. First, in ACT201, the processor 31 sets the screen of the touch panel 38 to the standby screen SBa (see Figure 17).

[0106] FIG. 17 is a display example of the standby screen SBa. The standby screen SBa is a screen that notifies the operator that the operator is on standby. In principle, the operator of the payment device 12 is the customer 3. Therefore, the standby screen SBa may be a screen that displays an image that the customer 3 will not operate arbitrarily. For example, it may be a screen that displays text such as "Welcome" or "Please wait," or a screen that displays an illustration such as the store's logo.

[0107] The processor 31, which has displayed the standby screen SBa, waits for an input event to be transmitted from the input device 11 in ACT202. In this standby state, when an input event is received via the communication unit 35, the processor 31 proceeds from ACT202 to ACT203. In ACT203, the processor 31 checks whether an input event including a product code has been received.

[0108] As described above, input events include input events that include a product code and input events that include a quantity, discount amount, or discount rate. In ACT203, processor 31 confirms that it has received an input event that includes a product code and proceeds to ACT204. In ACT204, processor 31 creates a detail record Ra. That is, processor 31 accesses server 13 and obtains from product master file 131 a product record that includes the product code included in the input event. Then, based on product information such as product name and unit price described in that product record, processor 31 creates a detail record Ra consisting of item data such as record number r, product code, product name, unit price, quantity, discount amount, and amount. Note that the quantity is "1". The discount amount is "0". The amount is the unit price.

[0109] After creating the detail record Ra, the processor 31 proceeds to ACT 205. In ACT 205, the processor 31 stores the detail record Ra in the second transaction file 811.

[0110] On the other hand, if the received input event does not include a product code, the processor 31 proceeds from ACT203 to ACT206. In ACT206, the processor 31 checks whether an input event including a quantity, a discount amount, or a discount rate has been received. If an input event including a quantity, a discount amount, or a discount rate has been received, the processor 31 proceeds from ACT206 to ACT207. In ACT207, the processor 31 updates the detail record Ra of record number r stored in the second transaction file 811. Specifically, if an input event including a quantity is received, the processor 31 sets the quantity in the detail record Ra to the value included in the input event, and sets the amount to the product of the unit price and the quantity. If an input event including a discount amount is received, the processor 31 writes the discount amount in the detail record Ra and subtracts the discount amount from the amount. If an input event including a discount rate is received, the processor 31 calculates and writes the discount amount from the unit price and discount rate in the detail record Ra, and subtracts the discount amount from the amount.

[0111] Thus, upon completing the processing of ACT205 or ACT207, the processor 31 proceeds to ACT208. In ACT208, the processor 31 checks whether the next input event has been received. If an input event has not been received, the processor 31 proceeds from ACT208 to ACT209. In ACT209, the processor 31 checks whether a completion event has been received. If a completion event has not been received, the processor 31 proceeds from ACT209 to ACT210. In ACT210, the processor 31 checks whether a delete event has been received. If a delete event has not been received, the processor 31 returns to ACT208. In this way, the processor 31 waits for an input event, a completion event, or a delete event in ACT208 to ACT210.

[0112] If an input event is received while in the standby state of ACT208 to ACT210, processor 31 returns from ACT208 to ACT203. Then, processor 31 executes the processing from ACT203 onwards in the same manner as described above. That is, if an input event including a product code is received, processor 31 creates a detail record Ra and stores the detail record Ra in the second transaction file 811. If an input event including a quantity, discount amount or discount rate is received, processor 31 updates the detail record Ra with record number r, that is, the detail record Ra stored in the second transaction file 811 in the processing of the immediately preceding ACT205. Then, processor 31 returns to the standby state of ACT208 to ACT210.

[0113] If a deletion event is received during the standby state of ACT208 to ACT210, the processor 31 proceeds from ACT210 to ACT211. In ACT211, the processor 31 clears the second transaction file 811. This clearing deletes all of the detail records Ra stored in the second transaction file 811. After clearing the second transaction file 811, the processor 31 terminates information processing in accordance with the payment program. Thereafter, the processor 31 again displays the standby screen SBa on the touch panel 38 in ACT201.

[0114] If a completion event is received in the standby state of ACT208 to ACT210, the processor 31 proceeds from ACT209 to ACT221 in Fig. 13. In ACT221, the processor 31 checks the status flag Fc in the flag memory 82. If the status flag Fc is "0", that is, if the payment device 12 is on standby, the processor 31 proceeds from ACT221 to ACT222. In ACT222, the processor 31 acquires the payment type included in the completion event.

[0115] After acquiring the payment type, the processor 31 proceeds to ACT223. In ACT223, the processor 31 checks whether the payment type indicates a cashless payment method. Payment types that indicate a cashless payment method are "credit" or "electronic money." The payment type "cash" is not a cashless payment type.

[0116] If the payment type is not a cashless payment method, i.e., if it is "cash," the processor 31 proceeds from ACT223 to ACT225. On the other hand, if the payment type is a cashless payment method, i.e., if it is "credit" or "electronic money," the processor 31 proceeds from ACT223 to ACT224. In ACT224, the processor 31 checks the connection flag Fb in the flag memory 82. If the connection flag Fb is "1," i.e., if a cashless payment terminal 5 is connected to the payment device 12, the processor 31 proceeds from ACT224 to ACT225.

[0117] In this way, if the payment type is "cash", or if the payment type is "credit" or "electronic money" and the connection flag Fb is "1", the processor 31 proceeds to ACT225. In ACT225, the processor 31 controls the communication unit 35 to send an affirmative response (OK) to the input device 11. By this control, an affirmative response (OK) signal is sent from the payment device 12 to the input device 11 that sent the completion event.

[0118] After controlling the transmission of the positive response (OK), the processor 31 proceeds to ACT226. In ACT226, the processor 31 changes the status flag Fc in the flag memory 82 from "0" to "1." That is, the processor 31 stores information indicating that the payment device 12 is in the process of payment. In addition, in ACT227, the processor 31 copies the data in the second transaction file 811 to the third transaction file 812. Then, in ACT228, the processor 31 clears the second transaction file 811. This clearing deletes all of the detail records Ra stored in the second transaction file 811.

[0119] After clearing the second transaction file 811, the processor 31 proceeds to ACT 229. In ACT 229, the processor 31 displays the accounting screen SBb (see FIG. 18) on the touch panel 38, which corresponds to the payment type.

[0120] Figure 18 is an example of the display of the checkout screen SBb when the payment type is "cash." The checkout screen SBb includes a total area ABa that displays the total points and total amount. The checkout screen SBb also includes software keys for a change button BBa and a store clerk call button BBb. The checkout screen SBb is a screen that informs the operator of the payment device 12 of the payment method. In principle, the operator of the payment device 12 is customer 3. Therefore, for example, text such as "Cash payment has been selected. Please insert the amount" is displayed on the checkout screen SBb. After checking this text, customer 3 inserts cash equivalent to the amount into the automatic change machine.

[0121] A customer 3 who wishes to call a store clerk presses the store clerk call button BBb. When the store clerk call button BBb is pressed, a store clerk call signal is output from the payment device 12 to the input device 11, and an image informing the store clerk that a customer has called is displayed on the touch panel 28 of the input device 11.

[0122] Furthermore, a customer 3 who wishes to change the payment method presses the change button BBa. By pressing the change button BBa, a payment method selection screen is displayed on the touch panel 38, and the customer 3 selects the desired payment method. However, in a payment device 12 to which a cashless payment terminal 5 is not connected, cashless payment methods such as credit cards and electronic money cannot be selected.

[0123] After displaying the checkout screen SBb, the processor 31 waits for the payment to be completed as ACT230. For example, if the payment type is "cash" and cash equivalent to the payment is inserted into the automatic change dispenser, the processor 31 determines that the payment has been completed. For example, if the payment type is "credit" or "electronic money," the processor 31 waits for a payment completion signal from the cashless payment terminal 5. Upon receiving the payment completion signal, the processor 31 determines that the payment has been completed.

[0124] When payment is complete, processor 31 proceeds from ACT230 to ACT231. In ACT231, processor 31 operates printer 39 to issue a transaction receipt. The transaction receipt prints the data in detail record Ra stored in third transaction file 812, i.e., the product name, quantity, unit price, amount, etc. of the purchased items. Also printed on the transaction receipt are the total amount of the purchased items, the payment amount, the change amount, the transaction number included in the completion event, etc.

[0125] After issuing the transaction receipt, processor 31 proceeds to ACT 232. In ACT 232, processor 31 performs sales processing of the purchased items based on the detail record Ra stored in the third transaction file 812. This sales processing updates the sales quantity and sales amount of the purchased items stored in the sales master file 132.

[0126] After completing the sales process for the purchased items, the processor 31 proceeds to ACT 233. In ACT 233, the processor 31 clears the third transaction file 812. As a result of this clearing, the detail record Ra stored in the third transaction file 812 is deleted.

[0127] After clearing the third transaction file 812, the processor 31 proceeds to ACT234. In ACT234, the processor 31 changes the status flag Fc from "1" to "0." That is, the processor 31 stores information indicating that the payment device 12 is on standby. With this, the processor 31 ends the information processing in accordance with the payment program. Thereafter, the processor 31 again sets the screen of the touch panel 38 to the standby screen SBa in ACT201.

[0128] On the other hand, if the status flag Fc is "1" in ACT221, that is, if the payment device 12 in the payment in progress state receives a completion event, the processor 31 proceeds from ACT221 to ACT235. The processor 31 controls the communication unit 35 to send a negative response (NG) to the input device 11 in ACT235.

[0129] Similarly, if the connection flag Fb is "1" in ACT224, that is, if the payment device 12 to which the cashless payment terminal 5 is not connected receives a completion event including the cashless payment type, the processor 31 proceeds from ACT224 to ACT235. The processor 31 controls the communication unit 35 to send a negative response (NG) to the input device 11 in ACT235.

[0130] This control causes the settlement device 12 to transmit a negative response (NG) signal to the input device 11 that transmitted the completion event. The processor 31, which controlled the transmission of the negative response (NG), returns to ACT208 in Fig. 12. The processor 31 returns to a standby state for an input event, a completion event, or a deletion event.

[0131] Here, the processor 31 realizes the function of the settlement side storage means 71 by processing ACT203 to ACT205. The processor 31 realizes the function of the amount display means 72 by processing ACT229. The processor 31 realizes the function of the settlement response means 73 by processing ACT221 to ACT225 and ACT235. The processor 31 realizes the function of the settlement means 74 by processing ACT230 to ACT232. The processor 31 realizes the function of the settlement side deletion means 75 by processing ACT211.

[0132] This concludes the explanation of the main information processing executed by the processor 21 of the input device 11 and the processor 31 of the settlement device 12. Next, the operation of the accounting system 1 based on this information processing will be described.

[0133] When the store clerk 2 operates the input device 61 of the input unit 11 to input data related to the transaction, a detail record Ra is created in the input unit 11 and stored in the first transaction file 631. Then, a detail screen SAa is displayed on the touch panel 28 based on the data of the detail record Ra stored in the first transaction file 631. At this time, the information displayed in the current area AAa and total area AAc of the detail screen SAa is displayed on the customer display 29. Therefore, the customer 3 can easily know the product name, unit price, total amount, etc. of the purchased product.

[0134] Furthermore, each time data related to a transaction is input to the input device 11, an input event including the data related to the transaction is sent to the payment device 120 in the same group. As a result, a detail record Ra is created in the payment device 120 as well and stored in the second transaction file 811. However, the screen of the touch panel 38 is the standby screen SBa. The detail screen SAa is never displayed on the touch panel 38. Therefore, information about the purchased items of the customer who is inputting data via the input device 11 cannot be seen by other customers on the screen of the payment device 12.

[0135] After inputting the transaction data, clerk 2 presses the subtotal button BAa, and the screen on touch panel 28 changes to the payment method selection screen SAb. Clerk 2 then confirms with the customer the payment method and selects the payment method desired by the customer. For example, if customer 3 wishes to pay in cash, clerk 2 presses the cash button BAd. For example, if customer 3 wishes to pay by credit card, clerk 2 presses the credit button BAe. For example, if customer 3 wishes to pay by electronic money, clerk 2 presses the electronic money button BAf.

[0136] When the cash button BAd, credit button BAe, or electronic money button BAf is pressed, the screen of the touch panel 28 changes to the payment screen SAc, and the store clerk 2 checks whether there is another customer in front of the base unit 121. If there is no other customer in front of the base unit 121, the store clerk 2 presses the input complete button BAj alone. If there is another customer in front of the base unit 121, the store clerk 2 presses the busy button BAk and then presses the input complete button BAj.

[0137] When the input completion button BAj is pressed, a completion event is transmitted from the input device 11 to any one of the payment devices 120 in the same group. Specifically, when the input completion button BAj is pressed alone, a completion event is transmitted to the parent device 121. When the input completion button BAj is pressed together with the busy button BAk, a completion event is transmitted to the child device 122. The completion event includes the payment type, which is identification data of the payment method selected on the payment method selection screen SAb.

[0138] When the payment device 12 receives the completion event, it determines whether to send a positive response (OK) or a negative response (NG) based on the payment type included in the completion event and the values ​​of the connection flag Fb and the status flag Fc. Next, the cases in which the payment device 12 sends a positive response (OK) and a negative response (NG) will be described in detail with reference to Figures 19 to 34. Figures 19 to 34 are diagrams for explaining response signals sent from the payment devices 120 of the same group, i.e., the payment device 12 (12-1) and the payment device 12 (12-2), for each pattern of operation input on the payment method selection screen Sab and the payment screen SAc of the input device 11 (11-1).

[0139] 19 to 22 show an example in which a payment device 12 (12-1) connected to a cashless payment terminal 5 is set as the parent device 121, and a payment device 12 (12-2) not connected to a cashless payment terminal 5 is set as the child device 122. FIG. 19 shows a case in which both the payment device 12 (12-1) and the payment device 12 (12-2) are on standby. FIG. 20 shows a case in which the payment device 12 (12-1) is in the middle of a payment, and the payment device 12 (12-2) is on standby. FIG. 21 shows a case in which the payment device 12 (12-1) is on standby, and the payment device 12 (12-2) is in the middle of a payment. FIG. 22 shows a case in which both the payment device 12 (12-1) and the payment device 12 (12-2) are in the middle of a payment.

[0140] In the example of FIG. 19, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master device 121. At this time, the payment device 12 (12-1) is in standby mode and is therefore able to process payments. In addition, since the payment device 12 (12-1) is connected to a cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0141] On the other hand, in the example of FIG. 19, if the busy button BAk is pressed after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is pressed, a completion event is transmitted to the settlement device 12 (12-2) of the slave device 122. At this time, the settlement device 12 (12-2) is in standby mode and is therefore capable of settlement processing. However, since the settlement device 12 (12-2) is not connected to a cashless settlement terminal 5, it does not support cashless payments using credit cards or electronic money. Therefore, when a completion event including the payment type [cash] is received, the settlement device 12 (12-2) returns a positive response (OK) signal to the input device 11 (11-1). However, when a completion event including the payment type [credit] or the payment type [electronic money] is received, the settlement device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1).

[0142] In the example of Figure 20, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master unit 121. At this time, the payment device 12 (12-1) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0143] In the input device 11 (11-1) that receives the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. Then, the completion event is transmitted to the payment device 12 (12-2) of the slave device 122. At this time, the payment device 12 (12-2) is in standby mode and is therefore capable of performing payment processing. However, since the cashless payment terminal 5 is not connected to the payment device 12 (12-2), the payment device 12 (12-2) does not support cashless payments using credit cards or electronic money. Therefore, when the payment device 12 (12-2) receives a completion event including the payment type [cash], it returns a positive response (OK) signal to the input device 11 (11-1), but when it receives a completion event including the payment type [credit] or the payment type [electronic money], it returns a negative response (NG) signal to the input device 11 (11-1).

[0144] On the other hand, in the example of FIG. 20, if the busy button BAk is pressed after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the payment device 12 (12-2) of the slave device 122. At this time, the payment device 12 (12-2) is in standby mode and is therefore able to process the payment. However, since the cashless payment terminal 5 is not connected to the payment device 12 (12-2), it does not support cashless payments using credit cards or electronic money. Therefore, when the payment device 12 (12-2) receives a completion event including the payment type [cash], it returns a positive response (OK) signal to the input device 11 (11-1). However, when it receives a completion event including the payment type [credit] or the payment type [electronic money], it returns a negative response (NG) signal to the input device 11 (11-1).

[0145] In the example of FIG. 21, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master device 121. At this time, the payment device 12 (12-1) is in standby mode and is therefore able to process payments. In addition, since the payment device 12 (12-1) is connected to a cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0146] 21, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-2) of the slave device 122. At this time, the settlement device 12 (12-2) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0147] In the example of Figure 22, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master unit 121. At this time, the payment device 12 (12-1) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0148] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. The completion event is then transmitted to the settlement device 12 (12-2) of the slave device 122. At this time, the settlement device 12 (12-2) is also in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0149] 22, if the busy button BAk is pressed after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-2) of the slave device 122. At this time, the settlement device 12 (12-2) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0150] 19 to 23, the input device 11 (11-1) notifies a transmission error when it receives a negative acknowledgement (NG) signal from the child device 122. Then, when a retransmission command is issued in response to this notification, the input device 11 (11-1) retransmits a completion event to the parent device 121 or the child device 122.

[0151] Figures 23 to 26 show an example in which a payment device 12 (12-1) connected to a cashless payment terminal 5 is set as a slave device 122, and a payment device 12 (12-2) not connected to a cashless payment terminal 5 is set as a master device 121. Figure 23 shows a case in which both the payment device 12 (12-1) and the payment device 12 (12-2) are on standby. Figure 24 shows a case in which the payment device 12 (12-1) is in the middle of a payment, and the payment device 12 (12-2) is on standby. Figure 25 shows a case in which the payment device 12 (12-1) is on standby, and the payment device 12 (12-2) is in the middle of a payment. Figure 26 shows a case in which both the payment device 12 (12-1) and the payment device 12 (12-2) are in the middle of a payment.

[0152] In the example of FIG. 23, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master device 121. At this time, the payment device 12 (12-2) is in standby mode and is therefore capable of performing payment processing. However, since the payment device 12 (12-2) is not connected to a cashless payment terminal 5, it does not support cashless payments using credit cards or electronic money. Therefore, when the payment device 12 (12-2) receives a completion event including the payment type [cash], it returns a positive response (OK) signal to the input device 11 (11-1), but when it receives a completion event including the payment type [credit] or payment type [electronic money], it returns a negative response (NG) signal to the input device 11 (11-1).

[0153] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. Then, the completion event is sent to the payment device 12 (12-1) of the slave device 122. At this time, the payment device 12 (12-1) is on standby and therefore able to process the payment. In addition, since the payment device 12 (12-1) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns a positive response (OK) signal to the input device 11 (11-1) in response to the completion event including the payment type [credit] or payment type [electronic money].

[0154] On the other hand, in the example of FIG. 23, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the payment device 12 (12-1) of the slave device 122. At this time, the payment device 12 (12-1) is on standby and therefore capable of performing payment processing. In addition, since the payment device 12 (12-1) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0155] In the example of FIG. 24, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master device 121. At this time, the payment device 12 (12-2) is in standby mode and is therefore capable of performing payment processing. However, since the cashless payment terminal 5 is not connected to the payment device 12 (12-2), the payment device 12 (12-2) does not support cashless payments using credit cards or electronic money. Therefore, when the payment device 12 (12-2) receives a completion event including the payment type [cash], it returns an affirmative response (OK) signal to the input device 11 (11-1). However, when the payment device 12 (12-2) receives a completion event including the payment type [credit] or the payment type [electronic money], it returns a negative response (NG) signal to the input device 11 (11-1).

[0156] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. The completion event is then transmitted to the settlement device 12 (12-1) of the slave device 122. At this time, the settlement device 12 (12-1) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0157] 24, if the busy button BAk is pressed after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-1) of the slave device 122. At this time, the settlement device 12 (12-1) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0158] In the example of Figure 25, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master unit 121. At this time, the payment device 12 (12-2) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0159] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. Then, the completion event is transmitted to the payment device 12 (12-1) of the slave device 122. At this time, the payment device 12 (12-1) is in standby mode and is therefore able to process the payment. In addition, since the payment device 12 (12-1) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns a positive response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0160] On the other hand, in the example of FIG. 25, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the payment device 12 (12-1) of the slave device 122. At this time, the payment device 12 (12-1) is on standby and therefore capable of performing payment processing. In addition, since the payment device 12 (12-1) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0161] In the example of Figure 26, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master unit 121. At this time, the payment device 12 (12-2) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0162] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. The completion event is then transmitted to the settlement device 12 (12-1) of the slave device 122. At this time, the settlement device 12 (12-1) is also in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0163] 26, if the busy button BAk is pressed after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-1) of the slave device 122. At this time, the settlement device 12 (12-1) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0164] 24 to 26, the input device 11 (11-1) notifies a transmission error when it receives a negative acknowledgement (NG) signal from the child device 122. Then, when a retransmission command is issued in response to this notification, the input device 11 (11-1) retransmits a completion event to the parent device 121 or the child device 122.

[0165] Figures 27 to 30 show an example in which not only the payment device 12 (12-1) but also the payment device 12 (12-2) is connected to the cashless payment terminal 5, the payment device 12 (12-1) is set as the parent device 121, and the payment device 12 (12-2) is set as the child device 122. Figure 27 shows a case in which the payment device 12 (12-1) and the payment device 12 (12-2) are both on standby. Figure 28 shows a case in which the payment device 12 (12-1) is in the middle of a payment, and the payment device 12 (12-2) is on standby. Figure 29 shows a case in which the payment device 12 (12-1) is on standby, and the payment device 12 (12-2) is in the middle of a payment. Figure 30 shows a case in which the payment device 12 (12-1) and the payment device 12 (12-2) are both in the middle of a payment.

[0166] In the example of FIG. 27, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master device 121. At this time, the payment device 12 (12-1) is in standby mode and is therefore able to process payments. In addition, since the payment device 12 (12-1) is connected to a cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0167] On the other hand, in the example of Figure 27, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the payment device 12 (12-2) of the slave device 122. At this time, the payment device 12 (12-2) is on standby and therefore able to process the payment. In addition, since the payment device 12 (12-2) is also connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-2) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0168] In the example of Figure 28, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master unit 121. At this time, the payment device 12 (12-1) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0169] In the input device 11 (11-1) that receives the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. Then, the completion event is transmitted to the payment device 12 (12-2) of the slave device 122. At this time, the payment device 12 (12-2) is in standby mode and is therefore able to process the payment. In addition, since the payment device 12 (12-2) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-2) returns a positive response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0170] On the other hand, in the example of FIG. 28, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the payment device 12 (12-2) of the slave device 122. At this time, the payment device 12 (12-2) is on standby and therefore capable of performing payment processing. In addition, since the payment device 12 (12-2) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-2) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0171] In the example of FIG. 29, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master device 121. At this time, the payment device 12 (12-1) is in standby mode and is therefore able to process payments. In addition, since the payment device 12 (12-1) is connected to a cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0172] 29, if the busy button BAk is pressed after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-2) of the slave device 122. At this time, the settlement device 12 (12-2) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0173] In the example of Figure 30, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-1) of the master unit 121. At this time, the payment device 12 (12-1) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0174] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. The completion event is then transmitted to the settlement device 12 (12-2) of the slave device 122. At this time, the settlement device 12 (12-2) is also in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0175] 30, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-2) of the slave device 122. At this time, the settlement device 12 (12-2) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0176] 27 to 30, the input device 11 (11-1) notifies a transmission error when it receives a negative acknowledgement (NG) signal from the child device 122. Then, when a retransmission command is issued in response to this notification, the input device 11 (11-1) retransmits a completion event to the parent device 121 or the child device 122.

[0177] Figures 31 to 34 show an example in which not only the payment device 12 (12-1) but also the payment device 12 (12-2) is connected to the cashless payment terminal 5, the payment device 12 (12-1) is set as the slave device 122, and the payment device 12 (12-2) is set as the master device 121. Figure 31 shows a case in which the payment device 12 (12-1) and the payment device 12 (12-2) are both on standby. Figure 32 shows a case in which the payment device 12 (12-1) is in the middle of a payment, and the payment device 12 (12-2) is on standby. Figure 33 shows a case in which the payment device 12 (12-1) is on standby, and the payment device 12 (12-2) is in the middle of a payment. Figure 34 shows a case in which the payment device 12 (12-1) and the payment device 12 (12-2) are both in the middle of a payment.

[0178] In the example of Figure 31, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master device 121. At this time, the payment device 12 (12-2) is in standby mode and is therefore able to process payments. In addition, since the payment device 12 (12-2) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-2) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0179] On the other hand, in the example of Figure 31, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the payment device 12 (12-1) of the slave device 122. At this time, the payment device 12 (12-1) is on standby and therefore able to process the payment. In addition, since the payment device 12 (12-1) is also connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0180] In the example of Fig. 32, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master unit 121. At this time, the payment device 12 (12-2) is on standby and therefore capable of performing payment processing. Therefore, the payment device 12 (12-2) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0181] 32, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-1) of the slave device 122. At this time, the settlement device 12 (12-1) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0182] In the example of Figure 33, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master unit 121. At this time, the payment device 12 (12-2) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0183] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. Then, the completion event is transmitted to the payment device 12 (12-1) of the slave device 122. At this time, the payment device 12 (12-1) is in standby mode and is therefore able to process the payment. In addition, since the payment device 12 (12-1) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns a positive response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0184] On the other hand, in the example of FIG. 33, if the busy button BAk is pressed after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the payment device 12 (12-1) of the slave device 122. At this time, the payment device 12 (12-1) is on standby and therefore capable of performing payment processing. In addition, since the payment device 12 (12-1) is connected to the cashless payment terminal 5, it can accept payments not only with cash but also with credit cards or electronic money. Therefore, the payment device 12 (12-1) returns an affirmative response (OK) signal to the input device 11 (11-1) in response to the completion event.

[0185] In the example of Figure 34, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12 (12-2) of the master unit 121. At this time, the payment device 12 (12-2) is in the middle of a payment and is therefore unable to process the payment. Therefore, the payment device 12 (12-2) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0186] In the input device 11 (11-1) that has received the negative response (NG) signal, the destination of the completion event is changed to the slave device 122. The completion event is then transmitted to the settlement device 12 (12-1) of the slave device 122. At this time, the settlement device 12 (12-1) is also in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0187] 34, if the busy button BAk is pressed after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is pressed, a completion event is sent to the settlement device 12 (12-1) of the slave device 122. At this time, the settlement device 12 (12-1) is in the middle of a settlement and is therefore unable to process the settlement. Therefore, the settlement device 12 (12-1) returns a negative response (NG) signal to the input device 11 (11-1) in response to the completion event.

[0188] 31 to 34, the input device 11 (11-1) notifies a transmission error when it receives a negative acknowledgement (NG) signal from the child device 122. When a retransmission command is issued in response to this notification, the input device 11 (11-1) retransmits a completion event to the parent device 121 or the child device 122.

[0189] As described above in detail, according to the first embodiment, an accounting system 1 can be provided in which the clerk 2 and the customer 3 can share the operations to settle a transaction without the input device 11 generating and transmitting payment information including detailed information and total information of the purchased and sold items to the payment device 12.

[0190] Furthermore, even if the master unit 121 is in the middle of a settlement and is unable to process the settlement, if the slave unit 122 is on standby and is able to process the settlement, the customer 3 can settle the transaction using the slave unit 122. Even in this case, the input device 11 does not need to generate settlement information and send it to the slave unit 122.

[0191] Furthermore, when a deletion event is received by the slave device 122 due to the master device 121 executing a payment process, the slave device 122 discards the detail record Ra stored in the second transaction file 811. Therefore, the slave device 122 can immediately prepare for the next customer's payment.

[0192] Furthermore, when the input complete button BAj is pressed alone, the input device 11 sends a completion event to the main unit 121, but when the input complete button BAj and the busy button BAk are pressed together, the input device 11 sends a completion event to the sub-unit 122. For example, if there is a customer 3 who has finished paying but is taking a long time to put the money back into his wallet in front of the main unit 121, the store clerk 2 presses the busy button BAk and then the input complete button BAj. In this case, the completion event is sent to the sub-unit 122, not to the main unit 121. Therefore, the completion event is sent to the main unit 121 where the delayed customer is located, and the payment amount for the next customer is not displayed on the touch panel 38 of the main unit 121.

[0193] The store clerk 2 also inputs the payment method desired by the customer 3 into the input device 11. The payment device 12, to which the completion event is sent, then executes the payment process using the payment method. This eliminates the need for the customer 3 to specify the payment method on the payment device 12.

[0194] Furthermore, if a payment device 12 is unable to process the payment using the payment method desired by the customer 3, it will return a negative response to the input device 11. Therefore, there is no problem in that the store clerk 2 guides the customer 3 to a payment device 12 that is unable to process the payment using the payment method desired by the customer 3.

[0195] [Second embodiment] Next, a second embodiment will be described with reference to FIGS. The second embodiment adds a function to the accounting system 1 of the first embodiment to retroactively correct the data of the purchased items for one transaction entered into the input device 11 before the input completion instruction, which is the input of the input completion button BAj, is given. Therefore, parts that are common to the first embodiment are given the same reference numerals and detailed explanations will be omitted.

[0196] 35 is a block diagram showing the main functional configuration of the processor 21 of the input device 11. The processor 21 has the functions of correction receiving means 511, input side correction means 512, and second transmission means 513 in addition to input side storage means 51, detail display means 52, completion detection means 53, first transmission means 54, selection means 55, first notification means 56, second notification means 57, third notification means 58, payment destination notification means 59, and input side deletion means 510.

[0197] The correction receiving means 511 is a function that receives corrections to the detail information displayed on the detail screen SAa of the touch panel 28 by the detail display means 52. The detail area AAb of the detail screen SAa displays in list form, in the order of the series of record numbers, the product name, quantity, unit price, discount amount, and amount of the product entered as the purchased product of one transaction. The correction receiving means 511 receives deletion of the detail record Ra in which the product name, quantity, unit price, etc. are displayed in the detail area AAb, or changes to the quantity, unit price, discount amount, discount rate, etc.

[0198] The input-side correction means 512 has a function of correcting data related to a transaction transmitted by the first transmission means 54 to each of the payment apparatuses 120 in the same group before the end detection means 53 detects an instruction to end input of the data related to the transaction. Data related to a transaction transmitted to multiple payment apparatuses 12 is stored in the first transaction file 631 as a detail record Ra. The input-side correction means 512 corrects the detail record Ra stored in the first transaction file 631 in response to input from the input device 61. For example, the input-side correction means 512 deletes the detail record Ra. For example, the input-side correction means 512 corrects the unit price, quantity, discount amount, etc. of the detail record Ra.

[0199] The second transmission means 513 has a function of transmitting the data related to the transaction corrected by the input side correction means 512 to each of the payment devices 120 in the same group before the end detection means 53 detects an instruction to end input of the data related to the transaction.

[0200] 36 is a block diagram showing the main functional configuration of the processor 31 of the payment device 12. The processor 31 has a function as a payment side correction means 76 in addition to a payment side storage means 71, an amount display means 72, a payment response means 73, a payment means 74, and a payment side deletion means 75.

[0201] The settlement side correction means 76 has a function of correcting the transaction data stored in the settlement side memory unit 81 using the transaction data transmitted from the input device 11 by the second transmission means 513. The second transaction file 811 of the settlement side memory unit 81 stores the detail record Ra created by the settlement device 12 based on the transaction data transmitted from the input device 11 by the first transmission means 54. The settlement side correction means 76 corrects the detail record Ra stored in the second transaction file 811 using the transaction data transmitted from the input device 11 by the second transmission means 513. For example, the settlement side correction means 76 deletes the detail record Ra. For example, the settlement side correction means 76 corrects the unit price, quantity, discount amount, etc. of the detail record Ra.

[0202] Next, the content and procedures of the information processing related to the second embodiment, among the information processing executed by the input device 11 and the settlement device 12 that constitute the accounting system 1, will be explained using the flowcharts of Figures 37 and 38 and the example screens of Figures 39 to 44. Note that the content and procedures of the information processing described below are merely examples. The content and procedures can be changed as appropriate as long as similar effects can be achieved. The example screens are also merely examples. The content of the output text, the arrangement of images, the type and layout of the software keys, etc. can be changed as appropriate.

[0203] First, the main steps of the information processing executed by the processor 21 of the input device 11 according to the input program will be described using the flowchart in Fig. 37. The flowchart in Fig. 37 corresponds to the flowchart in Fig. 9 in the first embodiment. Therefore, the same reference numerals are used to designate the same processing steps as in Fig. 9.

[0204] As in the first embodiment, the processor 21 sets the screen of the touch panel 28 to the detail screen SAa in ACT101. Then, the processor 21 waits for the product code to be input in ACT102. When the product code is input, the processor 21 executes the processes in ACT103 to ACT106, and then waits for ACT107 to ACT109. That is, the processor 21 waits for the product code, quantity or discount data, and the subtotal button BAa.

[0205] Here, in the second embodiment, in addition to the above-mentioned product code, quantity or discount data, and subtotal button BAa, ACT301 waits for the selection of a product displayed in the details area AAb of the details screen SAa.

[0206] FIG. 39 shows an example of the detail screen SAa after data related to the purchase of four items has been entered. Specifically, FIG. 39 shows the detail screen SAa after the product code for product AAAAA (unit price: 200 yen), product code BBBBB (unit price: 300 yen), product code CCCCC (unit price: 400 yen), and product code DDDDD (unit price: 100 yen) have been entered in this order. With these entries, the current area AAa displays the product name, quantity, and price of product DDDDD. The detail area AAb displays the product name, quantity, unit price, and price of product AAAAA in association with record number "1," the product name, quantity, unit price, and price of product BBBBB in association with record number "2," and the product name, quantity, unit price, and price of product CCCCC in association with record number "3." The total area AAc displays the total number of items (4) and the total price (1,000 yen).

[0207] At this time, the processing of ACT104 and ACT105 causes detail record Ra-A of product AAAAA, detail record Ra-B of product BBBBB, detail record Ra-C of product CCCCC, and detail record Ra-D of product DDDDD to be stored in the first transaction file 631. Furthermore, the processing of ACT106 causes an input event including the product code of product AAAAA, an input event including the product code of product BBBBB, an input event including the product code of product CCCCC, and an input event including the product code of product DDDDD to be sent to each of the payment devices 120 in the same group. Each input event is sent to each of the payment devices 120 in the same group each time a product code is input. By sending these input events, the payment devices 120 in the same group store detail record Ra-A for product AAAAA, detail record Ra-B for product BBBBB, detail record Ra-C for product CCCCC, and detail record Ra-D for product DDDDD in the second transaction file 811, respectively.

[0208] Returning to the explanation of Figure 37. In the standby state of ACT107 to ACT109 and ACT301, for example, assume that customer 3 requests the return of product BBBBB. In this case, store clerk 2, who is the operator of input device 11, touches the row in detail area AAb where data related to product BBBBB is displayed. In this way, by touching the row in detail area AAb, processor 21 determines in ACT301 that a product has been selected.

[0209] If it is determined that a product has been selected, the processor 21 proceeds from ACT 301 to ACT 302. In ACT 302, the processor 21 displays a correction screen SAd (see FIG. 40) on the touch panel 28.

[0210] 40 shows an example of the edit screen SAd. The edit screen SAd includes an area AAf that displays the product name of the product selected from the details area AAb, an area AAg that displays the quantity, unit price, discount amount, and total price of the product selected from the details area AAb, and an area AAh that displays operation guidance and the like. The edit screen SAd also includes software keys for a cancel button BAn, a change quantity button BAo, a change unit price button BAp, a discount button BAq, a discount button BAr, a cancel button BAs, and an OK button BAt. It is preferable that the edit screen SAd be displayed as a pop-up overlaid on the details screen SAa.

[0211] After checking the correction screen SAd, clerk 2 presses the cancel button BAn. When the cancel button BAn is pressed, a strikethrough is displayed on the quantity, unit price, discount amount, and price of product BBBBB displayed in area AAg, as shown in Figure 41. In addition, the quantity change button BAo, unit price change button BAp, discount button BAq, and discount button BAr are grayed out and cannot be entered. Here, if customer 3 cancels the return of product BBBBB, clerk 2 presses the cancel button BAs. If customer 3 wishes to confirm the return of product BBBBB, clerk 2 presses the OK button BAt.

[0212] Returning to the explanation of Figure 37. The processor 21, which has displayed the modification screen SAd, checks whether the OK button BAt has been pressed in ACT303. If the OK button BAt has not been pressed, the processor 21 proceeds from ACT303 to ACT304. The processor 21 checks whether the cancel button BAs has been pressed in ACT304. If the cancel button BAs has not been pressed, the processor 21 returns from ACT304 to ACT303. In this way, the processor 21, which has displayed the modification screen SAd, waits for the OK button BAt or the cancel button BAs to be pressed in ACT303 and ACT304.

[0213] If the cancel button BAs is pressed in the standby state of ACT303 and ACT304, the processor 21 proceeds from ACT304 to ACT305. The processor 21 erases the correction screen SAd in ACT305. Thereafter, the processor 21 returns to the standby state of ACT107 to ACT109 and ACT301. In this way, when the store clerk 2 presses the cancel button BAs, the correction screen SCd is erased. As a result, the screen of the touch panel 28 becomes the detail screen SAa shown in FIG.

[0214] On the other hand, if the OK button BAt is pressed during the standby state of ACT303 and ACT304, the processor 21 proceeds from ACT303 to ACT306. In ACT306, the processor 21 transmits a correction event to the payment devices 120 in the same group by multicast communication. The correction event includes the information input to the correction screen SAd, i.e., in this case, information indicating the cancellation of product BBBBB. The processor 21 also corrects the detail record Ra in ACT307. That is, the processor 21 deletes the detail record Ra-B for product BBBBB stored in the first transaction file 631. Then, in ACT308, the processor 21 erases the correction screen SAd and updates the detail screen SAa. Thereafter, the processor 21 returns to the standby state of ACT107 to ACT109 and ACT301.

[0215] Figure 42 is an example of the display of the detail screen SAa updated after deleting product BBBBB. As shown in Figure 42, the product name, quantity, unit price, discount amount, and price of product BBBBB are erased from detail area AAb. Then, the product name, quantity, unit price, discount amount, and price of product DDDDD that were displayed in current area AAa are displayed in detail area AAb. The product name, quantity, and price of product BBBBB are displayed in current area AAa. Then, the product name, quantity, and price in current area AAa are crossed out. This display allows store clerk 2 to confirm that product BBBBB has been canceled.

[0216] In the standby state of ACT107 to ACT109 and ACT301, for example, assume that the quantity of product BBBBB is to be changed from "1" to "3." In this case, too, the sales clerk 2 touches the row in the detail area AAb where the data for product BBBBB is displayed. This touch operation causes the processor 21 to execute the processing of ACT302. This processing causes the correction screen SAd to be displayed on the touch panel 28, and the sales clerk 2 presses the change quantity button BAo. When the change quantity button BAo is pressed, the background color of the section displaying the quantity in area AAg differs from the background color of the other sections, as shown in FIG. 43. This difference in background color allows the sales clerk 2 to recognize that a quantity correction has been instructed. Note that the cancel button BAn, change price button BAp, discount button BAq, and discount button BAr are grayed out and cannot be entered. The sales clerk 2 who instructed to correct the quantity operates the numeric keypad of the keyboard 26 to input the corrected quantity of "3" and presses the OK button BAt.

[0217] When the OK button BAt is pressed, the processor 21 executes the processing of ACT306 to ACT308. That is, the processor 21 sends a correction event to the payment devices 120 in the same group. The correction event includes the information input to the correction screen SAd, i.e., in this case, information to correct the quantity of product BBBBB from "1" to "3." The processor 21 also corrects the detail record Ra. That is, the processor 21 corrects the quantity in the detail record Ra-B of product BBBBB stored in the first transaction file 631 from "1" to "3." The processor 21 also corrects the amount in the detail record Ra-B from 300 yen to 900 yen. The processor 21 then updates the detail screen SAa.

[0218] Figure 44 shows the detail screen SAa after the quantity of product BBBBB has been revised from "1" to "3." As shown in Figure 44, the product name of product BBBBB whose quantity has been revised, the revised quantity, and the price after the revised quantity are displayed in the current area AAa. In addition, in the detail area AAb, the data for product BBBBB is deleted and the data for product DDDDD is added.

[0219] In the standby state of ACT107 to ACT109 and ACT301, for example, to modify the unit price of product BBBBB, clerk 2 presses the unit price change button BAp on the modification screen SAd, inputs the modified unit price using the numeric keypad, and presses the OK button BAt. For example, to modify the discount amount of product BBBBB, clerk 2 presses the discount button BAq on the modification screen SAd, inputs the modified discount amount using the numeric keypad, and presses the OK button BAt. For example, to modify the discount rate of product BBBBB, clerk 2 presses the discount button BAr on the modification screen SAd, inputs the modified discount rate using the numeric keypad, and presses the OK button BAt.

[0220] By these operations, the processor 21 executes the processes of ACT306 to ACT308. That is, the processor 21 transmits a correction event to the settlement apparatuses 120 in the same group. The processor 21 also corrects the detail record Ra. Then, the processor 21 updates the detail screen SAa.

[0221] Thereafter, when the subtotal button BAa is pressed, the processor 21 proceeds to ACT121 in Fig. 10. Then, the processor 21 executes the processes from ACT121 onwards, similarly to the first embodiment.

[0222] Here, the processor 21 realizes the function of correction receiving means 511 by processing ACT301 and ACT302. The processor 21 realizes the function of input side correction means 512 by processing ACT307. The processor 21 realizes the function of second transmission means 513 by processing ACT306.

[0223] Next, the main steps of the information processing executed by processor 31 of payment device 12 in accordance with the payment program will be described using the flowchart in Figure 38. The flowchart in Figure 38 corresponds to the flowchart in Figure 12 in the first embodiment. Therefore, the same reference numerals are used for the steps of the processing common to Figure 12.

[0224] As in the first embodiment, the processor 31 sets the screen of the touch panel 38 to the standby screen SBa in ACT201. Then, the processor 31 waits for an input event to be transmitted from the input device 11 in ACT202. In this standby state, when the processor 31 receives an input event via the communication unit 35, the processor 31 executes the processes of ACT203 to ACT207. Then, the processor 31 waits for an input event, a completion event, or a deletion event in ACT208 to ACT210.

[0225] In the second embodiment, in the standby state of ACT208 to ACT210, the processor 31 further waits for a correction event in ACT401. Then, upon receiving a correction event, the processor 31 proceeds from ACT401 to ACT402. In ACT402, the processor 31 corrects the detail record Ra stored in the second transaction file 811. Specifically, for example, when a correction event including information on the cancellation of product BBBBB is received, the processor 31 deletes the detail record Ra-B for product BBBBB from the second transaction file 811. For example, when a correction event including information on correcting the quantity of product BBBBB is received, the processor 31 corrects the quantity and price in the detail record Ra-B. For example, when a correction event including information on correcting the unit price, discount amount, or discount rate of product BBBBB is received, the processor 31 corrects the unit price or discount amount and price in the detail record Ra-B.

[0226] When the modification of detail record Ra is completed in this way, the processor 31 returns to the standby state of ACT208 to ACT210 and ACT401. If a completion event is received in this standby state, the processor 31 proceeds to ACT221 in Fig. 13. Thereafter, the processor 21 executes the processes from ACT221 onwards, as in the first embodiment.

[0227] Here, the processor 31 realizes the function of the settlement side correction means 76 by processing ACT402.

[0228] In this way, the second embodiment also provides an accounting system 1 in which the clerk 2 and the customer 3 share the operations to settle a transaction, without the input device 11 generating and transmitting payment information including details and total information for the purchased items to the payment device 12. Moreover, the accounting system 1 of the second embodiment can retroactively correct the data of the purchased items for one transaction that was entered into the input device 11 before the input completion instruction, which is the input of the input completion button BAj, was given.

[0229] [Third embodiment] Next, a third embodiment will be described with reference to FIGS. The third embodiment adds a function to the accounting system 1 of the first embodiment to undo and correct the transaction for which input completion was instructed after input completion is instructed by pressing the input completion button BAj. Therefore, parts that are common to the first embodiment are given the same reference numerals and detailed explanations will be omitted.

[0230] 45 is a block diagram showing the main functional configuration of the processor 21 of the input device 11. The processor 21 has the functions of an input side storage means 51, a statement display means 52, an end detection means 53, a first transmission means 54, a selection means 55, a first notification means 56, a second notification means 57, a third notification means 58, a settlement destination notification means 59, and an input side deletion means 510, as well as a cancellation detection means 514, a designation acceptance means 515, a fourth notification means 516, an input side correction means 517, a third transmission means 518, and a non-notification means 519.

[0231] The cancellation detection means 514 has a function of detecting an instruction to cancel the settlement of a transaction for which the end of input has been notified by the first notification means 56. When an operation input to instruct the cancellation of the settlement of a transaction is made via the input device 61, the cancellation detection means 514 detects a signal corresponding to the operation input as a signal instructing the cancellation of the settlement.

[0232] The designation receiving means 515 is a function that receives input specifying the payment apparatus 12 for which the settlement of the transaction is to be canceled from among the payment apparatuses 120 in the same group. The designation receiving means 515 receives input specifying the payment apparatus 12 for which the settlement of the transaction is to be canceled via the input device 61.

[0233] The fourth notification means 516 has a function of notifying each of the payment devices 120 in the same group of the payment cancellation when the cancellation detection means 514 detects an instruction to cancel the payment of a transaction via the communication unit 25. The fourth notification means 516 outputs a signal to each of the payment devices 120 in the same group notifying the cancellation of the payment together with the identification information of the payment device 12 that has accepted the designation input by the designation acceptance means 515.

[0234] The input-side correction means 517 is a function that corrects the data related to the transaction stored in the input-side memory unit 63, on the condition that a response (positive response: OK) approving the payment cancellation is received from one of the payment devices 12 in response to the payment cancellation notification. The data in the first transaction file 631 is copied to the fourth transaction file 632 when a signal responding that payment is possible is received from the payment device 12 that output a signal notifying the end of input. The input-side correction means 517 corrects the detail record Ra stored in the fourth transaction file 632 in accordance with input from the input device 61. For example, the input-side correction means 517 deletes the detail record Ra. For example, the input-side correction means 517 corrects the unit price, quantity, discount amount, etc. of the detail record Ra.

[0235] The third transmitting means 518 has a function of transmitting the data related to the transaction corrected by the input side correcting means 517 to each of the payment devices 120 in the same group via the communication unit 25. Every time the data related to the transaction is corrected, the third transmitting means 518 transmits the corrected data related to the transaction to each of the payment devices 120 in the same group.

[0236] The non-cancellation notification means 519 is a function that notifies that the payment cannot be canceled if there is no response from the payment device 12 in response to the notification of the payment cancellation permitting the payment cancellation. The non-cancellation notification means 519 notifies by, for example, displaying on the display device 62 a text or image indicating that the payment cannot be canceled.

[0237] 46 is a block diagram showing the main functional configuration of the processor 31 of the settlement device 12. The processor 31 has the functions of a settlement side storage means 71, an amount display means 72, a settlement response means 73, a settlement means 74, and a settlement side deletion means 75, as well as a cancellation response means 77 and a settlement side correction means 78.

[0238] The cancellation response means 77 has a function of returning a response approving the cancellation of a settlement to the input device 11 via the communication unit 35 if the settlement of the transaction for which the cancellation of a settlement has been notified has not been completed. If the settlement of the transaction for which the cancellation of a settlement has been notified has been completed, the cancellation response means 77 does not return the above response.

[0239] The settlement side correction means 78 has a function of correcting the data related to the transaction stored in the settlement side memory unit 81 using data related to the transaction transmitted from the input device 11 by the third transmission means 518. When the settlement means 74 receives a signal notifying the end of input from the input device 11 when the transaction is ready for settlement, it copies the detail record Ra stored in the second transaction file 811 to the third transaction file 812. The settlement side correction means 78 corrects the detail record Ra copied to the third transaction file 812 using the data related to the transaction transmitted from the input device 11 by the third transmission means 518. For example, the settlement side correction means 78 deletes the detail record Ra. For example, the settlement side correction means 78 corrects the unit price, quantity, discount amount, etc. of the detail record Ra.

[0240] Next, the content and procedures of information processing related to the third embodiment, among the information processing executed by the input device 11 and payment device 12 that constitute the accounting system 1, will be explained using the flowcharts in Figures 47 to 51 and the screen examples in Figures 52 to 54. Note that the content and procedures of the information processing described below are examples. The content and procedures can be changed as appropriate as long as similar effects can be achieved. The screen examples are also examples. The content of the output text, the arrangement of images, the type and layout of software keys, etc. can be changed as appropriate.

[0241] First, the main steps of the information processing executed by the processor 21 of the input device 11 according to the input program will be described using the flowcharts in Figures 47, 48, and 49. The flowchart in Figure 47 corresponds to the flowchart in Figure 11 in the first embodiment. Therefore, the same reference numerals are used to designate the same processing steps as in Figure 11. Figure 48 corresponds to the flowchart in Figure 9 in the first embodiment. Therefore, the same reference numerals are used to designate the same processing steps as in Figure 9.

[0242] As shown in FIG. 47, in the third embodiment, the processor 21 transmits a completion event to the payment device 12 determined as the destination among the payment devices 120 in the same group by unicast communication in ACT142, and then receives an acknowledgment (OK) signal from the payment device 12 in ACT144. Part of the processing after receiving the acknowledgment (OK) signal from the payment device 12 differs from that in the first embodiment. That is, upon receiving the acknowledgment (OK) signal, the processor 21 notifies the payment device 12 that is the destination of the completion event in ACT149. Furthermore, the processor 21 transmits a deletion event to the payment devices 12 other than the destination among the payment devices 120 in the same group by unicast communication in ACT150. Furthermore, the processor 21 copies all detail records Ra stored in the first transaction file 631 to the fourth transaction file 632 in ACT501. Thereafter, the processor 21 clears the first transaction file 631 in ACT151, and ends the information processing according to the input program.

[0243] In this way, the processor 21 has the function of sending a completion event to the payment device 12 determined as the destination, and upon receiving an affirmative response (OK) signal from that payment device 12, copying all detail records Ra stored in the first transaction file 631 to the fourth transaction file 632 and clearing the first transaction file 631. Therefore, the fourth transaction file 632 stores the detail records Ra of the transaction settled by the payment device 12 that returned the affirmative response (OK). Meanwhile, since the first transaction file 631 is cleared, the input device 11 becomes available for inputting data related to the next transaction with the customer.

[0244] When the first transaction file 631 is cleared, the processor 21 starts the information processing procedure shown in the flowchart of Fig. 48. That is, in ACT101, the processor 21 displays the screen of the touch panel 28 as the statement screen SAe (see Fig. 52).

[0245] FIG. 52 is a display example of the statement screen SAe in the third embodiment. The statement screen SAe differs from the statement screen SAa in the first embodiment in that a software key for a payment cancellation button BAu has been added. If a customer 3 who has moved to the payment device 12 requests a correction to their transaction before completing the payment, the store clerk 2 inputs the payment cancellation button BAu. This correction applies, for example, when there is an error in the quantity of goods or when the discount has not been applied. Alternatively, it applies when the customer 3 cancels the transaction.

[0246] Returning to the explanation of Figure 48. After displaying the statement screen SAe, the processor 21 proceeds to ACT102. The processor 21 checks whether a product code has been entered in ACT102. If a product code has not been entered, the processor 21 proceeds from ACT102 to ACT511. The processor 21 checks whether the payment cancellation button BAu has been entered in ACT511. If the payment cancellation button BAu has not been entered, the processor 21 returns from ACT511 to ACT102. In this way, the processor 21 waits in ACT102 and ACT511 for a product code to be entered or for the payment cancellation button BAu to be entered.

[0247] When a product code is entered in the standby state of ACT102 and ACT511, the processor 21 proceeds from ACT102 to ACT512. In ACT512, the processor 21 erases the payment cancellation button BAu on the statement screen SAe. Thereafter, the processor 21 proceeds to ACT103. The processor 21 then executes the processes of ACT103 to ACT148 described in the first embodiment in the same manner. Therefore, once the product code of the product to be purchased by the customer 3 is entered and the statement record Ra is stored in the first transaction file 631, the payment cancellation button BAu cannot be entered until the first transaction file 631 is cleared.

[0248] On the other hand, if the payment cancellation button baU is pressed in the standby state of ACT102 and ACT511, i.e., in a state where the first transaction file 631 is cleared, the processor 21 proceeds from ACT511 to ACT513. The processor 21 displays the payment device selection screen SAf (see FIG. 53) on the screen of the touch panel 28.

[0249] Figure 53 is an example of the display of the payment device selection screen SAf. The payment device selection screen SAf includes software keys for multiple payment device selection buttons BAv and BAw, each assigned to a payment device 120 in the same group. Incidentally, Figure 53 is an example of the payment device selection screen SAf displayed on the input device 11 (11-1). Since there are two payment devices 120 in the same group for the input device 11 (11-1), payment device 12 (12-1) and payment device 12 (12-2), two payment device selection buttons BAv and BAw are arranged. One payment device selection button BAv is assigned to payment device 12 (12-1), and the other payment device selection button BAw is assigned to payment device 12 (12-2).

[0250] After checking the payment device selection screen SAf, the clerk 2 inputs the payment device selection button BAv or BAw of the payment device 12 with which the customer 3 who requested a transaction correction was attempting to make the payment. For example, if the customer 3 who was attempting to make a payment with the payment device 12 (12-1) requests a transaction correction, the clerk 2 inputs the payment device selection button BAv. For example, if the customer 3 who was attempting to make a payment with the payment device 12 (12-2) requests a transaction correction, the clerk 2 inputs the payment device selection button BAw.

[0251] Returning to the explanation of Figure 48. The processor 21, which has displayed the payment device selection screen SAf, waits for either of the payment device selection buttons BAv, BAw to be input in ACT514. Then, when either of the payment device selection buttons BAv, BAw is input, the processor 21 proceeds from ACT514 to ACT515. The processor 21 acquires a payment device ID, which is identification information of the payment device 12 assigned to the payment device selection button BAv, BAw input in ACT515. For example, when the payment device selection button BAv is input, the processor 21 acquires the ID of the payment device 12 (12-1). For example, when the payment device selection button BAw is input, the processor 21 acquires the ID of the payment device 12 (12-2).

[0252] Next, the processor 21 transmits a payment cancellation event to the payment devices 120 in the same group by multicast communication in ACT 516. The payment cancellation event includes the payment device ID acquired in ACT 515.

[0253] After transmitting the payment cancellation event, the processor 21 proceeds from ACT516 to ACT517. In ACT517, the processor 21 waits for an affirmative response (OK) from any of the payment devices 12. In this waiting state, if the processor 21 does not receive an affirmative response (OK) signal within a certain period of time, the processor 21 proceeds from ACT517 to ACT518. In ACT518, the processor 21 notifies the user that the payment cannot be canceled. For example, the processor 21 notifies the user by displaying text or an image on the touch panel 28 indicating that the payment cannot be canceled. With this, the processor 21 ends the information processing in accordance with the input program.

[0254] In ACT517, if an affirmative response (OK) signal is received within a certain period of time, the processor 21 proceeds to ACT519. In ACT519, the processor 21 copies all detail records Ra stored in the fourth transaction file 632 to the first transaction file 631. Then, in ACT520, the processor 21 clears the fourth transaction file 632. Thereafter, in ACT521, the processor 21 changes the touch panel screen to the second detail screen SAg (see FIG. 54) based on the data of the detail records Ra copied to the first transaction file 631.

[0255] Figure 54 is an example of the display of the second detail screen SAg. Compared to the detail screen SAa (see Figure 52) displayed in ACT101, the second detail screen SAg has the Cancel Payment button BAu changed to the All Cancel button BAx. The Subtotal button BAa has also been changed to the Complete button BAY. Furthermore, the detail area AAb of the second detail screen SAg displays the product name, quantity, discount amount, and amount of the detail record Ra copied to the first transaction file 631, and the total area AAc displays the total points and total amount of the same detail record Ra. The second detail screen SAg also displays the identification name NA of the payment device 12 selected via the payment device selection screen SAf. Incidentally, the second detail screen SAg of Figure 52 shows the case where the payment device 12 (12-1) is selected by inputting the payment device selection button BAv, and the identification name NA is displayed as [Payment Device 1].

[0256] After displaying the second detail screen SAg, the processor 21 proceeds to ACT531 in FIG. 49. In ACT531, the processor 21 checks whether the all cancel button BAx has been pressed. If the all cancel button BAx has not been pressed, the processor 21 proceeds from ACT531 to ACT532. In ACT532, the processor 21 checks whether a product displayed in the detail area AAb of the second detail screen SAg has been selected. If a product has not been selected, the processor 21 returns to ACT531. In this way, the processor 21 waits in ACT531 and ACT532 for the all cancel button BAx to be pressed or a product to be selected.

[0257] If Customer 3 requests to cancel the transaction, Clerk 2 inputs the All Cancellation button BAx. If Customer 3 requests to delete the purchased item or to modify the quantity, unit price, discount amount, or discount rate, Clerk 2 touches the line in Detail Area AAb that displays the product name, etc. of the purchased item.

[0258] When the batch cancel button BAx is pressed in the standby state of ACT531 and ACT532, the processor 21 proceeds from ACT531 to ACT533. In ACT533, the processor 21 transmits a batch cancel event to the payment devices 120 in the same group by multicast communication. The batch cancel event includes the payment device ID acquired in the processing of ACT515.

[0259] After transmitting the batch cancellation command, the processor 21 proceeds to ACT 534. In ACT 534, the processor 21 clears the first transaction file 631. With this, the processor 21 ends the information processing in accordance with the input program.

[0260] In the standby state of ACT531 and ACT532, if it is determined that a product has been selected, the processor 21 proceeds from ACT532 to ACT535. In ACT535, the processor 21 displays a correction screen SAd (see FIG. 40) on the touch panel 28. The correction screen SAd is the same as the correction screen SAd described in the second embodiment. The information processing by the processor 21 in response to the operation input by the store clerk 2 on this correction screen SAd is also the same as in the second embodiment.

[0261] That is, the processor 21, which has displayed the edit screen SAd, waits for the OK button BAt to be pressed in ACT536, or for the cancel button BAs to be pressed in ACT537. If the cancel button BAs is pressed in the standby state of ACT536 and ACT537, the processor 21 proceeds from ACT537 to ACT538. The processor 21 erases the edit screen SAd in ACT538. Thereafter, the processor 21 proceeds to ACT542.

[0262] On the other hand, if the OK button BAt is pressed during the standby state of ACT536 and ACT537, the processor 21 proceeds from ACT536 to ACT539. The processor 21 transmits a correction event to the payment devices 120 in the same group by multicast communication in ACT539. The correction event includes information input to the correction screen SAd. For example, if the Cancel button BAn on the correction screen SAd is pressed, the processor 31 includes information that the selected product is canceled. For example, if the Change Quantity button BAo on the correction screen SAd is pressed and a corrected quantity is also input, the processor 31 includes information that the quantity of the selected product is corrected to the changed quantity. If the Change Unit Price button BAp, Discount button BAq, or Discount button BAr on the correction screen SAd is pressed, the processor 31 also includes information that the unit price, discount amount, or discount rate of the selected product is corrected, as in the case where the Change Quantity button BAo is pressed.

[0263] After transmitting the correction event, the processor 21 proceeds to ACT540. In ACT540, the processor 21 corrects the detail record Ra stored in the first transaction file 631. For example, if the Cancel button BAn on the correction screen SAd is pressed, the processor 31 deletes the detail record Ra of the selected product. For example, if the Change Quantity button BAo on the correction screen SAd is pressed and the corrected quantity is then entered, the processor 31 corrects the quantity and price in the detail record Ra of the selected product. If the Change Unit Price button BAp, the Discount button BAq, or the Discount button BAr on the correction screen SAd is pressed, the processor 21 corrects the unit price, discount amount or discount rate, and price in the detail record Ra of the selected product, just as if the Change Quantity button BAo was pressed. Then, in ACT541, the processor 21 erases the correction screen SAd and updates the second detail screen SAg. Thereafter, the processor 21 proceeds to ACT542.

[0264] In this way, when the correction screen SAd is erased in ACT538 or the second detail screen SAg is updated in ACT541, the processor 21 proceeds to ACT542. The processor 21 checks whether or not a product displayed in the detail area AAb of the second detail screen SAg has been selected in ACT542. If a product has not been selected, the processor 21 proceeds from ACT542 to ACT543. The processor 21 checks whether or not the complete button BAY has been pressed in ACT543. If the complete button BAY has not been pressed, the processor 21 returns from ACT543 to ACT542. In this way, the processor 21 waits in ACT542 and ACT543 for a product to be selected or for the complete button BAY to be pressed.

[0265] If a product is selected in the standby state of ACT542 and ACT543, the processor 21 returns from ACT542 to ACT535. Then, the processor 21 executes the processing of ACT535 to ACT541 in the same manner as described above.

[0266] On the other hand, if the complete button BAy is pressed in the standby state of ACT542 and ACT543, the processor 21 proceeds from ACT543 to ACT544. The processor 21 transmits a correction completion event to the payment devices 120 in the same group by multicast communication in ACT544. The correction completion event includes the payment device ID acquired in ACT515.

[0267] After transmitting the correction completion event, the processor 21 proceeds to ACT545. In ACT545, the processor 21 notifies the customer that the correction of the transaction has been completed. For example, the processor 21 notifies the customer by displaying a message indicating that the correction of the transaction has been completed on the customer display 29. After confirming this notification, the customer 3 goes to the location of the payment device 12 where the payment was suspended and makes the payment.

[0268] After notifying that the transaction correction has been completed, the processor 21 proceeds to ACT 546. In ACT 546, the processor 21 clears the first transaction file 631. With this, the processor 21 ends the information processing in accordance with the input program.

[0269] Here, the processor 21 realizes the function of cancellation detection means 514 by processing ACT511. The processor 21 realizes the function of designation reception means 515 by processing ACT513. The processor 21 realizes the function of fourth notification means 516 by processing ACT515 and ACT516. The processor 21 realizes the function of input side correction means 517 by processing ACT534 and ACT540. The processor 21 realizes the function of third transmission means 518 by processing ACT533 and ACT539. The processor 21 realizes the function of non-notification means 519 by processing ACT518.

[0270] Next, the main steps of the information processing executed by the processor 31 of the payment device 12 in accordance with the payment program will be described using the flowcharts in Figures 50 and 51. The processing steps shown in the flowcharts in Figures 50 and 51 correspond to the processing steps from ACT 229 onwards in Figure 13 in the first embodiment. Therefore, the same reference numerals are used to denote processing steps common to Figure 13.

[0271] After displaying the checkout screen SBb in ACT229, the processor 31 waits for payment to be completed in ACT230. In this standby state, the processor 31 checks whether a payment cancellation event has been received in ACT601. If payment is completed without receiving a payment cancellation event, the processor 31 executes the processing in ACT231 to ACT234 in the same manner as described above, and ends information processing in accordance with the payment program.

[0272] On the other hand, if a payment cancellation event is received before payment is completed, the processor 31 proceeds from ACT601 to ACT602. In ACT602, the processor 31 checks whether the payment device ID included in the payment cancellation event matches the ID of its own payment device 12. If the IDs do not match, the processor 31 returns from ACT602 to ACT230. That is, the processor 31 discards the payment cancellation event and waits again for payment to be completed or for the processor 31 to receive a payment cancellation event.

[0273] On the other hand, if the IDs match, the processor 31 proceeds from ACT602 to ACT603. In ACT603, the processor 31 sends an affirmative response (OK) signal to the input device 11 that sent the payment cancellation event. In ACT604, the processor 31 copies all detail records Ra stored in the third transaction file 812 to the second transaction file 811. Then, in ACT605, the processor 31 clears the third transaction file 812.

[0274] Thereafter, in ACT606, the processor 31 checks whether or not a batch cancel event has been received. If a batch cancel event has not been received, the processor 31 proceeds from ACT606 to ACT607. In ACT607, the processor 31 checks whether or not a modification event has been received. If a modification event has not been received, the processor 31 proceeds from ACT607 to ACT608 in Figure 51. In ACT608, the processor 31 checks whether or not a modification completion event has been received. If a modification completion event has not been received, the processor 31 returns to ACT606 in Figure 50. In this way, in ACT606 to ACT608, the processor 31 waits to receive a batch cancel event, a modification event, or a modification completion event.

[0275] If a bulk cancellation event is received in the standby state of ACT606 to ACT608, the processor 31 proceeds from ACT606 to ACT609. The processor 31 checks whether the payment apparatus ID included in the bulk cancellation event in ACT609 matches the ID of its own payment apparatus 12. If the IDs do not match, the processor 31 returns to the standby state of ACT606 to ACT608. That is, the processor 31 discards the bulk cancellation event and returns to the standby state for a bulk cancellation event, a modification event, and a modification completion event.

[0276] On the other hand, if the IDs match, the processor 31 proceeds from ACT 609 to ACT 610. In ACT 610, the processor 31 clears the second transaction file 811. With this, the processor 31 ends the information processing in accordance with the payment program.

[0277] If a modification event is received in the standby state of ACT606 to ACT608, the processor 31 proceeds from ACT607 to ACT611. The processor 31 checks whether the payment apparatus ID included in the modification event in ACT611 matches the ID of its own payment apparatus 12. If the IDs do not match, the processor 31 returns to the standby state of ACT606 to ACT608. That is, the processor 31 discards the modification event and returns to the standby state for a batch cancellation event, a modification event, and a modification completion event.

[0278] On the other hand, if the IDs match, the processor 31 proceeds from ACT611 to ACT612. The processor 31 modifies the data of the detail record Ra stored in the second transaction file 811 in ACT612 based on the information included in the modification event. This modification is similar to the processing of ACT402 described in the second embodiment, so a detailed description will be omitted here. After the processor 31 has finished modifying the detail record Ra, it returns to ACT606 and once again waits for the batch cancellation event, modification event, and modification completion event.

[0279] When a correction completion event is received in the standby state of ACT606 to ACT608, the processor 31 proceeds from ACT608 to ACT613 in Figure 51. The processor 31 checks whether the payment apparatus ID included in the correction completion event in ACT613 matches the ID of its own payment apparatus 12. If the IDs do not match, the processor 31 returns to the standby state of ACT606 to ACT608. That is, the processor 31 discards the correction completion event and returns to the standby state for a batch cancellation event, a correction event, and a correction completion event.

[0280] On the other hand, if the IDs match, the processor 31 proceeds from ACT 613 to ACT 227. Then, the processor 31 executes the processes of ACT 227 to ACT 234 in the same manner as in the first embodiment, and ends the information processing according to the payment program.

[0281] Here, the processor 31, by processing ACT601 to ACT603, realizes the function of the cancellation response means 77. The processor 31, by processing ACT610 and ACT612, realizes the function of the settlement side correction means 78.

[0282] In this way, the third embodiment also provides an accounting system 1 in which the clerk 2 and the customer 3 share the operations to settle a transaction, without the input device 11 generating and transmitting payment information including details of the purchased and sold items and total information to the payment device 12. Moreover, with the accounting system 1 of the third embodiment, after an input completion instruction is given by pressing the input completion button BAj, the transaction for which the input completion instruction was given can be reversed and corrected.

[0283] [Fourth embodiment] Next, a fourth embodiment will be described with reference to FIGS. The fourth embodiment adds gift certificates as a payment method to the accounting system 1 of the first embodiment. Therefore, parts that are common to the first embodiment are given the same reference numerals and detailed explanations will be omitted.

[0284] A gift certificate is an example of a gift certificate product. In this embodiment, there are two types of gift certificates: one with a face value of 500 yen and one with a face value of 1000 yen. Each gift certificate is assigned a unique gift certificate code, just like the product, and a barcode representing the gift certificate code is printed on it. Data records of gift certificates created in the same format as the product records are stored in the product master file 131. The data records of gift certificates describe the gift certificate code as the product code, the gift certificate name as the product name, and the face value as the unit price.

[0285] 55 is a block diagram showing the main functional configuration of the processor 21 of the input device 11. The processor 21 has the functions of input side identification means 520 and calculation means 521 in addition to input side storage means 51, detail display means 52, completion detection means 53, first transmission means 54, selection means 55, first notification means 56, second notification means 57, third notification means 58, payment destination notification means 59, and input side deletion means 510.

[0286] The input-side identification means 520 has a function of identifying whether transaction-related data input via the input device 61 is data related to a transaction of a gift certificate product or data related to a transaction of a product other than a gift certificate product. As described above, a barcode representing a gift certificate code is printed on a gift certificate. By scanning this barcode with the scanner 27 of the input device 61, the gift certificate code is input as transaction-related data. When the transaction-related data is a gift certificate code, the input-side identification means 520 identifies the transaction-related data as data related to a transaction of a gift certificate product. When the transaction-related data is a product code, the input-side identification means 520 identifies the transaction-related data as data related to a transaction of a product other than a gift certificate product.

[0287] When the input-side storage means 51 receives transaction data, it creates a detail record Rb for the product or gift certificate to be sold as one transaction based on the received data. As shown in FIG. 56, the detail record Rb is a record that describes data items such as the gift certificate code, gift certificate name, face value, quantity, amount, and gift certificate flag Fe in association with a series of record numbers. The gift certificate flag Fe is a value that identifies whether the record is a detail record Rb for a gift certificate or a detail record Rb for a product other than a gift certificate. In this embodiment, the value of the gift certificate flag Fe is set to "1" to indicate that the record is a detail record Rb for a gift certificate, and the value of the gift certificate flag Fe is set to "0" to indicate that the record is a detail record Rb for a product other than a gift certificate. When the input-side identification means 520 identifies the transaction data input via the input device 61 as data for a gift certificate transaction, the input-side storage means 51 creates a detail record Rb with the value of the gift certificate flag Fe set to "1," i.e., a detail record Rb for a gift certificate. When the input-side identification means 520 identifies data relating to a transaction input via the input device 61 as data relating to a transaction of a product other than a gift certificate, the input-side storage means 51 creates a detail record Rb with the value of the gift certificate flag Fe set to "0," i.e., a detail record Rb for a product other than a gift certificate. The input-side storage means 51 stores the detail record Rb for the gift certificate or product other than a gift certificate in the first transaction file 631 of the input-side storage unit 63.

[0288] The calculation means 521 has a function of calculating the total amount of the transaction by treating the sales amount of the product as a positive value for data relating to transactions of products other than gift certificates among the data relating to transactions stored in the first transaction file 631 of the input-side storage unit 63, and by treating the face value of the gift certificate as a negative value for data relating to gift certificates. The calculation means 522 displays the calculated total amount on the display device 62.

[0289] 57 is a block diagram showing the main functional configuration of the processor 31 of the payment device 12. The processor 31 has the functions of a payment side storage means 71, an amount display means 72, a payment response means 73, a payment means 74, and a payment side deletion means 75, as well as a payment side identification means 79 and a receipt output means 710.

[0290] The settlement side identification means 79 has a function of identifying whether the transaction data stored in the settlement side memory unit 81 is data related to a transaction of a gift certificate product or data related to a transaction of a product other than a gift certificate product. Similar to the input side identification means 520, when the transaction data is a gift certificate code, the settlement side identification means 79 identifies the transaction data as data related to a transaction of a gift certificate product. When the transaction data is a product code, the settlement side identification means 79 identifies the transaction data as data related to a transaction of a product other than a gift certificate product.

[0291] The second transaction file 811 of the settlement-side memory unit 81 stores a detail record created by the settlement-side memory means 71. This detail record has the same format as the detail record Rb created by the input-side memory means 51 and stored in the first transaction file 631 of the input-side memory unit 63. When the settlement-side identification means 79 identifies transaction-related data transmitted from the input device 11 and received via the communication unit 35 as data related to a transaction of a gift certificate product, the settlement-side memory means 71 creates a detail record Rb with the value of the gift certificate flag Fe set to "1," i.e., a detail record Rb for a gift certificate. When the settlement-side identification means 79 identifies transaction-related data transmitted from the input device 11 and received via the communication unit 35 as data related to a transaction of a product other than a gift certificate product, the settlement-side memory means 71 creates a detail record Rb with the value of the gift certificate flag Fe set to "0," i.e., a detail record Rb for a product other than a gift certificate. The settlement side storage means 71 stores the detail record Rb of the gift certificate or the product other than the gift certificate in the second transaction file 811 of the settlement side storage unit 81.

[0292] The receipt output means 710 has a function of outputting a receipt indicating the face value of the gift certificate product separately from the total amount of the sales amount of products other than the gift certificate product, as a receipt for the transaction settled by the settlement means 74. The receipt may be output by printing on a paper medium, or may be output as an electronic receipt to an information terminal such as a smartphone.

[0293] Next, the content and procedures of the information processing executed by the input device 11 and payment device 12 constituting the accounting system 1, which are related to the fourth embodiment, will be explained using the flowcharts in Figures 58 to 61, the example screens in Figures 62 and 63, and the example receipt in Figure 64. Note that the content and procedures of the information processing explained below are merely examples. The content and procedures can be changed as appropriate as long as similar effects can be achieved. The example screens and example receipts are also merely examples. The content of the output text, the arrangement of images, the type and layout of software keys, etc. can be changed as appropriate.

[0294] First, the main steps of the information processing executed by the processor 21 of the input device 11 according to the input program will be described using the flowcharts in Figures 58 and 59. The flowchart in Figure 47 corresponds to the flowchart in Figure 11 in the first embodiment. Therefore, the same reference numerals are used to designate the same processing steps as in Figure 11. Figure 58 corresponds to the flowchart in Figure 9 in the first embodiment. Furthermore, Figure 59 corresponds to the flowchart in Figure 10 in the first embodiment. Therefore, the same reference numerals are used to designate the same processing steps as in Figures 9 and 10.

[0295] 58, the processor 21, which has set the screen of the touch panel 28 to the details screen SAa, waits for the input of a product code in ACT102 or ACT107. In this standby state, when the product code of the purchased product is input, the processor 21 executes the processes of ACT103 and ACT104, similar to the first embodiment.

[0296] That is, processor 21 transmits an input event to payment devices 120 in the same group by multicast communication as ACT103. The input event includes a product code input from scanner 27 or touch panel 28. Processor 21 also creates a detail record Rb as ACT104. Processor 21 accesses server 13 and acquires a product record including the input product code from product master file 131. Then, based on product information such as product name and unit price described in the product record, processor 21 creates a detail record Rb consisting of item data such as record number r, product code, product name, unit price, quantity, and amount.

[0297] On the other hand, when a gift certificate code for a gift certificate is input during the standby state of ACT102 or ACT107, the processor 21 also executes the processing of ACT103 and ACT104. That is, the processor 21 transmits an input event to the settlement devices 120 in the same group by multicast communication in ACT103. The input event includes the gift certificate code. The processor 21 also creates a detail record Rb in ACT104. The processor 21 accesses the server 13 and acquires a data record including the input gift certificate code from the product master file 131. Then, based on information such as the gift certificate name and face value described in the data record, the processor 21 creates a detail record Rb consisting of item data such as a record number r, product code, product name, unit price, quantity, and amount. The product code in the detail record Rb is the gift certificate code. The product name is the gift certificate name. The unit price is the face value. The quantity is "1". The amount is the unit price multiplied by the quantity.

[0298] After completing the processing of ACT104, the processor 21 proceeds to ACT701. In ACT701, the processor 21 identifies whether the detail record Rb is a detail record of a product or a detail record of a gift certificate. If the product code included in the detail record Rb is a gift certificate code, the processor 21 recognizes it as a detail record Rb of a gift certificate. If the product code included in the detail record Rb is a code other than a gift certificate code, the processor 21 recognizes it as a detail record Rb of a product other than a gift certificate.

[0299] If detail record Rb is a detail record for a product other than a gift certificate, the processor 21 proceeds from ACT 701 to ACT 702. In ACT 702, the processor 21 sets the gift certificate flag Fe of detail record Rb to "0."

[0300] On the other hand, if detail record Rb is a detail record for a gift certificate, the processor 21 proceeds from ACT701 to ACT703. In ACT703, the processor 21 sets the gift certificate flag Fe of detail record Rb to "1." In ACT704, the processor 21 also adds a minus sign to the amount in detail record Rb.

[0301] After completing the processing of ACT702 or ACT704, the processor 21 proceeds to ACT105. Then, the processor 21 executes the processing of ACT105 to ACT112 in the same manner as in the first embodiment. That is, the processor 21 stores the detail record Ra in the first transaction file 631. Then, the processor 21 updates the detail screen SAa.

[0302] 62 shows the details screen SAa that appears after the barcode of a gift certificate with a face value of 1,000 yen is scanned by the scanner 27. As shown in the figure, the name, quantity, and face value of the gift certificate are displayed in the current area AAa. The face value is marked with a minus sign.

[0303] After completing the processing of ACT 106, the processor 21 enters a standby state for ACT 107 to ACT 109. In this standby state, when the barcode of the product or gift certificate is scanned, the processor 21 executes the processing of ACT 103 and ACT 104, ACT 701 to ACT 704, and further ACT 105 and ACT 106 in the same manner as described above.

[0304] When the subtotal button BAa is pressed in the standby state of ACT107 to ACT109, the processor 21 proceeds from ACT109 to ACT711 in FIG. 59. In ACT711, the processor 21 calculates the total amount and checks whether it is a positive value. The total amount is the sum of the amounts in all detail records Rb stored in the first transaction file 631. The amounts in the detail records Rb for merchandise are positive values, but the amounts in the detail records Rb for gift certificates are set to negative values ​​in the processing of ACT704. Therefore, the total amount is not necessarily a positive amount, and may be 0 yen or a negative amount.

[0305] If the total amount is a positive amount, payment is required. In this case, the processor 21 proceeds from ACT 711 to ACT 121. The processor 21 then executes the processes of ACT 121 to ACT 151 in the same manner as in the first embodiment.

[0306] On the other hand, if the total amount is 0 yen or a negative amount, the payment has been completed using the gift certificate. In this case, the processor 21 proceeds from ACT 711 to ACT 712. In ACT 712, the processor 31 displays the payment completion screen SAh (see FIG. 63) on the screen of the touch panel 28.

[0307] Figure 63 is an example of the display of the payment completion screen SAh. The payment completion screen SAh is a screen that is the payment screen SAc without the software keys for the subtotal discount button BAh and subtotal discount button BAi. As shown in the detail screen SAa of Figure 62, the payment completion screen SAh is displayed when customer 3 purchases four items totaling 1,000 yen and presents a gift certificate with a face value of 1,000 yen. In this case, the total amount is 0 yen, so no payment is made. However, since a receipt is issued from the payment device 12, the store clerk 2 presses the input completion button BAj alone. Alternatively, the store clerk 2 presses the busy button BAk and the input completion button BAj.

[0308] After displaying the payment completion screen SAh, the processor 21 proceeds to ACT125. Then, the processor 21 executes the processes of ACT125 to ACT151 in the same manner as in the first embodiment. Therefore, when the store clerk 2 presses the input completion button BAj alone, the processor 21 transmits a completion event to the parent device 121. When the store clerk 2 presses the busy button BAk and the input completion button BAj, the processor 21 transmits a completion event to the child device 1221.

[0309] Here, the processor 21 realizes the function of the input side identification means 520 by the processing of ACT701. Also, the processor 21 realizes the function of the calculation means 521 by the processing of ACT711.

[0310] Next, the main steps of the information processing executed by the processor 31 of the payment device 12 in accordance with the payment program will be described using the flowcharts in Figures 60 and 61. The processing steps shown in the flowchart in Figure 60 correspond to the flowchart in Figure 12 in the first embodiment. Therefore, the same reference numerals are used to designate the same processing steps as in Figure 12. The processing steps shown in the flowchart in Figure 61 correspond to the flowchart in Figure 13 in the first embodiment. Therefore, the same reference numerals are used to designate the same processing steps as in Figure 13.

[0311] As explained using Figure 58, an input event including a product code or a gift certificate code is transmitted from the input device 11 to the payment device 12. When the processor 31 of the payment device 12 receives an input event including a product code or a gift certificate code from the input device 11 in ACT203 of Figure 60, the processor 31 proceeds from ACT203 to ACT204. The processor 31 creates a detail record Rb in ACT204.

[0312] That is, when an input event including a product code is received, the processor 31 accesses the server 13 and acquires a product record including the product code from the product master file 131. Then, based on the product information such as the product name and unit price described in the product record, the processor 31 creates a detail record Rb consisting of item data such as the record number r, product code, product name, unit price, quantity, and amount.

[0313] On the other hand, when an input event including a gift certificate code is received, processor 31 also accesses server 13 and retrieves a data record including the gift certificate code from product master file 131. Then, based on information such as the gift certificate name and face value described in the data record, processor 31 creates a detail record Rb consisting of item data such as record number r, product code (gift certificate code), product name (gift certificate name), unit price (face value), quantity, and amount.

[0314] After completing the processing of ACT204, the processor 31 proceeds to ACT801. In ACT801, the processor 31 identifies whether the detail record Rb is a detail record of a product or a detail record of a gift certificate. If the product code included in the detail record Rb is a gift certificate code, the processor 31 recognizes it as a detail record Rb of a gift certificate. If the product code included in the detail record Rb is a code other than a gift certificate code, the processor 31 recognizes it as a detail record Rb of a product other than a gift certificate.

[0315] If the detail record Rb is a detail record of a product, the processor 31 proceeds from ACT801 to ACT802. In ACT802, the processor 31 sets the gift certificate flag Fe of the detail record Rb to "0".

[0316] On the other hand, if detail record Rb is a detail record for a gift certificate, processor 31 proceeds from ACT801 to ACT803. In ACT803, processor 31 sets the gift certificate flag Fe of detail record Rb to "1." In ACT804, processor 31 also adds a minus sign to the amount in detail record Rb.

[0317] After completing the processing of ACT802 or ACT804, the processor 31 proceeds to ACT205. In ACT205, the processor 31 stores the detail record Ra in the second transaction file 811. The processor 31 then enters a standby state for ACT208 to ACT210.

[0318] In the standby state of ACT208 to ACT210, when an input event including a product code or gift certificate code is received again, processor 31 executes the processing from ACT203 onwards in the same manner as described above. That is, when an input event including a product code is received, processor 31 creates a detail record Rb in which the gift certificate flag Fe is set to "0" and stores this detail record Rb in the second transaction file 811. When an input event including a gift certificate code is received, processor 31 creates a detail record Rb in which the gift certificate flag Fe is set to "1" and stores this detail record Rb in the second transaction file 811.

[0319] On the other hand, if a completion event is received in the standby state of ACT208 to ACT210, the processor 31 proceeds from ACT209 to ACT221 in Fig. 61. In ACT221, the processor 31 checks the status flag Fc in the flag memory 82. If the status flag Fc is "1", that is, if the payment device 12 is in the middle of a payment, the processor 31 proceeds from ACT221 to ACT235. In ACT235, the processor 31 controls the communication unit 35 to send a negative response (NG) to the input device 11. Thereafter, the processor 21 returns to the standby state of ACT208 to ACT210.

[0320] On the other hand, if the status flag Fc is "0", that is, if the payment device 12 is in a standby state and receives a completion event, the processor 21 proceeds from ACT221 to ACT811. In ACT811, the processor 21 calculates the total amount and checks whether it is a positive value. The total amount is the sum of the amounts in all detail records Rb stored in the second transaction file 811. The amounts in the detail records Rb for merchandise are positive values, but the amounts in the detail records Rb for gift certificates are negative values. Therefore, the total amount is not necessarily a positive amount, and may be 0 yen or a negative amount.

[0321] If the total amount is a positive amount, the processor 31 proceeds from ACT 811 to ACT 222. The processor 31 then executes the processing of ACT 222 to ACT 234 in the same manner as described above.

[0322] On the other hand, if the total amount is 0 or a negative amount, the processor 31 proceeds from ACT811 to ACT231. That is, the processing of ACT222 to ACT230 is skipped. Therefore, the customer 3 does not pay the price. The processor 21 then executes the processing of ACT231 to ACT234 in the same manner as described above. Therefore, a receipt RS (see Figure 64) is issued, and the customer 3 receives the receipt RS.

[0323] Figure 64 is an example of a receipt RS issued to a customer who presents a gift certificate with a face value of 1,000 yen for a purchase totaling 1,000 yen. As shown in Figure 64, the receipt RS lists the details of the four purchased items, followed by the total amount of 1,000 yen, and then the face value of the gift certificate, 1,000 yen, printed with a minus sign. Customer 3 can confirm from this receipt RS that he or she paid for the purchased items with the gift certificate.

[0324] Here, the processor 31 performs the processing of ACT801 to realize the function of the settlement side identification means 79. The processor 31 performs the processing of ACT231 to realize the function of the receipt output means 710.

[0325] In this way, even in the fourth embodiment, it is possible to provide an accounting system 1 in which the clerk 2 and the customer 3 share the operations to settle a transaction, without the input device 11 generating and transmitting payment information including detailed information and total information for the purchased and sold products to the payment device 12. Moreover, according to the fourth embodiment, it is possible to provide an accounting system 1 that is also compatible with gift certificates and other cash vouchers that require the intervention of a clerk as a payment method.

[0326] [Other embodiments] In the above embodiment, the case where the store clerk 2 selects and inputs the payment method by operating the input device 11 is exemplified. In another embodiment, the customer 3 may select and input the payment method by operating the payment device 12, as in existing accounting systems.

[0327] In addition, in the above embodiment, an example was given in which the input device 11 issues a transaction number and transmits it to the payment device 3 together with the completion event. In another embodiment, the payment device 3 that receives the completion event may issue the transaction number. In this case, for multiple payment devices 12 placed in the same checkout lane, it is advisable to, for example, assign different values ​​to the most significant digits of the transaction numbers so that the transaction numbers issued by each payment device 12 do not overlap.

[0328] In the input device 11, examples of means for instructing input completion are when the input completion button BAj is pressed alone and when the busy button BAk and the input completion button BAj are pressed. In another embodiment, when the input completion button BAj is pressed alone, a completion event may be sent to the parent device 121, and when the busy button BAk is pressed alone, a completion event may be sent to the child device 122. Alternatively, the busy button BAk may be eliminated and only the input completion button BAj may be used, and a completion event may be sent to one of the payment devices 12.

[0329] For example, assume that there are three payment devices 12: No. 1 12-1, No. 2 12-2, and No. 3 12-3. Each time the input completion button BAj is pressed, the input device 11 sends a completion event to No. 1 12-1, No. 2 12-2, and No. 3 12-3 in that order. If a negative response (NG) is received from a payment device 12, the input device 11 sends the completion event to the next payment device 12. Even with a checkout system configured in this way, a store clerk and a customer can share the operations to settle a transaction without generating payment information on the input device.

[0330] Also, for example, assume that the first payment device 12-1 and the second payment device 12-2 are connected to a cashless payment terminal 5, but the third payment device 12-3 is not connected to a cashless payment terminal 5. In this case, if a customer 3 requests cash payment, the input device 11 transmits a completion event to the first payment device 12-1, the second payment device 12-2, and the third payment device 12-3 in that order. If a customer requests cashless payment, the input device 11 transmits a completion event to the first payment device 12-1 and the second payment device 12-2 in that order, but does not transmit a completion event to the third payment device 12-3. This configuration can be realized by the input device 11 storing the connection flag Fb of each payment device 12. Even with this configuration, the store clerk 2 will not guide a customer 3 who requests cashless payment to the third payment device 12-3. Furthermore, this is efficient because the third payment device 12-3 will not return a negative response (NG) to a completion event that includes an identification code for the cashless payment method.

[0331] In the fourth embodiment, if the total amount is negative, the settlement device 12 may pay the negative amount as change from an automatic change dispenser. This makes it possible to deal with gift certificates for which change can be paid out.

[0332] 1 illustrates a checkout system 1 in which two payment devices 12 are provided for one checkout lane. However, the checkout system 1 is not limited to this. For example, the above-described embodiments can be applied to a checkout system in which three or more payment devices 12 are provided for one checkout lane.

[0333] Although several embodiments have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the inventions and their equivalents as defined in the claims. The inventions described in the original claims of this application are set forth below. [1] An input device for inputting transaction data via an input device is connected to a plurality of settlement devices for settling the transaction via a communication line, and the input device comprises: end detection means for detecting an instruction to end input of transaction data; first transmission means for transmitting the transaction data input via the input device to each of the plurality of settlement devices before the end detection means detects the instruction to end input of the transaction data; input side correction means for correcting the transaction data transmitted to each of the plurality of settlement devices by the first transmission means before the end detection means detects the instruction to end input of the transaction data; and and a first notification means, when an instruction to end input of transaction data is detected by the end detection means, notifying one of the plurality of payment devices of the end of input, wherein the payment device comprises: a settlement-side storage means, which stores the transaction data transmitted from the input device by the first transmission means in a settlement-side storage unit until the transaction is settled; a settlement-side correction means, which corrects the transaction data stored in the settlement-side storage unit with the corrected transaction data transmitted from the input device by the second transmission means; and a settlement means, when notified of the end of input from the input device when payment is possible, which settles the transaction based on the transaction data stored in the settlement-side storage unit. [2] The input device further comprises an input side memory means for storing transaction data input via the input device in an input side memory unit, a detail display means for displaying transaction detail information based on the transaction data stored in the input side memory unit, and a correction accepting means for accepting corrections to the detail information displayed by the detail display means, and the input side correction means corrects the transaction data stored in the input side memory unit using the detail information for which corrections have been accepted by the correction accepting means, in the accounting system described in appendix [1]. [3] The accounting system described in appendix [2], wherein the settlement device further comprises a settlement response means for responding to the input device whether or not the transaction can be settled when the input device notifies the input device that the input has ended, and the input device further comprises an input side deletion means for deleting the data relating to the transaction stored in the input side memory unit when the input device receives a response that the transaction can be settled from the settlement device that notified the input that the input has ended. [4] The accounting system described in appendix [3], wherein the input device further comprises a second notification means for notifying other payment devices that have not notified the completion of input of the completion of input when the input device receives a response from the payment device that has not notified the completion of input that payment is not possible. [5] The accounting system described in Appendix [3], wherein the input device further comprises a third notification means for notifying other payment devices that have not notified the completion of input of the completion of payment when it receives a response that payment is possible from the payment device that notified the completion of input, and the payment device further comprises a payment side deletion means for deleting data related to the transaction stored in the payment side memory unit when it receives the notification of the completion of payment from the input device. [6] The accounting system described in appendix [1], wherein the input device further comprises a selection means for accepting a selection input of a payment method required for settling the transaction, and the first notification means of the input device notifies one of the payment devices of completion of input together with payment method identification data that identifies the payment method selected and accepted by the selection means, and the payment means of the payment device settles the transaction using the payment method identified by the payment method identification data received along with the notification of completion of input. [7] An accounting system described in any one of appendices [1] to [6], wherein the first transmission means of the input device transmits the input transaction data to each of the plurality of payment devices each time the transaction data is input via the input device, and the second transmission means of the input device transmits the corrected transaction data to each of the plurality of payment devices each time the transaction data is corrected by the input side correction means. [8] An input device comprising: an input device for inputting transaction data; a communication device for communicating data with multiple payment devices that settle the transaction; end detection means for detecting an instruction to end input of transaction data; first transmission means for transmitting the transaction data inputted via the input device to each of the multiple payment devices before the end detection means detects an instruction to end input of the transaction data; input side correction means for correcting the transaction data transmitted to each of the multiple payment devices by the first transmission means before the end detection means detects an instruction to end input of the transaction data; second transmission means for transmitting the transaction data corrected by the input side correction means to each of the multiple payment devices before the end detection means detects an instruction to end input of the transaction data; and first notification means for notifying one of the multiple payment devices of the end of input when the end detection means detects an instruction to end input of the transaction data. [9] A payment device comprising: a communication device that performs data communication with an input device, the communication device comprising: a first transmission means that transmits transaction-related data input via an input device to each of a plurality of payment devices before an instruction to end input of the transaction-related data is detected; and a second transmission means that modifies the transaction-related data transmitted to each of the plurality of payment devices before the instruction to end input of the transaction-related data is detected, and transmits modified transaction-related data to each of the plurality of payment devices before the instruction to end input is detected; a payment side memory means that stores the transaction-related data transmitted from the input device by the first transmission means in a payment side memory unit until the transaction is settled; a payment side correction means that corrects the transaction-related data stored in the payment side memory unit with the transaction-related data transmitted from the input device by the second transmission means; and a payment means that, when receiving a notification of input end indicating that the instruction to end input has been detected from the input device when payment is possible, settles the transaction based on the transaction-related data stored in the payment side memory unit.

[10] A program for causing an input device computer equipped with an input device for inputting transaction data and a communication device for data communication with multiple payment devices that settle the transaction to function as: an end detection means for detecting an instruction to end input of transaction data; a first transmission means for transmitting the transaction data inputted via the input device to each of the multiple payment devices before the end detection means detects an instruction to end input of the transaction data; an input side correction means for correcting the transaction data transmitted to each of the multiple payment devices by the first transmission means before the end detection means detects an instruction to end input of the transaction data; a second transmission means for transmitting the transaction data corrected by the input side correction means to each of the multiple payment devices before the end detection means detects an instruction to end input of the transaction data; and a first notification means for notifying one of the multiple payment devices of the end of input when the end detection means detects an instruction to end input of the transaction data.

[11] A program for causing a computer of a payment apparatus equipped with a communication device that performs data communication with an input device having a first transmission means that transmits transaction-related data input via an input device to each of a plurality of payment devices before an instruction to end input of the transaction-related data is detected, and a second transmission means that modifies the transaction-related data transmitted to each of the plurality of payment devices before an instruction to end input of the transaction-related data is detected, and transmits modified transaction-related data to each of the plurality of payment devices before the instruction to end input is detected, to function as: a payment-side memory means that stores the transaction-related data transmitted from the input device by the first transmission means in a payment-side memory unit until the transaction is settled; a payment-side correction means that corrects the transaction-related data stored in the payment-side memory unit with the transaction-related data transmitted from the input device by the second transmission means; and a payment means that settles a transaction based on the transaction-related data stored in the payment-side memory unit when it receives a notification of input end, indicating that the instruction to end input has been detected from the input device when payment is possible. [Explanation of symbols]

[0334] 1...accounting system, 2...store clerk, 3...customer, 5...cashless payment terminal, 11...input device, 12...payment device, 13...server, 14...network, 21, 31...processor, 51...input side storage means, 52...detail display means, 53...end detection means, 54...first transmission means, 55...selection means, 56...first notification means, 57...second notification means, 58...third notification means, 59...payment destination notification means, 63...input side storage unit, 64...data table, 71...payment side storage means, 72...amount display means, 73...payment response means, 74...payment means, 75...payment side deletion means, 76...payment side modification correction means, 77...cancellation response means, 78...payment side correction means, 79...payment side identification means, 82...flag memory, 510...input side deletion means, 511...correction acceptance means, 512...input side correction means, 513...second transmission means, 514...cancellation detection means, 515...designation acceptance means, 516...fourth notification means, 517...input side correction means, 518...third transmission means, 519...non-notification means, 520...input side identification means, 521...calculation means, 631...first transaction file, 632...fourth transaction file, 710...receipt output means, 811...second transaction file, 812...third transaction file.

Claims

1. An input device for inputting data relating to a transaction via an input device is connected to a plurality of settlement devices for settling the transaction via a communication line; The input device is an end detection means for detecting that an instruction to end input of data relating to a transaction has been given to the input device via the input device; a first transmitting means for transmitting data relating to the transaction input via the input device to each of the plurality of payment devices before an instruction to end input of the data relating to the transaction is detected by the end detecting means; an input side correcting means for correcting the transaction data transmitted by the first transmitting means to each of the plurality of settlement devices before the completion detecting means detects an instruction to complete input of the transaction data; a second transmitting means for transmitting the transaction data corrected by the input correcting means to each of the plurality of settlement devices before the input end instruction is detected by the end detecting means; a first notification means for notifying one of the plurality of payment devices of the completion of input when the completion detection means detects an instruction to complete input of data related to the transaction; Equipped with The payment device a settlement-side storage means for storing data relating to the transaction transmitted from the input device by the first transmission means in a settlement-side storage unit until the transaction is settled; a settlement side correcting means for correcting the transaction data stored in the settlement side memory unit using the corrected transaction data transmitted from the input device by the second transmitting means; a settlement means for settling the transaction based on the transaction data stored in the settlement-side storage unit when a notification of the completion of input is received from the input device while the transaction is ready for settlement; An accounting system that includes:

2. The input device is an input-side storage means for storing transaction-related data input via the input device in an input-side storage unit; a statement display means for displaying statement information of a transaction based on the data relating to the transaction stored in the input side storage unit; a correction accepting means for accepting corrections to the detailed information displayed by the detailed display means; Further comprising: the input-side correcting means corrects the transaction-related data stored in the input-side storage unit using the detail information for which corrections have been accepted by the correction accepting means; The accounting system of claim 1.

3. Of the plurality of payment devices, the payment device to which the input completion has been notified by the first notification means is a settlement response means for responding to the input device as to whether or not the transaction can be settled by the settlement means; Further comprising: The input device is an input-side deletion means for deleting the data relating to the transaction stored in the input-side storage unit when receiving a response indicating that the settlement is possible from the settlement device that has been notified of the completion of the input by the first notification means; 3. The accounting system of claim 2, further comprising:

4. The input device is a second notification means for, when receiving a response indicating that payment is impossible from the payment device that has been notified of the completion of input by the first notification means, notifying other payment devices that have not been notified of the completion of input by the first notification means of the completion of input; 4. The accounting system of claim 3, further comprising:

5. The input device is a third notification means for notifying the other payment devices that have not notified the completion of input of the completion of payment when receiving a response indicating that payment is possible from the payment device that has not notified the completion of input; Further comprising: The payment device a settlement-side deletion means for deleting the data relating to the transaction stored in the settlement-side storage unit upon receiving a notification of the completion of the settlement from the input device; 4. The accounting system of claim 3, further comprising:

6. The input device is Further comprising a selection means for accepting a selection input of a payment method required for settlement of the transaction, The first notification means of the input device notifying one of the settlement devices of the completion of input together with payment method identification data identifying the payment method selected and input by the selection means; The payment means of the payment device settling the transaction using the payment method identified by the payment method identification data received together with the notification of completion of input; The accounting system of claim 1.

7. The first transmitting means of the input device Each time transaction data is input via the input device, the input transaction data is transmitted to each of the plurality of settlement devices; The second transmitting means of the input device each time the input side correcting means corrects the transaction data, the corrected transaction data is transmitted to each of the plurality of settlement devices; 7. An accounting system according to any one of claims 1 to 6.

8. an input device for inputting data relating to a transaction; a communication device for communicating data with a plurality of payment devices that settle transactions; an end detection means for detecting that an instruction to end input of data relating to a transaction has been given via the input device; a first transmitting means for transmitting data relating to the transaction input via the input device to each of the plurality of payment devices before an instruction to end input of the data relating to the transaction is detected by the end detecting means; an input side correcting means for correcting the transaction data transmitted by the first transmitting means to each of the plurality of settlement devices before the completion detecting means detects an instruction to complete input of the transaction data; a second transmitting means for transmitting the transaction data corrected by the input side correcting means to each of the plurality of settlement devices before the completion detecting means detects an instruction to complete input of the transaction data; a first notification means for notifying one of the plurality of payment devices of the completion of input when the completion detection means detects an instruction to complete input of data related to the transaction; An input device comprising:

9. a communication device that performs data communication with an input device, the communication device including: a first transmission means that transmits transaction-related data input via an input device to each of a plurality of settlement devices before an instruction to end input of the transaction-related data is detected; and a second transmission means that modifies the transaction-related data transmitted to each of the plurality of settlement devices before the instruction to end input of the transaction-related data is detected, and transmits modified transaction-related data to each of the plurality of settlement devices before the instruction to end input is detected; a settlement-side storage means for storing data relating to the transaction transmitted from the input device by the first transmission means in a settlement-side storage unit until the transaction is settled; a settlement side correcting means for correcting the transaction data stored in the settlement side memory unit using the transaction data transmitted from the input device by the second transmitting means; a settlement means for settling a transaction based on the data relating to the transaction stored in the settlement-side storage unit when receiving a notice of input completion indicating that the input completion instruction has been detected from the input device while the transaction is ready for settlement; A payment device comprising:

10. a computer including an input device for inputting data relating to a transaction and a communication device for performing data communication with a plurality of settlement devices for settling the transaction; an end detection means for detecting that an instruction to end input of data relating to a transaction has been given via the input device; a first transmitting means for transmitting the transaction data input via the input device to each of the plurality of payment devices before the completion detecting means detects an instruction to complete input of the transaction data; an input side correcting means for correcting the transaction data transmitted by the first transmitting means to each of the plurality of settlement devices before the completion detecting means detects an instruction to complete input of the transaction data; a second transmitting means for transmitting the transaction data corrected by the input side correcting means to each of the plurality of settlement devices before the completion detecting means detects an instruction to complete input of the transaction data; and a first notification means for notifying one of the plurality of payment devices of the completion of input when the completion detection means detects an instruction to complete input of data related to the transaction; A program to function as a

11. a computer of a settlement apparatus equipped with a communication device that performs data communication with an input device having a first transmission means that transmits transaction-related data inputted via an input device to each of a plurality of settlement apparatuses before an instruction to end input of the transaction-related data is detected, and a second transmission means that modifies the transaction-related data transmitted to each of the plurality of settlement apparatuses before an instruction to end input of the transaction-related data is detected and transmits modified transaction-related data to each of the plurality of settlement apparatuses before the instruction to end input is detected; a settlement-side storage means for storing data relating to the transaction transmitted from the input device by the first transmission means in a settlement-side storage unit until the transaction is settled; a settlement side correcting means for correcting the transaction data stored in the settlement side memory unit using the transaction data transmitted from the input device by the second transmitting means; and a settlement means for settling a transaction based on the data relating to the transaction stored in the settlement-side storage unit when receiving a notice of input completion indicating that the input completion instruction has been detected from the input device while the transaction is ready for settlement; A program to function as a

Images