JP7849313B2 - Accounting system, input device, payment device, and program - Google Patents

Description

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

In recent years, a type of accounting system for mass retailers that involves a shared operation between store employees and customers has become known. This type of accounting system separates an input device that receives data on the goods bought and sold in each transaction from a settlement device that processes the transaction based on the data entered by the input device. The system is then arranged so that store employees operate the input device and customers operate the settlement device.

In a shared-task accounting system, store employees handle the data entry of products, thus reducing the time required for data entry compared to a self-service system where customers perform all operations themselves. However, because customers operate the payment devices, it is anticipated that unfamiliar customers may have difficulty with the process. Therefore, generally, a shared-task accounting system assigns multiple payment devices to a single data entry device.

In conventional accounting systems of this type, once a store employee has entered all the data for the goods bought and sold in a transaction with a customer into an input device, the input device generates settlement information. This settlement information includes detailed information such as the product code, product name, unit price, quantity, and amount of the goods sold, as well as total information such as the total number of items and total amount. The settlement information is then transmitted to an available payment device, and the store employee guides the customer to that device. Upon receiving the settlement information, the payment device becomes ready for settlement, and the customer operates the device to pay using cash, credit card, electronic money, etc. Thus, in this shared-operation accounting system, the store employee and the customer share the operation of settling the transaction.

Japanese Patent Publication No. 2013-242839

The problem that the embodiments of this 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 using 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.

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 determination means, a completion detection means, a first transmission means, and a first notification means. Before inputting transaction data, the determination means determines one of several settlement devices as the connection destination. The completion detection means detects an instruction to complete input of transaction data. The first transmission means transmits the transaction data input via the input device to one of the settlement devices determined as the connection destination by the determination means before the completion detection means detects an instruction to complete input of the transaction data. When the completion detection means detects an instruction to complete input of transaction data, the first notification means outputs a signal to one of the settlement devices determined as the connection destination by the determination means to notify it of the completion of input.
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 a signal from the input device indicating the end of input, it settles the transaction based on the transaction data stored in the settlement-side storage unit.

Figure 1 is a schematic diagram showing the general configuration of the accounting system according to the embodiment. Figure 2 is a block diagram showing the hardware configuration of an input device to be incorporated into an accounting system. Figure 3 is a block diagram showing the hardware configuration of a payment device to be incorporated into an accounting system. Figure 4 is a block diagram showing the main functional configuration of the input device processor in the first embodiment. Figure 5 is a schematic diagram showing the configuration of the first data table of the input device in the first embodiment. Figure 6 is a schematic diagram showing the data structure of detail records. Figure 7 is a block diagram showing the main functional configuration of the payment device processor in the first embodiment. Figure 8 is a schematic diagram showing the configuration of the flag memory in the payment device. 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 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 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 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 shows an example of a connection destination selection screen displayed on the touch panel of an input device. Figure 14 shows an example of a connection failure screen displayed on the touch panel of an input device. Figure 15 shows an example of a connection destination selection screen displayed on the touch panel of an input device. Figure 16 shows an example of a details screen displayed on the touch panel of an input device. Figure 17 shows an example of a subplan view displayed on the touch panel of an input device. Figure 18 shows an example of a standby screen displayed on the touch panel of a payment device. Figure 19 shows an example of a payment method selection screen displayed on the touch panel of a payment device. Figure 20 shows an example of an accounting screen displayed on the touch panel of a payment device. Figure 21 is a block diagram showing the main functional configuration of the input device processor in the second embodiment. Figure 22 is a block diagram showing the main functional configuration of the processor of the payment device in the second embodiment. Figure 23 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 24 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 second embodiment. Figure 25 shows an example of a details screen displayed on the touch panel of an input device. Figure 26 shows an example of a correction screen displayed on the touch panel of an input device. Figure 27 shows an example of a correction screen displayed on the touch panel of an input device. Figure 28 shows an example of a details screen displayed on the touch panel of an input device. Figure 29 shows an example of a correction screen displayed on the touch panel of an input device. Figure 30 shows an example of a details screen displayed on the touch panel of an input device. Figure 31 is a block diagram showing the main functional configuration of the input device processor in the third embodiment. Figure 32 is a schematic diagram showing the configuration of the second data table of the input device in the third embodiment. Figure 33 is a block diagram showing the main functional configuration of the payment device processor in the third embodiment. Figure 34 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 35 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 36 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 37 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 third embodiment. Figure 38 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 39 shows an example of a connection destination selection screen displayed on the touch panel of an input device. Figure 40 shows an example of the second detail screen displayed on the touch panel of the input device. Figure 41 is a block diagram showing the main functional configuration of the input device processor in the fourth embodiment. Figure 42 is a schematic diagram showing the data structure of the detail record in the fourth embodiment. Figure 43 is a block diagram showing the main functional configuration of the payment device processor in the fourth embodiment. Figure 44 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 45 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 46 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 47 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 48 shows an example of a details screen displayed on the touch panel of an input device. Figure 49 shows an example of a payment completion screen displayed on the touch panel of the input device. Figure 50 shows an example of a receipt issued by a payment device. Figure 51 shows another example of a connection destination selection screen displayed on the touch panel of an input device. Figure 52 is a flowchart showing the main steps of information processing performed by the input device's processor according to the input program in another embodiment. Figure 53 is a flowchart showing the main steps of information processing performed by the processor of a payment device in accordance with a payment program in another embodiment.

The following describes embodiments of an accounting system that allows store clerks and customers to share the operation and settle transactions without generating payment information on an input device, in the order of the first, second, third, and fourth embodiments. 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 explained using Figures 1 to 3.

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.

The input device 11 is configured to accept data input for the goods to be bought and sold in each transaction. The settlement device 12 is configured to perform settlement processing for transactions based on the product data entered in the input device 11. In principle, the input device 11 is operated by a store employee 2, who plays 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 be store employee 2. That is, store employee 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.

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

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) in the first checkout lane can both perform settlement processing for transactions processed by the input device 11 (11-1) in the same checkout lane. The two settlement devices 12 (12-3, 12-4) in the second checkout lane can both perform settlement processing for transactions processed by the input device 11 (11-2) in the same checkout lane.

Furthermore, at least one settlement device 12 located in a single checkout lane may be capable of processing settlements for 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 processing settlements for 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 processing settlements for transactions processed not only by input device 11 (11-2) but also by input device 11 (11-1). This allows for an increase in the number of settlement devices 12 capable of processing settlements for transactions processed by a single input device 11, without the need to add additional settlement devices 12.

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.

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.

A product code is a unique code assigned to each product to identify it. Typically, each product has a barcode or QR code representing 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 items being bought and sold in a transaction by reading the barcode, QR code, or RFID tag attached to the product with a reader.

The 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. This tax information includes the tax rate and tax type (external tax, internal tax, tax-exempt).

The sales master file 132 is a data file that stores sales records created for each product sold at the 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.

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 to the other components directly or via signal input/output circuits, and transmits data signals exchanged between them.

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 this computer via the system transmission path 30.

The processor 21 corresponds to the central part of the computer described above. The processor 21 controls various parts 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).

Main memory 22 corresponds to the main memory portion of the computer described above. Main memory 22 includes both non-volatile 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 various parts, in either 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).

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), HDD (Hard Disk Drive), or SSD (Solid State Drive) can serve as the auxiliary storage device 23. The auxiliary storage device 23 stores data used by the processor 21 for various processing tasks, data created by the processing performed by the processor 21, and so on. The auxiliary storage device 23 may also store the application program described above.

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 clerk. The customer display 29 displays information to customer 3 whose purchased goods data has been entered into the input device 11.

An input device 11 with such hardware configuration can, for example, utilize an existing POS terminal. 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.

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, warning light 40, terminal interface 41, and system transmission path 42, etc. The system transmission path 42 includes an address bus, data bus, control signal lines, etc. The system transmission path 42 connects the processor 31 to the other components directly or via signal input/output circuits, and transmits data signals exchanged between them.

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 42. The payment device 12 then connects device interfaces or devices such as the change dispenser interface 36, scanner 37, touch panel 38, printer 39, warning light 40, and terminal interface 41 to this computer via the system transmission path 42.

The processor 31 corresponds to the central part of the computer described above. The processor 31 controls various parts 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.

The main memory 32 corresponds to the main memory portion of the computer described above. The main memory 32 includes both non-volatile and volatile memory areas. The non-volatile memory area of the main memory 32 stores the operating system or application programs. The main memory 32 may also store data necessary for the processor 31 to perform processing to control various parts, in either the non-volatile or volatile memory areas. The volatile memory area of the main memory 32 is used as a work area where data is rewritten as needed by the processor 31. The non-volatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer described above. For example, an EEPROM, HDD, or SSD could serve as the auxiliary storage device 33. The auxiliary storage device 33 stores data used by the processor 31 for various processing tasks, data created by the processing performed by the processor 31, and so on. The auxiliary storage device 33 may also store the application program described above.

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 constitutes an interface with an automatic change dispenser (not shown). The change dispenser interface 36 receives the amount 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.

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. The warning light 40 has, for example, two light-emitting elements, red and blue. The warning light 40 is installed at the top of a pole erected in the vicinity of the payment device 12, and lights up or flashes, for example, red or blue, depending on the state of the corresponding payment device 12.

The terminal interface 41 constitutes an interface with the cashless payment terminal 5. The cashless payment terminal 5 is an information terminal that supports cashless payments such as credit card payments, electronic money payments, and code payments. The terminal interface 41 outputs identification data for the cashless payment method selected from among several types of cashless payment methods to the cashless payment terminal 5. Since the cashless payment terminal 5 processes the transaction using the cashless payment method identified by the identification data, the terminal interface 41 receives the processing result from the cashless payment terminal 5. By connecting the cashless payment terminal 5 to the terminal interface 41, the payment device 12 becomes a device that supports not only cash payments but also cashless payments.

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

[First Embodiment]
Next, the first embodiment will be described with reference to Figures 4 to 20.
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 a connection destination selection means 51, a query means 52, a determination means 53, a disable means 54, an input side storage means 55, a detail display means 56, a termination detection means 57, a first transmission means 58, a first notification means 59, and a settlement destination notification means 510. However, the functions of the processor 21 are not limited to these.

The connection destination selection means 51 is a function that, before inputting transaction data, receives input from the input device 61 and selects one of the multiple payment devices 12 as the connection destination. The input device 61 is either a keyboard 26 or a touch panel 28. The connection destination selection means 51 has operators on the input device 61 that allow for individual selection of the multiple payment devices 12. When one of the operators is operated, the connection destination selection means 51 selects the payment device 12 specified by that operator as the connection destination.

The inquiry means 52 is a function that inquires whether a connection is possible to one of the payment devices 12 selected by the connection destination selection means 51. The payment device 12, upon receiving the inquiry, responds either "Connection OK" (allowing the connection) or "Connection NOT OK" (denying the connection).

The determination means 53 is a function that determines one of the multiple payment devices 12 as the connection destination before inputting transaction data. The determination means 53 determines the payment device 12 as the connection destination when it receives a connection permission response signal from the inquiry destination payment device 12 in response to an inquiry by the inquiry means 52.

The query means 52 and the determination means 53 operate by referring to the first data table 63. As shown in Figure 5, the first data table 63 is a data table that describes the payment device number (No.) and the connection destination flag Fa, associated with the payment device ID of the payment device 12 that can be connected to the input device 11. The payment device 12 that can be connected to are, in principle, multiple payment devices 12 installed in the same checkout lane as the input device 11. The payment device ID is identification information set for each payment device 12 to individually identify these multiple payment devices 12. The payment device number is a series of numbers assigned to the payment device 12 identified by the payment device ID. The connection destination flag Fa is a 1-bit data for identifying whether the payment device 12 identified by the corresponding payment device ID has been determined as a connection destination. In this embodiment, the connection destination flag Fa for a device determined as a connection destination is set to "1," and the connection destination flag Fa for a device not determined as a connection destination is set to "0."

Incidentally, in this embodiment, the payment device ID of payment device 12 (12-1) is set to [0001] and the payment device number to [1]. Similarly, the payment device ID of payment device 12 (12-2) is set to [0002] and the payment device number to [2], the payment device ID of payment device 12 (12-3) is set to [0003] and the payment device number to [3], and the payment device ID of payment device 12 (12-4) is set to [0004] and the payment device number to [4]. Therefore, Figure 5 illustrates the first data table 63 of the input device 11 (11-1) to which payment devices 12 (12-1) and 12 (12-2) can be connected.

The inquiry means 52 obtains the payment device ID of the payment device 12 selected by the connection destination selection means 51 from the first data table 63 and makes an inquiry to the payment device 12 identified by that payment device ID. When the determination means 53 receives a connection-ready response signal from the inquiry destination payment device 12, it changes the connection destination flag Fa corresponding to the payment device ID of that payment device 12 from "0" to "1".

The invalidation means 54 is a function that, when the inquiry means 52 receives a connection-denying response signal from the payment device 12, invalidates the operation of the operator that specifies the payment device 12 among the multiple operators located on the input device 61.

The input-side storage means 55 has the function of storing transaction data entered via the input device 61 in the input-side storage unit 64. The input-side storage unit 64 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, discount rate, etc., 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 55 creates a detail record Ra for each product to be sold as one transaction based on the entered data. As shown in Figure 6, 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 the amount calculated by multiplying the unit price by the quantity. In other words, the detail record Ra can be said to be a record that describes transaction data such as product code and quantity. The input-side storage means 55 stores the detail record Ra in the first transaction file 641 of the input-side storage unit 64.

The details display means 56 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 56 uses the display device 62 screen as the details screen SAc (see Figure 16), 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 641 on this details screen SAc. A detailed explanation of the details screen SAc will be provided later.

The termination detection means 57 has the function of detecting an instruction to complete the input of transaction-related data. The termination detection means 57 receives input from the input device 61 and detects the instruction to complete the input of transaction-related data.

The first transmission means 58 has the function of transmitting transaction data entered via the input device 61 to one of the settlement devices 12 determined as the connection destination by the determination means 53 via the communication unit 25, before the completion detection means 57 detects an instruction to end the input of the transaction data. The first transmission means 58 refers to the first data table 63 to recognize one of the settlement devices 12 determined as the connection destination by the determination means 53, i.e., the settlement device 12 whose connection destination flag Fa is set to "1". Hereinafter, one of the settlement devices 12 determined as the connection destination by the determination means 53 will be referred to as the connected settlement device 120. Each time transaction data is entered via the input device 61, the first transmission means 58 transmits the entered transaction data to the connected settlement device 120.

The first notification means 59 has the function of notifying the connected settlement device 120 of the completion of data input when the completion detection means 57 detects the end of data input related to the transaction. The first notification means 59 recognizes the connected settlement device 120 by referring to the first data table 63 and outputs a signal to the connected settlement device 120 notifying it of the completion of data input.

The payment destination notification means 510 has the function of notifying the connected payment device 120, which has been notified of the completion of input by the first notification means 59, as the payment destination. The payment destination notification means 510 notifies the store clerk 2 of the payment destination by displaying information that identifies the connected payment device 120 on the touch panel 28, which is the display device 62 for the store clerk 2. The payment destination notification means 510 may also notify the customer 3 of the payment destination by displaying information that identifies the connected payment device 120 on the customer display 29, which is the display device 62 for the customer 3. Alternatively, the payment destination notification means 510 may notify both the store clerk 2 and the customer 3 of the payment destination by displaying information that identifies the connected payment device 120 on both the touch panel 28 and the customer display 29. The information that identifies the connected payment device 120 is, for example, the payment device number set in the first data table 63.

The functions of the aforementioned connection destination selection means 51, inquiry means 52, determination means 53, invalidation means 54, input-side storage means 55, detail display means 56, termination detection means 57, first transmission means 58, first notification means 59, and settlement destination notification means 510 are realized by information processing executed by the processor 21 according to a program for the input device 11, so-called input program.

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 be of any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

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

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.

The amount display means 72 has the function of displaying the transaction settlement amount on the touch panel 38 when it receives a signal from the input device 11 indicating the end of input. The transaction settlement amount is calculated from the amount of the detail record Ra stored in the second transaction file 811 and the value discount amount. Incidentally, until the transaction settlement amount is displayed, that is, until the signal indicating the end of input is received from the input device 11, the amount display means 72 displays the standby screen SBa (see Figure 18) on the touch panel 38.

The connection response means 73, when it receives an inquiry from the input device 11 regarding the possibility of connection while the transaction settlement is possible, returns a connection-permitted response. If the connection response means 73 receives an inquiry from the input device 11 regarding the possibility of connection while the transaction settlement is impossible, it returns a connection-rejected response signal. The connection response means 73 refers to the flag memory 82 to determine whether the transaction settlement is possible. If the connection response means 73 determines that the transaction settlement is possible, it transmits a connection-permitted response, i.e., an affirmative response (OK) signal to the input device 11 via the communication unit 35. At this time, the connection response means 73 controls the warning light to illuminate, for example, in blue. If the connection response means 73 determines that the transaction settlement is impossible, it transmits a connection-rejected response, i.e., a negative response (NG) signal to the input device 11 via the communication unit 35. At this time, the warning light 40 remains off.

The flag memory 82 stores a status flag Fb, as shown in Figure 8. The status flag Fb is a 1-bit data that identifies whether the settlement device 12 is in standby mode or in the process of settlement. When the standby settlement device 12 receives transaction data from the input device 11, 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. Therefore, the connection response means 73 transmits a negative response (NG) signal. When the settlement process is completed in the settlement device 12 that is in the process of settlement, the settlement device 12 enters standby mode. When the settlement device 12 is in standby mode, it is able to settle the next transaction. Therefore, the connection response means 73 transmits an affirmative response (OK) signal. 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 Fb is set to "0" when the device is in standby mode, and the status flag Fb is set to "1" when the device is in the process of settlement.

The settlement means 74, upon receiving notification of input completion from the input device 11 via the communication unit 35, settles the transaction based on the transaction data stored in the settlement-side storage unit 81. Upon receiving the signal from the input device 11 indicating input completion, the settlement means 74 settles the transaction based on the data stored in the second transaction file 811. Once the settlement is complete, the settlement means 74 turns off the warning light 40. The settlement means 74 also clears the second transaction file 811 and changes the status flag Fb from "1" to "0". With the second transaction file 811 cleared and the status flag Fb set to "0", the settlement device 12 becomes capable of conducting transactions with the next customer.

The payment method 74 settles the transaction using the payment method selected via the payment method selection screen SBb (see Figure 19). For example, if cash payment is selected, the payment method 74 executes the settlement process for the cash transaction via the automatic change dispenser connected to the change dispenser interface 36. If credit card payment is selected, the payment method 74 executes the settlement process for the credit card transaction via the cashless payment terminal 5 connected to the terminal interface 41. If electronic money payment is selected, the payment method 74 executes the settlement process for the electronic money transaction via the cashless payment terminal 5 connected to the terminal interface 41. Since the settlement processes for cash, credit card, and electronic money transactions are well-known, detailed explanations are omitted.

The functions of the payment-side storage means 71, amount display means 72, connection response means 73, and payment means 74 described above are realized by information processing executed by the processor 21 according to a program for the payment device, a so-called payment program.

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 recorded on a removable recording medium, or distributed via communication over the network 14, and then installed in the main memory 32 or auxiliary storage device 33. The recording medium can be any form as long as it can store a program and is readable by the device, such as a CD-ROM or memory card.

Next, using the flowcharts in Figures 9 to 12 and the screen examples in Figures 13 to 20, 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. 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 screen examples 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.

First, the main 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 and 10.
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, employee 2, who is acting as the checker, declares the start of input to the input device 11. In response to this operation, the processor 21 begins processing information according to the procedure shown in the flowcharts of Figures 9 and 10.

First, the processor 21, as ACT101, sets the screen of the touch panel 28 to the connection destination selection screen SAa (see Figure 13).
Figure 13 shows an example of the display of the connection destination selection screen SAa. The connection destination selection screen SAa has a first button BAa and a second button BAb, which are operators that allow users to individually select from multiple payment devices 12 located in the same checkout lane as the input device 11.

Figure 13 shows an example of the connection destination selection screen SAa displayed on the touch panel 28 of the input device 11 (11-1). The payment devices 12 located in the same checkout lane as the input device 11 are payment device 12 (12-1) and payment device 12 (12-2). The first button BAa is for selecting payment device 12 (12-1). Therefore, the payment device number "1" for payment device 12 (12-1) is displayed on the first button BAa. The second button BAb is for selecting payment device 12 (12-2). Therefore, the payment device number "2" for payment device 12 (12-2) is displayed on the second button BAb.

Incidentally, in the input device 11 (11-2) located in the same checkout lane as payment devices 12 (12-3) and 12 (12-4), a connection selection screen SAa is displayed, which includes a first button BAa displaying payment device number "3" for payment device 12 (12-3) and a second button BAb displaying payment device number "4" for payment device 12 (12-4).

After confirming that the connection selection screen SAa is displayed on the touch panel 28, employee 2 searches for an available payment terminal 12. An available payment terminal 12 is one that does not have a customer 3 currently making a payment. Alternatively, it is a payment terminal 12 whose warning light 40 is off. Upon identifying an available payment terminal 12, the employee touches the control panel (first button BAa or second button BAb) displaying the payment terminal number of that terminal 12. For example, if employee 2 identifies payment terminal 12 (12-1) as available, they touch the first button BAa. Similarly, if employee 2 identifies payment terminal 12 (12-2) as available, they touch the second button BAb.

Let's return to the explanation of Figure 9.
The processor 21, which displays the connection destination selection screen SAa, waits for the payment device number to be entered as ACT 102. When the first button BAa located on the connection destination selection screen SAa is pressed, the processor 21 determines that the payment device number assigned to the first button BAa has been entered. When the second button BAb located on the connection destination selection screen SAa is pressed, the processor 21 determines that the payment device number assigned to the second button BAb has been entered.

When the payment device number is entered, the processor 21 proceeds from ACT 102 to ACT 103. As ACT 103, the processor 21 refers to the first data table 63 to obtain the payment device ID associated with the payment device number. Then, as ACT 104, the processor 21 controls the communication unit 25 to send a confirmation event to that payment device ID. This control sends the confirmation event to the network 14 via the communication unit 25. The confirmation event is received by one of the multiple payment devices 12 connected to the network 14, specifically the payment device 12 that has the payment device ID set as the destination for the confirmation event. The payment device 12 that receives the confirmation event sends back either an affirmative response (OK) to allow the connection, or a negative response (NG) to deny the connection.

The processor 21, which controls the transmission of the confirmation event, waits for an acknowledgment (OK) signal from the payment device 12 as ACT 105. In this waiting state, if a negative response (NG) signal is received via the communication unit 25 within a predetermined time, or if neither an acknowledgment (OK) nor a negative response (NG) signal is received, the processor 21 proceeds from ACT 105 to ACT 106. The processor 21 displays a connection failure screen SAb (see Figure 14) on the touch panel 28, indicating that connection to the payment device 12 identified by the payment device number entered as ACT 106 is not possible.

Figure 14 shows an example of the "Connection Failed" screen SAb. The "Connection Failed" screen SAb displays text indicating that connection to the payment device 12 failed, along with a confirmation button BAc. After reviewing the text, the store clerk 2 presses the confirmation button BAc by touch.

The processor 21, displaying the "Connection Unavailable" screen SAb, waits for confirmation button Bac to be input as ACT 107. Upon receiving confirmation button Bac, the processor 21 returns from ACT 107 to ACT 101. That is, the processor 21 returns the touch panel 28 screen from the "Connection Unavailable" screen SAb to the connection destination selection screen SAa (see Figure 15).

Figure 15 shows an example of the display on the connection destination selection screen SAa after receiving a negative response (NG) from payment device 12, the payment device number assigned to the first button BAa. As shown, the second button BAb can be used for touch input, but the first button BAa is grayed out and cannot be used for input. Thus, when a confirmation event is sent to payment device 12 but a negative response (NG) signal is received, the first button BAa or the second button BAb, to which the payment device number of payment device 12 (the recipient of the confirmation event) is assigned, is disabled.

After confirming the connection destination selection screen SAa in Figure 15, the store clerk 2 checks if the payment device 12 assigned to the second button BAb is available. If it is available, the clerk presses the second button BAb by touch. Upon input of the second button BAb, the processor 21 executes ACT 103 to ACT 105 in the same manner as described above. If the payment device 12 assigned to the second button BAb does not receive a negative response (NG) signal via the communication unit 25 within a predetermined time, or if it does not receive an affirmative response (OK) or negative response (NG) signal, the processor 21 executes ACT 106 and ACT 107 in the same manner as described above. Then, the processor 21 returns to ACT 101. At this point, the connection destination selection screen SAa shows the second button BAb grayed out, and the first button BAa becomes available for input.

In ACT 105, if an acknowledgment (OK) is received via the communication unit 25 within a predetermined time, the processor 21 proceeds from ACT 105 to ACT 108. As ACT 108, the processor 21 changes the connection destination flag Fa, which is associated with the payment device ID of the payment device 12 that sent the acknowledgment (OK) and described in the first data table 63, from "0" to "1". The processor 21 also sets the touch panel 28 screen to the details screen SAc (see Figure 16) as ACT 109.

Figure 16 shows an example of the details screen SAc. The details screen SAc 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, arranged in order of record number. The total area AAc displays the total quantity and total price of the purchased items.

The details screen SAc also includes software keys for the subtotal button BAd, the discount button BAe, and the discount button BAF. The subtotal button BAd is an operator used to signal that the input of purchased items in a transaction has been completed. The discount button BAe is an operator used to signal a discount on the most recently entered purchased item in a transaction. The discount button BAF is an operator used to signal a discount on the most recently entered purchased item in a transaction. Incidentally, when the operator inputs the discount button BAe and enters the discount amount using the numeric keypad on keyboard 26, the price of the item is discounted. Similarly, when the operator inputs the discount button BAF and enters the discount rate using the numeric keypad on keyboard 26, the price of the item is discounted.

In ACT109, the processor 21 uses the customer display 29 as the customer details screen. The customer details screen is the details screen SAc with the software keys removed.

After confirming that the details screen "SAc" 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. The barcode is read by the scanner 27, and the product code of the purchased item is entered into the input device 11. However, some items, such as fresh food, may 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 wishes to purchase from this list. Through this operation, the product code of the barcode-less purchased item is entered into the input device 11.

Let's return to the explanation of Figure 9.
The processor 21, displaying the details screen SAc, waits for the product code to be entered as ACT110. Once the product code is entered, the processor 21 proceeds from ACT110 to ACT111. As ACT111, the processor 21 obtains the payment device ID of the connected payment device 12. That is, the processor 21 refers to the first data table 63 and obtains the payment device ID for which the connection destination flag Fa is "1". Then, as ACT112, the processor 21 controls the communication unit 25 to send an input event with the payment device ID as the destination. This control sends the input event to the network 14 via the communication unit 25. The input event is received by one of the multiple payment devices 12 connected to the network 14, specifically the payment device 12 for which the payment device ID that is the destination of the input event is set. The input event includes the product code entered from the scanner 27 or touch panel 28.

Furthermore, processor 21 creates a detail record Ra as ACT 113. That is, processor 21 accesses server 13 and retrieves a product record containing the entered product code from product master file 131. Then, based on the product information such as product name and unit price described in that product record, 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.

Processor 21 stores the detail record Ra in the first transaction file 641 as ACT 114. Processor 21 also updates the detail screen SAc as ACT 115. Specifically, Processor 21 displays the product name, quantity, and amount of detail record Ra in the current area AAa of the detail screen SAc. If data for a detail record Ra with a record number one position prior to the current detail record Ra's record number r (r-1) is displayed in the current area AAa, Processor 21 displays the record number (r-1), product name, quantity, unit price, 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 641 in the total area AAc. Processor 21 updates the customer detail screen in the same manner.

After updating the details screen SAc, processor 21 proceeds to ACT121 in Figure 10. Processor 21 checks whether a product code has been entered as ACT121. If no product code has been entered, processor 21 proceeds from ACT121 to ACT122. Processor 21 checks whether quantity or value discount data has been entered as ACT122. If no quantity or value discount data has been entered, processor 21 proceeds from ACT122 to ACT123. Processor 21 checks whether the subtotal button BAd has been entered as ACT123. If the subtotal button BAd has not been entered, processor 21 returns from ACT123 to ACT121. Thus, after updating the details screen SAc, processor 21 enters a waiting state for product code, quantity or value discount data, and subtotal button BAd as ACT121 through ACT123.

When a product code is entered while in the waiting state of ACT121 to ACT123, the processor 21 returns from ACT121 to ACT111 in Figure 9. The processor 21 then executes the processing of ACT111 to ACT115 in the same manner as described above. Specifically, the processor 21 obtains the payment device ID of the connected payment device 12 and controls the communication unit 25 to send an input event to that payment device ID. The input event includes the product code entered from the scanner 27 or touch panel 28. The processor 21 also creates a detail record Ra and stores it in the first transaction file 641. The processor 21 then updates the detail screen SAc based on the data of the detail record Ra stored in the first transaction file 641. Afterward, the processor 21 returns to the waiting state of ACT121 to ACT123.

In the waiting state of ACTs 121 to 123, 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 BAe or discount button BAf and the numeric keypad, the processor 21 proceeds from ACT 122 to ACT 124. The processor 21 performs the same processing as described above for ACTs 111 and 112 as ACTs 124 and 125. That is, the processor 21 obtains the payment device ID of the connected payment device 12 and controls the communication unit 25 to send an input event to that payment device ID. The input event includes the entered quantity, discount amount, or discount rate.

Processor 21 updates the detail record Ra with record number r stored in the first transaction file 641 as ACT 126. 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 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, as ACT 127, Processor 21 updates the display of the current area AAa and total area AAc on the detail screen SAc using the data from the first transaction file 641 after updating detail record Ra. Processor 21 updates the customer detail screen in the same way. After that, Processor 21 returns to the waiting state of ACT 121 to ACT 123.

If the subtotal button BAd is pressed while in the standby state of ACT121 to ACT123, the processor 21 proceeds from ACT123 to ACT128. For ACT128, the processor 21 sets the touch panel 28 screen to the subtotal plane SAd (see Figure 17).

Figure 17 shows an example of the display of the sub-plan area SAd. The sub-plan area SAd includes a total area AAd where the total points and total amount are displayed. The sub-plan area SAd also includes software keys for the subtotal discount button BAg, the subtotal discount button BAh, the input completion button BAi, and the return to details button BAj. The subtotal discount button BAg is an operator used to command a discount on the total amount. The subtotal discount button BAh is also an operator used to command a discount on the total amount. Incidentally, by pressing the subtotal discount button BAg and entering the discount amount using the numeric keypad on keyboard 26, the total amount is discounted. Similarly, by pressing the subtotal discount button BAh and entering the discount rate using the numeric keypad on keyboard 26, the total amount is discounted.

The Input Complete button BAi is an operator used to indicate the completion of data entry related to a transaction. When clerk 2 has finished entering the transaction data, they touch the Input Complete button BAi. If clerk 2 has not finished entering the transaction data, they touch the Return to Details button BAj.

In ACT128, the processor 21 uses the screen of the customer display 29 as the customer subplan screen. The customer subplan screen is the subplan screen SAd with the software keys removed.

Incidentally, the details screen SAc and the sub-plan screen SAd display the identification name NAa of the connected payment device 120 that responded with an affirmative answer (OK) to the confirmation event in a portion of the screen. The identification name NAa includes the payment device number. For reference, the details screen SAc in Figure 16 and the sub-plan screen SAd in Figure 17 are examples of screens when payment device 12 (12-1), which is assigned payment device number "1," is selected as the connected payment device 120, and "[Payment Device 1]" is displayed as the identification name NAa. The store clerk 2 can easily determine from this identification name NAa that the connected payment device 120 is payment device 12 (12-1).

The processor 21, displaying the subplanning plane SAd, checks whether the button BAj (return to details) has been pressed as ACT 129. If the button BAj has not been pressed, the processor 21 proceeds from ACT 129 to ACT 130. The processor 21 then checks whether the input completion button BAi has been pressed as ACT 130. If the input completion button BAi has not been pressed, the processor 21 returns from ACT 130 to ACT 129.

The processor 21, displaying the subtotal plan (SAd) in this manner, waits for either the input of the "Return to Details" button (BAj) or the input completion button (BAi) in ACT 129 and ACT 130. If the "Subtotal Discount" button (BAg) or the "Subtotal Discount" button (BAh) is input during this waiting state, the processor 21 performs the subtotal discount or subtotal discount process and returns to the waiting state in ACT 129 and ACT 130.

When the button BAj (return to details) is pressed while in the standby state of ACT129 and ACT130, the processor 21 proceeds from ACT129 to ACT131. As ACT131, the processor 21 returns the touch panel 28 screen from the subplan screen SAd to the previous details screen SAc. Then, the processor 21 returns to the standby state of ACT121 through ACT123.

When the input completion button BAi is pressed while ACT129 and ACT130 are in standby mode, the processor 21 proceeds from ACT130 to ACT132. The processor 21 then issues a transaction number as ACT132. For example, the input device 11 is equipped with a counter for counting transaction numbers. The processor 21 increments this counter to issue a new transaction number.

The processor 21, which issued the transaction number, proceeds to ACT 133. As ACT 133, the processor 21 obtains the payment device ID of the connected payment device 12. Specifically, the processor 21 refers to the first data table 63 and obtains the payment device ID where the connection destination flag Fa is "1". Then, as ACT 134, the processor 21 controls the communication unit 25 to send a completion event to the payment device ID. This control transmits the completion event to the network 14 via the communication unit 25. The completion event is received by the payment device 12 among the multiple payment devices 12 connected to the network 14 that has the payment device ID set as the destination for the completion event. The completion event includes the transaction number issued in ACT 132.

The processor 21, having sent the completion event, proceeds to ACT 135. As ACT 135, the processor 21 notifies the payment device 12 to which the completion event was sent. For example, the processor 21 displays the payment device number assigned to 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 shown on the customer display 29. This allows the customer 3 to know which payment device 12 is available for payment.

The processor 21, having notified the settlement device 12 to which the completion event will be sent, proceeds to ACT 136. As ACT 136, the processor 21 clears the first transaction file 641. This clear deletes all detail records Ra stored in the first transaction file 641. Then, as ACT 137, the processor 21 refers to the first data table 63 and changes the connection destination flag Fa, which was set to "1", to "0". With this, the processor 21 completes the information processing according to the input program.

Thus, once the first transaction file 641 is cleared and all connection destination flags Fa in the first data table 63 are set to "0", the input device 11 becomes capable of inputting transaction data for the next customer. When the store clerk 2 declares the start of input to the input device 11, the processor 21 sets the touch panel 28 screen to the connection destination selection screen SAa. The processor 21 then executes the processing from ACT 102 onward in the same manner as described above.

Here, processor 21 implements the function of connection destination selection means 51 through the processing of ACT 101 and ACT 102. Processor 21 implements the function of inquiry means 52 through the processing of ACT 103 and ACT 104. Processor 21 implements the function of determination means 53 through the processing of ACT 105 and ACT 108. Processor 21 implements the function of invalidation means 54 through the processing of ACT 106 and ACT 101.

Furthermore, the processor 21 realizes the function of input-side storage means 55 through processing of ACT 113 and ACT 114. The processor 21 realizes the function of detail display means 56 through processing of ACT 115. The processor 21 realizes the function of completion detection means 57 through processing of ACT 130. The processor 21 realizes the function of first transmission means 58 through processing of ACT 111 and ACT 112. The processor 21 realizes the function of first notification means 59 through processing of ACT 132 to ACT 134. The processor 21 realizes the function of settlement destination notification means 510 through processing of ACT 135.

Next, the main steps of the information processing performed by the processor 31 of the payment device 12 according to the payment program will be explained using the flowcharts in Figures 11 and 12.
When the status flag Fb 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 11 and 12. First, the processor 31 sets the touch panel 38 screen as the standby screen SBa (see Figure 18) as ACT 201.

Figure 18 shows an example of the standby screen SBa. The standby screen SBa is a screen that informs the operator that the system 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 prevents customer 3 from operating it unnecessarily. For example, it could display text such as "Welcome" or "Please wait," or it could display an illustration such as the store's logo.

The processor 31, displaying the standby screen SBa, waits for a confirmation event to be transmitted from the input device 11 as ACT 202. In this waiting state, upon receiving a confirmation event via the communication unit 35, the processor 31 proceeds from ACT 202 to ACT 203. The processor 31 controls the communication unit 35 to send an acknowledgment response (OK), which authorizes connection to the input device 11, as ACT 203. This control transmits an acknowledgment response (OK) signal to the network 14 via the communication unit 35. The acknowledgment response (OK) signal includes an input device ID that identifies the input device 11 that sent the confirmation event. The acknowledgment response (OK) signal is received by the input device 11 connected to the network 14 that has the input device ID included in the signal configured.

Having sent an acknowledgment (OK), the processor 31 proceeds to ACT 204. As ACT 204, the processor 31 changes the state flag Fb in the flag memory 82 from "0" to "1". Furthermore, as ACT 205, the processor 31 controls the warning light 40 to illuminate, for example, in blue.

The processor 31, which has illuminated the warning light 40, waits for an input event transmitted from the input device 11 as ACT 206. In this waiting state, when an input event is received via the communication unit 35, the processor 31 proceeds from ACT 206 to ACT 207. The processor 31 then checks whether or not it received an input event containing a product code as ACT 207.

As mentioned above, input events include those containing a product code and those containing quantity, discount amount, or discount rate. In ACT 207, processor 31, having confirmed receipt of an input event containing a product code, proceeds to ACT 208. Processor 31 creates a detail record Ra as ACT 208. Specifically, processor 31 accesses server 13 and retrieves a product record containing the 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, processor 31 creates a detail record Ra consisting of item data such as record number r, product code, product name, unit price, quantity, discount amount, and amount. Note that the quantity is "1", the discount amount is "0", and the amount is the unit price.

The processor 31, having created the detail record Ra, proceeds to ACT 209. The processor 31 stores the detail record Ra in the second transaction file 811 as ACT 209.

On the other hand, if the received input event does not include a product code, the processor 31 proceeds from ACT 207 to ACT 210. As ACT 210, the processor 31 checks 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, the processor 31 proceeds from ACT 210 to ACT 211. As ACT 211, the processor 31 updates the detail record Ra of record number r stored in the second transaction file 811. Specifically, if it has received an input event that includes quantity, the processor 31 sets the quantity in detail record Ra to the value included in the input event, and the amount to the product of the unit price and the quantity. If it has received an input event that includes discount amount, the processor 31 writes the discount amount to detail record Ra and subtracts the discount amount from the amount. When an input event including a discount rate is received, the processor 31 calculates and writes the discount amount from the unit price and discount rate in the detail record Ra, and subtracts the discount amount from the total amount.

After completing the processing of ACT209 or ACT211, the processor 31 proceeds to ACT212. The processor 31 checks whether it has received the next input event as ACT212. If no input event has been received, the processor 31 proceeds from ACT212 to ACT213. The processor 31 checks whether it has received the completion event transmitted from the input device 11 as ACT213. If no completion event has been received, the processor 31 returns to ACT212. In this way, the processor 31 waits for input events or completion events transmitted from the input device 11 as ACT212 and ACT213.

When an input event is received while in the waiting state of ACT212 and ACT213, the processor 31 returns from ACT212 to ACT207. The processor 31 then executes the processing from ACT207 onward in the same manner as described above. Specifically, when an input event containing a product code is received, the processor 31 creates a detail record Ra and stores this detail record Ra in the second transaction file 811. When an input event containing quantity, discount amount, or discount rate is received, the processor updates the detail record Ra with record number r, i.e., the detail record Ra stored in the second transaction file 811 during the processing of the previous ACT209. The processor 31 then returns to the waiting state of ACT212 and ACT213.

When a completion event is received during the standby state of ACT212 and ACT213, the processor 31 proceeds from ACT213 to ACT221 in Figure 12. For ACT221, the processor 31 sets the touch panel 38 screen to the payment method selection screen SBb (see Figure 19).

Figure 19 shows an example of the payment method selection screen SBb. The payment method selection screen SBb includes a total area ABa where the total points and total amount are displayed. The payment method selection screen SBb also includes software keys for the cash button BBa, the credit button BBb, and the electronic money button BBc. The cash button BBa is the operator for selecting cash payment. The credit button BBb is the operator for selecting credit card payment. The electronic money button BBc is the operator for selecting electronic money payment.

Customer 3, after viewing the payment method selection screen SBb, selects their payment method. Customer 3 wishing to pay with cash touches the cash button BBa. Customer 3 wishing to pay with a credit card touches the credit button BBb. Customer 3 wishing to pay with electronic money touches the electronic money button BBc. In this embodiment, payment methods are limited to cash, credit card, and electronic money, but it goes without saying that payment methods are not limited to these three. For example, cashless payment methods such as QR code payments may also be included.

The processor 21, displaying the payment method selection screen SBb, waits for one of the payment methods to be selected as ACT 222. In this waiting state, the payment device 12 may receive a confirmation event from the input device 11 located in the same checkout lane. Therefore, the processor 31 checks whether or not a confirmation event has been received as ACT 223. If a confirmation event is received before a payment method is selected, the processor 31 proceeds from ACT 223 to ACT 224. The processor 31 controls the communication unit 35 to send a connection failure response, i.e., a negative response (NG), as ACT 224, denying connection with the input device 11. This control sends a negative response (NG) signal to the network 14 via the communication unit 35. The negative response (NG) signal includes an input device ID that identifies the input device 11 that sent the confirmation event. The negative response (NG) signal is received by the input device 11 among the multiple input devices 11 connected to the network 14 that has the input device ID included in the signal set. Processor 31, having sent a negative response (NG) signal, returns to ACT 222. Processor 21 waits for one of the payment methods to be selected.

In the standby state of ACT222, when a payment method is selected by inputting the cash button BBa, credit button BBb, or electronic money button BBc, the processor 31 proceeds to ACT225. As ACT225, the processor 31 obtains the payment type. The payment type is payment method identification data that identifies the payment method selected. For example, if the cash button BBa is input, the processor 31 obtains the payment type "cash" as the payment method identification data. If the credit button BBb is input, the processor 31 obtains the payment type "credit" as the payment method identification data. If the electronic money button BBc is input, the processor 31 obtains the payment type "electronic money" as the payment method identification data. Having obtained the payment type, the processor 31, as ACT226, sets the touch panel 38 screen to the accounting screen SBc (see Figure 20) corresponding to the payment type.

Figure 20 shows an example of the display of the accounting screen SBc when the payment type is "cash". The accounting screen SBc includes a total area ABb where the total points and total amount are displayed. The accounting screen SBc also includes software keys for the change button BBd and the staff call button BBe. The accounting screen SBc 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 SBc. Upon seeing this text, customer 3 inserts the equivalent amount of cash into the automatic change machine.

Customer 3, who wishes to change their payment method, touches the change button BBd. Customer 3, who wishes to call a staff member, touches the staff call button BBe. When the staff call button BBe is pressed, a staff call signal is output from the payment device 12 to the input device 11, and an image informing the staff member that a customer has called is displayed on the touch panel 28 of the input device 11.

The processor 31, displaying the accounting screen SBc, waits for either the completion of payment (ACT 227) or the input of the change button BBd (ACT 228). If the change button BBd is input, the processor 31 returns from ACT 228 to ACT 221. That is, the processor 31 sets the touch panel 38 screen to the payment method selection screen SBb. The processor 31 then executes the processes from ACT 222 onwards in the same manner as described above. Therefore, customer 3, who input the change button BBd via touch operation, can select a different payment method.

Incidentally, while in the waiting state of ACT227 and ACT228, the payment device 12 may receive a confirmation event from an input device 11 located in the same checkout lane. Therefore, the processor 31 checks whether or not a confirmation event has been received as ACT229. If a confirmation event is received before payment is completed, the processor 31 proceeds from ACT229 to ACT230. The processor 31 controls the communication unit 35 to send a negative response (NG) as ACT230, denying connection with the input device 11. This control sends a negative response (NG) signal to the network 14 via the communication unit 35. The negative response (NG) signal includes an input device ID that identifies the input device 11 that sent the confirmation event. The negative response (NG) signal is received by the input device 11 among the multiple input devices 11 connected to the network 14 that has the input device ID included in the signal set. After sending the negative response (NG) signal, the processor 31 returns to ACT227. The processor 21 waits for payment to be completed or for the change button BBd to be pressed.

For example, if the payment type is "cash" and the equivalent amount of cash is inserted into the automatic change dispenser, the processor 31 determines that the payment has been completed. 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.

Once payment is complete, processor 31 proceeds from ACT 227 to ACT 231. As ACT 231, processor 31 activates printer 39 to issue a transaction receipt. The transaction receipt prints the data from the detail record Ra stored in the second transaction file 811, including the product name, quantity, unit price, and total amount of the purchased items. It also prints the total amount of the purchased items, the payment amount, the change given, and the transaction number included in the completion event.

The processor 31, which issued the transaction receipt, proceeds to ACT 232. Based on the detail record Ra stored in the second transaction file 811 as ACT 232, the processor 31 performs sales processing for the purchased goods. This sales processing updates the number of items sold and the sales amount stored in the sales master file 132.

After completing the sales processing for the purchased goods, processor 31 proceeds to ACT 233. As ACT 233, processor 31 clears the second transaction file 811. This clear deletes the detail record Ra stored in the second transaction file 811. Next, as ACT 234, processor 31 changes the status flag Fb in flag memory 82 from "1" to "0". Finally, as ACT 235, processor 31 controls the flashing light 40, which was previously illuminated in blue, to turn off. With this, processor 31 completes the information processing according to the settlement program.

Thus, in the settlement device 12, where the second transaction file 811 is cleared and the status flag Fb in the flag memory 82 becomes "0", transaction settlement becomes possible. At this time, the touch panel 38 screen becomes the standby screen SBa. Also, the warning light 40 is off. In this state, when the processor 31 receives a confirmation event from the input device 11, it executes the processing from ACT 203 onwards in the same manner as described above.

Here, processor 31 realizes the function of settlement-side storage means 71 through the processing of ACT 208 and ACT 209. Processor 31 realizes the function of amount display means 72 through the processing of ACT 221 and ACT 226. Processor 31 realizes the function of connection response means 73 through the processing of ACT 202 and ACT 203, ACT 223 and ACT 224, and furthermore, ACT 229 and ACT 230. Processor 31 realizes the function of settlement means 74 through the processing of ACT 231 and ACT 232.

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.

As detailed above, in the first embodiment, the input device 11, through its functions as a connection destination selection means 51, inquiry means 52, and determination means 53, determines one of the multiple settlement devices 12 as the connection destination before inputting transaction data. When transaction data is input via the input device 61, the input device 11, through its function as a first transmission means 58, transmits the transaction data to the one settlement device 12 determined as the connection destination before an instruction to end input of the transaction data is detected. When the input device 11, through its function as a completion detection means 57, detects an instruction to end input of the transaction data, it notifies the one settlement device 12 determined as the connection destination that input has ended.
Meanwhile, the settlement device 12, which has been selected as the connection destination, stores the transaction data transmitted from the input device 11 in its settlement-side storage unit 81 as a settlement-side storage means 71 until the transaction is settled. When it receives notification from the input device 11 that input has finished, the settlement device 12 settles the transaction based on the transaction data stored in the settlement-side storage unit 81 as a settlement means.

Therefore, according to the first embodiment, the input device 11 does not need to generate settlement information including detailed information and total information of the purchased goods and transmit it to the settlement device 12. Instead, it is possible to provide an accounting system 1 in which the store clerk 2 and the customer 3 can share the operation and settle the transaction.

Furthermore, the connection destination selection means 51 of the input device 11 includes operators that can individually specify multiple payment devices. The input device 11, when it does not receive a response from the payment device 12 granting permission to connect in response to an inquiry by the inquiry means 52, disables the operation of the operator that specifies the payment device 12 through its invalidation means 54 function.

Therefore, even if the store clerk 2, who is the operator of the input device 11, selects a payment device 12 that does not respond to grant permission for connection, the corresponding operator becomes invalid, allowing the clerk to immediately select another payment device 12.

Furthermore, in the payment device 12, which has been selected as the connection destination, the touch panel 38 screen is set to the standby screen SAb until it receives notification from the input device 11 that input has finished. Upon receiving notification from the input device 11 that input has finished, the payment device 12 sets the touch panel 38 screen to the payment method selection screen SBb. In other words, when customer 3 is not present, the touch panel 38 screen in the payment device 12 is the standby screen SAb, and when customer 3 moves to the location of the payment device 12 for payment, the screen changes to the payment method selection screen SBb, which includes the transaction settlement amount. Therefore, even if the input device 11 transmits transaction data to the payment device 12 before detecting the instruction to finish inputting the data for that transaction, the settlement amount of that transaction will not be displayed on the payment device 12 until customer 3 moves to the location of the payment device 12 for payment.

[Second Embodiment]
Next, a second embodiment will be described with reference to Figures 21 to 30.
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 entered via the input completion button BAi, is issued. Therefore, the same reference numerals are used for parts common to the first embodiment, and detailed explanations are omitted.

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

The modification request means 511 is a function that accepts modifications to the detail information displayed on the detail screen SAc of the touch panel 28 via the detail display means 56. The detail area AAb of the detail screen SAc displays the product name, quantity, unit price, discount amount, and total amount of the purchased items entered in a single transaction in a list format, in order of a series of record numbers. The modification request means 511 accepts, via the input device 61, the deletion of detail record Ra where the product name, quantity, unit price, etc., are displayed in detail area AAb, or changes to the quantity, unit price, discount amount, discount rate, etc.

The first modification means 512 is a function that modifies the transaction data transmitted by the first transmission means 58 to one of the settlement devices 12, i.e., the destination settlement device 120, determined as the connection destination by the determination means 53, before the termination detection means 57 detects the end of input instruction for the transaction data. The transaction data transmitted to the destination settlement device 120 is stored in the first transaction file 641 as a detail record Ra. The first modification means 512 modifies the detail record Ra stored in the first transaction file 641 in response to input from the input device 61. For example, the first modification means 512 may delete the detail record Ra. For example, the first modification means 512 may modify the unit price, quantity, value discount amount, etc., of the detail record Ra.

The second transmission means 513 has the function of transmitting the transaction data corrected by the first correction means 512 to the connected settlement device 120 before the termination detection means 57 detects the end of data input for that transaction.

Figure 22 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, connection response means 73, and payment means 74, the processor 31 also functions as a second modification means 75.

The second modification means 75 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 in 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 58. The second modification means 75 modifies the detail records Ra stored in the second transaction file 811 based on transaction data transmitted from the input device 11 by the second transmission means 513. For example, the second modification means 75 deletes detail records Ra. For example, the second modification means 75 modifies the unit price, quantity, value discount amount, etc., of detail records Ra.

Next, using the flowcharts in Figures 23 and 24, and the screen examples in Figures 25 to 30, we will explain the content and procedures of the information processing related to the second embodiment, which is performed in the input device 11 and settlement device 12 that constitute the accounting system 1. Note that the content and procedures of the information processing described below are examples. The content and procedures can be modified as appropriate if similar effects can be achieved. Similarly, the screen examples are also examples. The content of the output text, the placement of images, the types and layouts of software keys, etc., can be modified as appropriate.

First, the essential information processing steps executed by the processor 21 of the input device 11 according to the input program will be explained using the flowchart in Figure 23. The flowchart in Figure 23 corresponds to the flowchart in Figure 10 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 10 and Figure 23.

In the first embodiment, after updating the details screen SAc in ACT 115 or ACT 127, the processor 21 entered a waiting state as ACT 121 to ACT 123, where it was waiting for product code, quantity or value discount data and the subtotal button BAd. In the second embodiment, while in the waiting state of ACT 121 to ACT 123, it further entered a waiting state as ACT 301, where it was waiting for a product displayed in the details area AAb of the details screen SAc to be selected.

Figure 25 shows an example of the details screen SAc after data related to the transactions of four purchased items has been entered. Specifically, Figure 25 shows the details screen SAc when the product codes for product AAAAAA (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 AAAAAA 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". The total area AAc displays a total score of 4 points and a total amount of 1,000 yen.

At this time, the first transaction file 641 stores the following detail records: Ra-A for product AAAA, Ra-B for product BBBBB, Ra-C for product CCCCC, and Ra-D for product DDDDD, as processed by ACT 113 and ACT 114. Furthermore, as processed by ACT 111 and ACT 112, input events including the product code for product AAAA, product BBBBB, product CCCCC, and product DDDDD are sent to the connected settlement device 120. Each input event is sent to the connected settlement device 120 each time a product code is entered. Upon transmission of these input events, the connected settlement device 120 stores the following detail records in its second transaction file 811: Ra-A for product AAAA, Ra-B for product BBBBB, Ra-C for product CCCCC, and Ra-D for product DDDDD.

Let's return to the explanation of Figure 23.
Let's assume that, while ACT121 to ACT123 and ACT301 are in standby mode, customer 3 requests to return product BBBBB. In this case, store clerk 2, who is the operator of input device 11, selects the row in detail area AAb that displays data related to product BBBBB by touch operation. When a row in detail area AAb is touched in this way, processor 21 determines that a product has been selected in ACT301.

If the processor 21 determines that a product has been selected, it proceeds from ACT 301 to ACT 302. As ACT 302, the processor 21 displays the correction screen SAe (see Figure 26) on the touch panel 28.

Figure 26 shows an example of the display of the editing screen SAe. The editing screen SAe consists of area AAe, which displays the product name of the item selected from the detail area AAb; area AAf, which displays the quantity, unit price, discount amount, and total amount of the item selected from the detail area AAb; and area AAg, which displays operation guidance, etc. The editing screen SAe also includes software keys for the Cancel button BAk, Quantity Change button BAl, Unit Price Change button BAm, Discount button BAn, Discount button BAo, Cancel button BAp, and OK button BAq. Incidentally, it is preferable that the editing screen SAe be displayed as a pop-up overlaid on the detail screen SAc.

After confirming the correction screen SAe, clerk 2 touches the Cancel button BAk. Once the Cancel button BAk is pressed, as shown in Figure 27, a strikethrough appears in the quantity, unit price, discount amount, and total amount of product BBBBB displayed in area AAf. Additionally, the quantity change button BAl, unit price change button BAm, discount button BAn, and discount button BAo are grayed out and cannot be edited. If customer 3 decides to cancel the return of product BBBBB, clerk 2 touches the Cancel button BAp. If customer 3 wants to confirm the return of product BBBBB, clerk 2 touches the OK button BAq.

Let's return to the explanation of Figure 23.
The processor 21, which displays the correction screen SAe, checks whether the OK button BAq has been entered as ACT 303. If the OK button BAq has not been entered, the processor 21 proceeds from ACT 303 to ACT 304. The processor 21 checks whether the Cancel button BAp has been entered as ACT 304. If the Cancel button BAp has not been entered, the processor 21 returns from ACT 304 to ACT 303. In this way, the processor 21, which displays the correction screen SAe, waits for either the OK button BAq or the Cancel button BAp to be entered as ACT 303 and ACT 304.

If the cancel button BAp is pressed while ACT303 and ACT304 are in standby mode, the processor 21 proceeds from ACT304 to ACT305. The processor 21 then clears the correction screen SAe as ACT305. Afterward, the processor 21 returns to the standby mode for ACT121 through ACT123 and ACT301. Thus, when the store clerk 2 presses the cancel button BAp, the correction screen SAe is cleared. As a result, the touch panel 28 screen becomes the details screen SAc shown in Figure 25.

On the other hand, if the OK button BAq is pressed while ACT303 and ACT304 are in standby mode, the processor 21 proceeds from ACT303 to ACT306. As ACT306, the processor 21 obtains the payment device ID of the connected payment device 120. That is, the processor 21 refers to the first data table 63 and obtains the payment device ID where the connection destination flag Fa is "1". Then, as ACT307, the processor 21 controls the communication unit 25 to send a correction event to the payment device ID as the destination. This control sends the correction event to the network 14 via the communication unit 25. The correction event includes the information entered on the correction screen SAe, which in this case is the information of canceling product BBBBB.

The processor 21, having sent the correction event, corrects the detail record Ra as ACT 308. Specifically, the processor 21 deletes the detail record Ra-B for product BBBBB stored in the first transaction file 641. Then, the processor 21 clears the correction screen SAe as ACT 309 and updates the detail screen SAc. Afterward, the processor 21 returns to the waiting state for ACTs 121 through 123 and ACT 301.

Figure 28 shows an example of the display of the updated details screen SAc after deleting product BBBBB. As shown in Figure 28, the product name, quantity, unit price, discount amount, and total amount of product BBBBB are removed from the details area AAb. Then, the product name, quantity, unit price, discount amount, and total amount of product DDDDD, which were displayed in the current area AAa, are 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.

In the standby state of ACT121 to ACT123 and ACT301, let's consider a case where, for example, the quantity of product BBBBB is to be changed from "1" to "3". In this case, the clerk 2 selects the row displaying the data related to product BBBBB in the detail area AAb using a touch operation. This touch operation causes the processor 21 to execute the process of ACT302. As a result of this process, the correction screen SAe is displayed on the touch panel 28, and the clerk 2 inputs the quantity change button BAl. When the quantity change button BAl is input, as shown in Figure 29, 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 the clerk 2 to recognize that a quantity correction has been instructed. Note that the cancel button BAk, the unit price change button BAm, the discount button BAn, and the discount button BAo are grayed out and cannot be input. The employee 2, who instructed the quantity correction, uses the numeric keypad on keyboard 26 to input the corrected quantity "3" and then presses the OK button (BAq).

When the OK button BAq is pressed, the processor 21 executes the processes of ACT 306 to ACT 309. Specifically, the processor 21 sends a correction event to the connected settlement device 120. The correction event includes information entered on the correction screen SAe, namely, in this case, information to correct the quantity of product BBBBB from "1" to "3". The processor 21 also corrects the detail record Ra. Specifically, the processor 21 corrects the quantity in detail record Ra-B of product BBBBB stored in the first transaction file 641 from "1" to "3". The processor 21 also corrects the amount in detail record Ra-B from 300 yen to 900 yen. Finally, the processor 21 updates the detail screen SAc.

Figure 30 shows the details screen SAc after the quantity of product BBBBB has been corrected from "1" to "3". As shown in Figure 30, 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.

In the standby state of ACT121 to ACT123 and ACT301, for example, to modify the unit price of product BBBBB, clerk 2 inputs the unit price change button BAm on the modification screen SAe, enters the modified unit price using the numeric keypad, and then inputs the OK button BAq. For example, to modify the discount amount of product BBBBB, clerk 2 inputs the discount button BAn on the modification screen SAe, enters the modified discount amount using the numeric keypad, and then inputs the OK button BAq. For example, to modify the discount rate of product BBBBB, clerk 2 inputs the discount button BAo on the modification screen SAe, enters the modified discount rate using the numeric keypad, and then inputs the OK button BAq.

These operations cause the processor 21 to execute ACTs 306 through 309. Specifically, the processor 21 sends a correction event to the connected payment device 120. The processor 21 also corrects the detail record Ra. Finally, the processor 21 updates the detail screen SAc.

Subsequently, when the subtotal button BAd is pressed, the processor 21 proceeds to ACT 128 in Figure 10. The processor 21 then executes the processing from ACT 128 onward in the same manner as in the first embodiment.

Here, processor 21 realizes the function of correction reception means 511 through processing of ACT 301 and ACT 302. Processor 21 realizes the function of first correction means 512 through processing of ACT 308. Processor 21 realizes the function of second transmission means 513 through processing of ACT 306 and ACT 307.

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

The processor 31, similar to the first embodiment, sets the touch panel 38 screen as the standby screen SBa as ACT 201. The processor 31 then waits for a confirmation event transmitted from the input device 11 as ACT 202. In this waiting state, upon receiving a confirmation event via the communication unit 35, the processor 31 executes the processing of ACTs 202 to ACT 205. Subsequently, the processor 31 waits for an input event transmitted from the input device 11 as ACT 206. In this waiting state, upon receiving an input event via the communication unit 35, the processor 31 executes the processing of ACTs 207 to ACT 211. Afterward, the processor 31 waits for an input event or a completion event as ACTs 212 and ACT 213.

In the second embodiment, while in the waiting state for ACT 212 and ACT 213, the processor 31 further waits for a modification event as ACT 401. Upon receiving a modification event, the processor 31 proceeds from ACT 401 to ACT 402. The processor 31 modifies the detail record Ra stored in the second transaction file 811 as ACT 402. Specifically, for example, if the processor 31 receives a modification event containing information about the cancellation of product BBBBB, it deletes the detail record Ra-B for product BBBBB from the second transaction file 811. If the processor 31 receives a modification event containing information about modifying the quantity of product BBBBB, it modifies the quantity and amount in detail record Ra-B. If the processor 31 receives a modification event containing information about modifying the unit price, discount amount, or discount rate of product BBBBB, it modifies the unit price or discount amount and amount in detail record Ra-B.

Once the modification of the detail record Ra is complete, the processor 31 returns to the waiting state for ACT 212, ACT 213, and further for ACT 401. If a completion event is received in this waiting state, the processor 31 proceeds to ACT 221 in Figure 12. Thereafter, the processor 21 executes the processing from ACT 221 onwards in the same manner as in the first embodiment.

Here, the processor 31 realizes the function of the second modification means 75 through the processing of ACT 402.

Thus, in the second embodiment as well, the accounting system 1 can be provided in which the store clerk 2 and the customer 3 can share the operation and settle the transaction without the input device 11 generating settlement information including detailed information and total information of the purchased goods and transmitting it to the settlement device 12. Furthermore, according to the accounting system 1 of the second embodiment, the data of purchased goods for a single transaction entered into the input device 11 can be retrospectively modified before the input completion instruction, which is the input of the input completion button BAi, is given.

[Third Embodiment]
Next, a third embodiment will be described with reference to Figures 31 to 39.
The third embodiment adds a function to the accounting system 1 of the first embodiment that, after an input completion instruction is given by pressing the input completion button BAi, 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.

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

The cancellation reception means 514 is a function that receives a settlement cancellation instruction for a transaction whose input completion has been notified by the first notification means 59. When the cancellation reception means 514 receives an operation input via the input device 61 instructing the settlement cancellation of a transaction, it receives a signal corresponding to that operation input as a settlement cancellation instruction signal.

The cancellation target selection means 515 is a function that selects the payment device 12 to cancel the payment from among multiple payment devices 12. The cancellation target selection means 515 selects the payment device 12 specified via the input device 61 as the payment device 12 to cancel the payment. Hereinafter, the payment device 12 to cancel the payment will be referred to as the cancellation target payment device 121.

The second notification means 516, upon receiving a transaction settlement cancellation instruction from the cancellation reception means 514, has the function of notifying the cancellation destination settlement device 121 of the settlement cancellation via the communication unit 25.

The cancellation target selection means 515 and the second notification means 516 operate by referring to the second data table 65. As shown in Figure 32, the second data table 65 is a data table that describes the payment device number (No.) and the cancellation target flag Fc, associated with the payment device ID of the payment device 12 that may be the cancellation target for the input device 11. The payment device 12 that may be the cancellation target are, in principle, multiple payment devices 12 installed in the same checkout lane as the input device 11. The payment device number is a series of numbers assigned to the payment device 12 identified by the payment device ID. The cancellation target flag Fc is a 1-bit data for identifying whether the payment device 12 identified by the corresponding payment device ID has been selected as the cancellation target. In this embodiment, the cancellation target flag Fc for a selected cancellation target is set to "1", and the cancellation target flag Fc for a non-selected cancellation target is set to "0".

The third modification means 517 is a function that modifies the transaction data stored in the input-side storage unit 64, conditional on the cancellation of the payment being acknowledged by the cancellation destination payment device 121 in response to the payment cancellation notification. The data in the first transaction file 641 is copied to the third transaction file 642 when a completion event is sent to the cancellation destination payment device 121. The third modification means 517 modifies the detail record Ra stored in the third transaction file 642 in response to input from the input device 61. For example, the third modification means 517 may delete the detail record Ra. For example, the third modification means 517 may modify the unit price, quantity, value discount amount, etc., of the detail record Ra.

The third transmission means 518 has the function of transmitting the transaction data modified by the third modification means 517 to the cancellation settlement device 121 via the communication unit 25. The third transmission means 518 transmits the modified transaction data to the cancellation settlement device 121 each time the transaction data is modified.

The non-cancellation notification means 519 is a function that notifies that the payment cannot be canceled if there is no acknowledgment from the cancellation destination payment device 121 in response to the payment cancellation notification. The non-cancellation notification means 519 notifies, for example, by displaying text or an image on the display device 62 indicating that the payment cannot be canceled.

Figure 32 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, connection response means 73, and payment means 74, the processor 31 also functions as a cancellation response means 76 and a fourth modification means 77.

The cancellation response means 76 is a function that, upon receiving a payment cancellation notice from the input device 11 before the transaction is settled by the settlement means 74, returns a response authorizing the payment cancellation. If the cancellation response means 76 receives a payment cancellation notice from the input device 11 after the transaction has been settled by the settlement means 74, it does not return a response authorizing the payment cancellation.

The fourth modification means 77 is a function that modifies the 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. The fourth modification means 77 modifies the detail record Ra stored in the second transaction file 811 with the transaction data transmitted from the input device 11 by the third transmission means 518. For example, the fourth modification means 77 deletes the detail record Ra. For example, the fourth modification means 77 modifies the unit price, quantity, value discount amount, etc., of the detail record Ra.

Next, using the flowcharts in Figures 33 to 37 and the screen examples in Figures 38 and 39, we will explain the content and procedures of the information processing related to the third embodiment, which is performed in the input device 11 and settlement device 12 that constitute the accounting system 1. 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 screen examples 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.

First, the essential information processing steps executed by the processor 21 of the input device 11 according to the input program will be explained using flowcharts in Figures 34 to 36. The flowchart in Figure 34 corresponds to the flowchart in Figure 10 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 10 and Figure 35. The flowchart in Figure 35 corresponds to the flowchart in Figure 9 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 9 and Figure 35.

As shown in Figure 34, in the third embodiment, some of the processing steps after the input completion button BAi is pressed differ from those in the first embodiment. Specifically, when the input completion button BAi is pressed, the processor 21 issues a transaction number as ACT 132. The processor 21 also obtains the settlement device ID of the connected settlement device 120 as ACT 133. Then, the processor 21 controls the communication unit 25 to send a completion event to the settlement device ID as the destination as ACT 134. The processor 21 also notifies the settlement device 12, the destination of the completion event, as ACT 135.

Having thus notified the settlement device 12, the recipient of the completion event, the processor 21 proceeds to ACT 501. As ACT 501, the processor 21 copies all detail records Ra stored in the first transaction file 641 to the third transaction file 642. Then, as ACT 136, the processor 21 clears the first transaction file 641. Furthermore, as ACT 137, the processor 21 refers to the first data table 63 and changes the connection destination flag Fa, which was set to "1", to "0". With this, the processor 21 completes the information processing according to the input program.

In this third embodiment, after the processor 21 has finished sending a completion event to the connected settlement device 120, it has the function of copying all detail records Ra stored in the first transaction file 641 to the third transaction file 642 and clearing the first transaction file 641. Therefore, the third transaction file 642 stores the detail records Ra of the transactions settled by the connected settlement device 120 that sent the completion event. Meanwhile, since the first transaction file 641 is cleared and all connection flags Fa become "0", the input device 11 can input data related to the next customer transaction.

The processor 21 of the input device 11, which is now ready to input data related to the next customer transaction, begins information processing according to the procedure shown in the flowchart of Figure 35. Specifically, the processor 21, as ACT 511, sets the screen of the touch panel 28 to the connection destination selection screen SAf (see Figure 39).

Figure 39 shows an example of the display of the connection destination selection screen SAf in the third embodiment. The difference between the connection destination selection screen SAf and the connection destination selection screen SAa in the first embodiment is the addition of a software key for the payment modification button Bar. If customer 3, who has moved to the payment device 12, requests a modification to their transaction before completing the payment, the store clerk 2 inputs the payment modification button Bar by touch. This modification may occur, for example, if there is an error in the quantity of goods or if a discount has not been applied. Alternatively, it may occur if customer 3 cancels the transaction.

Let's return to the explanation of Figure 35.
The processor 21, displaying the connection destination selection screen SAf, proceeds to ACT 512. The processor 21 checks whether a payment device number has been entered as ACT 512. If no payment device number has been entered, the processor 21 proceeds from ACT 512 to ACT 513. The processor 21 checks whether the payment modification button Bar has been entered as ACT 513. If no payment modification button Bar has been entered, the processor 21 returns from ACT 513 to ACT 512. In this way, the processor 21, displaying the connection destination selection screen SAf, waits for either a payment device number to be entered as ACT 512 or ACT 513, or for the payment modification button Bar to be entered.

When a payment device number is entered while ACT 512 and ACT 513 are in standby mode, processor 21 proceeds from ACT 512 to ACT 103. Processor 21 executes the processing from ACT 103 onward in the same manner as in the first embodiment.

If the payment modification button Bar is pressed while ACT512 and ACT513 are in standby mode, processor 21 proceeds from ACT513 to ACT514. Processor 21, as ACT514, waits for the payment device number to be entered via the connection destination selection screen SAf.

The store clerk who pressed the payment correction button BAr then touches either the first button BAa or the second button BAb, which is assigned the payment device number of the payment device 12 that customer 3, who requested the correction, was attempting to settle.

In ACT 514, the processor 21, having confirmed that the payment device number has been entered, proceeds to ACT 515. In ACT 515, the processor 21 refers to the second data table 65 to obtain the payment device ID associated with the payment device number. Then, in ACT 516, the processor 21 controls the communication unit 25 to send a payment cancellation event to that payment device ID. This control transmits the payment cancellation event to the network 14 via the communication unit 25. The payment cancellation event is received by one of the multiple payment devices 12 connected to the network 14, specifically the payment device 12 that has the payment device ID set as the destination for the payment cancellation event. The payment device 12 that receives the payment cancellation event, i.e., the cancellation destination payment device 121, sends back either an affirmative response (OK) authorizing the cancellation of the payment, or a negative response (NG) rejecting the cancellation.

The processor 21, which sent the payment cancellation event, proceeds from ACT 516 to ACT 517. As ACT 517, the processor 21 waits for an acknowledgment (OK) from the payment device 121. If an acknowledgment (OK) signal is not received within a certain time during this waiting state, the processor 21 proceeds from ACT 517 to ACT 518. As ACT 518, the processor 21 notifies that the payment cannot be canceled. For example, the processor 21 notifies this by displaying text or an image on the touch panel 28 indicating that the payment cannot be canceled. At this point, the processor 21 completes the information processing according to the input program.

In ACT 517, if an acknowledgment (OK) signal is received within a certain time, the processor 21 proceeds to ACT 519. As ACT 519, the processor 21 copies all detail records Ra stored in the third transaction file 642 to the first transaction file 641. Then, as ACT 520, the processor 21 clears the third transaction file 642. Furthermore, as ACT 521, the processor 21 changes the cancellation flag Fc, which is associated with the settlement device ID of the settlement device 12 that sent the acknowledgment (OK), i.e., the cancellation destination settlement device 121, and is described in the second data table 65, from "0" to "1". Afterward, as ACT 520, the processor 21 uses the data of the detail records Ra copied to the first transaction file 641 to set the touch panel screen to the second detail screen SAg (see Figure 40).

Figure 40 shows an example of the display of the second detail screen SAg. Compared to the detail screen SAc displayed in ACT 109 (see Figure 16), the second detail screen SAg adds a batch cancellation button BAs to the software key. Also, the subtotal button BAd has been changed to a complete button BAt. 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 641, and the total area AAc displays the total points and total amount of the same detail record Ra. The second detail screen SAg also displays the identification name NAb of the cancellation destination settlement device 121 selected by the connection destination selection screen SAf. Incidentally, the second detail screen SAg in Figure 40 is an example screen where settlement device 12 (12-1) is selected as the cancellation destination settlement device 121, and "[Settlement Device 1]" is displayed as the identification name NAb.

The processor 21, displaying the second detail screen SAg, proceeds to ACT 531 in Figure 36. As ACT 531, the processor 21 checks whether the "Batch Cancel" button BAs has been entered. If the "Batch Cancel" button BAs has not been entered, the processor 21 proceeds from ACT 531 to ACT 532. As ACT 532, 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 returns to ACT 531. In this way, the processor 21 waits for either the "Batch Cancel" button BAs to be entered or a product to be selected as ACT 531 and ACT 532.

If customer 3 requests to cancel the transaction, clerk 2 presses the "cancel all" button BAs. 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 names, etc., of the relevant purchased items are displayed.

When the batch cancellation button BAs is pressed while ACT 531 and ACT 532 are in standby mode, the processor 21 proceeds from ACT 531 to ACT 533. As ACT 533, the processor 21 obtains the payment device ID of the cancellation destination payment device 121. That is, the processor 21 refers to the second data table 65 and obtains the payment device ID where the cancellation destination flag Fc is "1". Then, as ACT 534, the processor 21 controls the communication unit 25 to send a batch cancellation event to the payment device ID as the destination. This control transmits the batch cancellation event to the network 14 via the communication unit 25. The batch cancellation event is received by the cancellation destination payment device 121, among the multiple payment devices 12 connected to the network 14, which has the payment device ID set as the destination for the batch cancellation event. The batch cancellation event includes the payment device ID obtained in the processing of ACT 515.

The processor 21, having sent the batch cancellation event, proceeds to ACT 535. As ACT 535, the processor 21 clears the first transaction file 641. Then, as ACT 536, the processor 21 refers to the second data table 65 and changes the cancellation destination flag Fc, which was set to "1", to "0". With this, the processor 21 completes the information processing according to the input program.

When ACT 531 and ACT 532 are in standby mode, if the processor 21 determines that a product has been selected, it proceeds from ACT 532 to ACT 537. As ACT 537, the processor 21 displays the modification screen SAe (see Figure 26) on the touch panel 28. The modification screen SAe is the same as the modification screen SAe described in the second embodiment. Furthermore, the information processing by the processor 21 in response to the operation input of the store clerk 2 on this modification screen SAe is also the same as in the second embodiment.

In other words, the processor 21, which displays the correction screen SAe, waits for either the OK button (BAq) input as ACT 538 or the Cancel button (BAp) input as ACT 539. If the Cancel button (BAp) is input during the waiting state of ACT 538 and ACT 539, the processor 21 proceeds from ACT 539 to ACT 540. The processor 21 then clears the correction screen SAe as ACT 540. After that, the processor 21 proceeds to ACT 545.

On the other hand, if the OK button BAq is input while ACT 538 and ACT 539 are in standby state, the processor 21 proceeds from ACT 538 to ACT 541. The processor 21 obtains the payment device ID of the cancellation destination payment device 121 as ACT 541. That is, the processor 21 refers to the second data table 65 and obtains the payment device ID for which the cancellation destination flag Fc is "1". Then, the processor 21 controls the communication unit 25 to send a correction event to the payment device ID as the destination as ACT 542. This control sends the correction event to the network 14 via the communication unit 25. The correction event is received by the cancellation destination payment device 121, which is the destination of the correction event, among the multiple payment devices 12 connected to the network 14. The correction event includes information entered for the correction screen SAe. For example, if the cancel button BAk is input on the correction screen SAe, the processor 31 includes information that the selected product has been canceled. For example, if the quantity change button BAl is pressed on the modification screen SAe, and then the modified quantity is entered, the processor 31 includes information to modify the quantity of the selected product to the modified quantity. Similarly, if the unit price change button BAm, the discount button BAn, or the discount button BAO are pressed on the modification screen SAe, the processor 31 includes information to modify the unit price, discount amount, or discount rate of the selected product, just as when the quantity change button BAl is pressed.

The processor 21, having sent the modification event, proceeds to ACT 543. As ACT 543, the processor 21 modifies the detail record Ra stored in the first transaction file 641. For example, if the Cancel button BAk is selected on the modification screen SAe, the processor 31 deletes the detail record Ra of the selected product. For example, if the Quantity Change button BAl is selected on the modification screen SAe, and a modified quantity is also entered, the processor 31 modifies the quantity and amount of the detail record Ra of the selected product. Similarly, if the Unit Price Change button BAm, Discount button BAn, or Price Reduction button BAo are selected on the modification screen SAe, the 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 BAl were selected. Then, as ACT 544, the processor 21 clears the modification screen SAe and updates the second detail screen SAg. Afterward, the processor 21 proceeds to ACT 545.

Thus, when the correction screen SAe is cleared in ACT 540, or the second detail screen SAg is updated in ACT 544, the processor 21 proceeds to ACT 545. In ACT 545, 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 ACT 545 to ACT 546. In ACT 546, the processor 21 checks whether the complete button BAt has been entered. If the complete button BAt has not been entered, the processor 21 returns from ACT 546 to ACT 545. In this way, the processor 21 waits for a product to be selected or for the complete button BAt to be entered in ACT 545 and ACT 546.

If a product is selected while ACT545 and ACT546 are in standby mode, processor 21 returns from ACT545 to ACT537. Then, processor 21 executes the processing of ACT537 through ACT544 in the same manner as described above.

On the other hand, if the completion button BAt is pressed while ACT545 and ACT546 are in the waiting state, the processor 21 proceeds from ACT546 to ACT547. As ACT547, the processor 21 obtains the payment device ID of the cancellation destination payment device 121. That is, the processor 21 refers to the second data table 65 and obtains the payment device ID where the cancellation destination flag Fc is "1". Then, as ACT548, the processor 21 controls the communication unit 25 to send a correction completion event with the payment device ID as the destination. This control sends the correction completion event to the network 14 via the communication unit 25. The correction completion event includes the payment device ID obtained in ACT547.

The processor 21, having sent the correction completion event, proceeds to ACT 549. As ACT 549, the processor 21 notifies that the transaction correction is complete. For example, the processor 21 displays a message on the customer display 29 indicating that the transaction correction is complete. Upon receiving this notification, customer 3 moves to the location of the settlement device 12 where the settlement was interrupted and completes the settlement.

Upon notifying that the transaction modification is complete, processor 21 proceeds to ACT 550. As ACT 550, processor 21 clears the first transaction file 641. Then, as ACT 551, processor 21 refers to the second data table 65 and changes the cancellation destination flag Fc, which was set to "1", to "0". With this, processor 21 completes the information processing according to the input program.

Here, the processor 21 implements the function of a cancellation reception means 514 through the processing of ACTs 511 to 513. The processor 21 implements the function of a cancellation destination selection means 515 through the processing of ACT 514. The processor 21 implements the function of a second notification means 516 through the processing of ACTs 515 and 516. The processor 21 implements the function of a third modification means 517 through the processing of ACTs 535 and 543. The processor 21 implements the function of a third transmission means 518 through the processing of ACTs 533 and 534, and ACTs 541 and 542. The processor 21 implements the function of an unnotification means 519 through the processing of ACT 518.

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 37 and 38. The processing steps shown in the flowchart of Figure 37 correspond to the processing steps from ACT 221 onwards in Figure 12 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 12 and Figure 38.

In ACT 221, the processor 31, which displayed the payment method selection screen SBb, waits for a payment method to be selected as ACT 222. In the third embodiment, during this waiting state, the payment device 12 may receive a payment cancellation event from the input device 11 located in the same checkout lane. Therefore, the processor 31 checks whether a payment cancellation event has been received as ACT 601. If a payment cancellation event is received before a payment method is selected, the processor 31 proceeds from ACT 601 to ACT 611 in Figure 38.

Furthermore, in ACT 226, the processor 31, which displays the accounting screen SBc, waits for either the completion of payment (ACT 227) or the input of the change button BBd (ACT 228). In the third embodiment, even in this waiting state, the payment device 12 may receive a payment cancellation event from the input device 11 located in the same checkout lane. Therefore, the processor 31 checks whether or not a payment cancellation event has been received (ACT 602). If a payment cancellation event is received before payment is completed, the processor 31 proceeds from ACT 602 to ACT 611 in Figure 38.

Thus, if a payment cancellation event is received before the payment method is entered or before payment is completed, the processor 31 proceeds to ACT 611. As ACT 611, the processor 31 sends a response to the input device 11 that sent the payment cancellation event, which is an acknowledgment (OK) signal authorizing the cancellation of the payment. After that, the processor 31 checks as ACT 612 whether or not a modification event has been received. If no modification event has been received, the processor 31 proceeds from ACT 612 to ACT 613. The processor 31 checks as ACT 613 whether or not a modification completion event has been received. If no modification completion event has been received, the processor 31 proceeds from ACT 613 to ACT 614. The processor 31 checks as ACT 614 whether or not a bulk cancellation event has been received. If no bulk cancellation event has been received, the processor 31 returns from ACT 614 to ACT 612. In this manner, the processor 31 waits for either a correction event, a correction completion event, or a batch cancellation event to be received in ACTs 612 through 614.

When a modification event is received while in the waiting state for ACTs 612 to 614, the processor 31 proceeds from ACT 612 to ACT 615. The processor 31 modifies the data of the detail record Ra stored in the second transaction file 811 as ACT 615, based on the information contained in the modification event. This modification is the same as the processing of ACT 402 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 ACT 612 and again enters a waiting state for modification events, modification completion events, and batch cancellation events.

If a correction completion event is received while in the waiting state of ACTs 612 through 614, the processor 31 proceeds from ACT 613 to ACT 221 in Figure 37. The processor 31 then executes the processing from ACT 221 onward in the same manner as described above.

If a batch cancellation event is received while in the waiting state of ACT 612 through ACT 614, processor 31 proceeds from ACT 614 to ACT 616. Processor 31 clears the second transaction file 811 as ACT 616. With this, processor 31 completes the information processing according to the settlement program.

Here, processor 31 realizes the function of cancellation response means 76 through the processing of ACT 611. Processor 31 also realizes the function of fourth modification means 77 through the processing of ACT 615 and ACT 616.

Thus, even in the third embodiment, the accounting system 1 can be provided that allows the store clerk 2 and the customer 3 to share the operation and settle the transaction without the input device 11 generating settlement information including detailed information and total information of the purchased goods and transmitting it to the settlement device 12. Furthermore, according to the accounting system 1 of the third embodiment, after the input completion instruction, which is the input of the input completion button BAi, is given, the transaction for which the input completion instruction was given can be returned and corrected.

[Fourth Embodiment]
Next, a fourth embodiment will be described with reference to Figures 41 to 50.
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.

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 code is printed on it. A data record for each gift certificate, created in the same format as the product record, is stored in the product master file 131. The gift certificate data record uses the gift certificate code as the product code, the gift certificate name as the product name, and the face value as the unit price.

Figure 41 is a block diagram showing the main functional configuration of the processor 21 of the input device 11. In addition to the connection destination selection means 51, inquiry means 52, determination means 53, invalidation means 54, input-side storage means 55, detail display means 56, completion detection means 57, first transmission means 58, first notification means 59, and settlement destination notification means 510, the processor 21 also functions as a voucher identification means 520, calculation means 521, and completion notification means 522.

The gift certificate identification means 520 has the function of identifying whether the transaction data entered via the input device 61 is data relating to a gift certificate product or data relating to 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 gift certificate identification means 520 identifies that the transaction data is data relating to a gift certificate product. When the transaction data is a product code, the gift certificate identification means 520 identifies that the transaction data is data relating to a product other than a gift certificate product.

The input-side storage means 55, upon receiving transaction data, creates a detail record Rb for the goods or gift certificates to be sold as a single transaction based on the input data. As shown in Figure 42, 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 Fd, associated with a series of record numbers. The gift certificate flag Fd 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 Fd indicating that it is a detail record Rb for gift certificates is set to "1", and the value of the gift certificate flag Fd indicating that it is a detail record Rb for goods other than gift certificates is set to "0". When the data related to a transaction input via the input device 61 is identified by the gift certificate identification means 520 as data related to a gift certificate product transaction, the input-side storage means 55 creates a detail record Rb with the value of the gift certificate flag Fd set to "1", i.e., a detail record Rb for gift certificates. When the input-side storage means 55 detects that the transaction data entered via the input device 61 is related to a transaction of a product other than a gift certificate by the gift certificate identification means 520, it creates a detail record Rb with the value of the gift certificate flag Fd set to "0," i.e., a detail record Rb for a product other than a gift certificate. The input-side storage means 55 stores the detail record Rb for the gift certificate or the product other than a gift certificate in the first transaction file 641 of the input-side storage unit 64.

The calculation means 521 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 641 of the input-side storage unit 64. The calculation means 521 displays the calculated total amount on the display device 62.

The completion notification means 522 is a function that notifies payment completion when the total transaction amount calculated by the calculation means 521 is 0 or a negative value, at the time when the completion detection means 57 detects the end of input instruction for transaction-related data. The completion notification means 522 notifies payment completion, for example, using a display device 62.

Figure 43 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, connection response means 73, and payment means 74, the processor 31 also functions as a voucher identification means 78 and a receipt output means 79.

The voucher identification means 78 has the function of identifying whether the transaction data stored in the settlement-side storage unit 81 is data related to a transaction of a voucher product or data related to a transaction of a product other than a voucher product. Similar to the voucher identification means 520 of the input device 11, the voucher identification means 78 identifies that the transaction data is related to a transaction of a voucher product when the transaction data is a voucher code. The voucher identification means 78 identifies that the transaction data is related to a transaction of a product other than a voucher product when the transaction data is a product code.

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 55 and stored in the first transaction file 641 of the input-side storage unit 64. When the transaction data transmitted from the input device 11 and received via the communication unit 35 is identified by the voucher identification means 78 as data relating to a voucher product transaction, the settlement-side storage means 71 creates a detail record Rb with the value of the voucher flag Fd set to "1", i.e., a detail record Rb for a voucher. When the transaction data transmitted from the input device 11 and received via the communication unit 35 is identified by the voucher identification means 78 as data relating to a product other than a voucher product, the settlement-side storage means 71 creates a detail record Rb with the value of the voucher flag Fd set to "0", i.e., a detail record Rb for a product other than a voucher. 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.

The receipt output means 79 is a function that outputs a receipt for transactions settled by the payment means 74, which separately shows the face value of the gift certificate in addition to 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.

Next, using the flowcharts in Figures 44 to 47, the screen examples in Figures 48 and 49, and the receipt example in Figure 50, the content and procedure of the information processing related to the fourth embodiment, which is performed in the input device 11 and payment device 12 constituting the accounting system 1, will be explained. Note that the content and procedure of the information processing described below are examples. The content and procedure can be modified as appropriate if similar effects can be achieved. Also, the screen examples and receipt examples are examples only. The content of the output text, the arrangement of images, the types and layouts of software keys, etc., can be modified as appropriate.

First, the essential information processing steps executed by the processor 21 of the input device 11 according to the input program will be explained using the flowcharts in Figures 44 and 45. The flowchart in Figure 44 corresponds to the flowchart in Figure 9 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 9 and Figure 44. Figure 45 corresponds to the flowchart in Figure 10 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 10 and Figure 45.

In ACT 110 in Figure 44 or ACT 121 in Figure 45, when the product code of the purchased item is entered, the processor 21 executes the processing of ACTs 111 to 113, similar to the first embodiment. That is, the processor 21 obtains the payment device ID of the connected payment device 12 and controls the communication unit 25 to send an input event containing the product code of the purchased item to this payment device ID. The processor 21 also creates a detail record Rb. Specifically, the processor 21 accesses the server 13 and obtains a data 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 data 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.

On the other hand, if the gift certificate code is entered in ACT 110 in Figure 44 or ACT 121 in Figure 45, the processor 21 executes the processing of ACTs 111 to 113. That is, the processor 21 obtains the payment device ID of the connected payment device 12 and controls the communication unit 25 to send an input event containing the gift certificate code to this payment device ID. The processor 21 also creates a detail record Rb. Specifically, the processor 21 accesses the server 13 and obtains a data record containing the entered gift certificate code from the product master file 131. Based on the information such as the gift certificate name and face value described in that data record, the processor 21 creates a detail record Rb consisting of item data such as record number r, product code (gift certificate code), product name (gift certificate name), unit price (face value), quantity, and amount. The product code in the detail record Rb is the gift certificate code. The product name is the gift certificate name.

After completing ACT 113, the processor 21 proceeds to ACT 701. In ACT 701, the processor 21 identifies whether the detail record Rb is a product detail record or a gift certificate detail record. If the product code contained in detail record Rb is a gift certificate code, the processor 21 recognizes it as a gift certificate detail record Rb. If the product code contained in 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.

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

In contrast, if the detail record Rb is a detail record for a gift certificate, the processor 21 proceeds from ACT 701 to ACT 703. As ACT 703, the processor 21 sets the gift certificate flag Fd of detail record Rb to "1". Also, as ACT 704, the processor 21 adds a minus sign to the amount of detail record Rb.

After completing the processing in ACT 702 or ACT 704, the processor 21 proceeds to ACT 114. The processor 21 then performs the processing in ACT 114 and ACT 115 in the same manner as in the first embodiment. That is, the processor 21 stores the detail record Rb in the first transaction file 641. The processor 21 then updates the detail screen SAc.

Figure 48 shows the details screen SAc after scanning the barcode of a gift certificate with a face value of 1000 yen using scanner 27. As shown in the figure, the current area AAa displays the name, quantity, and face value of the gift certificate. A minus sign is attached to the face value.

After completing ACT 115, the processor 21 enters a waiting state for ACTs 121 through 123. In this waiting state, when a barcode on a product or gift certificate is scanned, the processor 21 executes ACTs 111 through 113, ACTs 701 through 704, and further, ACTs 114 and 115, in the same manner as described above.

In the standby state of ACT121 to ACT123, if the subtotal button BAd is input, the processor 21 sets the touch panel 28 screen to the subtotal screen SAd, similar to the first embodiment. The processor 21 then waits for the input of the return-to-details button BAj or the input complete button BAi in ACT129 and ACT130.

When the input completion button BAi is pressed while ACT129 and ACT130 are in standby mode, processor 21 proceeds from ACT130 to ACT711. Processor 21 calculates the total amount in ACT711 and checks whether it is a positive value. The total amount is the sum of the amounts of all detail records Rb stored in the first transaction file 641. While the amounts of the product detail records Rb are positive, the amounts of the gift certificate detail records Rb are negative in the processing of ACT704. Therefore, the total amount is not necessarily positive and may be 0 yen or a negative amount.

If the total amount is positive, payment is required. In this case, processor 21 proceeds from ACT 711 to ACT 132. Then, processor 21 executes the processing of ACTs 132 to 137 in the same manner as in the first embodiment.

Conversely, 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 ACT 711 to ACT 712. Processor 31, as ACT 712, sets the touch panel 28 screen to the payment completion screen SAh (see Figure 49).

Figure 49 shows an example of the payment completion screen SAh. The payment completion screen SAh is the subtotal discount button BAg, the subtotal discount button BAh, and the return to details button BAj, removed from the subtotal discount screen SAd. The payment completion screen SAh displays text indicating that payment has been completed using a gift certificate. For example, the payment completion screen SAh in Figure 49 represents a case where customer 3, who purchased four items totaling 1000 yen, presents a gift certificate with a face value of 1000 yen, as shown in the details screen SAc in Figure 48. In this case, since the total amount is 0 yen, no payment is made. However, a receipt is issued by the payment device 12. Therefore, the processor 21, which displayed the payment completion screen SAh, proceeds to ACT 132. The processor 21 then executes the processing of ACTs 132 to 137 in the same manner as in the first embodiment.

Here, processor 21 realizes the function of a voucher identification means 520 through the processing of ACT 701. Processor 21 realizes the function of an arithmetic means 521 through the processing of ACT 711. Processor 21 realizes the function of a completion notification means 522 through the processing of ACT 712.

Next, the essential information processing steps executed by the processor 31 of the payment device 12 according to the payment program will be explained using flowcharts in Figures 46 and 47. The processing steps shown in the flowchart of Figure 46 correspond to the flowchart in Figure 11 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 11 and Figure 47. The processing steps shown in the flowchart of Figure 47 correspond to the flowchart in Figure 12 in the first embodiment. Therefore, the same reference numerals are used for processing steps common to both Figure 12 and Figure 47.

As explained using Figure 44, the payment device 12 receives an input event from the input device 11 that includes the product code or gift certificate code. When the processor 31 of the payment device 12 receives the input event including the product code or gift certificate code from the input device 11 in ACT 207 (Figure 46), it proceeds from ACT 207 to ACT 209. The processor 31 creates the detail record Rb as ACT 209.

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

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

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

If detail record Rb is a detail record for a product, processor 31 proceeds from ACT 801 to ACT 802. As ACT 802, processor 31 sets the gift certificate flag Fd of detail record Rb to "0".

In contrast, if the detail record Rb is a detail record for a gift certificate, the processor 31 proceeds from ACT 801 to ACT 803. As ACT 803, the processor 31 sets the gift certificate flag Fd of detail record Rb to "1". Also, as ACT 804, the processor 31 adds a minus sign to the amount of detail record Rb.

After completing the processing of ACT 802 or ACT 804, the processor 31 proceeds to ACT 210. The processor 31 stores the detail record Ra in the second transaction file 811 as ACT 210. Then, the processor 31 enters a waiting state for ACTs 212 and ACT 213.

When an input event is received in the waiting state of ACT212 and ACT213, processor 31 returns from ACT212 to ACT207. Processor 31 then executes the processing from ACT207 onward in the same manner as described above. Specifically, if an input event containing a product code is received, processor 31 creates a detail record Rb with the product certificate flag Fd set to "0" and stores this detail record Rb in the second transaction file 811. If an input event containing a product certificate code is received, processor 31 creates a detail record Rb with the product certificate flag Fd set to "1" and stores this detail record Rb in the second transaction file 811.

When a completion event is received in the waiting state of ACT212 and ACT213, processor 31 proceeds from ACT213 to ACT811 in Figure 45. Processor 21 calculates the total amount as ACT811 and checks whether it is a positive value. The total amount is the sum of the amounts of all detail records Rb stored in the second transaction file 811. While the amounts of product detail records Rb are positive, the amounts of gift certificate detail records Rb are negative. Therefore, the total amount is not necessarily positive and may be 0 yen or a negative amount.

If the total amount is positive, the processor 31 proceeds from ACT 811 to ACT 221. Then, the processor 31 executes the processing of ACTs 221 through ACT 235 in the same manner as in the first embodiment.

In contrast, if the total amount is zero or a negative amount, processor 31 proceeds from ACT 811 to ACT 231. That is, processor 31 skips the processing of ACTs 221 to 230. Therefore, customer 3 does not pay. Subsequently, processor 21 performs the processing of ACTs 231 to 235 in the same manner as in the first embodiment. Therefore, a receipt RS (see Figure 50) is issued, and customer 3 receives the receipt RS.

Figure 50 shows an example of a receipt RS issued to a customer who presented a gift certificate with a face value of 1,000 yen for a purchase totaling 1,000 yen. As shown in Figure 50, the receipt RS displays the details of the four purchased items, followed by the total amount of 1,000 yen, and then the face value of the gift certificate (1,000 yen) with a minus sign. This type of receipt RS allows customer 3 to confirm that they paid for their purchases with a gift certificate.

Here, processor 31 realizes the function of a gift certificate identification means 78 through the processing of ACT 801. Processor 31 also realizes the function of a receipt output means 79 through the processing of ACT 231.

Thus, even in the fourth embodiment, the accounting system 1 can be provided that allows the store clerk 2 and the customer 3 to share the operation and settle the transaction without the input device 11 generating settlement information including detailed information and total information of the purchased goods and transmitting it to the settlement device 12. Furthermore, according to the fourth embodiment, the accounting system 1 can also be provided that supports monetary vouchers and other gift certificates that require the intervention of a store clerk as a payment method.

[Other embodiments]
Figure 51 shows another embodiment of the connection destination selection screen SAi. The connection destination selection screen SAi includes a numeric keypad with numbers "0" through "9" (BAu) for manually entering the payment device number, a confirmation button (BAv), and a clear button (BAw) as software keys. The connection destination selection screen SAi also includes a field (AAi) for displaying the payment device number entered by the numeric keypad button (BAu).

After confirming the connection destination selection screen SAi, employee 2 enters the payment device number of an available payment device 12 using the numeric keypad button BAu and touches the confirmation button BAv. If the entry is incorrect, employee 2 touches the clear button BAw to clear the entry. When the confirmation button BAv is touched, the processor 21 inputs the value entered in ACT 102 in Figure 9 as the payment device number. Thereafter, the processor 21 executes the processing from ACT 103 onwards in the same manner as described above.
Thus, the input device 11 may use the connection destination selection screen SAi instead of the connection destination selection screen SAa.

In the above embodiment, an example was given where customer 3 operates the payment device 12 to input the payment method. In another embodiment, store clerk 2 may operate the input device 11 to input the payment method. Therefore, another embodiment in which the payment method is input using the input device 11 will now be described with reference to Figures 52 and 53.

Figure 52 is a flowchart showing the main steps of the information processing performed by the processor 21 of the input device 11 according to the input program. In the first embodiment, Figure 52 corresponds to the flowchart of Figure 10. Therefore, the same reference numerals are used for processing steps common to both Figure 10 and Figure 52.

As shown in Figure 52, when the input completion button BAi is pressed while ACT129 and ACT130 are in standby state, the processor 21 proceeds from ACT130 to ACT901. As ACT901, the processor 21 sets the touch panel 28 screen to the payment method selection screen. The payment method selection screen is the same as the payment method selection screen SBb displayed on the touch panel 38 of the payment device 12 in the first embodiment. At this time, the customer display 29 remains on the customer registration screen.

After checking the payment method selection screen, the store clerk confirms the customer's preferred payment method. If customer 3 wishes to pay with cash, clerk 2 presses the cash button (BBa). If customer 3 wishes to pay with a credit card, clerk 2 presses the credit button (BBb). If customer 3 wishes to pay with electronic money, clerk 2 presses the electronic money button (BBc).

The processor 21, displaying the payment method selection screen, waits for a payment method to be selected as ACT 902. Once a payment method is selected via input from the cash button BBa, credit button BBb, or electronic money button BBc, the processor 21 proceeds from ACT 902 to ACT 903. As ACT 903, the processor 21 obtains the payment type. The payment type is payment method identification data that identifies the payment method selected. For example, if the cash button BBa is entered, the processor 21 obtains the payment type "cash" as the payment method identification data. If the credit button BBb is entered, the processor 21 obtains the payment type "credit" as the payment method identification data. If the electronic money button BBc is entered, the processor 21 obtains the payment type "electronic money" as the payment method identification data.

The processor 21, having obtained the payment type, proceeds to ACT 132. As ACT 132, the processor 21 issues a transaction number. Having issued the transaction number, the processor 21 proceeds to ACT 133. As ACT 133, the processor 21 obtains the payment device ID of the connected payment device 12. That is, the processor 21 refers to the first data table 63 and obtains the payment device ID where the connection destination flag Fa is "1". Then, as ACT 904, the processor 21 controls the communication unit 25 to send a completion event to the payment device ID. This control sends the completion event to the network 14 via the communication unit 25. The completion event is received by the payment device 12 among the multiple payment devices 12 connected to the network 14 that has the payment device ID set as the destination for the completion event. The completion event includes the transaction number issued in ACT 132. The completion event also includes the payment type obtained in ACT 903.

The processor 21, having sent the completion event, proceeds to ACT 135. The processor 21 then executes the processes of ACT 135 through ACT 137 in the same manner as in the first embodiment.

Figure 53 is a flowchart showing the main steps of the information processing performed by the processor 31 of the payment device 12 according to the payment program. In the first embodiment, Figure 53 corresponds to the flowchart of Figure 12. Therefore, the same reference numerals are used for processing steps common to both Figure 12 and Figure 53.

In the first embodiment, when the processor 31 of the payment device 12 receives a completion event while in the waiting state for ACT 212 and ACT 213, it sets the screen of the touch panel 38 to the payment method selection screen SBb as ACT 221 in Figure 12. In the other embodiment, upon receiving a completion event, the process proceeds to ACT 911 in Figure 53. The processor 31 obtains the payment type from the completion event as ACT 911.

The processor 31, having obtained the payment type, proceeds to ACT 226. As ACT 226, the processor 31 displays the touch panel 38 screen as the accounting screen SBc corresponding to the payment type. Then, as ACT 227, the processor 31 waits for the payment to be completed. Once the payment is complete, the processor 31 proceeds from ACT 227 to ACT 231. The processor 31 executes the processing of ACTs 231 through ACT 235 in the same manner as in the first embodiment.

Thus, by modifying a portion of the information processing performed by the processor 21 of the input device 11 as shown in Figure 52, and modifying a portion of the information processing performed by the processor 31 of the payment device 12 as shown in Figure 53, it is possible to configure the system so that the store clerk 2 can operate the input device 11 to input the payment method.

In the above embodiment, the case where the payment device 12 is connected to a cashless payment terminal 5 was illustrated. The payment device 12 does not necessarily have to be connected to a cashless payment terminal 5. A payment device 12 that is not connected to a cashless payment terminal 5 becomes a payment device exclusively for cash payments. In that case, the processor 31 of the payment device 12 omits the processing of ACT221 to ACT226 in Figure 12. That is, when the processor 31 receives a completion event in the waiting state of ACT212 and ACT213 in Figure 11, it proceeds to the processing of ACT227 in Figure 12.

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 aforementioned embodiments can be applied to an accounting system with three or more payment devices 12 arranged for one checkout lane.

Furthermore, the payment devices 12 may include a mix of devices connected to a cashless payment terminal 5 and devices not connected to a cashless payment terminal 5. In this case, the store clerk 2, who is the operator of the input device 11, will confirm the payment method with the customer 3 in advance. If the customer 3 wishes to pay cashless, they should select the payment device 12 connected to the cashless payment terminal 5 on the connection selection screen SAa.

In the above embodiment, an example was given where the input device 11 issues a transaction number and transmits it to the settlement device 12 along with the completion event. In another embodiment, the settlement device 12 that receives the completion event may issue a transaction number. In this case, for multiple settlement devices 12 located in the same checkout lane, it is preferable 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.

Furthermore, in the fourth embodiment, the payment device 12 may be configured to dispense change from an automatic change dispenser if the total amount is negative. This allows for the use of gift certificates that can dispense change.

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 comprises: a determination means for determining one of the plurality of settlement devices as the connection destination before inputting the transaction data; a completion detection means for detecting an instruction to complete inputting the transaction data; a first transmission means for transmitting the transaction data input via the input device to one of the settlement devices determined as the connection destination by the determination means before the completion detection means detects an instruction to complete inputting the transaction data; and a first notification means for notifying one of the settlement devices determined as the connection destination by the determination means of the completion of input when the completion detection means detects an instruction to complete inputting the transaction data; wherein the settlement device comprises: a settlement-side storage means for storing the transaction data transmitted from the input device in a settlement-side storage unit until the transaction is settled; and a settlement means for settling a transaction based on the transaction data stored in the settlement-side storage unit when it receives notification of the completion of input from the input device.
[2] The accounting system as described in Appendix [1], wherein the input device further comprises a connection destination selection means for selecting one of the plurality of settlement devices before inputting data relating to the transaction, and an inquiry means for inquiring whether or not to connect to the settlement device selected by the connection destination selection means, the determination means determines the settlement device as the connection destination when the settlement device to be inquired about responds to the inquiry by the inquiry means and grants permission to connect, and the settlement device further comprises a connection response means that returns a response granting permission to connect when it receives an inquiry from the input device about whether or not to connect while in a state where it is able to settle the transaction.
[3] The accounting system as described in Appendix [2], wherein the connection destination selection means of the input device includes an operator capable of individually specifying the plurality of payment devices, and the input device further comprises a disabling means for disabling the operation of the operator that specifies the payment device when the payment device to be inquired about does not respond to an inquiry by the inquiry means with permission to connect.
[4] The accounting system according to Appendix [1], further comprising a detail display means on a display device which displays detail information of a transaction based on data relating to the transaction entered via the input device, together with information identifying the settlement device determined as the connection destination by the determination means.
[5] The accounting system as described in Appendix [1], further comprising: a payment device that displays a waiting screen on a display device until it receives notification of the completion of input from the input device, and when it receives notification of the completion of input, an amount display means that displays the settlement amount of the transaction calculated based on the transaction data stored by the payment-side storage means.
[6] The accounting system according to any one of the appendices [1] to [5], wherein the first transmission means of the input device transmits the input transaction data to one settlement device determined as a connection destination by the determination means each time transaction data is input via the input device.
[7] The accounting system as described in Appendix [1], wherein the input device further comprises: a first modification means for modifying transaction data transmitted to any one settlement device determined as a connection destination by the determination means before the termination detection means detects an instruction to end input of the transaction data; and a second transmission means for transmitting the modified transaction data modified by the first modification means to any one settlement device determined as a connection destination by the determination means before the termination detection means detects an instruction to end input of the transaction data; and the settlement device further comprises: a second modification means for modifying transaction data stored in the settlement-side storage unit with the modified transaction data transmitted from the input device by the second transmission means.
[8] The accounting system as described in Appendix [7], wherein the input device further comprises: an input-side storage means for storing transaction data entered via the input device in an input-side storage unit; a detail display means for displaying transaction details on a display device based on the transaction data stored in the input-side storage unit, together with information identifying the settlement device determined as the connection destination by the determination means; and a modification acceptance means for accepting modifications to the detail information displayed by the detail display means, wherein the first modification means modifies the transaction data stored in the input-side storage unit with the detail information modified by the modification acceptance means.
[9] The accounting system as described in Appendix [7] or [8], wherein the second transmission means of the input device transmits the modified transaction data to one of the settlement devices determined as a connection destination by the determination means each time the transaction data is modified.
[10] The input device includes an input-side storage means for storing transaction data entered via the input device in an input-side storage unit; a cancellation reception means for receiving a settlement cancellation instruction for a transaction whose input completion has been notified by the first notification means; a cancellation destination selection means for selecting a settlement device from among the plurality of settlement devices to cancel the settlement; a second notification means for notifying the settlement device selected by the cancellation destination selection means of the cancellation of the settlement when the cancellation reception means receives a settlement cancellation instruction for a transaction; and, on the condition that the settlement device to which the notification was received has given a response authorizing the cancellation of the settlement, the input-side storage unit stores the data. The accounting system as described in Appendix [1] further comprises: a third modification means for modifying data relating to a transaction; a third transmission means for transmitting the modified transaction data modified by the third modification means to a settlement device selected by the cancellation destination selection means, wherein the settlement device, upon receiving a cancellation notice of settlement from the input device before the transaction is settled by the settlement means, returns a response authorizing the cancellation of the settlement; and a fourth modification means for modifying the transaction data stored in the settlement-side storage unit with the modified transaction data transmitted from the input device by the third transmission means.
[11] The accounting system as described in Appendix [10], further comprising: an input device for notifying that a payment cannot be canceled if the payment device to which the notification is received does not respond to the payment cancellation notice with permission to cancel the payment.
[12] The accounting system described in Appendix [10] or [11], wherein the third transmission means of the input device transmits the modified transaction data to the settlement device selected by the cancellation destination selection means each time the transaction data is modified.
[13] The accounting system as described in Appendix [1], wherein the settlement device further comprises a voucher identification means for identifying whether the transaction data stored in the settlement-side storage unit is data relating to a transaction of a voucher product or data relating to a transaction of a product other than a voucher product, and when the settlement means receives notification of the completion of the input from the input device, it settles the transaction by setting the sales amount of the product as a positive value for data relating to a transaction of a product other than a voucher product among the transaction data stored in the settlement-side storage unit, and by setting the face value of the voucher as a negative value for data relating to a transaction of a voucher product.
[14] The accounting system described in Appendix [13] further comprises a receipt output means that outputs a receipt for a transaction settled by the payment means, which shows the face value of the gift certificate in addition to the total amount of sales of goods other than the gift certificate.
[15] The accounting system described in Appendix [13] or [14] further comprises: a gift certificate identification means for identifying whether the transaction data entered via the input device is data relating to a gift certificate product or data relating to a product other than a gift certificate product; a calculation means for calculating the total transaction amount by setting the sales price of the product as a positive value for data relating to a product other than a gift certificate product and the face value of the gift certificate product as a negative value for data relating to a gift certificate product; and a completion notification means for notifying the completion of payment when the total transaction amount calculated by the calculation means is 0 or a negative value at the time the completion detection means detects the end of input instruction for the transaction data.
[16] 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 determination means for determining one of the plurality of settlement devices as a connection destination before inputting the transaction data; 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 one of the settlement devices determined as a connection destination by the determination means before the end detection means detects an instruction to end inputting the transaction data; and a first notification means for notifying one of the settlement devices determined as a connection destination by the determination means of the end of input when the end detection means detects an instruction to end inputting transaction data.
[17] A settlement device comprising: a communication device that communicates data with an input device which transmits data relating to a transaction entered via an input device to one settlement device determined as a connection destination before an instruction to end the input of the data relating to the transaction is detected; a settlement-side storage means which stores the data relating to the transaction transmitted from the input device in a settlement-side storage unit until the transaction is settled; and a settlement means which, upon receiving notification from the input device that an instruction to end the input of the data relating to the transaction has been detected, settles the transaction based on the data relating to the transaction stored in the settlement-side storage unit.
[18] 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 determination means for determining one of the plurality of settlement devices as a connection destination before inputting the transaction data; 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 one of the settlement devices determined as a connection destination by the determination means before the end detection means detects an instruction to end inputting the transaction data; and a first notification means for notifying one of the settlement devices determined as a connection destination by the determination means that input has ended when the end detection means detects an instruction to end inputting transaction data.
[19] A program to cause a computer of a settlement device, which includes an input device and a communication device that communicates data with an input device and transmits data relating to a transaction entered via the input device to one settlement device determined as a destination before an instruction to end the input of the data relating to the transaction is detected, to function as a settlement-side storage means that stores data relating to a transaction transmitted from the input device in a settlement-side storage unit until the transaction is settled, and a settlement means that settles a transaction based on the data relating to the transaction stored in the settlement-side storage unit when it receives notification from the input device that an instruction to end the input of the data relating to the transaction has been detected.

1...Accounting system, 2...Clerk, 3...Customer, 5...Cashless payment terminal, 11...Input device, 12...Payment device, 13...Server, 14...Network, 21, 31...Processor, 51...Connection destination selection means, 52...Inquiry means, 53...Decision means, 54...Invalidation means, 55...Input side storage means, 56...Detail display means, 57...Termination detection means, 58...First transmission means, 59...First notification means, 63...First data table, 64...Input side storage unit, 65...Second data table, 71...Payment side storage means, 72...Amount display means, 73...Connection response means, 74...Payment means, 75...Second modification Means, 76...Cancellation response means, 77...Fourth modification means, 78...Voucher identification means, 79...Receipt output means, 81...Settlement side storage unit, 82...Flag memory, 510...Settlement destination notification means, 511...Modification acceptance means, 512...First modification means, 513...Second transmission means, 514...Cancellation acceptance means, 515...Cancellation destination selection means, 516...Second notification means, 517...Third modification means, 518...Third transmission means, 519...Notification of non-notification means, 520...Voucher identification means, 521...Calculation means, 522...Completion notification means, 641...First transaction file, 642...Third transaction file, 811...Second transaction file.

Claims (16)

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
Before inputting the data relating to the aforementioned transaction, a determination means is provided to determine which of the multiple payment devices will be used as the connection destination.
A termination detection means for detecting an instruction to complete the input of data related to the aforementioned transaction,
Before the termination detection means detects the end of input instruction for the transaction data, each time transaction data is input via the input device, the first transmission means transmits the input transaction data to one of the settlement devices determined as the connection destination by the determination means,
When the termination detection means detects an instruction to complete the input of transaction-related data, the first notification means notifies one of the settlement devices determined as the connection destination by the determination means that the input has been completed.
It is equipped with,
The aforementioned payment device is
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,
Upon receiving notification of the end of input from the input device, 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. The aforementioned input device is
Before inputting the data relating to the aforementioned transaction, a connection destination selection means selects one of the multiple payment devices,
An inquiry means for inquiring whether or not it is possible to connect to the payment device selected by the connection destination selection means,
Furthermore, it is equipped with,
The determination means determines the payment device to be the connection destination when it receives a response from the payment device to be inquired about in response to an inquiry made by the inquiry means,
The aforementioned payment device is
When the input device receives an inquiry regarding connection permission while the transaction is ready for settlement, the connection response means returns a response granting permission to connect.
The accounting system according to claim 1, further comprising: The connection destination selection means of the input device includes an operator that can individually specify the multiple payment devices.
The aforementioned input device is
If the payment device to which the inquiry was made does not respond to the inquiry made by the aforementioned inquiry means by which the payment device is not authorized to connect, the invalidation means disables the operation of the operator that designates the payment device.
The accounting system according to claim 2, further comprising: The aforementioned input device is
A detail display means that displays the transaction details information on the display device, based on the transaction data entered via the input device, together with information identifying the settlement device determined as the connection destination by the determination means.
The accounting system according to claim 1, further comprising: The aforementioned payment device is
The display device displays a waiting screen until it receives notification from the input device that the input has finished, and upon receiving the notification that the input has finished, it displays an amount display means that displays the settlement amount of the transaction calculated based on the transaction data stored by the settlement-side storage means.
The accounting system according to claim 1, further comprising: The aforementioned input device is
A first modification means modifies the transaction data transmitted to one of the payment devices determined as the connection destination by the determination means before the termination detection means detects the termination instruction for the input of the transaction data,
A second transmission means transmits the modified transaction data, modified by the first modification means, to one of the settlement devices determined as the connection destination by the determination means, before the termination detection means detects the termination of data input for the transaction.
Furthermore, it is equipped with,
The aforementioned payment device is
The accounting system according to claim 1, further comprising: a second modification means for modifying the transaction data stored in the settlement-side storage unit with the modified transaction data transmitted from the input device by the second transmission means. The aforementioned input device is
An input-side storage means that stores transaction data input via the aforementioned input device in an input-side storage unit,
A detail display means that displays the transaction details on a display device based on the transaction data stored in the input-side storage unit, along with information identifying the settlement device determined as the connection destination by the determination means.
A correction acceptance means for accepting corrections to the detail information displayed by the detail display means,
Furthermore, it is equipped with,
The first modification means modifies the transaction data stored in the input-side storage unit with the detail information that has been modified by the modification receiving means.
The accounting system according to claim 6 . The second transmission means of the input device is:
The accounting system according to claim 6 or 7 , wherein each time the transaction data is modified, the modified transaction data is transmitted to one of the settlement devices determined as the connection destination by the determination means. The aforementioned input device is
An input-side storage means that stores transaction data input via the aforementioned input device in an input-side storage unit,
A cancellation acceptance means that accepts a payment cancellation instruction for a transaction for which input completion has been notified by the first notification means,
A cancellation target selection means for selecting a payment device from among the multiple payment devices to cancel the payment,
When the cancellation acceptance means receives an instruction to cancel the settlement of a transaction, the second notification means notifies the settlement device selected by the cancellation destination selection means of the cancellation of the settlement,
A third modification means for modifying transaction data stored in the input-side storage unit, conditional on the payment device receiving the notification of the cancellation of the payment granting permission to cancel the payment,
A third transmission means transmits the data relating to the modified transaction, modified by the third modification means, to the settlement device selected by the cancellation destination selection means,
Furthermore, it is equipped with,
The aforementioned payment device is
If a cancellation notice for the settlement is received from the input device before the transaction is settled by the settlement means, the cancellation response means returns a response authorizing the cancellation of the settlement.
The accounting system according to claim 1, further comprising: a fourth modification means for modifying the transaction data stored in the settlement-side storage unit with the modified transaction data transmitted from the input device by the third transmission means. The aforementioned input device is
If the payment device to which the payment was notified does not respond to the payment cancellation notice with permission to cancel the payment, a non-notification means will be used to notify that the payment cannot be canceled.
The accounting system according to claim 9 , further comprising: The third transmission means of the input device is:
The accounting system according to claim 9 or 10 , wherein each time the transaction data is modified, the modified transaction data is transmitted to the settlement device selected by the cancellation destination selection means. The aforementioned payment device is
A gift certificate identification means for identifying whether the transaction data stored in the settlement-side storage unit is data relating to a gift certificate product or data relating to a product other than a gift certificate product.
Furthermore, it is equipped with,
The accounting system according to claim 1, wherein when the settlement means receives notification of the completion of input from the input device, it settles the transaction by setting the sales price of the product as a positive value for data relating to transactions of products other than gift certificates among the transaction data stored in the settlement-side storage unit, and setting the face value of the gift certificate as a negative value for data relating to transactions of gift certificates. The aforementioned payment device is
A receipt output means that outputs a receipt for a transaction settled by the aforementioned payment means, which separately shows the face value of the gift certificate in addition to the total amount of sales of goods other than the gift certificate.
The accounting system according to claim 12 , further comprising: The aforementioned input device is
A gift certificate identification means that identifies whether the transaction data entered via the input device is data relating to a gift certificate product or data relating to a product other than a gift certificate product,
A calculation means for calculating the total transaction amount, wherein for data relating to transactions of goods other than gift certificates, the sales amount of the said goods is set as a positive value, and for data relating to gift certificates, the face value of the said gift certificates is set as a negative value,
When the completion detection means detects the end of input instructions for transaction-related data, and the total transaction amount calculated by the calculation means is zero or a negative value, a completion notification means notifies that payment has been completed.
The accounting system according to claim 12 or 13 , further comprising: 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 an instruction to complete the input of transaction-related data,
Before inputting the data relating to the aforementioned transaction, a determination means is provided to determine which of the multiple payment devices will be used as the connection destination.
A termination detection means for detecting an instruction to complete the input of data related to the aforementioned transaction,
Before the termination detection means detects the end of input instruction for the transaction data, each time transaction data is input via the input device, the first transmission means transmits the input transaction data to one of the settlement devices determined as the connection destination by the determination means,
When the termination detection means detects an instruction to complete the input of transaction-related data, the first notification means notifies one of the settlement devices determined as the connection destination by the determination means that the input has been completed.
An input device equipped with the following. 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 an instruction to complete the input of transaction-related data,
Before inputting the data relating to the aforementioned transaction, a determination means determines which of the multiple payment devices will be used as the connection destination.
Termination detection means for detecting an instruction to complete input of data related to the transaction,
Before the termination detection means detects the end of input instruction for the transaction data, each time transaction data is input via the input device, a first transmission means transmits the input transaction data to one of the settlement devices determined as the connection destination by the determination means, and
When the termination detection means detects an instruction to complete the input of transaction-related data, the first notification means notifies one of the settlement devices determined as the connection destination by the determination means that the input has been completed.
A program designed to function as such.