Payment system, settlement device and program thereof

Abstract

To enable transactions to be settled by a clerk and a customer sharing an operation without generating settlement information with an input device.SOLUTION: An input device transmits data pertaining to a transaction to each of a plurality of settlement devices before an end-of-input instruction for data pertaining to the transaction is detected. When detecting the input end instruction for the data pertaining to the transaction, the input device transmits a completion event informing that the input is complete to each of the plurality of settlement devices. The settlement device stores the data pertaining to the transaction transmitted from the input device in a memory unit. The settlement device transmits payment start event to the input device in response to acceptance of the payment start declaration. When receiving a deletion event from the input device, the settlement device clears the memory unit and releases the state of waiting for the payment start declaration.SELECTED DRAWING: Figure 17

Description

[Technical field]

[0001] An embodiment of the present invention relates to an accounting system, a settlement device, and a program therefor. [Background technology]

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

[0003] In a shared accounting system, the store clerk inputs product data, so the time required for data input is shorter than in a self-service accounting system where the customer does all the operations themselves. On the other hand, since the customer operates the payment device, it is expected that customers who are unfamiliar with the operation will have difficulty in making a payment. Therefore, in a shared accounting system, multiple payment devices are generally assigned to one input device.

[0004] In this type of conventional accounting system, when a store clerk finishes inputting all data of the products to be bought and sold in a transaction with a customer into an input device, payment information is generated in the input device. The payment information includes detailed information such as the product code, product name, unit price, quantity, and amount of the sold products, as well as total information such as the total points and total amount. The payment information is then sent to any available payment device, and the store clerk guides the customer to that payment device. The payment device that receives the payment information becomes capable of processing the payment, and the customer operates the payment device to pay the price with cash, credit card, electronic money, or the like. Thus, in a sharing-type accounting system, the store clerk and the customer share the operations to settle the transaction. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2013-242839 A Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the embodiments of the present invention 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. [Means for solving the problem]

[0007] In one embodiment, the accounting system comprises an input device for inputting data relating to a transaction via an input device, and a plurality of payment devices for settling the transaction for which data has been input via the input device, the payment devices being connected via a communication line. The input device includes a completion detection means, a first transmission means, a second transmission means, and a third transmission means. The completion detection means detects an instruction to end input of data related to a transaction. The first transmission means transmits the data related to the transaction inputted via the input device to each of the multiple payment devices before the completion detection means detects an instruction to end input of the data related to the transaction. When the completion detection means detects an instruction to end input of the data related to the transaction, the second transmission means transmits a completion event notifying each of the multiple payment devices of completion of input. When the third transmission means receives an accounting start event declaring the start of accounting from any one of the multiple payment devices that transmitted the completion event, it transmits an execution event to the one payment device that transmitted the accounting start event, permitting the execution of accounting, and transmits a deletion event to instruct the other payment devices to delete the data related to the transaction. The multiple payment devices include a storage means, a waiting means, a fourth transmission means, a payment means, and a deletion means. The storage means stores data relating to a transaction transmitted from the input device in a storage unit. The waiting means waits for an accounting start declaration when a completion event is received from the input device in a state in which the transaction can be settled. The fourth transmission means transmits an accounting start event to the input device in response to receiving the accounting start declaration. The payment means settles the transaction based on the data relating to the transaction stored in the storage unit when an execution event is received from the input device. The deletion means clears the storage unit and cancels the waiting state for an accounting start declaration when a deletion event is received from the input device. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram showing the overall configuration of a transaction system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing a hardware configuration of the input device. [Diagram 3] FIG. 3 is a block diagram showing a hardware configuration of the payment device. [Figure 4] FIG. 4 is a block diagram showing the main functional configuration of the processor of the input device. [Diagram 5] FIG. 5 is a schematic diagram showing the data structure of a detail record. [Figure 6] FIG. 6 is a schematic diagram showing data transitions in a state table of the input device. [Figure 7] FIG. 7 is a block diagram showing the main functional configuration of the processor of the payment device. [Figure 8] FIG. 8 is a flowchart showing the main steps of information processing executed by the processor of the input device in accordance with the input program. [Figure 9] FIG. 9 is a flowchart showing the main steps of information processing executed by the processor of the input device in accordance with the input program. [Figure 10] FIG. 10 is a flowchart showing the main steps of information processing executed by the processor of the settlement device upon receiving an input event from the input device. [Figure 11] FIG. 11 is a flowchart showing the main steps of information processing executed by the processor of the settlement device upon receiving a completion event from the input device. [Figure 12] FIG. 12 is a schematic diagram showing an example of a display of the details screen. [Figure 13] FIG. 13 is a schematic diagram showing an example of a display of a sub-plan view. [Figure 14] FIG. 14 is a schematic diagram showing an example of the checkout waiting screen. [Figure 15] FIG. 15 is a schematic diagram showing an example of a transaction start screen. [Figure 16] FIG. 16 is a schematic diagram showing an example of a checkout screen. [Figure 17] FIG. 17 is a sequence diagram of various events transmitted and received between one input device and two payment devices. [Figure 18] FIG. 18 is a schematic diagram showing the overall configuration of a transaction system according to the second embodiment. [Figure 19] FIG. 19 is a block diagram showing the main functional configuration of the processor of the settlement device. [Figure 20] FIG. 20 is a schematic diagram showing data transitions in a control table of the settlement device. [Figure 21] FIG. 21 is a flowchart showing the main steps of information processing executed by a processor of the settlement device that receives an input event from the input device. [Figure 22] FIG. 22 is a flowchart showing the main steps of information processing executed by the processor of the settlement device that has received a completion event from the input device. [Diagram 23] FIG. 23 is a flowchart showing the main steps of information processing executed by the processor of the settlement device upon receiving a completion event from the input device. [Figure 24] FIG. 24 is a schematic diagram showing an example of a transaction start screen. [Diagram 25] FIG. 25 is a sequence diagram of various events transmitted and received between two input devices and one settlement device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, several embodiments of a payment system that allows a store clerk and a customer to share the operations to settle a transaction without generating payment information on an input device will be described with reference to the drawings.

[0010] <First embodiment> [Explanation of accounting system configuration] 1 is a schematic diagram showing the overall configuration of a transaction system 100 in the first embodiment. Transaction system 100 includes an input device 11, a payment device 12, a server 13, and a network 14 that connects these. There are no particular limitations on the type of network 14, but a wired or wireless LAN (local area network) is generally used.

[0011] The input device 11 is a device configured to receive data input of a commodity to be bought and sold in each transaction. The settlement device 12 is a device configured to perform settlement processing of the transaction based on the commodity data input by the input device 11. The input device 11 is operated, in principle, by a store clerk 2 who plays a role called a checker. The settlement device 12 is operated, in principle, by a consumer who purchases a commodity in a store, a so-called customer 3. The store clerk is also called an employee, etc. The customer 3 is also called a purchaser, etc. The operator of the input device 11 may be the customer 3. That is, the customer 3 may operate both the input device 11 and the settlement device 12. Similarly, the operator of the settlement device 12 may be the store clerk 2. That is, the store clerk 2 may operate both the input device 11 and the settlement device 12.

[0012] 1, the input device 11 is attached to a work table 4. The work table 4 has a rectangular top plate. A plurality of work tables 4 are arranged so that the longitudinal directions of the top plates are substantially parallel to each other, thereby forming a passage for customers 3, that is, a so-called checkout lane.

[0013] The input device 11 and the payment device 12 are arranged for each checkout lane in the store. For each checkout lane, one input device 11 is arranged, and two or more payment devices 12 are arranged. Various data signals are exchanged between the input device 11 and the payment device 12 arranged in the same checkout lane via the network 14. The data signals may be exchanged via the server 13 or may not be exchanged via the server 13.

[0014] 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 arranged in other checkout lanes. The two payment devices 12 (12-1, 12-2) arranged in the first checkout lane can both execute the payment process of a transaction 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 execute the payment process of a transaction processed by the input device 11 (11-2) arranged in the same checkout lane.

[0015] 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 connected to the outside of the server 13.

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

[0017] The product code is a unique code set for each product to identify the product. Usually, each product is provided with a barcode or two-dimensional code representing the product code. Alternatively, a radio frequency identification (RFID) tag storing the product code may be provided. The input device 11 can input the product code of the product being traded by reading the barcode, two-dimensional code, or RFID tag provided on the product with a reading device.

[0018] The product name and unit price are the name of the product identified by the product code and the price per item. The attribute is, for example, information about the tax on the product. Information about taxes includes tax rate, tax type (tax excluded, tax included, tax exempt), etc.

[0019] 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 sales units and sales amount in addition to the above-mentioned product code, product name, and unit price. The sales units are the total sales quantities of products identified by the corresponding product codes. The sales amount is the total sales amount of products identified by the corresponding product codes.

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

[0021] The input device 11 constitutes a computer by connecting the processor 21, the main memory 22, the auxiliary storage device 23, the clock 24, and the 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.

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

[0023] 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 an application program 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 the nonvolatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 21. The nonvolatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0024] 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 above application programs.

[0025] 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 performing data communication between the server 13 and the multiple payment devices 12 connected via the network 14. The keyboard 26 is an input device on which various keys necessary for inputting data related to the products purchased by the customer, that is, the purchased products, are arranged. The scanner 27 is an input device that reads and inputs 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 is the operator of the input device 11, and accepts operation input by the store clerk. The customer display 29 displays information to the customer 3 whose purchased product data has been input in the input device 11.

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

[0027] 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 machine 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 units directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0028] The settlement device 12 constitutes a computer by connecting the processor 31, the main memory 32, the auxiliary storage device 33, the clock 34, and the communication unit 35 via a system transmission path 41. The settlement device 12 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.

[0029] 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 according to an operating system or an application program. The processor 31 is, for example, a CPU.

[0030] 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 an application program 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 the nonvolatile or volatile memory area. The main memory 32 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 31. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0031] The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, a HDD, or an 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 above-mentioned application programs.

[0032] 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 performs data communication 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 the 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 received the change data automatically pays out coins equivalent to the change data as change.

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

[0034] 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 payment, electronic money payment, and code payment. The terminal interface 40 outputs identification data of a cashless payment method selected from a plurality of types of cashless payment methods to the cashless payment terminal 5. In the cashless payment terminal 5, payment of the transaction 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.

[0035] 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 payment but also cashless payment. In other words, a payment device 12 that does not connect the cashless payment terminal 5 to the terminal interface 40 becomes a device that supports only cash payment.

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

[0037] [Explanation of accounting system functions] 4 is a block diagram showing the main functional configuration of the processor 21 of the input device 11. The processor 21 has functions as an input side storage means 51, a first transmission means 52, a detail display means 53, an end detection means 54, a second transmission means 55, a third transmission means 56, and an input side deletion means 57. Note that the functions of the processor 21 are not limited to these.

[0038] The input side storage means 51 is a function for storing data related to a transaction inputted through the input device 61 in the input side storage unit 63. The input side storage unit 63 is a part of the storage area of ​​the main memory 22 or the auxiliary storage device 23. The data related to the transaction is, for example, the product code, quantity, discount amount, discount rate, etc. of the product bought and sold in a transaction with a customer. When the input side storage means 51 inputs the data related to the transaction through the input device 61 such as the keyboard 26, the scanner 27, or the touch panel 28, it creates a detail record Ra for each product to be sold as one transaction based on the input data. As shown in FIG. 5, the detail record Ra is a record that describes data of items such as the product code, product name, unit price, quantity, discount amount, amount, etc. in association with a series of record numbers. The amount is the amount 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 data related to the transaction such as the product code, quantity, etc. The input side storage means 51 stores the detail record Ra in the first transaction file 631 of the input side storage unit 63.

[0039] The input side storage means 51 also has a function of providing the data relating to the transaction inputted via the input device 61 to the first transmission means 52 . The first transmission means 52 is a function of transmitting data provided from the input side storage means 51, i.e., data related to a transaction inputted through the input device 61, to each of the multiple payment devices 12 via the communication unit 25 before the end detection means 54 detects an instruction to end inputting the data related to the transaction. The multiple payment devices 12 are payment devices 12 in which the customer 3, to whom the data of the purchased item has been inputted through the input device 11, can make a payment. Usually, the multiple payment devices 12 are installed in the same checkout lane as the input device 11. The multiple payment devices 12 may include a payment device 12 installed in an adjacent checkout lane. Hereinafter, the multiple payment devices 12 to which the data related to the transaction is transmitted from the input device 11 are referred to as the payment devices 12 of the same group. The first transmission means 52 transmits the input data related to the transaction to each of the payment devices 12 of the same group every time the data related to the transaction is inputted through the input device 61.

[0040] The statement display means 53 is a function that displays transaction statement information on the display device 62 based on transaction-related data inputted 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 53 displays the screen of the display device 62 as a statement screen SAa (see FIG. 12), and displays, on the statement screen SAa, statement information such as the product name, quantity, unit price, discount amount, and amount of the statement record Ra stored in the first transaction file 631. The statement screen SAa will be described later.

[0041] The end detection means 54 is a function for detecting an instruction to end input of data related to a transaction. The end detection means 54 detects an operation input to a first operator of the input device 61 as an input end instruction. The first operator will be described later.

[0042] Furthermore, when the end detection means 54 detects an input end instruction, it updates the status table 64. As shown in Fig. 6, the status table 64 is a data table with a column for a transaction number, a column for a status, and a column for a payment device ID. When the end detection means 54 detects an input end instruction, it adds a new transaction number that is issued each time, a default status "0", and a default payment device ID "0000" to the status table 64. The transaction number is a unique number for individually identifying each transaction.

[0043] The status is data specifying whether the transaction identified by the transaction number is in an unpaid state or a paid state. In this embodiment, a status indicating an unpaid state is set to "0," and a status indicating a paid state is set to "1." In other words, the default status "0" indicates that the transaction is in an unpaid state.

[0044] The payment device ID is device identification information assigned individually to each payment device 12. Each payment device 12 is assigned a unique payment device ID. However, "0000" is not used. In other words, the default payment device ID "0000" is device identification information that is not assigned to each payment device 12. Incidentally, each input device 11 is also assigned a unique device identification information, a so-called input device ID. However, "0000" is not used. Note that the number of digits of the payment device ID is set to four digits, which is just an example. The number of digits of the payment device ID is not particularly limited. The same applies to the number of digits of the input device ID. In short, any information that can individually identify each payment device 12 or input device 11 may be used.

[0045] Furthermore, the end detection means 54 also has a function of notifying the second transmission means 55 that an input end instruction has been detected. The second transmitting means 55 has a function of transmitting a completion event notifying each of the payment devices 12 in the same group of the completion of input when an instruction to end input of data related to a transaction is detected by the end detecting means 54. The completion event is an event indicating that input of data related to a transaction is completed. In other words, a data signal indicating the completion event is transmitted from the communication unit 25 via the communication network 14 to each of the payment devices 12 in the same group.

[0046] The third transmitting means 56 has a function that, when it receives an accounting start event declaring the start of accounting from any one of the payment devices 12 in the same group that sent the completion event, it transmits an execution event to the one payment device 12 that sent the accounting start event, authorizing the execution of the accounting, and transmits a deletion event to the other payment devices 12, instructing them to delete data related to the transaction.

[0047] The transaction start event is an event indicating that a transaction start has been instructed in the payment device 12. When the third transmission means 56 receives the transaction start event from the payment device 12, it transmits an execution event to that payment device 12. In addition, the third transmission means 56 transmits a deletion event to other payment devices 12 for which a transaction start has not been instructed. That is, a data signal indicating the execution event is transmitted from the communication unit 25 to the payment device 12 via the communication network 14. A data signal indicating the deletion event is transmitted from the communication unit 25 to the other payment devices 12 via the communication network 14.

[0048] Furthermore, the third transmission means 56 has a function of updating the status table 64 in response to receiving a transaction start event. That is, the third transmission means 56 updates the status from "0" to "1" as shown in Fig. 6. The third transmission means 56 also rewrites the payment device ID from the default payment device ID to the payment device ID of the payment device 12 that transmitted the transaction start event.

[0049] Furthermore, the third transmission means 56 also has a function of notifying the input side deletion means 57 of deletion in response to receiving a transaction start event. The input side deletion means 57 is a function that deletes data related to a transaction stored in the input side memory unit 63 upon receiving a deletion notification from the third transmission means 56. The input side deletion means 57 deletes all detail records Ra stored in the first transaction file 631 of the input side memory unit 63. In other words, the input side deletion means 57 clears the first transaction file 631. By clearing the first transaction file 631, the input device 11 becomes capable of inputting data related to the transaction with the next customer.

[0050] The functions of the above-mentioned input side memory means 51, first transmission means 52, detail display means 53, end detection means 54, second transmission means 55, third transmission means 56 and input side deletion means 57 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.

[0051] The input program is a type of application program stored in the main memory 22 or the auxiliary storage device 23. There is no particular limitation on the method for installing the input program in the main memory 22 or the auxiliary storage device 23. The input program can be installed in the main memory 22 or the auxiliary storage device 23 by recording it on a removable recording medium, or by distributing the input program by communication via the network 14. The recording medium may 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.

[0052] 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, a waiting means 72, a fourth transmission means 73, a fifth transmission means 74, a payment means 75, and a payment side deletion means 76. Note that the functions of the processor 31 are not limited to these.

[0053] The settlement side storage means 71 has a function of storing data related to a transaction transmitted from the input device 11 and received via the communication unit 35 in the settlement side storage unit 81. The settlement side storage unit 81 has a second transaction file 811 and a third transaction file 812 as transaction files for storing data related to a transaction. The settlement side storage unit 81 is a part of the storage area of ​​the main memory 32 or the auxiliary storage device 33.

[0054] The settlement side storage means 71 creates a detail record Ra for each product sold as one transaction based on the received transaction data. 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, in association with a series of record numbers. In other words, the detail record Ra can be said to be a record that describes transaction data such as the 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 waiting means 72 is a function that waits for a statement of the start of accounting when a completion event is received from the input device 11 via the communication unit 35 in a state where the settlement of a transaction is possible. The state where the settlement of a transaction is possible is an idle state in which the settlement device 12 is not executing the settlement of the transaction. However, even in an idle state, if an error such as running out of receipt paper or change occurs, the settlement of the transaction is impossible. The waiting means 72 refers to the status flag F in the flag memory 82 to determine whether the settlement of the transaction is possible. The flag memory 82 is, for example, a storage area of ​​1-bit data secured in the main memory 32. The above-mentioned 1-bit data becomes the status flag F. The status flag F becomes "0" when the settlement of the transaction is possible, and becomes "1" when the settlement of the transaction is impossible.

[0056] The waiting means 72 waits for a statement to start a transaction when the status flag F is "0", that is, when the transaction can be settled. The statement to start a transaction is usually made by the customer 3 who is the operator of the payment device 12. The waiting means 72 displays an image for accepting the statement to start a transaction on the touch panel 38, and waits for the statement to start a transaction by the customer 3. The image displays a second operator that the customer 3 operates to make the statement to start a transaction. The second operator will be described later.

[0057] The waiting means 72 also displays the payment amount of the customer 3 on an image for accepting the accounting start declaration, and waits for the accounting start declaration. The payment amount is calculated from data related to the transaction stored in the payment side memory unit 81. The payment amount is the total price of the products purchased by the customer 3. If tax is levied on the products, the total price includes tax. When the waiting means 72 detects the accounting start declaration by operational input on the touch panel 38, it notifies the fourth transmission means 73 that an accounting start declaration has been made.

[0058] The fourth transmission means 73 is a function that transmits an accounting start event to the input device 11 in response to receiving an accounting start declaration. The accounting start event is an event that indicates that an accounting start declaration has been received. The accounting start event is transmitted to the input device 11 that transmitted the completion event. In other words, a data signal of the accounting start event is transmitted from the communication unit 35 to the input device 11 via the communication network 14.

[0059] The fifth transmitting means 74 has a function of transmitting an accounting impossible event when a completion event is received from the input device 11 via the communication unit 35 when settlement of the transaction is impossible. The accounting impossible event is an event that notifies the input device 11 that settlement is impossible. The fifth transmitting means 74 refers to the status flag F. When the waiting means 72 receives a completion event when the status flag is "1", that is, when settlement of the transaction is impossible, the fifth transmitting means 74 transmits the accounting impossible event to the input device 11 that transmitted the completion event. In other words, the data signal of the accounting impossible event is transmitted from the communication unit 35 to the input device 11 via the communication network 14.

[0060] The settlement means 75 has a function of settling a transaction based on the data related to the transaction stored in the settlement side memory unit 81 when an execution event is received from the input device 11 via the communication unit 35. When the settlement means 75 receives an execution event from the input device 11 that has transmitted a transaction start event by functioning as the fourth transmission means 73, the settlement means 75 starts settlement of the transaction. Specifically, the settlement means 75 copies the data stored in the second transaction file 811 to the third transaction file 812 and clears the second transaction file 811. Then, the settlement means 75 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 75 settles the transaction with the selected payment method. For example, when cash payment is selected, the payment means 75 executes a payment process for the transaction by cash via an automatic change machine connected to the change machine interface 36. For example, when credit card payment is selected, the payment means 75 executes a payment process for the transaction by credit card via the cashless payment terminal 5 connected to the terminal interface 40. For example, when electronic money payment is selected, the payment means 75 executes a payment process for the transaction by electronic money via the cashless payment terminal 5 connected to the terminal interface 40. It should be noted that the payment processes for transactions by cash, credit card, and electronic money are all well-known processes, and therefore detailed explanations will be omitted.

[0062] The settlement side deletion means 76 has a function of clearing the settlement side memory unit 81 and canceling the standby state for the accounting start declaration when a deletion event is received from the input device 11 via the communication unit 35. Receiving a deletion event means that an execution event is sent to another settlement device 12 in the same group, and the transaction is settled by that settlement device 12. Therefore, the data related to the transaction stored in the second transaction file 811 of the settlement side memory unit 81 becomes unnecessary. In response to receiving a deletion event, the settlement side deletion means 76 deletes all of the detail records Ra stored in the second transaction file 811. By clearing the second transaction file 811 in this way, the settlement device 12 becomes able to accept data related to the transaction with the next customer.

[0063] The settlement side deletion means 76 also cancels the standby state of the standby means 72. That is, the settlement side deletion means 76 erases the image for accepting the accounting start declaration that was displayed on the touch panel 38, and cancels the standby state. Therefore, there is no possibility that the accounting start declaration will be issued twice from different settlement devices 12 for one transaction.

[0064] The functions of the above-mentioned payment side memory means 71, waiting means 72, fourth transmission means 73, fifth transmission means 74, payment means 75 and payment side deletion means 76 are realized by information processing executed by the processor 31 in accordance with a program for the payment device, a so-called payment program.

[0065] The payment program is a type of application program stored in the main memory 32 or the auxiliary storage device 33. There is no particular limitation on the method of 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 distributed by communication via the network 14, and installed in the main memory 32 or the auxiliary storage device 33. The recording medium may 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.

[0066] [Explanation of accounting system operation] 8 and 9 are flow charts showing the main steps of the information processing executed by the processor 21 of the input device 11 according to the input program. FIG. 10 and FIG. 11 are flow charts showing the main steps of the information processing executed by the processor 31 of the payment device 12 according to the payment program. FIG. 12 to FIG. 14 are examples of screens displayed on the touch panel 28 of the input device 11. FIG. 15 and FIG. 16 are examples of screens displayed on the touch panel 38 of the payment device 12. Below, the main operations of the accounting system 100 are explained using each figure. Specifically, the operation of the accounting system 100 is explained by focusing on one input device 11-1 and two payment devices 12-1 and 12-2 installed in the same checkout lane. The operation of the input device 11-2 and two payment devices 12-3 and 12-4 installed in other checkout lanes is similar, so the explanation here is omitted.

[0067] The contents and procedures of the information processing described below are merely examples. The contents and procedures can be changed as appropriate as long as the same operational effect can be achieved. The screen examples are also merely examples. The contents of the output text, the arrangement of images, the type and layout of the software keys, etc. can be changed as appropriate.

[0068] (Operation description of input device) First, the main steps of the information processing executed by the processor 21 of the input device 11-1 in accordance with an input program will be described with reference to the flowcharts of FIGS. A customer 3 places the products he or she wishes to purchase from those displayed in the sales area in a shopping basket or the like, and heads to the checkout lane. When the customer 3 reaches 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-1. In response to this operation, the processor 21 starts information processing according to the procedure shown in the flowcharts of Figures 8 and 9.

[0069] First, the processor 21 displays the screen of the touch panel 28 as the details screen SAa (see FIG. 12) in ACT101. 12 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 in list form the product name, quantity, unit price, discount amount, and price of the products entered as purchased items in one transaction in the order of a series of record numbers. The total area AAc displays the total quantity and total price of the purchased items.

[0070] The details 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 instructing that input of purchased items in one transaction has been completed. The discount button BAb is an operator for instructing a discount on the most recent item input as a purchased item in one transaction. The discount button BAc is an operator for instructing 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 keypad of 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 keypad of the keyboard 26.

[0071] In ACT101, the processor 21 sets the screen of the customer display 29 to a customer details screen. The customer details screen is the details screen SAa without the software key.

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

[0073] Returning to the explanation of Figure 8. The processor 21, which has displayed the statement screen SAa, waits for a product code to be input in ACT102. When the product code is input, the processor 21 proceeds from ACT102 to ACT103. The processor 21 controls the communication unit 25 to transmit an input event to the payment devices 12-1 and 12-2 in the same group by multicast communication in ACT103. By this control, a data signal indicating the input event is transmitted from the communication unit 25. The data signal indicating the input event is transmitted to the payment device 12-1 and the payment device 12-2 via the communication network 14. The input event includes the product code input from the scanner 27 or the touch panel 28. The input event also includes the input device ID of the input device 11-1.

[0074] The processor 21 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.

[0075] The processor 21 stores the detail record Ra in the first transaction file 631 in ACT105. The processor 21 also updates the detail screen SAa in ACT106. That is, the processor 21 displays the product name, quantity, and amount 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 record number 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 amount of the detail record Ra in the detail area AAb. The processor 21 also displays the total quantity and total amount 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.

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

[0077] 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 processes of ACT103 to ACT106 in the same manner as described above. That is, the processor 21 controls to transmit an input event to the settlement devices 12-1 and 12-2 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. After that, the processor 21 enters a standby state of ACT107 to ACT109.

[0078] In the standby state of ACT107 to ACT109, when a quantity is input by the numeric keypad and multiplication key of the keyboard 26, or when a discount amount or discount rate is input by the discount button BAb or the discount button BAc and the numeric keypad, the processor 21 proceeds from ACT108 to ACT110. The processor 21 controls the communication unit 25 to transmit an input event to the payment devices 12-1 and 12-2 of the same group by multicast communication as ACT110. By this control, a data signal indicating the input event is transmitted from the communication unit 25. The data signal indicating the input event is transmitted to the payment device 12-1 and the payment device 12-2 via the communication network 14. The input event includes the quantity, discount amount, or discount rate input from the keyboard 26. The input event also includes the input device ID of the input device 11-1.

[0079] The processor 21 updates the detail record Ra of the record number r stored in the first transaction file 631 in ACT111. Specifically, when 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. When a discount amount is input, the processor 21 writes the discount amount in the detail record Ra and subtracts the discount amount from the amount. When a discount rate is input, the processor 21 calculates and writes the discount amount from the unit price and the discount rate in the detail record Ra, and subtracts the discount amount from the amount. Then, the processor 21 updates the display of the current area AAa and the total area AAc of the detail screen SAa with the data of the first transaction file 631 after updating the detail record Ra in ACT112. The processor 21 also updates the customer detail screen in the same way. After that, the processor 21 enters a standby state for ACT107 to ACT109.

[0080] In the standby state of ACT107 to ACT109, if the subtotal button BAa is input, the processor 21 proceeds from ACT109 to ACT113. In ACT113, the processor 21 sets the screen of the touch panel 28 to the subtotal screen SAb (see FIG. 13).

[0081] FIG. 13 is a display example of the subtotal display surface SAb. The subtotal display surface SAb includes a total area AAd in which the total points and the total amount are displayed. The total area AAd displays the total points and the total amount of the detail records Ra stored in the first transaction file 631. The subtotal display surface SAb also includes software keys of a subtotal discount button BAd, a subtotal discount button BAe, an input completion button BAf, and a back to detail button BAg. The subtotal discount button BAd is an operator for instructing a discount on the total amount. The subtotal discount button BAe is an operator for instructing a discount on the total amount. Incidentally, the total amount is discounted by inputting the subtotal discount button BAd and inputting the discount amount on the numeric keypad of the keyboard 26. Similarly, the total amount is discounted by inputting the subtotal discount button BAe and inputting the discount rate on the numeric keypad of the keyboard 26.

[0082] The input completion button BAf is an operator for instructing the end of inputting data related to the transaction. Here, the input completion button BAf functions as a first operator. The return to details button BAg is an operator for instructing the return to the details screen SAa.

[0083] In ACT113, the processor 21 sets the screen of the customer display 29 to a customer small screen. The customer small screen is the small screen SAb from which the software key is removed.

[0084] After confirming that the subtotal display SAb is displayed on the touch panel 28, the sales clerk 2 operates the subtotal discount button BAe or BAe to perform a subtotal discount or discount operation if a subtotal discount or discount is required. Also, if it is necessary to return to the statement screen SAa because, for example, there is an item that has not been registered, the sales clerk 2 operates the return to statement button BAg. On the other hand, when the registration of the items is complete and the process proceeds to the checkout, the sales clerk 2 operates the input completion button BAf.

[0085] Returning to the explanation of Figure 8. After displaying the sub-plan screen SAb, the processor 21 proceeds to ACT114. The processor 21 checks whether the input completion button BAf has been pressed in ACT114. If the input completion button BAf has not been pressed, the processor 21 proceeds to ACT115. The processor 21 checks whether the return to details button BAg has been pressed in ACT115. If the return to details button BAg has not been pressed, the processor 21 returns to ACT114.

[0086] After displaying the subtotal plan screen SAb in this manner, the processor 21 waits for the input completion button BAf to be pressed or the return to details button BAg to be pressed in ACT114 and ACT115. When the subtotal discount button BAd or the subtotal discount button BAe is pressed in this standby state, the processor 21 executes the subtotal discount process or the subtotal discount process. The processor 21 then waits for ACT114 and ACT115.

[0087] When the back to details button BAg is pressed in the standby state of ACT114 and ACT115, the processor 21 proceeds from ACT115 to ACT116. The processor 21 returns the screen of the touch panel 28 to the previous details screen in ACT116. Then, the processor 21 proceeds to ACT107. The processor 21 enters a standby state of ACT107 to ACT109.

[0088] In the standby state of ACT114 and ACT115, if the input completion button BAf is pressed, the processor 21 proceeds from ACT114 to ACT121 in Fig. 9. The processor 21 issues a transaction number in ACT121. For example, the input device 11-1 is provided with a counter for counting transaction numbers. The processor 21 counts up this counter to issue a new transaction number.

[0089] After issuing the transaction number, the processor 21 proceeds to ACT122. The processor 21 creates a status table 64 in ACT122. That is, the processor 21 creates a status table 64-1 (see FIG. 6) that is composed of the transaction number acquired in the processing of ACT121, the default status "0", and the default payment device ID "0000".

[0090] After creating the state table 64-1, the processor 21 proceeds to ACT123. The processor 21 controls the communication unit 25 to transmit a completion event to the payment devices 12-1 and 12-2 of the same group by multicast communication as ACT123. This control causes the communication unit 25 to transmit a data signal indicating the completion event. The data signal indicating the completion event is transmitted to the payment devices 12-1 and 12-2 via the communication network 14. The completion event includes the transaction number issued in the processing of ACT121. The completion event also includes the input device ID of the input device 11-1. Although details will be described later, an accounting start event or an accounting impossible event is returned from the payment devices 12-1 and 12-2 that received the completion event. The accounting start event and the accounting impossible event include the payment device ID and the transaction number set in the payment devices 12-1 and 12-2 that sent the completion event.

[0091] The processor 21 of the input device 11-1 that sent the completion event resets the counter N to "0" in ACT124. The processor 21 then proceeds to ACT125. The processor 21 checks whether an accounting start event has been received in ACT125. If an accounting start event has not been received, the processor 21 proceeds to ACT126. The processor 21 checks whether an accounting impossible event has been received in ACT126. If an accounting impossible event has not been received, the processor 21 returns to ACT125.

[0092] In this way, the processor 21 of the input device 11-1 that has transmitted a completion event to the payment devices 12-1 and 12-2 of the same group waits in ACT125 and ACT126 to receive a transaction start event or a transaction impossible event from the payment device 12-1 or the payment device 12-2.

[0093] When a transaction start event is received in the standby state of ACT125 and ACT126, the processor 21 proceeds from ACT125 to ACT127. The processor 21 acquires the payment device ID and transaction number from the transaction start event in ACT127. The processor 21 then updates the state table 64 in ACT128. Specifically, the processor 21 changes the status of the state table 64-1 in which the acquired transaction number is set from "0" to "1", as shown in state table 64-2 in FIG. 6. The processor 21 also rewrites the payment device ID from the default payment device ID to the payment device ID acquired in the processing of ACT127.

[0094] After updating state table 64, processor 21 proceeds to ACT129. Processor 21 controls communication unit 25 to transmit an execution event by unicast communication to the payment device 12 that transmitted the transaction start event in ACT129. This control causes communication unit 25 to transmit a data signal of the execution event. The data signal of the execution event is transmitted via communication network 14 to one payment device 12 that transmitted the transaction start event. The execution event includes the transaction number obtained from the transaction start event.

[0095] Furthermore, the processor 21 controls the communication unit 25 to transmit a deletion event by unicast communication to the payment device 12 that has not transmitted the transaction start event among the payment devices 12-1, 12-2 of the same group as ACT130. For example, if the payment device that transmitted the transaction start event is the payment device 12-1, the processor 21 controls the communication unit 25 to transmit a deletion event to the payment device 12-2. This control causes the communication unit 25 to transmit a data signal of the deletion event. The data signal of the deletion event is transmitted to the payment device 12-2 via the communication network 14. The deletion event includes the transaction number issued in the processing of ACT121. The deletion event also includes the input device ID of the input device 11-1.

[0096] The processor 21 of the input device 11-1 that transmitted the execution event and the deletion event proceeds to ACT 131. The processor 21 clears the first transaction file 631 in ACT 131. By this clearing, all the detail records Ra stored in the first transaction file 631 are deleted.

[0097] On the other hand, if an unacceptable transaction event is received during the standby state of ACT125 and ACT126, the processor 21 proceeds from ACT126 to ACT132. The processor 21 counts up the counter N by "1" in ACT132. Then, the processor 21 checks whether the counter N has become "2" in ACT133. The number "2" compared with the counter N is the number of payment devices 12 belonging to the same group. If three payment devices 12 belong to the same group, the number compared with the counter N in the processing of ACT133 will be "3".

[0098] If the counter N is smaller than "2" in ACT133, the processor 21 returns to ACT125. The processor 21 goes into a standby state for ACT125 and ACT126.

[0099] If the counter N is equal to "2" in ACT133, that is, if a transaction impossible event has been received from all payment devices 12-1, 12-2 belonging to the same group, the processor 21 proceeds to ACT134. In ACT135, the processor 21 sets the screen of the touch panel 28 to the transaction waiting screen SAc (see FIG. 14). Receiving a transaction impossible event from all payment devices 12-1, 12-2 belonging to the same group means that both payment devices 12-1 and 12-2 are currently executing a payment process, and payment is impossible for the customer 3 whose purchased item has been registered in the input device 11-1.

[0100] Fig. 14 is an example of the display of the checkout waiting screen SAc. The checkout waiting screen SAc includes a total area AAd in which the total points and the total amount are displayed. The checkout waiting screen SAc also includes a software key for the checkout button BAh. The checkout button BAh is an operator for commanding a transition to checkout. After checking the checkout waiting screen SAc, the store clerk 2 waits for the checkout machine, i.e., the payment device 12-1 or the payment device 12-2, to become available, as indicated in the message displayed on the checkout waiting screen SAc. Then, once it is confirmed that the payment device 12-1 or the payment device 12-2 has become available, the store clerk 2 presses the checkout button BAh.

[0101] Returning to the explanation of Figure 9. The processor 21 of the input device 11-1 that has displayed the checkout standby screen SAc proceeds to ACT135. The processor 21 waits for the checkout button BAh to be input in ACT135. Then, when the checkout button BAh is input, the processor 21 returns to ACT123. The processor 21 controls the transmission of a completion event to the payment devices 12-1 and 12-2 of the same group by multicast communication. Thereafter, the processor 21 executes the processing from ACT123 onwards in the same manner as described above. Therefore, when a checkout start event is received from the payment device 12-1 or the payment device 12-2 of the same group, the processor 21 executes the processing of ACT127 to ACT131. Thus, the first transaction file 631 is cleared, and the input device 11-1 becomes capable of inputting data related to the transaction with the next customer.

[0102] This concludes the description of the information processing that the processor 21 of the input device 11-1 executes in accordance with the input program.

[0103] Here, the processor 21 realizes the function of the input side storage means 51 by the processing of ACT105 and ACT111. The processor 21 realizes the function of the first transmission means 52 by the processing of ACT103 and ACT110. The processor 21 realizes the function of the detail display means 53 by the processing of ACT106 and ACT112. The processor 21 realizes the function of the end detection means 54 by the processing of ACT113 and ACT114. The processor 21 times out the function of the second transmission means 55 by the processing of ACT123. The processor 21 realizes the function of the third transmission means 56 by the processing of ACT125 to ACT130. The processor 21 realizes the function of the input side deletion means 57 by the processing of ACT131.

[0104] (Operation description of payment device) Next, the main steps of the information processing executed by the processor 31 of the payment device 12-1 and the payment device 12-2 according to the payment program will be described with reference to the flow charts in Figs. 10 and 11. The information processing steps executed by the processor 31 of the payment device 12-1 and the payment device 12-2 are the same. Therefore, the following description will be given using the processor 31 of the payment device 12-1 as an example.

[0105] 10 is a flow chart showing the main steps of the information processing executed by the processor 31 of the settlement device 12-1 that receives an input event from the input device 11-1. As described above, the input event includes an input event including a product code and an input event including a quantity, a discount amount, or a discount rate.

[0106] Upon receiving the input event, processor 31 checks in ACT201 whether an input event including a product code has been received. If an input event including a product code has been received, processor 31 proceeds to ACT202. Processor 31 creates a detail record Ra in ACT202. That is, processor 31 accesses server 13 and acquires a product record including the product code included in the input event from product master file 131. Then, 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, based on product information such as product name and unit price described in the product record. Note that the quantity is "1". The discount amount is "0". The amount is the unit price.

[0107] Having created the detail record Ra, the processor 31 proceeds to ACT 203. In ACT 203, the processor 31 stores the detail record Ra in the second transaction file 811.

[0108] On the other hand, if the received input event does not include a product code, the processor 31 proceeds from ACT201 to ACT204. The processor 31 checks whether an input event including a quantity, a discount amount, or a discount rate has been received in ACT204. If an input event including a quantity, a discount amount, or a discount rate has been received, the processor 31 proceeds from ACT204 to ACT205. The processor 31 updates the detail record Ra of the record number r stored in the second transaction file 811 in ACT205. Specifically, if an input event including a quantity has been 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 has been 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 has been 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. With this, processor 31 ends the information processing performed when an input event is received.

[0109] FIG. 11 is a flow chart showing the main steps of the information processing executed by the processor 31 of the payment device 12-1 that receives the completion event from the input device 11-1. The processor 31 that receives the completion event checks the status flag F as ACT211. If the status flag F is "1", that is, if the transaction cannot be settled in the payment device 12-1, the processor 31 proceeds to ACT212. The processor 31 controls the communication unit 35 to transmit an accounting impossible event as ACT212. This control causes the communication unit 35 to transmit a data signal of the accounting impossible event to the input device 11-1. The data signal of the accounting impossible event is transmitted to the input device 11-1 via the communication network 14. The accounting impossible event includes the payment device ID of the payment device 12-1. In the input device 11-1 that receives the data signal of the accounting impossible event, the information processing shown in the procedures ACT132 to ACT135 of FIG. 9 is executed.

[0110] On the other hand, if the status flag F is "0", that is, if a completion event is received while the transaction is in an idle state and settlement is possible, the processor 31 proceeds to ACT213. In ACT213, the processor 31 obtains the transaction number from the completion event and stores it in the main memory 32. In ACT214, the processor 31 causes the screen of the touch panel 38 to display the transaction start screen SBa (see FIG. 15).

[0111] FIG. 15 is an example of a display of the transaction start screen SBa. The transaction start screen SBa includes a total area ABd in which the total points and total amount are displayed. The total area ABd displays the total points and total amount of the detail record Ra stored in the second transaction file 811. The transaction start screen SBa also includes a software key for a start button BBa. The start button BBa is an operator that a customer 3 who has confirmed the transaction start screen SBa operates to declare the start of a transaction. In other words, the start button BBa functions as a second operator.

[0112] After displaying the transaction start screen SBa, the processor 31 proceeds to ACT215. In ACT215, the processor 31 checks whether the start button BBa has been pressed. If the start button BBa has not been pressed, the processor 31 proceeds to ACT216. In ACT216, the processor 31 checks whether a delete event has been received. If a delete event has not been received, the processor 31 returns to ACT215. After displaying the transaction start screen SBa in this way, the processor 31 waits for the start button BBa to be pressed or for a delete event to be received.

[0113] When a delete event is received in the standby state of ACT215 and ACT216, the processor 31 proceeds from ACT216 to ACT217. In ACT217, the processor 31 clears the second transaction file 811. As a result of this clearing, all of the detail records Ra stored in the second transaction file 811 are deleted.

[0114] On the other hand, if the start button BBa is pressed while in the standby state of ACT215 and ACT216, the processor 31 proceeds from ACT215 to ACT218. The processor 31 controls the communication unit 35 to send a transaction start event as ACT218. This control causes the communication unit 35 to send a data signal of the transaction start event. The data signal of the transaction start event is sent to the input device 11-1 via the communication network 14. The transaction start event includes the transaction number obtained from the completion event in ACT213. The transaction start event also includes the payment device ID of the payment device 12. In the input device 11-1 that receives the data signal of the transaction start event, information processing of the procedure shown in ACT127 to ACT131 of FIG. 9 is executed.

[0115] The processor 31 of the payment device 12-1 that sent the transaction start event proceeds to ACT219. The processor 31 waits for an execution event in ACT219. When the processor 31 receives an execution event from the input device 11-1 that sent the transaction start event, the processor 31 proceeds to ACT220. The processor 31 copies the data of the second transaction file 811 to the third transaction file 812 in ACT220. Then, the processor 31 clears the second transaction file 811 in ACT221. This clearing deletes all of the detail records Ra stored in the second transaction file 811.

[0116] After clearing the second transaction file 811, the processor 31 proceeds to ACT222. In ACT222, the processor 31 changes the status flag F from "0" to "1." In addition, in ACT223, the processor 31 changes the screen of the touch panel 38 to the accounting screen SBb (see FIG. 16).

[0117] FIG. 16 is an example of a display of the accounting screen SBb. The accounting screen SBb includes a total area ABa in which the total points and total amount are displayed. The accounting screen SBb also includes the following software keys: a cash button BBb, a credit button BBC, an electronic money button BBd, and a code payment button BBe. The cash button BBb, credit button BBC, electronic money button BBd, and code payment button BBe are controls for selecting the payment method. A customer 3 wishing to pay in cash presses the cash button BBb. A customer 3 wishing to pay by credit card presses the credit button BBC. A customer 3 wishing to pay by electronic money presses the electronic money button BBd. A customer 3 wishing to pay by code presses the code payment button BBe.

[0118] After displaying the checkout screen SBb, the processor 31 proceeds to ACT224. In ACT224, the processor 31 waits for a payment method to be selected and for the payment of the price to be made using that payment method. Once the payment of the price has been made, the processor 31 proceeds to ACT225. In ACT225, the processor 31 executes the settlement process using the selected payment method.

[0119] For example, when the cash button BBb on the accounting screen SBb is pressed and cash is inserted into the automatic change machine, the processor 31 executes cash payment processing. When the credit button BBc is pressed and credit card data is read by the cashless payment terminal 5, the processor 31 executes credit payment processing. When the electronic money button BBd is pressed and electronic money card data is read by the cashless payment terminal 5, the processor 31 executes electronic money payment processing. When the code payment button BBe is pressed and a barcode or two-dimensional code for code payment is read by the scanner 37, the processor 31 executes code payment processing.

[0120] The processor 31 also drives the printer 39 to control the issuance of receipts. A receipt is a record of information capable of identifying a transaction, such as the transaction date and time, transaction number, input device ID, and payment device ID, as well as details of the transaction, such as purchase data and total data, based on the data stored in the third transaction file 812. Note that the receipt need not be a paper receipt, but may be an electronic receipt in which the receipt data has been digitized and can be viewed on the customer's smartphone, etc.

[0121] After completing the settlement process, the processor 31 proceeds to ACT226. In ACT226, the processor 31 clears the third transaction file 812. This clearing deletes all of the detail records Ra stored in the third transaction file 812. In addition, in ACT227, the processor 31 changes the status flag F from "1" to "0." With this, the processor 31 ends the information processing performed when a completion event is received.

[0122] Here, the processor 31 realizes the function of the settlement side storage means 71 by the processing of ACT203 and ACT205. The processor 31 realizes the function of the waiting means 72 by the processing of ACT211 to ACT216. The processor 31 realizes the function of the fourth transmission means 73 by the processing of ACT218. The processor 31 realizes the function of the fifth transmission means 74 by the processing of ACT212. The processor 31 realizes the function of the settlement means 75 by the processing of ACT223 to ACT225. The processor 31 realizes the function of the settlement side deletion means 76 by the processing of ACT217.

[0123] [Explanation of the accounting system's function] FIG. 17 is a sequence diagram of various events transmitted and received between one input device 11-1 and two payment devices 12-1 and 12-2. First, it is assumed that both payment devices 12-1 and 12-2 are in an idle state, and a standby screen is displayed on the touch panel 38. The standby screen is a screen that notifies the operator that the device is on standby. In principle, the operator of the payment device 12 is the customer 3. Therefore, the standby screen may be a screen that displays an image that the customer 3 will not operate without permission. For example, the standby screen may be a screen that displays text such as "Welcome" or "Please wait," or a screen that displays an illustration such as a store logo.

[0124] Each time data related to a transaction, such as the product code, quantity, discount amount or discount rate of a product purchased by the first customer "Customer P", is input to input device 11-1, an input event including the data related to the transaction is transmitted to payment device 12-1 and payment device 12-2 by multicast communication. In payment device 12-1 and payment device 12-2, the data in second transaction file 811 is updated based on the data related to the transaction included in the input event.

[0125] When the customer P completes data entry of the product to be purchased and presses the input completion button BAf in the input device 11-1, a completion event is transmitted to the payment device 12-1 and the payment device 12-2 by multicast communication. In the payment device 12-1 and the payment device 12-2, a checkout start screen SBa is displayed on the touch panel 38.

[0126] Now, assume that customer "Customer P" moves to the location where payment device 12-1 is installed and presses the start button BBa on the transaction start screen SBa displayed on touch panel 38. This causes a transaction start event to be sent from payment device 12-1 to input device 11-1. Then, input device 11-1, which has received the transaction start event, sends an execution event to payment device 12-1. On the other hand, a deletion event is sent to payment device 12-2.

[0127] In the payment device 12-1 that has received the execution event, the accounting screen SBb is displayed on the touch panel 38. Thus, the customer "Customer P" can operate the payment device 12-1 to make the payment. Meanwhile, in the payment device 12-2 that has received the deletion event, the second transaction file 811 is cleared and a standby screen is displayed on the touch panel 38. In this way, the payment device 12-2 that has received the deletion event has the second transaction file 811 cleared, so that it can receive an input event for the next customer. Also, in the payment device 12-1 that has received the execution event, the data of the second transaction file 811 is transferred to the third transaction file 812 and the second transaction file 811 is cleared, so that it can receive an input event for the next customer.

[0128] Therefore, when data related to a transaction for a second customer "Customer Q" is input in input device 11-1, an input event including the data related to the transaction is transmitted to payment device 12-1 and payment device 12-2 by multicast communication. Similarly, when an input completion button BAf is pressed in input device 11-1, a completion event is transmitted to payment device 12-1 and payment device 12-2 by multicast communication.

[0129] At this time, if "Customer P" has not yet completed the payment, that is, if the status flag F of the payment device 12-1 is "1", a transaction impossible event is sent from the payment device 12-1 to the input device 11-1. On the other hand, in the payment device 12-2, whose status flag F is "0", the transaction start screen SBa is displayed on the touch panel 38. Customer "Customer Q" then moves to the location where the payment device 12-2 is installed and inputs the start button BBa of the transaction start screen SBa displayed on the touch panel 38.

[0130] When the start button BBa is pressed, a transaction start event is sent from the payment device 12-2 to the input device 11-1. Then, the input device 11-1, which has received the transaction start event, sends an execution event to the payment device 12-2. On the other hand, a deletion event is sent to the payment device 12-2.

[0131] In the payment device 12-2 that has received the execution event, the payment screen SBb is displayed on the touch panel 38. Thus, "Customer Q" can operate the payment device 12-2 to make the payment. On the other hand, in the payment device 12-2 that has received the deletion event, when "Customer P" has completed the payment, the screen of the touch panel 38 becomes the standby screen.

[0132] As described above in detail, input device 11 simply transmits transaction-related data to multiple payment devices 12 via multicast communication, and does not generate payment information including details of the sold and purchased items and total information. Therefore, it is possible to provide an accounting system 100 in which a clerk 2 and a customer 3 can share the operations to settle a transaction without input device 11 generating and transmitting payment information to payment device 12.

[0133] <Second embodiment> In the first embodiment, an example is shown in which two payment devices 12 arranged in one checkout lane execute payment processing for a transaction processed by one input device 11 arranged in the same checkout lane. In the second embodiment, an example is shown in which one of the two payment devices 12 executes payment processing for a transaction processed not only by an input device 11 arranged in the same checkout lane, but also by an input device 11 arranged in an adjacent checkout lane.

[0134] 18 is a schematic diagram showing the overall configuration of a transaction system 200 according to the second embodiment. Like the transaction system 100 according to the first embodiment, the transaction system 200 also includes an input device 11, a payment device 12, a server 13, and a network 14 that connects these together.

[0135] However, there are three payment devices 12 for two input devices 11. In the second embodiment, the multiple payment devices 12 that form the same group as input device 11-1 are payment device 12-1 and payment device 12-2. The multiple payment devices 12 that form the same group as input device 11-2 are payment device 12-3 and payment device 12-2. In other words, payment device 12-2 is a multi-purpose machine that can settle transactions in which transaction-related data has been input by the two input devices 11-1 and 11-2, respectively.

[0136] The operation of the payment device 12-1 and the payment device 12-3 that are not a shared machine is the same as that of the first embodiment. Therefore, the description here is omitted. On the other hand, the payment device 12-2 that is a shared machine has a part of the functional configuration of the processor 31 that is different. Therefore, the following describes the payment device 12-2.

[0137] 19 is a block diagram showing the main functional configuration of the processor 31 of the settlement device 12-2. The processor 31 has functions as a settlement side storage means 711, a waiting means 721, a fourth transmission means 731, a fifth transmission means 741, a settlement means 751, a settlement side deletion means 761, and a control means 771. The functions of the settlement side storage means 711, the waiting means 721, the fourth transmission means 731, the fifth transmission means 741, the settlement means 751, and the settlement side deletion means 761 are basically the same as the functions of the settlement side storage means 71, the waiting means 72, the fourth transmission means 73, the fifth transmission means 74, the settlement means 75, and the settlement side deletion means 76 in the first embodiment.

[0138] However, the settlement side storage means 711 stores the transaction-related data transmitted from the input device 11-1 or the input device 11-2 in different transaction files of the settlement side storage unit 81. The settlement side storage unit 81 has a second transaction file 813 and a third transaction file 814 as transaction files for storing the transaction-related data inputted by the input device 11-1. The settlement side storage unit 81 also has a second transaction file 815 and a third transaction file 816 as transaction files for storing the transaction-related data inputted by the input device 11-2. The settlement side storage means 711 stores the detail record Ra created based on the transaction-related data received from the input device 11-1 in the second transaction file 813 of the settlement side storage unit 81. The settlement side storage means 711 stores the detail record Ra created based on the transaction-related data received from the input device 11-2 in the second transaction file 815 of the settlement side storage unit 81.

[0139] The waiting means 721 is a function that waits for an accounting start declaration when a completion event is received from the input device 11 via the communication unit 35 while the transaction settlement is possible. When the waiting means 721 receives a completion event from each of the two input devices 11-1, 11-2, it waits for an accounting start declaration from each of the input devices 11-1, 11-2 that transmitted the completion event.

[0140] The fourth transmission means 731 is a function that transmits an accounting start event to the input device 11 in response to receiving an accounting start declaration. When the fourth transmission means 731 receives an accounting start declaration for the input device 11-1, it transmits an accounting start event to the input device 11-1. When the fourth transmission means 731 receives an accounting start declaration for the input device 11-2, it transmits an accounting start event to the input device 11-2.

[0141] The fifth transmission means 741 is a function of transmitting an unaccountable event when a completion event is received from the input device 11 via the communication unit 35 while settlement of the transaction is impossible. When the fifth transmission means 741 receives a completion event from the input device 11-1 while settlement of the transaction is impossible, it transmits an unaccountable event to the input device 11-1. When the fifth transmission means 741 receives a completion event from the input device 11-2 while settlement of the transaction is impossible, it transmits an unaccountable event to the input device 11-2.

[0142] The settlement means 751 has a function of settling a transaction based on the data relating to the transaction stored in the settlement side memory unit 81 when an execution event is received from the input device 11 via the communication unit 35. When the settlement means 751 receives an execution event from the input device 11-1, it settles the transaction based on the data relating to the transaction stored in the third transaction file 814. When the settlement means 751 receives an execution event from the input device 11-2, it settles the transaction based on the data relating to the transaction stored in the third transaction file 816.

[0143] The settlement side deletion means 761 is a function that clears the settlement side memory unit 81 and cancels the waiting state for the accounting start declaration when a deletion event is received from the input device 11 via the communication unit 35. When the settlement side deletion means 761 receives a deletion event from the input device 11-1, it clears the second transaction file 813. When the settlement side deletion means 761 receives a deletion event from the input device 11-2, it clears the second transaction file 815. When the control means 77 receives an accounting start declaration for any one of the input devices 11, it temporarily does not accept accounting start declarations for the other input devices 11. Then, when the settlement of the transaction by the settlement means 75 is completed, it has a function to resume waiting for accounting start declarations for the other input devices 11.

[0144] The control means 771 refers to the control table 83. As shown in FIG. 20, the control table 83 has a column for a transaction number, a column for a status, and a column for an input device ID. The transaction number and input device ID columns describe the transaction number and input device ID included in the completion event received from the input device 11. The status column describes a numerical value indicating the state of payment at the payment device 12-2 for the transaction with the corresponding transaction number. The payment state includes pre-payment, in-payment, and post-payment. In this embodiment, the numerical value of the status indicating pre-payment is set to "0". The numerical value of the status indicating in-payment is set to "1". The numerical value of the status indicating post-payment is set to "2". In the following, the transaction number, status, and input device ID described in the same row of each column are referred to as a control record.

[0145] If any of the statuses described in control table 83 is "0" at the time settlement of one transaction is completed, the control means 771 resumes waiting for an accounting start declaration for the input device 11 identified by the input device ID described in the same row as that status. For example, if the input device identified by the input device ID is input device 11-1, the control means 771 displays an image on the touch panel 38 for accepting an accounting start declaration for the input device 11-1. For example, if the input device identified by the input device ID is input device 11-2, the control means 771 displays an image on the touch panel 38 for accepting an accounting start declaration for the input device 11-2.

[0146] [Operation description of payment device 12-2] 21 is a flow chart showing the main steps of information processing executed by the processor 31 of the settlement device 12-1 in response to receiving an input event from the input device 11-1 or the input device 11-2. As described in the first embodiment, the input event includes an input event including a product code and an input event including a quantity, a discount amount, or a discount rate. The input event also includes an input device ID that identifies the input device 11-1 or the input device 11-2 that sent the input event.

[0147] When the processor 31 receives an input event, it first acquires an input device ID from the input event in ACT 301. Next, similar to the first embodiment, the processor 31 checks whether or not an input event including a product code has been received in ACT 302. If an input event including a product code has been received, the processor 31 creates a detail record Ra in ACT 303.

[0148] The processor 31, having created the detail record Ra, stores the detail record Ra in the second transaction file 813 or the second transaction file 815 as ACT304. Specifically, if the input device identified by the input device ID acquired in ACT301 is the input device 11-1, the processor 31 stores the detail record Ra in the second transaction file 813. If the input device identified by the input device ID acquired in ACT301 is the input device 11-2, the processor 31 stores the detail record Ra in the second transaction file 815.

[0149] On the other hand, even when an input event including a quantity, a discount amount, or a discount rate is received as ACT305, the processor 31 executes the same as in the first embodiment. That is, the processor 31 updates the detail record Ra of the record number r stored in the second transaction file 813 or the second transaction file 815 as ACT306. Specifically, if the input device specified by the input device ID acquired in ACT301 is the input device 11-1, the processor 31 updates the detail record Ra stored in the second transaction file 813. If the input device specified by the input device ID acquired in ACT301 is the input device 11-2, the processor 31 updates the detail record Ra stored in the second transaction file 815. With this, processor 31 ends the information processing performed when an input event is received.

[0150] 11 is a flow diagram showing the main steps of the information processing executed by the processor 31 of the settlement device 12-1 in response to receiving a completion event from the input device 11-1 or the input device 11-2. As described in the first embodiment, the completion event includes the input device ID and the transaction number.

[0151] Processor 31, which has received the completion event, acquires the input device ID from the completion event in ACT 311. Processor 31 also acquires the transaction number from the completion event in ACT 312.

[0152] Next, the processor 31 checks the status flag F in ACT313. If the status flag F is "1", that is, if the settlement of the transaction is not possible in the settlement device 12-2, the processor 31 proceeds to ACT314. The processor 31 controls the communication unit 35 to transmit an accounting impossible event to the input device 11 specified by the input device ID in ACT314. By this control, if the input device specified by the input device ID is the input device 11-1, a data signal of the accounting impossible event is transmitted from the communication unit 35 to the input device 11-1. If the input device specified by the input device ID is the input device 11-2, a data signal of the accounting impossible event is transmitted from the communication unit 35 to the input device 11-2. In the input device 11-1 or the input device 11-2 that receives the data signal of the accounting impossible event, information processing of the procedure shown in ACT132 to ACT135 of FIG. 9 is executed.

[0153] On the other hand, if the status flag F is "0", that is, if a completion event is received in an idle state where settlement of the transaction is possible, the processor 31 proceeds to ACT315. The processor 31 adds a control record to the control table 83 as ACT315. Specifically, the processor 31 adds to the control table 83 a control record consisting of the input device ID acquired in the processing of ACT311, the transaction number acquired in the processing of ACT312, and a status of "0" indicating before settlement, as shown in the control table 83-1 of Fig. 20.

[0154] Incidentally, control table 83-1 shows a case in which a completion event including an input device ID "1000" and a transaction number "1001" is received from input device 11-1, and further a completion event including an input device ID "2000" and a transaction number "2001" is received from input device 11-2.

[0155] After adding the control record, the processor 31 proceeds to ACT 316. In ACT 316, the processor 31 displays the transaction start screen SBc (see FIG. 24) on the screen of the touch panel 38.

[0156] Figure 24 is an example of the display of the transaction start screen SBc when the control record stored in the control table 83 is in the state of control table 83-1 in Figure 20. Note that input device 11-1 is represented as the "cash register number 1," and input device 11-2 is represented as the "cash register number 2." The transaction start screen SBc has a start button BBg for the "cash register number 1," that is, the input device 11-1, and a start button BBh for the "cash register number 2," that is, the input device 11-2.

[0157] After displaying the transaction start screen SBc, the processor 31 proceeds to ACT317. The processor 31 checks whether a completion event has been received in ACT317. If a completion event has not been received, the processor 31 proceeds to ACT318. The processor 31 checks whether the start button BBg or the start button BBh has been pressed in ACT318. If the start button BBg or the start button BBh has not been pressed, the processor 31 proceeds to ACT319. The processor 31 checks whether a delete event has been received in ACT319. If a delete event has not been received, the processor 31 returns to ACT317. After displaying the transaction start screen SBc in this manner, the processor 31 waits for a completion event to be received, for the start button BBg or the start button BBh to be pressed, or for a delete event to be received.

[0158] When a completion event is received in the standby state of ACT317 and ACT319, the processor 31 returns to ACT311. The processor 31 executes the processing from ACT311 onwards in the same manner as described above. Although the explanation is out of order, the processing at this time would normally cause a second control record to be written to the control table 83. As a result, the accounting start screen SBc shown in FIG. 24 is displayed. If only the first control record is written in the control table 83, one start button is displayed on the accounting start screen SBc. For example, if only a control record including the input device ID of the input device 11-1 is written, an accounting start screen SBc with only the start button BBg arranged thereon is displayed. For example, if only a control record including the input device ID of the input device 11-2 is written, an accounting start screen SBc with only the start button BBh arranged thereon is displayed.

[0159] In the standby state of ACT317 and ACT319, when a deletion event is received, the processor 31 proceeds to ACT320. As described in the first embodiment, the deletion event includes an input device ID. The processor 31 acquires the input device ID from the deletion event as ACT320. Then, the processor 31 clears the second transaction file related to the input device identified by the input device ID as ACT321. Specifically, when the input device identified by the input device ID is the input device 11-1, the processor 31 clears the second transaction file 813. When the input device identified by the input device ID is the input device 11-2, the processor 31 clears the second transaction file 815. Also, receiving the deletion event means that the transaction will be settled by another settlement device 12. Therefore, the processor 31 changes the status described in the control table 83 in association with the input device ID as ACT322 from the unprocessed numerical value "0" to the settled numerical value "2". With this, the processor 31 ends the completion event receiving process.

[0160] If the start button BBg or start button BBh is pressed during the standby state of ACT317 to ACT319, the processor 31 proceeds to ACT323. The processor 31 erases the transaction start screen SBc that was displayed on the touch panel 38 in ACT323. By erasing the transaction start screen SBc, transaction start declarations to other input devices 11 are temporarily not accepted. After erasing the transaction start screen SBc, the processor 31 proceeds to ACT331 in FIG. 23. The processor 31 acquires an input device ID in ACT331. That is, if the start button BBg is pressed, the processor 31 acquires the input device ID of the "register with register number 1," that is, the input device 11-1. If the start button BBh is pressed, the processor 31 acquires the input device ID of the "register with register number 2," that is, the input device 11-2.

[0161] Having acquired the input device ID, the processor 31 proceeds to ACT332. The processor 31 controls the communication unit 35 to send a transaction start event as ACT332. That is, when the processor 332 acquires the input device ID of the input device 11-1, it controls the communication unit 35 to send a transaction start event to the input device 11-1. When the processor 332 acquires the input device ID of the input device 11-2, it controls the communication unit 35 to send a transaction start event to the input device 11-2. Thus, in the input device 11-1 or input device 11-2 that has received the data signal of the transaction start event, information processing of the procedures shown in ACT127 to ACT131 in FIG. 9 is executed.

[0162] The processor 31 of the settlement device 12-2 that transmitted the accounting start event proceeds to ACT333. The processor 31 waits for an execution event in ACT333. When the processor 31 receives an execution event from the input device 11-1 or the input device 11-2 that transmitted the accounting start event, the processor 31 proceeds to ACT335. The processor 31 copies the data of the second transaction file to the third transaction file in ACT335. Then, the processor 31 clears the second transaction file in ACT336. That is, when the processor 31 receives an execution event from the input device 11-1, the processor 31 copies the data of the second transaction file 813 to the third transaction file 814 and clears the second transaction file 813. When the processor 31 receives an execution event from the input device 11-2, the processor 31 copies the data of the second transaction file 815 to the third transaction file 816 and clears the second transaction file 815.

[0163] After clearing the second transaction file 813 or the second transaction file 815, the processor 31 proceeds to ACT 336. In ACT 336, the processor 31 changes the status flag F from "0" to "1." In addition, the processor 31 updates the control table 83 in ACT 337. Specifically, the processor 31 changes the status associated with the input device ID of the input device 11 that is the sender of the execution event from the unprocessed value "0" to the settlement value "1."

[0164] The processor 31 displays the billing screen SBb (see FIG. 16) on the touch panel 38 in ACT 338. The billing screen SBb is the same as in the first embodiment. After displaying the billing screen SBb, the processor 31 waits for a payment method to be selected in ACT 339 and for the payment to be made using that payment method, as in the first embodiment. Once the payment has been made, the processor 31 executes payment processing using the selected payment method in ACT 340. The payment processing is also the same as in the first embodiment, so a description thereof will be omitted here.

[0165] After completing the settlement process, the processor 31 proceeds to ACT341. In ACT341, the processor 31 clears the third transaction file. That is, if the input device 11 that is the source of the execution event is the input device 11-1, the processor 31 clears the third transaction file 814. If the input device 11 that is the source of the execution event is the input device 11-2, the processor 31 clears the third transaction file 816.

[0166] Next, the processor 31 updates the control table 83 as ACT342. Specifically, the processor 31 changes the status associated with the input device ID of the input device 11 that is the source of the execution event from the value "1" indicating that payment is in progress to the value "2" indicating that payment has been completed.

[0167] The processor 31 changes the status flag F from "1" to "0" in ACT343. The processor 31 then refers to the control table 83 to check whether or not there is an unprocessed control record. If the status is "0", in other words, if there is an unprocessed control record, the processor 31 returns to ACT316 in FIG. 22. The processor 31 sets the screen of the touch panel 38 to the transaction start screen SBc in ACT316. Thereafter, the processor 31 executes the processes from ACT317 onwards in the same manner as described above. For example, if the status of the control record including the input device ID of the input device 11-1 is "0", the transaction start screen SBc on which only the start button BBg is arranged is displayed. For example, if the status of the control record including the input device ID of the input device 11-2 is "0", the transaction start screen SBc on which only the start button BBh is arranged is displayed.

[0168] On the other hand, if there is no unprocessed control record in ACT344, the processor 31 ends the completion event receiving process.

[0169] Here, the processor 31 realizes the function of the settlement side storage means 711 by the processing of ACT304 and ACT306. The processor 31 realizes the function of the waiting means 721 by the processing of ACT316 to ACT319. The processor 311 realizes the function of the fourth transmission means 731 by the processing of ACT331 and ACT332. The processor 31 realizes the function of the fifth transmission means 741 by the processing of ACT314. The processor 31 realizes the function of the settlement means 751 by the processing of ACT338 to ACT340. The processor 31 realizes the function of the settlement side deletion means 761 by the processing of ACT320 and ACT321. The processor 31 realizes the function of the control means 774 by the processing of ACT322 and ACT344.

[0170] [Explanation of the accounting system's function] 25 is a sequence diagram of various events transmitted and received between two input devices 11-1 and 11-2 and one payment device 12-2. First, it is assumed that the payment device 12-2 is in an idle state and a standby screen is displayed on the touch panel 38.

[0171] Each time data related to a transaction, such as the product code, quantity, discount amount or discount rate of a product purchased by customer "Customer P," is input to one input device 11-1, an input event including the data related to the transaction is transmitted to payment devices 12-1 and 12-2 by multicast communication. In payment device 12-1, data in second transaction file 811 is updated based on the data related to the transaction included in the input event. In payment device 12-2, data in second transaction file 813 is updated based on the data related to the transaction included in the input event.

[0172] Each time data related to a transaction, such as the product code, quantity, discount amount or discount rate of a product purchased by customer "Customer Q", is input to the other input device 11-1, an input event including the data related to the transaction is transmitted to payment device 12-3 and payment device 12-2 by multicast communication. In payment device 12-3, data in second transaction file 811 is updated based on the data related to the transaction included in the input event. In payment device 12-2, data in second transaction file 815 is updated based on the data related to the transaction included in the input event.

[0173] When the input of data of the product to be purchased by the customer "Customer P" is completed in the input device 11-1 and the input completion button BAf is pressed, a completion event is sent to the payment device 12-1 and the payment device 12-2 by multicast communication. At almost the same time, when the input of data of the product to be purchased by the customer "Customer Q" is completed in the input device 11-1 and the input completion button BAf is pressed, a completion event is sent to the payment device 12-3 and the payment device 12-2 by multicast communication. As a result, the payment device 12-1 displays a transaction start screen SBa on the touch panel 38, on which a start button BBa for the customer "Customer P" to operate is arranged. The payment device 12-3 displays a transaction start screen SBa on the touch panel 38, on which a start button BBa for the customer "Customer Q" to operate is arranged. The payment device 12-2 displays a transaction start screen SBc on which a start button BBg for the customer "Customer P" to operate and a start button BBh for the customer "Customer P" to operate are arranged. At this time, the control record shown in the control table 83-1 of FIG. 20 is written in the control table 83 of the settlement device 12-2.

[0174] Now, suppose that customer "Customer P" moves to the location where payment device 12-2 is installed and presses the start button BBg on the transaction start screen SBc displayed on touch panel 38. This causes a transaction start event to be sent from payment device 12-2 to input device 11-1. Then, input device 11-1, which has received the transaction start event, sends an execution event to payment device 12-2. On the other hand, a deletion event is sent to payment device 12-1.

[0175] In the payment device 12-2 that has received the execution event, the billing screen SBb is displayed on the touch panel 38. Thus, the customer "Customer P" can operate the payment device 12-2 to make the payment. At this time, the control record shown in the control table 83-2 of FIG. 20 is written in the control table 83 of the payment device 12-2. Meanwhile, in the payment device 12-1 that has received the deletion event, the second transaction file 811 is cleared and a standby screen is displayed on the touch panel 38.

[0176] When the payment process is completed in the payment device 12-2, the control record shown in the control table 83-3 of Fig. 20 is written in the control table 83. Therefore, in the payment device 12-2, a transaction start screen SBc is displayed on the touch panel 38, on which a start button BBh is arranged for the customer "Customer Q" to operate.

[0177] Now, assume that customer "Customer Q" moves to the location where payment device 12-2 is installed and presses the start button BBh on the transaction start screen SBc displayed on touch panel 38. This causes a transaction start event to be sent from payment device 12-2 to input device 11-2. Then, input device 11-2, which has received the transaction start event, sends an execution event to payment device 12-2. On the other hand, a deletion event is sent to payment device 12-3.

[0178] In the payment device 12-2 that has received the execution event, the accounting screen SBb is displayed on the touch panel 38. Thus, the customer "Customer Q" can operate the payment device 12-2 to make the payment. At this time, the control record shown in the control table 83-4 of FIG. 20 is written in the control table 83 of the payment device 12-2. Meanwhile, in the payment device 12-3 that has received the deletion event, the second transaction file 811 is cleared and a standby screen is displayed on the touch panel 38.

[0179] When the payment process is completed in the payment device 12-2, the control record shown in the control table 83-5 of Fig. 20 is written in the control table 83. Therefore, the standby screen is also displayed in the payment device 12-2.

[0180] In the second embodiment, which functions in this manner, as in the first embodiment, an accounting system 100 can be provided in which a store clerk 2 and a customer 3 can share the operations to settle a transaction, without the input device 11 generating payment information and sending it to the payment device 12.

[0181] Moreover, according to the second embodiment, there is an advantage that the number of payment devices 12 capable of processing the payment of a transaction processed by one input device 11 can be increased without installing additional payment devices 12.

[0182] [Other embodiments] In the above embodiment, the input device 11 issues a transaction number and transmits it to the payment device 12 together with the completion event. In another embodiment, the payment device 12 that receives the completion event may issue the transaction number. In this case, for multiple payment devices 12 arranged in the same checkout lane, it is preferable to prevent the transaction numbers issued by each payment device 12 from overlapping by, for example, assigning different values ​​to the most significant digit of the transaction number.

[0183] Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented 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 invention and its equivalents described in the claims. [Explanation of symbols]

[0184] 2... store clerk, 3... customer, 11 (11-1, 11-2)... input device, 12 (12-1, 12-2, 12-3, 12-4) payment device, 13... server, 14... communication network, 21, 31... processor, 28, 38... touch panel, 51... input side storage means, 52... first transmission means, 53... statement display means, 54... end detection means, 55 second transmission means, 56... third transmission means , 57...input side deletion means, 63...input side memory unit, 64...status table, 71, 711...payment side memory means, 72, 721...standby means, 73, 731...fourth transmission means, 74, 741...fifth transmission means, 75, 751...payment means, 76, 761...payment side deletion means, 81...payment side memory unit, 83...control table, 100, 200...accounting system, 771...control means.

Claims

1. an input device for inputting data relating to a transaction via an input device and a plurality of settlement devices for settling the transaction for which data has been input via the input device are connected by a communication line; The input device is end detection means for detecting an instruction to end input of data relating to the transaction; a first transmission means for transmitting the data related to the transaction input via the input device to each of the plurality of payment devices before the end detection means detects an instruction to end the input of the data related to the transaction; a second transmission means for transmitting a completion event notifying each of the plurality of settlement devices of completion of input of the transaction data when the completion detection means detects an instruction to end input of the transaction data; a third transmission means for, when receiving a transaction start event declaring the start of a transaction from any one of the plurality of payment devices that have transmitted the completion event, transmitting an execution event to the one of the payment devices that transmitted the transaction start event, permitting the execution of the transaction, and transmitting a deletion event to the other payment devices instructing them to delete data related to the transaction; Equipped with The plurality of payment devices a storage means for storing data relating to the transaction transmitted from the input device in a storage unit; a waiting means for waiting for a statement of start of accounting when the completion event is received from the input device in a state where the transaction can be settled; a fourth transmission means for transmitting the accounting start event to the input device in response to receiving the accounting start declaration; a settlement means for settling a transaction based on the transaction data stored in the storage unit when the execution event is received from the input device; a deletion means for clearing the storage unit and canceling the waiting state for the accounting start declaration when the deletion event is received from the input device; An accounting system that includes:

2. 2. The accounting system according to claim 1, wherein the waiting means waits for the accounting start declaration by displaying on a display device an image for accepting the accounting start declaration, together with a payment amount calculated from the transaction data stored in the memory unit.

3. The payment device, a fifth transmission means for transmitting, when the completion event is received from the input device in a state in which settlement of the transaction is impossible, a transaction impossible event notifying the input device that settlement is impossible; Further comprising: The input device is a notification means for notifying the user that a transaction is not possible when the transaction impossibility event is received from all of the payment devices that have transmitted the completion event; 2. The accounting system of claim 1, further comprising:

4. At least one of the plurality of payment devices is capable of receiving data related to the transaction and a completion event from two or more of the input devices; The one payment device, As the storage means, the data relating to the transaction transmitted from each of the two or more input devices is stored in a storage unit for each input device, as the waiting means, when the completion event is received from the two or more input devices in a state in which settlement of the transaction is possible, waiting for a statement of start of accounting for each input device that has transmitted the completion event; as the fourth transmission means, in response to receiving an accounting start declaration for any one of the input devices, transmitting an accounting start event to the one input device; as the settlement means, when the execution event is received from the input device that transmitted the transaction start event, settling the transaction based on the transaction-related data stored in the storage unit for each input device; An accounting system as described in any one of claims 1 to 3, wherein the deletion means, when receiving the deletion event from another input device that has not transmitted the accounting start event, deletes the transaction-related data stored in the memory unit for that other input device, and cancels the standby state for the accounting start declaration for that other input device.

5. The one payment device, a control means for temporarily not accepting an accounting start declaration for the other input devices when an accounting start declaration for any one of the input devices is accepted, and for resuming waiting for an accounting start declaration for the other input devices when the settlement of the transaction by the settlement means is completed; 5. The accounting system of claim 4, further comprising:

6. an input device for inputting data relating to a transaction via an input device and a plurality of settlement devices for settling the transaction for which data has been input via the input device are connected by a communication line; The input device is end detection means for detecting an instruction to end input of data relating to the transaction; a first transmission means for transmitting the data related to the transaction input via the input device to each of the plurality of payment devices before the end detection means detects an instruction to end the input of the data related to the transaction; a second transmission means for transmitting a completion event notifying each of the plurality of settlement devices of completion of input of the transaction data when the completion detection means detects an instruction to end input of the transaction data; a third transmission means for, when receiving a transaction start event declaring the start of a transaction from any one of the plurality of payment devices that have transmitted the completion event, transmitting an execution event to the one of the payment devices that transmitted the transaction start event, permitting the execution of the transaction, and transmitting a deletion event to the other payment devices instructing them to delete data related to the transaction; The settlement device of the accounting system comprising: a storage means for storing data relating to the transaction transmitted from the input device in a storage unit; a waiting means for waiting for a statement of start of accounting when the completion event is received from the input device in a state where the transaction can be settled; a fourth transmission means for transmitting the accounting start event to the input device in response to receiving the accounting start declaration; a settlement means for settling a transaction based on the transaction data stored in the storage unit when the execution event is received from the input device; a deletion means for clearing the storage unit and canceling the waiting state for the accounting start declaration when the deletion event is received from the input device; A payment device comprising:

7. an input device for inputting data relating to a transaction via an input device and a plurality of settlement devices for settling the transaction for which data has been input via the input device are connected by a communication line; The input device is end detection means for detecting an instruction to end input of data relating to the transaction; a first transmission means for transmitting the data related to the transaction input via the input device to each of the plurality of payment devices before the end detection means detects an instruction to end the input of the data related to the transaction; a second transmission means for transmitting a completion event notifying each of the plurality of settlement devices of completion of input of the transaction data when the completion detection means detects an instruction to end input of the transaction data; a third transmission means for, when receiving a transaction start event declaring the start of a transaction from any one of the plurality of payment devices that have transmitted the completion event, transmitting an execution event to the one of the payment devices that transmitted the transaction start event, permitting the execution of the transaction, and transmitting a deletion event to the other payment devices instructing them to delete data related to the transaction; A computer of the settlement device of an accounting system comprising: A storage means for storing data relating to the transaction transmitted from the input device in a storage unit; a waiting means for waiting for a statement of start of accounting when the completion event is received from the input device in a state in which settlement of the transaction is possible; a fourth transmission means for transmitting the accounting start event to the input device in response to receiving the accounting start declaration; a settlement means for settling a transaction based on the transaction data stored in the storage unit when the execution event is received from the input device; and a deletion means for clearing the storage unit and canceling the waiting state for the accounting start declaration when the deletion event is received from the input device; A program to function as a

Images