Accounting machine, program thereof, and method of processing accounting machine

Abstract

To enable an accounting machine to be used not only as a semi-self-service type accounting machine but also as a terminal input type or full-self-service type accounting machine.SOLUTION: The accounting machine includes first processing means, second processing means, and switching means. The first processing means processes charge payment of a first purchased commodity based on data pertaining to the first purchased commodity inputted with a registration machine. The second processing means processes charge payment of a second purchased commodity based on data pertaining to the second purchased commodity inputted with a terminal or a device other than the registration machine. The switching means switches between validating the processing of the charge payment with the first processing means or validating the processing of the charge payment with the second processing means, in response to an operation input of an operator.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] FIELD OF THE INVENTION The present invention relates to an accounting machine, a program therefor, and a processing method for the accounting machine. [Background technology]

[0002] In recent years, semi-self-service transaction processing systems have become popular as transaction processing systems for mass retailers. Semi-self-service transaction processing systems separate a registration machine, which inputs data related to purchased items for each transaction, from a cashier, which processes payment for the purchased items. The system is arranged so that a store clerk operates the registration machine and the customer operates the cashier.

[0003] In a semi-self-service transaction processing system, the store clerk inputs data related to purchased items, so the time required for data input is shorter than in a full-self-service transaction processing system in which the customer inputs the data themselves.

[0004] On the other hand, there are already known terminal input type transaction processing systems in which customers operate a communication terminal such as a smartphone or tablet device themselves in the sales floor where the products are displayed to input data related to the purchased products, and then pay for the purchased products themselves by operating a dedicated cash register. In terminal input type transaction processing systems, because customers input data related to the purchased products in the sales floor, the registration machines that were previously operated by store clerks are no longer necessary.

[0005] Incidentally, the hardware configuration of accounting machines in semi-self-service transaction processing systems and those in terminal-input transaction processing systems is usually the same. These accounting machines can also be used as full-self-service systems. For example, during busy times when there are many customers, they can be used as semi-self-service machines to speed up customer checkouts, but during quiet times when there are fewer customers, they can be used as terminal-input or full-self-service machines to reduce the number of employees. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Publication No. 2017-016413 Summary of the Invention [Problem to be solved by the invention]

[0007] The problem that the embodiments of the present invention aim to solve is to provide an accounting machine and its program, as well as an accounting machine processing method, that can be used not only as a semi-self-service accounting machine, but also as a terminal input type or full-self-service accounting machine. [Means for solving the problem]

[0008] In one embodiment, a system is configured with a registration machine for inputting data related to purchased items, and a payment machine for processing payment for the purchased items includes a first processing means, a second processing means, and a switching means. The first processing means processes payment for a first purchased item based on data related to the first purchased item input by the registration machine. The second processing means processes payment for a second purchased item based on data related to the second purchased item input by a terminal or device other than the registration machine. The switching means switches between enabling payment processing by the first processing means and enabling payment processing by the second processing means in response to an operation input from an operator. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a schematic diagram showing a general configuration of a transaction processing system. [Figure 2] FIG. 2 is a block diagram showing the main circuit configuration of the payment machine. [Figure 3] FIG. 3 is a schematic diagram showing the main program structure of the accounting machine. [Figure 4] FIG. 4 is a sequence diagram showing an example of communication related to a semi-self-service transaction processing system. [Figure 5]FIG. 5 is a sequence diagram showing an example of communication related to a transaction processing system using the individual input method. [Figure 6] FIG. 6 is a flowchart showing the information processing procedure executed by the processor of the accounting machine in accordance with the mode setting program. [Figure 7] FIG. 7 is a flowchart showing the information processing steps executed by the processor of the checkout machine in accordance with the first payment engine program. [Figure 8] FIG. 8 is a flowchart showing the information processing steps executed by the processor of the checkout machine in accordance with the second payment engine program. [Figure 9] FIG. 9 is a flowchart showing the information processing steps executed by the processor of the checkout machine in accordance with the third payment engine program. [Figure 10] FIG. 10 is a sequence diagram showing an example of communication related to the semi-self-service transaction processing system in the second embodiment. [Figure 11] FIG. 11 is a block diagram showing the main circuit configuration of a payment machine in the second embodiment. [Figure 12] FIG. 12 is a flowchart showing the procedure of information processing executed by the processor of the checkout machine in accordance with the first payment engine program in the second embodiment. [Figure 13] FIG. 13 is a flowchart showing the procedure of information processing executed by the processor of the checkout machine in accordance with the second payment engine program in the second embodiment. [Figure 14] FIG. 14 is a flowchart showing the procedure of information processing executed by the processor of the checkout machine in accordance with the third payment engine program in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the accounting machine will be described with reference to the drawings. This embodiment illustrates a case in which a semi-self-service transaction processing system, a terminal-input transaction processing system, and a full-self-service transaction processing system are used in combination in one store. The semi-self-service transaction processing system is a transaction processing system in which a store clerk inputs data related to purchased items into a registration machine and the customer pays for the purchased items at a cash register. The terminal-input transaction processing system is a transaction processing system in which a customer inputs data related to purchased items using a portable communication terminal such as a smartphone or tablet device in a sales floor where items are displayed, and then pays for the purchased items at a cash register. The full-self-service transaction processing system is a system in which a customer inputs data related to purchased items and pays for the purchased items at a single cash register. The hardware configuration of the cash register used in both transaction processing systems is the same.

[0011] Furthermore, terminal-input transaction processing systems can also be considered full-self-service transaction processing systems, since the customer performs all processes themselves, from inputting data about the purchased items to paying for them. Therefore, in the following, we will distinguish between transaction processing systems that use communication terminals and those that use a single accounting machine, by calling them individual-input transaction processing systems and continuous-input transaction processing systems.

[0012] [First embodiment] <Description of transaction processing system configuration> 1 is a schematic diagram showing the overall configuration of a transaction processing system 1 according to a first embodiment. Transaction processing system 1 includes a registration machine 11, a checkout machine 12, a store server 13, a virtual POS server 14, an access point 15, and a network 16 connecting these. There are no particular limitations on the type of network 16, but a wired or wireless LAN (local area network) is generally used.

[0013] In transaction processing system 1, registration machine 11 and accounting machine 12 are elements that make up a semi-self-service transaction processing system. The accounting machine 12 and virtual POS server 14, together with communication terminal 2 connected wirelessly via access point 15, are elements that make up an individual input transaction processing system. The accounting machine 12 can also be said to be an element that makes up a continuous input transaction processing system. The store server 13 is involved in each of the semi-self-service, continuous input, and individual input transaction processing systems.

[0014] The registration machine 11 is operated by a store clerk 21 who plays the role of a checker. In principle, the checkout machine 12 is operated by a consumer who purchases products at the store, a customer 22. In FIG. 1, the registration machine 11 is attached to a work table 23. The work table 23 has a rectangular top. By arranging multiple work tables 23 so that the longitudinal directions of the tops are approximately parallel, a passageway for customers 22, a so-called checkout lane, is formed.

[0015] A registration machine 11 and a payment machine 12 are arranged for each checkout lane in the store. One registration machine 11 and two payment machines 12 are arranged for each checkout lane. Hereinafter, one payment machine 12 will be referred to as the first payment machine 12-1, and the other payment machine 12 will be referred to as the second payment machine 12-2. Various data signals are exchanged over a network 16 between the registration machine 11 and the payment machine 12 (12-1, 12-2) arranged in the same checkout lane. Data signals may be exchanged via the store server 13, or may be exchanged without going through the store server 13.

[0016] Note that Figure 1 shows an example in which one registration machine 11 and two payment machines 12 (12-1, 12-2) are arranged for each of two checkout lanes. The number of payment machines 12 arranged in one checkout lane is not limited to two. Three or more payment machines 12 may be arranged. Furthermore, data may be exchanged via network 16 between registration machines 11 and payment machines 12 arranged in different checkout lanes.

[0017] The store server 13 includes a product master file. The product master file may be stored in a storage device built into the store server 13, or may be stored in a storage device externally connected to the store server 13.

[0018] The product master file is a data file that stores product records created for each product sold in a store. The product records are data records that describe product data such as product code, product name, unit price, and attributes.

[0019] A product code is a unique code assigned to each product to identify it. Usually, each product is provided with a barcode or two-dimensional code representing the product code. The registration device 11 can input the product code of the purchased product in a transaction by reading the barcode or two-dimensional code attached to the product with a reader.

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

[0021] The virtual POS server 14 is a computer that cooperates with the communication terminal 2 to assist in making it appear as if a known POS terminal is operating. For example, the virtual POS server 14 has the following three functions. The first function is to register product sales data for products identified by product codes entered via the communication terminal 2 in a transaction file. The second function is to display a registration screen created based on the product sales data registered in the transaction file on the display device of the communication terminal 2. The third function is to create an accounting barcode in response to an accounting instruction from the communication terminal 2, associate it with the transaction file, and display the accounting barcode on the display device of the communication terminal 2.

[0022] The access point 15 is a communication facility installed in the store as a relay point when the communication terminal 2 performs data communication with the virtual POS server 14 via a wireless LAN. The wireless LAN conforms to the Wi-Fi (registered trademark) standard, for example. Although only one access point 15 is shown in FIG. 1, the number of access points 15 is not limited. Depending on the size of the store, multiple access points 15 may be connected to the network 16.

[0023] The communication terminal 2 is a terminal used by customers in the sales area where the products are displayed to input data related to the products they have purchased. The communication terminal 2 is a portable terminal equipped with an input device, a display device, a wireless unit, and an imaging device required to read code symbols such as two-dimensional codes or barcodes. For example, a commercially available smartphone or tablet equipped with a digital camera can be used as the communication terminal 2.

[0024] The configuration of transaction processing system 1 is not limited to that shown in Fig. 1. For example, an attendant terminal may be connected to network 16. The attendant terminal is a device that allows a store clerk, known as an attendant, to monitor the status of checkout machine 12, which processes payments by a customer through self-operation. Furthermore, instead of separating store server 13 and virtual POS server 14, a single server having the functions of store server 13 and virtual POS server 14 may be connected to network 16.

[0025] <Explanation of the accounting machine configuration> Figure 2 is a block diagram showing the main circuit configuration of the payment machine 12. The first payment machine 12-1 and the second payment machine 12-2 have the same configuration, so in Figure 2 they will be collectively referred to as the payment machine 12 and their configuration will be explained.

[0026] The accounting machine 12 includes a processor 31, a main memory 32, an auxiliary storage device 33, a clock 34, a communication interface 35, a change dispenser interface 36, a scanner 37, a touch panel 38, a printer 39, a reader / writer 40, and a system transmission path 41. The system transmission path 41 includes an address bus, a data bus, a control signal line, etc. The system transmission path 41 connects the processor 31 to each of the other components directly or via a signal input / output circuit, and transmits data signals exchanged between them.

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

[0028] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the accounting machine 12 in accordance with an operating system or application programs. The processor 31 is, for example, a CPU (Central Processing Unit).

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

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

[0031] The clock 34 keeps track of the date and time. The processor 31 processes the date and time kept by the clock 34 as the current date and time.

[0032] The communication interface 35 performs data communication with the registration machine 11, other accounting machines 12, the store server 13, the virtual POS server 14, and the like, which are connected via the network 16.

[0033] The change machine interface 36 constitutes an interface with an automatic change machine (not shown). The change machine interface 36 inputs amount data of coins inserted into the automatic change machine from the automatic change machine. The change machine interface 36 outputs change data from the accounting machine 12 to the automatic change machine. Having input the change data, the automatic change machine automatically dispenses coins equivalent to the change data as change.

[0034] The scanner 37 is an example of a reading device that reads code symbols such as barcodes, two-dimensional codes, etc. The scanner 37 may be a type that reads code symbols by scanning with laser light, or a type that reads code symbols from images captured by an imaging device.

[0035] The touch panel 38 is a device that combines an input device and a display device. The touch panel 38 displays information to the operator of the payment machine 12 and accepts operational inputs from the operator.

[0036] The printer 39 issues receipts by printing various characters or images on receipt paper. This type of printer 39 may be, for example, a thermal printer or a dot-matrix printer.

[0037] The reader / writer 40 has the function of reading data recorded on a medium such as a card or smartphone, and the function of writing data to the medium. Cards may include payment cards such as credit cards, debit cards, electronic money cards, and prepaid cards, as well as point cards such as company point cards and shared point cards. The reader / writer 40 may be a magnetic, contact, or contactless device, or may include multiple types of devices.

[0038] In the payment machine 12 configured as described above, the processor 31 has the functions of a first processing means 311, a second processing means 312, a switching means 313, and a response means 314. The functions of the first processing means 311, the second processing means 312, the switching means 313, and the response means 314 are all realized by information processing that the processor 31 executes in accordance with a program.

[0039] The first processing means 311 has a function of processing payment for the first purchased product based on data relating to the first purchased product inputted by the registration machine 11. In other words, the first processing means 311 has a function corresponding to a semi-self-service transaction processing system.

[0040] The second processing means 312 is a function that processes payment for the second purchased product based on data relating to the second purchased product input by a terminal or device other than the registration machine 11. The terminal other than the registration machine 11 refers to the communication terminal 2. The device refers to the scanner 37 or touch panel 38. In other words, the second processing means 312 is a function that corresponds to a transaction processing system that uses an individual input method or a continuous input method. Note that the data relating to the first purchased product and the data relating to the second purchased product are essentially data with the same structure, with only the input source being different.

[0041] The switching means 313 has a function of switching, in response to an operation input of an operator, whether to enable the payment processing by the first processing means 311 or the payment processing by the second processing means 312. The operators will be described later.

[0042] The response means 314 has a function of responding that it will not accept data transmission from the registration machine 11 relating to the first purchased product when the payment processing by the second processing means 312 is valid. The payment processing by the second processing means 312 being valid means that the payment machine 12 is functioning as a payment machine in a transaction processing system using either the individual input method or the continuous input method.

[0043] In order to realize the above-mentioned functions, the accounting machine 12 uses part of the volatile memory area in the main memory 32 as an area for a mode memory 321 and a status memory 322.

[0044] The mode memory 321 is an area for storing mode data M. The mode data M includes data for a first mode Ma, data for a second mode Mb, and data for a third mode Mc. The first mode Ma is a mode corresponding to a semi-self-service transaction processing system. The second mode Mb is a mode corresponding to an individual input transaction processing system. The third mode Mc is a mode corresponding to a continuous input transaction processing system.

[0045] The status memory 322 is an area for storing status data S. The status data S includes first status Sa data and second status Sb data. The first status Sa indicates a state in which the checkout machine of a semi-self-service transaction processing system can execute payment processing. The second status Sb indicates a state in which the checkout machine of a semi-self-service transaction processing system cannot execute payment processing. Payment processing is processing related to paying for purchased goods. There are two states in which processing is not executable. One is a state in which payment processing is being executed and another payment processing cannot be executed. The other is a state in which the checkout machine is functioning as a checkout machine of a transaction processing system using an individual input method or a continuous input method.

[0046] Furthermore, in order to realize the above-mentioned functions, the payment device 12 has the program structure shown in the schematic diagram of Figure 3. Specifically, the payment device 12 is equipped with a first payment engine program 51, a second payment engine program 52, a third payment engine program 53, and a mode setting program 54. Each of the programs 51-54 is a type of application program stored in the main memory 32 or the auxiliary storage device 33. There are no particular limitations on the method for installing each of the programs 51-54 into the main memory 32 or the auxiliary storage device 33. Each of the programs 51-54 can be installed in the main memory 32 or the auxiliary storage device 33 by recording it on a removable recording medium, or by distributing each of the programs 51-54 via communication via the network 16. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store the programs and is readable by the device.

[0047] The first payment engine program 51 is an application program for assisting the payment machine 12 to function as a payment machine in a semi-self-service transaction processing system. The second payment engine program 52 is an application program for assisting the payment machine 12 to function as a payment machine in a transaction processing system using an individual input method. The third payment engine program 53 is an application program for assisting the payment machine 12 to function as a payment machine in a transaction processing system using a continuous input method.

[0048] The mode setting program 54 is an application program that controls the computer so as to set mode data M in the mode memory 321 in response to input from the first mode setting key 61, the second mode setting key 62, or the third mode setting key 63.

[0049] Specifically, when first mode setting key 61 is pressed under predetermined conditions, mode setting program 54 controls the computer to set first mode Ma data in mode memory 321. First mode Ma is a mode compatible with a semi-self-service transaction processing system. The function compatible with a semi-self-service transaction processing system is a function provided by first processing means 311. In other words, first mode setting key 61 is an example of an operator for enabling payment processing by first processing means 311.

[0050] When the second mode setting key 62 is pressed under predetermined conditions, the mode setting program 54 controls the computer to set second mode Mb data in the mode memory 321. The second mode Mb is a mode compatible with a transaction processing system using an individual input method. The function compatible with the transaction processing system using an individual input method is a function provided by the second processing means 312. In other words, the second mode setting key 62 is an example of an operator for enabling the payment processing by the second processing means 312.

[0051] When the third mode setting key 63 is pressed under predetermined conditions, the mode setting program 54 controls the computer to set the data of the third mode Mc in the mode memory 321. The third mode Mc is a mode compatible with a transaction processing system using a continuous input method. The function compatible with the transaction processing system using a continuous input method is also a function provided by the second processing means 312. In other words, the third mode setting key 63 is also an example of an operator for enabling the payment processing by the second processing means 312.

[0052] The first mode setting key 61, the second mode setting key 62, and the third mode setting key 63 are, for example, soft keys displayed on a part of the screen of the touch panel 38. If the accounting machine 12 further includes a keyboard as an input device, the first mode setting key 61, the second mode setting key 62, and the third mode setting key 63 may be hard keys arranged on the keyboard.

[0053] Thus, the checkout machine 12 can operate not only as a checkout machine for a semi-self-service transaction processing system, but also as a checkout machine for a transaction processing system using an individual input method or a continuous input method. Before explaining the operation of the checkout machine 12, a brief explanation of the semi-self-service, individual input, and continuous input method transaction processing systems will be provided.

[0054] <Outline of the semi-self-service method> FIG. 4 is a sequence diagram showing an example of communication between registration machine 11, first transaction machine 12-1, and second transaction machine 12-2 that make up a semi-self-service transaction processing system.

[0055] In the semi-self-service system, registration machine 11 inputs data related to the products purchased by the customer. Then, when data related to all purchased products has been input, registration machine 11 sends a request command for status data S, for example, to first payment machine 12-1. Upon receiving this request command, first payment machine 12-1 sends a response command including the status data S stored in status memory 322 to registration machine 11.

[0056] Upon receiving the response command, the registration machine 11 checks the status data S contained in the command. If the status data S is status Sa, meaning that the first payment machine 12-1 is ready to execute payment processing, the registration machine 11 sends payment data to the first payment machine 12-1. The payment data is data necessary for the payment machine 12 to process payment for the purchased items. The payment data includes at least the product code and purchase quantity of the purchased items. If a discount or deduction has been entered for the transaction subtotal, the payment data also includes the discount amount or discount rate. The payment data is an example of data related to the first purchased item.

[0057] On the other hand, if the status data S is status Sb, that is, if the first payment machine 12-1 is in a state where it is unable to perform payment processing, the registration machine 11 sends a request command for the status data S to the second payment machine 12-2. Upon receiving this request command, the second payment machine 12-2 sends a response command to the registration machine 11 that includes the status data S stored in the status memory 322.

[0058] Upon receiving the response command, the registration machine 11 checks the status data S included in the command. If the status data S is status Sa, meaning that the second payment machine 12-2 is in a state where it can execute payment processing, the registration machine 11 sends payment data to the second payment machine 12-2.

[0059] On the other hand, if the status data S is status Sb, that is, if the second payment machine 12-2 is also in a state where it is unable to perform the payment process, the registration machine 11 again sends a request command for status data S to the first payment machine 12-1. Thus, when either the first payment machine 12-1 or the second payment machine 12-2 becomes able to perform the payment process, the registration machine 11 sends payment data to the payment machine 12 (first payment machine 12-1 or second payment machine 12-2) that is able to perform that payment process. The payment machine 12 (first payment machine 12-1 or second payment machine 12-2) that receives the payment data performs the payment process based on the customer's operational input.

[0060] Incidentally, if the status data S included in the response command is status Sa, the registration machine 11 displays information identifying the payment machine 12 that sent the response command on the display device. The store clerk operating the registration machine 11 simply instructs the customer to pay for the purchased items at the payment machine 12 identified by the displayed information.

[0061] The payment machine 12 to which the registration machine 11 first sends a request command for status data S is not limited to the first payment machine 12-1. The request command for status data S may be sent to the second payment machine 12-2 first. Alternatively, the registration machine 11 may send the request command for status data S to one of the payment machines 12 selected by a clerk's input. Typically, the clerk operating the registration machine 11 can visually confirm whether the customer is paying at the first payment machine 12-1 or the second payment machine 12-2. Therefore, the clerk selects an available payment machine 12. By doing so, the status data S included in the response command from that payment machine 12 is highly likely to be status "Sa," allowing the customer to quickly select the payment machine 12.

[0062] <Outline of individual input method> 5 is a sequence diagram showing an example of communication between the communication terminal 2, virtual POS server 14, and payment machine 12 that make up the individual input method transaction processing system. Payment machine 12 may be either first payment machine 12-1 or second payment machine 12-2.

[0063] First, a customer who wants to use a smartphone as the communication terminal 2 installs a shopping support application program for a store in which the transaction processing system 1 is installed, a so-called shopping app, on the smartphone. The customer then performs user registration. By doing so, the customer can use the smartphone as the communication terminal 2.

[0064] A customer carrying communication terminal 2 launches a shopping app before entering a store. This activates the camera of communication terminal 2, making it possible to read a store entry code. The store entry code is store-related setting information coded using a predetermined two-dimensional code system, and is prepared, for example, at the entrance of the store. The setting information includes, for example, parameters necessary for communication terminal 2 to communicate with access point 15 using wireless LAN, or information related to operational restrictions of communication terminal 2. The customer causes the camera of communication terminal 2 to read the store entry code.

[0065] When the store entry code is read by the communication terminal 2, the communication terminal 2 connects to the access point 15 using wireless LAN. Then, when the communication terminal 2 is connected to the access point 15, the communication terminal 2 transmits a check-in request command to the virtual POS server 14. The check-in request command includes terminal identification information of the communication terminal 2. The terminal identification information is unique information that differs from communication terminals 2 used by other customers. For example, the program ID of a shopping app installed on the communication terminal 2 is used as the terminal identification information.

[0066] Upon receiving the check-in request command, the virtual POS server 14 creates a transaction file. The transaction file is a data file for storing product sales data of a product identified by a product code input via the communication terminal 2. A transaction file is created for each communication terminal 2. The terminal identification information of the communication terminal 2 is associated with each transaction file.

[0067] The virtual POS server 14 that created the transaction file sends a check-in completion command to the communication terminal 2 that sent the check-in request command. Upon receiving the check-in completion command, the communication terminal 2 sets the screen of its display device to a registration screen. The registration screen is a screen for displaying the product name, price, etc. of the product identified by the product code entered via the communication terminal 2. A product registration button is displayed on the registration screen.

[0068] A customer places the communication terminal 2 in a shopping cart or carries it with them as they walk around the sales floor where products are displayed. When they find a product they want to purchase, they press the product registration button. When the product registration button is pressed, the communication terminal 2 enters data related to the purchased product. For example, the communication terminal 2 enters a standby state for reading a barcode. The customer has the camera read the barcode attached to the purchased product. When the camera reads the product's barcode, the communication terminal 2 enters the product code represented by the barcode as data for the purchased product.

[0069] The registration screen also displays a "No barcode" button. If the purchased item does not have a barcode attached, the customer presses the "No barcode" button. When the "No barcode" button is pressed, a list of items without barcodes is displayed on the display device. The customer selects the purchased item from the list. When the purchased item is selected, the communication terminal 2 inputs the product code of the selected item as data related to the purchased item.

[0070] When the data related to the purchased product is input, the communication terminal 2 transmits a product registration command to the virtual POS server 14. The product registration command includes the terminal identification information of the communication terminal 2 and the data of the purchased product.

[0071] Upon receiving the product registration command, the virtual POS server 14 adds product sales data to the transaction file associated with the terminal identification information of the communication terminal 2 that sent the product registration command. The product sales data includes the product code, product name, price, number of units sold, sales amount, etc. of the purchased product. The sales amount is the price multiplied by the number of units sold.

[0072] The virtual POS server 14, which has added the product sales data to the transaction file, sends a registration completion command to the communication terminal 2 that sent the product registration command. Upon receiving the registration completion command, the communication terminal 2 updates the registration screen. That is, the communication terminal 2 updates the registration screen so that the product name, price, etc. of the product sales data added to the transaction file are displayed. The updated registration screen displays a checkout button along with the product registration button, etc. The communication terminal 2, which has updated the registration screen, waits for the data of the purchased product to be entered or for the checkout button to be pressed.

[0073] When the customer finds the next item to purchase, he or she presses the product registration button. When the product registration button is pressed, the communication terminal 2 inputs data related to the purchased item. The communication terminal 2 then transmits a product registration command to the virtual POS server 14. The subsequent functions of the communication terminal 2 and the virtual POS server 14 are the same as those described above.

[0074] When a customer has finished shopping in the sales area, they press the checkout button. When the checkout button is pressed, the communication terminal 2 sends a checkout request command to the virtual POS server 14. The checkout request command includes the terminal identification information of the communication terminal 2.

[0075] Upon receiving the transaction request command, the virtual POS server 14 creates a unique transaction barcode. For example, the virtual POS server 14 creates a transaction barcode by barcoding the terminal identification information of the communication terminal 2 that sent the transaction request command using a specified barcode system. After creating the transaction barcode, the virtual POS server 14 sends a transaction authorization command to the communication terminal 2 that sent the transaction request command. The transaction authorization command includes the transaction barcode data. Upon receiving the transaction authorization command, the communication terminal 2 displays an image of the transaction barcode on a display device.

[0076] After completing their shopping at the sales floor and pressing the checkout button, the customer confirms that a checkout barcode is displayed on the display device of the communication terminal 2. Then, the customer holds the checkout barcode over the scanner 37 of the checkout machine 12, which displays the checkout waiting screen. When the checkout barcode is held over the scanner 37, it is read by the scanner 37. Once the checkout barcode is read by the scanner 37, a checkout notification command is sent from the checkout machine 12 to the virtual POS server 14. The checkout notification command includes terminal identification information obtained by decoding the checkout barcode. Upon receiving the checkout notification command, the virtual POS server 14 sends a transaction file associated with the terminal identification information to the checkout machine 12. The data in the transaction file is an example of data related to the second purchased item. The checkout machine 12 then executes the settlement process based on the data in the transaction file.

[0077] <Outline of the continuous input method> The continuous input method is realized by a single payment device 12. Payment device 12 may be a first payment device 12-1 or a second payment device 12-2.

[0078] After finishing their shopping at the sales floor, a customer goes to the location where the payment machine 12 is installed. The customer then operates the scanner 37 or touch panel 38, which are input devices of the payment machine 12, to input data related to each purchased item. For example, if the purchased item has a barcode, the customer scans the barcode with the scanner 37. If the purchased item does not have a barcode, the customer selects the purchased item from a list of items without barcodes displayed on the touch panel 38. After inputting the data related to all purchased items, the customer declares their intention to pay. This declaration of payment allows the customer to pay, and the customer then operates a change dispenser or reader / writer 40 to pay. The data related to the purchased items for which data has been entered is an example of data related to a second purchased item. The payment machine 12 executes a settlement process in response to the customer's payment operation.

[0079] <Explanation of the operation of the accounting machine> Next, the main operations of the payment device 12 will be explained using the flowcharts in Figures 6 to 9. Note that the operations explained below are just examples. The procedures or processing that lead to these operations can be modified as appropriate as long as similar effects can be achieved.

[0080] <<Explanation of the operation of the accounting machine using the mode setting program>> Figure 6 is a flowchart showing the information processing steps executed by the processor 31 of the payment device 12 in accordance with the mode setting program 54. First, in ACT1, the processor 31 sets the mode data M in the mode memory 321 to the first mode Ma, which corresponds to a semi-self-service transaction processing system. The processor 31 also sets the status data S in the status memory 322 to status Sa. In other words, the processor 31 puts the payment device 12 into a state where it can execute payment processing as a payment device in a semi-self-service transaction processing system. The processor 31 then starts the first payment engine program 51 in ACT2. The operation of the payment device 12 when the first payment engine program 51 is started will be explained later using Figure 7.

[0081] After starting the first settlement engine program 51, the processor 31 waits for an instruction to switch the operating mode as ACT3. At this point, the first mode Ma, which corresponds to a semi-self-service transaction processing system, is set. Therefore, the processor 31 waits for an instruction to switch to the second mode Mb or the third mode Mc, which correspond to a transaction processing system using the individual input method or the continuous input method. The switch to the individual input method is instructed by operating the second mode setting key 62. The switch to the continuous input method is instructed by operating the third mode setting key 63.

[0082] When an instruction to switch the operating mode is issued, processor 31 checks in ACT4 whether first payment engine program 51 is idle. If first payment engine program 51 is not idle, i.e., if payment processing is being executed, the operating mode cannot be switched. Processor 31 determines NO in ACT4 and returns to ACT3.

[0083] If the first payment engine program 51 is idle, i.e., if payment processing is not being executed, the processor 31 determines YES in ACT 4 and proceeds to ACT 5. In ACT 5, the processor 31 stops the first payment engine program 51. Then, in ACT 6, the processor 31 determines the operating mode to which the switch has been instructed.

[0084] Here, if the second mode setting key 62 has been operated to instruct switching to a mode compatible with a transaction processing system using the individual input method ("Mb" in ACT6), processor 31 proceeds to ACT7. In ACT7, processor 31 sets the mode data M in mode memory 321 to second mode Mb data compatible with a transaction processing system using the individual input method. Processor 31 also sets the status data S in status memory 322 to status Sb. In other words, processor 31 places the transaction processing system in a semi-self-service mode, rendering the transaction processing unable to be performed by the transaction processing system. Processor 31 then starts the second payment engine program 52 in ACT8. The operation of the transaction processing system using the second payment engine program 52 will be described later using Figure 8.

[0085] After starting the second payment engine program 52, the processor 31 waits for an instruction to switch the operating mode as ACT9. At this point, the second mode Mb, which corresponds to a transaction processing system using the individual input method, is set. Therefore, the processor 31 waits for an instruction to switch to the first mode Ma or the third mode Mc, which correspond to a transaction processing system using the semi-self-service method or the continuous input method. An instruction to switch to the semi-self-service method is given by operating the first mode setting key 61. An instruction to switch to the continuous input method is given by operating the third mode setting key 63.

[0086] When an instruction to switch the operating mode is issued, processor 31 checks whether second payment engine program 52 is idle in ACT 10. If second payment engine program 52 is not idle, i.e., if payment processing is being executed, the operating mode cannot be switched. Processor 31 determines NO in ACT 10 and returns to ACT 9.

[0087] If the second payment engine program 52 is idle, i.e., if payment processing is not being executed, the processor 31 determines YES in ACT 10 and proceeds to ACT 11. In ACT 11, the processor 31 stops the second payment engine program 52. Then, in ACT 12, the processor 31 determines the operating mode to which the switch has been instructed.

[0088] Here, if an instruction to switch to a mode corresponding to a semi-self-service transaction processing system is given by operating first mode setting key 61 ("Ma" in ACT12), processor 31 proceeds to ACT1. That is, processor 31 sets mode data M in mode memory 321 to data for first mode Ma, and sets status data S in status memory 322 to status Sa. Processor 31 also starts first settlement engine program 51. Processor 31 then executes the processing from ACT3 onwards in the same manner as described above.

[0089] If, in ACT6 or ACT12, an instruction to switch to the third mode Mc, which is compatible with a transaction processing system using the continuous input method, is input by operating the third mode setting key 63 ("Mc" in ACT6 or ACT12), processor 31 proceeds to ACT13. In ACT13, processor 31 sets the mode data M in the mode memory 321 to data for the third mode Mc, which is compatible with a transaction processing system using the continuous input method. Processor 31 also sets the status data S in the status memory 322 to status Sb. In other words, processor 31 sets the payment device 12 to a state in which it is unable to perform payment processing as a payment device in a semi-self-service transaction processing system. Then, processor 31 starts the third payment engine program 53 in ACT14. The operation of the payment device 12 when the third payment engine program 53 is started will be described later using Figure 9.

[0090] After starting the third payment engine program 53, the processor 31 checks whether an instruction to switch the operating mode has been issued in ACT15. At this point, the third mode Mc, which corresponds to a transaction processing system using the continuous input method, is set. Therefore, the processor 31 waits for an instruction to switch to the first mode Ma or the second mode Mb, which correspond to a transaction processing system using the semi-self-service method or the individual input method. An instruction to switch to the semi-self-service method is issued by operating the first mode setting key 61. An instruction to switch to the individual input method is issued by operating the second mode setting key 62.

[0091] When an instruction to switch the operating mode is issued, processor 31 checks whether third payment engine program 53 is idle in ACT 16. If third payment engine program 53 is not idle, i.e., if payment processing is being executed, the operating mode cannot be switched. Processor 31 determines NO in ACT 16 and returns to ACT 15.

[0092] If the third payment engine program 53 is idle, i.e., if the third payment engine program 53 is not currently executing payment processing as a checkout machine in a continuous input transaction processing system, the processor 31 determines YES in ACT 16 and proceeds to ACT 17. In ACT 17, the processor 31 stops the third payment engine program 53. Then, in ACT 18, the processor 31 determines the operating mode to which the switch has been instructed.

[0093] Here, when an instruction to switch to first mode Ma corresponding to a semi-self-service transaction processing system is given by operating first mode setting key 61 ("Ma" in ACT18), processor 31 proceeds to ACT1. That is, processor 31 sets mode data M in mode memory 321 to data of first mode Ma, and sets status data S in status memory 322 to status Sa. Processor 31 also starts first settlement engine program 51. Processor 31 then executes the processes from ACT3 onwards in the same manner as described above.

[0094] On the other hand, when an instruction to switch to second mode Mb corresponding to an individual input type transaction processing system is given by operating second mode setting key 62 ("Mb" in ACT18), processor 31 proceeds to ACT7. That is, processor 31 sets mode data M in mode memory 321 to second mode Mb data, and sets status data S in status memory 322 to status Sb. Processor 31 also starts second settlement engine program 52. Processor 31 then executes the processing from ACT9 onwards in the same manner as described above.

[0095] In this way, processor 31 cooperates with the first mode setting key 61, second mode setting key 62, and third mode setting key 63, which are the operating elements, to execute the information processing procedure shown in the flowchart of Figure 6 in accordance with mode setting program 54. Through this information processing, processor 31 can set the operating mode of accounting machine 12 to one of the following: first mode Ma, which corresponds to a semi-self-service transaction processing system; second mode Mb, which corresponds to an individual input transaction processing system; or third mode Mc, which corresponds to a continuous input transaction processing system.

[0096] Specifically, when the operator operates the first mode setting key 61 while the second payment engine program 52 or the third payment engine program 53 is idle, the processor 31 sets the operating mode of the payment machine 12 to the first mode Ma, which corresponds to a semi-self-service transaction processing system. When the operator operates the second mode setting key 62 while the first payment engine program 51 or the third payment engine program 53 is idle, the processor 31 sets the operating mode of the payment machine 12 to the second mode Mb, which corresponds to a transaction processing system using an individual input method. When the operator operates the third mode setting key 63 while the first payment engine program 51 or the second payment engine program 52 is idle, the processor 31 sets the operating mode of the payment machine 12 to the third mode Mc, which corresponds to a transaction processing system using a continuous input method.

[0097] Here, the processor 31 that executes the processes of ACT1 to ACT18 in FIG.

[0098] <<Explanation of the operation of the cashier using the first payment engine program>> 7 is a flowchart showing the information processing procedure executed by the processor 31 of the payment machine 12 in accordance with the first payment engine program 51. When the first payment engine program 51 starts and is in an idle state, the processor 31 waits for a request command for status data S as ACT21.

[0099] As explained using FIG. 4, the request command for the status data S is transmitted from the registration device 11. When the request command for the status data S is received, the processor 31 determines YES in ACT21 and proceeds to ACT22. In ACT22, the processor 31 obtains the status data S from the status memory 322. The status data S is set to status Sa in ACT1 of FIG. 6. The processor 31 transmits a response command including the status data S to the registration device 11 that sent the request command.

[0100] In ACT24, processor 31 waits for payment data. As described with reference to FIG. 4, when a response command including status Sa is sent to registration device 11, payment data is sent from registration device 11. Upon receiving the payment data, processor 31 determines YES in ACT24 and proceeds to ACT25. In ACT25, processor 31 temporarily sets status data S to status Sb. Then, in ACT26, processor 31 displays the payment method selection screen on the screen of touch panel 38.

[0101] The payment method selection screen is a screen on which payment method selection buttons such as a cash button, a credit button, and an electronic money button are arranged as operators. The cash button is touched by a customer who selects cash as their payment method. The credit button is touched by a customer who selects credit card as their payment method. The electronic money button is touched by a customer who selects electronic money as their payment method. Note that the payment methods are not limited to cash, credit card, and electronic money. Any two of these methods may be used, or another payment method may be selectable. Also, only one payment method may be used. In this case, instead of the payment method selection buttons, an operator for instructing the start of payment, such as a start payment button, may be displayed on the payment method selection screen.

[0102] The processor 31 waits for a payment method to be selected in ACT27. If a payment method is selected by operating the payment method selection screen, the processor 31 determines YES in ACT27 and proceeds to ACT28. The processor 31 executes the settlement process in ACT28. For example, if cash is selected as the payment method, the processor 31 subtracts the total amount from the amount inserted into the automatic change dispenser, calculates the change, and dispenses it from the automatic change dispenser. For example, if a credit card is selected as the payment method, the processor 31 authenticates the credit card read by the reader / writer 40, and, if approved, determines the total amount as the credit card settlement amount. For example, if electronic money is selected as the payment method, the processor 31 subtracts the total amount from the balance of the electronic money medium read by the reader / writer 40.

[0103] When the payment process is complete, processor 31 proceeds to ACT 29. In ACT 29, processor 31 controls the printing of a receipt by printer 39. Transaction detail data such as the name of the purchased item, price, number of items sold, sales amount, total number of items, total amount, and payment amount are printed on the receipt.

[0104] Thereafter, processor 31 returns status data S to status Sa as ACT30. With this, processor 31 ends information processing in accordance with first payment engine program 51. First payment engine program 51 returns to the idle state. Therefore, processor 31 again waits for a request command for status data S as ACT21.

[0105] Note that a status request command may be sent from the registration device 11 between the time when the status data S is set to status Sb in ACT 25 and the time when it is changed back to status Sa in ACT 30. In this case, too, the processor 31 obtains the status data S from the status memory 322 and sends a response command including the status data S to the registration device 11. Since the status data S at this time is status Sb, as explained with reference to FIG. 4, no payment data is sent from the registration device 11.

[0106] Here, the processor 31 realizes the function of first processing means 311 by executing the process of ACT28 in FIG.

[0107] <<Explanation of the operation of the cashier using the second payment engine program>> 8 is a flowchart showing the information processing procedures executed by the processor 31 of the payment machine 12 in accordance with the second payment engine program 52. When the second payment engine program 52 starts and is in an idle state, the processor 31 checks in ACT41 whether a request command for status data S has been received. If a request command has not been received, the processor 31 determines NO in ACT41 and proceeds to ACT42. In ACT42, the processor 31 checks whether an accounting barcode has been scanned with the scanner 37. If an accounting barcode has not been scanned, the processor 31 determines NO in ACT42 and returns to ACT41. In this way, when the second payment engine program 52 is in an idle state, the processor 31 waits to receive a request command for status data S or to scan an accounting barcode.

[0108] As explained using Figure 4, the request command for status data S is sent from registration machine 11. Even when the second payment engine program 52 is running and the payment machine 12 is operating as a payment machine in an individual input method transaction processing system, a request command for status data S may be sent from registration machine 11. For example, in Figure 4, the first payment machine 12-1 is a payment machine that constitutes a semi-self-service method transaction processing system, and the second payment machine 12-2 is a payment machine that constitutes an individual input method transaction processing system. In this case, when a request command is sent from registration machine 11 at a time when the status data S of the first payment machine 12-1 is status Sb, registration machine 11 sends a request command for status data S to the second payment machine 12-2.

[0109] When a request command for status data S is received in the standby state of ACT41 and ACT42, processor 31 determines YES in ACT41 and proceeds to ACT43. In ACT43, processor 31 retrieves status data S from status memory 322. Status data S is set to status Sb in ACT7 of Figure 6. In ACT43, processor 31 sends a response command including status data S to registration device 11, which sent the request command. When registration device 11 receives a response command including status data of status Sb, it does not send payment data to payment device 12, which sent the response command.

[0110] Here, the processor 31 realizes the function of the response means 314 by executing the processes of ACT43 and ACT44 in FIG.

[0111] When the transaction barcode is scanned while in standby mode in ACT41 or ACT42, the processor 31 determines YES in ACT42 and proceeds to ACT45. In ACT45, the processor 31 sends a transaction notification command to the virtual POS server 14. As explained using FIG. 5, the transaction notification command includes terminal identification information obtained by decoding the transaction barcode. Upon receiving the transaction notification command, the virtual POS server 14 sends a transaction file associated with the terminal identification information to the accounting machine 12.

[0112] The processor 31 waits for a transaction file in ACT46. When the processor 31 receives the transaction file from the virtual POS server 14, it determines YES in ACT46 and proceeds to ACT47. The processor 31 executes a product registration process based on the data in the transaction file in ACT47. That is, the processor 31 registers the sales data of the purchased products in the sales total memory based on the product sales data stored in the transaction file. This registration process calculates the total amount of the transaction. The sales total memory is formed in the volatile memory area of ​​the main memory 32.

[0113] Upon completing the product registration process, processor 31 executes the same processes as ACT26 to ACT29 in FIG. 7 in ACT48 to ACT51. That is, processor 31 displays the payment method selection screen on touch panel 38 in ACT48. Then, processor 31 waits for a payment method to be selected in ACT49. If a payment method is selected, processor 31 executes the payment process in ACT50. Then, upon completing the payment process, processor 31 controls the issuance of a receipt in ACT51. With this, processor 31 ends the information processing in accordance with second payment engine program 52. Second payment engine program 52 returns to the idle state. Therefore, processor 31 again enters the standby state for ACT41 and ACT42.

[0114] Here, the processor 31 realizes the function of second processing means 312 by executing the process of ACT50 in FIG. <<Explanation of the operation of the cashier using the third payment engine program>> FIG. 9 is a flowchart showing the information processing steps executed by the processor 31 of the payment device 12 in accordance with the third payment engine program 53. When the third payment engine program 53 starts and is in an idle state, the processor 31 checks in ACT61 whether a request command for status data S has been received. If a request command has not been received, the processor 31 determines NO in ACT61 and proceeds to ACT62. The processor 31 checks in ACT62 whether a registration start declaration operation has been performed. When the third payment engine program 53 is in an idle state, a registration start button is displayed on the screen of the touch panel 38. The registration start button is the button that a customer who is operating the payment device 12 by themselves to enter data related to purchased items and pay for those purchased items will first operate. When the registration start button is operated, the processor 31 determines that a registration start declaration operation has been performed.

[0115] If the operation to declare the start of registration has not been performed, the processor 31 determines NO in ACT 62 and returns to ACT 61. In this way, when the third payment engine program 53 is in the idle state, the processor 31 waits for the reception of a request command for the status data S or for the operation to declare the start of registration.

[0116] As explained using Figure 4, the request command for status data S is sent from registration device 11. Even when third payment engine program 53 is running and payment device 12 is operating as a payment device in a transaction processing system using a continuous input method, a request command for status data S may be sent from registration device 11, just as when payment device 12 is operating as a payment device in a transaction processing system using an individual input method.

[0117] When a request command for status data S is received in the standby state of ACT61 and ACT62, processor 31 determines YES in ACT61 and proceeds to ACT63. In ACT63, processor 31 retrieves status data S from status memory 322. Status data S is set to status Sb in ACT13 of Figure 6. In ACT63, processor 31 sends a response command including status data S to registration device 11, which sent the request command. When registration device 11 receives a response command including status data of status Sb, it does not send payment data to payment device 12, which sent the response command.

[0118] Here, the processor 31 realizes the function of the response means 314 by executing the processes of ACT63 and ACT64 in FIG.

[0119] When the registration start button is operated in the standby state of ACT 61 and ACT 62, the processor 31 determines YES in ACT 62 and proceeds to ACT 65. The processor 31 clears the transaction file in ACT 65. The transaction file is formed in the volatile memory area of ​​the main memory 32.

[0120] Processor 31 waits for product registration in ACT66. If the purchased product has a barcode attached, the customer who pressed the registration start button scans the barcode with scanner 37. If the purchased product does not have a barcode attached, the customer selects the purchased product from a list of products without barcodes displayed on touch panel 38. When data related to the purchased product is entered through this operation, processor 31 determines that product registration has been completed. Processor 31 executes product registration processing in ACT67. That is, processor 31 registers product sales data including the purchased product's product code, product name, price, number of units sold, sales amount, etc., in the transaction file.

[0121] Processor 31 then checks in ACT 68 whether the next product has been registered. If no product has been registered, processor 31 determines NO in ACT 68 and proceeds to ACT 69. Processor 31 then checks in ACT 69 whether a transaction has been performed. If no transaction has been performed, processor 31 determines NO in ACT 69 and returns to ACT 68. In this way, processor 31 waits for a product to be registered or a transaction to be performed.

[0122] If product registration is performed in the standby state of ACT68 and ACT69, processor 31 determines YES in ACT68 and returns to ACT67. That is, processor 31 executes the product registration process. Processor 31 then waits again for product registration or a checkout operation to be performed.

[0123] A checkout button is displayed on touch panel 38. When a customer has finished entering data for all purchased items and wishes to proceed to payment, they press the checkout button. When the checkout button is pressed, processor 31 determines that a checkout operation has been performed.

[0124] When a payment operation is performed while in standby mode in ACT68 and ACT69, processor 31 executes the same processing as ACT48 to ACT51 in Figure 8 in ACT70 to ACT73. That is, processor 31 displays the payment method selection screen on touch panel 38 in ACT70. Then, processor 31 waits for a payment method to be selected in ACT71. If a payment method is selected, processor 31 executes the payment process in ACT72. Then, once the payment process is complete, processor 31 controls the issuance of a receipt in ACT73. This completes information processing in accordance with third payment engine program 53. Third payment engine program 53 returns to idle mode. Therefore, processor 31 once again enters standby mode in ACT61 and ACT62.

[0125] Here, the processor 31 performs the process of ACT72 in FIG. 9, thereby realizing the function of the second processing means 312 in the same way as when the process of ACT50 in FIG. 8 is performed.

[0126] <Effects of the transaction processing system> In the transaction processing system 1 illustrated in Figure 1, the operating mode of all first payment machines 12-1 and second payment machines 12-2 is set to first mode Ma. By doing so, the first payment machine 12-1 and second payment machine 12-2 function as payment machines that make up a semi-self-service transaction processing system together with the corresponding registration machine 11. Therefore, a customer whose purchase data has been entered by a store clerk into the registration machine 11 can pay for the purchased items themselves at the payment machine 12 (first payment machine 12-1 or second payment machine 12-2) indicated by the store clerk.

[0127] Meanwhile, for example, the second mode setting key 62 of the second payment machine 12-2 is operated to change the operating mode to second mode Mb. In this case, the first payment machine 12-1 functions as a payment machine that, together with the corresponding registration machine 11, constitutes a semi-self-service transaction processing system, while the second payment machine 12-2 functions as a payment machine that, together with the communication terminal 2 and virtual POS server 14, constitutes an individual-input transaction processing system. Therefore, a customer who has entered the data of their purchased items by themselves using the communication terminal 2 on the sales floor can then use the scanner 37 of the second payment machine 12-2 to scan the payment barcode displayed on the display device of the communication terminal 2, thereby paying for the purchased items by themselves at the second payment machine 12-2.

[0128] Also, for example, the third mode setting key 63 of the second payment machine 12-2 is operated to change the operating mode to third mode Mc. In this case, the first payment machine 12-1 functions as a payment machine that, together with the corresponding registration machine 11, constitutes a semi-self-service transaction processing system, while the second payment machine 12-2 functions as a payment machine that constitutes a continuous-input transaction processing system. Therefore, by using the second payment machine 12-2, a customer can complete all the steps for themselves, from entering data about the purchased items to paying the price.

[0129] After the second payment machine 12-2 has been changed to the second mode Mb or the third mode Mc, it can be returned to the first mode Ma by operating the first mode setting key 61. In other words, the second payment machine 12-2 can be made to function as a semi-self-service payment machine.

[0130] In this way, the accounting machine 12 in this embodiment can be switched between functioning as a semi-self-service accounting machine and as an individual input or continuous input accounting machine with a simple key operation. Therefore, for example, during busy times when there are many customers, it can be used as a semi-self-service accounting machine to speed up customer payments, but during quiet times when there are fewer customers, it can be used as an individual input or continuous input accounting machine to reduce the number of employees, making it easy to implement an operation like this.

[0131] Furthermore, for example, when the second payment device 12-2 is functioning as a payment device using the individual input method or the continuous input method, the status data S in the status memory 322 is status Sb. Then, when the second payment device 12-2 receives a status request command from the registration device 11, it responds to the registration device 11 with status data S of status Sb. Upon receiving this response, the registration device 11 does not send payment data to the second payment device 12-2. Therefore, there is no chance of the registration device 11 sending payment data to the second payment device 12-2, which is functioning as a payment device using the individual input method or the continuous input method.

[0132] Note that input of the first mode setting key 61 is valid when the second payment engine program 52 or the third payment engine program 53 is in an idle state. Input of the second mode setting key 62 is valid when the first payment engine program 51 or the third payment engine program 53 is in an idle state. Input of the third mode setting key 63 is valid when the first payment engine program 51 or the second payment engine program 52 is in an idle state. Therefore, there is no risk of the operating mode of the payment machine 12 switching during a payment process, causing an error in the payment process.

[0133] [Second embodiment] Next, a second embodiment will be described with reference to FIGS. The second embodiment differs from the first embodiment in the sequence of communication between registration machine 11, first accounting machine 12-1, and second accounting machine 12-2, which make up the semi-self-service transaction processing system. Since the configuration of the transaction processing system is the same as in the first embodiment, Figure 1 is used as is in the second embodiment.

[0134] FIG. 10 is a sequence diagram of the above according to the second embodiment. In the semi-self-service system, the registration machine 11 inputs data related to the items purchased by the customer. Then, once the data related to all purchased items has been input, the registration machine 11 transmits payment data to, for example, the first payment machine 12-1. The payment data is data necessary for the payment machine 12 to process payment for the purchased items. The payment data includes at least the product code and the number of items purchased. If a discount or deduction has been input for the subtotal of the transaction, the payment data also includes the discount amount or discount rate. The payment data is an example of data related to the first purchased item.

[0135] Upon receiving the payment data, the first payment machine 12-1 checks the status data S stored in the status memory 322. If the status data S is status Sa, meaning that the payment process can be executed, it sends an execution response command to the registration machine 11. The first payment machine 12-1 executes the payment process according to the customer's input.

[0136] If the status data S is status Sb, meaning that the payment process cannot be executed, the first payment machine 12-1 sends (transfers) the payment data to the second payment machine 12-2. Upon receiving the payment data, the second payment machine 12-2 checks the status data S stored in the status memory 322. If the status data S is status Sa, meaning that the payment process can be executed, it sends an execution response command to the registration machine 11. The second payment machine 12-2 executes the payment process according to the customer's operational input.

[0137] If the status data S is status Sb, that is, if the payment process cannot be performed, the second payment machine 12-2 sends an error response command to the registration machine 11. Upon receiving the error response command, the registration machine 11 again sends payment data to the first payment machine 12-1. Thus, when either the first payment machine 12-1 or the second payment machine 12-2 becomes able to perform the payment process, the payment process is performed at the payment machine 12 (first payment machine 12-1 or second payment machine 12-2) that received the payment data.

[0138] Incidentally, when the registration machine 11 receives the execution response command, it displays information identifying the payment machine 12 (first payment machine 12-1 or second payment machine 12-2) that sent the execution response command on the display device. The store clerk operating the registration machine 11 simply instructs the customer to pay for the purchased items at the payment machine 12 identified by the displayed information.

[0139] It should be noted that the payment machine 12 to which the registration machine 11 first sends payment data is not limited to the first payment machine 12-1. The payment data may be sent to the second payment machine 12-2 first, and if the second payment machine 12-2 is unable to execute the payment process, the second payment machine 12-2 may send (transfer) the payment data to the first payment machine 12-1.

[0140] Figure 11 is a block diagram showing the main circuit configuration of the payment machine 12 in the second embodiment. Note that parts that are common to Figure 2, which shows the main circuit configuration of the payment machine 12 in the first embodiment, are given the same reference numerals, and detailed explanations thereof will be omitted.

[0141] The second embodiment of the payment machine 12 differs from the first embodiment in some of the functions of the processor 31. In other words, instead of the response means 314 function possessed by the processor 31 in the first embodiment, the second embodiment of the payment machine 12 possesses a transfer means 315. The transfer means 315 transfers data related to the first purchased item received from the registration machine 11 to another payment machine when payment processing by the second processing means 312 is valid.

[0142] Like the first embodiment, the payment machine 12 configured as above also has the program structure shown in the schematic diagram of Figure 3. The information processing procedure executed by the processor 31 of the payment machine 12 in accordance with the mode setting program 54 is the same as in the first embodiment. Therefore, Figure 6 is also adopted as is in the second embodiment.

[0143] On the other hand, the information processing procedures executed by processor 31 in accordance with first payment engine program 51, second payment engine program 52, and third payment engine program 53 are partially different from those in the first embodiment. Therefore, the procedures will be explained below step by step.

[0144] <<Explanation of the operation of the cashier using the first payment engine program>> 12 is a flowchart showing the information processing steps executed by the processor 31 of the payment device 12 in accordance with the first payment engine program 51. When the first payment engine program 51 starts and is in an idle state, the processor 31 waits for payment data as ACT81. As explained using FIG. 4, the payment data is transmitted from the registration device 11 or the other payment device 12.

[0145] Upon receiving the payment data, the processor 31 determines YES in ACT81 and proceeds to ACT82. In ACT82, the processor 31 checks the status data S stored in the status memory 322. If the status data S is status Sa, that is, if the payment process can be executed, the processor 31 determines YES in ACT82 and proceeds to ACT83. In ACT83, the processor 31 temporarily sets the status data S to status Sb. In addition, in ACT84, the processor 31 sends an execution response command to the registration device 11. Then, in ACT85, the processor 31 displays the payment method selection screen on the screen of the touch panel 38.

[0146] The subsequent processing procedures from ACT86 to ACT89 are the same as ACT27 to ACT30 in the first embodiment described with reference to Fig. 7. Therefore, the description here will be omitted.

[0147] When the processing of ACT89 is completed, the processor 31 ends the information processing in accordance with the first payment engine program 51. The first payment engine program 51 returns to the idle state. Therefore, the processor 31 waits for payment data again as ACT81.

[0148] On the other hand, if the status data S when the payment data is received is status Sb, i.e., if the payment process cannot be executed, processor 31 judges NO in ACT82 and proceeds to ACT90. In ACT90, processor 31 checks whether there is another payment machine to which the payment data can be transferred. In the example sequence of Figure 10, the first payment machine 12-1 has a second payment machine 12-2 as a transfer destination. However, the second payment machine 12-2 does not have another payment machine as a transfer destination.

[0149] If a transfer destination exists, processor 31 determines YES in ACT90 and proceeds to ACT91. In ACT91, processor 31 sends (transfers) the payment data to the other payment machine that is the transfer destination. If a transfer destination does not exist, processor 31 determines NO in ACT90 and proceeds to ACT92. In ACT92, processor 31 sends an error response command to registration machine 11.

[0150] When the processing of ACT91 or ACT92 is completed, the processor 31 ends the information processing in accordance with the first payment engine program 51. The first payment engine program 51 returns to the idle state. Therefore, the processor 31 again waits for payment data in ACT81.

[0151] Here, the processor 31 performs the processing of ACT87 to realize the function of first processing means 311. The processor 31 also performs the processing of ACT91 to realize the function of forwarding means 315.

[0152] <<Explanation of the operation of the cashier using the second payment engine program>> 13 is a flowchart showing the information processing procedures executed by the processor 31 of the payment device 12 in accordance with the second payment engine program 52. When the second payment engine program 52 starts and is in an idle state, the processor 31 checks in ACT101 whether payment data has been received. If payment data has not been received, the processor 31 determines NO in ACT101 and proceeds to ACT102. In ACT102, the processor 31 checks whether an accounting barcode has been scanned with the scanner 37. If an accounting barcode has not been scanned, the processor 31 determines NO in ACT102 and returns to ACT101. In this way, when the second payment engine program 52 is in an idle state, the processor 31 waits to receive payment data or scan an accounting barcode.

[0153] When the transaction barcode is scanned in the standby state of ACT101 and ACT102, processor 31 determines YES in ACT102 and proceeds to ACT 103. Then, processor 31 executes the same processing as ACT45 to ACT51 of the first embodiment described using Figure 8 in ACT103 to ACT109. Therefore, a description thereof will be omitted here.

[0154] When the processing of ACT109 is completed, the processor 31 ends the information processing in accordance with the second payment engine program 52. The second payment engine program 52 returns to the idle state. Therefore, the processor 31 again enters the standby state for ACT101 and ACT102.

[0155] On the other hand, if payment data is received in the standby state of ACT101 and ACT102, the processor 31 determines YES in ACT101 and proceeds to ACT110. In ACT110, the processor 31 checks whether there is another payment machine to which the payment data can be transferred. If there is a transfer destination, the processor 31 determines YES in ACT110 and proceeds to ACT111. In ACT111, the processor 31 sends (transfers) the payment data to the other payment machine that is the transfer destination. If there is no transfer destination, the processor 31 determines NO in ACT110 and proceeds to ACT112. In ACT112, the processor 31 sends an error response command to the registration device 11.

[0156] When the processing of ACT111 or ACT112 is completed, the processor 31 ends the information processing in accordance with the second payment engine program 52. The second payment engine program 52 returns to the idle state. Therefore, the processor 31 again enters the standby state for ACT101 and ACT102.

[0157] Here, the processor 31 performs the processing of ACT108 to realize the function of second processing means 312. The processor 31 also performs the processing of ACT111 to realize the function of forwarding means 315. <<Explanation of the operation of the cashier using the third payment engine program>> 14 is a flowchart showing the information processing procedures executed by the processor 31 of the payment device 12 in accordance with the third payment engine program 53. When the third payment engine program 53 starts and is in an idle state, the processor 31 checks in ACT121 whether payment data has been received. If payment data has not been received, the processor 31 determines NO in ACT121 and proceeds to ACT122. In ACT122, the processor 31 checks whether a declaration operation to start registration has been performed. If a declaration operation to start registration has not been performed, the processor 31 determines NO in ACT122 and returns to ACT121. In this way, when the third payment engine program 53 is in an idle state, the processor 31 waits for the receipt of payment data or the declaration operation to start registration.

[0158] If a registration start declaration operation is performed in the standby state of ACT121 and ACT122, the processor 31 determines YES in ACT122 and proceeds to ACT123. Then, the processor 31 executes the same processes as ACT65 to ACT73 of the first embodiment described with reference to Fig. 9 in ACT123 to ACT131. Therefore, a description thereof will be omitted here.

[0159] When the processing of ACT131 is completed, the processor 31 ends the information processing in accordance with the third payment engine program 53. The third payment engine program 53 returns to the idle state. Therefore, the processor 31 again enters the standby state for ACT121 and ACT122.

[0160] On the other hand, if payment data is received in the standby state in ACT121 and ACT122, the processor 31 determines YES in ACT121 and proceeds to ACT132. In ACT132, the processor 31 checks whether there is another payment machine to which the payment data can be transferred. If there is a transfer destination, the processor 31 determines YES in ACT132 and proceeds to ACT133. In ACT133, the processor 31 sends (transfers) the payment data to the other payment machine that is the transfer destination. If there is no transfer destination, the processor 31 determines NO in ACT132 and proceeds to ACT134. The processor 31 sends an error response command to the registration device 11 in ACT13.

[0161] When the processing of ACT133 or ACT134 is completed, the processor 31 ends the information processing in accordance with the third payment engine program 53. The third payment engine program 53 returns to the idle state. Therefore, the processor 31 again enters the standby state for ACT121 and ACT122.

[0162] Here, by executing the processing of ACT130, the processor 31 realizes the function of second processing means 312, similar to when the processing of ACT108 in Fig. 13 is executed. In addition, by executing the processing of ACT133, the processor 31 realizes the function of forwarding means 315.

[0163] In the second embodiment described above, the accounting machine 12 can also be switched by a simple key operation between functioning as a semi-self-service accounting machine and as an individual input or continuous input accounting machine.

[0164] [Other embodiments] In the above embodiment, the payment machine 12 is equipped with the first payment engine program 51, the second payment engine program 52, the third payment engine program 53, and the mode setting program 54. In this regard, the payment machine 12 is equipped with the first payment engine program 51 and the mode setting program 54, but it may be equipped with either the second payment engine program 52 or the third payment engine program 53. Even in this case, for example, a payment machine 12 equipped with the second payment engine program 52 can be easily switched between being used as a payment machine in a semi-self-service transaction processing system and being used as a payment machine in an individual input transaction processing system. Similarly, a payment machine 12 equipped with the third payment engine program 53 can be easily switched between being used as a payment machine in a semi-self-service transaction processing system and being used as a payment machine in a continuous input transaction processing system.

[0165] In the above embodiment, in describing the operation of the payment machine 12 using the mode setting program, the processor 31 first sets the mode data M in the mode memory 321 to the first mode Ma, which corresponds to a semi-self-service transaction processing system, in ACT 1. In this regard, the processor 31 may first set the mode data M in the mode memory 321 to the second mode Mb, which corresponds to a transaction processing system using an individual input method, in ACT 7. Alternatively, the processor 31 may first set the mode data M in the mode memory 321 to the third mode Mc, which corresponds to a transaction processing system using a continuous input method, in ACT 13.

[0166] In the above embodiment, an example was given in which two payment machines are connected to one registration machine, but the number of payment machines connected to a registration machine may be one or more than two. The payment machines connected to a registration machine are flexibly determined depending on the size of the store.

[0167] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0168] 1...transaction processing system, 11...registration machine, 12...accounting machine, 12-1...first accounting machine, 12-2...second accounting machine, 13...store server, 14...virtual POS server, 15...access point, 16...network, 31...processor, 32...main memory, 33...auxiliary storage device, 34...clock, 35...communication interface, 36...change machine interface, 37...scanner, 38...touch panel, 39...printer, 40...reader / writer, 41...system transmission path, 51...first payment engine program, 52...second payment engine program, 53...third payment engine program, 54...mode setting program, 61...first mode setting key, 62...second mode setting key, 63...third mode setting key, 311...first processing means, 312...second processing means, 313...switching means, 314...response means, 315...transfer means, 321...mode memory, 322...status memory.

Claims

1. A system is configured with a registration machine for inputting data related to purchased goods, and an accounting machine for processing payment for the purchased goods, a first processing means for processing payment for the first purchased product based on data relating to the first purchased product inputted by the registration machine; a second processing means for processing payment for the second purchased product based on data relating to the second purchased product input by a terminal or device other than the registration machine; a switching means for switching between enabling the payment process by the first processing means and enabling the payment process by the second processing means in response to an operation input of an operator; An accounting machine equipped with the above.

2. the system includes a plurality of the accounting machines; the registration machine transmits the input data relating to the first purchased product to any one of the accounting machines; a response means for responding, when the payment processing by the second processing means is valid, to the effect that the transmission of data relating to the first purchased product from the registration machine is not accepted; 2. The accounting machine of claim 1, further comprising:

3. the system includes a plurality of the accounting machines; the registration machine transmits the input data relating to the first purchased product to any one of the accounting machines; a transfer means for transferring data relating to the first purchased product received from the registration machine to another payment machine when the payment processing by the second processing means is valid; 2. The accounting machine of claim 1, further comprising:

4. 4. A cash register according to claim 1, wherein the data relating to the second purchased item for which payment is processed by the second processing means is data relating to the purchased item inputted into a terminal operated by a customer in the sales area.

5. 4. A payment machine according to claim 1, wherein the data relating to the second purchased item for which payment is processed by the second processing means is data relating to the purchased item input from an input device possessed by the payment machine.

6. A system is configured with a registration machine for inputting data related to purchased goods, and a computer of an accounting machine for processing payment for the purchased goods, a first processing means for processing payment for the first purchased product based on data relating to the first purchased product inputted by the registration machine; a second processing means for processing payment for the second purchased product based on data relating to the second purchased product input by a terminal or device other than the registration machine; and a switching means for switching between enabling the payment process by the first processing means and enabling the payment process by the second processing means in response to an operation input of an operator; A program to function as a

7. A system is configured with a registration machine for inputting data related to purchased goods, and an accounting machine for processing payment for the purchased goods, a first processing means for processing payment for the first purchased product based on data relating to the first purchased product inputted by the registration machine; a second processing means for processing payment for the second purchased product based on data relating to the second purchased product input by a terminal or device other than the registration machine; and A processing method for a checkout machine, which switches between enabling the payment processing by the first processing means and enabling the payment processing by the second processing means in response to an operation input from an operator.

Images