POS system, commodity sales data processing apparatus, and program thereof
The integration of a product sales data processing device and program addresses the issue of inaccurate sales data aggregation by comparing and correcting transaction data from POS and mobile payment systems, ensuring real-time accuracy and precision in sales reporting.
Patent Information
- Application Number
- JP2023086501
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-25
- Publication Date
- 2024-12-05
- Estimated Expiration
- 2043-05-25
AI Technical Summary
When a POS system is used in conjunction with a mobile payment system, the product sales data from transactions settled via the mobile payment system are not aggregated in real time by the POS server, leading to potential inaccuracies in sales data due to price differences caused by time-limited discounts.
A product sales data processing device and program that includes monitoring, data acquisition, processing, and output means to accurately integrate and compare transaction data from both systems, ensuring real-time aggregation and correction of sales data.
Enables accurate and timely aggregation of sales data from both POS and mobile payment systems, correcting for price discrepancies due to time-limited discounts, thereby ensuring precise sales data reporting.
Smart Images

Figure 2024169216000001_ABST
Abstract
Description
[Technical field]
[0001] An embodiment of the present invention relates to a POS system, a product sales data processing device, and a program therefor. [Background technology]
[0002] In recent years, mobile payment systems have been developed that allow customers to operate their own mobile terminals to complete the entire process from registering purchased items to making payments, and these systems are already in use in supermarkets and other places. By introducing mobile payment systems, stores can alleviate congestion at the cash register. They can also reduce the number of accounting staff, which helps to cut labor costs. On the other hand, there are many customers who do not want to use mobile payment systems. For this reason, it is common to introduce mobile payment systems while retaining the existing POS (Point Of Sales) payment system.
[0003] The POS system has the advantage that the sales data of the store at the time of the sale of the product is always known because the POS server compiles the product sales data of the commercial transactions settled at each POS terminal in real time. However, when the POS system and the mobile payment system are used together, the sales data of the commercial transactions settled with the mobile payment system is not compiled by the POS server, so it takes time to grasp the sales of the store with the POS system.
[0004] Therefore, the system is configured so that each time a transaction is settled using the mobile payment system, the POS terminal retrieves data related to the purchased item, and the POS server compiles the product sales data of the transaction based on that data. With this configuration, the product sales data of transactions settled using the mobile payment system is also compiled in the POS server in near real time, making it possible to grasp the store's sales through the POS system.
[0005] However, when a limited-time discount sale is implemented, such as a limited-time sale, a difference may occur between the price of the purchased product at the time the payment is made through the mobile payment system and the price of the purchased product at the time the POS terminal retrieves the data from the mobile payment system. When a difference occurs, the sales calculated from the product sales data compiled by the POS server may not necessarily be accurate. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] Special Publication No. 2013-541107 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 a product sales data processing device and its program, and a POS system, that can accurately grasp the sales of a store that uses both a POS system and a mobile payment system. [Means for solving the problem]
[0008] In one embodiment, the product sales data processing device includes a monitoring means, a first acquisition means, a second acquisition means, a processing means, a calculation means, and an output means. The monitoring means monitors the settlement of a commercial transaction with a purchaser on the basis of data input via a mobile terminal operated by the purchaser. The first acquisition means acquires data related to purchased items in the commercial transaction settled with the mobile payment system. The second acquisition means acquires a total amount of the commercial transaction calculated at the time the commercial transaction is settled with the mobile payment system. The processing means processes product sales data of the commercial transaction settled with the mobile payment system based on the data related to the purchased items acquired by the first acquisition means. The calculation means calculates the total amount of the commercial transaction based on the product sales data processed by the processing means. The output means outputs the difference between the total amount acquired by the second acquisition means and the total amount calculated by the calculation means. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a schematic diagram showing the general configuration of a store system established in a store that uses both a POS system and a mobile payment system. [Diagram 2] FIG. 2 is a schematic diagram showing the data structure of a product record stored in the product master. [Diagram 3] FIG. 3 is a schematic diagram showing the data structure of the discount table. [Figure 4] FIG. 4 is a schematic diagram showing main data described in a transaction file held by the mobile server. [Diagram 5] FIG. 5 is a block diagram showing the main circuit configuration of the POS terminal. [Figure 6] FIG. 6 is a schematic diagram showing main data written in a transaction file held by a POS terminal. [Figure 7] FIG. 7 is a schematic diagram showing the main functional configuration of the processor of the POS terminal. [Figure 8] FIG. 8 is a flowchart showing the procedure of information processing executed by the mobile server in cooperation with the mobile terminal. [Figure 9] FIG. 9 is a flow chart showing the main information processing steps executed by the processor of the POS terminal. [Figure 10] FIG. 10 is a flowchart showing the procedure of information processing executed by the mobile server in cooperation with the POS terminal. [Figure 11] FIG. 11 is a flowchart showing a specific procedure of the sales integration process in FIG. [Figure 12] FIG. 12 is a flowchart showing a specific procedure of the sales integration process in FIG. [Figure 13] FIG. 13 is a diagram showing an example of a journal recorded in an electronic journal for a commercial transaction in which the first total amount and the second total amount match. [Figure 14] FIG. 14 is a diagram showing an example of a journal recorded in an electronic journal for a commercial transaction in which the first total amount and the second total amount do not match. [Figure 15] FIG. 15 is a diagram showing an example of a total discrepancy report. [Figure 16] FIG. 16 is a diagram showing another example of a journal recorded in an electronic journal for a commercial transaction in which the first total amount and the second total amount match. [Figure 17] FIG. 17 is a diagram showing another example of a journal recorded in an electronic journal for a commercial transaction in which the first total amount and the second total amount do not match. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, some embodiments will be described with reference to the drawings. In this embodiment, a store such as a supermarket equipped with a POS system also uses a mobile payment system. First, a store system constructed in this type of store will be described.
[0011] [Store system (POS system) explanation] 1 is a schematic diagram showing the schematic configuration of a store system established in a store that uses both a POS system 10 and a mobile payment system 20. The store system includes the POS system 10 and the mobile payment system 20.
[0012] The POS system 10 includes a plurality of POS terminals 11 and a POS server 12. The POS system 10 connects the plurality of POS terminals 11 and the POS server 12 via a communication network 13. The communication network 13 is, for example, a LAN (Local Area Network).
[0013] The POS terminal 11 is a device for registering purchased goods and settling commercial transactions. The POS terminal 11 may be a face-to-face type in which an employee performs the process from registering purchased goods to settling commercial transactions, or a self-service type in which a customer (a purchaser) performs the process from registering purchased goods to settling commercial transactions. Alternatively, the POS terminal 11 may be a shared type in which an employee registers purchased goods and the purchaser setstling commercial transactions.
[0014] The POS system 10 manages information such as store sales and inventory at the time of product sales by having the POS server 12 collect and compile product sales data for purchased products registered in commercial transactions settled at each POS terminal 11 via a communication network 13.
[0015] The POS server 12 includes a product master 14 and a discount table 15. The product master 14 is a collection of product records 141 (see FIG. 2) created for each product. FIG. 2 is a schematic diagram showing the data structure of the product record 141. As shown in the figure, the product record 141 is a data record that describes product data such as a product code, a product name, and a unit price. The product code is a unique code set for each product to identify each product. The product name and unit price are the name of the product identified by the product code and the price per item. The product data includes a discount target flag Fx. The discount target flag Fx is one-bid data for identifying whether the product is subject to a time-limited discount sale. For example, a product that is temporarily discounted only during a set time period such as a time sale, or a product that is discounted just before closing time such as a lunch box, a prepared meal, or fresh food, is subject to a time-limited discount sale. Hereinafter, a product that is subject to a time-limited discount sale is referred to as a discount target product. In this embodiment, the discount target flag Fx for a discount target product is set to "1", and the discount target flag Fx for other products is set to "0".
[0016] The discount table 15 is an area for writing data related to discounted products. FIG. 3 is a schematic diagram showing the data structure of the discount table 15. As shown in the figure, the discount table 15 has a column of product code, a column of start time, a column of end time, and a column of discount amount. The product code column describes the product code of the product to be discounted. If the time-limited discount sale is a time service, the start time and end time columns describe the start time and end time of the time service. If the time-limited discount sale is a discount service just before closing time, the start time of the service and the closing time or any time after closing time are described. The discount amount column describes the amount discounted by the time service or the amount discounted by the discount sale just before closing time. Note that instead of the discount amount, a discount rate or a discounted price may be described. Also, the discount amount, the discount rate, and the discounted price may be described together. In the case of a mixture of both, a column may be added to discount table 15 that describes data for identifying whether the value described in the column is the discount amount, the discount rate, or the discounted price.
[0017] Returning to the explanation of Figure 1. The POS terminal 11 has a means for inputting a product code. For example, each product is provided with a barcode that represents a product code unique to that product, and the POS terminal 11 has a scanner as an input means for scanning the barcode. When a product code is input via the input means, the POS terminal 11 queries the POS server 12 for data on the product identified by that product code.
[0018] The POS server 12 that has received the inquiry detects the product record 141 including the product code inputted at the POS terminal 11 from the product master 14. The POS server 12 also checks whether the product code is described in the discount table 15. If the product code is not described in the discount table 15, the POS server 12 transmits the product data of the product record 141 to the POS terminal 11. If the product code is described in the discount table 15, the POS server 12 obtains data of the start time, end time and discount amount associated with the product code from the discount table 15. The POS server 12 then transmits the data obtained from the discount table 15 together with the product data to the POS terminal 11. Hereinafter, the data of the start time, end time and discount amount obtained from the discount table 15 will be referred to as discount data.
[0019] The POS terminal 11 processes the product sales data based on the data received from the POS server 12. That is, when the POS terminal 11 receives product data, it processes the product sales data by taking the unit price in the product record 141 as the price of the purchased product. On the other hand, when discount data is received together with the product data, the POS terminal 11 processes the product sales data by taking the amount obtained by discounting the unit price in the product data by the discount amount in the discount data as the price of the purchased product. If a discount rate is described in the discount table 15, the POS terminal 11 processes the product sales data by taking the amount obtained by discounting the unit price in the product data by the discount rate as the price of the purchased product. If a discounted price is described in the discount table 15, the POS terminal 11 processes the product sales data by taking the discounted price as the price of the purchased product.
[0020] Thus, for discounted products for which a time-limited discount sale has been established, the POS terminal 11 processes the product sales data at the discounted price. For discounted products for which a time-limited discount sale has not been established and products other than discounted products, the POS terminal 11 processes the product sales data at the price set in the product master 14.
[0021] [Store system (mobile payment system) explanation] The mobile payment system 20 includes a plurality of mobile terminals 21 and a mobile server 22. The mobile payment system 20 wirelessly connects the plurality of mobile terminals 21 and the mobile server 22 via an access point 24 of a communication network 23.
[0022] The mobile terminal 21 is a portable information terminal equipped with input / output devices such as a touch panel and a camera, and a wireless communication unit capable of wireless communication with the access point 24. For example, the mobile terminal 21 can be a smartphone owned by a purchaser, a handheld terminal rented out by a store, a tablet terminal attached to a shopping cart, etc.
[0023] The mobile terminal 21 is operated by a purchaser who moves around the sales floor and collects products to be purchased. Each time a purchaser acquires a product, the purchaser operates the mobile terminal 21 to input data related to the purchased product. For example, the purchaser inputs the product code of the purchased product by scanning the barcode of the purchased product with the camera of the mobile terminal 21. For example, the purchaser inputs the product code, purchase quantity, etc. of the purchased product by operating the touch panel of the mobile terminal 21. The data related to the purchased product input to the mobile terminal 21 is wirelessly transmitted and received by the mobile server 22 via the access point 24.
[0024] When the purchaser has finished shopping, he / she performs an operation on the mobile terminal 21 to instruct the purchaser to make a payment. When the purchaser performs an operation to make a payment, the payment method becomes selectable on the mobile terminal 21, so the purchaser selects the desired payment method and performs an operation on the mobile terminal 21 to pay the price using that payment method. Payment methods include electronic money, credit card, code payment, etc. When the purchaser performs the payment operation, payment data is wirelessly transmitted from the mobile terminal 21. The payment data is received by the mobile server 22 via the access point 24.
[0025] Like the POS server 12, the mobile server 22 also includes a product master 25 and a discount table 26. The product records stored in the product master 25 match the product records 141 stored in the product master 14. The product code, start time, end time, and discount amount data described in the discount table 26 also match the data in the discount table 15.
[0026] The mobile server 22 detects a product record including the product code inputted by the mobile terminal 21 from the product master 25. The mobile server 22 also checks whether the product code is described in the discount table 26. If the product code is not described in the discount table 26, the mobile server 22 sets the unit price of the product record detected from the product master 25 as the price of the purchased product. If the product code is described in the discount table 26, the mobile server 22 sets the unit price of the product record detected from the product master 25 discounted by the discount amount of the product described in the discount table 26 as the price of the purchased product. The mobile server 22 uses the price to process the product sales data of the purchased product. If a discount rate is described in the discount table 26, the unit price of the product record discounted by the discount rate is set as the price of the purchased product. If a discounted price is described in the discount table 26, the discounted price is set as the price of the purchased product.
[0027] In this way, the mobile server 22 executes a process similar to the process of product sales data executed by the POS terminal 11 and the POS server 12 of the POS system 10, based on the data related to the purchased product received from the mobile terminal 21.
[0028] The mobile server 22 has a storage area for storing a plurality of transaction files 27. The transaction file 27 is a data file created for each purchaser who uses the mobile terminal 21 to carry out operations from registering a purchased item to settling a commercial transaction.
[0029] 4 is a schematic diagram showing the main data described in the transaction file 27. As shown in the figure, the transaction file 27 describes a transaction number, transaction date and time, one or more product sales data, total data, payment data, a settlement completion flag Fa, an integration flag Fb, etc. The transaction number is a unique number that is issued to identify a commercial transaction settled by the mobile terminal 21. The transaction date and time is the date and time when the commercial transaction was performed. The time may be a start time or an end time.
[0030] The product sales data is composed of data such as the product code, price, number of items purchased, and purchase amount of the purchased product. The product code is an identification code of the purchased product entered into the mobile terminal 21. The price is a price determined by the mobile server 22 based on the product code of the purchased product entered into the mobile terminal 21. The number of items purchased is the number of items purchased if one was entered into the mobile terminal 21, and is "1" if no number was entered. The purchase amount is an amount calculated by multiplying the price by the number of items purchased.
[0031] The total data is composed of data on the total number of items and the total price. The total number of items is the total of the purchased items of the product sales data included in the transaction file 27. The total price is the total of the purchased prices of the product sales data included in the transaction file 27.
[0032] The payment data includes a payment type for identifying the payment method and the payment amount according to the payment method. Since a commercial transaction settled by the mobile terminal 21 does not go through a cash register, the payment method is limited to cashless methods such as credit card, electronic money, and code payment.
[0033] The payment completion flag Fa is 1-bit data for identifying whether or not the payment has been completed for the commercial transaction managed in the transaction file 27. In this embodiment, the payment completion flag Fa indicating that the payment has not been completed is set to "0", and the payment completion flag Fa indicating that the payment has been completed is set to "1".
[0034] The integration flag Fb is one-bit data for identifying whether or not the sales of the commercial transactions managed in the transaction file 27 have been integrated into the sales tallied by the POS system 10. In this embodiment, the integration flag Fb indicating that the transactions have not been integrated is set to "0," and the integration flag Fb indicating that the transactions have been integrated is set to "1."
[0035] Returning to the explanation of Figure 1. The POS system 10 connects a communication server 31 to the communication network 13. The mobile payment system 20 connects a communication server 32 to the communication network 23. Both communication servers 31 and 32 provide data communication services via the inter-server network 30. This connection allows the POS server 12 in the POS system 10 and the mobile server 22 in the mobile payment system 20 to transmit and receive data between each other. This data communication ensures consistency between the product master 14 and discount table 15 in the POS server 12 and the product master 25 and discount table 26 in the mobile server 22. In addition, data on commercial transactions settled by the mobile payment system 20 is imported into the POS system 10.
[0036] [POS terminal configuration explanation] 5 is a block diagram showing the main circuit configuration of the POS terminal 11. The POS terminal 11 includes a processor 41, a main memory 42, an auxiliary storage device 43, a clock 44, a communication interface 45, a keyboard 46, a display 47, a printer 48, a scanner interface 49, a change machine interface 50, and a system transmission path 51. The system transmission path 51 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 51 connects the processor 41 to each of the other parts, and transmits data signals exchanged between them.
[0037] The POS terminal 11 constitutes a computer by connecting a processor 41, a main memory 42, an auxiliary storage device 43, a clock 44, and a communication interface 45 via a system transmission line 51. Input / output devices such as a keyboard 46, a display 47, and a printer 48, and device interfaces such as a scanner interface 49 and a change machine interface 50 are connected to the system transmission line 51 and controlled by a computer, thereby realizing the function of the POS terminal 11. Note that the input / output devices or device interfaces connected to the system transmission line 51 are not limited to those mentioned above. For example, other input / output devices such as a card reader and a pointing device may be connected, or an interface of a cashless payment terminal may be connected.
[0038] The processor 41 corresponds to the central part of the computer. The processor 41 controls each part to realize various functions of the POS terminal 11 according to an operating system or an application program. The processor 41 is, for example, a CPU (Central Processing Unit). The processor 41 is preferably a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.
[0039] The main memory 42 corresponds to the main storage portion of the computer. The main memory 42 includes a nonvolatile memory area and a volatile memory area. The main memory 42 stores an operating system or an application program in the nonvolatile memory area. The main memory 42 may store data required for the processor 41 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 42 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 41. The nonvolatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).
[0040] The auxiliary storage device 43 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 43. The auxiliary storage device 43 stores data used by the processor 41 when performing various processes, data created by the processes in the processor 41, etc. The auxiliary storage device 43 may also store the above-mentioned application programs.
[0041] The clock 44 keeps track of the date and time. The processor 41 processes the date and time kept by the clock 44 as the current date and time.
[0042] The communication interface 45 is an interface for performing data communication with the POS server 12 connected to the communication network 13 .
[0043] The keyboard 46 is an input device equipped with various keys required for registering purchased items and settling commercial transactions. The display 47 is a display device for displaying the names, prices, total amounts, etc. of registered purchased items. The printer 48 is a printing device for printing data on receipt paper to issue purchase receipts, etc. The scanner interface 49 is an interface with a scanner capable of scanning codes such as barcodes and two-dimensional codes. The change machine interface 50 is an interface with an automatic change machine capable of depositing deposits and dispensing change.
[0044] In the POS terminal 11 having such a configuration, a part of the volatile memory area in the main memory 42 is used as an area for a transaction file 61 and a discrepancy file 62. The transaction file 61 is a data file for describing data related to one commercial transaction. The discrepancy file 62 is a data file for storing one or more discrepancies. The discrepancy data will be described later.
[0045] 6 is a schematic diagram showing main data described in a transaction file 61 possessed by the POS terminal 11. As shown in the figure, the transaction file 61 describes a transaction number, transaction date and time, one or more product sales data, total data, payment data, difference flag Fc, difference B, etc. The transaction number is a unique number that is issued to identify a commercial transaction settled at the POS terminal 11. The transaction date and time is the date and time when the commercial transaction was performed. The time may be a start time or an end time.
[0046] The product sales data is composed of data such as the product code, price, number of items purchased, and purchase amount. The product code is an identification code of the purchased product entered into the POS terminal 11. The price is a price determined based on the product code of the purchased product entered into the POS terminal 11. The number of items purchased is the number of items purchased if one has been entered into the POS terminal 11, and is "1" if no number has been entered. The purchase amount is an amount calculated by multiplying the price by the number of items purchased.
[0047] The total data is composed of data on the total number of items and the total price. The total number of items is the total of the purchased items of the product sales data included in the transaction file 61. The total price is the total of the purchased prices of the product sales data included in the transaction file 61.
[0048] The payment data includes a payment type for identifying the payment method and a payment amount according to the payment method. The payment method is, for example, cash. The payment method may be a cashless method such as credit card, electronic money, or code payment. The difference flag Fc and the difference B will be described later.
[0049] The POS terminal 11 uses a part of the storage area in the auxiliary storage device 43 as an area for an electronic journal 63. The electronic journal 63 electronically stores journal data of commercial transactions settled at the POS terminal 11.
[0050] In this embodiment, one of the multiple POS terminals 11 constituting the POS system 10 is a product sales data processing device that processes data on purchased products in a commercial transaction settled through the mobile payment system 20. Hereinafter, this POS terminal 11 is referred to as a mobile-only device.
[0051] Any of the multiple POS terminals 11 can be a mobile-only device. That is, in order for each POS terminal 11 to operate as a mobile-only device, the processor 41 has the functions of a determination means 71, a monitoring means 72, a first acquisition means 73, a second acquisition means 74, a processing means 75, a calculation means 76, a recording means 77, a storage means 78, and an output means 79 shown in FIG.
[0052] The determination means 71 is a function that determines whether or not to operate as a mobile-only machine. The POS terminal 11 has a dedicated machine flag as an option flag. The dedicated machine flag is 1-bit data for determining whether or not to operate as a mobile-only machine, and is set to "1" or "0." In this embodiment, the dedicated machine flag indicating that the terminal operates as a mobile-only machine is set to "1," and the dedicated machine flag indicating that the terminal does not operate as a mobile-only machine is set to "0." The determination means 71 checks the dedicated machine flag, and determines that the terminal operates as a mobile-only machine if the dedicated machine flag is set to "1."
[0053] In this embodiment, among the multiple POS terminals 11, the dedicated machine flag of any one of the POS terminals 11 is set to "1" to operate as a mobile dedicated machine. The POS terminal 11 operated as a mobile dedicated machine is installed, for example, in the back yard of a store. The dedicated machine flags of the other POS terminals 11 are set to "0". The POS terminal 11 with the dedicated machine flag set to "0" is installed in the checkout area (cash register) of the store.
[0054] The functions of the monitoring means 72, the first acquisition means 73, the second acquisition means 74, the processing means 75, the calculation means 76, the recording means 77, the storage means 78 and the output means 79 are enabled when the determination means 71 determines that the device will operate as a mobile-only device.
[0055] Monitoring means 72 is a function that monitors the settlement of a commercial transaction in mobile payment system 20. First acquisition means 73 is a function that acquires data related to the purchased items in a commercial transaction settled in mobile payment system 20. Second acquisition means 74 is a function that acquires the total amount of the commercial transaction calculated at the time the commercial transaction is settled in mobile payment system 20. Hereinafter, the total amount acquired by second acquisition means 74 is referred to as the first total amount.
[0056] The processing means 75 has a function of processing sales data of a commercial transaction settled by the mobile payment system 20 based on data related to the product acquired by the first acquisition means 73. The processing means 75 writes the sales data of the commercial transaction in the transaction file 61. The calculation means 76 has a function of calculating the total amount of the commercial transaction based on the sales data processed by the processing means 75. Hereinafter, the total amount calculated by the calculation means 76 is referred to as the second total amount. The recording means 77 has a function of recording journal data of the commercial transaction, the sales data of which is processed by the processing means 75, in the electronic journal 63.
[0057] The saving means 78 has a function of saving in the discrepancy file 62 discrepancy data relating to a commercial transaction in which a difference occurs between the first total amount acquired by the second acquiring means 74 and the second total amount calculated by the calculating means 76. The discrepancy data is data including the transaction number, the first total amount, the second total amount, and the difference of the commercial transaction.
[0058] The output means 79 is a function for outputting the difference between the first total amount and the second total amount. The output means 79 outputs a total amount discrepancy report 80 indicating the difference between the first total amount and the second total amount based on, for example, the discrepancy data stored in the discrepancy file 62. The output means 79 outputs the difference between the first total amount and the second total amount to be recorded in, for example, the electronic journal 63.
[0059] The functions of the determining means 71, the monitoring means 72, the first acquiring means 73, the second acquiring means 74, the processing means 75, the calculation means 76, the recording means 77, the saving means 78 and the output means 79 are realized by information processing executed by the processor 41 in accordance with a business program. The business program is a type of application program stored in the main memory 42 or the auxiliary storage device 43. The method of installing the business program in the main memory 42 or the auxiliary storage device 43 is not particularly limited. The business program can be installed in the main memory 42 or the auxiliary storage device 43 by recording it on a removable recording medium or by distributing the business program by communication via a network. The form of the recording medium is not important as long as it can store a program and is readable by a device, such as a CD-ROM or a memory card.
[0060] [Store system operation explanation] FIG. 8 is a flow chart showing the procedure of information processing executed by the mobile server 22 in conjunction with the mobile terminal 21 when the purchaser operates the mobile terminal 21 to register the purchased item to settle the transaction. FIG. 9 is a flow chart showing the procedure of main information processing executed by the processor 41 of the POS terminal 11. FIG. 10 is a flow chart showing the procedure of information processing executed by the mobile server 22 in conjunction with the POS terminal 11 operating as a mobile-only device. FIG. 11 and FIG. 12 are flow charts showing the specific procedure of the sales integration process in FIG. 9. Below, the main operations of the POS system 10 and the mobile payment system 20 will be described according to the information processing procedures explained using each flow chart. Note that the operations described below are examples. The information processing procedures and the contents of the processing related to the operations are not particularly limited as long as they can achieve the same effects as those of the present embodiment.
[0061] First, the information processing procedure shown in the flowchart of FIG. 8 will be described. A purchaser who operates the mobile terminal 21 to register the purchased item to settle the transaction performs an operation to command the mobile terminal 21 to start shopping. For example, the purchaser touches the start button on the start-up screen displayed on the touch panel of the mobile terminal 21. This operation causes the mobile terminal 21 to transmit a start-up command. The start-up command is transmitted to the mobile server 22 via the access point 24.
[0062] Upon receiving the start command, the mobile server 22 starts information processing according to the procedure shown in the flow chart of Figure 8. The mobile server 22 issues a new transaction number as ACT1. For example, the mobile server 22 is equipped with a transaction number counter, and counts up the counter each time a start command is received. The mobile server 22 acquires the incremented counter value as the transaction number. Next, the mobile server 22 acquires the transaction date and time as ACT2. For example, the mobile server 22 acquires the current date and time kept by the built-in clock IC as the transaction date and time.
[0063] After completing the processing of ACT1 and ACT2, the mobile server 22 proceeds to ACT3. The mobile server 22 creates a transaction file 27 in ACT3. That is, the mobile server 22 creates the transaction file 27 that describes the transaction number obtained in the processing of ACT1 and the transaction date and time obtained in the processing of ACT2.
[0064] The mobile server 22, which has created the transaction file 27, proceeds to ACT 4. In ACT 4, the mobile server 22 sets both the settlement completion flag Fa and the integration flag Fb of the transaction file 27 to "0".
[0065] Upon completing the processing of ACT1 to ACT4, the mobile server 22 proceeds to ACT5. In ACT5, the mobile server 22 waits to receive a product purchase event from the mobile terminal 21. The product purchase event is sent from the mobile terminal 21 in response to data related to a purchased product being input into the mobile terminal 21. The product purchase event includes data related to the purchased product, i.e., product code, purchase quantity, etc.
[0066] When the product purchase event is received, the mobile server 22 proceeds to ACT6. In ACT6, the mobile server 22 searches the product master 25 for the product code included in the product purchase event, and acquires product data including the product name, unit price, discount flag Fx, etc. of the product record that includes the product code. In ACT7, the mobile server 22 checks the discount flag Fx to confirm whether the purchased product is a discounted product. If the discount flag Fx is "0", the mobile server 22 determines that the purchased product is not a discounted product. If the discount flag Fx is "1", the mobile server 22 determines that the purchased product is a discounted product.
[0067] If the purchased item is a discounted item, the mobile server 22 proceeds from ACT7 to ACT8. In ACT8, the mobile server 22 refers to the discount table 26 to confirm whether or not the discount will be granted. Specifically, the mobile server 22 confirms whether or not the current time measured by the clock IC is within the time period between the start time and the end time described in the discount table 26 corresponding to the product code of the purchased item. If the current time is not within the time period between the start time and the end time, the mobile server 22 determines that the discount will not be granted. If the current time is within the time period between the start time and the end time, the mobile server 22 determines that the discount will be granted.
[0068] If the discount is granted, the mobile server 22 proceeds to ACT 9. In ACT 9, the mobile server 22 obtains the price of the purchased item by subtracting the discount amount described in the discount table 26 corresponding to the product code of the purchased item from the unit price of the product data.
[0069] On the other hand, if the discount is not granted or if the purchased item is not a discounted item, the mobile server 22 proceeds to ACT 10. In ACT 10, the mobile server 22 acquires the unit price of the item data as the price of the purchased item.
[0070] After completing the processing of ACT9 or ACT10, the mobile server 22 proceeds to ACT11. In ACT11, the mobile server 22 creates product sales data including the product code, price, purchase quantity, and purchase amount, and writes the product sales data to the transaction file 27 created in the processing of ACT3. The mobile server 22 also updates the total data written in the transaction file 27 in ACT12. That is, the mobile server 22 adds the purchase quantity of the product sales data to the total number of items. The mobile server 22 also adds the purchase amount of the product sales data to the total amount.
[0071] The mobile server 22 then checks whether a transaction event has been received as ACT13. The transaction event is sent from the mobile terminal 21 in response to payment data being entered into the mobile terminal 21. The transaction event includes the payment type and payment amount, which are payment data.
[0072] If a transaction event has not been received, the mobile server 22 returns to ACT5. That is, the mobile server 22 waits for a product purchase event. Then, when a product purchase event is received, the mobile server 22 executes the processes of ACT6 to ACT12 in the same manner as described above. In this way, the mobile server 22 repeatedly executes the processes of ACT6 to ACT12 every time a product purchase event is received from the mobile terminal 21. As a result, product sales data is written in the transaction file 27 for each purchased product registered on the mobile terminal 21. In addition, the total data is updated based on each product sales data.
[0073] When the mobile server 22 receives a transaction event, it proceeds to ACT14. The mobile server 22 writes the payment data included in the transaction event in the transaction file 27 as ACT14. The mobile server 22 also executes cashless payment processing as ACT15. The cashless payment processing is processing related to credit card credit transactions, for example, when the payment type of the payment data is a credit card. For example, when the payment type of the payment data is electronic money, it is processing of deducting the payment amount from the balance of electronic money. For example, when the payment type of the payment data is code payment, it is processing of deducting the payment amount from the payable amount specified by the code. This type of cashless payment processing is well known, so a detailed explanation will be omitted.
[0074] After completing the cashless payment process, the mobile server 22 proceeds to ACT 16. In ACT 16, the mobile server 22 switches the payment completion flag Fa in the transaction file 27 to “1.”
[0075] With the above, the mobile server 22 ends the information processing when it receives a start-up command from the mobile terminal 21. When the mobile server 22 receives a start-up command from another mobile terminal 21, the mobile server 22 executes the processing of ACT1 to ACT16 in the same manner as described above. Then, when a start-up command is received from another mobile terminal 21 before the information processing related to one mobile terminal 21 is finished, the mobile server 22 executes the processing of ACT1 to ACT16 in parallel.
[0076] Next, the information processing procedure shown in the flowchart of FIG. 9 will be described. When the processor 41 of each POS terminal 11 is powered on and starts up, it starts information processing according to the procedure shown in the flowchart of Fig. 9. First, the processor 41 performs an option check in ACT21. The option check is a process for checking the option flags set in the auxiliary storage device 43. The option flags include the dedicated machine flag described above. The processor 41 checks whether the dedicated machine flag is "1" in ACT42.
[0077] If the dedicated machine flag is not "1", the POS terminal 11 is set not to operate as a mobile dedicated machine. In this case, the processor 41 proceeds to ACT23. The processor 41 waits for an operator to sign on in ACT23. If an operator signs on, the processor 41 proceeds to ACT24. The processor 41 executes processing as a normal POS terminal 11 in ACT24. This processing is well known, so a description thereof will be omitted here.
[0078] On the other hand, if the dedicated machine flag is "1", the POS terminal 11 is set to operate as a mobile dedicated machine. In this case, the processor 41 proceeds to ACT25. The processor 41 executes automatic sign-on in ACT25. For example, the processor 41 assumes that a prepared sign-on code has been entered and proceeds to ACT26. The processor 41 starts the sales integration mode in ACT26.
[0079] Having started the sales integration mode, the processor 41 proceeds to ACT27. The processor 41 controls the communication interface 45 to send an inquiry command for the payment completion transaction in ACT27. This control causes the inquiry command for the payment completion transaction to be sent from the communication interface 45. The inquiry command for the payment completion transaction is sent from the communication server 31 to the communication server 32 via the inter-server network 30, and is further sent to the mobile server 22.
[0080] In the mobile server 22 that has received the inquiry command for the settlement completion transaction, information processing is executed according to the procedure shown in the flowchart of Fig. 10. As a result, the mobile server 22 returns a transaction response or a no-transaction response to the POS terminal 11 that sent the inquiry.
[0081] When the processor 41 receives a transaction response, the processor 41 proceeds to ACT 29. The processor 41 executes the sales integration process according to the procedure shown in the flowcharts of Figures 11 and 12. On the other hand, when the processor 41 receives a no-transaction response, the processor 41 does not execute the sales integration process.
[0082] The processor 41 executes the sales integration process according to the transaction response, or proceeds to ACT 30 if it receives a no-transaction response. The processor 41 checks whether the sales integration mode has ended in ACT 30. The sales integration mode ends at a specified time, for example, after closing time.
[0083] If the sales integration mode has not ended, the processor 41 returns to ACT27. Then, the processor 41 executes the processes of ACT27 to ACT30 in the same manner as described above. In this manner, the processor 41 repeatedly executes the processes of ACT27 to ACT30 from the start to the end of the sales integration mode. That is, the processor 41 periodically transmits a settlement completion inquiry command, and executes the sales integration process only when a transaction response is received. This period depends on the speed of information processing, but is preferably every few seconds or every tens of seconds.
[0084] Here, the processor 41 realizes the function of a decision means 71 by the processing of ACT21 and ACT22. The processor 41 also realizes the function of a monitoring means 72 by the processing of ACT27 and ACT28.
[0085] Next, the information processing procedure shown in the flowchart of FIG. 10 will be described. The mobile server 22 waits for a query command for a settlement completion transaction in ACT41. Upon receiving the query command, the mobile server 22 proceeds to ACT42. In ACT42, the mobile server 22 searches the transaction file 27 in ascending order of transaction number, and checks the settlement completion flag Fa and the integration flag Fb. Alternatively, the mobile server 22 searches the transaction file 27 in descending order of transaction number in ACT42, and checks the settlement completion flag Fa and the integration flag Fb.
[0086] A transaction file 27 with a payment completion flag Fa of "0" is for a transaction that has not yet been settled. A transaction file 27 with a payment completion flag Fa of "1" is for a transaction that has been settled by operating the mobile terminal 21. A transaction file 27 with an integration flag Fb of "0" is for which sales integration processing has not been completed. A transaction file 27 with an integration flag Fb of "1" is for which sales integration processing has already been completed.
[0087] The mobile server 22 checks in ACT43 whether the transaction file 27 has a settlement completion flag Fa of "1" and an integration flag Fb of "0". If the transaction file 27 has a settlement completion flag Fa of "0" or an integration flag Fb of "1", the mobile server 22 proceeds to ACT44. The mobile server 22 checks in ACT44 whether the search for the transaction file 27 has been completed. If the search for the transaction file 27 has not been completed, the mobile server 22 returns to ACT42. The mobile server 22 searches for the next transaction file 27 and checks the settlement completion flag Fa and the integration flag Fb.
[0088] When the mobile server 22 detects a transaction file 27 in which the settlement completion flag Fa is "1" and the integration flag Fb is "0", the process proceeds to ACT45. The mobile server 22 rewrites the integration flag Fb of the transaction file 27 to "1" in ACT45. The mobile server 22 then acquires the transaction file 27 in ACT46. The mobile server 22 then transmits a transaction response in ACT47. The transaction response includes the data of the transaction file 27 acquired in the processing of ACT46. The transaction response is received by the POS terminal 11 that sent the inquiry command, i.e., the POS terminal 11 operating as a mobile-only device.
[0089] On the other hand, if the search for the transaction file 27 is terminated without finding a transaction file 27 in which the settlement completion flag Fa is "1" and the integration flag Fb is "0", the mobile server 22 proceeds to ACT48. The mobile server 22 transmits a no-transaction response as ACT48. The no-transaction response is also received by the POS terminal 11 that transmitted the inquiry command, i.e., the POS terminal 11 operating as a mobile-only device. The mobile server 22, which has sent either the no-transaction response or the transaction response, ends the information processing procedure shown in FIG.
[0090] In this way, the mobile server 22 executes the processes of ACT42 to ACT48 every time it receives a payment completion transaction inquiry command. As a result, when a transaction file 27 with a payment completion flag Fa of "1" and an integration flag Fb of "0" is detected, a transaction response including data of the transaction file 27 is transmitted from the mobile server 22 to the POS terminal 11 operating as a mobile-only device. The transaction file 27 transmitted to the POS terminal 11 has an integration flag Fb of "1", so it will not be transmitted thereafter.
[0091] The processor 41 of the POS terminal 11 that has received the transaction response executes the sales integration process as described above. Next, a specific procedure of the sales integration process will be described with reference to FIGS.
[0092] When the sales integration process is started, the processor 41 clears the addition memory Ma to "0" as ACT51 in FIG. 11. The addition memory Ma is part of the volatile memory area in the main memory 42. The processor 41 also stores the transaction number as ACT52. For example, the POS terminal 11 is equipped with a transaction number counter, and the counter is counted up each time the sales integration process is started. The processor 41 writes the incremented counter value as the transaction number in the transaction file 61. Note that the transaction file 61 is cleared before the sales integration process is started. The processor 41 then stores the transaction date and time as ACT53. The processor 41 obtains the transaction date and time from the transaction file 27 included in the transaction response, and writes the transaction date and time in the transaction file 61.
[0093] After completing the processes in ACT51 to ACT53, the processor 41 proceeds to ACT54. The processor 41 acquires one item of product sales data from the transaction file 27 included in the transaction response in ACT54. Then, the processor 41 adds the purchase amount of the item sales data to the addition memory Ma in ACT55.
[0094] The processor 41 also detects the product code and the number of items purchased from the product sales data as ACT 56. The processor 41 then controls the communication interface 45 to send a product data request command as ACT 57. This control causes the product data request command to be sent from the POS terminal 11. The product data request command is sent to the POS server 12 via the communication network 13. The product data request command includes the product code detected from the product sales data.
[0095] Upon receiving the product data request command, the POS server 12 searches the product master 14 for the product code included in the product data request command. The POS server 12 then obtains a product record including the product code from the product master 14. The POS server 12 also searches the discount table 15 for the product code. If the product code is found in the discount table 15, the POS server 12 obtains discount data for the start time, end time, and discount amount corresponding to the product code.
[0096] The POS server 12 transmits the product data of the product record acquired from the product master 14 to the POS terminal 11 that transmitted the product data request command. When the POS server 12 acquires discount data from the discount table 15, the POS server 12 also transmits the discount data to the POS terminal 11 that transmitted the product data request command.
[0097] The processor 41 of the POS terminal 11 that sent the product data request command waits to receive data from the POS server 12 in ACT 58. When the processor 41 receives the product data from the POS server 12, the processor 41 proceeds to ACT 59. The processor 41 checks the discount target flag Fx of the product data received in ACT 59 to confirm whether the purchased product is a discount target product. If the discount target flag Fx is "0", the processor 41 determines that the purchased product is not a discount target product. If the discount target flag Fx is "1", the processor 41 determines that the purchased product is a discount target product.
[0098] If the purchased item is a discounted item, the processor 41 proceeds from ACT59 to ACT60. The processor 41 checks whether or not the discount is granted in ACT60. If the processor 41 receives item data with the discount target flag Fx set to "1", the processor 41 receives discount data including the item code of the item data from the POS server 12. The processor 41 checks whether or not the current time clocked by the clock IC is in a time period between the start time and the end time of the discount data. If the current time is not in a time period between the start time and the end time, the processor 41 determines that the discount is not granted. If the current time is in a time period between the start time and the end time, the processor 41 determines that the discount is granted.
[0099] If the discount is granted, the processor 41 proceeds to ACT 61. In ACT 61, the processor 41 acquires the amount obtained by subtracting the discount amount of the discount data from the unit price of the product data as the price of the purchased product. In contrast, if the discount is not granted or the purchased product is not a discount eligible product, the processor 41 proceeds to ACT 62. In ACT 62, the processor 41 acquires the unit price of the product data as the price of the purchased product.
[0100] Upon completing the processing of ACT61 or ACT62, the processor 41 proceeds to ACT63. In ACT63, the processor 41 creates product sales data including the product code, price, purchase quantity, and purchase amount, and writes the product sales data to the transaction file 61. The processor 41 also updates the total data written in the transaction file 61 in ACT64. That is, the processor 41 adds the purchase quantity of the product sales data to the total number of items. The processor 41 also adds the purchase amount of the product sales data to the total amount.
[0101] After completing the processes of ACT63 and ACT64, the processor 41 proceeds to ACT65. In ACT65, the processor 41 checks whether the next product sales data is included in the transaction file 27. If the next product sales data is included in the transaction file 27, the processor 41 returns to ACT54. The processor 41 then executes the processes of ACT54 to ACT64 in the same manner as described above.
[0102] When the processing of ACT54 to ACT64 has been completed for all the product sales data included in the transaction file 27, the processor 41 proceeds to ACT71 in Fig. 12. In ACT71, the processor 41 obtains payment data from the transaction file 27 and writes the payment data in the transaction file 61.
[0103] Next, the processor 41 compares the amount in the addition memory Ma, that is, the first total amount, with the total amount of the total data stored in the transaction file 61, that is, the second total amount, in ACT72. If the first total amount and the second total amount match, the processor 41 proceeds to ACT73. The processor 41 sets the difference flag Fc of the transaction file 61 to "0" in ACT73. The processor 41 also sets the difference B of the transaction file 61 to "0" in ACT74.
[0104] On the other hand, if the first total amount and the second total amount do not match, the processor 41 proceeds to ACT75. The processor 41 sets the difference flag Fc of the transaction file 61 to "1" in ACT75. The processor 41 also sets the difference B of the transaction file 61 to the amount obtained by subtracting the second total amount from the first total amount in ACT76. Therefore, if the second total amount is greater than the first total amount, the difference B is positive. If the second total amount is less than the first total amount, the difference B is negative. Note that the difference B may be the amount obtained by subtracting the first amount from the second amount. In that case, if the second total amount is greater than the first total amount, the difference B is negative. If the second total amount is less than the first total amount, the difference B is positive.
[0105] In this way, the difference flag Fc is 1-bit data for identifying whether the first total amount and the second total amount match. In this embodiment, when the first total amount and the second total amount match, the difference flag Fc is set to "0", and when they do not match, the difference flag Fc is set to "1". In addition, the difference B is the difference between the first total amount and the second total amount.
[0106] Upon completing the processing of ACT74 or ACT76, the processor 41 proceeds to ACT77. The processor 41 controls the communication interface 45 to transmit the transaction file 61 to the POS server 12 in ACT77. By this control, the data of the transaction file 61 is transmitted to the POS server 12. The POS server 12 tally up the store's sales based on the product sales data etc. contained in the transaction file 61.
[0107] The processor 41 records a journal in the electronic journal 63 based on the data in the transaction file 61 as ACT 78. The journal includes the transaction number, transaction date and time, product sales data, total data, and payment data.
[0108] After completing the processes in ACT77 and ACT78, the processor 41 proceeds to ACT79. In ACT79, the processor 41 checks the difference flag Fc included in the transaction file 61. If the difference flag Fc is "0", the processor 41 ends the sales integration process.
[0109] On the other hand, if the difference flag Fc is "1", the processor 41 proceeds from ACT79 to ACT80. The processor 41 creates discrepancy data as ACT80 and saves it in the discrepancy file 62. That is, the processor 41 saves discrepancy data including the transaction number described in the transaction file 61, the second total amount and difference B of the total data, and the first total amount in the addition memory Ma in the discrepancy file 62. The processor 41 also obtains a discrepancy message as ACT81. The discrepancy message is a message that explains the cause of the difference between the first total amount and the second total amount. The discrepancy message is stored in, for example, the auxiliary storage device 43. The processor 41 records the difference B and the discrepancy message in the electronic journal 63 as ACT82. With the above, the processor 41 of the POS terminal 11 operating as a mobile-only device ends the sales integration process.
[0110] Here, the processor 41 realizes the function of first acquisition means 73 by processing ACT54. The processor 41 realizes the function of second acquisition means 74 by processing ACT55. The processor 41 realizes the function of processing means 75 by processing ACT56 to ACT63. The processor 41 realizes the function of calculation means 76 by processing ACT64. The processor 41 realizes the function of recording means 77 by processing ACT78. The processor 41 realizes the function of saving means 78 by processing ACT80. The processor 41 realizes the function of output means 79 by processing ACT82.
[0111] [Journal description] Fig. 13 shows an example of journal 81 recorded in electronic journal 63 for a transaction in which the first total amount (600 yen) and the second total amount (600 yen) match, with the difference being "0". On the other hand, Fig. 14 shows journal 82 recorded in electronic journal 63 for a transaction in which the first total amount (600 yen) and the second total amount (580 yen) do not match, with the difference being -20 yen. The purchased items match between the transaction in journal 81 and the transaction in journal 82. The purchased item CCC is eligible for a limited time service.
[0112] The time when the transaction in journal 81 was settled by mobile payment system 20 and the time when transaction file 27 of this transaction was imported by POS terminal 11 operating as a mobile-only device were not within the time service period. Therefore, there is no difference between the total amount of the transaction calculated at the time when the transaction was settled by mobile payment system 20, i.e., the first total amount, and the total amount of the transaction calculated by POS terminal 11, i.e., the second total amount.
[0113] Even if the time when the transaction in journal 81 is settled by mobile settlement system 20 and the time when the transaction file 27 of this transaction is imported by POS terminal 11 operating as a mobile-only device are both during the time service period, there will be no difference between the first total amount and the second total amount. As a result, the contents recorded in journal 81 will be that the price of product CCC is 280 yen, the total amount is 580 yen, and the payment amount is also 580 yen. Other than that, it is the same as shown in FIG. 13.
[0114] On the other hand, the time when the transaction in journal 82 was settled by mobile payment system 20 was before the start time of the time service, and the time when the transaction file 27 of this transaction was imported by POS terminal 11 operating as a mobile-only device was after the start time of the time service. Therefore, the product sales data of product CCC was processed by mobile payment system 20 at the pre-discount price of 300 yen, whereas it was processed by POS terminal 11 at the post-discount price of 280 yen. As a result, the first total amount is 600 yen and the second total amount is 580 yen, resulting in a difference of -20 yen. Therefore, the difference of -20 yen is recorded in journal 82 in electronic journal 63. Also, a discrepancy message explaining the cause of the difference between the first total amount and the second total amount, for example, "The difference is due to a system linkage error" is output.
[0115] Note that even if the transaction in journal 82 is settled by mobile payment system 20 before the end of the time service, and the transaction file 27 of this transaction is imported by POS terminal 11 operating as a mobile-only device after the end of the time service, a difference will occur between the first total amount and the second total amount. As a result, the contents recorded in journal 82 will show that the price of product CCC is 300 yen, the total amount is 600 yen, and the payment amount is 580 yen. Also, the difference is +20 yen. Other than that, it is the same as shown in FIG. 14.
[0116] [Discrepancy report description] The POS terminal 11 operating as a mobile-only device has a function of generating discrepancy data and saving it in the discrepancy file 62 when a difference occurs between the first total amount and the second total amount. The POS terminal 11 also has a function as an output means 79 that outputs a total amount discrepancy report 80 based on the discrepancy data saved in the discrepancy file 62. The total amount discrepancy report 80 is printed on receipt paper by the printer 48 and issued, for example, as a type of inspection report that can be issued in an inspection operation of the POS terminal 11 or as a type of settlement report that can be issued in a settlement operation.
[0117] 15 is an example of a total amount discrepancy report 80. The total amount discrepancy report 80 indicates that a difference occurred between the transaction with transaction number "123456" and the transaction with transaction number "234567." Additionally, the total amount discrepancy report 80 indicates that the difference is -20 yen for the transaction with transaction number "123456" and +20 yen for the transaction with transaction number "234567."
[0118] [Explanation of effects] As described above in detail, in a store where POS system 10 and mobile payment system 20 are used together, by operating one of POS terminals 11 as a mobile-only device, each time a commercial transaction is settled using mobile payment system 20, product sales data for that commercial transaction can be compiled by POS server 12. As a result, product sales data for commercial transactions settled using mobile payment system 20 can also be compiled by POS server 12 in approximately real time.
[0119] Furthermore, when a limited-time discount sale such as a limited-time sale is implemented, a difference may occur between the price of the purchased item at the time the payment is made with mobile payment system 20 and the price of the purchased item at the time POS terminal 11 retrieves the data from mobile payment system 20. In such a case, the difference is recorded as a journal in electronic journal 63. In addition, a total amount discrepancy report 80 indicating the difference can be issued. Therefore, by taking the difference into account, it becomes possible to accurately grasp the sales of a store that uses both POS system 10 and mobile payment system 20.
[0120] [Other embodiments] Fig. 16 shows another example of a journal 83 recorded in an electronic journal for a transaction in which the first total amount and the second total amount match. As shown in Fig. 16, even when the first total amount and the second total amount match, a difference of 0 yen may be recorded in the journal 83. By doing so, it is possible to easily identify which transactions have a difference and which do not.
[0121] Fig. 17 shows another example of a journal 84 recorded in an electronic journal for a transaction in which the first and second total amounts do not match. As shown in Fig. 17, when the first and second total amounts do not match, an identification mark, such as a star, may be added to the product name for which there is a price difference. This makes it easy to determine which product caused the price difference.
[0122] In the above embodiment, the POS server 12 and the mobile server 22 are respectively provided with a product master and a discount table. In this regard, for example, the product master and the discount table may be stored on a cloud, and the POS server 12 and the mobile server 22 may access the cloud via the inter-server network 30 to retrieve necessary data from the product master and the discount table. Also, the discount table 15 in the POS system 10 may be stored in each POS terminal 11, and the price of the discounted product may be determined by referring to the discount table 15.
[0123] In the above embodiment, the discrepancy data includes the transaction number, the first total amount, the second total amount, and the difference of the transaction. The discrepancy data may further include the product code, the first price, the second price, etc. of the product for which the first price at the time the transaction is settled in the mobile payment system is different from the second price at the time the product sales data is processed by the processing means. In this way, the product that caused the discrepancy can be identified by the total discrepancy report 80.
[0124] Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the invention and its equivalents described in the claims. [Explanation of symbols]
[0125] 10... POS system, 11... POS terminal, 12... POS server, 13, 23... communication network, 14, 25... product master, 15, 26... discount table, 20... mobile payment system, 21... mobile terminal, 22... mobile server, 24... access point, 27, 61... transaction file, 30... inter-server network, 31, 32... communication server, 41... processor, 42... main memory, 43... auxiliary storage device, 44... clock, 45... communication Interface, 46...keyboard, 47...display, 48...printer, 49...scanner interface, 50...change machine interface, 51...system transmission path, 62...mismatch file, 63...electronic journal, 71...determination means, 72...monitoring means, 73...first acquisition means, 74...second acquisition means, 75...processing means, 76...calculation means, 77...recording means, 78...storage means, 79...output means, 80...mismatch report, 81-84...journals.
Claims
1. A monitoring means for monitoring the settlement of a commercial transaction in a mobile payment system that settles a commercial transaction with a purchaser based on data input via a mobile terminal operated by the purchaser; A first acquisition means for acquiring data related to a purchased item in a commercial transaction settled by the mobile payment system; A second acquisition means for acquiring a total amount of the commercial transaction calculated at the time the commercial transaction is settled using the mobile payment system; A processing means for processing product sales data of a commercial transaction settled by the mobile payment system based on the data related to the purchased product acquired by the first acquisition means; A calculation means for calculating a total amount of a commercial transaction based on the product sales data processed by the processing means; an output means for outputting the difference between the total amount acquired by the second acquisition means and the total amount calculated by the calculation means; A product sales data processing device comprising:
2. a recording means for recording a journal of a commercial transaction in which the product sales data is processed by the processing means; Further comprising:
2. The product sales data processing device according to claim 1, wherein said output means outputs said difference so as to be recorded in said journal.
3. a storage means for storing data of a commercial transaction in which a difference occurs between the total amount acquired by the second acquisition means and the total amount calculated by the calculation means; Further comprising:
2. The product sales data processing device according to claim 1, wherein said output means outputs a difference based on the transaction data stored by said storage means.
4. A plurality of POS terminals for processing product sales data of commercial transactions; a POS server that tally up sales based on product sales data of commercial transactions processed by each POS terminal; Including, Any one of the plurality of POS terminals, A monitoring means for monitoring the settlement of a commercial transaction in a mobile payment system that settles a commercial transaction with a purchaser based on data input via a mobile terminal operated by the purchaser; A first acquisition means for acquiring data related to a purchased item in a commercial transaction settled by the mobile payment system; A second acquisition means for acquiring a total amount of the commercial transaction calculated at the time of payment via the mobile payment system; a processing means for processing merchandise sales data of a commercial transaction settled by the mobile payment system based on the data relating to the purchased merchandise acquired by the first acquisition means; A calculation means for calculating a total amount of a commercial transaction based on the product sales data processed by the processing means; and an output means for outputting the difference between the total amount acquired by the second acquisition means and the total amount calculated by the calculation means; The POS system functions as a product sales data processing device having the above.
5. a determination means for determining whether or not the plurality of POS terminals operate as the product sales data processing device; Further comprising:
5. The POS system according to claim 4, wherein when it is determined that the system operates as the product sales data processing device, the monitoring means starts a monitoring operation.
6. A computer of a product sales data processing device, A monitoring means for monitoring the settlement of a commercial transaction in a mobile payment system that settles a commercial transaction with a purchaser based on data input via a mobile terminal operated by the purchaser; A first acquisition means for acquiring data related to a purchased item in a commercial transaction settled by the mobile payment system; A second acquisition means for acquiring a total amount of the commercial transaction calculated at the time of payment via the mobile payment system; a processing means for processing merchandise sales data of a commercial transaction settled by the mobile payment system based on the data relating to the purchased merchandise acquired by the first acquisition means; A calculation means for calculating a total amount of a commercial transaction based on the product sales data processed by the processing means; and an output means for outputting the difference between the total amount acquired by the second acquisition means and the total amount calculated by the calculation means; A program to function as a
Citation Information
Patent Citations
Self-payment method using a portable device
JP2013541107A
Tenant management server and program
JP2019067188A
