Information processor and program

Abstract

To provide an information processor and a program capable of flexibly handling vouchers.SOLUTION: The information processor includes: reception means configured to receive an input of a use condition related to a usage of vouchers according to each of vouchers usable in payment for a merchandise or exchange for a merchandise; generation means configured to generate master data associating the inputted use condition with the type of vouchers; and registration means configured to register the master data generated by the generation means in a storage part to be referenced by a store terminal selling the merchandise at a store.SELECTED DRAWING: Figure 15

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing apparatus and a program.

Background Art

[0002] Conventionally, in stores such as supermarkets and department stores, employees such as store clerks and workers (hereinafter also referred to as store clerks, etc.) operate a POS terminal or the like to register and settle the products purchased by customers. In recent years, there are also types that can be operated by the customers themselves. For example, there are forms called semi-self where a store clerk registers the products and the customer settles the registered products, and forms called full-self where the customer registers and settles the products by themselves.

[0003] By the way, in the above-mentioned stores, when paying for products or exchanging them using vouchers such as gift vouchers and coupon vouchers, the store clerks, etc. check the usage conditions such as whether the vouchers are available when the customers use the vouchers.

[0004] Thus, transactions using vouchers are more complicated and time-consuming compared to transactions using cash or the like. In addition, since it is necessary to collect the used vouchers, not only can it not be unmanned, but there is also a current situation where it is a burden on store clerks, etc. Also, in the above-mentioned full-self and semi-self types, it is difficult for store clerks, etc. to check the vouchers, so it has been difficult to perform settlement processing using vouchers.

[0005] Note that conventionally, a technique has been proposed to store the amount data of a service voucher in a portable storage medium when the expiration date of the service voucher has not expired. However, in the conventional technique, There is room for improvement in terms of convenience, such as the usage conditions being limited to the expiration date of the deposit.

Summary of the Invention

Problems to be Solved by the Invention

[0006] The problem to be solved by the present invention is to provide an information processing apparatus and a program capable of flexibly handling securities.

Means for Solving the Problem

[0007] The information processing apparatus according to the embodiment includes: a reception unit that receives an input of usage conditions regarding the use of securities for each type of security that can be used for payment for goods or exchange for goods; a generation unit that generates master data associating the input usage conditions with the type of security; and a registration unit that registers the master data generated by the generation unit in a storage unit that can be referred to by a store terminal that sells the goods.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following embodiments, a form in which a store conducts a transaction for paying for a product or exchanging it for a product based on data obtained by digitizing coupons such as gift certificates and coupon tickets will be described. Note that the present invention is not limited to the embodiments described below.

[0010] FIG. 1 is a diagram showing an example of a settlement system according to an embodiment. As shown in FIG. 1, the settlement system 1 includes a store terminal 10, a head office device 20, and a settlement server 30. The store terminal 10, the head office device 20, and the settlement server 30 are communicably connected to each other via a network N.

[0011] The network N can be used alone or in an appropriate combination, such as the Internet, VPN (Virtual Private Network), LAN (Local Area Network), public communication network, mobile communication network, etc. Note that the number of store terminals 10 connected to the network N is not particularly limited.

[0012] The store terminal 10 is an information processing device used in a store that sells goods, such as a supermarket or a department store. The store terminal 10 is divided into, for example, a reception terminal 11 and a sales data processing device 12. Hereinafter, when the reception terminal 11 and the sales data processing device 12 are not distinguished, they are collectively referred to as the store terminal 10.

[0013] The reception terminal 11 is a device such as an attendant terminal installed at the service counter of the store or a POS (Point Of Sales) terminal.

[0014] The reception terminal 11 executes a charge process that digitizes (dataizes) the vouchers owned by the customer in response to a request from the customer and makes them available for use in paying for goods or exchanging them for goods. Such a charge process can also be described as a purchase process in which the store purchases the vouchers and returns the corresponding price in electronic data to the customer.

[0015] Voucher-like items are paper-based vouchers such as merchandise vouchers, beer vouchers, rice vouchers, gift vouchers, etc., which are used for paying for or exchanging goods. For example, a merchandise voucher has an amount marked on its face, and goods up to that amount can be purchased. Note that there are two types of merchandise vouchers: those that can pay the difference as change when the marked amount is greater than the total amount of the purchased goods (when over-tended), and those that do not pay change. For beer vouchers and rice vouchers, there are those with an amount marked on the face and those without. Also, beer vouchers and rice vouchers may be treated in the same way as merchandise vouchers depending on the operation of the store. For example, since the number of beers that can be purchased with one beer voucher is determined, it may be used for goods other than beer as a merchandise voucher for the amount corresponding to that number. Also, for example, a gift voucher such as an ice cream voucher is a voucher that can be used to exchange for the goods marked on the gift voucher. In addition, voucher-like items can be divided into vouchers that can be used in a store and those that cannot, and the voucher-like items that can be used may vary from store to store.

[0016] The sales data processing device 12 is a sales data processing device such as a POS (Point Of Sales) terminal. The sales data processing device 12 performs sales data processing such as registration processing and settlement processing of the goods purchased by the customer according to the operation of the operator. For example, the sales data processing device 12 can execute settlement processing using the data of voucher-like items digitized in the charge processing of the reception terminal 11, in addition to payment methods such as cash and code settlement. Note that in this embodiment, the operator of the sales data processing device 12 is assumed to be a store clerk or the like of the store, but it is not limited to this, and it may be the customer himself / herself.

[0017] The head office device 20 is an example of an information processing device. The head office device 20 is a terminal device or a server device installed, for example, in the head office of a company that operates a store. The head office device 20 performs settings and management of voucher-like items that can be used in the stores operated by its own company according to the operation of the operator. Note that hereinafter, "using" voucher-like items is also expressed as "using" the voucher-like items.

[0018] The settlement server 30 is an example of a storage unit. The settlement server 30 is installed, for example, in a data center outside the store. By cooperating with the store terminal 10, the settlement server 30 provides a settlement service (prepaid settlement service) using electronic tickets or cash that has been digitized in the charge process. In this embodiment, it is assumed that the settlement server 30 is realized by a single server device, but it is not limited to this, and it may be realized in the form of a cloud server or the like by a plurality of server devices.

[0019] Next, the configurations of the store terminal 10, the headquarters device 20, and the settlement server 30 that make up the settlement system 1 will be described.

[0020] FIG. 2 is a diagram showing an example of the hardware configuration of the store terminal 10. The store terminal 10 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, and a RAM (Random Access Memory) 103.

[0021] The CPU 101 is an example of a processor and comprehensively controls each part of the store terminal 10. The ROM 102 stores various programs. The RAM 103 is a workspace for expanding programs and various data.

[0022] The CPU 101, ROM 102, and RAM 103 are connected via a bus or the like to form a control unit 100 of a computer configuration. In the control unit 100, the CPU 101 operates according to a program stored in the ROM 102 or the storage unit 104 and expanded in the RAM 103, thereby executing various processes.

[0023] The store terminal 10 also includes a storage unit 104, a display unit 105, an operation unit 106, a reading unit 107, an imaging unit 108, a printing unit 109, and a communication unit 110, etc.

[0024] The storage unit 104 has a storage medium such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory, and maintains the stored content even when the power is turned off. The storage unit 104 stores programs that can be executed by the CPU 101 and various setting information. For example, the storage unit 204 stores the company code of the company operating its own store. The company code is a company identifier that can identify each company.

[0025] In addition, the storage unit 104 stores a product master. The product master is a data table for storing and managing information related to products sold in the store. The product master stores product information such as the product name, unit price, and classification code in association with a product identifier (hereinafter also referred to as a product code) that can identify the product. As the product code, for example, a JAN (Japan Article Number) code or the like can be used. It is assumed that the product code of each product sold in the store is attached in the form of a code symbol such as a barcode.

[0026] The display unit 105 is a display device such as an LCD (Liquid Crystal Display). The display unit 105 displays various information under the control of the CPU 101. The operation unit 106 is an input device such as a keyboard or a pointing device. The operation unit 106 outputs the operation content input via the input device to the CPU 101. Note that the operation unit 106 may be a touch panel provided on the display unit 105.

[0027] The reading unit 107 is a reading device that reads information from various media. For example, the reading unit 107 is a code scanner that reads information from code symbols such as barcodes and two-dimensional codes. Also, for example, the reading unit 107 is a magnetic card reader that reads information from a card medium such as a magnetic card.

[0028] The imaging unit 108 is a digital camera having an image sensor such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor). The imaging unit 108 is used, for example, to read information displayed on the face of bills. Also, the imaging unit 108 may be used to read a code symbol.

[0029] The printing unit 109 is a printing device such as a thermal printer. Under the control of the CPU 101, the printing unit 109 issues a sheet of paper (hereinafter also referred to as a receipt) on which details of bills charged in the charge process described later, breakdowns of transactions, etc. are printed.

[0030] The communication unit 110 is a wired or wireless communication interface connectable to the network N. The communication unit 110 communicates with external devices such as the head office device 20 and the settlement server 30 via the network N.

[0031] FIG. 3 is a diagram showing an example of the hardware configuration of the head office device 20. The head office device 20 includes a CPU 201, a ROM 202, and a RAM 203.

[0032] The CPU 201 is an example of a processor and comprehensively controls each part of the head office device 20. The ROM 202 stores various programs. The RAM 203 is a workspace for developing programs and various data.

[0033] The CPU 201, the ROM 202, and the RAM 203 are connected via a bus or the like and constitute a control unit 200 of a computer configuration. In the control unit 200, various processes are executed by the CPU 201 operating according to a program stored in the ROM 202 or the storage unit 204 and developed in the RAM 203.

[0034] Also, the head office device 20 includes a storage unit 204, a display unit 205, an operation unit 206, and a communication unit 207, etc.

[0035] The storage unit 204 has a storage medium such as an HDD, SSD, or flash memory, and maintains the stored content even when the power is turned off. The storage unit 204 stores programs that can be executed by the CPU 201 and various setting information. In addition, the storage unit 204 stores the company code of the company to which its own main device 20 belongs, etc.

[0036] The display unit 205 is a display device such as an LCD. The display unit 205 displays various information under the control of the CPU 201. The operation unit 206 is an input device such as a keyboard or a pointing device. The operation unit 206 outputs the operation content input via the input device to the CPU 201. Note that the operation unit 206 may be a touch panel provided on the display unit 205.

[0037] The communication unit 207 is a wired or wireless communication interface connectable to the network N. The communication unit 207 communicates with external devices such as the store terminal 10 and the payment server 30 via the network N.

[0038] FIG. 4 is a diagram showing an example of the hardware configuration of the payment server 30. The payment server 30 includes a CPU 301, a ROM 302, and a RAM 303.

[0039] The CPU 301 is an example of a processor and comprehensively controls each part of the payment server 30. The ROM 302 stores various programs. The RAM 303 is a workspace for expanding programs and various data.

[0040] The CPU 301, ROM 302, and RAM 303 are connected via a bus or the like and constitute a control unit 300 of a computer configuration. In the control unit 300, the CPU 301 operates according to a program stored in the ROM 302 or the storage unit 304 and expanded in the RAM 303, thereby executing various processes.

[0041] In addition, the payment server 30 includes a storage unit 304, a communication unit 305, etc.

[0042] The storage unit 304 has a storage medium such as an HDD, SSD, or flash memory, and maintains the stored content even when the power is turned off. The storage unit 304 stores programs that can be executed by the CPU 301 and various setting information.

[0043] In addition, the storage unit 304 stores a ticket master 3041 and a balance management table 3042. The ticket master 3041 is a data table or database for storing and managing various setting information related to the use of tickets. Also, the balance management table 3042 is a data table or database for storing and managing information related to the balance of electronic cash or tickets (hereinafter also referred to as the recharge balance) of customers (hereinafter also referred to as members) who use the prepaid payment service. Hereinafter, storing the information of electronic cash or tickets in the balance management table 3042 is also referred to as recharge.

[0044] FIG. 5 is a diagram showing an example of the data configuration of the ticket master 3041. As shown in FIG. 5, the ticket master 3041 stores one or more ticket master data in association with the company code, for example. The ticket master data is created for each type of ticket. For example, when a company handles multiple types of tickets, a plurality of ticket master data is registered in the ticket master 3041 in association with the company code of the company.

[0045] The ticket master data has, for example, ticket basic information and usage condition information. The ticket basic information holds information about the ticket. The ticket basic information includes, for example, ticket ID, ticket name, ticket face image, issuer information, billing destination information, and presence or absence of expiration date, etc.

[0046] The voucher ID is identification information capable of identifying the type of vouchers. The voucher name is information indicating the name of the vouchers. The voucher surface image is image data representing the surface of the vouchers. The issuer information includes information regarding the issuer who issues the vouchers. For example, the issuer information includes the name and contact information of the issuer. The claim destination information is information indicating the destination to which the payment amount generated by the use of the vouchers is claimed. The presence or absence of an expiration date is binary information indicating whether there is an expiration date for the vouchers.

[0047] The usage condition information holds various settings related to the use of the vouchers corresponding to the voucher ID in the basic voucher information. The usage condition information can set items such as usage permission information, usage price, setting of the presence or absence of change, specified conditions for purchased goods, specified conditions for exchanged goods, etc.

[0048] The usage permission information is binary setting information indicating whether the vouchers can be used in the store. For example, when the use of the vouchers is permitted, "usable" is set in the usage permission information. On the other hand, when the vouchers are made unusable, "not usable" is set in the usage permission information.

[0049] The usage price is setting information that defines the amount that becomes the price for the use of the vouchers. Here, the use of the vouchers means both the process of digitizing the vouchers in the recharge process and the use of the digitized vouchers. For example, for a merchandise voucher, etc., the amount corresponding to the face value of the merchandise voucher is set as the usage price. As an example, for a 1000-yen merchandise voucher, the usage price "1000 yen" is set. Note that when the specified conditions for exchanged goods described later are set, since the price of the goods to be exchanged may vary depending on the store and the date, it is preferable to set the usage price as a blank, 0 yen, etc. and invalidate it.

[0050] The change availability setting is setting information that defines whether, when there is an over-tend (i.e., the amount of vouchers used for payment of goods is greater than the total amount of the purchased goods), the difference is paid as change. For example, when change is to be paid in case of over-tend, "change available" is set in the change availability setting. On the other hand, when change is not to be paid in case of over-tend, "no change" is set in the change availability setting.

[0051] For the purchased goods specified conditions, the conditions for the goods that can be purchased are set. For example, when any goods can be purchased, "no specification" is set in the purchased goods specified conditions. Also, when specifying the goods that can be purchased, the classification code and product code of the target goods (hereinafter also referred to as target goods) are set in the purchased goods specified conditions. For example, for vouchers issued for the purpose of purchasing goods of a specific classification such as beer vouchers, the classification code and product code indicating the classification and product are set in the purchased goods specified conditions.

[0052] Also, when specifying the number of target goods to be purchased, the specified number may be included and set in the purchased goods specified conditions. Also, information specifying the applicable range that can be covered by vouchers, that is, whether the goods that can be paid with vouchers are limited to the target goods or include all goods including goods other than the target goods, may be included and set in the purchased goods specified conditions, etc. In the case where there are multiple target goods, the purchased goods specified conditions are registered for each target good.

[0053] For the exchange goods specified conditions, the conditions for the goods that can be exchanged (traded) for vouchers are set. The exchange goods specified conditions are set, for example, for gift vouchers (e.g., ice cream vouchers, etc.) issued for the purpose of exchanging for specific goods. When specifying the goods that can be exchanged, the classification code and product code of the target goods (hereinafter also referred to as exchange goods) are set in the exchange goods specified conditions. In the case where there are multiple exchange goods, the exchange goods specified conditions are registered for each exchange good.

[0054] FIG. 6 is a diagram showing an example of the data configuration of the balance management table 3042. As shown in FIG. 6, the balance management table 3042 stores balance information such as charge type, balance, expiration date, and number of sheets in association with the member ID of each member.

[0055] Here, the member ID is an example of a customer identifier that can identify a customer. The member ID is, for example, a customer identifier assigned in units of companies or stores. Note that the member ID may be a customer identifier that can be used among multiple companies.

[0056] The charge type is information indicating the charge type of cash or vouchers. For example, when a charge process of converting cash into electronic form (electronic money) is performed, the charge type such as "cash" is set. Also, when a charge process of converting vouchers into electronic form is performed, the "voucher ID" or "voucher name" that can identify the type of the vouchers is set as the charge type.

[0057] The balance stores the charged balance. For example, when the charge type is cash, the total amount of the charged cash is stored as the balance. Note that in this embodiment, the balance of vouchers is not used, and the remaining amount of vouchers is managed based on the number of vouchers described later and the usage price stored in the voucher master 3041. However, the balance management of vouchers is not limited to this form, and a configuration may be adopted in which the amount obtained by multiplying the usage price by the number of sheets is stored as the balance of vouchers.

[0058] The expiration date stores the expiration date of the charged vouchers. Here, the expiration date is information indicating the date (year, month, and day) on which the vouchers can be used. The expiration date is printed on the face of the vouchers, for example. The number of sheets stores the number of the charged vouchers. Specifically, the number of vouchers with the same voucher ID and expiration date is stored. Note that the combination of the voucher ID and the expiration date can also be regarded as information indicating the type of the vouchers.

[0059] Returning to FIG. 4, the communication unit 305 is a wired or wireless communication interface that can be connected to the network N. The communication unit 305 communicates with external devices such as the store terminal 10 and the head office device 20 via the network N.

[0060] Next, with reference to FIG. 7, the functional configurations of the store terminal 10, the head office device 20, and the settlement server 30 will be described. FIG. 7 is a diagram showing an example of the functional configurations of the reception terminal 11, the sales data processing device 12, the head office device 20, and the settlement server 30. The functional configurations provided in each of the reception terminal 11, the sales data processing device 12, the head office device 20, and the settlement server 30 are realized, for example, by the processor of each device operating according to a program stored in the ROM or the storage unit. Note that some or all of the functional configurations provided in each device may be realized by a hardware configuration such as a dedicated circuit.

[0061] First, the functional configuration related to the management of the coupon master data registered in the coupon master 3041 will be described. As shown in FIG. 7, the head office device 20 includes a coupon setting processing unit 211 as a functional configuration. Further, the settlement server 30 includes a coupon master management unit 311 as a functional configuration.

[0062] The coupon setting processing unit 211 of the head office device 20 is an example of a reception means, a generation means, and a registration means. The coupon setting processing unit 211 executes processing related to the setting or reference of the coupon master data related to its own company in cooperation with the coupon master management unit 311 of the settlement server 30.

[0063] Specifically, the coupon setting processing unit 211 obtains information for referring to or setting the coupon master data from the settlement server 30 by transmitting an access request instructing the company code of its own company to the settlement server 30. Note that the coupon setting processing unit 211 shall perform communication with the settlement server 30 including the company code of its own company even after communication with the settlement server 30 is established by transmitting the access request.

[0064] The voucher master management unit 311 of the settlement server 30 executes processes related to the setting or reference of voucher master data by cooperating with the voucher setting processing unit 211 of the head office device 20. When the voucher master management unit 311 of the settlement server 30 receives an access request specifying a company code from the head office device 20, it provides the head office device 20 of the access source with a screen (or information for displaying the screen) that supports the setting and reference of voucher master data.

[0065] Specifically, when the voucher master management unit 311 receives an access request from the head office device 20, it searches for voucher master data related to the company code specified in the access request from the voucher master 3041. If the corresponding voucher master data does not exist in the voucher master 3041, the voucher master management unit 311 of the settlement server 30 provides the head office device 20 with a screen (hereinafter also referred to as a voucher master creation screen) for assisting in creating voucher master data.

[0066] Note that the voucher master management unit 311 may perform a process of authenticating the head office device 20 of the access source based on the password transmitted from the head office device 20 together with the company code. In this case, the voucher master management unit 311 may previously store in the storage unit 304 or the like an access management table associating the company code and the password, and perform authentication on the head office device 20 based on the access management table. Also, in the head office device 20, when accessing the settlement server 30, a set of the company code and the password shall be transmitted.

[0067] When the voucher master creation screen is provided from the settlement server 30, the voucher setting processing unit 211 of the head office device 20 causes the display unit 205 to display the voucher master creation screen.

[0068] FIG. 8 is a diagram showing an example of the voucher master creation screen displayed on the head office device 20. As shown in FIG. 8, the voucher master creation screen A is provided with input fields for setting various items that can be set in the voucher master 3041.

[0069] Specifically, the ticket master creation screen A is provided with an input field Aa for entering the company code. Note that the ticket master management unit 311 of the settlement server 30 may provide the ticket master creation screen A with the company code specified in the access request entered in the input field Aa.

[0070] In addition, the ticket master creation screen A is respectively provided with input fields Ab to Ag for setting the ticket ID, ticket name, ticket face image, issuer information, billing destination information, and presence or absence of expiration date.

[0071] In addition, the ticket master creation screen A is provided with an input field Ah for setting availability information. Also, the ticket master creation screen A is provided with input fields Ai to Al for setting various usage conditions. The input field Ai is an input field for setting the usage price. The input field Aj is an input field for setting the presence or absence of change. The input field Ak is an input field for setting the target product designation conditions. The input field Al is an input field for setting the exchange product designation conditions.

[0072] Here, it is possible to input the classification code, product code, specified quantity, application range, etc. of the target product in the input field Ak. Also, it is possible to input the classification code, product code, specified quantity, etc. of the exchange product in the input field Al. Note that the addition (or deletion) of the input field Ak and the input field Al is to be performed in response to the operation of adding (or deleting) the target product or the exchange product.

[0073] In addition, the ticket master creation screen A is provided with a registration button Am. The registration button Am is an operator for instructing the registration of the ticket master data.

[0074] The operator of the head office device 20 inputs various settings related to the use of the vouchers into the input fields Aa to Al based on the voucher master creation screen A displayed on the display unit 205. For example, the operator makes settings for the vouchers that are permitted to be used in the stores operated by their own company. Then, after making various settings related to the use of the vouchers, the operator operates the registration button Am. When the voucher setting processing unit 211 of the head office device 20 receives the operation of the registration button Am, it generates the setting contents input in each item of the voucher master creation screen A as voucher master data. Then, the voucher setting processing unit 211 registers the generated voucher master data in the settlement server 30 by transmitting the voucher master data to the settlement server 30.

[0075] On the other hand, when the voucher master management unit 311 of the settlement server 30 receives the voucher master data from the head office device 20, it stores the received voucher master data in the voucher master 3041. As a result, new voucher master data is registered in the voucher master 3041.

[0076] In FIG. 8, among the voucher master data, the voucher basic information (input fields Ab to Ag) and the usage condition information (input fields Ah to Al) are input by the operator of the head office device 20. However, the voucher master management unit 311 of the settlement server 30 may provide the head office device 20 with information for assisting in the input of the voucher basic information and the usage condition information. For example, the voucher master management unit 311 may store in advance template data that holds setting values serving as the prototypes of the items of the voucher basic information and the usage condition information for each voucher ID, and use the template data to assist in the input of the voucher basic information and the usage condition information.

[0077] In this case, for example, the ticket master management unit 311 reads the template data corresponding to the ticket ID on the condition that the ticket ID is entered in the input field Ab of the ticket master creation screen A, and may display the set values of each item included in the template data in each of the input fields Ab to Ag and the input fields Ah to Al. As a result, the operator of the main unit device 20 can create ticket master data by checking or editing the set values based on the set values of the template data displayed on the ticket master creation screen A. Therefore, the ticket master management unit 311 can assist in creating ticket master data.

[0078] Returning to FIG. 7, when the ticket master data related to the company code specified in the access request exists in the ticket master 3041, the ticket master management unit 311 of the settlement server 30 reads out the corresponding ticket master data from the ticket master 3041. Then, the ticket master management unit 311 of the settlement server 30 provides a screen representing the read ticket master data (hereinafter also referred to as a ticket master screen) to the main unit device 20.

[0079] When the ticket master screen is provided from the settlement server 30, the ticket setting processing unit 211 of the main unit device 20 causes the display unit 205 to display the ticket master screen.

[0080] FIG. 9 is a diagram showing an example of the ticket master screen displayed by the main unit device 20. As shown in FIG. 9, the ticket master screen B is displayed in a screen configuration similar to that of the ticket master creation screen A, for example. Specifically, on the ticket master screen B, the set contents entered in the input fields Aa to Al on the ticket master creation screen A are displayed in the corresponding input fields Ba to Bl. As a result, the operator of the main unit device 20 can check the set contents of the set ticket master data by looking at the ticket master screen B.

[0081] Also, on the ticket master screen B, it is also possible to edit the setting contents of the input fields Ba to Bk. For example, the operator of the headquarters device 20 can change the usage conditions of the tickets. Note that some items such as the company code and ticket ID may not be editable.

[0082] In addition, the ticket master screen B is provided with a setting change button Bm, a switching button Bn, a deletion button Bo, and the like.

[0083] The setting change button Bm is an operator for instructing the change of the ticket master data. When the operator of the headquarters device 20 edits the setting contents of the ticket master data, after the editing, by operating the setting change button Bm, the edited setting contents are reflected in the ticket master data. In this case, when the ticket setting processing unit 211 of the headquarters device 20 receives the operation of the setting change button Bm, it generates update ticket master data from the setting contents of each item displayed on the ticket master screen B. Then, the ticket setting processing unit 211 registers the generated update ticket master data in the settlement server 30 by transmitting it to the settlement server 30.

[0084] Also, the ticket setting processing unit 211 of the headquarters device 20 may generate the setting contents of the edited items among the items displayed on the ticket master screen B as update ticket master data and transmit it to the settlement server 30. In the latter case, the ticket setting processing unit 211 transmits the company code and ticket ID together with the update ticket master data.

[0085] When the ticket master management unit 311 of the settlement server 30 receives the update ticket master data from the headquarters device 20, it updates the ticket master data by reflecting the setting contents of the ticket master data in the existing ticket master data. As a result, the ticket master data after the setting change is stored in the ticket master 3041.

[0086] The switching button Bn is an operator for switching the voucher master data to be displayed when a plurality of voucher master data are registered in association with the same company code. When the operator of the head office device 20 wants to switch the voucher master data to be displayed, the operator operates the switching button Bn. When the voucher setting processing unit 211 of the head office device 20 receives the operation of the switching button Bn, it instructs the settlement server 30 to switch the voucher master data.

[0087] When the voucher master management unit 311 of the settlement server 30 receives an instruction to switch the voucher master data from the head office device 20, it switches the voucher master data according to the instruction and transmits it. Here, FIG. 9 shows an example in which a switching button Bn for instructing switching in the "next" or "previous" direction is provided. In this case, when the voucher master management unit 311 receives an instruction to switch in the "previous" direction by operating the switching button Bn in the "previous" direction, it switches to the voucher master data with the previous display order and transmits it to the head office device 20. Further, when the voucher master management unit 311 receives an instruction to switch in the "next" direction by operating the switching button Bn in the "next" direction, it switches to the voucher master data with the next display order and transmits it to the head office device 20. Here, the display order of the voucher master data is not particularly limited, and it can be arbitrarily set, for example, in the order in which the voucher master data are registered or in ascending order of the voucher ID.

[0088] Thereby, the operator of the head office device 20 can confirm the setting contents of a plurality of voucher master data associated with the company code of his / her own company while switching the voucher master data.

[0089] Note that the method of switching the voucher master data is not limited to this. For example, the voucher master management unit 311 may provide the head office device 20 with a screen on which the voucher ID and the voucher master data can be selected according to the operation of the switching button Bn or the like, and provide the head office device 20 with the voucher master screen of the voucher master data selected on the screen.

[0090] The deletion button Bo is an operator for instructing the deletion of the coupon master data. When the operator of the head office device 20 wants to delete the displayed coupon master data, the operator operates the deletion button Bo. When the coupon setting processing unit 211 of the head office device 20 receives the operation of the deletion button Bo, it instructs the settlement server 30 to delete the displayed coupon master data. Specifically, the coupon setting processing unit 211 instructs the settlement server 30 of the coupon ID to be deleted.

[0091] When the coupon master management unit 311 of the settlement server 30 receives the deletion instruction of the coupon master data from the head office device 20, it deletes the instructed coupon master data from the coupon master 3041. Specifically, the coupon master management unit 311 deletes the coupon master data corresponding to the coupon ID instructed by the deletion instruction among the coupon master data stored in the coupon master 3041 in association with the company code of the head office device 20.

[0092] Thereby, the operator of the head office device 20 can delete the desired coupon master data among the coupon master data associated with the company code of its own company.

[0093] In addition, when the coupon setting processing unit 211 of the head office device 20 receives an operation instruction for creating new coupon master data via an operator (not shown), it instructs the settlement server 30 to create new coupon master data. In this case, the coupon master management unit 311 of the settlement server 30 provides the above-described coupon master creation screen to the head office device 20. The operator for instructing the creation of new coupon master data may be provided on the coupon master screen B.

[0094] Next, the functional configuration related to the management of the remaining recharge amount of the coupon will be described. As shown in FIG. 7, the reception terminal 11 includes a member information acquisition unit 111 and a recharge processing unit 112 as functional configurations. The settlement server 30 includes a recharge balance management unit 312 as a functional configuration.

[0095] The member information acquisition unit 111 of the reception terminal 11 executes a process for acquiring the member information of a customer who charges or has charged vouchers. For example, the member information acquisition unit 111 acquires the member ID of the customer from the code symbol or magnetic data attached to the member card held by the customer via the reading unit 107 or the like. Note that the member information acquisition unit 111 may acquire the member ID input via the operation unit 106.

[0096] The charge processing unit 112 of the reception terminal 11 executes a process related to the confirmation of the charge balance of vouchers or the charge of vouchers by cooperating with the charge balance management unit 312 of the settlement server 30.

[0097] Specifically, the charge processing unit 112 transmits a balance inquiry request instructing the member information (member ID) of the customer acquired by the member information acquisition unit 111 and the company code related to its own store to the settlement server 30, and thereby acquires balance information indicating the charge balance stored in association with the member ID of the customer from the settlement server 30. When the balance information includes the balance of vouchers, the charge processing unit 112 acquires voucher master data corresponding to the type of the vouchers from the settlement server 30. Then, the charge processing unit 112 causes the display unit 105 to display a screen based on the acquired balance information and voucher master data.

[0098] In addition, the charge processing unit 112 acquires voucher information including information capable of specifying the type of the vouchers to be charged from the vouchers to be charged via the imaging unit 108 or the like. For example, the charge processing unit 112 uses a known character recognition technology or the like to acquire information (voucher ID, voucher name) capable of specifying the type of the vouchers and voucher information such as the expiration date from the character string on the voucher surface of the vouchers imaged by the imaging unit 108. Also, for example, the charge processing unit 112 uses a known image recognition technology or the like to acquire information capable of specifying the type of the vouchers and voucher information such as the expiration date from the image of the voucher surface of the vouchers imaged by the imaging unit 108. Note that the charge processing unit 112 may acquire the voucher information input by an operator via the operation unit 106.

[0099] In addition, when the charge processing unit 112 of the reception terminal 11 acquires the ticket information of the tickets to be charged, it transmits a usage availability confirmation request instructing the ticket ID included in the acquired ticket information and the company code stored in the storage unit 104 of its own device to the settlement server 30.

[0100] On the other hand, when the charge balance management unit 312 of the settlement server 30 receives a balance inquiry request from the reception terminal 11, it reads out the balance information associated with the member ID indicated in the balance inquiry request from the balance management table 3042 and transmits it to the requesting reception terminal 11 as response information. Further, when the balance information of the tickets is included in the read balance information, that is, when the ticket ID is included, the charge balance management unit 312 of the settlement server 30 reads out the ticket master data corresponding to the combination of the company code and the ticket ID indicated in the balance inquiry request from the ticket master 3041 and includes it in the response information and transmits it to the requesting reception terminal 11.

[0101] In addition, when the charge balance management unit 312 of the settlement server 30 receives a usage availability confirmation request instructing the company code and the ticket ID from the head office device 20, it searches the ticket master 3041 for the ticket master data corresponding to the combination of the company code and the ticket ID. Then, the charge balance management unit 312 determines the usage availability based on the search result of the ticket master data or the set value of the usage availability information included in the searched ticket master data, and transmits response information according to the determination result to the requesting reception terminal 11.

[0102] For example, when the ticket master data corresponding to the combination of the company code and the ticket ID does not exist in the ticket master 3041, the charge balance management unit 312 determines that it is not available. Also, for example, when the ticket master data corresponding to the combination of the company code and the ticket ID exists and the set value of the usage availability information included in the ticket master data is not available, the charge balance management unit 312 determines that it is not available. When the charge balance management unit 312 determines that it is not available, it transmits response information indicating that to the reception terminal 11.

[0103] Also, for example, when there is stored value master data corresponding to a combination of a company code and a voucher ID in the stored value master data, and the setting value of the availability information included in the stored value master data is available, the charge balance management unit 312 determines that it is available. When the charge balance management unit 312 determines that it is available, it transmits response information indicating that fact to the reception terminal 11. Also, in this case, the charge balance management unit 312 reads out the retrieved stored value master data from the stored value master 3041 and transmits it to the reception terminal 11 included in the response information.

[0104] When the charge processing unit 112 of the reception terminal 11 obtains response information indicating non-availability as a response to the availability confirmation request from the settlement server 30, it displays on the display unit 105 a screen notifying that the use of the voucher is not permitted, and suppresses the charging of the voucher.

[0105] Also, when the charge processing unit 112 of the reception terminal 11 obtains response information indicating availability as a response to the availability confirmation request from the settlement server 30, it determines that the charging of the voucher is possible. In this case, the charge processing unit 112 executes a process for charging the voucher based on the stored value master data and the like provided from the settlement server 30.

[0106] Specifically, the charge processing unit 112 causes the display unit 105 of the screen to display detailed information including the expiration date, usage price, usage conditions, etc. of the voucher to be charged based on the voucher information related to the voucher to be charged and the stored value master data obtained from the settlement server 30. Also, when the charge processing unit 112 reads a plurality of vouchers, it causes the display unit 105 to display detailed information regarding each voucher. Then, the charge processing unit 112 executes a charge process for the voucher related to the specified detailed information according to the operation of the operator.

[0107] Hereinafter, an example of the screen displayed by the charge processing unit 112 will be described. Hereinafter, an example will be described in which after displaying a screen based on the balance information (hereinafter also referred to as a balance confirmation screen), a screen related to the charging of the voucher (hereinafter also referred to as a detailed screen) is displayed.

[0108] FIG. 10 is a diagram showing an example of a balance screen displayed by the reception terminal 11. The balance confirmation screen is an example of a screen displayed by the charge processing unit 112 based on, for example, balance information provided from the settlement server 30.

[0109] As shown in FIG. 10, the balance confirmation screen C has a member ID display area Ca, a cash balance display area Cb, and a coupon balance display area Cc. In the member ID display area Ca, the member ID acquired by the member information acquisition unit 111 is displayed.

[0110] In the cash balance display area Cb, among the balance information acquired from the settlement server 30, the balance information with the charge type being cash is displayed. In FIG. 10, it shows that there is a balance of ¥20,000 as the cash charge type.

[0111] In the coupon balance display area Cc, among the balance information acquired from the settlement server 30, the balance information with the charge type being coupons is displayed. For example, in the coupon balance display area Cc, for each coupon with the same coupon ID and expiration date, the balance and the content of the coupon master data are displayed in association. FIG. 10 shows an example of displaying 4 pieces of coupons.

[0112] Specifically, in the coupon balance display area Cc, for each coupon with the same coupon ID and expiration date, the expiration date, the coupon type of the coupon (coupon ID, coupon name), the balance, the presence or absence of change, the usage conditions, and the cumulative balance are displayed in association. Here, the balance indicates the amount obtained by multiplying the number of coupons with the same coupon ID and expiration date by the usage consideration set in the coupon master data of the coupon ID. Also, the presence or absence of change and the usage conditions indicate the set values of the change presence or absence information and the usage condition information set in the coupon master data. Also, the cumulative balance indicates the cumulative result of accumulating the balances of 4 pieces of coupons in the order of display of the coupons.

[0113] By viewing the balance screen, the operator who operates the reception terminal 11 can easily check the balance of the cash and vouchers that the customer has charged so far. Also, by showing the balance screen to the customer, the operator can have the customer check the balance of the cash and vouchers that the customer has charged so far.

[0114] In the voucher balance display area Cc, the display order of the vouchers is not particularly limited and can be set arbitrarily. For example, the charge processing unit 112 may display the vouchers in ascending order of the period from the current date to the expiration date, starting from the earliest. Also, for example, the charge processing unit 112 may display the vouchers in ascending (or descending) order of the voucher ID. Note that the display order of the balance information is preferably switchable according to an operation.

[0115] Also, for vouchers whose period from the current date to the expiration date is less than a threshold value (for example, 30 days), the charge processing unit 112 may emphasize and display items such as the expiration date to notify that the expiration date is approaching. Thereby, the charge processing unit 112 can make the operator and the customer recognize the vouchers whose expiration date is approaching, and thus can promote the use of the vouchers.

[0116] Also, the balance confirmation screen C is provided with a print button Cd and a buyback service button Ce. The print button Cd is an operator for instructing to output the content of the balance of the cash and vouchers displayed on the balance confirmation screen C from the printing unit 109. For example, when the operator of the reception terminal 11 is requested by the customer to print the balance information, the operator operates the print button Cd to instruct the printing of the balance information. When the charge processing unit 112 receives the operation of the print button Cd, the charge processing unit 112 causes the printing unit 109 to print the content of the balance information displayed on the balance confirmation screen C.

[0117] Thereby, the charge processing unit 112 can improve the convenience related to balance confirmation because the customer can check the balance of the cash and vouchers that the customer has charged even after leaving the reception terminal 11.

[0118] The redemption service button Ce is an operator for instructing the charging of vouchers. For example, when a customer requests the charging of vouchers, the operator of the reception terminal 11 operates the redemption service button Ce to instruct the charging of vouchers.

[0119] When the charge processing unit 112 receives the operation of the redemption service button Ce, it cooperates with the imaging unit 108, etc., to acquire voucher information related to the vouchers to be charged. Further, the charge processing unit 112 inquires of the settlement server 30 whether the vouchers corresponding to the voucher IDs included in the acquired voucher information are available for use. When the vouchers to be charged are available for use, the charge processing unit 112 acquires the voucher master data provided from the settlement server 30 and displays a details screen related to the vouchers to be charged.

[0120] FIG. 11 is a diagram showing an example of the details screen D displayed by the reception terminal 11. As shown in FIG. 11, the details screen D has a member ID display area Da, a details display area Db, and a total display area Dc. The member ID acquired by the member information acquisition unit 111 is displayed in the member ID display area Da.

[0121] Information related to the vouchers to be charged is displayed in the details display area Db. Specifically, as the details information related to the vouchers to be charged, the content of the voucher information read from the vouchers and the content of the voucher master data related to the voucher type of the vouchers are displayed in association with each other. FIG. 11 shows an example in which two types of vouchers are to be charged, and the details information is displayed for each voucher.

[0122] Here, the voucher information corresponds to the voucher type information (voucher ID, voucher name), expiration date, etc. Further, the face image, issuer information, billing destination information, usage price, change availability information, other usage conditions, etc. included in the voucher master data are displayed. When the setting of the expiration date availability included in the voucher master data indicates "yes", the charge processing unit 112 may prompt the confirmation of the expiration date and the input of the expiration date by highlighting and displaying the expiration date column.

[0123] In addition, in each piece of detailed information in the detailed display area Db, a quantity column Dba, a total column Dbb, and a purchase execution check column Dbc are provided. Here, the quantity column Dba is an area for inputting the recharge quantity of the vouchers. For example, when there are multiple vouchers with the same voucher type and expiration date, the operator of the reception terminal 11 inputs the quantity of such vouchers into the quantity column Dba. Further, when the recharge processing unit 112 acquires a plurality of voucher information with the same voucher type and expiration date, it may automatically input the number of acquisitions into the quantity column. Note that the quantity column Dba shall have "1" input as the initial state.

[0124] In the total column Dbb, the amount obtained by multiplying the amount displayed in the usage consideration by the quantity input in the quantity column Dba is displayed.

[0125] In the purchase execution check column Dbc, a checkbox Dbd for selecting whether or not to target the vouchers for recharge processing is provided. When the vouchers shown in the detailed information are to be the target of recharge processing, the operator of the reception terminal 11 checks the checkbox Dbd.

[0126] In the total display area Dc, the total quantity and total amount of the vouchers to be the target of recharge are displayed. Specifically, in the total display area Dc, the total value of the quantities input in the quantity columns Dba of the vouchers for which the checkboxes Dbd are checked and the total value of the amounts displayed in the total columns Dbb are displayed.

[0127] In addition, on the detailed screen D, a batch selection button Dd and a purchase execution button De are provided. The batch selection button Dd is an operator for checking the checkboxes Dbd provided for each piece of detailed information all at once. When the recharge processing unit 112 receives the operation of the batch selection button Dd, it checks the checkboxes Dbd provided for each piece of detailed information.

[0128] The redemption execution button De is an operator for instructing the execution of the charging process. When the charging processing unit 112 receives the operation of the redemption execution button De, it executes the charging process for the vouchers for which the checkbox Dbd is checked. Specifically, the charging processing unit 112 transmits a charging request instructing the set of voucher IDs, expiration dates, and quantities of the vouchers for which the checkbox Dbd is checked and the member ID displayed in the member ID display area Da to the settlement server 30.

[0129] In addition, when the setting value of the presence or absence of an expiration date is "none", the charging processing unit 112 transmits a charging request with an empty expiration date. Also, even if the presence or absence of an expiration date is set to "yes", when the expiration date is in an empty state, the charging processing unit 112 causes the display unit 105 to display a message prompting the input of the expiration date without transmitting a charging request.

[0130] On the other hand, when the charge balance management unit 312 of the settlement server 30 receives a charging request from the receiving terminal 11, it associates the set of voucher IDs, expiration dates, and quantities indicated in the charging request with the member ID indicated in the charging request and stores them in the balance management table 3042. Also, when vouchers with the same voucher ID and the same expiration date exist in the balance management table 3042, the charge balance management unit 312 adds the quantity included in the charging request to the quantity of the vouchers. As a result, the vouchers of the customer received by the receiving terminal 11 are charged to the balance management table 3042 in a digitized state.

[0131] In addition, after the charging process is completed, the charging processing unit 112 of the receiving terminal 11 may print the details of the charged vouchers on receipt paper or the like via the printing unit 109. Also, it is assumed that the vouchers for which the charging process has been completed are collected by the operator of the receiving terminal 11.

[0132] In addition, the charge processing unit 112 of the reception terminal 11 may perform cash charge processing. In this case, the charge processing unit 112 transmits a charge request including the customer's membership ID and the amount deposited by the customer for charging to the settlement server 30. Further, the charge balance management unit 312 of the settlement server 30 adds the amount included in the charge request to the cash balance corresponding to the membership ID associated with the charge request in the balance management table 3042.

[0133] Next, the functional configuration related to settlement using the charged vouchers will be described. As shown in FIG. 7, the sales data processing device 12 includes a member information acquisition unit 121 and a sales data processing unit 122 as functional configurations. Further, the settlement server 30 includes the charge balance management unit 312 described above as a functional configuration.

[0134] The member information acquisition unit 121 of the sales data processing device 12 has the same function as the member information acquisition unit 111. The sales data processing unit 122 of the sales data processing device 12 performs registration processing and settlement processing of the products purchased by the customer according to the operator's operation.

[0135] Here, the registration processing refers to the processing of acquiring the product code that identifies the product sold in the store and storing (registering) product information such as the product name and price of the product corresponding to the acquired product code in the RAM 103, the storage unit 104, etc. Note that the product information corresponding to the product code is acquired from a product master (not shown). The settlement processing refers to the processing of settling the price of the product based on the product information of the product stored in the registration processing with the amount paid by a payment method such as cash, credit card, vouchers, etc.

[0136] In addition, when the customer settles using the vouchers charged, the operator of the sales data processing device 12 performs an operation for reading the membership ID in order to read the balance information of the customer. For example, the operator performs an operation for reading the membership ID from the membership card etc. presented by the customer. The member information acquisition unit 111 acquires the membership ID according to the operator's operation.

[0137] The sales data processing unit 122 obtains balance information associated with the member ID of the customer from the settlement server 30 by sending a balance inquiry request including the member information (member ID) of the customer obtained by the member information acquisition unit 121 to the settlement server 30. Further, when the balance information includes the balance of cash vouchers, the sales data processing unit 122 obtains the cash voucher type master data corresponding to the type of the cash vouchers from the settlement server 30. Then, the sales data processing unit 122 causes the display unit 105 to display a screen based on the obtained balance information and the cash voucher type master data. Specifically, the sales data processing unit 122 causes the display unit 105 to display a screen (hereinafter also referred to as a balance usage screen) on which the cash vouchers to be used for settlement can be selected.

[0138] On the other hand, when the charge balance management unit 312 of the settlement server 30 receives a balance inquiry request specifying a member ID from the sales data processing device 12, it reads out the balance information associated with the member ID from the balance management table 3042 and transmits it to the head office device 20 that is the request source. Further, when the balance information includes the balance of cash vouchers, the charge balance management unit 312 of the settlement server 30 reads out the cash voucher type master data corresponding to the type of the cash vouchers from the cash voucher type master 3041 and transmits it to the sales data processing device 12 that is the request source together with the balance information.

[0139] FIG. 12 is a diagram showing an example of the balance usage screen displayed by the sales data processing device 12. As shown in FIG. 12, the balance usage screen E has a cash balance display area Ea and a cash voucher balance display area Eb.

[0140] In the cash balance display area Ea, the balance information of which the charge type is cash among the balance information obtained from the settlement server 30 is displayed. In FIG. 12, it shows that there is a balance of ¥20,000 as the cash balance with the charge type being cash.

[0141] In the coupon balance display area Eb, based on the balance information and coupon master data acquired from the settlement server 30, the balance and usage conditions of the charged coupons are displayed as usage candidates. Specifically, in the coupon balance display area Eb, for each coupon with the same coupon ID and expiration date, the expiration date, balance, presence or absence of change, usage conditions, etc. of that coupon are displayed. Here, the balance is a value derived by multiplying the number of coupons included in the balance information by the usage consideration set in the coupon master data of the relevant coupon. For the presence or absence of change and usage conditions, the set values of the change presence or absence information and usage condition information set in the coupon master data are displayed.

[0142] Note that the order in which the usage candidates of coupons are displayed in the coupon balance display area Eb is not particularly limited and can be set arbitrarily. For example, the sales data processing unit 122 may display them in ascending order (or descending order) starting from the earliest period from the current date to the expiration date. Also, for example, the charge processing unit 112 may display them in ascending (or descending) order of coupon ID or balance. Note that it is preferable that the display order of the balance information can be switched according to the operation.

[0143] In addition, for usage candidates whose period from the current date to the expiration date is less than a threshold value (for example, 30 days), the sales data processing unit 122 may display items such as the expiration date in an emphasized manner to notify that the expiration date is approaching. Thereby, the sales data processing unit 122 can make the operator or customer recognize the coupons whose expiration date is approaching, and thus can promote the use of the relevant coupons.

[0144] In addition, a usage check box Ebb is provided in association with each usage candidate in the coupon balance display area Eb. In the usage check box Ebb, a check box Ebc for selecting whether to use the usage candidate is provided. When the operator of the sales data processing device 12 is informed by the customer of a usage candidate for which usage is desired, the operator checks the check box Ebc of the corresponding usage candidate. Here, the operation of the check box Ebc may also be in a form where the customer himself / herself performs it.

[0145] Note that the check of the check box Ebc may be automatically performed instead of manually. In this case, for example, the sales data processing unit 122 may be provided with an automatic check button or the like that instructs to automatically check the check boxes of the usage candidates to be used, and may be configured to select the usage candidates to be used on the condition that the automatic check button is operated. The selection criteria can be arbitrarily set. For example, the sales data processing unit 122 may select vouchers that can pay the price of the product based on the total amount and breakdown of the registered products. Also, the sales data processing unit 122 may preferentially select usage candidates with earlier expiration dates. Also, for example, when there are multiple usage candidates with the same expiration date, the sales data processing unit 122 may preferentially select usage candidates with no change given in the usage conditions. Also, a configuration may be adopted in which a check box is provided for the cash charge type as well.

[0146] Note that in the balance usage screen E of FIG. 12, the presence or absence of use can be selected in units of vouchers with the same voucher ID and expiration date. However, when there are multiple vouchers with the same voucher ID and expiration date, a configuration may be adopted in which the number of vouchers to be used can be specified.

[0147] Also, a use button Ec is provided on the balance usage screen E. The use button Ec is an operator for instructing payment using vouchers for which the check box Ebc is checked. When the sales data processing unit 122 receives an operation of the use button Ec, it executes a settlement process using the vouchers corresponding to the usage candidates for which the check box Ebc is checked. Specifically, the sales data processing unit 122 determines whether it can be used for the transaction to be settled based on the usage conditions of the vouchers for which use is applied by checking the check box Ebc.

[0148] For example, when target products or exchange products are specified as usage conditions, the sales data processing unit 122 determines whether the products registered in the registration process (hereinafter also referred to as purchased products) include the target products or exchange products with the specified classification codes or product codes. In this case, when the target products or exchange products specified are included in the purchased products, the sales data processing unit 122 determines that it is available for use; when the target products or exchange products specified are not included in the purchased products, the sales data processing unit 122 determines that it is not available for use.

[0149] Also, for example, when the number of purchases is specified as a usage condition, the sales data processing unit 122 determines whether the quantity of the purchased products (or the quantity of the target products or exchange products included in the purchased products) meets the specified quantity. In this case, when the quantity of the purchased products meets the specified quantity, the sales data processing unit 122 determines that it is available for use; when the quantity of the purchased products does not meet the specified quantity, the sales data processing unit 122 determines that it is not available for use.

[0150] In addition, when the above-mentioned specifications of target products, exchange products, and purchase quantity are not stipulated in the usage conditions, or when they do not conflict with the prohibited content of the usage conditions, the sales data processing unit 122 determines that it is available for use.

[0151] When the sales data processing unit 122 determines that it is available for use, it executes the settlement process using the vouchers. When it determines that it is not available for use, the sales data processing unit 122 causes the display unit 105 to display a screen notifying that the vouchers corresponding to the checked usage candidates cannot be used in this transaction.

[0152] When the sales data processing unit 122 determines that the vouchers are available for use, it executes the settlement process based on the usage conditions of the vouchers. Specifically, the sales data processing unit 122 determines the applicable range of the vouchers and calculates the change amount based on the usage conditions of the vouchers.

[0153] For example, when the applicable range for which vouchers can be used is defined as a usage condition, the sales data processing unit 122 applies the remaining balance of the vouchers to the payment for products falling within the applicable range. Also, for example, when an exchange product is specified as a usage condition, the sales data processing unit 122 applies the vouchers to the payment for the specified exchange product.

[0154] Also, for example, when no change is set as a usage condition, the sales data processing unit 122 suppresses the calculation of the change amount even in an over-tend state where the remaining balance of the vouchers is greater than the total amount of the products to be purchased.

[0155] Also, when the remaining balance of the vouchers does not reach the total amount of the products to be purchased, the sales data processing unit 122 causes the display unit 105 to display a screen prompting the use of other vouchers or a screen for selecting another payment method such as cash, thereby prompting the selection of a payment method. Then, the sales data processing unit 122 executes settlement processing on the condition that the remaining balance of the vouchers has reached the total amount of the products to be purchased. Note that when there is a remaining balance in the cash recharge type, the sales data processing unit 122 may be configured to automatically apply the remaining balance of the cash to the payment of the shortage amount.

[0156] Note that there is no particular limitation on the handling of change during mixed use, such as when vouchers with change and vouchers without change are mixed and used, or when vouchers without change and other settlement methods are mixed and used. For example, it is preferable to adopt a configuration that allows selection for each company or each store by separately defining the presence or absence of change during mixed use in usage conditions or the like.

[0157] When performing settlement processing using the recharge amount, the sales data processing unit 122 cooperates with the settlement server 30 and executes processing for subtracting the amount of cash or vouchers to be used from the recharge remaining balance. Specifically, the sales data processing unit 122 transmits remaining balance usage information indicating the voucher ID, expiration date, and member ID of the vouchers to be used in the settlement processing to the settlement server 30.

[0158] In the case of a configuration that allows specifying the number of vouchers used, the sales data processing unit 122 transmits the number of vouchers used included in the balance usage information. Also, when the charged amount in cash is used, the sales data processing unit 122 transmits the amount of cash used included in the balance usage information.

[0159] When the balance information is updated in the settlement server 30, the sales data processing unit 122 obtains an approval number, which will be described later, from the settlement server 30 as response information for the balance usage information. Also, the sales data processing unit 122 may obtain the updated balance information together.

[0160] Also, when the settlement process is completed, the sales data processing unit 122 controls the printing unit 109 to cause the printing unit 109 to issue a receipt printed with the details of the transaction. It is preferable to print on the receipt, in addition to the breakdown of the goods registered in the registration process, the total amount of the goods, the breakdown of the amount paid in the settlement process, etc., also the state of the charge balance before and after the settlement process.

[0161] Specifically, the sales data processing unit 122 sets the balances of cash and vouchers displayed on the balance usage screen E as the charge balance before the settlement process, and sets the result obtained by removing the balance used in the settlement process from the charge balance before the settlement process as the charge balance after the settlement process. Then, the sales data processing unit 122 issues a receipt including the charge balances before and after the settlement process, that is, before and after the transaction. When obtaining the updated balance information from the settlement server 30, the sales data processing unit 122 may derive the charge balance after the transaction based on the updated balance information.

[0162] Here, FIGS. 13 and 14 are diagrams showing an example of a receipt issued by the sales data processing apparatus 12. In FIGS. 13 and 14, the breakdown of the goods registered in the registration process is shown omitted.

[0163] As shown in FIG. 13, on the receipt F issued by the sales data processing unit 122, the total amount Fa of the products registered in the registration process, the breakdown Fb of the amount paid in the settlement process, etc. are printed. In the breakdown Fb in FIG. 13, it shows that the coupon Ta with a balance of ¥1,200 and the cash of ¥4,416 were used for the payment of the products. Note that 2024 / 12 / 31 printed in association with the coupon Ta represents the expiration date of the coupon Ta.

[0164] Also, on the receipt F, a balance display area Fc for displaying the customer's charge balance is provided. In the balance display area Fc, member information Fd indicating the member ID, approval number Fe, etc. are printed. Also, in the balance display area Fc, a pre-transaction balance detailed area Ff representing the breakdown of the charge balance before the transaction and a post-transaction balance detailed area Fg representing the breakdown of the charge balance after the transaction are provided. Here, in each of the pre-transaction balance detailed area Ff and the post-transaction balance detailed area Fg, the balance of cash, the balance of each coupon with the same coupon ID and expiration date, the total amount of the balance of cash and coupons, etc. are printed. Note that the content of the post-transaction balance detailed area Fg is obtained by subtracting the coupon Ta with an expiration date of 2024 / 12 / 31 and a balance of ¥1,200 from the content of the pre-transaction balance detailed area Ff.

[0165] As a result, the customer who receives the receipt F can easily confirm the charge balance, expiration date of cash and coupons associated with their own member ID by looking at the receipt F. Also, the customer can easily confirm the transition of the charge balance used in the settlement by looking at the receipt F.

[0166] Note that the form of the receipt F is not limited to that in FIG. 13. For example, as in the receipt F shown in FIG. 14, instead of the pre-transaction balance detailed area Ff and the post-transaction balance detailed area Fg, a pre-transaction balance simple area Fh and a post-transaction balance simple area Fi may be used.

[0167] Here, in the pre-transaction balance simple area Fh and the post-transaction balance simple area Fi, the balances of the vouchers are printed together. Specifically, the total amount of the balances for each voucher with the same voucher ID and expiration date shown in FIG. 13 is printed in a simplified state as the balance of the vouchers. Note that the receipts F shown in FIGS. 13 and 14 represent receipts issued in the same transaction.

[0168] As shown in FIG. 14, even in the simplified receipt F, the customer can easily confirm, by looking at the receipt F, the remaining balance, expiration date, and the transition of the used remaining balance of cash and vouchers associated with their own member ID. Also, when using the receipt F in FIG. 14, compared with the receipt F in FIG. 13, the amount of information to be printed can be reduced, so the usage amount of the receipt paper can be reduced.

[0169] Also, as another form of the receipt issued by the sales data processing unit 122, a receipt printing the post-transaction balance among the pre- and post-transaction balances may be issued. Further, the sales data processing unit 122 may also issue a receipt printing the balance for transactions in which the remaining balance was not used in the settlement process.

[0170] On the other hand, the remaining balance management unit 312 of the settlement server 30 realizes settlement using the remaining balance by cooperating with the sales data processing unit 122 of the sales data processing apparatus 12. Specifically, when the remaining balance management unit 312 receives the remaining balance usage information from the sales data processing apparatus 12, it executes a process for subtracting the amount of cash or vouchers used in the settlement from the remaining balance based on the remaining balance usage information.

[0171] Specifically, the remaining balance management unit 312 executes a process for subtracting the amount of cash or vouchers indicated by the remaining balance usage information from the remaining balance information in the remaining balance management table 3042 related to the member ID indicated by the remaining balance usage information.

[0172] For example, when a set of ticket IDs and expiration dates is indicated in the balance usage information, the charge balance management unit 312 deletes the data corresponding to the set of ticket IDs and expiration dates from the balance information in the balance management table 3042. Also, for example, when the amount of cash is indicated in the balance usage information, the charge balance management unit 312 subtracts the indicated amount from the cash balance in the balance information of the balance management table 3042. Further, for example, when the number of tickets to be used is specified in the balance usage information together with the set of ticket IDs and expiration dates, the charge balance management unit 312 executes a process of subtracting the indicated number of tickets from the number of data in the balance information corresponding to the set of ticket IDs and expiration dates.

[0173] Then, when the charge balance management unit 312 updates the balance information by the above process, it issues an approval number and transmits it as response information to the sales data processing device 12 that transmitted the balance usage information. Here, the approval number is information for notifying that the settlement by the charge balance has been completed, and for example, a unique number is assigned for each settlement.

[0174] Note that the charge balance management unit 312 may transmit the updated balance information to the sales data processing device 12 including it in the response information. In this case, the updated balance information indicates the charge balance after the settlement.

[0175] Next, the processes performed by the store terminal 10, the head office device 20, and the settlement server 30 will be described.

[0176] First, with reference to FIG. 15, an example of the ticket master setting process performed between the head office device 20 and the settlement server 30 will be described. FIG. 15 is a sequence diagram showing an example of the ticket master setting process performed between the head office device 20 and the settlement server 30.

[0177] First, the ticket setting processing unit 211 of the head office device 20 transmits an access request indicating its own company code to the settlement server 30 (step S11).

[0178] When the voucher master management unit 311 of the settlement server 30 receives an access request from the head office device 20, it determines whether voucher master data related to the company code indicated in the access request exists in the voucher master 3041 (step S12).

[0179] Here, when the voucher master data does not exist, the voucher master management unit 311 provides the head office device 20 with a voucher master creation screen for creating a voucher master (step S13). Also, when the voucher master data exists, the voucher master management unit 311 reads out the corresponding voucher master data from the voucher master 3041 and provides the head office device 20 with a voucher master screen representing the voucher master data (step S13).

[0180] When the voucher setting processing unit 211 of the head office device 20 is provided with a voucher master creation screen or a voucher master screen from the settlement server 30, it causes the display unit 205 to display the screen (step S14). Thereby, the operator of the head office device 20 can create voucher master data or edit existing voucher master data based on the screen displayed on the display unit 205.

[0181] When the voucher setting processing unit 211 receives an operation for creating or changing (editing) the setting of the voucher master data (step S15), it transmits the created voucher master data or the voucher master data for change to the settlement server 30 (step S16).

[0182] When the voucher master management unit 311 of the settlement server 30 receives the voucher master data from the head office device 20, it registers or updates the voucher master data by associating the received voucher master data with the company code of the head office device 20 and storing it in the voucher master 3041 (step S17).

[0183] As a result, the voucher master data created by each company will be stored in the voucher master 3041 of the settlement server 30. As described above, the voucher master data stored in the voucher master 3041 is referred to during the charge process of vouchers and the settlement process using vouchers at each store.

[0184] Next, with reference to FIG. 16, an example of the voucher charge process performed between the reception terminal 11 and the settlement server 30 will be described. FIG. 16 is a sequence diagram showing an example of the voucher charge process performed between the reception terminal 11 and the settlement server 30.

[0185] First, when the operator of the reception terminal 11 is requested by a customer to charge vouchers, an operation for starting the voucher charge process is performed. The member information acquisition unit 111 of the reception terminal 11 acquires the customer's member ID from a medium such as a membership card in response to the start operation of the charge process (step S21). When the member ID is acquired in step S21, the charge processing unit 112 of the reception terminal 11 transmits a balance inquiry request instructing the member ID and the company code related to its own store to the settlement server 30 (step S22).

[0186] When the charge balance management unit 312 of the settlement server 30 receives the balance inquiry request, it reads out the balance information associated with the member ID indicated in the balance inquiry request from the balance management table 3042 (step S23). Further, when the read balance information includes a voucher ID, the charge balance management unit 312 reads out the voucher master data corresponding to the pair of the voucher ID and the company code indicated in the balance inquiry request from the voucher master 3041 (step S24). Then, the charge balance management unit 312 transmits the read balance information and voucher master data as response information to the requesting reception terminal 11 (step S25).

[0187] The charge processing unit 112 of the reception terminal 11 causes the remaining balance confirmation screen to be displayed on the display unit 105 based on the response information acquired from the settlement server 30 (step S26). As a result, the operator of the reception terminal 11 or the customer who charges the vouchers can check the current charge remaining balance, expiration date, usage conditions, etc. by viewing the remaining balance confirmation screen.

[0188] Here, when an operator of the reception terminal 11 performs an operation of reading vouchers to be charged or an operation of inputting voucher information, the charge processing unit 112 of the reception terminal 11 acquires voucher information related to the vouchers to be charged (step S27). Next, the charge processing unit 112 transmits a usage availability confirmation request instructing the voucher ID included in the acquired voucher information and the company code related to its own store to the settlement server 30 (step S28).

[0189] When the charge remaining balance management unit 312 of the settlement server 30 receives a usage availability confirmation request from the reception terminal 11, it searches for voucher master data corresponding to the set based on the set of the company code and voucher ID instructed in the usage availability confirmation request from the voucher master 3041 (step S29). Next, the charge remaining balance management unit 312 determines whether the vouchers are available based on the search result of the voucher master data (step S30).

[0190] If it is determined in step S30 that the usage is unavailable, the charge remaining balance management unit 312 of the settlement server 30 transmits response information indicating unavailability to the reception terminal 11 that is the request source (step S31). When the charge processing unit 112 of the reception terminal 11 receives response information indicating unavailability from the settlement server 30, it causes the display unit 105 to display a screen notifying that the vouchers read in step S27 are unavailable (step S32).

[0191] On the one hand, when it is determined that it is available in step S30, the charge balance management unit 312 of the settlement server 30 reads the voucher master data retrieved in step S30 from the voucher master 3041 (step S33). Next, the charge balance management unit 312 includes the voucher master data read in step S33 together with the information indicating availability in the response information and transmits it to the reception terminal 11 (step S34).

[0192] When the charge processing unit 112 of the reception terminal 11 receives the response information indicating availability, based on the voucher master data included in the response information, it causes the display unit 105 to display a details screen showing details regarding the vouchers to be charged (step S35). Here, after the operator of the reception terminal 11 inputs necessary items such as the expiration date and the number of vouchers to be charged, an operation to instruct the execution of the charge is performed.

[0193] When the charge execution is instructed, the charge processing unit 112 of the reception terminal 11 transmits a charge request instructing the set of the voucher ID, expiration date, and number of the vouchers to be charged and the member ID acquired in step S21 to the settlement server 30 (step S36). Also, the charge processing unit 112 of the reception terminal 11 issues a receipt showing the details of the charged vouchers from the printing unit 109 (step S37). Note that in addition to the details of the charged vouchers, the existing balance may be printed on the receipt issued in step S37.

[0194] On the other hand, when the charge balance management unit 312 of the settlement server 30 receives a charge request from the reception terminal 11, it performs the charge of the vouchers by associating and storing in the balance management table 3042 the member ID, voucher ID, expiration date, and the set of the number of vouchers instructed in the charge request (step S38).

[0195] By the above processing, the vouchers brought in by the customer are digitized and managed by the settlement server 30 in association with the customer's member ID.

[0196] Next, with reference to FIG. 17, an example of prepaid settlement processing performed between the sales data processing device 12 and the settlement server 30 will be described. FIG. 17 is a sequence diagram showing an example of settlement processing performed between the sales data processing device 12 and the settlement server 30. Note that as a premise of this processing, it is assumed that the product registration process has been executed in the sales data processing device 12. That is, the product registration process has been executed by a store clerk or the customer himself / herself in the sales data processing device 12, for example, or is in a state where it has been executed by the customer himself / herself using a mobile terminal. Therefore, it is assumed that there is transaction data (data subject to settlement processing) based on the product information of the product stored in the registration process. Also, in this processing, it is assumed that the payment for the product is made using prepaid vouchers.

[0197] When the sales data processing unit 122 of the sales data processing device 12 receives an operation instructing the start of settlement processing for the products registered in one transaction, it starts the settlement processing for the registered products. In such settlement processing, when it receives an operation instructing a payment method using prepaid vouchers, the member information acquisition unit 121 of the sales data processing device 12 acquires the customer's member ID from a medium such as a membership card (step S41).

[0198] When the member ID is acquired in step S41, the sales data processing unit 122 of the sales data processing device 12 transmits a balance inquiry request instructing the member ID and the company code related to its own store to the settlement server 30 (step S42).

[0199] When the charge balance management unit 312 of the settlement server 30 receives a balance inquiry request from the sales data processing device 12, it reads out the balance information associated with the member ID indicated in the balance inquiry request from the balance management table 3042 (step S43). Further, when the read balance information includes a coupon ID, the charge balance management unit 312 reads out the coupon master data corresponding to the pair of the coupon ID and the company code indicated in the balance inquiry request from the coupon master 3041 (step S44). Then, the charge balance management unit 312 transmits the read balance information and the coupon master data to the sales data processing device 12 that is the request source (step S45).

[0200] Based on the information acquired from the settlement server 30, the sales data processing unit 122 of the sales data processing device 12 causes the display unit 105 to display a balance usage screen (step S46). The operator of the sales data processing device 12 or the customer who purchases the product can check the current charge balance, expiration date, usage conditions, etc. by viewing the balance usage screen. Also, the operator of the sales data processing device 12 or the customer who purchases the product can select the coupons to be used for payment.

[0201] When the coupons to be used for payment are selected, the sales data processing unit 122 of the sales data processing device 12 compares the usage conditions of the selected coupons with the details of the product to be settled (the product registered in the registration process) (step S47), and determines whether it is available for use in paying for the product (step S48).

[0202] If it is determined in step S48 that it is not available for use, the sales data processing unit 122 of the sales data processing device 12 displays a screen notifying that the selected coupons cannot be used (step S49). Also, in this case, the sales data processing unit 122 of the sales data processing device 12 prompts a payment method other than the selected coupons by returning the process to step S36 or displaying a screen where other payment methods can be selected.

[0203] If it is determined to be available in step S48, the sales data processing unit 122 of the sales data processing apparatus 12 determines an applicable range for which the coupon can be applied based on the usage conditions of the selected coupon (step S50). Next, the sales data processing unit 122 transmits remaining balance usage information indicating the coupon ID and expiration date of the selected coupon and the member ID to the settlement server 30 in order to apply the selected coupon to the payment or exchange of goods corresponding to the determined applicable range (step S51).

[0204] When the charge remaining balance management unit 312 of the settlement server 30 receives the remaining balance usage information from the sales data processing apparatus 12, it deletes data of the coupon corresponding to the coupon ID and expiration date indicated by the remaining balance usage information from the remaining balance information of the member ID indicated by the remaining balance usage information, etc., and performs settlement (prepaid settlement) using the charge remaining balance (step S52).

[0205] Subsequently, the charge remaining balance management unit 312 of the settlement server 30 issues an approval number (step S53). Further, when the charge remaining balance management unit 312 reads the updated remaining balance information (step S54), it transmits response information including the remaining balance information and the approval number to the sales data processing apparatus 12 (step S55).

[0206] When the sales data processing unit 122 of the sales data processing apparatus 12 receives the response information from the settlement server 30, it issues a receipt indicating the breakdown of the settled transaction and the state of the remaining balance before and after the transaction from the printing unit based on the remaining balance information etc. included in the response information (step S56).

[0207] Note that when there is an unpaid amount at the time when the prepaid settlement is completed, the sales data processing unit 122 of the sales data processing apparatus 12 returns the process to step S36 or displays a screen where other payment methods can be selected, and does not issue a receipt until all the amounts are paid.

[0208] Next, with reference to FIG. 18, the allocation range determination process performed by the sales data processing apparatus 12 will be described. Here, FIG. 18 is a flowchart showing an example of the allocation range determination process performed by the sales data processing apparatus 12. Note that this process corresponds to the process of step S50 in FIG. 17 described above.

[0209] First, the sales data processing unit 122 refers to the usage conditions of the tickets selected on the balance usage screen and determines whether a purchased product is specified (step S61). If a purchased product is specified (step S61; Yes), the sales data processing unit 122 determines whether it is specified that the applicable range in the usage conditions is limited to the target product (step S62). Here, if it is specified that the applicable range is limited to the target product (step S62; Yes), the sales data processing unit 122 allocates the selected tickets to pay for the target product (step S63) and proceeds to step S51 in FIG. 17. Note that in step S63, "allocation" means, for example, adding a predetermined amount (e.g., an amount corresponding to the price of the corresponding target product) or an arbitrary amount to the customer's payment amount as a payment for the product price of the corresponding target product. Also, "allocation" in step S63 may be subtracting a predetermined amount (e.g., an amount corresponding to the price of the corresponding target product) or an arbitrary amount from the total amount of the registered products.

[0210] Also, in step S62, if it is not specified that the applicable range is limited to the target product (step S62; No), the sales data processing unit 122 allocates the selected tickets to pay for the products registered in the registration process (hereinafter also referred to as registered products) (step S64) and proceeds to step S51 in FIG. 17. Note that in step S64, "allocation" means, for example, including the amount of the selected tickets (e.g., the balance) in the customer's payment amount as a payment for the registered products (payment for one transaction). Also, "allocation" in step S64 may be subtracting the amount of the selected tickets from the total amount of the registered products.

[0211] Also, in step S61, when it is determined that no purchased product is specified (step S61; No), the sales data processing unit 122 determines whether an exchange product is specified (step S65). When an exchange product is specified (step S65; Yes), the sales data processing unit 122 appropriates the selected gift certificates for exchange with the exchange product (step S66) and proceeds to step S51 in FIG. 17. Note that, in step S66, "appropriation" means, for example, treating the amount corresponding to the price of the corresponding exchange product as if it had been paid by the customer as a payment for the registered product (payment for one transaction). Also, "appropriation" in step S66 may be to add the amount corresponding to the price of the corresponding target product to the customer's payment amount, or to subtract the amount corresponding to the price of the corresponding target product from the total amount of the registered products.

[0212] Also, in step S65, when it is determined that no exchange product is specified (step S65; No), the sales data processing unit 122 appropriates the selected gift certificates for payment of the registered products (step S67) and proceeds to step S51 in FIG. 17. Note that, in step S67, "appropriation" means, similar to step S64, for example, treating the amount of the selected gift certificates (e.g., balance) as included in the customer's payment amount as a payment for the registered products (payment for one transaction). Also, "appropriation" in step S67 may be to subtract the amount of the selected gift certificates from the total amount of the registered products.

[0213] In this way, in the sales data processing device 12, various gift certificates can be used flexibly by appropriating the gift certificates within the applicable range according to the usage conditions of the gift certificates to be used.

[0214] As described above, in the settlement system 1 of the present embodiment, the usage conditions of the gift certificates set in the headquarters device 20 are stored as gift certificate master data, and based on the gift certificate master data, recharge of the gift certificates, confirmation of the balance of the recharged gift certificates, and use of the recharged gift certificates can be performed at each of the store terminals 10.

[0215] As a result, in the settlement system 1, since transactions can be conducted using electronic vouchers, the handling of vouchers can be made flexible. Also, by making the vouchers electronic and available for use, the burden on store clerks and the like can be reduced, so that the handling of vouchers can be made flexible. Further, in the settlement system 1, since vouchers with various usage conditions can be made electronic and used, it is possible to charge multiple types of vouchers, and the handling of vouchers can be made flexible.

[0216] Also, the reception terminal 11 acquires a member ID that can identify the customer who is the user and a voucher type ID that can identify the type of voucher owned by the customer, and by sending a charge request instructing the member ID and the voucher type ID to the settlement server 30, the member ID and the voucher type ID are stored in the settlement server 30 (balance management table 3042) in association with the usage conditions corresponding to the voucher type ID. Thereby, since the reception terminal 11 can charge vouchers with various usage conditions in association with the corresponding usage conditions, the convenience related to deriving the usage conditions when using the vouchers can be improved. Therefore, the handling of vouchers can be made flexible.

[0217] Also, the reception terminal 11 acquires the expiration date of the voucher included in the voucher information, and stores it in the settlement server 30 (balance management table 3042) in units of voucher information where the types of vouchers are the same and the expiration dates are the same. Thereby, since the charged vouchers can be handled in units of vouchers where the types and expiration dates of the vouchers are the same, the convenience related to the use of the vouchers can be improved, and the handling of the vouchers can be made flexible.

[0218] In addition, the reception terminal 11 acquires the coupon information and coupon master data charged to the settlement server 30 in association with the customer's membership ID based on the membership ID, and displays a balance confirmation screen in which the coupon information is associated with the usage conditions and the like included in the coupon master data. As a result, since the correspondence between the charged coupons and the usage conditions can be easily confirmed, the handling of the coupons can be performed flexibly.

[0219] In addition, the reception terminal 11 displays, as the balance of the charged coupons, the result of multiplying the number (pieces) of the same type of coupons with the same coupon information by the usage price of the coupons. As a result, since the balance of the charged coupons can be confirmed for each type of coupon with the same coupon type and expiration date, the handling of the coupons can be performed flexibly.

[0220] In addition, when the sales data processing device 12 acquires the membership ID of the customer who is the user, it acquires the coupon information and coupon master data of the coupons charged in association with the membership ID from the settlement server 30. Then, the sales data processing device 12 appropriates the coupons charged for the payment of the goods purchased by the customer or the exchange with the goods based on the acquired coupon information and the usage conditions included in the coupon master data. As a result, the sales data processing device 12 can use various types of coupons according to their usage conditions. Therefore, the handling of the coupons can be performed flexibly.

[0221] In addition, the sales data processing device 12 associates and displays the coupon information and coupon master data acquired from the settlement server 30, and accepts the selection of the coupon information to be used from the displayed coupon information. Then, the sales data processing device 12 uses the selected coupon information to pay for the goods purchased by the customer or exchange them with the goods. As a result, the sales data processing device 12 can improve the convenience regarding the use of the charged coupons. Therefore, the handling of the coupons can be performed flexibly.

[0222] In addition, the sales data processing device 12 makes payments for the products purchased by the customer based on the amount of the usage consideration specified in the ticket data master data. Also, the sales data processing device 12 appropriates the tickets charged to the products that are the subject of payment or exchange specified in the ticket data master data among the products purchased by the customer. Further, when there are no products that are the subject of payment or exchange specified in the ticket data master data among the products purchased by the customer, the sales data processing device 12 notifies that the tickets cannot be used. In this way, since the sales data processing device 12 can control the use of tickets based on various usage conditions, it can handle tickets flexibly.

[0223] In addition, the head office device 20 accepts input of usage conditions regarding the use of tickets for each ticket type, and generates ticket data master data associating the input usage conditions with the ticket type of the tickets. Then, the head office device 20 registers the generated ticket data master data in the settlement server 30 that can be referred to by the store terminal 10 of the store that sells the products. Thereby, when the charged tickets are used in the store, the head office device 20 can cause a transaction to be conducted under usage conditions corresponding to the ticket type used. Therefore, in the store, transactions using various ticket types of tickets can be realized using the store terminal 10, so that tickets can be handled flexibly.

[0224] Also, the head office device 20 displays on the display unit 205 a ticket data master creation screen or a ticket data master screen on which usage conditions can be input for a plurality of items related to the usage conditions, and generates ticket data master data based on the input usage conditions. Thereby, since the head office device 20 can support the setting work of the usage conditions, the creation of the ticket data master data can be performed efficiently.

[0225] In addition, as usage conditions, the head office device 20 generates voucher master data including items that define the availability of vouchers, items that define the usage price of vouchers, and items that specify the products to be the objects of payment or exchange. Thereby, since the head office device 20 can control the use of vouchers based on various usage conditions, it can handle vouchers flexibly.

[0226] Note that the above-described embodiments can also be appropriately modified and implemented by changing part of the configurations or functions of the above-described respective devices. Therefore, below, some modification examples according to the above-described embodiments will be described as other embodiments. Note that below, mainly the points different from the above-described embodiments will be described, and detailed descriptions of the points common to the already described content will be omitted. Also, the modification examples described below may be implemented individually or in appropriate combinations.

[0227] (Modification Example 1) In the above-described embodiment, the reception terminal 11 and the sales data processing device 12 were described separately, but the reception terminal 11 and the sales data processing device 12 are not limited to individual devices and may be the same device.

[0228] Also, in the above-described embodiment, the configuration is such that the settlement server 30 stores and manages the voucher master 3041 and the balance management table 3042, but it is not limited to this. The head office device 20 may be configured to store and manage the voucher master 3041 and the balance management table 3042 related to its own company. In this case, the store terminal 10 of the store can perform the same processing as in the above-described embodiment by referring to the voucher master 3041 and the balance management table 3042 stored in the head office device 20 of the company operating its own store.

[0229] (Modification Example 2) In the above-described embodiment, the form is such that the settlement server 30 performs the availability confirmation process performed prior to the charging of vouchers. However, it is not limited to this form, and it may be a form performed on the reception terminal 11 side.

[0230] In this case, the charge processing unit 112 of the reception terminal 11 searches for the voucher master data corresponding to the combination of the company code of its own company and the voucher ID of the vouchers to be charged from the voucher master 3041 of the settlement server 30. Then, the charge processing unit 112 may determine the availability based on the search result of the voucher master data or the setting value of the availability information included in the searched voucher master data.

[0231] Also, when the charge processing unit 112 of the reception terminal 11 determines that it is available, it may acquire the searched voucher master data from the settlement server 30 (voucher master 3041) and display the details screen.

[0232] (Modification Example 3) In the above-described embodiment, the form in which the store terminal 10 outputs a receipt using the printing unit 109 which is a printing device has been described. However, the output form of the receipt is not limited to this. For example, the charge processing unit 112 or the sales data processing unit 122 of the store terminal 10 may display and output the content to be printed on the receipt on the display unit 105. Also, for example, the charge processing unit 112 or the sales data processing unit 122 of the store terminal 10 may output it in the form of an electronic receipt.

[0233] In this case, for example, in an electronic receipt system in which the store terminal 10, a mobile terminal held by a customer (also referred to as a consumer), and an electronic receipt management server are connected through a network, the electronic receipt management server stores the information of the electronic receipt output from the store terminal 10 for each member ID. Also, the mobile terminal held by the consumer has an application for viewing the electronic receipt installed in advance. When the electronic receipt management server receives a request to view an electronic receipt specifying the member ID from the mobile terminal, it transmits the electronic receipt to the mobile terminal. When the mobile terminal receives the electronic receipt from the electronic receipt management server, it displays the electronic receipt. Thereby, the consumer can confirm the remaining balance of the vouchers charged by himself / herself and the breakdown of the transactions using the vouchers by looking at the electronic receipt displayed on the mobile terminal.

[0234] As described above, the embodiments of the present invention have been described. However, 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, replacements, combinations, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalent scope thereof.

[0235] Also, the program executed by each device of the above-described embodiment is provided by being pre-incorporated in a storage medium (ROM or storage unit) provided in the device, but is not limited thereto. For example, the program may be configured to be recorded and provided on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), etc. in an installable or executable file format. Furthermore, the storage medium is not limited to a medium independent of a computer or an embedded system, and also includes a storage medium that stores or temporarily stores a program transmitted via a LAN, the Internet, etc. after downloading.

[0236] Also, the program executed by each device of the above-described embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network, or may be configured to be provided or distributed via a network such as the Internet.

Explanation of Reference Numerals

[0237] 1 Settlement system 10 Store terminal 11 Reception terminal 12 Sales data processing device 20 Head office device 30 Settlement server 111 Member information acquisition unit 112 Charge processing unit 121 Member information acquisition unit 122 Sales data processing unit 211 Voucher setting processing unit 311 Voucher master management unit 312 Charge balance management unit

Prior art documents

Patent documents

[0238]

Patent Document 1

Claims

1. Receiving means for receiving input of usage conditions regarding the use of the vouchers for each type of voucher that can be used for payment for goods or exchange for goods; Generating means for generating master data associating the input usage conditions with the type of voucher; Registration means for registering the master data generated by the generating means in a storage unit that can be referenced by a store terminal of a store that sells the goods; An information processing apparatus comprising the above.

2. The receiving means displays, on a display unit, a screen on which the usage conditions can be input for a plurality of items related to the usage conditions; The generating means generates the master data based on the usage conditions input on the screen. The information processing apparatus according to Claim 1.

3. The usage conditions include an item that defines whether the vouchers can be used. The information processing apparatus according to Claim 1 or 2.

4. The usage conditions include an item that defines the consideration for using the vouchers. The information processing apparatus according to Claim 1 or 2.

5. The usage conditions include an item that designates the goods to be the subject of payment or exchange. The information processing apparatus according to Claim 1 or 2.

6. A program for causing a computer of an information processing apparatus to function as: Receiving means for receiving input of usage conditions regarding the use of the vouchers for each type of voucher that can be used for payment for goods or exchange for goods; Generating means for generating master data associating the input usage conditions with the type of voucher; Registration means for registering the master data generated by the generating means in a storage unit that can be referenced by a store terminal of a store that sells the goods.

7. The program according to Claim 6, further causing the computer to function as: Display control means for displaying, on a display unit, a screen on which the usage conditions can be input for a plurality of items related to the usage conditions; Generating means for generating the master data based on the usage conditions input on the screen.

8. The program according to Claim 6 or 7, wherein the usage conditions include an item that defines whether the vouchers can be used.

9. The program according to Claim 6 or 7, wherein the usage conditions include an item that defines the consideration for using the vouchers.

10. The program according to Claim 6 or 7, wherein the usage conditions include an item that designates the goods to be the subject of payment or exchange.

Images