JP2022024105A - Receipt data management device, program thereof, and receipt data management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a receipt data management device, a method for managing the same, and a program for providing a customer with purchase information of a commodity to be subjected to tax deduction based on receipt data.

SOLUTION: An electronic receipt system includes: an electronic receipt management server connected to a communication network; a plurality of POS systems and a plurality of base stations; and a plurality of information terminals capable of wirelessly communicating with the base stations. An electronic receipt management server 10 has a CPU 11 that detects sales data of a commodity to be subjected to tax deduction from receipt data including sales data of a commodity purchased by a customer, stores the sales data of the commodity to be subjected to tax deduction in an auxiliary storage device 14 in association with customer identification information associated with the receipt data including sales data, and in response to a request for browsing including the customer identification information, executes output processing of a total amount of commodities to be subjected to tax deduction bought and sold within a prescribed period to an apparatus of a browsing request source based on sales data of a commodity to be subjected to tax deduction stored in association with the customer identification information.

SELECTED DRAWING: Figure 3

COPYRIGHT: (C)2022,JPO&INPIT

Description

An embodiment of the present invention relates to a program for making a receipt data management device and a computer function as the receipt data management device, and a receipt data management method.

In Japan, it has been decided to introduce a self-medication tax system from FY2017 in order to promote self-medication (self-medication). The self-medication tax system is the total amount of money (including consumption tax) purchased by one household per year for so-called switch OTC (Over The Counter) drugs (hereinafter referred to simply as OTC drugs) that have been diverted from medical use. It is a tax system that deducts from total income when the prescribed lower limit is exceeded. In order to comply with such a tax system, taxpayers need to manage receipts issued by pharmacies and the like when they purchase OTC drugs.

An electronic receipt system is effective for managing receipts. The electronic receipt system stores receipt data including sales data of products purchased by customers in a server for a certain period of time. Then, within that period, the server distributes the receipt data to the information terminal used by the customer via the Internet or the like in response to the request from the customer. By using such an electronic receipt system, the customer does not need to manage the receipt of the paper medium issued by the pharmacy or the like.

However, the current electronic receipt system does not support the self-medication tax system. In order to build an electronic receipt system that supports the self-medication tax system, it will be possible to provide taxpayer customers with purchase information for tax-deductible products based on the receipt data managed by the receipt data management device. Is desirable.

Japanese Unexamined Patent Publication No. 2014-229072

An object to be solved by the embodiment of the present invention is to provide a receipt data management device and a management method capable of providing a customer with purchase information of a product subject to tax deduction based on the receipt data.

In one embodiment, the receipt data management device includes a detection means, a storage means, a first aggregation means, a second aggregation means, an information output means, and a sales data output means. The detection means detects the sales data of the product subject to tax deduction from the receipt data including the sales data of the product purchased by the customer. The storage means stores the sales data of the product subject to the tax deduction detected by the detection means in association with the customer identification information associated with the receipt data including the sales data. The first aggregation means aggregates the sales data of products on a monthly basis. The second aggregation means aggregates the sales data of the products subject to the tax deduction every year. The information output means responds to a browsing request including the customer identification information, and based on the sales data aggregated by the first aggregation means, the total amount of the tax-deductible products bought and sold in a month. The image data including the image for instructing to display the sales data of the product subject to the tax deduction and the image data including the image data are output to the device of the viewing request source. When the sales data output means receives an instruction to display the sales data of the product subject to the tax deduction from the device of the viewing request source, the tax is based on the sales data aggregated by the second aggregation means. The total annual amount of the deductible products is output to the device from which the viewing request is made.

Further, in one embodiment, in the receipt data management method, the server executes the following processing. That is, the server detects the sales data of the product subject to tax deduction from the receipt data including the sales data of the product purchased by the customer, and the detected sales data of the product subject to tax deduction is the sales data. Is stored in the storage unit in association with the customer identification information associated with the receipt data including. In addition, the server aggregates the sales data of the products on a monthly basis, and further aggregates the sales data of the products subject to the tax deduction on a yearly basis. Then, in response to the browsing request including the customer identification information, the server is subject to the total amount of goods bought and sold in the month and the tax deduction based on the sales data aggregated for each month. The image data including the image for instructing to display the sales data of the product and the image data including the image data are output to the device of the viewing request source. Further, when the server receives an instruction to display the sales data of the product subject to the tax deduction from the device of the viewing request source, the server is subject to the tax deduction based on the sales data aggregated for each year. The total annual amount of the product is output to the device of the viewing request source.

Schematic block diagram of the electronic receipt system. Schematic diagram showing the structure of receipt data. A block diagram showing a circuit configuration of a main part of an electronic receipt management server. Schematic diagram showing the main data files stored in the auxiliary storage device of the electronic receipt management server. The schematic diagram which shows the structure of the data stored in a member setting file. The schematic diagram which shows the structure of the data stored in a store information file. Schematic diagram showing the structure of the data stored in the monthly summary file. The schematic diagram which shows the structure of the data stored in the OTC drug summary file. The flow chart which shows the information processing procedure which the CPU of an electronic receipt management server executes at the time of receiving a receipt data. The flow chart which shows concretely the processing procedure of the processing step "analysis" of FIG. The flow chart which shows a part of the information processing procedure which the CPU of the electronic receipt management server executes when the monthly aggregation request command is received. The flow chart which shows a part of the information processing procedure which the CPU of the electronic receipt management server executes when the monthly aggregation request command is received. The flow chart which shows a part of the information processing procedure which the CPU of the electronic receipt management server executes when the monthly aggregation request command is received. The schematic diagram which shows one display example of the home screen displayed on the display device of an information terminal. The schematic diagram which shows one display example of the receipt list screen displayed on the display device of an information terminal. The schematic diagram which shows one display example of the monthly total screen displayed on the display device of an information terminal. The schematic diagram which shows one display example of the OTC drug list screen displayed on the display device of an information terminal. The schematic diagram which shows one display example of the electronic receipt screen displayed on the display device of an information terminal.

Hereinafter, embodiments of a receipt data management device and a management method capable of providing customers with purchase information of products subject to tax deduction based on the receipt data will be described with reference to the drawings. In the embodiment described below, the electronic receipt management server 10 of the electronic receipt system 100 shown in FIG. 1 is made to function as an electronic receipt management device.

As shown in FIG. 1, the electronic receipt system 100 includes an electronic receipt management server 10, a plurality of POS (Point Of Sales) systems 20, a communication network 30 such as the Internet, and a plurality of communication networks 30 connected to the communication network 30. A plurality of information terminals 50 capable of wireless communication between the base station 40 and the base station 40 are included. The electronic receipt management server 10 is built in the electronic receipt management center that controls the electronic receipt service. The POS system 20 is constructed in each store that is a member of the electronic receipt service. The information terminal 50 is used by a consumer who has registered as a member in order to receive an electronic receipt service.

The POS system 20 includes a plurality of POS terminals 21 and a store server 22, and these are connected by a communication line 23 such as a LAN (Local Area Network). The POS terminal 21 functions as a settlement terminal for commercial transactions. The store server 22 manages sales, inventory, etc. of the entire store based on the data of commercial transactions settled by each POS terminal 21.

The POS terminal 21 generates receipt data including sales data of products purchased by a customer who is a settler. Further, the POS terminal 21 accepts the input of the member ID issued to the customer who has registered as a member in order to receive the electronic receipt service.

When the POS system 20 receives the input of the member ID in the POS terminal 21, the POS system 20 creates the receipt data 24 (see FIG. 2) by converting the receipt of the commercial transaction in which the customer identified by the member ID as the settler into text. Then, the POS system 20 outputs the receipt data 24 together with the member ID to the electronic receipt management server 10 via the communication network 30. The receipt may be converted into text by the POS terminal 21 or the store server 22. When the POS terminal 21 converts the receipt into text, the receipt data 24 may be directly output from the POS terminal 21 to the electronic receipt management server 10 via the communication network 30, or may be output via the store server 22. May be good. When the store server 22 converts the receipt into text, the receipt data 24 is output from the store server 22 to the electronic receipt management server 10 via the communication network 30. Since the technique of converting the receipt into text and generating the receipt data 24 is a well-known technique, detailed description thereof will be omitted here.

FIG. 2 is a schematic diagram showing the structure of the receipt data 24 output from the POS system 20 to the electronic receipt management server 10. The receipt data 24 includes a member ID, a store code, a transaction date and time, a transaction number, product sales data, and payment data. The product sales data includes the product code, classification code, product name, unit price, points, price, and the like. The payment data includes the payment amount, payment type, payment information, and the like.

Incidentally, the store code is a unique code set for each store to identify each store. The transaction date and time is, for example, the date and time when the commercial transaction is started or settled on the POS terminal 21.

The product sales data classification code is a unique code set for each product classification in order to identify the product classification (food, daily necessities, medical products, clothing, etc.) based on the attributes of each product. In this embodiment, in order to classify OTC drugs and other drugs with respect to medical products, a sub-classification code for OTC drugs and a sub-classification code for other drugs are set as subordinate codes of the drug classification codes. There is. The product sales data of OTC medical products includes a drug classification code and a sub-classification code of OTC drugs. Similarly, the product sales data of drugs other than OTC drugs include a drug classification code and a sub-classification code of other drugs.

The price is an amount calculated by multiplying the unit price by the points, and if the unit price is a price including consumption tax, it is a tax-included price, and if it is a price excluding consumption tax, it is a tax-excluded price. The payment type of the payment data is information that specifies the payment type (cash, credit card, points, cash voucher, etc.) for the payment amount.

The explanation is returned to FIG.
The information terminal 50 includes at least a display device, an input device, and a wireless communication device. Further, the information terminal 50 implements a Web browser. Then, the consumer who receives the electronic receipt service installs the electronic receipt viewing program, which is a dedicated application program, on the information terminal 50. By installing this electronic receipt viewing program on the information terminal 50, it is possible to register as a member and view receipt images. By registering as a member, the member ID is set in the management area of the electronic receipt viewing program formed in the memory of the information terminal 50. As the information terminal 50 of this type, electronic devices such as smartphones, mobile phones, tablet terminals, and notebook computers are used.

The electronic receipt management server 10 stores the receipt data 24 output from the POS system 20 of each store for a certain period of time. Then, the electronic receipt management server 10 responds to the browsing request from the information terminal 50 and transmits the image data created based on the receipt data 24 to the information terminal 50 of the browsing request source.

FIG. 3 is a block diagram showing a main circuit configuration of the electronic receipt management server 10. The electronic receipt management server 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM 13, an auxiliary storage device 14, a clock unit 15, a communication unit 16, and the like. The CPU 11 and the ROM 12, the RAM 13, the auxiliary storage device 14, the clock unit 15, and the communication unit 16 are connected by a system transmission line 17 such as an address bus and a data bus.

The electronic receipt management server 10 constitutes a computer by a CPU 11, a ROM 12, a RAM 13, an auxiliary storage device 14, and a system transmission line 17 connecting them.
The CPU 11 corresponds to the central part of the computer. The CPU 11 controls each part in order to realize various functions as the electronic receipt management server 10 according to the operating system and the application program.

The ROM 12 corresponds to the main storage portion of the computer. The ROM 12 stores the above-mentioned operating system and application program. The ROM 12 may store data necessary for the CPU 11 to execute a process for controlling each unit.

The RAM 13 corresponds to the main storage portion of the computer. The RAM 13 stores data necessary for the CPU 11 to execute a process. The RAM 13 is also used as a work area where information is appropriately rewritten by the CPU 11.

The auxiliary storage device 14 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 14 may store the above operating system or application program. Further, the auxiliary storage device 14 may store data used by the CPU 11 for performing various processes, or data generated by the processes of the CPU 11. As the auxiliary storage device 14, for example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), an SSD (Solid State Drive), or the like can be used.

The clock unit 15 measures the current date and time.
The communication unit 16 performs data communication with a POS system 20 or an information terminal 50 via a communication network 30 by a predetermined protocol.

As shown in FIG. 4, the electronic receipt management server 10 having such a configuration assists the member setting file 141, the store information file 142, the electronic receipt file 143, the monthly total file 144, the OTC drug setting file 145, and the OTC drug total file 146. It is stored in the storage device 14.

The member setting file 141 stores the member setting data 141R (see FIG. 5) created for each consumer who has registered as a member in order to receive the electronic receipt service. As shown in FIG. 5, the member setting data 141R includes information such as a member ID, an e-mail address, and a password. The e-mail address and password are information arbitrarily set by the consumer identified by the member ID by operating the information terminal 50.

The store information file 142 stores the store information data 142R (see FIG. 6) created for each store that is a member of the electronic receipt service. As shown in FIG. 6, the store information data 142R includes information such as a store code, a store name, and a tax status. The tax status is information indicating whether the store identified by the store code is a store in which the price of the product is tax-excluded or a store in which the price of the product is tax-included. At stores that are tax-excluded, the price of the product is the tax-excluded price. At stores that are tax-included, the price of the product is the tax-included price.

The electronic receipt file 143 stores the receipt data 24 received from each POS system 20 via the communication network 30 for a certain period of time for each member ID.

The monthly tabulation file 144 stores the monthly tabulation data 144R (see FIG. 7) created for each consumer who has registered as a member in order to receive the electronic receipt service. As shown in FIG. 7, the monthly aggregate data 144R uses the member ID and the year and month as header information, and is added to this header information to include the monthly total, information P1 related to product classification without subclassification, and subclassification. The information P2 related to the product classification of the above is stored.

The monthly total is the total price of the products purchased by the customer identified by the member ID of the header information at the store that is a member of the electronic receipt service in the month specified by the year and month of the header information. Information P1 includes a classification code, a classification name, a total classification, and a number of minor classifications. The classification total is the product of the classification code among the products purchased by the consumer identified by the member ID of the header information in the month specified by the year and month of the header information at the store that is a member of the electronic receipt service. It is the total price of the products belonging to the category. The number of subclasses is "0". Information P2 includes the number of sub-classification codes, sub-classification names, and sub-classification totals in addition to the classification code, classification name, total classification, and number of sub-classifications. The sub-category total is a sub-category code among the products purchased by the consumer identified by the member ID of the header information in the month specified by the year and month of the header information at the store that is a member of the electronic receipt service. It is the total price of the products belonging to the product classification of.

The OTC drug setting file 145 stores the product codes (for example, JAN codes) of all OTC drugs published by the Ministry of Health, Labor and Welfare as items subject to the self-medication tax system.

The OTC drug summary file 146 stores OTC drug summary data 146R (see FIG. 8) created for each consumer who has registered as a member in order to receive the electronic receipt service. As shown in FIG. 8, the OTC drug aggregate data 146R uses the member ID, the sub-classification code of the OTC drug, and the year as header information, and is added to this header information to add the year total, the deduction flag, and the purchase details data of the OTC drug. Memorize D1. The purchase detail data D1 is data of an OTC drug purchased by a consumer identified by the member ID of the header information at a store affiliated with the electronic receipt service during the year specified in the year of the header information. The purchase statement data D1 includes the product code, product name and price of the OTC drug, the store code of the store where the product was purchased, and the purchase date and time (transaction date and time). The price is the price including consumption tax.

Further, in the OTC drug aggregate data 146R, the annual total is the total price of the purchase details data D1 included in the data 146R. The deduction flag is reset to "0" until the total amount reaches the lower limit for deduction (12,000 yen for the self-medication tax system introduced from 2017), and when the total amount exceeds the lower limit, it becomes "1". It is set.

Next, the operation when the CPU 11 of the electronic receipt management server 10 receives the receipt data 24 via the communication unit 16 will be described with reference to FIGS. 9 and 10.
9 and 10 are flow charts showing an information processing procedure executed by the CPU 11 according to a control program which is a kind of application program stored in the ROM 12 or the auxiliary storage device 14. The processing contents shown in FIGS. 9 and 10 and described below are examples, and the processing procedure and processing contents are not particularly limited as long as similar results can be obtained.

When the CPU 11 receives the receipt data 24 via the communication unit 16, the information processing of the procedure shown in the flow chart of FIG. 9 is started. First, the CPU 11 stores the receipt data 24 as Act1 in the work area of the RAM 13. Next, the CPU 11 detects the member ID and the transaction date and time from the receipt data 24 as Act2. Then, the CPU 11 searches the monthly aggregate file 144 as Act3, and acquires the monthly aggregate data 144R having the member ID detected by Act2 and the year and month of the transaction date and time as header information. Then, the CPU 11 updates the monthly total of the monthly aggregated data 144R as Act4. That is, the CPU 11 adds the settlement amount of the settlement data included in the receipt data 24 to the monthly total.

Next, the CPU 11 detects one product sales data from the receipt data 24 as Act5. Then, the CPU 11 analyzes the product sales data as Act6. The analysis processing procedure will be described later.

When the analysis is completed, the CPU 11 confirms whether or not there is unanalyzed product sales data in the receipt data 24 as Act7. If there is unanalyzed product sales data (NO in Act7), the CPU 11 returns to the processing of Act5. That is, the CPU 11 detects unanalyzed product sales data from the receipt data 24 and analyzes it.

In this way, when all the product sales data included in the receipt data 24 are analyzed and it is confirmed that there is no unanalyzed product sales data (YES in Act7), the CPU 11 determines the receipt data 24 in the work area as Act8. Is saved in the electronic receipt file 143. This completes the information processing of the CPU 11 when the receipt data 24 is received.

FIG. 10 is a flow chart showing a processing procedure of analysis executed in Act 6 of FIG. First, the CPU 11 detects the classification code from the product sales data to be analyzed as Act 11. At this time, if the product sales data also includes the sub-classification code, the CPU 11 also detects the sub-classification code. Then, the CPU 11 determines whether or not the sub-classification code is detected as Act 12. When the subclassification code is not detected (NO in Act12), the CPU 11 updates the classification total of the monthly summary file 144 acquired in the processing of Act3 as Act13. That is, the CPU 11 adds the price included in the product sales data to be analyzed to the total classification of the information P1 in which the classification code detected in the processing of Act 12 is set. With the above, the CPU 11 ends the analysis.

On the other hand, when the sub-classification code is detected (YES in Act 12), the CPU 11 updates the total classification and the total sub-classification of the monthly summary file 144 acquired in the processing of Act 3 as Act 14. That is, the CPU 11 includes the product sales data to be analyzed in the total classification of the information P2 in which the classification code detected in the processing of Act 12 is set and the total classification of the small classification code detected in the processing of Act 12 in the information P2. Add the price included in.

Next, the CPU 11 detects the product code from the product sales data to be analyzed as Act 15. Then, the CPU 11 searches the OTC drug setting file 145 with the product code as Act 16, and confirms whether or not the same product code is set in the OTC drug setting file 145. When the product sales data to be analyzed is not the sales data of the OTC drug, the same product code is not set in the OTC drug setting file 145. In this case (NO in Act16), the CPU 11 ends the analysis.

On the other hand, when the product sales data to be analyzed is the sales data of the OTC drug, the same product code is set in the OTC drug setting file 145. In this case (YES in Act16), the CPU 11 searches the store information file 142 with the store code included in the receipt data 24 as Act17, and the store specified by the store code is a store excluding tax on the price of the product. Check if the store is tax-included. In the case of a store where the price of the product is tax-excluded (YES in Act17), the price included in the product sales data to be analyzed is the tax-excluded price, so the CPU 11 is included in the product sales data to be analyzed as Act18. Convert the price to the tax-included price. In the case of a store where the price of the product is tax-included (NO in Act17), the price included in the product sales data to be analyzed is the tax-included price, so the CPU 11 does not execute the processing of Act18.

Next, the CPU 11 generates OTC drug specification data D1 as Act19. The OTC drug detail data D1 includes a transaction date and time, a store code and a transaction number included in the receipt data 24, and a product code, a product name and a price included in the product sales data to be analyzed. However, when the processing of Act18 is executed, the price will be the tax-included price calculated by the processing.

When the OTC drug detail data D1 is generated, the CPU 11 stores the OTC drug detail data D1 as Act 20 in the OTC drug summary file 146. That is, the CPU 11 adds the OTC drug detail data D1 to the OTC drug summary data 146R including the membership number of the receipt data 24 and the year of the transaction date and time. Further, the CPU 11 updates the annual total of the OTC drug aggregate data 146R as Act21. That is, the CPU 11 adds the price of the OTC drug detail data D1 to the annual total.

Next, the CPU 11 confirms whether or not the deduction flag is set to "1" as Act22. When the deduction flag is set to "1" (YES in Act22), the CPU 11 ends the analysis.

If the deduction flag is not set to "1" (NO in Act22), the CPU 11 confirms whether the updated annual total as Act23 exceeds the lower limit of the deduction target. If the annual total does not exceed the lower limit (NO in Act23), the CPU 11 ends the analysis process. On the other hand, when the annual total exceeds the lower limit (YES in Act23), the CPU 11 sets the deduction flag of the OTC drug aggregate data 146R as Act24 to “1”. With the above, the CPU 11 ends the analysis.

As described above, each time the electronic receipt management server 10 receives the receipt data 24 from the POS system 20, the receipt data 24 is stored in the electronic receipt file 143 (AAct8). Further, the electronic receipt management server 10 updates the monthly total file 144 specified from the member ID and the transaction date and time included in the receipt data 24 (Act2 to Act7, Act11 to Act14).

Further, the electronic receipt management server 10 confirms whether or not the receipt data 24 includes the product sales data of the OTC drug (Act 15 to Act 16). When the product sales data of the OTC drug is included, the electronic receipt management server 10 updates the OTC drug summary file 146 based on the product sales data of the OTC drug. Specifically, first, when the price including the product sales data of the OTC drug is the tax-excluded price, the electronic receipt management server 10 converts the tax-excluded price into the tax-included price (Act17 to Act18). Next, the electronic receipt management server 10 adds the purchase detail data D1 of the OTC drug generated based on the receipt data 24 to the OTC drug aggregate data 146R specified from the member ID included in the receipt data 24 and the year of the transaction date and time. (Act19 to Act20). In addition, the annual total of the OTC drug aggregate data 146R is updated to the amount obtained by adding the tax-included price of the OTC drug (Act21).

Here, the electronic receipt management server 10 constitutes a detection means by executing the processes of Acts 15 to 16 of FIG. 10 by a computer mainly composed of the CPU 11. Further, the electronic receipt management server 10 constitutes a conversion means by executing the processes of Act 17 to Act 18 of FIG. 10 by a computer mainly composed of the CPU 11. Further, the electronic receipt management server 10 constitutes a storage means by the computer mainly composed of the CPU 11 collaborating with the auxiliary storage device 14 to execute the processes of Acts 19 to 20 in FIG.

Next, a case where a viewer who is a member of the electronic receipt service browses the purchase information of the OTC drug, which is a tax-deductible product, using the information terminal 50 will be described with reference to FIGS. 11 to 18.

11 to 13 are flow charts showing an information processing procedure executed by the CPU 11 of the electronic receipt management server 10 according to a control program which is a kind of application program stored in the ROM 12 or the auxiliary storage device 14. 14 to 18 are examples of screen transitions displayed on the display device (touch panel) of the information terminal 50. The contents of the processes shown in FIGS. 11 to 13 and described below are examples, and the process procedure and the process contents are not particularly limited as long as similar results can be obtained. Further, the content of the screen shown in FIGS. 14 to 18 and described below is also an example, and if the viewer who is the user of the information terminal 50 can obtain necessary information from the screen, the content is the content. It is not particularly limited.

A viewer who wants to browse the purchase information of an OTC drug first activates an electronic receipt browsing program installed in the information terminal 50. Then, the home screen SC1 (see FIG. 14) is displayed on the display device of the information terminal 50.
A display example of the home screen SC1 is shown in FIG. As shown in the figure, a barcode BC representing a member ID is displayed on the home screen SC1. In addition, the home icon IC1, the receipt icon IC2, and the other icon IC3 are displayed. The home icon IC1 is in the selected state, and the receipt icon IC2 and the other icon IC3 are not selected. Incidentally, by scanning the barcode SC1 of the home screen SC1 with a scanner connected to the POS terminal 21, the POS terminal 21 can input the member ID.

The viewer who confirmed the home screen SC1 touches the receipt icon IC2. Then, the receipt list request command is transmitted from the information terminal 50 to the electronic receipt management server 10. Various commands from the information terminal 50 described below, including this command, include a member ID set in the information terminal 50. It should be noted that not all commands need to include the member ID. It is not necessary to include the member ID in the command that does not need to inform the electronic receipt management server 10 of the member ID.

The CPU 11 of the electronic receipt management server 10 that has received the receipt list request command detects the receipt data 24 stored for each member ID included in the command from the electronic receipt file 143. Then, the CPU 11 creates a receipt list image based on the detected receipt data 24, and transmits the created receipt list image to the information terminal 50 of the command transmission source. Thus, in the information terminal 50, the screen of the display device is switched from the home screen SC1 to the receipt list screen SC2 (see FIG. 15).

FIG. 15 shows an example of displaying the receipt list screen SC2. As shown in the figure, the receipt list image is displayed on the receipt list screen SC2. Further, the receipt icon IC2 is in the selected state, and the home icon IC1 and the other icon IC3 are not selected.

The receipt list image includes the total amount of receipts for one month (“January total amount \ 99,999” in FIG. 15) and the first to third arrow icons M1, M2, and M3. In addition, the monthly total button BT1 is displayed on the screen SC2. When the first arrow icon M1 is touched, the image is switched to the receipt list image one month ago. When the second arrow icon M2 is touched, the image is switched to the receipt list image one month later. When the third arrow icon M3 is touched, a list of receipt data 24 generated in that month is displayed.

The viewer who confirmed the receipt list screen SC2 touches the monthly total button BT1. When the monthly total button BT1 is touched, the monthly total request command is transmitted from the information terminal 50 to the electronic receipt management server 10.

The CPU 11 of the electronic receipt management server 10 that has received the monthly aggregation request command starts information processing of the procedure shown in the flow chart of FIGS. 11 to 13.
First, the CPU 11 detects the current year and month from the date and time data measured by the clock unit 15 as Act 31 in FIG. Next, the CPU 11 searches the monthly total file 144 as Act 32, and detects the monthly total data 144R whose header information is the member ID included in the monthly total request command and the year and month detected in the process of Act 31.

If the monthly aggregated data 144R is detected, the CPU 11 generates a monthly aggregated image based on the monthly aggregated data 144R as Act33. Then, the CPU 11 transmits the monthly aggregated image as the Act 34 to the information terminal 50 of the command transmission source. Thus, in the information terminal 50, the screen of the display device is switched from the receipt list screen SC2 to the monthly total screen SC3 (see FIG. 16).

FIG. 16 shows an example of displaying one of the monthly tabulation screen SC3. As shown in the figure, the monthly tabulation image is displayed on the monthly tabulation screen SC3. The state of the receipt icon IC, the home icon IC1, and the other icon IC3 does not change.
The monthly total image includes the monthly total amount (“\ 99,999” in FIG. 16), the name by classification code and the list L1 of the total amount, and the arrow icons M5 and M6. Further, the browsing end button BT2 is displayed on the screen SC3. In the list L1, the text "list display" is attached to the sub-classification name "OTC drug" for the sub-classification code of the OTC drug.

From the monthly aggregated image, the viewer can confirm the monthly aggregated data showing the total amount of the products purchased at the member stores of the electronic receipt service in the current month and the total amount of each category.

When the viewer wants to browse the monthly aggregated data of the previous month, the viewer touches the arrow icon M5. When the arrow icon M5 is touched, the information terminal 50 transmits the first date change command to the electronic receipt management server 10.
When the viewer wants to browse the monthly aggregated data of the next month, the viewer touches the arrow icon M6. When the arrow icon M6 is touched, the information terminal 50 transmits a second year / month change command to the electronic receipt management server 10. If the monthly aggregate data 144R of the next month does not exist, the arrow icon M6 is invalidated, and the second year / month change command is not transmitted even if it is touched.

When the viewer wants to browse the purchase information of the OTC drug, the viewer touches the text "list display". When the text "list display" is touched, the information terminal 50 transmits a list display command to the electronic receipt management server 10.
To end browsing, the viewer touches the browsing end button BT2. When the browsing end button BT2 is touched, the information terminal 50 transmits a browsing end command to the electronic receipt management server 10.

The CPU 11 that has transmitted the monthly aggregated image determines whether or not the first or second year / month change command has been received as Act35. When the first or second year / month change command has not been received (NO in Act35), the CPU 11 determines whether or not the list display command has been received as Act36. When the list display command has not been received (NO in Act36), the CPU 11 determines whether or not the browsing end command has been received as Act37. If the browsing end command has not been received (NO in Act37), the CPU 11 returns to the processing of Act35. Therefore, the CPU 11 waits for the first or second year / month change command, the list display command, or the browsing end command to be received by the processing of Act35 to Act37.

When the first or second year / month change command is received in the standby state of Act35 to Act37 (YES in Act35), the CPU 11 returns to the processing of Act32. Then, in the case of the first year / month change command, the CPU 11 detects the monthly total data 144R of the previous month from the monthly total file 144 and executes the processing after Act 33. In the case of the second year / month change command, the CPU 11 detects the monthly total data 144R of the next month from the monthly total file 144 and executes the processing after Act 33. As a result, in the information terminal 50, the image displayed on the monthly total screen SC3 is switched to the monthly total image of the previous month or the next month.

When the browsing end command is received in the standby state of Act35 to Act37 (YES in Act37), the CPU 11 outputs an erase command to the information terminal 50 of the command transmission source as Act38. With the above, the CPU 11 ends the process when the monthly aggregation command is received. Incidentally, in the information terminal 50 that has received the erase command, the screen of the display device returns to the home screen SC1.

When a list display command is received in the standby state of Act35 to Act37 (YES in Act36), the CPU 11 detects the year as Act39 from the year and month of the monthly aggregated data 144R detected by Act32. Then, the CPU 11 searches the OTC drug total file 146 as Act 40, and uses the member ID included in the monthly total request command, the sub-classification code of the OTC drug, and the year detected by the processing of Act 39 as header information. OTC drug aggregate data 146R to be detected.

If the OTC drug summary data 146R is detected, the CPU 11 generates an OTC drug list image based on the OTC drug summary data 146R as Act 41. Further, the CPU 11 examines the deduction flag of the OTC drug aggregate data 146R as Act 42. Then, when the deduction flag is set to "1" (YES in Act42), that is, when the annual total exceeds the lower limit of the deduction target, the CPU 11 deducts the self-medication tax system as Act43. A message is added to the OTC drug list image to notify the viewer that the drug can be received. As a message, for example, "medical expenses are deductible", "self-medication tax deduction is available", etc. can be considered. When the deduction flag is reset to "0" (NO in Act42), that is, when the annual total does not exceed the lower limit of the deduction target, the CPU 11 does not execute the processing of Act43.

After that, the CPU 11 transmits an OTC drug list image as an Act 44 to the information terminal 50 of the command transmission source. Thus, on the information terminal 50, the screen of the display device is switched from the monthly total screen SC3 to the OTC drug list screen SC4 (see FIG. 17).

FIG. 17 shows an example of displaying the OTC drug list screen SC4. As shown in the figure, an OTC drug list image is displayed on the OTC drug list screen SC4. The state of the receipt icon IC, the home icon IC1, and the other icon IC3 does not change.

The OTC drug list image includes the annual total amount (“total: \ 99,999” in FIG. 17) A, the detailed purchase list L2 of the OTC drug, and the arrow icons M7 and M8. Further, the list transmission button B3 and the browsing end button BT4 are displayed on the screen SC4. Further, the screen SC4 in FIG. 17 is a case where the annual total exceeds the lower limit of the deduction target. That is, the OTC drug list image includes the message MS1.

The detailed purchase list L2 is created by each purchase detailed data D1 included in the OTC drug aggregate data 146R. That is, the transaction date and time, the product name, and the tax-included price of one purchase detail data D1 are represented by one row (referred to as a detail line), and this detail line is arranged in the column direction by the number of all purchase detail data D1. The detailed purchase list L2 is created. As for the transaction date and time, as shown in FIG. 17, only the date may be displayed on the detail line, or the transaction date and time may be displayed on the detail line until the time.

From the OTC drug list image, the viewer can see the OTC drug purchase information that shows the total amount of OTC drugs purchased at the member stores of the electronic receipt service in the past year and the individual details (transaction date and time, product name, and tax-included price). You can check.

When the viewer wants to browse the OTC drug purchase information of the previous year, the viewer touches the arrow icon M7. When the arrow icon M7 is touched, the information terminal 50 transmits the first year change command to the electronic receipt management server 10.
When the viewer wants to browse the OTC drug purchase information of the next year, the viewer touches the arrow icon M8. When the arrow icon M8 is touched, the information terminal 50 transmits a second year change command to the electronic receipt management server 10. If the OTC drug aggregate data 146R of the next year does not exist, the arrow icon M8 is invalidated, and the second year change command is not transmitted even if it is touched.

When it is desired to acquire a list of OTC drug purchase information, the viewer touches the list transmission button RT3. When the list transmission button RT3 is touched, the information terminal 50 transmits a list transmission command to the electronic receipt management server 10.

When the viewer wants to obtain the receipt when the OTC drug purchase information is purchased, the viewer touches the desired line. When the detail line is touched, the information terminal 50 sends a detail selection command to the electronic receipt management server 10. The item selection command includes the transaction date and time, the product name, and the tax-included price displayed on the touched item line.

To end browsing, the viewer touches the browsing end button BT4. When the browsing end button BT2 is touched, the information terminal 50 transmits a browsing end command to the electronic receipt management server 10.

The CPU 11 that has transmitted the OTC drug list image determines whether or not the browsing end command has been received as Act 51 in FIG. When the browsing end command has not been received (NO in Act51), the CPU 11 determines whether or not the first or second year change command has been received as Act52. When the first or second year change command has not been received (NO in Act 52), the CPU 11 determines whether or not the detail selection command has been received as Act 53. When the detail selection command has not been received (NO in Act53), the CPU 11 determines whether or not the list transmission command has been received as Act54. If the list transmission command has not been received (NO in Act54), the CPU 11 returns to the processing of Act51. Therefore, the CPU 11 waits for the browsing end command, the first or second year change command, the detail selection command, or the list transmission command to be received by the processing of Act51 to Act54. ..

When a browsing end command is received in the standby state of Act51 to Act54 (YES in Act51), the CPU 11 returns to the process of Act32 in FIG. As a result, in the information terminal 50, the screen of the display device returns from the OTC drug list screen SC4 to the monthly total screen SC3.

When the first or second year change command is received in the standby state of Act51 to Act54 (YES in Act52), the CPU 11 returns to the process of Act40 in FIG. Then, in the case of the first year change command, the CPU 11 detects the OTC drug aggregate data 146R of the previous year and executes the processing after Act41. In the case of the second year change command, the CPU 11 detects the OTC drug aggregate data 146R of the next year and executes the processing after Act33. As a result, in the information terminal 50, the image displayed on the OTC drug list screen SC4 is switched to the OTC drug list image of the previous year or the next year.

When the detail selection command is received in the standby state of Act51 to Act54 (YES in Act53), the CPU 11 determines the purchase details including the transaction date and time, the product name, and the price included in the detail selection command as Act60 in FIG. Data D1 is detected from OTC drug aggregate data 146R. Next, the CPU 11 searches the electronic receipt file 143 as the Act 61, and detects one receipt data 24 specified from the purchase detail data D1. Then, the CPU 11 generates an electronic receipt image as Act 62 based on the detected receipt data 24.

After the electronic receipt image is generated, the CPU 11 transmits the electronic receipt image as the Act 63 to the information terminal 50 of the command transmission source. Thus, in the information terminal 50, the screen of the display device is switched from the OTC drug list screen SC4 to the electronic receipt screen SC5 (see FIG. 18).

FIG. 18 shows an example of displaying the electronic receipt screen SC5. As shown in the figure, the electronic receipt image R is displayed on the electronic receipt screen SC5. The state of the receipt icon IC, the home icon IC1, and the other icon IC3 does not change. Further, the send button BT5 and the browsing end button BT6 are displayed on the electronic receipt screen SC5.

From the electronic receipt image R, the viewer can confirm the receipt issued by the store when the OTC drug whose product name or the like is displayed in the selected line is purchased. When the viewer wants to obtain the receipt, the viewer touches the send button BT5. When the transmission button BT5 is touched, the information terminal 50 transmits a transmission command to the electronic receipt management server 10.

When ending the viewing of the electronic receipt image R, the viewer touches the viewing end button BT6. When the browsing end button BT6 is touched, the information terminal 50 transmits a browsing end command to the electronic receipt management server 10.

The CPU 11 that has transmitted the electronic receipt image determines whether or not the browsing end command has been received as Act64. When the browsing end command has not been received (NO in Act64), the CPU 11 determines whether or not the transmission command has been received as Act65. If the transmission command has not been received, the CPU 11 returns to the Act64 process. Therefore, the CPU 11 waits for the browsing end command to be received or the transmission command to be received by the processing of Act64 and Act65.

When the browsing end command is received (YES in Act64) in the standby state of Act64 and Act65, the CPU 11 returns to the process of Act40 in FIG. As a result, in the information terminal 50, the screen of the display device returns from the electronic receipt screen SC5 to the OTC drug list screen SC4.

When a transmission command is received in the standby state of Act64 and Act65 (YES in Act65), the CPU 11 detects an e-mail address from the member setting data 141R specified by the member ID included in the transmission command as Act67. Then, the CPU 11 converts the electronic receipt image generated by the processing of the Act 62 into the data of the PDF (Portable Document Format) file as the Act 68. Then, the CPU 11 starts the mail software as Act69, creates an e-mail with the electronic receipt image converted into PDF file data as an attached file, and sends it to the e-mail address acquired by the processing of Act67. After that, the CPU 11 returns to the process of Act 40 in FIG. As a result, in the information terminal 50, the screen of the display device returns from the electronic receipt screen SC5 to the OTC drug list screen SC4.

When a list transmission command is received (YES in Act54) in the standby state of Act51 to Act54 in FIG. 12, the CPU 11 detects an e-mail address from the member setting data 141R specified by the member ID included in the transmission command as Act55. do. Further, the CPU 11 generates an image of the OTC drug purchase list as the Act 56 based on the OTC drug aggregate data 146R detected in the process of the Act 40. What kind of items are included in this OTC drug purchase list is arbitrary. For example, it may include a member ID, a year and a total of the years, and a list of transaction date and time, store code, transaction number, product code, product name and tax-included price of each purchase detail data D1. Further, the product code may be omitted from the list. Further, instead of the store code in the list, the store information file 142 may include the store name set in association with the store code.

After generating the image of the OTC drug purchase list, the CPU 11 converts the image of the OTC drug purchase list into the data of the PDF (Portable Document Format) file as Act57. Then, the CPU 11 starts the mail software as Act58, creates an e-mail with the image of the OTC drug purchase list converted into the data of the PDF file as an attached file, and sends it to the e-mail address acquired by the processing of Act55. .. After that, the CPU 11 returns to the standby state of Act51 to Act54.

Here, the electronic receipt management server 10 constitutes an information output means by executing the processes of Act 39 to Act 44 of FIG. 11 by a computer whose main body is the CPU 11. Further, the electronic receipt management server 10 constitutes a list output means by executing the processes of Act 54 to Act 58 of FIG. 12 by a computer mainly composed of the CPU 11. Further, the electronic receipt management server 10 constitutes a receipt output means by executing the processes of Act65 to Act69 of FIG. 12 by a computer mainly composed of the CPU 11.

As described above, according to the present embodiment, the viewer who is a member of the electronic receipt service can use the information terminal 50 in which the electronic receipt viewing program is installed to obtain information on the OTC drug purchased in a desired year. Can be confirmed. Here, the information relating to the OTC drug includes at least the total amount of the OTC drug purchased in the one year. If this total amount exceeds the deductible minimum amount, the viewer can receive a self-medication tax deduction. Therefore, the viewer can easily confirm whether or not the self-medication tax system can be deducted by browsing the information related to the OTC drug.

The information relating to the OTC drug may include the detailed purchase list L2 including the transaction date, product name, tax-included price, etc. for each OTC drug purchased in one year. By including the detailed purchase list L2 in the information relating to the OTC drug, the viewer can easily confirm the purchase history of each OTC drug.

In the present embodiment, when the detail line of the detail purchase list L2 is touched, the image of the receipt issued from the store when the OTC drug displayed in the detail line is purchased is displayed on the display device of the information terminal 50. Will be done. Therefore, the viewer can easily confirm the receipt issued from the store when the OTC drug is purchased in the form of an electronic receipt.

Further, in the present embodiment, when the viewer touches the send button BT5 on the electronic receipt screen SC5 on which the receipt image is displayed, the receipt image is converted into the PDF format and attached to the e-mail, and the e-mail specified by the viewer is used. It will be sent to the address. Therefore, the viewer can obtain the receipt issued from the store when the OTC drug is purchased, for example, in a paper medium.

Further, in the present embodiment, when the viewer touches the list transmission button BT3 on the OTC drug list screen SC4 in which the OTC drug list image including the detailed purchase list L2 is displayed, the image of the OTC drug purchase list is converted into the PDF format. Is attached to the e-mail and sent to the e-mail address specified by the viewer. Therefore, the viewer may obtain an OTC drug purchase list, for example, in a paper medium, which shows the purchase history (transaction date / time, store name, product name, tax-included price, etc.) of the OTC drug purchased in one year together with the total amount. can.

By the way, in the electronic receipt management server 10 of the present embodiment, it is determined whether the store that sold the OTC drug is the tax-excluded system or the tax-included system by the process of Act 17 in FIG. In the case of the tax-excluded method, the price of the OTC drug is converted into the price including tax and aggregated in the OTC drug summary file 146. Therefore, even if the tax-excluded store and the tax-included store are mixed, this embodiment can support the self-medication tax system.

Hereinafter, a modified example of the embodiment will be described.
In the above embodiment, the CPU 11 of the electronic receipt management server 10 confirms the deduction flag in Act 42 of FIG. 11, and when it is set to “1”, a predetermined message is added as Act 43. The processing of Act 42 and Act 43 may be executed between Act 33 and Act 34 in FIG. By doing so, it is possible to notify the viewer on the monthly total screen SC3 that the self-medication tax system can be deducted.

In the above embodiment, the CPU 11 of the electronic receipt management server 10 converts the receipt image and the list image of the OTC drug purchase information into a PDF file and sends the mail. The file at that time is not limited to the PDF file. For example, the list of OTC drug purchase information may be converted into a CSV file format and sent by e-mail. By doing so, the viewer can process the list of OTC drug purchase information by using an Excel file or the like.

Further, the receipt image and the list image of the OTC drug purchase information may be downloaded to the information terminal 50 instead of being sent by e-mail to the designated e-mail address. Alternatively, it may be output to a printer and printed directly. In the case of downloading, the PDF file or CSV file may be directly downloaded to the information terminal 50 when instructed to download. In the case of printing, it is sufficient to enable printing with the printer specified by the information terminal 50 when there is a printing instruction.

In the above embodiment, the CPU 11 of the electronic receipt management server 10 generates an image of the OTC drug purchase list based on the OTC drug aggregate data 146R detected in the process of Act 40 in Act 56 of FIG. In this Act 56, instead of the OTC drug purchase list, an electronic receipt image may be generated based on the receipt data specified from each purchase detail data D1. By doing so, the viewer can collectively obtain the receipt issued from the store when the OTC drug is purchased. Needless to say, in Act56, both the OTC drug purchase list and the electronic receipt image may be created and both may be sent by e-mail.

In addition, in the above-described embodiment, the tax-deductible product is an OTC drug, but the classification of the product is not particularly limited.

Further, the transfer of the electronic receipt management server 10 is generally performed in a state where a program such as a control program is stored in the ROM 12. However, the present invention is not limited to this, and a control program or the like transferred separately from the electronic receipt management server 10 may be written in the auxiliary storage device 14 included in the electronic receipt management server 10 according to an operation by a user or the like. The control program or the like can be transferred by recording it on a removable recording medium or by communicating via a network. The recording medium may be in any form as long as it can store a program such as a CD-ROM or a memory card and the device can read it. Further, the function obtained by installing or downloading the program may be one that realizes the function in cooperation with the OS (operating system) or the like inside the device.

In addition, 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 embodiments, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and variations thereof are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and the equivalent scope thereof.
The inventions described in the original claims of the present application are described below.
[1] A detection means for detecting sales data of a product subject to tax deduction from receipt data including sales data of a product purchased by a customer, and a sale of the product subject to the tax deduction detected by the detection means. A storage means for storing data in association with customer identification information associated with the receipt data including the sales data, and storage associated with the customer identification information in response to a browsing request including the customer identification information. Based on the sales data of the tax-deductible products, the information output means for outputting the total amount of the tax-deductible products sold within a predetermined period to the device of the viewing request source, and Receipt data management device.
[2] The receipt data management device according to the appendix [1], wherein the information output means further outputs a list of products that are subject to the tax deduction that are bought and sold within the predetermined period.
[3] A supplementary note [2] further comprising a list output means for outputting data based on the list output by the information output means by a predetermined output method when the transmission of the list is instructed by the device of the viewing request source. ] Described receipt data management device.
[4] When the selection of the product displayed in the list is instructed by the viewing requesting device, the receipt data including the sales data of the selected product is output to the viewing requesting device. The receipt data management device according to the appendix [2], further comprising means.
[5] When the price included in the sales data of the product subject to the tax deduction is the tax-excluded price, the information output means further comprises a conversion means for converting the tax-excluded price into the tax-excluded price. The receipt data management device according to any one of the appendices [1] to [4], wherein the total amount to be output is the total price including tax of the products subject to the tax deduction that are bought and sold within a predetermined period.
[6] A function that detects sales data of products subject to tax deduction from the receipt data on a computer that has a means of communication with an information terminal and that captures and processes receipt data including sales data of products purchased by the customer. And a function to store the detected sales data of the product subject to the tax deduction in association with the customer identification information associated with the receipt data including the sales data, and a browsing request including the customer identification information. In response to, based on the sales data of the tax-deductible product stored in association with the customer identification information, the total amount of the tax-deductible product bought and sold within a predetermined period is calculated. A program for realizing the function of outputting to the device of the viewing request source.
[7] The server detects the sales data of the product subject to tax deduction from the receipt data including the sales data of the product purchased by the customer, and the server detects the detected product subject to the tax deduction. The sales data is stored in the storage unit in association with the customer identification information associated with the receipt data including the sales data, and the server responds to a browsing request including the customer identification information and stores the sales data in the storage unit. Based on the sales data of the tax-deductible product stored in association with the customer identification information, the total amount of the tax-deductible product sold within a predetermined period is calculated by the device of the viewing request source. Receipt data management method to output to.

10 ... Electronic receipt management server, 11 ... CPU, 12 ... ROM, 13 ... RAM, 14 ... Auxiliary storage device, 15 ... Interface, 16 ... Communication unit, 20 ... POS system, 30 ... Communication network, 40 ... Base station, 50 ... Information terminal, 100 ... Electronic receipt system, 141 ... Member setting file, 142 ... Store information file, 143 ... Electronic receipt file, 144 ... Monthly summary file, 145 ... OTC drug setting file, 146 ... OTC drug summary file.

Claims (9)

A detection means for detecting sales data of products subject to tax deduction from receipt data including sales data of products purchased by customers.
A storage means for storing the sales data of the product subject to the tax deduction detected by the detection means in association with the customer identification information associated with the receipt data including the sales data.
The first tabulation method for summarizing product sales data on a monthly basis,
A second tabulation method that aggregates sales data of products subject to tax deduction on a yearly basis,
Based on the sales data aggregated by the first aggregation means in response to the browsing request including the customer identification information, the total amount of the products sold and sold in a month and the sales of the products subject to the tax deduction. An information output means for outputting image data including an image for giving an instruction to display data to the device of the viewing request source, and an information output means.
Upon receiving an instruction to display the sales data of the product subject to the tax deduction from the device of the viewing request source, the product subject to the tax deduction is based on the sales data aggregated by the second aggregation means. A receipt data management device comprising a sales data output means for outputting the annual total amount of money to the device of the viewing request source. The receipt data according to claim 1, wherein the sales data output means outputs a list of the products subject to the tax deduction together with the annual total amount of the products subject to the tax deduction to the device of the viewing request source. Management device. The sales data output means outputs a message for notifying the customer that the tax deduction can be received when the tax deduction is received by the product subject to the tax deduction, together with the total amount for the year. The receipt data management device according to claim 1 or 2. A computer that has a means of communication with an information terminal and captures and processes receipt data including sales data of products purchased by customers.
A function to detect sales data of products subject to tax deduction from the receipt data, and
A function to store the detected sales data of the product subject to the tax deduction in association with the customer identification information associated with the receipt data including the sales data.
The first aggregation function that aggregates product sales data on a monthly basis,
The second aggregation function that aggregates the sales data of the products subject to the tax deduction every year, and
Based on the sales data aggregated by the first aggregation function in response to the browsing request including the customer identification information, the total amount of products bought and sold in a month and the sales data of the products subject to the tax deduction. An information output function that outputs image data including an image for giving an instruction to display the image to the device of the viewing request source, and an information output function.
Upon receiving an instruction to display the sales data of the product subject to the tax deduction from the device of the viewing request source, the product subject to the tax deduction is based on the sales data aggregated by the second aggregation function. A program to realize a sales data output function that outputs the total annual amount to the device that requested viewing. The sales data output function is a function of outputting a list of products subject to the tax deduction to the device of the viewing request source together with the annual total amount of the products subject to the tax deduction, according to claim 4. Program. The sales data output function outputs a message for notifying the customer that the tax deduction can be received when the tax deduction is received by the product subject to the tax deduction, together with the total amount for the year. The program according to claim 4 or 5. The server detects the sales data of the product subject to tax deduction from the receipt data including the sales data of the product purchased by the customer, and uses the detected sales data of the product subject to tax deduction as the sales data. Stored in the storage unit in association with the customer identification information associated with the receipt data including the receipt data.
The server aggregates the sales data of the products on a monthly basis, and further aggregates the sales data of the products subject to the tax deduction on a yearly basis.
The server responds to the browsing request including the customer identification information, and based on the sales data aggregated for each month, the total amount of the products sold and sold in the month and the products subject to the tax deduction. The image data including the image for instructing to display the sales data and the image data including the image data are output to the device of the viewing request source.
When the server receives an instruction to display the sales data of the product subject to the tax deduction from the device of the viewing request source, the server is subject to the tax deduction based on the sales data aggregated for each year. Receipt data management method that outputs the total annual amount of products to the device that requested viewing. The receipt data management method according to claim 7, wherein the server outputs a list of the products subject to the tax deduction together with the annual total amount of the products subject to the tax deduction to the device of the viewing request source. The server outputs a message for notifying the customer that the tax deduction is available when the tax deduction is received by the product subject to the tax deduction, together with the total amount for the year. Item 7. The receipt data management method according to Item 7.

Images