Sales data processing system

Abstract

We provide a sales data processing system that can automatically process payments using vouchers such as gift certificates and exchange vouchers. [Solution] The sales data processing system comprises master information storing information on vouchers, which are sheet-shaped media used for payment in settlement processing; a reader that reads information from the vouchers; and a settlement processing unit that performs settlement processing using the vouchers when the information of the vouchers corresponding to the reading result of the reader exists in the master information.

Description

Technical Field

[0001] Embodiments of the present invention relate to a sales data processing system.

Background Art

[0002] There are many types of vouchers such as gift certificates and exchange vouchers used in settlement processing. Vouchers are roughly classified into two types. One is a cash voucher (gift certificate) that can be used to pay the face value. The other is an exchange voucher that can be exchanged for a target product. For example, an exchange voucher is based on the exchange of the exchange voucher and the product. Since the selling price of the target product of the exchange voucher varies depending on the store, even when using a reading device that reads the voucher, it is necessary for a store clerk to intervene and perform sales data processing. In addition, the operation of gift certificates and exchange vouchers varies depending on the store.

Summary of the Invention

Problems to be Solved by the Invention

[0003] The problem to be solved by the present invention is to provide a sales data processing system that can appropriately perform settlement processing using vouchers such as gift certificates and exchange vouchers.

Means for Solving the Problems

[0004] The sales data processing system according to the embodiment includes master information in which information on a sheet-like medium (voucher) used for payment in settlement processing is stored, a reading device that reads information from the voucher, and a settlement processing unit that performs settlement processing using the voucher when the information on the voucher corresponding to the reading result of the reading device exists in the master information.

Brief Description of the Drawings

[0005] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a sales data processing system according to the first embodiment. [Figure 2] FIG. 2 is a perspective view showing an example of the appearance of a reading device according to the first embodiment. [Figure 3]Figure 3 is a block diagram showing an example of the server hardware configuration in the first embodiment. [Figure 4] Figure 4 is a block diagram showing an example of the hardware configuration of the reading device in the first embodiment. [Figure 5] Figure 5 is a block diagram showing an example of the hardware configuration of the sales data processing device in the first embodiment. [Figure 6] Figure 6 is a block diagram showing an example of the functional configuration in the first embodiment. [Figure 7] Figure 7 is a schematic sequence diagram showing an example of the payment processing flow in the first embodiment. [Figure 8] Figure 8 shows an example of a screen displayed by the display unit of the sales data processing device in the first embodiment. [Figure 9] Figure 9 shows an example of a screen displayed by the display unit of the sales data processing device in the first embodiment. [Figure 10] Figure 10 shows an example of a screen displayed by the display unit of the sales data processing device in the first embodiment. [Figure 11] Figure 11 shows an example of a screen displayed by the display unit of the sales data processing device in the first embodiment. [Figure 12] Figure 12 shows an example of a screen displayed by the display unit of the sales data processing device in the first embodiment. [Figure 13] Figure 13 shows an example of a screen displayed by the display unit of the sales data processing device in the first embodiment. [Figure 14] Figure 14 shows an example of a screen displayed by the display unit of the sales data processing device in the second embodiment. [Figure 15] Figure 15 shows an example of a screen displayed by the display unit of the sales data processing device in the third embodiment. [Figure 16] Figure 16 shows an example of a screen displayed by the display unit of the sales data processing device in the fourth embodiment. [Figure 17] Figure 17 shows an example of a screen displayed by the display unit of the sales data processing device in the fourth embodiment. [Figure 18] Figure 18 shows an example of a screen displayed by the display unit of the sales data processing device in the fourth embodiment. [Figure 19] Figure 19 shows an example of a screen displayed by a display device connected to the server in the fifth embodiment. [Modes for carrying out the invention]

[0006] (First Embodiment) A first embodiment will be described with reference to the drawings. Figure 1 is a block diagram showing an example of the configuration of a sales data processing system in the first embodiment. The sales data processing system includes a server 1, a reader 3, and a sales data processing device 5.

[0007] Server 1 is an information processing device such as a PC (personal computer), and is installed, for example, in the back room of a store. Server 1 manages information used and generated by other devices within the store (such as the sales data processing device 5), and is also called a store controller. Server 1 may also be a cloud server installed outside the store.

[0008] The sales data processing device 5 is installed in the store and processes information about products sold to customers. More specifically, the sales data processing device 5 performs tasks such as registering product information and settling payments for registered products.

[0009] The sales data processing device 5 includes not only general POS terminals operated by store staff, but also self-checkout devices (also called self-POS) for customers to register and pay for their own products, payment machines (also called payment devices or semi-self-service terminals) for customers to pay for products registered by store staff, and registration devices used by store staff to register products. Note that POS is an abbreviation for "Point of Sale," meaning "point-of-sale information management." The sales data processing device 5, including POS terminals and self-checkout devices, is a device that manages point-of-sale information.

[0010] The reading device 3 is a device that reads information from a "ticket", which is a sheet-like medium such as paper. The ticket is, for example, a gift ticket or an exchange ticket, and is used for payment in a settlement process for paying the price of a product. A gift ticket is a money ticket that can be used in place of cash equivalent to the displayed amount (face value). An exchange ticket is a ticket that can be exchanged for a target product, such as a beer ticket or a rice ticket.

[0011] More specifically, the reading device 3 recognizes the type of the ticket and determines whether the ticket is genuine or fake, and cooperates with the sales data processing device 5. Specifically, the reading device 3 operates according to an instruction received from the sales data processing device 5, and outputs the recognition result of the ticket determined to be genuine to the sales data processing device 5.

[0012] FIG. 2 is a perspective view showing an example of the appearance of the reading device 3 in the first embodiment. The reading device 3 includes a main body portion 41, a lid portion 42, a hinge portion 43, an insertion / discharge port 45, a support portion 46, a storage portion 47, and the like.

[0013] The main body portion 41 and the lid portion 42 constitute the housing of the reading device 3. The main body portion 41 is a box having an upward opening, and incorporates various electronic components (see FIG. 4, described later) including a reader 37 and a storage portion 47. The hinge portion 43 rotatably connects the rear end of the lid portion 42 to the main body portion 41. The lid portion 42 moves between a position where it closes the opening of the main body portion 41 and a position where it opens the opening as it rotates.

[0014] The insertion / discharge port 45 is an opening that receives the insertion of a ticket into the housing and discharges the ticket outside the housing. The support portion 46 supports the lower surface of the ticket discharged from the insertion / discharge port 45. Also, the support portion 46 serves as a guide for easily inserting the tip of the ticket into the insertion / discharge port 45 when inserting the ticket into the housing.

[0015] The reading device 3 stores the ticket whose use has been determined after reading in the storage portion 47. Also, the reading device 3 discharges the ticket whose non-use has been determined after reading from the insertion / discharge port 45.

[0016] Figure 3 is a block diagram showing an example of the hardware configuration of Server 1 in the first embodiment. Server 1 includes a CPU (Central Processing Unit) 11, ROM (Read Only Memory) 12, RAM (Random Access Memory) 13, a communication unit 14, a storage unit 19, etc.

[0017] The communication unit 14 is a wired or wireless communication interface that can be connected to a network such as a LAN. The communication unit 14 communicates with various sales data processing devices via the network.

[0018] CPU11 is an example of a processor that comprehensively controls the operation of Server 1. ROM12 stores various programs. RAM13 is a workspace for displaying programs and various data.

[0019] The CPU 11, ROM 12, and RAM 13 are connected via a bus or the like to form a control unit 10 of the computer configuration. In the control unit 10, the CPU 11 operates according to a program stored in the ROM 12 or memory unit 19 and loaded into the RAM 13, thereby executing various processes.

[0020] The storage unit 19 is composed of a non-volatile storage medium such as an HDD (Hard Disk Drive) or flash memory, and retains its contents even when the power is cut off. The storage unit 19 stores programs 191 that the CPU 11 can execute, as well as various setting information. For example, the program 191 includes a program for realizing the functional configuration described later.

[0021] The memory unit 19 stores product master data 193, ticket master data 195, transaction information 197, and the like.

[0022] These are just examples, and the storage unit 19 may store other information as well. The various types of information stored in the storage unit 19 may be acquired in advance from other external devices via a network, or they may be acquired and updated automatically.

[0023] <Product Master> The product master 193 is a compilation of information (product information) about the products handled by the store, and is stored in the storage unit 19, for example, in the form of a data table. The items included in the data table as the product master 193 are, for example, as follows: Product Code ·Product name ·unit price • Verification data

[0024] A product code is information that uniquely identifies a product (identification information), such as a JAN (Japanese Article Number) code. Other information (product name, unit price, matching data, classification, etc.) is stored in association with the product code. The "product name" field stores the name of the product. The "unit price" field stores the selling price (sale price) for one unit of the product.

[0025] The "matching data" field stores reference feature quantities. Each device processing sales data can recognize a product by comparing the feature quantities of the product image contained in the image captured and output by a camera, etc. (captured image), with the matching data, and obtaining the product code associated with the matching data. The matching determination described above is made, for example, by calculating the similarity between the feature quantities of the captured image and the matching data, comparing the calculated similarity with a threshold, and determining that the matching data has a similarity equal to or greater than the threshold. The product code may also be obtained by reading (scanning and decoding) code symbols such as barcodes or two-dimensional codes attached to the product.

[0026] <Ticket Master> Ticket Master 195 is an example of master information. Master information stores information about gift certificates used as monetary vouchers equivalent to their face value, associated with the identification information of those gift certificates. Master information also stores information about exchange vouchers that can be exchanged for target products, associated with the identification information of those exchange vouchers.

[0027] The ticket master 195 is a compilation of information on tickets such as gift certificates and exchange vouchers, and is stored in the storage unit 19, for example, in the form of a data table. The items included in the data table as the ticket master 195 are, for example, the following: Ticket ID ·Ticket name Ticket type • Face value • Target products Processing type • Expiration information • Store information

[0028] The term "voucher type" refers to the type of voucher, such as a gift certificate or an exchange voucher. A gift certificate is a monetary voucher that can be used in place of cash equivalent to its face value. An exchange voucher is a voucher that can be exchanged for a designated product.

[0029] The face value is the amount displayed on the gift certificate. If the gift certificate type is an exchange voucher, the face value setting is, for example, blank.

[0030] The target products are items that customers can obtain for free in exchange for a voucher. One or more target products are specified for each voucher. Correspondingly, one or more product codes are recorded in the target product field of the record where the voucher type is a voucher. The product codes recorded in the target product field are the product codes of the target products.

[0031] The ticket ID is the identification information for the ticket, and is unique to each combination of ticket type and face value, or each combination of ticket type and the product it is used for, for example, a number. The ticket name is the name given to the ticket by the issuer.

[0032] The processing type is a value set when the ticket ID indicates an exchange voucher. This value specifies the sales data processing when the ticket ID is used. For example, if the processing type value is "1", a discount equal to the selling price of the product covered by the ticket ID will be applied in the payment (first processing). Also, for example, if the processing type value is "2", the payment using the ticket ID will be processed in the same way as when a cash voucher equivalent to the selling price of the product covered by the ticket is used (second processing).

[0033] The expiration information indicates the expiration date of the ticket indicated by the ticket ID. Tickets with an expiration date of the current date and time or later can be used for payment. If the expiration date is in the past than the current date and time, the ticket with that ticket ID cannot be used for payment.

[0034] Store handling information indicates whether the ticket indicated by the ticket ID is currently being handled by the store, that is, whether it is available for payment at the store. This information is represented by a binary value, such as "1" or "0," where "1" indicates it is usable and "0" indicates it is not handled and therefore unusable.

[0035] <Transaction Information> Transaction information 197 is information about the products purchased by the customer in a transaction, and is received from the in-store sales data processing device and stored (registered). Transaction information 197 may include not only information from the store itself, but also transaction information received from sales data processing devices of other stores.

[0036] Transaction information 197 is compiled, for example, in the format of a journal log. The items included in transaction information 197 are, for example, the following: Store ID • Device ID • Employee ID Transaction ID · Date and time • Detailed information • Transaction amount • Payment method and amount information

[0037] The "Store ID" field stores the store ID of the store where the transaction for the record took place. The "Terminal ID" field stores the terminal ID of the sales data processing device that performed the transaction for the record. The terminal ID is identification information for the sales data processing device and is assigned in a way that does not duplicate even within the same store. The "Employee ID" field stores the ID of the employee who was logged into the sales data processing device 5 as the operator for the transaction for the record. If the sales data processing device 5 was a customer and not an employee, the "Employee ID" field will either store a code indicating this or be left blank.

[0038] The transaction ID is the identification information for a transaction and is automatically assigned, for example, during the initial product registration process for that transaction. The "Date and Time" field stores the date and time (date and time) when the transaction for that record took place.

[0039] The "Transaction Amount" field stores the total price (total amount) of all items purchased in that transaction.

[0040] Here, for each combination of store ID, terminal ID, and transaction ID, there is only one transaction amount, but there is not limited to one piece of detail information; multiple pieces of detail information may be associated with it. The details information may include, for example, the following items: <Detailed Information> Product Code ·Product name ·unit price ·quantity ·price

[0041] The product code, product name, and unit price are as described above and will be omitted here. The "Quantity" field stores the quantity (number of items, weight, volume, etc.) of the product indicated by the product code purchased in the transaction for that record. The "Price" field stores the value obtained by multiplying the unit price by the quantity.

[0042] Payment methods include, for example, cash, credit card information, electronic payments, code payments, gift certificates, and vouchers. One or more payment methods are stored for each transaction ID. Amount information indicating how much of the transaction amount was paid using each payment method is also stored.

[0043] Figure 4 is a block diagram showing an example of the hardware configuration of the reading device 3 in the first embodiment. The reading device 3 includes a CPU 31, ROM 32, RAM 33, communication unit 34, display unit 35, operation unit 36, reader 37, transport unit 38, storage unit 39, etc.

[0044] The communication unit 34 is a wired or wireless communication interface that can be connected to a network such as a LAN. The communication unit 34 communicates with other devices connected via the network.

[0045] The display unit 35 has a display device such as an LED (light-emitting diode) and operates under the control of the CPU 31. The operation unit 36 ​​has an input device such as a push button and outputs the operation content input via the input device to the CPU 31.

[0046] The reader 37, for example, is equipped with an image sensor and obtains image data (image data) of the appearance of the gift certificate or exchange voucher.

[0047] The transport unit 38 is equipped with transport rollers and a motor. The motor generates a driving force that is transmitted to the transport rollers. The transport rollers rotate due to the driving force of the motor, thereby drawing the tickets inserted into the insertion / discharge port 45 into the interior and transporting them to the reader 37 or storage unit 47, or discharging them from the insertion / discharge port 45.

[0048] The CPU 31 is an example of a processor and comprehensively controls the operation of the reader 3. The ROM 32 stores various programs. The RAM 33 is a workspace for displaying programs and various data.

[0049] The CPU 31, ROM 32, and RAM 33 are connected via a bus or the like, and constitute the control unit 30 of the computer configuration. The CPU 31 operates according to the program stored in the ROM 32 or memory unit 39 and loaded into the RAM 33, causing the control unit 30 to function as various functional units and execute various processes.

[0050] The memory unit 39 has a storage medium such as an HDD or flash memory, and retains its contents even when the power is cut off. The memory unit 39 stores programs 391 that the CPU 31 can execute, as well as various setting information. For example, the program 391 includes a program for implementing the functions described later.

[0051] The storage unit 39 stores ticket data 395, etc. This data is just an example, and the storage unit 39 may store other data as well.

[0052] The ticket data 395 is a compilation of information about the ticket and is stored in the storage unit 19, for example, in the form of a data table. The items included in the data table as ticket data 395 are, for example, the following:

[0053] <Ticket Data> Ticket ID ·Recognition information ·Judgment information • Expiration information

[0054] The ticket ID is the same as previously mentioned, so its explanation will be omitted. The recognition information is information that the reader 3 uses to recognize the type and face value of the ticket, and is, for example, a reference value for the feature quantities of the ticket image, a numerical value to compare with the face value obtained by OCR reading, or a decoded value of a code symbol such as a barcode displayed on the ticket.

[0055] The judgment information is the information that the reader 3 uses to determine whether the ticket is genuine or counterfeit. The details of what this information is will be omitted. As the result of the judgment, the reader 3 returns the value "1" or the value "0" to the sales data processing device 5. The value "1" is an example of a value when the ticket is determined to be "genuine," i.e., normal. The value "0" is an example of a value when the ticket is determined to be "counterfeit," i.e., abnormal.

[0056] The expiration date information indicates the validity period of the ticket.

[0057] Figure 5 is a block diagram showing an example of the hardware configuration of the sales data processing device 5 in the first embodiment. The sales data processing device 5 includes a CPU 51, ROM 52, RAM 53, communication unit 54, display unit 55, operation unit 56, code scanner 57, imaging unit 58, deposit / withdrawal unit 59, receipt printer 60, notification unit 61, storage unit 69, etc.

[0058] The communication unit 54 is a wired or wireless communication interface that can be connected to a network such as a LAN. The communication unit 54 communicates with other devices connected via the network.

[0059] The display unit 55 has a display device such as an LCD (Liquid Crystal Display) and displays various information for the operator under the control of the CPU 51.

[0060] The operation unit 56 has a touch panel superimposed on the display surface of the display unit 55, as well as input devices such as a keyboard and a pointing device, and outputs the operation content input via the input devices to the CPU 51. The touch panel of the operation unit 56, together with the display device of the display unit 55, constitutes a touch panel display.

[0061] The code scanner 57 is, for example, a code reader or image sensor that reads (decodes) code symbols such as barcodes and two-dimensional codes. Code scanners 57 can be handheld or stationary. For example, the code scanner 57 reads a code symbol that contains coded information including a product code and obtains the product code.

[0062] The imaging unit 58 is equipped with an image sensor and obtains image data (imaging data) of the appearance of an object (for example, a product).

[0063] The deposit and withdrawal unit 59 incorporates, for example, a coin deposit and withdrawal device and a banknote deposit and withdrawal device, and accepts cash payments (settlements). The deposit and withdrawal unit 59 may also accept cashless payments such as credit card payments, electronic money payments, and code payments via information exchange using code symbols displayed on smart devices.

[0064] The receipt printer 60 issues (outputs) a paper (receipt) with the transaction details printed on it upon completion of the payment processing. The receipt has a code symbol, which is a coded representation of the receipt ID, printed on it along with the transaction details. In this embodiment, the receipt ID is assumed to be the same as the transaction ID. Note that both the receipt ID and the code symbol, which is a coded representation of the receipt ID, are examples of identifiers.

[0065] The notification unit 61 specifically consists of sound-emitting devices such as buzzers and speakers, and light-emitting devices such as LEDs (light-emitting diodes), and operates under the control of the CPU 51.

[0066] The CPU 51 is an example of a processor and comprehensively controls the operation of the sales data processing device 5. The ROM 52 stores various programs. The RAM 53 is a workspace for displaying programs and various data.

[0067] The CPU 51, ROM 52, and RAM 53 are connected via a bus or the like, and constitute the control unit 50 of the computer configuration. The CPU 51 operates according to the program stored in the ROM 52 or memory unit 69 and loaded into the RAM 53, causing the control unit 50 to function as various functional units and execute various processes.

[0068] The memory unit 69 has a storage medium such as an HDD or flash memory, and retains its contents even when the power is cut off. The memory unit 69 stores programs 691 that the CPU 51 can execute, as well as various setting information. For example, program 691 includes programs for implementing functions described later.

[0069] The memory unit 69 stores registration information 697, etc. Since the registration information 697 is the source information for transaction information 197, the data structure is in the same format as transaction information 197, so a detailed explanation is omitted.

[0070] The data stored in the memory unit 69 is just an example, and the memory unit 69 may store other data as well.

[0071] For example, the storage unit 69 may store a product master or a ticket master. In this case, if the sales data processing device 5 is unable to communicate with the server 1 when it needs to access, for example, the product master 193 or the ticket master 195, it can access the product master or ticket master stored in its own storage unit 69. In this case, the sales data processing device 5 updates the product master or ticket master stored in the storage unit 69 based on information received from a higher-level device (for example, the server 1). This update is performed at predetermined times, such as after closing or before opening.

[0072] <Function> Figure 6 is a block diagram showing an example of the functional configuration in the first embodiment. The control unit 50 has the functions of a registration processing unit 501, a settlement processing unit 502, and a printing processing unit 503. The control unit 30 has the functions of a reading processing unit 301 and a determination processing unit 302. The control unit 10 has the function of an update processing unit 101.

[0073] The registration processing unit 501 performs registration processing based on the operation of the sales data processing unit 5. More specifically, the registration processing unit 501 obtains the product code, for example, via the code scanner 57 or the operation unit 56. Alternatively, the registration processing unit 501 calculates the feature quantities from the product images included in the captured image based on the imaging data output by the imaging unit 58, compares them with the matching data in the product master 193, and obtains the product code.

[0074] Next, the registration processing unit 501 retrieves product information corresponding to the acquired product code from the product master 193. The registration processing unit 501 then stores (registers) the acquired product information as registration information 697 in the storage unit 69. The registration processing unit 501 transmits the registration information 697 to the server 1 at a predetermined timing.

[0075] The update processing unit 101 is an example of a recording processing unit that performs processing to record information related to transactions for which settlement has been completed. The update processing unit 101 stores the registration information 697 received by the server 1 as transaction information 197 in the storage unit 19. Furthermore, when the update processing unit 101 receives information on a transaction that has been settled by the settlement processing unit 502, it updates the transaction information 197.

[0076] The reading processing unit 301 and the determination processing unit 302 operate when the reading device 3 receives instructions from the sales data processing device 5. The reading processing unit 301 reads the information shown on the surface of gift certificates, exchange vouchers, etc., and recognizes the type and face value of the voucher by comparing the read information with the recognition information in the voucher data 395. The determination processing unit 302 determines the authenticity of the voucher based on the information shown on the surface of gift certificates, exchange vouchers, etc. A detailed explanation of the specific processes performed by the reading processing unit 301 and the determination processing unit 302 will be omitted here, as existing technology will be used, but for example, they perform the following processes.

[0077] The reading processing unit 301 acquires data (image data) of the ticket surface image from the reader 37 and recognizes the ticket based on the image data. For example, the reading processing unit 301 compares the feature quantities of the acquired ticket surface image data with the reference values ​​of each ticket and selects those with high similarity. The reading processing unit 301 also recognizes the face value (the amount displayed on the ticket surface) using, for example, OCR (Optical Character Recognition) technology.

[0078] The settlement processing unit 502 performs settlement processing based on the operation of the operator of the sales data processing unit 5. More specifically, the settlement processing unit 502 accepts deposits to the deposit / withdrawal unit 59 and dispenses change from the deposit / withdrawal unit 59. Alternatively, the settlement processing unit 502 acquires electronic payment information (e.g., credit card information or payment code) presented by the customer and performs settlement processing using that information.

[0079] Furthermore, when vouchers such as gift certificates or exchange vouchers are used for payment, the payment processing unit 502 responds accordingly and, if the information of the voucher corresponding to the reading result of the reader 3 exists in the voucher master 195, it performs payment processing using the voucher. For example, prior to payment processing, the payment processing unit 502 presents options for payment methods and accepts the selection. The options include, for example, cash, credit card information, electronic payment, code payment, gift certificates, and exchange vouchers. The payment processing unit 502 performs payment processing according to the option selected by the operator.

[0080] The settlement processing unit 502 updates the "payment method and amount information" field in the registration information 697 upon completion of the settlement. This update is reflected in the transaction information 197 by the update processing unit 101 of server 1.

[0081] When the sales data processing device 5 receives ticket information from the reader 3, the payment processing unit 502 performs payment processing according to the type of ticket, etc.

[0082] If the voucher is a gift certificate (cash voucher), the settlement processing unit 502 processes it in the same way as if cash equivalent to the face value of the voucher had been deposited. In other words, the settlement processing unit 502 treats the gift certificate at its face value.

[0083] If the voucher is an exchange voucher, it cannot be processed in the same way as cash, like a monetary voucher, so it requires a different processing method. There are two typical ways to process vouchers when they are exchange vouchers, which are described below as the first and second processes. The settlement processing unit 502 performs either the first or second process below when the voucher is an exchange voucher.

[0084] In the first process, the settlement processing unit 502 confirms the selling price of the target product using the product master 193 and deducts the selling price from the payment. In the second process, the settlement processing unit 502 confirms the selling price of the target product using the product master 193 and treats the exchange voucher as a monetary voucher for the selling price.

[0085] The settlement processing unit 502 determines whether to perform the first or second process according to the processing type setting stored in the ticket master 195 in association with the ticket ID.

[0086] Note that both the first and second processes are executed only if the product eligible for the exchange voucher exists in the registration information 697. If the product eligible for the exchange voucher does not exist in the registration information 697, the settlement processing unit 502 will notify the system of the error via the notification unit 61. Furthermore, in the case of exchange vouchers, there may be multiple eligible products listed in the registration information 697. In that case, the payment processing unit 502 will apply the exchange vouchers to the eligible products in order of price, starting with the most expensive (highest price first), in order to benefit the customer.

[0087] The settlement processing unit 502 instructs the reader 3 to start and complete the reading process. Furthermore, each time the settlement processing unit 502 receives a reading result from the reader 3, it displays information corresponding to the reading result on the display unit 55 of the sales data processing device 5. Additionally, if the reading result received from the reader 3 indicates an error, the settlement processing unit 502 instructs the reader 3 to eject the ticket.

[0088] The printing unit 503 causes the receipt printer 60 to print a receipt.

[0089] Figure 7 is a sequence diagram schematically showing an example of the payment processing flow in the first embodiment. Figures 8 to 13 are examples of screens displayed by the display unit 55 of the sales data processing device 5 in the first embodiment. Although screens 71 to 76 shown in Figures 8 to 13 are for the case where the sales data processing device 5 is a self-checkout device, similar screens are used for POS terminals and accounting machines.

[0090] The screen 71 shown in Figure 8 is the screen displayed by the display unit 55 of the sales data processing device 5 when processing by the settlement processing unit 502 begins. The screen 71 includes text 711, 712, operators 713 to 716, display fields 717, etc.

[0091] Text 711 is displayed at the top of screen 71 and is, for example, "You can pay with the following card." Text 712 is displayed in the center of screen 71 and explains the operation required of the operator by screen 71, for example, "Please select your payment method." Display field 717 displays the amount to be paid, i.e., the price of the goods.

[0092] Operator 713 accepts an operation declaring payment in cash. Operator 714 accepts an operation declaring payment by credit card. Operator 715 accepts an operation declaring payment by debit card. Operator 716 accepts an operation declaring payment by voucher or other form of payment.

[0093] When the operator 716 receives an operation on screen 71 (step S1), and the operation unit 56 transmits this information to the control unit 50, the settlement processing unit 502 transitions the display on the display unit 55 to screen 72 (see Figure 9) and sends a command to the reader 3 to read the ticket (step S2).

[0094] The screen 72 shown in Figure 9 includes text 721, an image 722, and an operator 729. The text 721 is displayed at the top and explains the operation required of the operator by the screen 72, for example, "Please insert the gift certificate into the reader." The image 722 shows the process of inserting the certificate into the reader 3. This image 722 is intended to help the operator intuitively understand the operation required of the sales data processing device 5. The operator 729 accepts an operation to return to screen 71.

[0095] When the reading device 3 receives a command from the sales data processing device 5, it performs a reading process and a determination process (step S3), and transmits the result to the sales data processing device 5 (step S4).

[0096] In step S3, the reading processing unit 301 operates the transport unit 38 and the reader 37 to pull the sheet-like medium inserted by the operator through the insertion / discharge port 45 into the housing and obtain image data of the ticket surface. Furthermore, the reading processing unit 301 calculates the feature quantities of the image data and compares them with reference values ​​to obtain the ticket ID of the ticket that is most likely to match the medium.

[0097] Furthermore, in step S3, the determination processing unit 302 determines whether the sheet-shaped medium is genuine as a ticket based on the information obtained from the sheet-shaped medium (such as the image data mentioned above). If the determination processing unit 302 determines that the medium is "genuine," i.e., normal, as a ticket, in step S4 it transmits the ticket ID, expiration information, and authenticity information (value "1") to the sales data processing unit 5 as the ticket recognition result. If the determination processing unit 302 determines that the medium is "fake," i.e., abnormal, in step S4 it transmits authenticity information (value "0") without the ticket ID and expiration information to the sales data processing unit 5 as the ticket recognition result.

[0098] When the sales data processing device 5 receives the result from the reading device 3, the settlement processing device 502 executes steps S5 to S7 if the authenticity information is value "1" and the expiration information is on or after the current date and time.

[0099] In other words, the settlement processing unit 502 sends a request to the server 1 to retrieve information about the ticket indicated by the ticket ID (step S5). The control unit 10 of the server 1, upon receiving the retrieval request, reads the information of the ticket corresponding to the ticket ID from the ticket master 195 and provides it as a response to the request. Subsequently, the settlement processing unit 502 retrieves the information provided by the server 1 as a response to the request (step S6).

[0100] Furthermore, if the voucher is an exchange voucher, the settlement processing unit 502 matches the voucher information received from the server 1 with the registration information 697 (step S7). In other words, the settlement processing unit 502 determines whether the product (target product) that is the exchange target for the exchange voucher read by the reader 3 exists in the registration information 697, and if multiple products exist, it applies them in order of highest selling price.

[0101] The settlement processing unit 502 then displays screen 73 (see Figure 10) on the display unit 55 (step S8). Screen 73 is displayed as a pop-up window overlaid on screen 72. The contents of screen 73 are updated each time from step S6 or S7 to step S8.

[0102] The settlement processing unit 502 sends a storage instruction to the reader 3 in conjunction with the update of the screen 73 (step S9). Upon receiving the storage instruction, the reader 3 stores the ticket in the storage unit 47 (step S10) and sends a reply to the sales data processing unit 5 to that effect (step S11).

[0103] The screen 73 shown in Figure 10 includes a list 731, a total amount 732, an operator 739, etc. The list 731 displays information on tickets that have been determined to be "true" by the reader 3. In the example in Figure 10, the list 731 displays the ticket name, ticket type, and face value. In Figure 10, "Type" refers to the ticket type, "Exchange" refers to an exchange voucher, and "Gift" refers to a gift certificate.

[0104] The total amount of 732 is the sum of the face values ​​of the gift certificates displayed in list 731.

[0105] Until the operator 739 for the "Complete" button on screen 73 is operated, the reader 3 waits for the next ticket to be inserted, and each time a ticket is inserted, the control units 50, 30, and 10 repeat steps S3 to S11.

[0106] When the operator 739 receives an operation (step S12), the settlement processing unit 502 closes the screen 73, returns the display on the display unit 55 to the screen 71, and executes the settlement process using the voucher (step S13). In the settlement process, as described above, if the voucher is a gift certificate, it is processed in the same way as a cash deposit of its face value, and if the voucher is an exchange voucher, it is processed as a discount equal to the selling price of the target product or as a payment of a monetary voucher equal to the selling price.

[0107] Once the payment processing is complete, the payment processing unit 502 sends a completion notification to the server 1 (step S14). Upon receiving the completion notification, the update processing unit 101 of the server 1 updates the transaction information 197 (step S15).

[0108] If the expiration information received in step S4 is in the past than the current date and time, or if the authenticity information is value "0", the settlement processing unit 502 will display an error notification screen 74 (see Figure 11) on the display unit 55 in step S8.

[0109] Screen 74 is also displayed when a ticket is valid as a ticket and within its expiration date, but is not handled by the store (store handling information is "0"), or when it is not recognized as a ticket in the ticket master 195.

[0110] The screen 74 shown in Figure 11 includes text 741, 742 and an operator 749. Text 741 is displayed at the top of the screen 74 and is, for example, "This cannot be processed." Text 742 is displayed in the center of the screen 74 and explains what the screen 74 wants to convey to the operator, for example, "We are sorry, but this gift certificate cannot be processed. Please press the OK button and insert another gift certificate." Operator 749 is the "OK button" in the example of text 742.

[0111] When the operator 749 receives an operation, the settlement processing unit 502 closes the error notification screen 74 and returns the display on the display unit 55 to screen 73, and in step S9, sends an ejection instruction to the reader 3. When the reader 3 receives the ejection instruction, it ejects the ticket from the insertion / discharge opening 45 (step S10) and sends a reply to the sales data processing unit 5 to that effect (step S11).

[0112] If, in step S7, the matching process finds that the product to be redeemed for the voucher is not registered in the registration information 697, the payment processing unit 502 will display an error notification screen 75 (see Figure 12) on the display unit 55 in step S8.

[0113] The screen 75 shown in Figure 12 includes text 741, 752 and an operator 749. Since text 741 and operator 749 are as described above, their explanation is omitted. The text 752 is displayed in the center of screen 75 and explains what the screen 75 wants to convey to the operator, for example, "We apologize, but the item you selected is not registered. Please press the OK button and insert another gift certificate."

[0114] When the operator 749 is operated on screen 75, the settlement processing unit 502 performs the same processing as when the operator 749 on screen 74 is operated. That is, the settlement processing unit 502 closes screen 75 which notifies of the error, returns the display on the display unit 55 to screen 73, and in step S9, sends an ejection instruction to the reader 3. When the reader 3 receives the ejection instruction, it ejects the ticket from the insertion / discharge opening 45 (step S10) and sends a reply to the sales data processing unit 5 to that effect (step S11).

[0115] The screen 76 shown in Figure 13 is another example of the screen 73 in Figure 10. Screen 76 includes a list 731, the amount of the gift certificate 762, the total amount 763, the remaining balance 764, the operator 739, etc.

[0116] In this case, when payment is made using an exchange voucher, the payment processing unit 502 performs either the first or second process as described above. The first process is to deduct the selling price of the product to which the exchange voucher applies. The second process is to treat the exchange voucher as a monetary voucher for the selling price of the product to which the exchange voucher applies.

[0117] Screen 73 in Figure 10 is the screen for the first process of the former, and screen 76 in Figure 13 is the screen for the second process of the latter. Therefore, in the list table 731 on screen 76, exchange ticket No. 1 is displayed as a monetary voucher equivalent to the selling price of the target product.

[0118] The total amount of 763 is the sum of the selling prices of the products registered in registration information 697. The voucher amount of 762 corresponds to the total amount of 732 on screen 73 and is the sum of the amounts displayed in list 731. The remaining amount of 764 is the total amount of 763 minus the voucher amount of 762.

[0119] If the remaining balance 764 is 1 yen or more, when the operator 739 receives an operation, screen 71 is displayed after screen 76 (or screen 73) is closed, and the user is asked to select a method for paying the remaining balance 764.

[0120] In this configuration, when the operator of the sales data processing device 5 uses vouchers such as gift certificates or exchange vouchers as a means of payment, they can have the reader 3 read the vouchers and automatically determine whether the vouchers are valid or invalid.

[0121] Furthermore, sales data can be recorded even when the voucher is an exchange voucher. More specifically, even items exchanged for exchange vouchers, which were previously handled manually by store staff and not recorded in the history, can now be recorded in transaction information 197. This eliminates the inconvenience of items exchanged for exchange vouchers being omitted from statistical data.

[0122] This configuration is preferable because, if the operator is the customer, there is no need to call a store employee and wait. Furthermore, even if the operator is unfamiliar with the tickets, there is no need to consult with an employee who is knowledgeable about them.

[0123] Furthermore, with this configuration, the reader 3 only needs to store data on gift certificates and vouchers that are commonly available in the market, and does not need to individually store data or settings tailored to the store's product handling situation.

[0124] In the above embodiment, the server 1 has the product master 193 and the ticket master 195, but in implementation, this is not limited to this configuration. For example, the server 1 may not exist, and the storage unit 69 of the sales data processing device 5 may be configured to store the product master and the ticket master.

[0125] Furthermore, while the above embodiment described the use of gift certificates (vouchers) and exchange vouchers such as beer vouchers and rice vouchers that are available on the market, the vouchers used in the implementation are not limited to those commonly found on the market. For example, coupon vouchers issued individually by stores may also be used as the vouchers in the above embodiment.

[0126] Furthermore, although the above embodiment describes a device and system that handles both gift certificates and exchange vouchers, in practice, the sales data processing device 5 and the sales data processing system may be a device and system that handles at least one of gift certificates or exchange vouchers, that is, a device and system that does not handle either gift certificates or exchange vouchers.

[0127] Furthermore, although the above embodiment described a sales data processing device 5 equipped with a registration processing unit 501 as an example, in practice, the sales data processing device 5 may not be equipped with a registration processing unit 501. An example of a sales data processing device 5 that does not have a registration processing unit 501 is the accounting machine described above. The accounting machine is a sales data processing device 5 that does not have a registration processing unit 501 but is equipped with a settlement processing unit 502.

[0128] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, several modifications of the embodiments described above will be described below as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and the same reference numerals will be used for parts that are common with the content already described, and detailed explanations will be omitted. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.

[0129] (Second Embodiment) This embodiment is a modification of the first embodiment. In this embodiment, in step S4, the reader 3 outputs to the sales data processing device 5 the recognition result along with the image data of the ticket surface for any ticket it determines to be true. In this case, in step S8, the sales data processing device 5 displays a screen (see Figure 14, described later) on the display unit 55 that includes the ticket surface image based on the image data input from the reader 3.

[0130] Figure 14 shows an example of a screen 77 displayed by the display unit 55 of the sales data processing device 5 in the second embodiment. Note that the screen 77 shown in Figure 14 is an example where the sales data processing device 5 is a self-checkout device.

[0131] Screen 77 is a modified version of Screen 73 shown in Figure 10, and is an example of a ticket confirmation screen that displays the ticket read by the reader 3 in a verifiable manner. Screen 77 includes a ticket image 771 and an operator 779. The ticket image 771 shows the ticket face (appearance) of the most recent ticket, such as a gift certificate, that the reader 3 has read and determined to be genuine. The operator 779 accepts an operation to call a store employee. When the operator 779 receives an operation, the sales data processing device 5 transmits a signal to a predetermined device (such as a terminal device used by the store employee or an indicator light it has installed) to call a store employee.

[0132] According to this embodiment, the operator of the sales data processing device 5 can confirm the appearance of the ticket most recently read by the reader 3 by referring to the ticket image 771.

[0133] In the example shown in Figure 14, although the face value shown in the ticket image 771 is 5,000 yen, the amount shown in the list 731 and the total amount 732 is 1,000 yen. This indicates that the reader 3 may have misread the face value. In such a case, the customer, who is the operator, can press the control button 779 to call a store employee or call out to a nearby employee for assistance.

[0134] (Third embodiment) This embodiment is a modification of the second embodiment. In step S4, the reader 3 of this embodiment outputs to the sales data processing device 5 the recognition result and image data of the ticket surface, along with the information read from the image data of the ticket surface (read information), for tickets that it has determined to be true. Here, the information to be read includes, for example, the feature quantities of the ticket image, numerical values ​​obtained through OCR reading (such as face value and serial number), and the decoded values ​​of code symbols such as barcodes displayed on the ticket. The above-mentioned ticket recognition results, ticket image data, and reading information are collectively referred to as "ticket information" below.

[0135] When the sales data processing device 5 receives the ticket information, the settlement processing device 502 associates each piece of information constituting the ticket information with each other and stores it in a predetermined storage area of ​​the storage unit 69. Furthermore, the settlement processing unit 502 includes identification information (e.g., file name) of the image data of the ticket surface stored in the storage unit 69 in the registration information 697.

[0136] The registration information 697 of this embodiment further includes, in addition to that of the second embodiment (which is the same as that of the first embodiment), identification information of the image data of the ticket surface stored in the storage unit 69. The same applies to the transaction information 197 that corresponds to the registration information 697. In other words, the items included in the registration information 697 and transaction information 197 of this embodiment are, for example, the following: Store ID • Device ID • Employee ID Transaction ID · Date and time • Detailed information • Transaction amount • Payment method and amount information • Identification information of the image data on the ticket

[0137] The identification information of the image data on the ticket surface is recorded when the ticket is used as a means of payment in a transaction. The identification information of the image data on the ticket surface (e.g., file name) shall not overlap with the identification information of the image data on the ticket surface acquired by other sales data processing devices 5.

[0138] In this embodiment, the settlement processing unit 502 includes identification information (e.g., file name) of the image data of the ticket stored in the storage unit 69 in the information sent to the server 1 in step S14. As a result, information about the ticket used for settlement remains in the transaction information 197, similar to the registration information 697.

[0139] Figure 15 shows an example of a screen 81 displayed by the display unit 55 of the sales data processing device 5 in the third embodiment. Although the screen 81 shown in Figure 15 is an example where the sales data processing device 5 in this embodiment is a POS terminal, a similar screen may be displayed in other sales data processing devices 5 as well.

[0140] Screen 81 is displayed as a pop-up window overlaid on the registration screen 80.

[0141] The registration screen 80 is a screen displayed on the display unit 55 during the execution of the registration process for registering product information, and displays a list of registered product information. The registration screen 80 also includes operators 801 and 805. When operator 801 is operated, the search processing unit of the sales data processing device 5 displays screen 81. When operator 805 is operated, the search processing unit of the sales data processing device 5 displays a screen for searching electronic journals.

[0142] Screen 81 is an example of a ticket confirmation screen that displays the ticket read by the reader 3 for verification. Screen 81 includes a ticket image display area 810, a ticket image 811, ticket supplementary information 812, and operators 817, 818, 819, etc.

[0143] The ticket image display area 810 is the area where the ticket image 811 is displayed. The screen 81 displays the ticket image 811 as an image based on the ticket image data that the sales data processing device 5 most recently received in step S4 and stored in the storage unit 69. The ticket accompanying information 812 includes information indicating the date and time when the image data corresponding to the ticket image 811 was stored in the storage unit 69, and identification information of the image data (e.g., file name).

[0144] Operators 817 and 818 accept operations to change (transition) the currently displayed ticket image 811. When operator 817 is operated, the search processing unit of the sales data processing device 5 displays an image based on the image data stored in the storage unit 69 immediately before the image data that forms the basis of the currently displayed ticket image 811 as the ticket image 811. Similarly, when operator 818 is operated, the sales data processing device 5 displays an image based on the image data stored in the storage unit 69 immediately after the image data that forms the basis of the currently displayed ticket image 811 as the ticket image 811. The sequence of images can be determined by the timestamp of the image data (information indicating the date and time stored in the storage unit 69).

[0145] When the operator 819 receives an operation, the sales data processing device 5 closes the screen 81 and returns the display on the display unit 55 to the registration screen 80.

[0146] In this configuration, if the operator of the sales data processing device 5 needs to reconfirm the ticket read by the reader 3 after the operator 739 has been operated, they operate the operator 801 on the registration screen 80 to display screen 81. In addition, the operator can change the ticket image 811 displayed in the ticket image display field 810 by operating the operators 817 and 818 as needed.

[0147] In this embodiment, the case where the sales data processing device 5 is a POS terminal was described as an example, but the implementation is not limited to this, and the configuration of this embodiment may be applied to cases where the sales data processing device 5 is, for example, a self-checkout device.

[0148] (Fourth Embodiment) This embodiment is a modification of the third embodiment. In this embodiment, when the settlement processing unit 502 transmits information to the server 1 in step S14, it also transmits the "ticket information" which includes image data of the ticket surface. The server 1 stores the received ticket information in a predetermined storage area of ​​the storage unit 19, associating each piece of information constituting the ticket information with each other.

[0149] Furthermore, the control unit 50 of the sales data processing device 5 in this embodiment also has the function of a search processing unit. The search processing unit receives input of search conditions, searches for information that matches the received conditions from the transaction information 197, and displays it.

[0150] Figures 16 to 18 show examples of screens 85 displayed by the display unit 55 of the sales data processing device 5 in the fourth embodiment. Although the screens 85 shown in Figures 16 to 18 are examples when the sales data processing device 5 is a POS terminal, similar screens may be displayed in other sales data processing devices 5 as well.

[0151] Screen 85 is for searching electronic journals. This screen is displayed when the operator 805 is operated on the registration screen 80 shown in Figure 15.

[0152] Screen 85 includes a search criteria field 851, an operator 852, a search results field 853, a journal log field 854, and operators 855 to 859. When operator 859 is operated, the search processing unit of the sales data processing device 5 closes screen 85 and returns the display contents of the display unit 55 to the registration screen 80.

[0153] Search criteria field 851 is a field for entering search criteria. Examples of search criteria include register number (No.), date, transaction terms, responsible person, transaction number, time, and any arbitrary string.

[0154] The register number is the terminal ID of the sales data processing device 5. The transaction number is the transaction ID. The person in charge is the operator's identification information, for example, the employee ID. The date, time, and transaction number can be specified within a range. Transaction conditions can be specified, for example, all transactions, returns, register minus, etc.

[0155] When the operator 852 receives an operation, the search processing unit of the sales data processing device 5 retrieves metadata of records that match the conditions specified in the search condition field 851 from the transaction information 197 (or registration information 697) and displays them in a list in the search results field 853 (see Figure 17). Here, the above metadata (also called supplementary information, attribute information, or related information) includes, for example, the date and time, transaction number, transaction conditions, and responsible person. In addition to this metadata, details information, transaction amount, payment method, and amount information are referred to below as the main body of the record information.

[0156] The search results field 853 displays a list of metadata for transaction information 197 (or registration information 697) records that match the conditions specified in the search criteria field 851. When the search results field 853 accepts an operation to select any row, the search processing unit of the sales data processing device 5 retrieves the entire information of the selected record from the transaction information 197 (or registration information 697) and displays it in the journal log field 854 (see Figure 18).

[0157] If the record of information to be displayed in the journal log column 854 includes identification information (e.g., file name) of the image data of the ticket, the search processing unit of the sales data processing device 5 retrieves the image data indicated by the identification information from the storage unit 19 (or storage unit 69), and also displays the ticket image 860 based on that image data in the journal log column 854.

[0158] When operator 855 is operated, the search processing unit of the sales data processing device 5 moves (scrolls) the contents of the journal log field 854 downwards to display the contents above the current display range. When operator 856 is operated, the search processing unit of the sales data processing device 5 moves the contents of the journal log field 854 upwards to display the contents below the current display range. When operator 857 is operated, the search processing unit of the sales data processing device 5 switches the contents of the journal log field 854 to the contents above the current display range. When operator 858 is operated, the search processing unit of the sales data processing device 5 switches the contents of the journal log field 854 to the contents below the current display range.

[0159] With this configuration, the operator of the sales data processing device 5 can, if a voucher or exchange voucher was used to settle a transaction shown in the displayed journal log, confirm not only the type, number, and amount of the voucher, but also the voucher image 860.

[0160] (Fifth embodiment) Figure 19 shows an example of a screen 87 displayed by a display device connected to the server 1 in the fifth embodiment. Screen 87 is the screen corresponding to screen 85 and is a screen for searching electronic journals.

[0161] The server 1 of this embodiment includes a display unit and an operation unit. The display unit has a display device such as an LCD and displays various information for the operator under the control of the CPU 11. The operation unit has a touch panel superimposed on the display surface of the display unit, as well as input devices such as a keyboard and a pointing device, and outputs the operation content entered via the input devices to the CPU 11. The touch panel of the operation unit, together with the display device of the display unit, constitutes a touch panel display.

[0162] Screen 87 includes a search criteria field 871, a search results field 873, a journal log field 874, and operators 872, 875, 876, and 879. The search criteria field 871, the search results field 873, and the journal log field 874 correspond to the search criteria field 851, the search results field 853, and the journal log field 854 in the fourth embodiment, so a detailed explanation is omitted. Similarly, the operators 872, 875, 876, and 879 correspond to the operators 852, 855, 856, and 859 in the fourth embodiment, so a detailed explanation is omitted.

[0163] In this configuration, when checking an electronic journal on Server 1 (store controller) located in the back office, the operator enters conditions in the search conditions field 871 and operates the operator 872 to select one of the records displayed in the search results field 873. Server 1 then displays the entire information of the selected record in the journal log field 874.

[0164] If the record of information to be displayed in journal log column 874 includes identification information (e.g., file name) of the image data on the ticket, server 1 will also display the ticket image 860 in journal log column 874 based on the image data indicated by the identification information.

[0165] With this configuration, if a voucher or exchange coupon was used to settle a transaction shown in the displayed journal log, it is possible to check not only the type, number, and amount of the voucher, but also the voucher image 860.

[0166] The programs executed by each device in the above-described embodiments are provided pre-installed in ROM or the like. The programs executed by each device in the above-described embodiments may also be provided as files in an installable or executable format, recorded on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk).

[0167] Furthermore, the programs executed by each of the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Alternatively, the programs executed by each of the above-described embodiments may be provided or distributed via a network such as the Internet.

[0168] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, modifications, and combinations are possible without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [Explanation of symbols]

[0169] 1...Server, 10...Control unit, 101...Update processing unit (an example of a recording processing unit), 11...CPU, 12...ROM, 13...RAM, 14...Communication section, 19...Storage section, 191...Program, 193...Product Master, 197...Transaction Information 195... Ticket Master (Example of Master Information), 3...Reading device, 30...Control unit, 301...Reading processing unit, 302...Determination processing unit, 31...CPU, 32...ROM, 33...RAM, 34...Communication section, 35...Display unit, 36...Operation unit, 37...Reader, 38...Transport unit, 39...Memory unit, 391...Program, 395...Ticket data, 41...Main body, 42...Lid, 43...Hinge 45...Insertion / extraction port, 46...Support part, 47...Storage part, 5. Sales data processing device, 50...Control unit, 501...Registration processing unit, 502...Settlement processing unit, 503...Printing processing unit, 51...CPU, 52...ROM, 53...RAM, 54...Communication section, 55...Display unit, 56...Operation unit, 57...Code scanner, 58...Imaging unit, 59... Deposit and withdrawal department, 60... Receipt printer, 61... News department, 69...Memory unit, 691...Program, 697...Registration information, 71...screen, 711,712...text, 713~716...operators, 717...display field, 72...screen, 721...text, 722...image, 729...operator 73...Screen, 731...List, 732...Total Amount, 739...Operator 74...Screen, 741,742...Text, 749...Controller, 75...screen, 752...text, 76...Screen, 762...Gift amount, 763...Total amount, 764...Remaining balance 77...screen, 771...ticket image, 779...operator 80...Registration screen, 801, 805...Operator, 81...Screen, 810...Ticket image display area, 811...Ticket image, 812...Ticket supplementary information, 817, 818, 819... Operators, 85...Screen, 851...Search criteria field, 852...Operator, 853...Search results section, 854...Journal log section, 855-859...Operator, 860...Ticket image, 87...Screen, 871...Search criteria field, 872...Operator, 873... Search results column, 874... Journal log column, 875, 876, 879... Operators. [Prior art documents] [Patent Documents]

[0170] [Patent Document 1] Japanese Patent Publication No. 2023-136760

Claims

1. Master information that stores information about vouchers, which are sheet-like media used for payment processing, A reader that reads information from the aforementioned ticket, A settlement processing unit performs settlement processing using the ticket if the information of the ticket corresponding to the reading result of the reader device exists in the master information, A sales data processing system equipped with the following features.

2. The aforementioned voucher is at least one of the following: a gift certificate used as a monetary voucher equivalent to its face value, or an exchange voucher that can be exchanged for the target product. The sales data processing system according to claim 1.

3. The master information includes information specifying, as information on the exchange voucher, whether to deduct the selling price of the target product or to treat it as a voucher for the selling price in the settlement process using the voucher, The settlement processing unit performs settlement processing using the voucher in accordance with the settings of the master information. The sales data processing system according to claim 2.

4. The system further includes a recording processing unit that performs processing to record information relating to the transaction for which the settlement process has been completed. The reading device outputs image data of the appearance of the ticket and information read from the ticket. When the voucher is used in the settlement process, the recording processing unit records the image data of the voucher in association with the information relating to the transaction. The sales data processing system according to claim 1.

5. The settlement processing unit is provided in a sales data processing unit that cooperates with the reading device, The settlement processing unit instructs the reading device to start and complete the reading process. The payment processing unit, each time it receives a reading result from the reader, displays information corresponding to the reading result on the display device provided by the sales data processing unit. The sales data processing system according to claim 1.

6. If the reading result received from the reader indicates an error, the payment processing unit instructs the reader to eject the ticket. The sales data processing system according to claim 4.

Images