Electronic receipt processing apparatus and information processing program

Abstract

To enable flexible modification of data which is to be displayed on an electronic receipt screen.SOLUTION: An electronic receipt processing apparatus includes first and second acquisition means and generation means. The first acquisition means acquires transaction data representing a content of a transaction. The second acquisition means acquires common data common to multiple transactions, from a transaction processing apparatus in association with the transaction data. The generation means generates, if the common data is acquired, electronic receipt data for displaying, on a display device, information on the transaction represented by the acquired transaction data on the basis of the acquired common data and the acquired transaction data, or generates, if the common data is not acquired, electronic receipt data on the basis of predetermined common data and the acquired transaction data.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE An embodiment of the present invention relates to an electronic receipt processing device. [Background technology]

[0002] Electronic receipt processing devices that display an electronic receipt screen showing the details of a transaction at a store on a display device are already in use. In this electronic receipt processing device, data that should be displayed on the electronic receipt screen in common for multiple transactions is stored in advance, and when changing the data stored in this electronic receipt processing device, a store manager or the like needs to access the electronic receipt processing device and update the data stored in the electronic receipt processing device. Due to these circumstances, it has been desirable to be able to flexibly change the data to be displayed on the electronic receipt screen. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2021-180043 A Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present invention is to provide an electronic receipt processing device and an information processing program that can flexibly change data to be displayed on an electronic receipt screen. [Means for solving the problem]

[0005] The electronic receipt processing device of the embodiment includes a first acquisition means, a second acquisition means, and a generation means. The first acquisition means acquires transaction data representing the contents of a transaction processed by the transaction processing device. The second acquisition means acquires common data common to a plurality of transactions from the transaction processing device in association with the transaction data. If the common data output from the transaction processing device is acquired by the second acquisition means, the generation means generates electronic receipt data for displaying information on the transaction represented by the transaction data acquired by the first acquisition means on a display device based on the common data acquired by the second acquisition means and the transaction data acquired by the first acquisition means, and if the common data output from the transaction processing device is not acquired by the second acquisition means, the generation means generates electronic receipt data for displaying information on the transaction represented by the transaction data acquired by the first acquisition means on a display device based on the predetermined common data and the transaction data acquired by the first acquisition means. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing a main circuit configuration of the electronic receipt processing device in FIG. 1. [Diagram 3] 3 is a diagram showing an example of the data structure of a data record included in the management table in FIG. 2; [Figure 4] A sequence diagram outlining the processing steps for one transaction in a transaction processing system. [Diagram 5] 10 is a flowchart showing the procedure of a receipt registration process. [Figure 6] FIG. 13 is a diagram illustrating an example of an electronic receipt screen. [Figure 7] FIG. 13 is a diagram illustrating an example of an electronic receipt screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, an example of an embodiment will be described with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system according to this embodiment. The transaction processing system shown in FIG. 1 is configured so that a store system 1, a transaction processing device 2, an electronic receipt processing device 3, and a user terminal 4 are capable of communicating with each other via a communication network 5.

[0008] The store system 1 is installed in a plurality of stores that trade products. The store system 1 is configured to be adapted to each store, taking into consideration the management policy of each store in which it is installed. 1, the store system 1 includes, for example, a plurality of store terminals 11, a plurality of input / output devices 12, a plurality of peripheral devices 13, and a connection device 14. The store terminals 11, the input / output devices 12, and the connection devices 14 are capable of communicating with each other via an in-store network 15. As the in-store network 15, for example, a LAN (local area network) is used.

[0009] Store terminal 11 is a user interface terminal for receiving operations from an operator. As hardware for store terminal 11, for example, a tablet computer is assumed to be used. Store terminal 11 is provided with an application program that realizes a user interface for communicating with or controlling transaction processing device 2, input / output device 12, and peripheral device 13 in response to operations by the operator. The operator of store terminal 11 is, for example, a store clerk. However, store terminal 11 may also be operated by a customer.

[0010] One or more peripheral devices 13 are appropriately connected to each of the input / output devices 12. The input / output devices 12 perform interface processing to enable the connected peripheral devices 13 to communicate via the communication network 5. As an example, the multiple input / output devices 12 are provided corresponding to each of a plurality of checkout lanes set at a checkout counter in a store. The input / output devices 12 are connected to the peripheral devices 13 used for transaction processing in the corresponding checkout lane.

[0011] The peripheral devices 13 are devices that perform various processes related to transaction processing. Various types of devices such as an automatic change machine, a drawer, a payment terminal, a printer, a scanner, or a display can be used as the peripheral devices 13. Most of the peripheral devices 13 are equipped in existing POS terminals or are various devices that are externally attached to existing POS terminals. The combination of peripheral devices 13 connected to each of the multiple input / output devices 12 does not need to be the same. The connection device 14 performs communication processing to enable each device included in the store system 1 to communicate via the communication network 5. As the connection device 14, a well-known device such as an Internet router can be used.

[0012] Transaction processing device 2 is an information processing device that performs information processing for processing a transaction while appropriately using peripheral device 13 in response to operation by an operator at store terminal 11. Transaction processing device 2 is provided with application programs for executing processes that have been executed in conventional POS terminals, such as product registration processing for registering products to be purchased, accounting processing for accounting for registered products, and other business processing. Transaction processing device 2 executes various processes related to a transaction in response to operation by an operator at store terminal 11. Transaction processing device 2 is realized, for example, as a cloud server. Transaction processing device 2 may be realized by distributed processing by multiple cloud servers. Alternatively, transaction processing device 2 may be realized as a web server, or as an in-store server or an in-company server.

[0013] The electronic receipt processing device 3 is an information processing device that performs information processing to enable a screen showing a receipt related to a transaction processed by the transaction processing device 2 (hereinafter referred to as an electronic receipt screen) to be confirmed on the user terminal 4. The electronic receipt processing device 3 is realized, for example, as a cloud server. The electronic receipt processing device 3 may also be realized by distributed processing using multiple cloud servers. Alternatively, the electronic receipt processing device 3 may be realized as a web server, or as an in-store server or corporate server.

[0014] The user terminal 4 is any information and communication terminal that can be used by a customer who has completed a transaction at a store where the store system 1 is installed. As the user terminal 4, various information and communication terminals such as a smartphone, a tablet terminal, or a computer terminal may be used. Typically, a smartphone on which an application program for using the electronic receipt service provided by the electronic receipt processing device 3 is installed is used as the user terminal 4. In other words, there are an infinite number of information and communication terminals that can be used as the user terminal 4, but FIG. 1 shows only one. The communication network 5 may be the Internet, a virtual private network (VPN), a LAN, a public communication network, a mobile communication network, or the like, either alone or in appropriate combination. As the communication network 5, a LAN and the Internet are used, for example.

[0015] FIG. 2 is a block diagram showing the main circuit configuration of the electronic receipt processing device 3. The electronic receipt processing device 3 includes a processor 31, a main memory unit 32, an auxiliary memory unit 33, a communication unit 34, and a transmission path 35. The processor 31, the main memory unit 32, the auxiliary memory unit 33, and the communication unit 34 are capable of communicating with each other via the transmission path 35.

[0016] The processor 31, the main memory unit 32, and the auxiliary memory unit 33 are connected via a transmission line 35 to form a computer that performs information processing to realize the various functions of the electronic receipt processing device 3. The processor 31 corresponds to the central part of the computer. The processor 31 executes information processing to realize various functions of the electronic receipt processing device 3 in accordance with an operating system and information processing programs such as application programs.

[0017] The main memory unit 32 corresponds to the main memory portion of the computer. The main memory unit 32 includes a read-only memory area and a rewritable memory area. The main memory unit 32 stores part of the information processing program in the read-only memory area. The main memory unit 32 may also store data required for the processor 31 to execute processes for controlling each part in the read-only memory area or the rewritable memory area. The main memory unit 32 uses the rewritable memory area as a work area for the processor 31.

[0018] The auxiliary storage unit 33 corresponds to the auxiliary storage portion of the computer. The auxiliary storage unit 33 may be, for example, an EEPROM (electric erasable programmable read-only memory), a HDD (hard disk drive), an SSD (solid state drive), or any other known storage device. The auxiliary storage unit 33 stores data used by the processor 31 in performing various processes and data generated by the processes in the processor 31. The auxiliary storage unit 33 may also store the information processing program. In this embodiment, the auxiliary storage unit 33 stores an electronic receipt program PRA, which is one of the information processing programs. The electronic receipt program PRA is an application program that describes the information processing procedure for providing an electronic receipt service, as described later. A part of the storage area of ​​the auxiliary storage unit 33 is used as an area for storing the image data group DAA, the management table TAA, and the electronic receipt data group DAB.

[0019] The image data group DAA may include a plurality of image data to be commonly included in a plurality of electronic receipt screens. The image data, as an example, represents a logo (also called a store logo) according to a store brand. In this case, the image data can be commonly used for a plurality of transactions performed in a plurality of stores operated by one company under the same store brand. The image data, as an example, represents an image including store-specific information such as a branch name, location, or telephone number in addition to a logo according to the store brand. In this case, the image data can be commonly used for a plurality of transactions performed in one store. The image data, as an example, represents an image including store-specific information such as a register number assigned to the store terminal 11 in addition to a logo according to the store brand. In this case, the image data can be commonly used for a plurality of transactions performed using one store terminal 11. Thus, these image data are an example of common data. The auxiliary memory unit 33 is an example of a storage means.

[0020] The image data included in the image data group DAA is associated with a store terminal 11, a store, or a company. That is, the image data associated with a store terminal 11 represents an image commonly displayed on an electronic receipt screen for each of a plurality of transactions processed using the associated store terminal 11. The image data associated with a store represents an image commonly displayed on an electronic receipt screen for each of a plurality of transactions processed using each of a plurality of store terminals 11 belonging to the store system 1 installed in the associated store. The image data associated with a company represents an image commonly displayed on an electronic receipt screen for each of a plurality of transactions processed using each of a plurality of store terminals 11 belonging to the store system 1 installed in a plurality of stores operated by the associated company. That is, in either case, the image data is associated with the store terminal 11.

[0021] The management table TAA is a data table for managing the associations related to each of the image data included in the image data group DAA. FIG. 3 shows an example of the data structure of a data record REA contained in the management table TAA.

[0022] The management table TAA is a collection of data records REA corresponding to each of the image data included in the image data group DAA. The data record REA includes fields FEA, FEB, FEC, and FED. In the field FEA, an image data code is set as an identifier of the corresponding image data. For example, a file path for identifying the corresponding image data in the auxiliary storage unit 33 can be used as the image data code. In the field FEB, a terminal code is set as an identifier of the store terminal 11 with which the corresponding image data is associated. If the corresponding image data is not associated with the store terminal 11, the field FEB is set to blank or a predetermined invalid code is set to indicate that there is no association. In the field FEC, a store code is set as an identifier of the store with which the corresponding image data is associated. If the corresponding image data is not associated with a store, the field FEC is set to blank or an invalid code is set. In the field FED, a company code is set as an identifier of the company with which the corresponding image data is associated. If the corresponding image data is not associated with a company, the field FED is set to blank or an invalid code is set.

[0023] The electronic receipt data group DAB may include a plurality of data for displaying an electronic receipt screen on the user terminal 4 (hereinafter, referred to as electronic receipt data). The communication unit 34 executes communication processing for performing data communication via the communication network 5. As the communication unit 34, for example, an existing communication device for Internet communication can be used. The transmission path 35 includes an address bus, a data bus, and control signal lines, and transmits data and control signals between the connected components.

[0024] Now, for example, a general-purpose server device can be used as the hardware of the electronic receipt processing device 3. The electronic receipt processing device 3 is generally transferred in a state in which the electronic receipt program PRA is stored in the auxiliary storage unit 33. However, the electronic receipt program PRA may be transferred separately from the hardware in a state in which the electronic receipt program PRA is not stored in the auxiliary storage unit 33, or in a state in which a different version of the same type of application program is stored in the auxiliary storage unit 33. The electronic receipt processing device 3 may be configured by writing the electronic receipt program PRA to the auxiliary storage unit 33 in response to an operation by an arbitrary worker. The electronic receipt program PRA may be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network.

[0025] Next, the operation of the transaction processing system configured as above will be described, focusing on the operation of the electronic receipt processing device 3. Note that the contents of the processing described below are merely examples, and it is possible to change the order of some of the processing, omit some of the processing, or add other processing as appropriate. Also, for the specific processing described below, other processing that achieves similar results may be applied.

[0026] FIG. 4 is a sequence diagram showing an outline of the processing procedure in the transaction processing system for one transaction. A customer picks up a product to be purchased from among products displayed in a store, and then brings the product to the checkout lane of the store. The store clerk in charge of the checkout lane performs a predetermined registration operation on the store terminal 11 to register the product brought by the customer as a transaction product. The registration operation is, for example, an operation in which the store clerk uses a scanner or the like connected to the store terminal 11 as a peripheral device 13 to have the store terminal 11 read the barcode attached to the product. Alternatively, the registration operation is, for example, an operation in which the store clerk selects and inputs a product to be registered from a selection of products displayed on the screen of the store terminal 11. The registration operation may be performed by the customer. Furthermore, after completing the registration of the transaction product on the store terminal 11, the store clerk performs a predetermined operation to calculate the price of the transaction product and settle the price by an arbitrary payment method. Hereinafter, when the store clerk simply refers to the "store terminal 11," it refers to the store terminal 11 used for the above operation among the multiple store terminals 11.

[0027] At this time, store terminal 11 executes user interface processing as ACT11 to accept operations by a store clerk. Furthermore, transaction processing device 2 executes product registration processing and accounting processing as ACT21 in cooperation with the user interface processing in store terminal 11 as described above. That is, transaction processing device 2 generates a list of transaction products, for example, from product codes represented by barcodes read by store terminal 11 through the above registration operation or a list of product codes of selected products. Then, transaction processing device 2 acquires product information associated with the product codes of the transaction products, and calculates the payment amount for all transaction products, taking into consideration the unit price and discount information included in the product information. Furthermore, transaction processing device 2 settles the calculated payment amount by applying an applicable payment method among various payment methods such as cash payment, credit payment, prepaid payment, code payment, or point payment. Note that the various processes in store terminal 11 and transaction processing device 2 at this time can be directly applied to processes already known as processes for implementing a so-called tablet POS, which performs transaction processing using a tablet terminal as a user interface terminal, for example.

[0028] When a customer wishes to use the electronic receipt service for a transaction, the customer presents a user code for identifying a user of the electronic receipt service (hereinafter referred to as a receipt member code) or a user code for another service to which the receipt member code is linked. That is, the customer presents the user terminal 4, for example, displaying a screen including a barcode representing the receipt member code, to the store clerk. Alternatively, the customer presents the store clerk a point card on which a point member code to which the receipt member code is linked is recorded. In response to this, the store clerk causes the transaction processing device 2 to obtain the receipt member code or the user code for the other service via the store terminal 11, for example, by reading a barcode or a card. If the transaction processing device 2 does not obtain the receipt member code or the user code for the other service, the transaction processing device 2 causes a receipt printer, which is one of the peripheral devices 13, to print a paper receipt, but this case is not shown in FIG. 4. The paper receipt is a receipt image printed on receipt paper that shows the contents of the transaction, such as a list of transaction items, and the transaction result in text. Paper receipts often also have images such as store logos printed on them.

[0029] If the transaction processing device 2 has acquired a receipt member code during the product registration process, or if it has acquired a user code for another service linked to the receipt member code, it requests receipt registration from the electronic receipt processing device 3 in ACT22. When making this request, the transaction processing device 2 notifies the electronic receipt processing device 3 of the terminal code of the store terminal 11, the store code of the store in which the store system 1 to which the store terminal 11 belongs is located, and the company code of the company that operates the store. When making this request, the transaction processing device 2 also notifies the electronic receipt processing device 3 of the user code for the electronic receipt service acquired above, or the user code for the electronic receipt service linked to the acquired user code.

[0030] The transaction processing device 2 sends receipt text data to the electronic receipt processing device 3 as ACT23. Receipt text data is data that represents characters that are included on a paper receipt to indicate the transaction details and transaction results. In other words, receipt text data is an example of transaction data. The receipt text data does not need to completely represent all of the characters that appear on a paper receipt; some characters may not be represented, and characters that do not appear on a paper receipt may be added. This receipt text data may also include a terminal code, store code, company code, and user code. Of the terminal code, store code, company code, and user code, the codes included in the receipt text data may not be subject to notification in ACT22.

[0031] Transaction processing device 2 transmits image data as ACT24 to electronic receipt processing device 3. Image data is data representing an image to be printed on a paper receipt. The image data transmitted by transaction processing device 2 may be, for example, the same data as that included in image data group DAA. Alternatively, the image data transmitted by transaction processing device 2 may be data including, for example, an advertisement.

[0032] Transaction processing device 2 may also pass ACT24. For example, if a setting is made for each store terminal 11, each store, or each company so that image data is not sent, transaction processing device 2 passes ACT24 and does not send image data. In other words, transaction processing device 2 passes ACT24 for a transaction using, as a user interface terminal, store terminal 11 used in a store belonging to a company that is set so that image data is not sent.

[0033] Alternatively, transaction processing device 2 may pass ACT24 and not transmit image data if the setting for transmitting image data is not made for each store terminal 11, store, or company, for example. In other words, transaction processing device 2 passes ACT24 for transactions using, as a user interface terminal, store terminal 11 used in a store belonging to a company that is not set to transmit image data.

[0034] Although not shown in FIG. 4, the transaction processing device 2 notifies the electronic receipt processing device 3 of a terminal code if image data is sent according to the settings for each store terminal 11, a store code if image data is sent according to the settings for each store, or a company code if image data is sent according to the settings for each company, together with the image data. After completing ACT24, or if transaction processing device 2 completes ACT23 and passes ACT24, it proceeds to ACT25 and notifies electronic receipt processing device 3 of the completion of transfer.

[0035] During the period when the electronic receipt service is to be provided, the processor 31 in the electronic receipt processing device 3 executes information processing based on the electronic receipt program PRA. When the receipt registration request is received by the communication unit 34, the processor 31 starts the receipt registration process during this information processing.

[0036] FIG. 5 is a flowchart showing the procedure of the receipt registration process. As ACT301, processor 31 acquires receipt text data transmitted from transaction processing device 2 as described above. That is, for example, when receipt text data transmitted from transaction processing device 2 as described above is received by communication unit 34, processor 31 stores this receipt text data in auxiliary storage unit 33. In this way, processor 31 executes information processing based on electronic receipt program PRA, and the computer with processor 31 as its central part functions as a first acquisition means.

[0037] In ACT 302, processor 31 checks whether image data has been transmitted from transaction processing device 2. If image data has been transmitted from transaction processing device 2 and received by communication unit 34 as described above, then processor 31 determines that the result is YES and proceeds to ACT 303. Processor 31 acquires image data as ACT303. That is, processor 31 adds, for example, image data transmitted from transaction processing device 2 and received by communication unit 34 as described above to image data group DAA. Thus, processor 31 executes information processing based on electronic receipt program PRA, and the computer with processor 31 as the central part functions as second acquisition means and storage control means.

[0038] Processor 31 updates management table TAA in ACT304. That is, processor 31 adds data record REA corresponding to the image data added to image data group DAA in ACT303 to management table TAA. Processor 31 sets the file path of the image data added to image data group DAA in ACT303 in field FEA of the data record REA to be added. If processor 31 is notified of a terminal code from transaction processing device 2, processor 31 sets the terminal code in field FEB of the data record REA to be added, and sets fields FEC and FED to blank or invalid codes. If processor 31 is notified of a store code from transaction processing device 2, processor 31 sets the store code in field FEC of the data record REA to be added, and sets fields FEB and FED to blank or invalid codes. If processor 31 is notified of a company code from transaction processing device 2, processor 31 sets the company code in field FED of the data record REA to be added, and sets fields FEB and FEC to blank or invalid codes.

[0039] If processor 31 judges YES in ACT302, it may confirm whether the image data sent from transaction processing device 2 is different from the image data to be replaced, for example by comparing the hash values ​​of both image data, and if it confirms that they are different, it may execute ACT304 and ACT305.

[0040] In ACT305, the processor 31 generates electronic receipt data for displaying an electronic receipt screen on the user terminal 4 based on the receipt text data stored in ACT301 and the image data added to the image data group DAA in ACT303.

[0041] FIG. 6 is a diagram illustrating an example of an electronic receipt screen. In the electronic receipt screen shown in FIG. 6, area ARA is based on image data, and area ARB is based on receipt text data.

[0042] If transaction processing device 2 passes ACT24, processor 31 determines NO in ACT302 in response to receiving a notification of transfer completion from communication unit 34 without receiving image data, and proceeds to ACT306. In ACT306, the processor 31 checks whether there is image data associated with the store terminal 11. For example, the processor 31 searches the management table TAA for a data record REA in which the terminal code notified or included in the receipt text data is set in the field FEB. If the processor 31 finds the corresponding data record REA, for example, it determines that there is image data associated with the store terminal 11 and judges the result as YES, and proceeds to ACT307.

[0043] In ACT307, the processor 31 generates electronic receipt data for displaying an electronic receipt screen on the user terminal 4 based on the receipt text data stored in ACT301 and the image data included in the image data group DAA. That is, the processor 31 selects, for example, image data identified by the image data code set in the field FEA of the data record REA found in ACT306 from the image data group DAA. The processor 31 then generates electronic receipt data based on, for example, the image data and the receipt text data stored in ACT301.

[0044] For example, if the processor 31 is notified or is unable to find a data record REA in which the terminal code contained in the receipt text data is set in the field FEB, the processor 31 determines NO in ACT306 and proceeds to ACT308. In ACT308, the processor 31 checks whether there is image data associated with the store in which the store system 1 to which the store terminal 11 belongs is installed. For example, the processor 31 searches the management table TAA for a data record REA in which the store code notified or included in the receipt text data is set in the field FEC. If the processor 31 finds the corresponding data record REA, for example, the processor 31 determines that there is image data associated with the corresponding store and judges YES, and proceeds to ACT309.

[0045] In ACT309, the processor 31 generates electronic receipt data for an electronic receipt screen based on the receipt text data stored in ACT301 and the image data included in the image data group DAA. That is, the processor 31 selects, for example, image data identified by the image data code set in the field FEA of the data record REA found in ACT308 from the image data group DAA. The processor 31 then generates electronic receipt data based on, for example, the image data and the receipt text data stored in ACT301.

[0046] For example, if the processor 31 is notified or is unable to find a data record REA in which the store code included in the receipt text data is set in the field FEC, the processor 31 determines NO in ACT308 and proceeds to ACT310. In ACT310, the processor 31 checks whether there is image data associated with the company that operates the store in which the store system 1 to which the store terminal 11 belongs is installed. For example, the processor 31 searches the management table TAA for a data record REA in which the company code notified or included in the receipt text data is set in the field FED. If the processor 31 finds the corresponding data record REA, for example, it determines that there is image data associated with the company and judges YES, and proceeds to ACT311.

[0047] In ACT311, the processor 31 generates electronic receipt data for an electronic receipt screen based on the receipt text data stored in ACT301 and the image data included in the image data group DAA. That is, the processor 31 selects, for example, image data identified by the image data code set in the field FEA of the data record REA found in ACT310 from the image data group DAA. The processor 31 then generates electronic receipt data based on the image data and the receipt text data stored in ACT301.

[0048] As described above, when the processor 31 is able to acquire image data as common data in ACT 303, it generates electronic receipt data in ACT 305 based on the image data and the receipt text data acquired in ACT 301. When the processor 31 is unable to acquire image data as common data, it generates electronic receipt data in ACT 307, ACT 309, or ACT 311 based on the image data pre-stored in the auxiliary storage unit 33 and the receipt text data acquired in ACT 301. In this way, the processor 31 executes information processing based on the electronic receipt program PRA, and the computer with the processor 31 as its central part functions as a generating means.

[0049] For example, if the processor 31 is notified or is unable to find a data record REA in which the company code contained in the receipt text data is set in the field FED, the processor 31 determines NO in ACT310 and proceeds to ACT312. In ACT312, the processor 31 generates electronic receipt data for displaying an electronic receipt screen based on the receipt text data stored in ACT301 on the user terminal 4. That is, at this time, the processor 31 generates electronic receipt data for displaying, for example, an electronic receipt screen not including the area ARA in FIG.

[0050] When the processor 31 has finished generating the electronic receipt data in any of ACT305, ACT307, ACT309, ACT311, and ACT312, it proceeds to ACT313 in any case. The processor 31 stores the generated electronic receipt data in ACT 313. That is, the processor 31 adds the electronic receipt data generated in, for example, any of ACT 305, ACT 307, ACT 309, ACT 311, and ACT 312 to the electronic receipt data group DAB. The processor 31 then ends the receipt registration process. When processor 31 has completed the receipt registration process in this manner, it notifies transaction processing device 2 of the completion of registration of the electronic receipt (ACT 321 in FIG. 4).

[0051] Now, the customer of the above transaction can access the electronic receipt processing device 3 at any time thereafter using any user terminal 4 and instruct to display a receipt screen for the above transaction. That is, the customer instructs to display a receipt screen for the above transaction on the user terminal 4, for example, by operating a user interface screen based on an application program for using an electronic receipt service. In response to this instruction, the user terminal 4 requests the electronic receipt processing device 3 to display a receipt (ACT41). In response to this request, the processor 31 in the electronic receipt processing device 3 transmits the corresponding electronic receipt data to the user terminal 4 that made the request (ACT331). Then, when the user terminal 4 receives the electronic receipt data, it displays a receipt screen based on the electronic receipt data on a display device provided in the user terminal 4 or connected to the user terminal 4 (ACT42). The processing performed by the electronic receipt processing device 3 and the user terminal 4 in relation to the display of the receipt screen may be similar to the processing performed in existing electronic receipt services, and therefore a detailed description thereof will be omitted.

[0052] As described above, when image data is not sent from the transaction processing device 2 at the time of registering a receipt, the electronic receipt processing device 3 uses the image data included in the image data group DAA to generate electronic receipt data. Also, when image data is sent from the transaction processing device 2 at the time of registering a receipt, the electronic receipt processing device 3 uses this image data to generate electronic receipt data. Thus, by not sending image data from the transaction processing device 2, image data previously determined by the electronic receipt processing device 3 can be used to generate electronic receipt data. Also, by sending image data from the transaction processing device 2, the sent image data can be used to generate electronic receipt data. Thus, data to be displayed on the electronic receipt screen can be flexibly changed. Also, as long as image data included in the image data group DAA is used, there is no need to exchange image data between the transaction processing device 2 and the electronic receipt processing device 3, so the amount of data communication between them can be reduced. Also, if image data is sent from the transaction processing device 2, it is possible to include an image on the receipt screen without having to include the image data in the image data group DAA in advance. It is also possible to determine the image to be included on the receipt screen for each transaction by transmitting image data from transaction processing device 2.

[0053] Furthermore, if image data is sent from the transaction processing device 2 when registering a receipt, the electronic receipt processing device 3 adds this image data to the image data group DAA, and uses it to generate electronic receipt data if no image data is sent later. Therefore, even if the work of including image data in the image data group DAA in advance is not performed, image data representing an image to be included on the receipt screen can be added to the image data group DAA by sending the image data only once from the transaction processing device 2. This also makes it easy to frequently change the image to be included on the receipt screen depending on the circumstances of the store. This means that, for example, if the store logo is changed to comply with legal changes or to refresh the company's image, the new store logo can be easily displayed on the electronic receipt screen based on the image data included in the image data group DAA.

[0054] This embodiment can be modified in various ways as follows. When registering a receipt, if image data is sent from the transaction processing device 2, the image data may be excluded from being included in the image data group DAA. This allows the electronic receipt data to be generated normally using image data included in the image data group DAA, but also allows the store to generate electronic receipt data using image data temporarily sent from the transaction processing device 2 depending on circumstances.

[0055] The common data may be any data that represents information that is common to multiple receipt screens regardless of the content of the transaction, and may be data other than image data, such as text data representing store information. FIG. 7 is a diagram illustrating an example of an electronic receipt screen. The electronic receipt screen shown in Fig. 7 has areas ARE and ARH based on receipt text data. The information displayed in these areas ARE and ARH is the same as that displayed in area ARB in Fig. 6, but in the example of Fig. 7, it is divided into two areas ARE and ARH, separated by another area. The area ARA represents an image based on image data as common data, and the image represents a store logo. The common data is typically associated with a company. Area ARC represents information based on text data as common data, and the information represents, by character strings, the store name, address, and telephone number of the store where the transaction was performed. The common data is typically associated with the store. Area ARD represents information based on text data as common data, and the information represents a text message for promoting a business policy of a company. The common data is typically associated with a company. The area ARF represents information based on text data as common data, and represents a text message of caution regarding the checkout lane used in the transaction. The common data is typically associated with the store terminal 11. Area ARG represents information based on image data as common data, and represents an advertisement image. The common data is typically associated with a company or a store.

[0056] If it is necessary to transmit image data, the transaction processing device 2 may transmit transfer data that combines the receipt text data and image data into one unit in ACT 23. In this case, the electronic receipt processing device 3 is configured to be able to determine the presence or absence of image data from the transfer data itself, or the electronic receipt processing device 3 is configured to be able to make the determination in ACT 302 in FIG. 5 by notifying the presence or absence of image data in the transfer completion notification, etc.

[0057] Each function realized by the processor 31 through information processing can be realized in part or in whole by hardware that executes information processing not based on a program, such as a logic circuit, etc. Also, each of the above functions can be realized by combining the above hardware, such as the logic circuit, with software control.

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

[0059] 1...store system, 2...transaction processing device, 3...electronic receipt processing device, 4...user terminal, 5...communication network, 11...store terminal, 12...input / output device, 13...peripheral device, 14...connection device, 15...in-store network, 31...processor, 32...main memory unit, 33...auxiliary memory unit, 34...communication unit, 35...transmission path.

Claims

1. a first acquiring means for acquiring transaction data representing the content of a transaction processed by the transaction processing device; a second acquiring means for acquiring common data related to a plurality of transactions from the transaction processing device in association with the transaction data; a generating means for generating electronic receipt data for displaying information on a transaction represented by the transaction data acquired by the first acquisition means on a display device based on the common data acquired by the second acquisition means and the transaction data acquired by the first acquisition means, if the common data output from the transaction processing device is acquired by the second acquisition means, and for generating electronic receipt data for displaying information on a transaction represented by the transaction data acquired by the first acquisition means on a display device based on predetermined common data and the transaction data acquired by the first acquisition means, if the common data output from the transaction processing device is not acquired by the second acquisition means; An electronic receipt processing device comprising:

2. A storage unit for storing the common data is further provided. the generating means generates electronic receipt data based on the common data stored in the storage means and the transaction data acquired by the first acquiring means, if the common data output from the transaction processing device in association with the transaction data acquired by the first acquiring means is not acquired by the second acquiring means; The electronic receipt processing device according to claim 1 .

3. the storage means stores a plurality of common data in association with a user interface terminal used when the transaction processing device processes a transaction; if common data output from the transaction processing device in association with the transaction data acquired by the first acquisition means is not acquired by the second acquisition means, the generation means generates electronic receipt data based on the common data stored in the storage means in association with a user interface terminal used when the transaction processing device processes the transaction represented by the transaction data acquired by the first acquisition means and on the transaction data acquired by the first acquisition means; The electronic receipt processing device according to claim 2 .

4. a storage control means for storing the common data acquired by the second acquisition means in the storage means in association with a user interface terminal used when the transaction processing device processes a transaction represented by transaction data to which the common data is attached; The electronic receipt processing device of claim 2 further comprising:

5. The transaction data is text data, and the common data is image data. The electronic receipt processing device according to claim 1 .

6. Computer, a first acquiring means for acquiring transaction data representing the content of a transaction processed by the transaction processing device; a second acquiring means for acquiring common data related to a plurality of transactions from the transaction processing device in association with the transaction data; a generating means for generating electronic receipt data for displaying information on a transaction represented by the transaction data acquired by the first acquisition means on a display device based on the common data acquired by the second acquisition means and the transaction data acquired by the first acquisition means, if the common data output from the transaction processing device is acquired by the second acquisition means, and for generating electronic receipt data for displaying information on a transaction represented by the transaction data acquired by the first acquisition means on a display device based on predetermined common data and the transaction data acquired by the first acquisition means, if the common data output from the transaction processing device is not acquired by the second acquisition means; An information processing program that enables the system to function as such.

Images