Accounting system, input device, payment device, and program

Abstract

To provide an accounting system that allows a clerk and a customer to divide operations to settle a transaction without generating settlement information in an input apparatus.SOLUTION: An input apparatus detects an input end instruction for data related to a transaction. The input apparatus transmits the data related to the transaction input through an input device to each of a plurality of settlement apparatuses before the input end instruction for the data related to the transaction is detected. When the input end instruction for the data related to the transaction is detected, the input apparatus notifies any one settlement apparatus of the plurality of settlement apparatuses of input end. The settlement apparatus stores the data related to the transaction transmitted from the input apparatus in a settlement-side storage unit until the transaction is settled. Upon receiving the notification of input end from the input apparatus in a state where the transaction can be settled, the settlement apparatus settles the transaction based on the data related to the transaction stored in the settlement-side storage unit.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] Embodiments of the present invention relate to an accounting system, an input device and a settlement device of this system, and further to programs for the input device and the settlement device respectively.

Background Art

[0002] In recent years, as an accounting system for general merchandise stores, a shared accounting system in which a store clerk and a customer share operations is known. This type of accounting system separates an input device that receives data input of products sold in each transaction and a settlement device that executes settlement processing of the transaction based on the product data input by this input device. Then, it is arranged such that the store clerk operates the input device and the customer operates the settlement device.

[0003] In the shared accounting system, since the store clerk performs the product data input operation, the time required for data input is shorter than that of the self-service accounting system in which the customer performs all operations by himself / herself. On the other hand, since the customer operates the settlement device, it is assumed that a customer who is not used to operating will have trouble with settlement. Therefore, generally, in the shared accounting system, a plurality of settlement devices are assigned to one input device.

[0004] In this type of conventional accounting system, when the store clerk finishes all data input of products sold in the transaction with the customer to the input device, settlement information is generated in the input device. The settlement information includes details information such as product codes, product names, unit prices, quantities, amounts, etc. of the sold products, and total information such as total number of items, total amount, etc. Then, since the settlement information is transmitted to any available settlement device, the store clerk guides the customer to that settlement device. Since the settlement device that has received the settlement information can perform settlement processing, the customer operates the settlement device to pay the price in cash, by credit card, electronic money, etc. Thus, the shared accounting system settles the transaction with the store clerk and the customer sharing the operations.

Prior Art Documents

Patent Documents

[0005] [Patent Document 1] Japanese Patent Publication No. 2013-242839 [Overview of the Initiative] [Problems that the invention aims to solve]

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

[0007] In one embodiment, the accounting system connects an input device that inputs transaction data via an input device with multiple settlement devices that settle transactions via a communication line. The input device comprises a completion detection means, a first transmission means, and a first notification means. The completion detection means detects an instruction to complete the input of transaction data. The first transmission means transmits the transaction data entered via the input device to each of the multiple settlement devices before the completion detection means detects an instruction to complete the input of the transaction data. When the completion detection means detects an instruction to complete the input of transaction data, the first notification means notifies one of the multiple settlement devices that the input has been completed. The settlement device comprises a settlement-side storage means and a settlement means. The settlement-side storage means stores transaction data transmitted from the input device in the settlement-side storage unit until the transaction is settled. When the settlement means receives notification from the input device that the input has finished when the transaction is ready for settlement, it settles the transaction based on the transaction data stored in the settlement-side storage unit. [Brief explanation of the drawing]

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

[0009] The following describes embodiments of an accounting system in which store clerks and customers can share the operation to settle transactions without generating payment information on an input device, in the order of the first embodiment, second embodiment, third embodiment, and fourth embodiment. First, the general configuration of the accounting system, the hardware configuration of the input device and the payment device, which are common to each embodiment, will be described using Figures 1 to 3.

[0010] Figure 1 is a schematic diagram showing the general configuration of accounting system 1. Accounting system 1 includes an input device 11, a settlement device 12, a server 13, and a network 14 connecting them. The type of network 14 is not particularly limited, but generally a wired or wireless LAN (local area network) is used.

[0011] The input device 11 is configured to accept data input for each transaction, specifically for the goods to be bought and sold in that transaction. The settlement device 12 is configured to perform settlement processing for a transaction based on the product data entered in the input device 11. In principle, the input device 11 is operated by a store clerk 2, who is in the role of a checker. In principle, the settlement device 12 is operated by a consumer, or customer 3, who purchases goods at the store. However, the operator of the input device 11 may also be customer 3. That is, customer 3 may operate both the input device 11 and the settlement device 12. Similarly, the operator of the settlement device 12 may also be store clerk 2. That is, store clerk 2 may operate both the input device 11 and the settlement device 12. In Figure 1, the input device 11 is attached to the work table 4. The work table 4 has a rectangular tabletop. Multiple work tables 4 are arranged so that the longitudinal directions of their tabletops are approximately parallel, forming a passageway for customers 3, a so-called checkout lane.

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

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

[0014] Furthermore, at least one settlement device 12 located in a single checkout lane may be capable of settling transactions processed by an input device 11 located in an adjacent checkout lane. For example, in Figure 1, settlement device 12(12-2) is capable of settling transactions processed not only by input device 11(11-1) but also by input device 11(11-2). Similarly, settlement device 12(12-3) is capable of settling transactions processed not only by input device 11(11-2) but also by input device 11(11-1). In this way, the number of settlement devices 12 capable of settling transactions processed by a single input device 11 can be increased without adding any additional settlement devices 12.

[0015] Of the multiple payment devices 12 placed in a single checkout lane, one is set as the master unit, and the others are set as slave units. For example, in Figure 1, assuming that payment devices 12(12-1) and 12(12-3) are set as master units, payment devices 12(12-2) and 12(12-4) are set as slave units. Incidentally, the slave payment device 12(12-2) monitors the status of the master payment device 12(12-1). Furthermore, if payment device 12(12-1) goes down due to a communication failure or malfunction, payment device 12(12-2) has a function to declare that it will become the master unit. Upon receiving this declaration, the input device 11(11-1) sets payment device 12(12-2) as the master unit. Similarly, the slave payment device 12(12-4) monitors the status of the master payment device 12(12-3). When payment device 12(12-3) goes down, payment device 12(12-4) has a function to declare that it will become the master device. Upon receiving this declaration, input device 11(11-2) sets payment device 12(12-4) as the master device. In the following explanation, when distinguishing between master and slave payment devices 12, the master payment device will be referred to as master device 121, and the slave payment device will be referred to as slave device 122.

[0016] 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 Server 13, or they may be stored in a storage device connected to an external device of Server 13.

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

[0018] A product code is a unique code assigned to each product to identify it. Typically, each product has a barcode or two-dimensional code that represents the product code. Alternatively, it may have an RFID (Radio Frequency Identification) tag that stores the product code. The input device 11 can input the product codes of products bought and sold in a transaction by reading the barcode, two-dimensional code, or RFID tag attached to the product with a reader.

[0019] Product name and unit price are the name of the product identified by the product code and the price per unit. Attributes include, for example, information regarding the product's taxation. Tax information includes the tax rate and tax type (external tax, internal tax, tax-exempt).

[0020] Sales Master File 132 is a data file that stores sales records created for each product sold in a store. Each sales record contains sales data such as the product code, product name, and unit price mentioned above, as well as the number of items sold and the total sales amount. The number of items sold is the total quantity sold for each product identified by its corresponding product code. The total sales amount is the total sales amount for each product identified by its corresponding product code.

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

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

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

[0024] Main memory 22 corresponds to the main memory portion of the computer described above. Main memory 22 includes non-volatile memory areas and volatile memory areas. In the non-volatile memory area, main memory 22 stores the operating system or application programs. Main memory 22 may also store data necessary for the processor 21 to perform processing to control each part in non-volatile or volatile memory areas. Main memory 22 uses the volatile memory area as a work area where data is rewritten as needed by the processor 21. The non-volatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

[0025] The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer described above. 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 in performing various processes, data created by the processing performed by the processor 21, etc. The auxiliary storage device 23 may also store the application programs described above.

[0026] The clock 24 measures the date and time. The processor 21 processes the date and time measured by the clock 24 as the current date and time. The communication unit 25 is an interface for data communication with the server 13 and multiple payment devices 12 connected via the network 14. The keyboard 26 is an input device with various keys necessary for inputting data related to the goods purchased by the customer, so-called purchased goods. 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 from the store clerk. The customer display 29 displays information to customer 3 whose purchased goods data has been entered into the input device 11.

[0027] An existing POS terminal can be used as an input device 11 with such hardware configuration. Note that the devices connected to the input device 11 are not limited to the keyboard 26, scanner 27, touch panel 28, and customer display 29. Additional devices may be added or some devices omitted depending on the application of the input device 11.

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

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

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

[0031] Main memory 32 corresponds to the main memory portion of the computer described above. Main memory 32 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, main memory 32 stores the operating system or application programs. Main memory 32 may also store data necessary for the processor 31 to perform processing to control each part in the non-volatile or volatile memory area. Main memory 32 uses the volatile memory area as a work area where data is rewritten as appropriate by the processor 31. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

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

[0033] The clock 34 measures the date and time. The processor 31 processes the date and time measured by the clock 34 as the current date and time. The communication unit 35 communicates data with the server 13 or input device 11 connected via the network 14. The change dispenser interface 36 forms an interface with an automatic change dispenser (not shown). The change dispenser interface 36 receives monetary data of the money inserted into the automatic change dispenser from the automatic change dispenser. The change dispenser interface 36 outputs change data from the payment device 12 to the automatic change dispenser. The automatic change dispenser, having received the change data, automatically dispenses the amount of money corresponding to that change data as change.

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

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

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

[0037] As a payment device 12 with such hardware configuration, for example, an existing self-service POS terminal, or so-called self-checkout terminal, can be used. Note that the devices connected to the payment device 12 are not limited to the scanner 37, touch panel 38, and printer 39. Additional devices may be added or some devices omitted depending on the application of the payment device 12.

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

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

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

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

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

[0043] The selection means 55 is a function that accepts input for selecting a payment method necessary for settling a transaction. The selection means 55 selects a payment method from among various payment methods, such as cash payment, credit card payment, and electronic money payment, based on the operation input to the input device 61.

[0044] The first notification means 56 has the function of notifying one of the settlement devices 120 in the same group of the completion of data input via the communication unit 25 when the completion detection means 53 detects the completion of data input related to a transaction. The first notification means 56 determines the recipient of the notification of completion of input by referring to the data table 64.

[0045] As shown in Figure 6, the data table 64 stores a master unit flag Fa associated with a payment device ID for individually identifying payment devices 120 in the same group. The master unit flag Fa is a 1-bit data for identifying whether the payment device 12 identified by the corresponding payment device ID is a master unit 121 or a slave unit 122. In this embodiment, the master unit flag Fa for master unit 121 is set to "1", and the master unit flag Fa for slave unit 122 is set to "0".

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

[0047] The second notification means 57, upon receiving a payment failure response signal from a payment device 12 that has been notified of the end of input by the first notification means 56, has the function of notifying other payment devices 12 that have not been notified of the end of input via the communication unit 25. For example, if the payment device 12 that has been notified of the end of input is the master unit 121, and the second notification means 57 receives a payment failure response from this master unit 121, the second notification means 57 refers to the data table 64 and outputs a signal to notify the payment device 12 set as the slave unit 122, that is, the payment device 12 identified by the payment device ID with master unit flag Fa set to "0", of the end of input. For example, if the payment device 12 that has been notified of the end of input is the slave unit 122, and the second notification means 57 receives a payment failure response from this slave unit 122, the second notification means 57 refers to the data table 64 and outputs a signal to notify the payment device 12 set as the master unit 121, that is, the payment device 12 identified by the payment device ID with master unit flag Fa set to "1", of the end of input.

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

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

[0050] The input-side deletion means 510 has the function of deleting transaction data stored in the input-side storage unit 63 when it receives a payment-ready response signal from the payment device 12, which has been notified of the end of input by the first notification means 56. When the input-side deletion means 510 receives a payment-ready response from the payment device 12, it deletes all the detail records Ra stored in the first transaction file 631 of the input-side storage unit 63. In other words, it clears the first transaction file 631. With the first transaction file 631 cleared, the input device 11 becomes able to input data related to the next customer's transaction.

[0051] The functions of the input-side storage means 51, detail display means 52, termination detection means 53, first transmission means 54, selection means 55, first notification means 56, second notification means 57, third notification means 58, settlement destination notification means 59, and input-side deletion means 510 described above are realized by information processing performed by the processor 21 according to a program for the input device 11, so-called input program.

[0052] The input program is a type of application program stored in the main memory 22 or the auxiliary storage device 23. The method of installing the input program in the main memory 22 or auxiliary storage device 23 is not particularly limited. The input program can be installed in the main memory 22 or auxiliary storage device 23 by recording it on a removable recording medium or by distributing it via communication over the network 14. The recording medium can take any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

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

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

[0055] The amount display means 72 is a function that displays the settlement amount of a transaction on the touch panel 38 when it receives notification from the input device 11 that input has finished and the transaction is ready for settlement. The settlement amount of a transaction is calculated from the amount of the detail record Ra stored in the second transaction file 811 and the value discount amount.

[0056] The settlement response means 73, upon receiving notification from the input device 11 that input has finished, has the function of responding to the input device 11 whether or not the transaction can be settled. The settlement response means 73 refers to the flag memory 82 to determine whether or not the transaction can be settled. If the settlement response means 73 determines that the transaction can be settled, it sends an affirmative response (OK) signal to the input device 11 via the communication unit 35. If the settlement response means 73 determines that the transaction cannot be settled, it sends a negative response (NG) signal to the input device 11 via the communication unit 35.

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

[0058] The status flag Fc is a 1-bit data that identifies whether the settlement device 12 is in standby mode or in the process of settlement. When a standby settlement device 12 outputs a signal from the input device 11 indicating the end of input, the settlement device 12 enters the settlement mode. When a transaction is being settled, the settlement device 12 is unable to settle the next transaction. When the settlement process is completed in a settlement device 12 that is in the process of settlement, the settlement device 12 enters standby mode. When in standby mode, the settlement device 12 is able to settle the next transaction. In other words, a standby settlement device 12 is a settlement device that is able to settle transactions. A settlement device 12 that is in the process of settlement is a settlement device that is unable to settle transactions. In this embodiment, the status flag Fc is set to "0" when the device is in standby mode, and the status flag Fc is set to "1" when the device is in the process of settlement.

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

[0060] The settlement means 74 has the function of settling a transaction based on the transaction data stored in the settlement-side storage unit 81 when it receives a signal from the input device 11 indicating the end of input when the transaction is ready for settlement. When the settlement means 74 receives a signal from the input device 11 indicating the end of input when the transaction is ready for settlement, it copies the data stored in the second transaction file 811 to the third transaction file 812 and clears the second transaction file 811. Then the settlement means 74 settles the transaction based on the data stored in the third transaction file 812. With the second transaction file 811 cleared, the settlement device 12 becomes able to accept data related to the next customer's transaction.

[0061] The payment method 74 settles the transaction using the payment method identified by the payment method identification data received along with a signal indicating the end of input. For example, if the payment method identified by the payment method identification data is cash payment, the payment method 74 performs the cash transaction settlement process via the automatic change dispenser connected to the change dispenser interface 36. If the payment method identified by the payment method identification data is credit card payment, the payment method 74 performs the credit card transaction settlement process via the cashless payment terminal 5 connected to the terminal interface 40. If the payment method identified by the payment method identification data is electronic money payment, the payment method 74 performs the electronic money transaction settlement process via the cashless payment terminal 5 connected to the terminal interface 40. Since the settlement processes for cash, credit card, and electronic money transactions are well-known, a detailed explanation is omitted.

[0062] The settlement-side deletion means 75 is a function that deletes transaction data stored in the settlement-side storage unit 81 when it receives notification of settlement completion from the input device 11. Receiving notification of settlement completion means that a signal notifying other settlement devices 12 in the same group of input completion has been output, and the input device 11 has received a signal from those settlement devices 12 indicating that settlement is possible. Therefore, the transaction data stored in the settlement-side storage unit 81 becomes unnecessary. When the settlement-side deletion means 75 receives a signal from the input device 11 notifying of settlement completion, it deletes all the detail records Ra stored in the second transaction file 811 of the settlement-side storage unit 81. In other words, it clears the second transaction file 811. As mentioned above, by clearing the second transaction file 811, the settlement device 12 becomes able to accept data related to the next customer's transaction.

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

[0064] The payment program is a type of application program stored in the main memory 32 or the auxiliary storage device 33. The method of installing the payment program in the main memory 32 or auxiliary storage device 33 is not particularly limited. The payment program can be installed in the main memory 32 or auxiliary storage device 33 by recording it on a removable recording medium or by distributing it via communication over the network 14. The recording medium can take any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

[0065] Next, the content and procedures of the main information processing performed in the input device 11 and settlement device 12 that constitute the accounting system 1 will be explained using the flowcharts in Figures 9 to 13 and the example screens in Figures 14 to 18. Note that the content and procedures of the information processing described below are examples only. The content and procedures can be modified as appropriate if similar effects can be achieved. Similarly, the example screens are also examples only. The content of the output text, the placement of images, the types and layouts of software keys, etc., can be modified as appropriate.

[0066] First, the essential steps of the information processing performed by the processor 21 of the input device 11 according to the input program will be explained using the flowcharts in Figures 9 to 11.

[0067] Customer 3 places the items they wish to purchase from the products displayed on the sales floor into a shopping basket or similar container and heads to the checkout lane. When Customer 3 arrives at the checkout lane, clerk 2, who is acting as the checker, declares the start of input to the input device 11. In response to this operation, processor 21 begins processing information according to the procedure shown in the flowcharts in Figures 9 to 11.

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

[0069] The details screen SAa also includes software keys for the subtotal button BAa, the discount button BAb, and the discount button BAc. The subtotal button BAa is an operator used to signal that the input of purchased items in a transaction has been completed. The discount button BAb is an operator used to signal a discount on the most recently entered purchased item in a transaction. The discount button BAc is an operator used to signal a discount on the most recently entered purchased item in a transaction. Incidentally, the price of an item is discounted when the operator presses the discount button BAb and enters the discount amount using the numeric keypad on keyboard 26. Similarly, the price of an item is discounted when the operator presses the discount button BAc and enters the discount rate using the numeric keypad on keyboard 26.

[0070] In ACT101, the processor 21 uses the customer display 29 as the customer details screen. The customer details screen is the details screen SAa with the software keys removed.

[0071] After confirming that the details screen SAa is displayed on the touch panel 28, clerk 2 operates the scanner 27 to read the barcode attached to the item purchased by customer 3. When the barcode is read by the scanner 27, the product code of the purchased item is entered into the input device 11. On the other hand, some products, such as fresh food, do not have barcodes. If an item does not have a barcode, clerk 2 displays a list of items without barcodes on the touch panel 28. The clerk then selects the item the customer will purchase from that list. Through this operation, the product code of the purchased item without a barcode is entered into the input device 11.

[0072] Returning to the explanation of Figure 9. The processor 21, displaying the details screen SAa, waits for the product code to be entered as ACT102. Once the product code is entered, the processor 21 proceeds from ACT102 to ACT103. The processor 21 sends an input event as ACT103 to the payment device 120 of the same group via multicast communication. The input event includes the product code entered from the scanner 27 or touch panel 28.

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

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

[0075] After updating the details screen SAa, processor 21 proceeds to ACT107. Processor 21 checks whether a product code has been entered as ACT107. If no product code has been entered, processor 21 proceeds from ACT107 to ACT108. Processor 21 checks whether quantity or value discount data has been entered as ACT108. If no quantity or value discount data has been entered, processor 21 proceeds from ACT108 to ACT109. Processor 21 checks whether the subtotal button BAa has been entered as ACT109. If the subtotal button BAa has not been entered, processor 21 returns from ACT109 to ACT107. In this way, after updating the details screen SAa, processor 21 enters a waiting state for product code, quantity or value discount data, and subtotal button BAa as ACT107 through ACT109.

[0076] When a product code is entered while in the waiting state for ACT107 to ACT109, the processor 21 returns from ACT107 to ACT103. Then the processor 21 executes the processing of ACT103 to ACT106 in the same manner as described above. That is, the processor 21 sends the input event to the settlement device 120 of the same group via 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 returns to the waiting state for ACT107 to ACT109.

[0077] In the waiting state of ACT107 to ACT109, if a quantity is entered using the numeric keypad and multiplication key on the keyboard 26, or if a discount amount or discount rate is entered using the discount button BAb or discount button BAc and the numeric keypad, the processor 21 proceeds from ACT108 to ACT110. The processor 21 sends an input event as ACT110 to the settlement device 120 of the same group via multicast communication. The input event includes the quantity, discount amount, or discount rate entered from the keyboard 26.

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

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

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

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

[0082] The processor 21, displaying the payment method selection screen SAb, waits as ACT122 for one of the payment methods to be selected. Although not shown in the diagram, if the back button BAg is pressed while in the ACT122 waiting state, the processor 21 returns the touch panel 28 screen to the previous details screen SAa. The processor 21 then enters the waiting state for ACT107 to ACT109.

[0083] When a payment method is selected in the standby state of ACT122 by inputting the cash button BAd, the credit button BAe, or the electronic money button BAf, the processor 21 proceeds to ACT123. The processor 21 obtains the payment type as ACT123. The payment type is payment method identification data that identifies the payment method selected. For example, if the cash button BAd is input, the processor 21 obtains the payment type "cash" as the payment method identification data. If the credit button BAe is input, the processor 21 obtains the payment type "credit" as the payment method identification data. If the electronic money button BAf is input, the processor 21 obtains the payment type "electronic money" as the payment method identification data. Having obtained the payment type, the processor 21 sets the touch panel 28 screen to the payment screen SAc (see Figure 16) as ACT124.

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

[0085] The Input Complete button BAj and the Busy button BAk are both operators used to indicate the completion of data entry related to a transaction. When instructing the master unit 121 of the same group of settlement devices 120 to complete input, the employee 2 presses the Input Complete button BAj alone. When instructing the slave unit 122 to complete input, the employee 2 presses the Busy button BAk and then the Input Complete button BAj. Here, the Input Complete button BAj functions as the first operator. The Busy button BAk functions as the second operator.

[0086] In ACT124, the processor 21 uses the customer display 29 as the customer payment screen. The customer payment screen is the payment screen SAc with the software key removed.

[0087] After confirming that the payment screen SAc is displayed on the touch panel 28, clerk 2 checks whether the main unit 121 is free. If the main unit 121 is free, clerk 2 presses the input completion button BAj. For example, if the previous customer was paying at the main unit 121, or if the customer appears to have finished paying but is lingering near the main unit 121 putting their change into their wallet, clerk 2 presses the busy button BAk and then the input completion button BAj.

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

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

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

[0091] Processor 21, which issued the transaction number, proceeds to ACT130. Processor 21 initializes the increment counter n to "0" as ACT130. Next, processor 21 checks the busy flag Fd as ACT131. If the busy flag Fd is "0", that is, if the input completion button BAj was pressed alone, processor 21 proceeds from ACT131 to ACT132. Processor 21 determines that the destination for sending the completion event is the master unit 121 as ACT132.

[0092] In contrast, if the busy flag Fd is "1", that is, if the busy button BAk is pressed and then the input complete button BAj is pressed, the processor 21 proceeds from ACT131 to ACT133. As ACT133, the processor 21 increments the increment counter n by "1". Also, as ACT134, the processor 21 determines that the destination for sending the completion event is the slave unit 122.

[0093] Thus, when the destination of the completion event is determined to be the master unit 121 in ACT132, or when the destination of the completion event is determined to be the slave unit 122 in ACT134, the processor 21 proceeds to ACT141 in Figure 11. As ACT141, the processor 21 increments the increment counter n by "1". Therefore, if the destination of the completion event is determined to be the master unit 121, the increment counter n becomes "1". If the destination of the completion event is determined to be the slave unit 122, the increment counter n becomes "2".

[0094] After incrementing the increment counter n, the processor 21 proceeds to ACT142. As ACT142, the processor 21 sends a completion event via unicast communication to the payment device 12 of the same group that has been determined as the destination. Specifically, if the destination is determined to be the master device 121 in ACT132, the processor 21 sends a completion event to the payment device 12 identified by the payment device ID in which the master device flag Fa is set to "1". If the destination is determined to be the slave device 122 in ACT134, the processor 21 sends a completion event to the payment device 12 identified by the payment device ID in which the master device flag Fa is set to "0". The completion event includes the payment type obtained in ACT123 and the transaction number issued in ACT129.

[0095] The processor 21 that sent the completion event proceeds to ACT143. The processor 21 waits for a response signal from the settlement device 12 as ACT143. When a settlement device 12 capable of settling the transaction receives the completion event, it sends an affirmative response (OK) signal. When a settlement device 12 that is not capable of settling the transaction receives the completion event, it sends a negative response (NG) signal.

[0096] Upon receiving a response signal, the processor 21 proceeds from ACT143 to ACT144. As ACT144, the processor 21 determines whether the response signal is an affirmative response (OK) or a negative response (NG). Upon receiving a negative response (NG) signal, the processor 21 proceeds from ACT144 to ACT145. As ACT145, the processor 21 checks whether the increment counter n has exceeded the number N of settlement devices 12 in the same group. If the increment counter n is "1", that is, if a completion event has been sent to the master device 121 but a negative response (NG) signal has been returned from the master device 121, the processor 21 proceeds from ACT145 to ACT146. As ACT146, the processor 21 determines that the destination for the completion event is the slave device 122. Then the processor 21 returns to ACT141 and executes the processing from ACT141 onwards in the same way as described above. That is, the processor 21 increments the increment counter n by another "1". The processor 21 also sends a completion event to the slave unit 122, which is identified by the payment device ID in which the master unit flag Fa is set to "0", and waits for a response signal.

[0097] In response to this, if the increment counter n in ACT145 is "2," meaning that a completion event was sent to the slave unit 122 but a negative response (NG) signal is returned from the slave unit 122, the processor 21 proceeds from ACT145 to ACT147. As ACT147, the processor 21 displays a screen on the touch panel 28 to notify the completion event transmission error. A resend button is displayed on this screen, so the store clerk who has confirmed the transmission error presses the resend button.

[0098] Upon reporting a transmission error, processor 21 proceeds from ACT147 to ACT148. Processor 21 waits for a retransmission command as ACT148. When the retransmission button is pressed, processor 21 returns from ACT148 to ACT130 in Figure 10 and executes the processing from ACT130 onward in the same manner as described above. In this case, the increment counter n becomes "0" in ACT130, and the completion event is sent to the master unit 121.

[0099] If an acknowledgment (OK) signal is received in ACT144, the processor 21 proceeds from ACT144 to ACT149. In ACT149, the processor 21 notifies the payment device 12 to which the completion event will be sent. For example, the processor 21 displays information indicating the payment device 12 on the touch panel 28. Upon seeing this display, the store clerk 2 instructs the customer 3 to make the payment at the payment device 12. The processor 21 may also display information indicating the payment device 12 on a portion of the customer payment screen displayed on the customer display 29. In this way, the customer 3 can find out which payment device 12 is available for payment.

[0100] The processor 21, having notified the destination payment device 12, proceeds to ACT 150. As ACT 150, the processor 21 sends a deletion event via unicast communication to the payment devices 120 in the same group other than the destination. That is, if the destination payment device 12 is the master unit 121, the processor 21 sends the deletion event to the slave unit 122, i.e., the payment device 12 identified by the payment device ID in which the master unit flag Fa is set to "0". If the destination payment device 12 is the slave unit 122, the processor 21 sends the deletion event to the master unit 121, i.e., the payment device 12 identified by the payment device ID in which the master unit flag Fa is set to "1".

[0101] Processor 21, which sent the delete event, proceeds to ACT151. Processor 21 clears the first transaction file 631 as ACT151. This clear deletes all detail records Ra that were stored in the first transaction file 631. With this, processor 21 finishes processing the information according to the input program.

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

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

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

[0105] Next, the essential information processing steps performed by the processor 31 of the payment device 12 in accordance with the payment program will be explained using the flowcharts in Figures 12 and 13. When the status flag Fc is "0", i.e., the payment device 12's processor 31 is in standby mode, it starts processing information according to the procedure shown in the flowcharts in Figures 12 and 13. First, the processor 31 sets the touch panel 38 screen as the standby screen SBa (see Figure 17) as ACT201.

[0106] Figure 17 shows an example of the standby screen SBa. The standby screen SBa is a screen that informs the operator that the device is on standby. The operator of the payment device 12 is, in principle, customer 3. Therefore, the standby screen SBa should display an image that customer 3 will not operate on its own. For example, it could be a screen that displays text such as "Welcome" or "Please wait," or a screen that displays an illustration such as the store's logo.

[0107] The processor 31, displaying the standby screen SBa, waits for an input event to be transmitted from the input device 11 as ACT202. In this waiting state, when an input event is received via the communication unit 35, the processor 31 proceeds from ACT202 to ACT203. The processor 31 checks whether or not it has received an input event containing a product code as ACT203.

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

[0109] The processor 31 that created the detail record Ra proceeds to ACT205. The processor 31 stores the detail record Ra in the second transaction file 811 as ACT205.

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

[0111] After completing the processing of ACT205 or ACT207, the processor 31 proceeds to ACT208. The processor 31 checks whether it has received the next input event as ACT208. If it has not received an input event, the processor 31 proceeds from ACT208 to ACT209. The processor 31 checks whether it has received a completion event as ACT209. If it has not received a completion event, the processor 31 proceeds from ACT209 to ACT210. The processor 31 checks whether it has received a deletion event as ACT210. If it has not received a deletion event, the processor 31 returns to ACT208. In this way, the processor 31 waits for input events, completion events, or deletion events as ACT208 through ACT210.

[0112] When an input event is received while in the waiting state for ACT208 to ACT210, the processor 31 returns from ACT208 to ACT203. The processor 31 then executes the processing from ACT203 onward in the same manner as described above. That is, when an input event containing a product code is received, the processor 31 creates a detail record Ra and stores that detail record Ra in the second transaction file 811. When an input event containing a quantity, discount amount, or discount rate is received, the processor 31 updates the detail record Ra with record number r, i.e., the detail record Ra stored in the second transaction file 811 in the processing of the previous ACT205. The processor 31 then returns to the waiting state for ACT208 to ACT210.

[0113] If a delete event is received while in the waiting state of ACT208 to ACT210, processor 31 proceeds from ACT210 to ACT211. Processor 31 clears the second transaction file 811 as ACT211. This clear deletes all detail records Ra stored in the second transaction file 811. After clearing the second transaction file 811, processor 31 terminates information processing according to the settlement program. Subsequently, processor 31 sets the touch panel 38 screen to the waiting screen SBa again as ACT201.

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

[0115] The processor 31, having obtained the payment type, proceeds to ACT223. As ACT223, the processor 31 checks whether the payment type is a cashless payment method. Cashless payment methods are "credit" or "electronic money". The payment type "cash" is not a cashless payment method.

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

[0117] Thus, if the payment type is "cash," or if the payment type is "credit" or "electronic money" and the connection flag Fb is "1," the processor 31 proceeds to ACT225. The processor 31 controls the communication unit 35 to send an acknowledgment (OK) to the input device 11 as ACT225. This control causes the payment device 12 to send an acknowledgment (OK) signal to the input device 11, which is the source of the completion event.

[0118] The processor 31, which controlled the transmission of the acknowledgment (OK), proceeds to ACT226. As ACT226, the processor 31 changes the status flag Fc of the flag memory 82 from "0" to "1". That is, the processor 31 stores information indicating that the settlement device 12 is in the process of settlement. The processor 31 also copies the data of the second transaction file 811 to the third transaction file 812 as ACT227. Then, as ACT228, the processor 31 clears the second transaction file 811. This clear deletes all the detail records Ra that were stored in the second transaction file 811.

[0119] After clearing the second transaction file 811, processor 31 proceeds to ACT229. As ACT229, processor 31 sets the touch panel 38 screen to the accounting screen SBb (see Figure 18) corresponding to the payment type.

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

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

[0122] Furthermore, customer 3, who wishes to change their payment method, presses the change button BBa. When the change button BBa is pressed, the payment method selection screen is displayed on the touch panel 38, and customer 3 selects their desired payment method. However, in payment devices 12 that are not connected to a cashless payment terminal 5, it is not possible to select cashless payment methods such as credit cards or electronic money.

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

[0124] Once payment is complete, processor 31 proceeds from ACT230 to ACT231. Processor 31 operates printer 39 as ACT231 to issue a transaction receipt. The transaction receipt prints the data of the detail record Ra stored in the third transaction file 812, which includes the name of the purchased item, quantity, unit price, and total amount. It also prints the total amount of the purchased items, the payment amount, the change amount, and the transaction number included in the completion event.

[0125] Processor 31, which issued the transaction receipt, proceeds to ACT232. Processor 31 processes the sales of the purchased goods based on the detail record Ra stored in the third transaction file 812 as ACT232. This sales process updates the number of purchased items and the sales amount stored in the sales master file 132.

[0126] After completing the sales processing for the purchased goods, processor 31 proceeds to ACT233. Processor 31 clears the third transaction file 812 as ACT233. This clear deletes the detail record Ra that was stored in the third transaction file 812.

[0127] After clearing the third transaction file 812, processor 31 proceeds to ACT234. As ACT234, processor 31 changes the status flag Fc from "1" to "0". That is, processor 31 stores information indicating that the settlement device 12 is in standby mode. With this, processor 31 finishes processing information according to the settlement program. After that, processor 31 again sets the touch panel 38 screen to standby screen SBa as ACT201.

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

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

[0130] This control causes the payment device 12 to send a negative response (NG) signal to the input device 11, the source of the completion event. The processor 31, which controlled the transmission of the negative response (NG), returns to ACT208 in Figure 12. The processor 31 returns to a state of waiting for input events, completion events, or deletion events.

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

[0132] This concludes the explanation of the main information processing performed by the processor 21 of the input device 11 and the processor 31 of the payment device 12. Next, we will explain the operation of the accounting system 1 based on this information processing.

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

[0134] Furthermore, in the input device 11, each time transaction data is entered, an input event containing the transaction data is sent to the settlement device 120 of the same group. As a result, the settlement device 120 also creates a detail record Ra and stores it in the second transaction file 811. However, the touch panel 38 screen is the standby screen SBa. The detail screen SAa is never displayed on the touch panel 38. Therefore, information about the purchased items of a customer whose data is being entered via the input device 11 cannot be seen by other customers from the screen of the settlement device 12.

[0135] After completing the input of transaction data, when clerk 2 presses the subtotal button BAa, the touch panel 28 screen changes to the payment method selection screen SAb. At this point, clerk 2 confirms the payment method with the customer and selects the customer's preferred payment method. For example, if customer 3 wants to pay in cash, clerk 2 presses the cash button BAd. For example, if customer 3 wants to pay by credit card, clerk 2 presses the credit button BAe. For example, if customer 3 wants to pay with electronic money, clerk 2 presses the electronic money button BAf.

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

[0137] When the input completion button BAj is pressed, a completion event is sent from the input device 11 to one of the payment devices 120 in the same group, namely payment device 12. Specifically, if the input completion button BAj is pressed alone, a completion event is sent to the master device 121. If the input completion button BAj is pressed together with the busy button BAk, a completion event is sent to the slave device 122. The completion event includes the payment type, which is the identification data of the payment method selected on the payment method selection screen SAb.

[0138] Upon receiving a completion event, the payment device 12 determines whether to send an acknowledgment (OK) or a denial (NG) based on the payment type included in the completion event and the values ​​of the connection flag Fb and the status flag Fc. Next, the cases in which the payment device 12 sends an acknowledgment (OK) and a denial (NG) will be explained in detail using Figures 19 to 34. Figures 19 to 34 are diagrams illustrating the response signals sent from payment devices 120 of the same group, namely payment devices 12(12-1) and 12(12-2), for each pattern of operation input to the payment method selection screen Sab and payment screen SAc of the input device 11(11-1).

[0139] Figures 19 to 22 show an example where payment device 12(12-1) connected to the cashless payment terminal 5 is set as the master unit 121, and payment device 12(12-2) not connected to the cashless payment terminal 5 is set as the slave unit 122. Figure 19 shows the case where both payment device 12(12-1) and payment device 12(12-2) are in standby mode. Figure 20 shows the case where payment device 12(12-1) is processing a payment and payment device 12(12-2) is in standby mode. Figure 21 shows the case where payment device 12(12-1) is in standby mode and payment device 12(12-2) is processing a payment. Figure 22 shows the case where both payment device 12(12-1) and payment device 12(12-2) are processing a payment.

[0140] In the example shown in Figure 19, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12(12-1) of the master unit 121. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

[0141] On the other hand, in the example in Figure 19, if the busy button BAk is entered after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-2) of the slave unit 122. At this time, the payment device 12(12-2) is in standby mode and can process payments. However, since the payment device 12(12-2) is not connected to the cashless payment terminal 5, it does not support cashless payments by credit card or electronic money. Therefore, when the payment device 12(12-2) receives a completion event that includes payment type [cash], it returns an affirmative response (OK) signal to the input device 11(11-1). However, when the payment device 12(12-2) receives a completion event that includes payment type [credit] or payment type [electronic money], it returns a negative response (NG) signal to the input device 11(11-1).

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

[0143] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-2) on the slave device 122. At this time, the payment device 12(12-2) is in standby mode and is therefore capable of processing payments. However, since the payment device 12(12-2) is not connected to the cashless payment terminal 5, it does not support cashless payments by credit card or electronic money. Therefore, if the payment device 12(12-2) receives a completion event that includes payment type [cash], it returns an affirmative response (OK) signal to the input device 11(11-1), but if it receives a completion event that includes payment type [credit] or payment type [electronic money], it returns a negative response (NG) signal to the input device 11(11-1).

[0144] On the other hand, in the example in Figure 20, if the busy button BAk is entered after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-2) of the slave unit 122. At this time, the payment device 12(12-2) is in standby mode and can process payments. However, since the payment device 12(12-2) is not connected to the cashless payment terminal 5, it does not support cashless payments by credit card or electronic money. Therefore, if the payment device 12(12-2) receives a completion event that includes payment type [cash], it returns an affirmative response (OK) signal to the input device 11(11-1), but if it receives a completion event that includes payment type [credit] or payment type [electronic money], it returns a negative response (NG) signal to the input device 11(11-1).

[0145] In the example shown in Figure 21, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12(12-1) of the master unit 121. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

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

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

[0148] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-2) on the slave device 122. At this time, the payment device 12(12-2) is also in the middle of a payment and is therefore unable to process the payment. Consequently, the payment device 12(12-2) returns a negative response (NG) signal to the input device 11(11-1) in response to the completion event.

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

[0150] In the examples shown in Figures 19 to 23, when the input device 11(11-1) receives a negative response (NG) signal from the slave unit 122, it notifies a transmission error. If a retransmission command is issued in response to this notification, the input device 11(11-1) retransmits a completion event to the master unit 121 or the slave unit 122.

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

[0152] In the example shown in Figure 23, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12(12-2) of the master unit 121. At this time, the payment device 12(12-2) is in standby mode and can process payments. However, since the payment device 12(12-2) is not connected to the cashless payment terminal 5, it does not support cashless payments by credit card or electronic money. Therefore, if the payment device 12(12-2) receives a completion event that includes payment type [cash], it returns an affirmative response (OK) signal to the input device 11(11-1), but if it receives a completion event that includes payment type [credit] or payment type [electronic money], it returns a negative response (NG) signal to the input device 11(11-1).

[0153] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-1) on the slave device 122. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an affirmative response (OK) signal to the input device 11(11-1) in response to a completion event that includes either payment type [credit] or payment type [electronic money].

[0154] On the other hand, in the example in Figure 23, if the busy button BAk is entered after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-1) of the slave unit 122. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

[0155] In the example in Figure 24, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12(12-2) of the master unit 121. At this time, the payment device 12(12-2) is in standby mode and can process payments. However, since the payment device 12(12-2) is not connected to the cashless payment terminal 5, it does not support cashless payments by credit card or electronic money. Therefore, if the payment device 12(12-2) receives a completion event that includes payment type [cash], it returns an affirmative response (OK) signal to the input device 11(11-1), but if it receives a completion event that includes payment type [credit] or payment type [electronic money], it returns a negative response (NG) signal to the input device 11(11-1).

[0156] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the settlement device 12(12-1) on the slave device 122. At this time, the settlement device 12(12-1) is in the middle of a settlement and is therefore unable to process the settlement. Consequently, the settlement device 12(12-1) returns a negative response (NG) signal to the input device 11(11-1) in response to the completion event.

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

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

[0159] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-1) on the slave device 122. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an affirmative response (OK) signal to the input device 11(11-1) in response to the completion event.

[0160] On the other hand, in the example in Figure 25, if the busy button BAk is entered after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-1) of the slave unit 122. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

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

[0162] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-1) on the slave device 122. At this time, the payment device 12(12-1) is also in the middle of a payment and is therefore unable to process the payment. Consequently, the payment device 12(12-1) returns a negative response (NG) signal to the input device 11(11-1) in response to the completion event.

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

[0164] In the examples shown in Figures 24 to 26, the input device 11(11-1) notifies a transmission error when it receives a negative response (NG) signal from the slave unit 122. If a retransmission command is issued in response to this notification, the input device 11(11-1) retransmits a completion event to the master unit 121 or the slave unit 122.

[0165] Figures 27 to 30 show an example where not only payment device 12(12-1) but also payment device 12(12-2) is connected to the cashless payment terminal 5, with payment device 12(12-1) set as the master unit 121 and payment device 12(12-2) set as the slave unit 122. Figure 27 shows the case where both payment device 12(12-1) and payment device 12(12-2) are in standby mode. Figure 28 shows the case where payment device 12(12-1) is processing a payment and payment device 12(12-2) is in standby mode. Figure 29 shows the case where payment device 12(12-1) is in standby mode and payment device 12(12-2) is processing a payment. Figure 30 shows the case where both payment device 12(12-1) and payment device 12(12-2) are processing a payment.

[0166] In the example shown in Figure 27, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12(12-1) of the master unit 121. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash payments but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

[0167] On the other hand, in the example in Figure 27, if the busy button BAk is entered after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-2) of the slave unit 122. At this time, the payment device 12(12-2) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-2) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-2) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

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

[0169] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-2) on the slave device 122. At this time, the payment device 12(12-2) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-2) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-2) returns an affirmative response (OK) signal to the input device 11(11-1) in response to the completion event.

[0170] On the other hand, in the example in Figure 28, if the busy button BAk is entered after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-2) of the slave unit 122. At this time, the payment device 12(12-2) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-2) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-2) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

[0171] In the example shown in Figure 29, if the input completion button BAj is pressed alone following the cash button BAd, credit button BAe, or electronic money button BAf, a completion event is sent to the payment device 12(12-1) of the master unit 121. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash payments but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

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

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

[0174] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-2) on the slave device 122. At this time, the payment device 12(12-2) is also in the middle of a payment and is therefore unable to process the payment. Consequently, the payment device 12(12-2) returns a negative response (NG) signal to the input device 11(11-1) in response to the completion event.

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

[0176] In the examples shown in Figures 27 to 30, the input device 11(11-1) notifies a transmission error when it receives a negative response (NG) signal from the slave unit 122. If a retransmission command is issued in response to this notification, the input device 11(11-1) retransmits a completion event to the master unit 121 or the slave unit 122.

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

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

[0179] On the other hand, in the example in Figure 31, if the busy button BAk is entered after the cash button BAd, credit button BAe, or electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-1) of the slave unit 122. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

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

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

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

[0183] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-1) on the slave device 122. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an affirmative response (OK) signal to the input device 11(11-1) in response to the completion event.

[0184] On the other hand, in the example in Figure 33, if the busy button BAk is entered after the cash button BAd, the credit button BAe, or the electronic money button BAf, and then the input completion button BAj is entered, the completion event is sent to the payment device 12(12-1) of the slave unit 122. At this time, the payment device 12(12-1) is in standby mode and is therefore capable of processing payments. Furthermore, since the payment device 12(12-1) is connected to the cashless payment terminal 5, it supports not only cash but also credit card or electronic money payments. Therefore, the payment device 12(12-1) returns an acknowledgment (OK) signal to the input device 11(11-1) in response to the completion event.

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

[0186] Upon receiving a negative response (NG) signal, the input device 11(11-1) changes the destination of the completion event to the slave device 122. The completion event is then sent to the payment device 12(12-1) on the slave device 122. At this time, the payment device 12(12-1) is also in the middle of a payment and is therefore unable to process the payment. Consequently, the payment device 12(12-1) returns a negative response (NG) signal to the input device 11(11-1) in response to the completion event.

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

[0188] In the examples shown in Figures 31 to 34, the input device 11(11-1) notifies a transmission error when it receives a negative response (NG) signal from the slave unit 122. If a retransmission command is issued in response to this notification, the input device 11(11-1) retransmits the completion event to the master unit 121 or the slave unit 122.

[0189] As described in detail above, according to the first embodiment, the input device 11 does not generate settlement information including detailed information and total information of the goods bought and sold and transmit it to the settlement device 12, and a settlement system 1 can be provided in which the store clerk 2 and the customer 3 share the operation and settle the transaction.

[0190] Furthermore, even if, for example, the master unit 121 is in the middle of a settlement and cannot process the settlement, if the slave unit 122 is in standby mode and can process the settlement, customer 3 can settle the transaction using the slave unit 122. In this case as well, the input device 11 does not need to generate settlement information and send it to the slave unit 122.

[0191] Furthermore, for example, when a child unit 122 receives a deletion event in order for settlement processing to be executed on the master unit 121, the detail record Ra stored in the second transaction file 811 is discarded. Therefore, the child unit 122 can immediately prepare for the settlement of the next customer.

[0192] Furthermore, the input device 11 sends a completion event to the master unit 121 when the input completion button BAj is pressed alone, but sends a completion event to the slave unit 122 when the input completion button BAj and the busy button BAk are pressed together. For example, if there is a customer 3 who has finished paying but is taking a long time to put the money in their wallet in front of the master unit 121, the employee 2 will press the busy button BAk and then the input completion button BAj. In this case, the completion event will be sent to the slave unit 122 and not to the master unit 121. Consequently, the completion event will be sent to the master unit 121 where the slow-moving customer is, and the payment amount of the next customer will not be displayed on the master unit 121's touch panel 38.

[0193] Furthermore, employee 2 inputs the payment method desired by customer 3 into input device 11. Upon receiving a completion event, payment device 12 then executes the payment process using that method. Therefore, the inconvenience of customer 3 having to specify the payment method at payment device 12 is eliminated.

[0194] Furthermore, payment device 12, which is unable to process the payment using the payment method desired by customer 3, sends a negative response back to input device 11. Therefore, there is no risk of employee 2 directing customer 3 to payment device 12, which is unable to process the payment using the payment method desired by customer 3.

[0195] [Second Embodiment] Next, a second embodiment will be described using Figures 35 to 44. The second embodiment adds a function to the accounting system 1 of the first embodiment that allows for retrospective modification of the data of purchased goods for a single transaction entered into the input device 11 before the input completion instruction, which is input by the input completion button BAj, is given. Therefore, the same reference numerals are used for parts common to the first embodiment, and detailed explanations are omitted.

[0196] Figure 35 is a block diagram showing the main functional configuration of the processor 21 of the input device 11. In addition to the input-side storage means 51, detail display means 52, completion detection means 53, first transmission means 54, selection means 55, first notification means 56, second notification means 57, third notification means 58, settlement destination notification means 59, and input-side deletion means 510, the processor 21 also functions as a modification acceptance means 511, an input-side modification means 512, and a second transmission means 513.

[0197] The modification acceptance means 511 is a function that accepts modifications to the detail information displayed on the detail screen SAa of the touch panel 28 via the detail display means 52. In the detail area AAb of the detail screen SAa, the product name, quantity, unit price, discount amount, and total amount of the products entered as purchased items in a single transaction are displayed in a list format in the order of a series of record numbers. The modification acceptance means 511 accepts deletion of detail record Ra in the detail area AAb where the product name, quantity, unit price, etc. are displayed, or changes to the quantity, unit price, discount amount, discount rate, etc.

[0198] The input-side modification means 512 is a function that modifies the transaction data transmitted to each of the settlement devices 120 of the same group by the first transmission means 54 before the termination detection means 53 detects an instruction to end the input of the transaction data. The transaction data transmitted to multiple settlement devices 12 is stored in the first transaction file 631 as a detail record Ra. The input-side modification means 512 modifies the detail record Ra stored in the first transaction file 631 in response to input from the input device 61. For example, the input-side modification means 512 deletes the detail record Ra. For example, the input-side modification means 512 modifies the unit price, quantity, value discount amount, etc. of the detail record Ra.

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

[0200] Figure 36 is a block diagram showing the main functional configuration of the processor 31 of the payment device 12. In addition to the payment-side storage means 71, amount display means 72, payment response means 73, payment means 74, and payment-side deletion means 75, the processor 31 also functions as a payment-side modification means 76.

[0201] The settlement-side modification means 76 is a function that modifies transaction data stored in the settlement-side storage unit 81 using transaction data transmitted from the input device 11 by the second transmission means 513. The second transaction file 811 of the settlement-side storage unit 81 stores detail records Ra created by the settlement device 12 based on transaction data transmitted from the input device 11 by the first transmission means 54. The settlement-side modification means 76 modifies the detail records Ra stored in the second transaction file 811 with transaction data transmitted from the input device 11 by the second transmission means 513. For example, the settlement-side modification means 76 deletes detail records Ra. For example, the settlement-side modification means 76 modifies the unit price, quantity, value discount amount, etc. of detail records Ra.

[0202] Next, using the flowcharts in Figures 37 and 38, and the screen examples in Figures 39 to 44, the content and procedures of the information processing related to the second embodiment, among the information processing performed in the input device 11 and settlement device 12 that constitute the accounting system 1, will be explained. Note that the content and procedures of the information processing described below are examples. The content and procedures can be changed as appropriate if similar effects can be achieved. Also, the screen examples are examples. The content of the output text, the arrangement of images, the types and layouts of software keys, etc., can be changed as appropriate.

[0203] First, the essential steps of the information processing performed by the processor 21 of the input device 11 according to the input program will be explained using the flowchart in Figure 37. The flowchart in Figure 37 corresponds to the flowchart in Figure 9 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 9 and Figure 37.

[0204] Similar to the first embodiment, the processor 21 sets the touch panel 28 screen as the details screen SAa as ACT101. The processor 21 then waits for the product code to be entered as ACT102. Once the product code is entered, the processor 21 executes the processes of ACT103 to ACT106, and then enters a waiting state for ACT107 to ACT109. That is, the processor 21 enters a waiting state for the product code, quantity or value discount data, and the subtotal button BAa.

[0205] In this second embodiment, in addition to the product code, quantity or value discount data and the subtotal button BAa described above, the system waits for the product displayed in the detail area AAb of the detail screen SAa to be selected as ACT301.

[0206] Figure 39 shows an example of the display on the details screen SAa after data related to the transaction of four purchased items has been entered. Specifically, Figure 39 shows the details screen SAa when the product codes for product AAAAA (unit price 200 yen), product BBBBB (unit price 300 yen), product CCCCC (unit price 400 yen), and product DDDDD (unit price 100 yen) have been entered in order. With this input, the product name, quantity, and price of product DDDDD are displayed in the current area AAa. In the details area AAb, the product name, quantity, unit price, and price of product AAAAA are displayed in association with record number "1", the product name, quantity, unit price, and price of product BBBBB are displayed in association with record number "2", and the product name, quantity, unit price, and price of product CCCCC are displayed in association with record number "3". In the total area AAc, the total points of 4 and the total amount of 1,000 yen are displayed.

[0207] At this time, the first transaction file 631 stores the detail records Ra-A for product AAAAA, Ra-B for product BBBBB, Ra-C for product CCCCC, and Ra-D for product DDDDD as a result of the processing in ACT104 and ACT105. Furthermore, the processing in ACT106 sends input events containing the product code for product AAAAA, product BBBBB, product CCCCC, and product DDDDD to each of the settlement devices 120 in the same group. Each input event is sent to each of the settlement devices 120 in the same group each time a product code is entered. Upon transmission of these input events, the settlement device 120 of the same group will store the following detail records in the second transaction file 811: Ra-A for product AAAAA, Ra-B for product BBBBB, Ra-C for product CCCCC, and Ra-D for product DDDDD.

[0208] Let's return to the explanation of Figure 37. Let's assume, for example, that customer 3 requests to return product BBBBB while ACT107 to ACT109 and ACT301 are in standby mode. In this case, store clerk 2, who is the operator of input device 11, touches the row in detail area AAb that displays the data related to product BBBBB. As a result of touching the row in detail area AAb, processor 21 determines in ACT301 that a product has been selected.

[0209] If it determines that a product has been selected, the processor 21 proceeds from ACT301 to ACT302. As ACT302, the processor 21 displays the correction screen SAd (see Figure 40) on the touch panel 28.

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

[0211] After confirming the correction screen SAd, clerk 2 enters the cancel button BAn. When the cancel button BAn is entered, a strikethrough appears in the quantity, unit price, discount amount, and total amount of product BBBBB displayed in area AAg, as shown in Figure 41. In addition, the quantity change button BAo, unit price change button BAp, discount button BAq, and discount button BAr are grayed out and cannot be edited. If customer 3 decides not to return product BBBBB, clerk 2 enters the cancel button BAs. If customer 3 decides to confirm the return of product BBBBB, clerk 2 enters the OK button BAt.

[0212] Let's return to the explanation of Figure 37. The processor 21, which displays the correction screen SAd, checks whether the OK button BAt has been input as ACT303. If the OK button BAt has not been input, the processor 21 proceeds from ACT303 to ACT304. The processor 21 then checks whether the Cancel button BAs has been input as ACT304. If the Cancel button BAs has not been input, the processor 21 returns from ACT304 to ACT303. In this way, the processor 21, which displays the correction screen SAd, waits for either the OK button BAt or the Cancel button BAs to be input as ACT303 and ACT304.

[0213] If the cancel button BAs is pressed while ACT303 and ACT304 are in standby mode, the processor 21 proceeds from ACT304 to ACT305. The processor 21 then erases the correction screen SAd as ACT305. After that, the processor 21 returns to the standby mode of ACT107 to ACT109 and ACT301. In this way, when the store clerk 2 presses the cancel button BAs, the correction screen SCd is erased. As a result, the screen of the touch panel 28 becomes the details screen SAa shown in Figure 39.

[0214] On the other hand, if the OK button BAt is pressed while ACT303 and ACT304 are in standby mode, processor 21 proceeds from ACT303 to ACT306. Processor 21, as ACT306, sends a correction event to the settlement device 120 of the same group via multicast communication. The correction event includes the information entered for the correction screen SAd, which in this case is the information that product BBBBB has been canceled. Processor 21 also corrects the detail record Ra as ACT307. That is, processor 21 deletes the detail record Ra-B for product BBBBB stored in the first transaction file 631. Then, as ACT308, processor 21 clears the correction screen SAd and updates the detail screen SAa. After that, processor 21 returns to the standby mode of ACT107 to ACT109 and ACT301.

[0215] Figure 42 shows an example of the updated details screen SAa display after product BBBBB has been deleted. As shown in Figure 42, the product name, quantity, unit price, discount amount, and total amount of product BBBBB are removed from the details area AAb. The product name, quantity, unit price, discount amount, and total amount of product DDDDD, which were displayed in the current area AAa, are then displayed in the details area AAb. The product name, quantity, and total amount of product BBBBB are displayed in the current area AAa. A strikethrough is then displayed on the product name, quantity, and total amount in the current area AAa. This display allows employee 2 to confirm that product BBBBB has been deleted.

[0216] In the standby state of ACT107 to ACT109 and ACT301, let's consider a case where, for example, the quantity of product BBBBB needs to be changed from "1" to "3". In this case, clerk 2 touches the row in detail area AAb where the data for product BBBBB is displayed. This touch operation causes processor 21 to execute the process of ACT302. As a result of this process, the correction screen SAd is displayed on touch panel 28, and clerk 2 presses the quantity change button BAo. When the quantity change button BAo is pressed, as shown in Figure 43, the background color of the section in area AAg where the quantity is displayed is different from the background color of the other sections. This difference in background color allows clerk 2 to recognize that a quantity correction has been instructed. The cancel button BAn, unit price change button BAp, discount button BAq, and discount button BAr are grayed out and cannot be used. Having instructed the quantity correction, clerk 2 uses the numeric keypad on keyboard 26 to enter the corrected quantity "3" and presses the OK button BAt.

[0217] When the OK button BAt is pressed, processor 21 executes the processes of ACT306 to ACT308. Specifically, processor 21 sends a correction event to the settlement device 120 of the same group. The correction event includes the information entered on the correction screen SAd, which in this case is the information to correct the quantity of product BBBBB from "1" to "3". Processor 21 also corrects the detail record Ra. Specifically, processor 21 corrects the quantity in detail record Ra-B of product BBBBB stored in the first transaction file 631 from "1" to "3". Processor 21 also corrects the amount in detail record Ra-B from 300 yen to 900 yen. Then processor 21 updates the detail screen SAa.

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

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

[0220] These operations cause the processor 21 to execute the processes of ACT306 to ACT308. Specifically, the processor 21 sends a correction event to the settlement device 120 of the same group. The processor 21 also corrects the detail record Ra. Finally, the processor 21 updates the detail screen SAa.

[0221] Subsequently, when the subtotal button BAa is pressed, the processor 21 proceeds to ACT121 in Figure 10. Then, the processor 21 executes the processing from ACT121 onward, similar to the first embodiment.

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

[0223] Next, the essential information processing steps performed by the processor 31 of the payment device 12 according to the payment program will be explained using the flowchart in Figure 38. The flowchart in Figure 38 corresponds to the flowchart in Figure 12 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 12 and Figure 38.

[0224] Similar to the first embodiment, the processor 31 sets the screen of the touch panel 38 as the standby screen SBa as ACT201. The processor 31 then waits for input events transmitted from the input device 11 as ACT202. In this waiting state, when the processor 31 receives an input event via the communication unit 35, it executes the processing of ACT203 to ACT207. The processor 31 then waits for input events, completion events, or deletion events as ACT208 to ACT210.

[0225] In the second embodiment, while in the waiting state for ACT208 to ACT210, the processor 31 further waits for a correction event as ACT401. Upon receiving a correction event, the processor 31 proceeds from ACT401 to ACT402. The processor 31 corrects the detail record Ra stored in the second transaction file 811 as ACT402. Specifically, for example, if a correction event is received that includes information about the cancellation of product BBBBB, the processor 31 deletes the detail record Ra-B for product BBBBB from the second transaction file 811. For example, if a correction event is received that includes information about correcting the quantity of product BBBBB, the processor 31 corrects the quantity and amount in detail record Ra-B. For example, if a correction event is received that includes information about correcting the unit price, discount amount, or discount rate of product BBBBB, the processor 31 corrects the unit price or discount amount and amount in detail record Ra-B.

[0226] Once the modification of the detail record Ra is complete, the processor 31 returns to the waiting state for ACT208 to ACT210 and ACT401. If a completion event is received in this waiting state, the processor 31 proceeds to ACT221 in Figure 13. Thereafter, the processor 21 executes the processing from ACT221 onwards, similar to the first embodiment.

[0227] Here, the processor 31 realizes its function as a settlement-side modification means 76 through the processing of ACT 402.

[0228] Thus, in the second embodiment as well, the input device 11 does not generate settlement information including detailed information and total information of the purchased goods and transmit it to the settlement device 12, and an accounting system 1 is provided in which the store clerk 2 and the customer 3 share the operation and settle the transaction. Moreover, according to the accounting system 1 of the second embodiment, the data of purchased goods for a transaction entered into the input device 11 can be retrospectively corrected before the input completion instruction, which is the input of the input completion button BAj, is given.

[0229] [Third Embodiment] Next, a third embodiment will be described using Figures 45 to 54. The third embodiment adds a function to the accounting system 1 of the first embodiment that, after an input completion instruction is given by input completion button BAj, returns and modifies the transaction for which the input completion instruction was given. Therefore, the same reference numerals are used for parts common to the first embodiment, and detailed explanations are omitted.

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

[0231] The cancellation detection means 514 has the function of detecting a settlement cancellation instruction for a transaction whose input completion has been notified by the first notification means 56. When the cancellation detection means 514 receives an operation input via the input device 61 that instructs the settlement cancellation of a transaction, it detects a signal corresponding to that operation input as a settlement cancellation instruction signal.

[0232] The designated receiving means 515 is a function that receives input to specify a settlement device 12 from among the settlement devices 120 of the same group to cancel the settlement of a transaction. The designated receiving means 515 receives input to specify a settlement device 12 to cancel the settlement of a transaction via the input device 61.

[0233] The fourth notification means 516 has the function of notifying each of the settlement devices 120 in the same group of the settlement cancellation via the communication unit 25 when the cancellation detection means 514 detects a settlement cancellation instruction for a transaction. The fourth notification means 516 outputs a signal to each of the settlement devices 120 in the same group notifying the settlement cancellation along with the identification information of the settlement device 12 that received the designated input via the designated reception means 515.

[0234] The input-side modification means 517 is a function that modifies transaction data stored in the input-side storage unit 63, provided that a response (affirmative response: OK) authorizing the cancellation of the payment is received from one of the payment devices 12 in response to the notification of payment cancellation. The data in the first transaction file 631 is copied to the fourth transaction file 632 when a signal indicating that payment is possible is received from the payment device 12 that output a signal notifying the end of input. The input-side modification means 517 modifies the detail record Ra stored in the fourth transaction file 632 in response to input from the input device 61. For example, the input-side modification means 517 deletes the detail record Ra. For example, the input-side modification means 517 modifies the unit price, quantity, value discount amount, etc. of the detail record Ra.

[0235] The third transmission means 518 has the function of transmitting the transaction data corrected by the input-side correction means 517 to each of the settlement devices 120 in the same group via the communication unit 25. The third transmission means 518 transmits the corrected transaction data to each of the settlement devices 120 in the same group each time the transaction data is corrected.

[0236] The non-reporting means 519 is a function that notifies that a payment cannot be canceled if the payment device 12 does not respond to the notification of payment cancellation with permission to cancel the payment. The non-reporting means 519 notifies, for example, by displaying text or an image on the display device 62 indicating that the payment cannot be canceled.

[0237] Figure 46 is a block diagram showing the main functional configuration of the processor 31 of the payment device 12. In addition to the payment-side storage means 71, amount display means 72, payment response means 73, payment means 74, and payment-side deletion means 75, the processor 31 also functions as a cancellation response means 77 and a payment-side modification means 78.

[0238] The cancellation response means 77 is a function that returns a response to the input device 11 via the communication unit 35 authorizing the cancellation of settlement if the settlement of the transaction for which the cancellation notice has been received has not been completed. The cancellation response means 77 does not return the above response if the settlement of the transaction for which the cancellation notice has been received has been completed.

[0239] The settlement-side modification means 78 is a function that modifies transaction data stored in the settlement-side storage unit 81 using transaction data transmitted from the input device 11 by the third transmission means 518. When the settlement means 74 receives a signal from the input device 11 indicating the end of input when the transaction is ready for settlement, it copies the detail record Ra stored in the second transaction file 811 to the third transaction file 812. The settlement-side modification means 78 modifies the detail record Ra copied to the third transaction file 812 with transaction data transmitted from the input device 11 by the third transmission means 518. For example, the settlement-side modification means 78 deletes the detail record Ra. For example, the settlement-side modification means 78 modifies the unit price, quantity, value discount amount, etc. of the detail record Ra.

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

[0241] First, the essential information processing steps performed by the processor 21 of the input device 11 according to the input program will be explained using flowcharts in Figures 47, 48, and 49. The flowchart in Figure 47 corresponds to the flowchart in Figure 11 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 11 and Figure 48. Figure 48 corresponds to the flowchart in Figure 9 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 9 and Figure 48.

[0242] As shown in Figure 47, in the third embodiment, the processor 21 sends a completion event via unicast communication in ACT 142 to the settlement device 12 of the same group that has been determined as the destination, and in ACT 144, it receives an acknowledgment (OK) signal from that settlement device 12. Part of the processing after this point differs from the first embodiment. That is, upon receiving the acknowledgment (OK) signal, the processor 21 notifies the settlement device 12 that is the destination of the completion event as ACT 149. The processor 21 also sends a deletion event via unicast communication in ACT 150 to a settlement device 12 of the same group that is not the destination. Furthermore, the processor 21 copies all detail records Ra stored in the first transaction file 631 to the fourth transaction file 632 as ACT 501. After that, the processor 21 clears the first transaction file 631 as ACT 151 and terminates the information processing according to the input program.

[0243] Thus, the processor 21 has the function of sending a completion event to the settlement device 12, which has been determined as the destination, and upon receiving an acknowledgment (OK) signal from the settlement device 12, copying all detail records Ra stored in the first transaction file 631 to the fourth transaction file 632 and clearing the first transaction file 631. Therefore, the fourth transaction file 632 stores the detail records Ra of the transactions settled by the settlement device 12 that returned an acknowledgment (OK). Meanwhile, since the first transaction file 631 is cleared, the input device 11 becomes able to input data related to the next customer transaction.

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

[0245] FIG. 52 is an example of a display of the details screen SAe in the third embodiment. The difference between the details screen SAe and the details screen SAa in the first embodiment is that a software key for the payment cancellation button BAu is added. When the customer 3 who has moved to the payment device 12 requests a correction of the transaction before completing his own transaction payment, the store clerk 2 inputs the payment cancellation button BAu. This correction applies, for example, when there is a mistake in the quantity of goods or when a discount has not been applied. Or it also applies when the customer 3 cancels the transaction.

[0246] Return to the description of FIG. 48. The processor 21 that has displayed the details screen SAe proceeds to ACT102. The processor 21 checks whether a product code has been input as ACT102. If the product code has not been input, the processor 21 proceeds from ACT102 to ACT511. The processor 21 checks whether the payment cancellation button BAu has been input as ACT511. If the payment cancellation button BAu has not been input, the processor 21 returns from ACT511 to ACT102. Thus, the processor 21 waits for a product code to be input or the payment cancellation button BAu to be input in ACT102 and ACT511.

[0247] In the waiting states of ACT102 and ACT511, when a product code is input, the processor 21 proceeds from ACT102 to ACT512. The processor 21 erases the payment cancellation button BAu on the details screen SAe as ACT512. After that, the processor 21 proceeds to ACT103. Then the processor 21 executes the processes of ACT103 to ACT148 described in the first embodiment in the same way. Therefore, when the product code of the product purchased by customer 3 is input and the details record Ra is stored in the first transaction file 631, the payment cancellation button BAu cannot be input until the first transaction file 631 is cleared.

[0248] On the other hand, in the waiting states of ACT102 and ACT511, that is, when the first transaction file 631 is cleared, if the payment cancellation button baU is input, the processor 21 proceeds from ACT511 to ACT513. The processor 21 makes the screen of the touch panel 28 the payment device selection screen SAf (see FIG. 53).

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

[0250] After checking the payment device selection screen SAf, clerk 2 inputs the payment device selection buttons BAv and BAw for the payment device 12 that customer 3 was trying to use to make a payment. For example, if customer 3 was trying to make a payment using payment device 12(12-1) and requested a transaction modification, clerk 2 inputs the payment device selection button BAv. For example, if customer 3 was trying to make a payment using payment device 12(12-2) and requested a transaction modification, clerk 2 inputs the payment device selection button BAw.

[0251] Returning to the explanation of Figure 48. The processor 21, which displays the payment device selection screen SAf, waits for either payment device selection button BAv or BAw to be input as ACT514. When either payment device selection button BAv or BAw is input, the processor 21 proceeds from ACT514 to ACT515. As ACT515, the processor 21 obtains the payment device ID, which is the identification information of the payment device 12 assigned to the input payment device selection button BAv or BAw. For example, if payment device selection button BAv is input, the processor 21 obtains the ID of payment device 12 (12-1). For example, if payment device selection button BAw is input, the processor 21 obtains the ID of payment device 12 (12-2).

[0252] Next, the processor 21 sends a payment cancellation event to the payment device 120 of the same group via multicast communication as ACT516. The payment cancellation event includes the payment device ID obtained in ACT515.

[0253] The processor 21 that sent the payment cancellation event proceeds from ACT516 to ACT517. As ACT517, the processor 21 waits for an acknowledgment (OK) from one of the payment devices 12. If an acknowledgment (OK) signal is not received within a certain time in this waiting state, the processor 21 proceeds from ACT517 to ACT518. As ACT518, the processor 21 notifies that the payment cannot be canceled. For example, the processor 21 notifies by displaying text or an image on the touch panel 28 indicating that the payment cannot be canceled. With this, the processor 21 terminates the information processing according to the input program.

[0254] In ACT517, if an acknowledgment (OK) signal is received within a certain time, the processor 21 proceeds to ACT519. As ACT519, the processor 21 copies all detail records Ra stored in the fourth transaction file 632 to the first transaction file 631. Then, as ACT520, the processor 21 clears the fourth transaction file 632. After that, as ACT521, the processor 21 uses the data of the detail records Ra copied to the first transaction file 631 to set the touch panel screen to the second detail screen SAg (see Figure 54).

[0255] Figure 54 shows an example of the display of the second detail screen SAg. Compared to the detail screen SAa displayed in ACT101 (see Figure 52), the second detail screen SAg has the settlement cancellation button BAu changed to the bulk cancellation button BAx. Also, the subtotal button BAa has been changed to the complete button BAy. Furthermore, the detail area AAb of the second detail screen SAg displays the product name, quantity, value discount amount, and amount of the detail record Ra copied to the first transaction file 631, and the total area AAc displays the total points and total amount of the same detail record Ra. In addition, the second detail screen SAg displays the identification name NA of the settlement device 12 selected by the settlement device selection screen SAf. For reference, the second detail screen SAg in Figure 52 is the case when settlement device 12 (12-1) is selected by inputting the settlement device selection button BAv, and [Settlement Device 1] is displayed as the identification name NA.

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

[0257] If customer 3 requests to cancel the transaction, clerk 2 presses the "cancel all" button BAx. If the customer requests to delete purchased items or modify the quantity, unit price, discount amount, or discount rate, clerk 2 touches the row in detail area AAb where the product name, etc., of the relevant purchased item is displayed.

[0258] When the batch cancellation button BAx is pressed while ACT531 and ACT532 are in the waiting state, processor 21 proceeds from ACT531 to ACT533. Processor 21, as ACT533, sends a batch cancellation event to the payment devices 120 of the same group via multicast communication. The batch cancellation event includes the payment device ID obtained in the processing of ACT515.

[0259] Processor 21, having sent the batch cancellation command, proceeds to ACT534. Processor 21 clears the first transaction file 631 as ACT534. With this, Processor 21 completes the information processing according to the input program.

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

[0261] In other words, the processor 21, which displays the correction screen SAd, waits for either the OK button BAt to be input as ACT536, or the Cancel button BAs to be input as ACT537. If the Cancel button BAs is input while waiting for ACT536 or ACT537, the processor 21 proceeds from ACT537 to ACT538. The processor 21 clears the correction screen SAd as ACT538. After that, the processor 21 proceeds to ACT542.

[0262] On the other hand, if the OK button BAt is pressed while ACT536 and ACT537 are in the waiting state, the processor 21 proceeds from ACT536 to ACT539. The processor 21 sends a correction event to the settlement device 120 of the same group via multicast communication as ACT539. The correction event includes the information entered for the correction screen SAd. For example, if the cancel button BAn is pressed on the correction screen SAd, the processor 31 includes the information that the selected product has been canceled. For example, if the quantity change button BAo is pressed on the correction screen SAd, and the corrected quantity is also entered, the processor 31 includes the information that the quantity of the selected product has been corrected to the corrected quantity. Similarly, if the unit price change button BAp, discount button BAq, or discount button BAr is pressed on the correction screen SAd, the processor 31 includes the information that the unit price, discount amount, or discount rate of the selected product has been corrected.

[0263] Processor 21, which sent the modification event, proceeds to ACT540. Processor 21 modifies the detail record Ra stored in the first transaction file 631 as ACT540. For example, if the cancel button BAn is entered on the modification screen SAd, processor 31 deletes the detail record Ra of the selected product. For example, if the quantity change button BAo is entered on the modification screen SAd, and the modified quantity is also entered, processor 31 modifies the quantity and amount of the detail record Ra of the selected product. Similarly, if the unit price change button BAp, discount button BAq, or discount button BAr is entered on the modification screen SAd, processor 31 modifies the unit price, discount amount or discount rate and amount of the detail record Ra of the selected product, just as if the quantity change button BAo were entered. Then, processor 21 clears the modification screen SAd as ACT541 and updates the second detail screen SAg. After that, processor 21 proceeds to ACT542.

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

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

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

[0267] The processor 21 that has transmitted the correction completion event proceeds to ACT545. The processor 21 notifies that the correction of the transaction has been completed as ACT545. For example, the processor 21 displays and notifies a message indicating that the correction of the transaction has been completed on the customer display 29. The customer 3 who has confirmed this notification will move to the location of the settlement device 12 where the settlement was interrupted and perform the settlement.

[0268] The processor 21 that has notified that the correction of the transaction has been completed proceeds to ACT546. The processor 21 clears the first transaction file 631 as ACT546. Thus, the processor 21 finishes the information processing according to the input program.

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

[0270] Next, the essential information processing steps performed by the processor 31 of the payment device 12 according to the payment program will be explained using the flowcharts in Figures 50 and 51. The processing steps shown in the flowcharts in Figures 50 and 51 correspond to the processing steps from ACT229 onwards in Figure 13 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 13 and Figure 13.

[0271] In ACT229, the processor 31, which displays the accounting screen SBb, waits for the payment to be completed as ACT230. In this waiting state, the processor 31 checks whether or not it has received a payment cancellation event as ACT601. If the payment is completed without receiving a payment cancellation event, the processor 31 executes the processes of ACT231 to ACT234 as described above and terminates the information processing according to the payment program.

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

[0273] If the IDs match, the processor 31 proceeds from ACT602 to ACT603. As ACT603, the processor 31 sends an acknowledgment (OK) signal to the input device 11 that sent the settlement cancellation event. The processor 31 also copies all the detail records Ra stored in the third transaction file 812 to the second transaction file 811 as ACT604. Finally, the processor 31 clears the third transaction file 812 as ACT605.

[0274] Subsequently, processor 31 checks whether it has received a batch cancellation event as ACT606. If it has not received a batch cancellation event, processor 31 proceeds from ACT606 to ACT607. Processor 31 checks whether it has received a correction event as ACT607. If it has not received a correction event, processor 31 proceeds from ACT607 to ACT608 in Figure 51. Processor 31 checks whether it has received a correction completion event as ACT608. If it has not received a correction completion event, processor 31 returns to ACT606 in Figure 50. In this way, processor 31 waits in ACT606 through ACT608 for the reception of a batch cancellation event, a correction event, or a correction completion event.

[0275] If a batch cancellation event is received while in the waiting state for ACT606 to ACT608, the processor 31 proceeds from ACT606 to ACT609. As ACT609, the processor 31 checks whether the payment device ID included in the batch cancellation event matches the ID of its own payment device 12. If the IDs do not match, the processor 31 returns to the waiting state for ACT606 to ACT608. In other words, the processor 31 discards the batch cancellation event and returns to the waiting state for batch cancellation events, modification events, and modification completion events.

[0276] If the IDs match, processor 31 proceeds from ACT609 to ACT610. Processor 31 clears the second transaction file 811 as ACT610. With this, processor 31 completes the information processing according to the settlement program.

[0277] If a correction event is received while in the waiting state for ACT606 to ACT608, the processor 31 proceeds from ACT607 to ACT611. The processor 31 checks if the payment device ID included in the correction event as ACT611 matches the ID of its own payment device 12. If the IDs do not match, the processor 31 returns to the waiting state for ACT606 to ACT608. In other words, the processor 31 discards the correction event and returns to the waiting state for batch cancellation events, correction events, and correction completion events.

[0278] If the IDs match, the processor 31 proceeds from ACT611 to ACT612. The processor 31 modifies the data of the detail record Ra stored in the second transaction file 811 as ACT612 based on the information contained in the modification event. This modification is the same as the processing of ACT402 described in the second embodiment, so a detailed explanation is omitted here. After completing the modification of the detail record Ra, the processor 31 returns to ACT606 and again enters a state of waiting for the batch cancellation event, modification event, and modification completion event.

[0279] If a correction completion event is received while in the waiting state for ACT606 to ACT608, the processor 31 proceeds from ACT608 to ACT613 in Figure 51. The processor 31 checks whether the payment device ID included in the correction completion event as ACT613 matches the ID of its own payment device 12. If the IDs do not match, the processor 31 returns to the waiting state for ACT606 to ACT608. In other words, the processor 31 discards the correction completion event and returns to the waiting state for batch cancellation events, correction events, and correction completion events.

[0280] In contrast, if the IDs match, the processor 31 proceeds from ACT613 to ACT227. The processor 31 then executes the processing of ACT227 to ACT234 in the same manner as in the first embodiment, and terminates the information processing according to the settlement program.

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

[0282] Thus, in the third embodiment as well, the input device 11 does not generate settlement information including detailed information and total information of the goods bought and sold and transmit it to the settlement device 12, and an accounting system 1 is provided in which the store clerk 2 and the customer 3 share the operation and settle the transaction. Moreover, according to the accounting system 1 of the third embodiment, after an input completion instruction is given, which is the input of the input completion button BAj, the transaction for which the input completion instruction was given can be returned and corrected.

[0283] [Fourth Embodiment] Next, a fourth embodiment will be described using Figures 55 to 64. The fourth embodiment is an addition to the accounting system 1 of the first embodiment, with the addition of gift certificates as a payment method. Therefore, parts common to the first embodiment are denoted by the same reference numerals, and detailed explanations are omitted.

[0284] Gift certificates are an example of monetary voucher products. In this embodiment, there are two types of gift certificates: one with a face value of 500 yen and another with a face value of 1000 yen. Each gift certificate is assigned a unique gift certificate code, similar to other products, and a barcode representing that gift certificate code is printed on it. A data record for the gift certificates, created in the same format as the product record, is stored in the product master file 131. The data record for the gift certificates describes the gift certificate code as the product code, the gift certificate name as the product name, and the face value as the unit price.

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

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

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

[0288] The calculation means 521 is a function that calculates the total transaction amount by treating the sales price of goods other than gift certificates as a positive value, and the face value of gift certificates as a negative value, among the transaction data stored in the first transaction file 631 of the input-side storage unit 63. The calculation means 522 displays the calculated total amount on the display device 62.

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

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

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

[0292] The receipt output means 710 is a function that outputs a receipt for a transaction settled by the payment means 74, which shows the face value of the gift certificate separately from the total amount of sales of goods other than the gift certificate. The receipt may be printed on paper or output as an electronic receipt to an information terminal such as a smartphone.

[0293] Next, using the flowcharts in Figures 58 to 61, the screen examples in Figures 62 and 63, and the receipt example in Figure 64, the content and procedures of the information processing related to the fourth embodiment, which is performed in the input device 11 and payment device 12 that constitute the accounting system 1, will be explained. Note that the content and procedures of the information processing described below are examples. The content and procedures can be changed as appropriate if similar effects can be achieved. Also, the screen examples and receipt examples are examples. The content of the output text, the arrangement of images, the types and layouts of software keys, etc., can be changed as appropriate.

[0294] First, the essential information processing steps performed by the processor 21 of the input device 11 according to the input program will be explained using flowcharts in Figures 58 and 59. The flowchart in Figure 47 corresponds to the flowchart in Figure 11 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 11 and Figure 47. Figure 58 corresponds to the flowchart in Figure 9 in the first embodiment. Also, Figure 59 corresponds to the flowchart in Figure 10 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 9 and Figure 10.

[0295] As shown in Figure 58, the processor 21, with the touch panel 28 screen set to the details screen SAa, waits for the product code to be entered as ACT102 or ACT107. In this waiting state, when the product code of the purchased product is entered, the processor 21 executes the processes of ACT103 and ACT104, similar to the first embodiment.

[0296] Specifically, the processor 21 sends an input event as ACT103 to the payment device 120 of the same group via multicast communication. The input event includes the product code entered from the scanner 27 or touch panel 28. The processor 21 also creates a detail record Rb as ACT104. The processor 21 accesses the server 13 and retrieves a product record containing the entered product code from the product master file 131. Then, based on the product information such as product name and unit price described in that product record, the processor 21 creates a detail record Rb consisting of item data such as record number r, product code, product name, unit price, quantity, and amount.

[0297] On the other hand, if a gift certificate code is entered while ACT102 or ACT107 is in standby mode, the processor 21 also executes the processes of ACT103 and ACT104. Specifically, the processor 21 sends an input event to the payment device 120 of the same group via multicast communication as ACT103. The input event includes the gift certificate code. The processor 21 also creates a detail record Rb as ACT104. The processor 21 accesses the server 13 and retrieves a data record containing the entered gift certificate code from the product master file 131. The processor 21 then creates a detail record Rb consisting of item data such as record number r, product code, product name, unit price, quantity, and amount, based on the information such as the gift certificate name and face value described in the data record. The product code of the detail record Rb is the gift certificate code. The product name is the gift certificate name. The unit price is the face value. The quantity is "1". The amount is the value obtained by multiplying the unit price by the quantity.

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

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

[0300] In contrast, if the detail record Rb is a detail record for a gift certificate, the processor 21 proceeds from ACT701 to ACT703. As ACT703, the processor 21 sets the gift certificate flag Fe of the detail record Rb to "1". Also, as ACT704, the processor 21 adds a minus sign to the amount of the detail record Rb.

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

[0302] Figure 62 shows the details screen SAa after scanning the barcode of a gift certificate with a face value of 1000 yen with scanner 27. As shown in the figure, the current area AAa displays the name, quantity, and face value of the gift certificate. The face value is accompanied by a minus sign.

[0303] After completing the processing of ACT106, the processor 21 enters a waiting state for ACT107 to ACT109. In this waiting state, when the barcode of a product or gift certificate is scanned, the processor 21 executes the processing of ACT103 and ACT104, ACT701 to ACT704, and furthermore, ACT105 and ACT106, in the same manner as described above.

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

[0305] If the total amount is positive, payment is required. In this case, processor 21 proceeds from ACT711 to ACT121. Then processor 21 executes the processing of ACT121 to ACT151 in the same manner as in the first embodiment.

[0306] In contrast, if the total amount is 0 yen or a negative amount, payment has been completed using the gift certificate. In this case, processor 21 proceeds from ACT711 to ACT712. Processor 31, as ACT712, sets the screen of touch panel 28 to the payment completion screen SAh (see Figure 63).

[0307] Figure 63 shows an example of the payment completion screen SAh. The payment completion screen SAh is the payment screen SAc with the subtotal discount button BAh and the subtotal discount button BAi software keys removed. The payment completion screen SAh is shown in the case where customer 3 purchased four items totaling 1000 yen and presented a gift certificate with a face value of 1000 yen, as shown in the details screen SAa in Figure 62. In this case, the total amount is 0 yen, so there is no payment to be made. However, since the receipt is issued by the payment device 12, the store clerk 2 presses the input completion button BAj alone. Alternatively, the store clerk 2 presses the busy button BAk and the input completion button BAj.

[0308] After displaying the payment completion screen SAh, the processor 21 proceeds to ACT125. The processor 21 then executes the processing of ACT125 through ACT151 in the same manner as in the first embodiment. Therefore, if the store clerk 2 presses the input completion button BAj alone, the processor 21 sends a completion event to the master unit 121. If the store clerk 2 presses both the busy button BAk and the input completion button BAj, the processor 21 sends a completion event to the slave unit 1221.

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

[0310] Next, the essential information processing steps performed by the processor 31 of the payment device 12 according to the payment program will be explained using flowcharts in Figures 60 and 61. The processing steps shown in the flowchart of Figure 60 correspond to the flowchart of Figure 12 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 12 and Figure 61. The processing steps shown in the flowchart of Figure 61 correspond to the flowchart of Figure 13 in the first embodiment. Therefore, the same reference numerals are used for processing steps that are common to both Figure 13 and Figure 61.

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

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

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

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

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

[0316] In contrast, if the detail record Rb is a detail record for a gift certificate, the processor 31 proceeds from ACT801 to ACT803. As ACT803, the processor 31 sets the gift certificate flag Fe of the detail record Rb to "1". Also, as ACT804, the processor 31 adds a minus sign to the amount of the detail record Rb.

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

[0318] When the processor 31 receives an input event containing a product code or gift certificate code again while in the waiting state of ACT208 to ACT210, it executes the processing from ACT203 onwards in the same manner as described above. That is, if an input event containing a product code is received, the processor 31 creates a detail record Rb with the gift certificate flag Fe set to "0" and stores the detail record Rb in the second transaction file 811. If an input event containing a gift certificate code is received, the processor 31 creates a detail record Rb with the gift certificate flag Fe set to "1" and stores the detail record Rb in the second transaction file 811.

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

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

[0321] If the total amount is positive, processor 31 proceeds from ACT811 to ACT222. Then processor 31 executes the processing of ACT222 through ACT234 in the same manner as described above.

[0322] In contrast, if the total amount is 0 or a negative amount, processor 31 proceeds from ACT811 to ACT231, skipping the processing of ACT222 through ACT230. Therefore, customer 3 does not pay the amount. Subsequently, processor 21 performs the processing of ACT231 through ACT234 as described above. As a result, receipt RS (see Figure 64) is issued, and customer 3 receives receipt RS.

[0323] Figure 64 shows an example of a receipt RS issued to a customer who presents a gift certificate with a face value of 1,000 yen for a purchase totaling 1,000 yen. As shown in Figure 64, the receipt RS has the details of the four purchased items printed on it, followed by the total amount of 1,000 yen, and then the face value of the gift certificate, 1,000 yen, printed with a minus sign. With such a receipt RS, customer 3 can confirm that they paid for the purchased items with a gift certificate.

[0324] Here, processor 31 realizes the function of payment-side identification means 79 through processing of ACT801. Processor 31 also realizes the function of receipt output means 710 through processing of ACT231.

[0325] Thus, in the fourth embodiment as well, the input device 11 does not generate settlement information including detailed information and total information of the goods bought and sold and transmit it to the settlement device 12, and an accounting system 1 is provided in which the store clerk 2 and the customer 3 share the operation and settle the transaction. Moreover, according to the fourth embodiment, an accounting system 1 is provided that also supports monetary vouchers such as gift certificates that require the intervention of a store clerk as a method of payment.

[0326] [Other embodiments] In the above embodiment, an example was given in which a store clerk 2 selects and inputs the payment method by operating the input device 11. In another embodiment, the customer 3 may select and input the payment method by operating the payment device 12, similar to existing accounting systems.

[0327] Furthermore, the above embodiment illustrates a case where the input device 11 issues a transaction number and transmits it to the settlement device 3 along with the completion event. In another embodiment, the settlement device 3, upon receiving the completion event, may issue a transaction number. In this case, for multiple settlement devices 12 located in the same checkout lane, it is advisable to ensure that the transaction numbers issued by each settlement device 12 do not overlap, for example, by assigning different values ​​to the most significant digit of the transaction number.

[0328] In the input device 11, examples were given of inputting the input completion button BAj alone and inputting both the busy button BAk and the input completion button BAj as means of indicating input completion. In other embodiments, if the input completion button BAj is input alone, a completion event may be sent to the master unit 121, and if the busy button BAk is input alone, a completion event may be sent to the slave unit 122. Alternatively, the busy button BAk may be omitted, leaving only the input completion button BAj, and a completion event may be sent to one of the payment devices 12.

[0329] For example, suppose there are three payment devices 12: device 12-1, device 22-2, and device 32-3. The input device 11 sends a completion event to device 12-1, device 22-2, and device 32-3 in that order each time the input completion button BAj is pressed. If a negative response (NG) is received from a payment device 12, a completion event is sent to the next payment device 12. Even with an accounting system configured in this way, transactions can be settled by store staff and customers sharing the operation without the input device generating payment information.

[0330] Furthermore, let's assume, for example, that unit 12-1 and unit 22-2 are connected to the cashless payment terminal 5, but unit 32-3 is not connected to the cashless payment terminal 5. In that case, if customer 3 wishes to pay with cash, the input device 11 sends completion events in the order of unit 12-1, unit 22-2, and unit 32-3. If the customer wishes to pay using cashless payment, the input device 11 sends completion events in the order of unit 12-1 and unit 22-2, and does not send a completion event to unit 32-3. Such a configuration can be realized by the input device 11 storing the connection flag Fb of each payment device 12. Even with such a configuration, the store clerk 2 will not direct customer 3 who wishes to pay using cashless payment to unit 32-3. Moreover, since unit 32-3 will not return a negative response (NG) to the completion event which includes the identification code for the cashless payment method, it is efficient.

[0331] In the fourth embodiment, the payment device 12 may dispense change from an automatic change dispenser if the total amount is negative. This allows the device to accept gift certificates that can dispense change.

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

[0333] Although several embodiments have been described above, these embodiments are presented as examples only 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 variations are included within the scope of the invention, as well as within the scope of the invention and its equivalents as described in the claims. The invention described in the original claims of this application is listed below. [1] An accounting system comprising: an input device for inputting transaction data via an input device; and a plurality of settlement devices for settling transactions, connected by a communication line, wherein the input device includes: an end detection means for detecting an instruction to end inputting transaction data; a first transmission means for transmitting the transaction data input via the input device to each of the plurality of settlement devices before the end detection means detects an instruction to end inputting transaction data; and a first notification means for notifying one of the plurality of settlement devices of the end of input when the end detection means detects an instruction to end inputting transaction data, wherein the settlement device includes: a settlement-side storage means for storing transaction data transmitted from the input device in a settlement-side storage unit until the transaction is settled; and a settlement means for settling the transaction based on the transaction data stored in the settlement-side storage unit when the input device notifies the end of input in a state where the transaction is ready for settlement. [2] The accounting system as described in Appendix [1], wherein the settlement device further comprises a settlement response means that, upon receiving notification of the completion of the input from the input device, responds to the input device whether or not the transaction can be settled, and the input device further comprises a second notification means that, upon receiving a response of non-settlement from the settlement device that notified it of the completion of the input, notifies other settlement devices that have not notified it of the completion of the input of the completion of the input. [3] The accounting system as described in Appendix [2], wherein the input device further comprises a third notification means for notifying other payment devices that have not notified the end of the input that payment is complete when the payment device that has notified the end of the input has notified it that payment is complete, and the payment device further comprises a payment-side deletion means for deleting transaction data stored in the payment-side storage unit when the payment device has received notification of the end of payment from the input device. [4] The accounting system as described in Appendix [1], wherein the input device further comprises a detail display means for displaying transaction details based on data relating to a transaction entered via the input device, and the settlement device further comprises an amount display means for displaying the settlement amount of the transaction when it receives notification of the completion of the input from the input device in a state where settlement of the transaction is possible. [5] The accounting system as described in Appendix [1], wherein one of the plurality of payment devices functions as a master unit and the rest functions as slave units, and the completion detection means of the input device includes a first means for detecting an operation input to a first operator as an input completion instruction and a second means for detecting an operation input to a second operator as an input completion instruction, and the first notification means of the input device notifies the payment device functioning as the master unit of the completion of input when the first means of the completion detection means detects the input completion instruction, and notifies the payment device functioning as a slave unit of the completion of input when the second means detects the input completion instruction. [6] The accounting system as described in Appendix [1], wherein the input device further comprises a selection means for receiving input of a payment method necessary for settling a transaction, the input device's first notification means notifies one of the settlement devices of the completion of input along with payment method identification data identifying the payment method selected by the selection means, and the settlement means of the settlement device settles the transaction with the payment method identified by the payment method identification data received along with the notification of the completion of input. [7] The accounting system as described in Appendix [6], wherein the settlement device further comprises a settlement response means that, upon receiving notification of the completion of input from the input device, responds to the input device whether or not the transaction can be settled, and the settlement response means responds to the input device that the transaction cannot be settled if the payment method identified by the payment method identification data received together with the notification of the completion of input is a payment method not applicable to the settlement device. [8] The accounting system according to any one of the appendices [1] to [7], wherein the first transmission means of the input device transmits the entered transaction data to each of the plurality of settlement devices each time transaction data is entered via the input device. [9] An input device comprising: an input device for inputting transaction data; a communication device for communicating data with a plurality of settlement devices for settling transactions; an end detection means for detecting an instruction to end inputting transaction data; a first transmission means for transmitting the transaction data input via the input device to each of the plurality of settlement devices before the end detection means detects an instruction to end inputting transaction data; and a first notification means for notifying one of the plurality of settlement devices of the end of input when the end detection means detects an instruction to end inputting transaction data.

[10] A settlement device comprising: an input device that transmits transaction data entered via an input device to each of a plurality of settlement devices before an instruction to end the input of the transaction data is detected; a settlement-side storage means that stores the transaction data transmitted from the input device in a settlement-side storage unit until the transaction is settled; and a settlement means that, when the input end instruction is received from the input device in a state where the transaction is ready for settlement, settles the transaction based on the transaction data stored in the settlement-side storage unit.

[11] A program for causing a computer of an input device, which includes an input device for inputting transaction data and a communication device for communicating data with a plurality of settlement devices for settling transactions, to function as: an end detection means for detecting an instruction to end inputting transaction data; a first transmission means for transmitting transaction data input via the input device to each of the plurality of settlement devices before the end detection means detects an instruction to end inputting transaction data; and a first notification means for notifying one of the plurality of settlement devices of the end of input when the end detection means detects an instruction to end inputting transaction data.

[12] A program to cause a computer of a settlement device equipped with an input device and a communication device that communicates with an input device to transmit transaction data entered via an input device to each of a plurality of settlement devices before an instruction to end the input of the transaction data is detected to function as a settlement-side storage means that stores the transaction data transmitted from the input device in a settlement-side storage unit until the transaction is settled, and a settlement means that, when the input end instruction is received from the input device in a state where the transaction is ready for settlement, settles the transaction based on the transaction data stored in the settlement-side storage unit. [Explanation of Symbols]

[0334] 1…Accounting system, 2…Shop assistant, 3…Customer, 5…Cashless payment terminal, 11…Input device, 12…Payment device, 13…Server, 14…Network, 21,31…Processor, 51…Input-side storage means, 52…Detail display means, 53…Termination detection means, 54…First transmission means, 55…Selection means, 56…First notification means, 57…Second notification means, 58…Third notification means, 59…Payment destination notification means, 63…Input-side storage unit, 64…Data table, 71…Payment-side storage means, 72…Amount display means, 73…Payment response means, 74…Payment means, 75…Payment-side deletion means, 76…Payment-side modification Correction means, 77... Cancellation response means, 78... Settlement side modification means, 79... Settlement side identification means, 82... Flag memory, 510... Input side deletion means, 511... Modification acceptance means, 512... Input side modification means, 513... Second transmission means, 514... Cancellation detection means, 515... Designation acceptance means, 516... Fourth notification means, 517... Input side modification means, 518... Third transmission means, 519... Non-notification means, 520... Input side identification means, 521... Calculation means, 631... First transaction file, 632... Fourth transaction file, 710... Receipt output means, 811... Second transaction file, 812... Third transaction file.

Claims

1. An input device that inputs transaction data via an input device and multiple settlement devices that settle transactions are connected by a communication line. The aforementioned input device is A termination detection means for detecting that an instruction to terminate the input of transaction-related data has been given to the input device via the input device, A first transmission means transmits the transaction data entered via the input device to each of the multiple payment devices so that each of the multiple payment devices stores a detail record with the same content as a detail record showing the details of the goods sold as one transaction in its payment-side storage unit, before the termination detection means detects the end of input of the transaction data. When the termination detection means detects an instruction to complete the input of transaction-related data, the first notification means notifies one of the multiple settlement devices, each of which has stored the same detail record in its settlement-side storage unit, that the input has been completed. It is equipped with, The aforementioned multiple payment devices are A settlement-side storage means that stores transaction data transmitted from the input device in a settlement-side storage unit until the transaction is settled, When the input device receives notification of the completion of the input while the transaction is ready for settlement, the settlement means settles the transaction based on the transaction data stored in the settlement-side storage unit. An accounting system equipped with the following features.

2. Of the multiple payment devices, the payment device for which the completion of input has been notified by the first notification means is: A settlement response means that responds to the input device whether or not settlement of the transaction by the settlement means is possible. Furthermore, it is equipped with, The aforementioned input device is When the first notification means receives a response indicating that payment is impossible from the payment device that has been notified of the end of input, the second notification means notifies other payment devices that have not been notified of the end of input by the first notification means that the end of input has been notified. The accounting system according to claim 1, further comprising:

3. The aforementioned input device is When the first notification means receives a payment completion response from the payment device that has been notified of the end of the input, the third notification means notifies other payment devices that have not been notified of the end of the input of the first notification means that the payment has been completed. Furthermore, it is equipped with, The aforementioned payment device is Upon receiving notification of the completion of the settlement from the input device, the settlement-side deletion means deletes the transaction data stored in the settlement-side storage unit. The accounting system according to claim 2, further comprising:

4. The aforementioned input device is A detail display means that displays transaction details based on transaction data entered via the aforementioned input device. Furthermore, it is equipped with, The aforementioned payment device is When the input device receives notification of the completion of the input while the transaction is ready for settlement, the amount display means displays the settlement amount of the transaction. The accounting system according to claim 1, further comprising:

5. Of the aforementioned multiple payment devices, one functions as the master unit, and the rest function as slave units. The termination detection means of the input device is, A first means for detecting an operation input to a first operator provided on the input device as an input termination instruction, The input device is provided with a second means for detecting an operation input to a second operator that emits a signal different from the first operator as an input termination instruction, Includes, The first notification means of the input device is, When the first means of the termination detection means detects the input termination instruction, it notifies the payment device, which functions as the master unit, of the input termination; when the second means detects the input termination instruction, it notifies the payment device, which functions as the slave unit, of the input termination. The accounting system according to claim 1.

6. The aforementioned input device is A selection method that accepts input for the payment method required for settling a transaction. Furthermore, it is equipped with, The first notification means of the input device is, The payment device is notified of the completion of input along with payment method identification data that identifies the payment method selected and entered by the selection means. The payment means of the aforementioned payment device is: The transaction is settled using the payment method identified by the payment method identification data received along with the notification of completion of input. The accounting system according to claim 1.

7. The aforementioned payment device is A settlement response means, upon receiving notification of the completion of the input from the input device, identifies whether or not settlement of the transaction is possible and responds to the input device. Furthermore, it is equipped with, If the payment response means identifies that the payment method identified in the payment method identification data received along with the notification of completion of input is a payment method not applicable to the payment device, The payment means does not settle transactions using the payment method identified by the payment method identification data. The accounting system according to claim 6, wherein the settlement response means responds to the input device that settlement of the transaction is impossible.

8. The first transmission means of the input device is: Each time transaction data is entered via the input device, the entered transaction data is transmitted to each of the multiple settlement devices. The accounting system according to any one of claims 1 to 7.

9. An input device for entering transaction-related data, Multiple settlement devices for settling transactions and communication devices for data communication, A termination detection means for detecting that an instruction to end the input of transaction-related data has been given via the input device, A first transmission means transmits the transaction data entered via the input device to each of the multiple payment devices so that each of the multiple payment devices stores a detail record with the same content as a detail record showing the details of the goods sold as one transaction in its payment-side storage unit, before the termination detection means detects the end of input of the transaction data. When the termination detection means detects an instruction to complete the input of transaction-related data, the first notification means notifies one of the multiple settlement devices, each of which has stored the same detail record in its settlement-side storage unit, that the input has been completed. An input device equipped with the following:

10. A communication device that communicates with an input device to transmit transaction data entered via an input device to each of the multiple payment devices so that each of the payment devices stores the same detail record in its payment-side storage unit as a detail record showing the details of the goods sold as one transaction, before an instruction to end the input of transaction data is detected. A settlement-side storage means that stores transaction data transmitted from the input device in a settlement-side storage unit until the transaction is settled, When the input device receives the input termination instruction while the transaction is ready for settlement, the settlement means settles the transaction based on the transaction data stored in the settlement-side storage unit, A payment device equipped with the following features.

11. A computer for an input device, which includes an input device for entering transaction-related data and a communication device for communicating data with multiple settlement devices for settling transactions, Termination detection means for detecting that an instruction to terminate the input of transaction-related data has been given to the input device via the input device, A first transmission means transmits the transaction data entered via the input device to each of the multiple payment devices so that each of the multiple payment devices stores a detail record with the same content as a detail record showing the details of the goods sold as one transaction in its respective payment-side storage unit, before the termination detection means detects the end of input of the transaction data. When the termination detection means detects an instruction to complete the input of transaction-related data, the first notification means notifies one of the multiple settlement devices, each of which has the same detail record stored in its settlement-side storage unit, that the input has been completed. A program designed to function as such.

12. A computer for a payment device that has an input device and a communication device that communicates data to each of the multiple payment devices, so that before an instruction to end the input of the transaction data is detected, each of the multiple payment devices stores the same detail record in its payment-side storage unit as a detail record showing the details of the goods sold as one transaction. A settlement-side storage means that stores transaction data transmitted from the input device in a settlement-side storage unit until the transaction is settled, and When the input device receives an input termination instruction while the transaction is ready for settlement, the settlement means settles the transaction based on the transaction data stored in the settlement-side storage unit. A program designed to function as such.

Images