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

Description

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

In Japan, in order to promote self-medication (self-administration of medication), it has been decided to introduce a self-medication tax system from fiscal year 2017. The self-medication tax system is a tax system that allows a taxpayer to deduct from their total income the total amount (including consumption tax) of pharmaceuticals that have been diverted from medical use, so-called switch OTC (over-the-counter) pharmaceuticals (hereafter simply referred to as OTC pharmaceuticals), purchased by a household in a year, if the total amount exceeds a specified lower limit. In order to comply with this tax system, taxpayers are required to keep receipts issued by pharmacies, etc. when they purchase OTC pharmaceuticals.

An electronic receipt system is effective for managing receipts. An electronic receipt system stores receipt data, including sales data for products purchased by a customer, on a server for a certain period of time. Then, within that period, the server distributes the receipt data via the Internet or other means to an information terminal used by the customer in response to a request from the customer. By using such an electronic receipt system, customers no longer need to manage paper receipts issued by pharmacies, etc.

However, current electronic receipt systems do not support the self-medication tax system. In order to build an electronic receipt system that supports the self-medication tax system, it is desirable to be able to provide taxpayers, or customers, with purchasing information on products eligible for tax deductions based on receipt data managed by a receipt data management device.

JP 2014-229072 A

The problem that the embodiment of the present invention aims to solve is to provide a receipt data management device and management method that can provide customers with purchase information on tax-deductible products based on receipt data.

In one embodiment, the receipt data management device includes a detection means, a compilation means, an output means, and a transmission means . The detection means detects sales data of products eligible for tax deduction from receipt data including sales data of products purchased by a customer. The compilation means compilations the sales data of products eligible for tax deduction purchased by the customer by year for each customer. The output means outputs an image displaying the total amount of the products eligible for tax deduction purchased by the customer for the year and a button for instructing to attach the sales data of the products eligible for tax deduction purchased by the customer during the year to an e-mail and send it to the device that has made the view request. When the transmission means receives an instruction from the device that has made the view request to attach the sales data of the products eligible for tax deduction purchased by the customer during the year to an e-mail and send it, it attaches an image or a list of the sales data of the products eligible for tax deduction purchased by the customer during the year to an e-mail address of the customer and sends it.

In one embodiment, the receipt data management method includes a server that executes the following process: the server detects sales data of tax-deductible products from receipt data including sales data of products purchased by a customer, tallying up the sales data of tax-deductible products purchased by the customer by year for each customer, outputs to the device that has requested the viewing an image displaying the total amount of tax-deductible products purchased by the customer for the year and a button for issuing an instruction to attach the sales data of tax-deductible products purchased by the customer during the year to an e-mail and send it, and when an instruction is received from the device that has requested the viewing to attach the sales data of tax-deductible products purchased by the customer during the year to an e-mail and send it, the server attaches an image or list of the sales data of tax-deductible products purchased by the customer during the year to an e-mail address of the customer and sends it.

FIG. 1 is a schematic diagram of an electronic receipt system. FIG. 4 is a schematic diagram showing the structure of receipt data. FIG. 2 is a block diagram showing a main circuit configuration of an electronic receipt management server. FIG. 2 is a schematic diagram showing main data files stored in an auxiliary storage device of the electronic receipt management server. FIG. 4 is a schematic diagram showing the structure of data stored in a member setting file. FIG. 4 is a schematic diagram showing the structure of data stored in a store information file. FIG. 4 is a schematic diagram showing the structure of data stored in a monthly summary file. FIG. 2 is a schematic diagram showing the structure of data stored in an OTC drug tally file. 5 is a flowchart showing an information processing procedure executed by a CPU of the electronic receipt management server when receiving receipt data. 10 is a flowchart specifically showing the processing procedure of the processing step “analysis” in FIG. 9 . 11 is a flowchart showing a part of an information processing procedure executed by a CPU of the electronic receipt management server when a monthly tally request command is received. 11 is a flowchart showing a part of an information processing procedure executed by a CPU of the electronic receipt management server when a monthly tally request command is received. 11 is a flowchart showing a part of an information processing procedure executed by a CPU of the electronic receipt management server when a monthly tally request command is received. FIG. 4 is a schematic diagram showing an example of a home screen displayed on a display device of an information terminal. FIG. 13 is a schematic diagram showing an example of a receipt list screen displayed on a display device of an information terminal. FIG. 13 is a schematic diagram showing an example of a monthly tally screen displayed on a display device of an information terminal. FIG. 2 is a schematic diagram showing an example of an OTC drug list screen displayed on a display device of an information terminal. FIG. 4 is a schematic diagram showing an example of an electronic receipt screen displayed on a display device of an information terminal.

Below, an embodiment of a receipt data management device and management method that can provide customers with purchase information on tax-deductible products based on 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 functions as the electronic receipt management device.

As shown in FIG. 1, the electronic receipt system 100 includes an electronic receipt management server 10, multiple POS (Point Of Sales) systems 20, a communication network 30 such as the Internet, multiple base stations 40 connected to the communication network 30, and multiple information terminals 50 capable of wireless communication with the base stations 40. The electronic receipt management server 10 is installed in an electronic receipt management center that manages the electronic receipt service. The POS system 20 is installed in each store that is a member of the electronic receipt service. The information terminals 50 are used by consumers who have registered as members to receive the electronic receipt service.

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

The POS terminal 21 generates receipt data including sales data for the products purchased by the customer who made the payment. The POS terminal 21 also accepts input of a member ID issued to a customer who has registered as a member to receive the electronic receipt service.

When the POS system 20 receives a member ID input at the POS terminal 21, it converts the receipt of the transaction in which the customer identified by the member ID is the payer into text to create receipt data 24 (see FIG. 2). The POS system 20 then 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. If the receipt is converted into text by the POS terminal 21, the receipt data 24 may be output directly 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. If the receipt is converted into text by the store server 22, the receipt data 24 is output from the store server 22 to the electronic receipt management server 10 via the communication network 30. Note that the conversion of receipts into text and the generation of receipt data 24 are well-known techniques, so a detailed description thereof will be omitted here.

Figure 2 is a schematic diagram showing the structure of 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 a product code, a classification code, a product name, a unit price, a quantity, a price, etc. The payment data includes a payment amount, a payment type, payment information, etc.

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

The classification code of the product sales data is a unique code set for each product classification 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 medical products into OTC drugs and other drugs, a subcategory code for OTC drugs and a subcategory code for other drugs are set as subcodes of the drug classification code. The product sales data for OTC medical products includes the drug classification code and the OTC drug subcategory code. Similarly, the product sales data for drugs other than OTC drugs includes the drug classification code and the other drug subcategory code.

The price is calculated by multiplying the unit price by the number of points. If the unit price includes consumption tax, the price includes tax. If the unit price excludes consumption tax, the price excludes tax. The payment type in the payment data is information that specifies the type of payment for the payment amount (cash, credit card, points, gift certificate, etc.).

Returning to FIG.
The information terminal 50 is equipped with at least a display device, an input device, and a wireless communication device. The information terminal 50 also has a web browser. A consumer who receives the electronic receipt service installs an electronic receipt viewing program, which is a dedicated application program, in the information terminal 50. By installing this electronic receipt viewing program in the information terminal 50, it becomes possible to register as a member and view receipt images, etc. By registering as a member, a member ID is set in the management area of the electronic receipt viewing program formed in the memory of the information terminal 50. As this type of information terminal 50, electronic devices such as smartphones, mobile phones, tablet terminals, and notebook computers are used.

The electronic receipt management server 10 stores receipt data 24 output from the POS system 20 of each store for a certain period of time. In response to a viewing request from an information terminal 50, the electronic receipt management server 10 transmits image data created based on the receipt data 24 to the information terminal 50 that issued the viewing request.

Figure 3 is a block diagram showing the 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, and a communication unit 16. The CPU 11, 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 path 17 such as an address bus and a data bus.

The electronic receipt management server 10 is configured as a computer including a CPU 11, a ROM 12, a RAM 13, an auxiliary storage device 14, and a system transmission line 17 that connects these components.
The CPU 11 corresponds to the central part of the computer. The CPU 11 controls each part to realize various functions of the electronic receipt management server 10 in accordance with an operating system and application programs.

ROM 12 corresponds to the main memory of the computer. ROM 12 stores the operating system and application programs. ROM 12 may also store data necessary for CPU 11 to execute processes to control each part.

RAM 13 corresponds to the main memory of the computer. RAM 13 stores data necessary for CPU 11 to execute processing. RAM 13 is also used as a work area where information is rewritten by CPU 11 as appropriate.

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

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

As shown in FIG. 4, the electronic receipt management server 10 configured as above stores a member setting file 141, a store information file 142, an electronic receipt file 143, a monthly tally file 144, an OTC drug setting file 145, and an OTC drug tally file 146 in the auxiliary storage device 14.

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

The store information file 142 stores store information data 142R (see FIG. 6) that is 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 the store code, store name, and tax status. The tax status is information that indicates whether the store identified by the store code is a store that charges product prices exclusive of tax or inclusive of tax. In stores that charge product prices exclusive of tax, the product price is the price excluding tax. In stores that charge product prices inclusive of tax, the product price is the price including tax.

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

The monthly tally file 144 stores monthly tally data 144R (see FIG. 7) that is created by year and month for each consumer who has registered as a member to receive the electronic receipt service. As shown in FIG. 7, the monthly tally data 144R uses the member ID and year and month as header information, and stores the monthly total, information P1 relating to product classifications without subcategories, and information P2 relating to product classifications with subcategories in addition to this header information.

The monthly total is the total price of products purchased by a consumer identified by the member ID in the header information at a store affiliated with the electronic receipt service during a month specified by the year and month in the header information. Information P1 includes a classification code, classification name, classification total, and number of minor categories. The classification total is the total price of products belonging to the product classification of the classification code among the products purchased by a consumer identified by the member ID in the header information at a store affiliated with the electronic receipt service during a month specified by the year and month in the header information. The number of minor categories is "0". Information P2 includes the classification code, classification name, classification total, and number of minor categories, as well as the minor category code, minor category name, and minor category total for the number of minor categories. The minor category total is the total price of products belonging to the product classification of the minor category code among the products purchased by a consumer identified by the member ID in the header information at a store affiliated with the electronic receipt service during a month specified by the year and month in the header information.

The OTC drug settings file 145 stores the product codes (e.g., JAN codes) of all OTC drugs that have been announced 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) that is created by year for each consumer who has registered as a member to receive the electronic receipt service. As shown in FIG. 8, the OTC drug summary data 146R has the member ID, OTC drug subcategory code, and year as header information, and stores the year total, deduction flag, and OTC drug purchase detail data D1 added to this header information. The purchase detail data D1 is data on OTC drugs purchased at a store affiliated with the electronic receipt service during the year specified by the year in the header information by a consumer identified by the member ID in the header information. The purchase detail data D1 includes the product code, product name, and price of the OTC drug, as well as the store code of the store where the product was purchased and the purchase date and time (transaction date and time). The price includes consumption tax.

In addition, in the OTC drug summary data 146R, the annual total is the sum of the prices in the purchase details data D1 included in the same data 146R. The deduction flag is reset to "0" until the total amount reaches the lower limit of the deduction target (12,000 yen under the self-medication tax system introduced in fiscal year 2017), and is set to "1" when the lower limit is exceeded.

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

When the CPU 11 receives receipt data 24 via the communication unit 16, it starts information processing according to the procedure shown in the flow chart of FIG. 9. First, the CPU 11 stores the receipt data 24 in the work area of the RAM 13 in Act 1. Next, the CPU 11 detects the member ID and transaction date and time from the receipt data 24 in Act 2. Then, the CPU 11 searches the monthly tally file 144 in Act 3 to obtain monthly tally data 144R whose header information is the member ID detected in Act 2 and the year and month of the transaction date and time. Then, the CPU 11 updates the monthly total of this monthly tally data 144R in Act 4. That is, the CPU 11 adds the payment amount of the payment data included in the receipt data 24 to the monthly total.

Next, in Act 5, the CPU 11 detects one item of product sales data from the receipt data 24. Then, in Act 6, the CPU 11 analyzes this item sales data. The analysis process will be described later.

After completing the analysis, the CPU 11 checks in Act 7 whether or not there is unanalyzed product sales data in the receipt data 24. If there is unanalyzed product sales data (NO in Act 7), the CPU 11 returns to the process of Act 5. That is, the CPU 11 detects the unanalyzed product sales data from the receipt data 24 and analyzes it.

In this way, all product sales data included in the receipt data 24 is analyzed, and when it is confirmed that there is no unanalyzed product sales data (YES in Act 7), the CPU 11 stores the receipt data 24 in the work area in the electronic receipt file 143 in Act 8. This marks the end of the information processing of the CPU 11 when receiving the receipt data 24.

Figure 10 is a flow diagram showing the procedure of the analysis executed in Act 6 of Figure 9. First, in Act 11, the CPU 11 detects a classification code from the product sales data to be analyzed. At this time, if a subcategory code is also included in the product sales data, the CPU 11 also detects the subcategory code. Then, in Act 12, the CPU 11 determines whether or not a subcategory code has been detected. If a subcategory code has not been detected (NO in Act 12), the CPU 11 updates the classification total of the monthly tally file 144 obtained in the processing of Act 3 in Act 13. That is, the CPU 11 adds the price included in the product sales data to be analyzed to the classification total of the information P1 in which the classification code detected in the processing of Act 12 is set. With this, the CPU 11 ends the analysis.

On the other hand, if a minor category code is detected (YES in Act 12), the CPU 11 updates the category total and minor category total of the monthly tally file 144 obtained in the processing of Act 3 in Act 14. That is, the CPU 11 adds the price included in the product sales data to be analyzed to the category total of the information P2 in which the category code detected in the processing of Act 12 is set and the minor category total for the minor category code detected in the processing of Act 12 in that information P2.

Then, in Act 15, the CPU 11 detects a product code from the product sales data to be analyzed. Then, in Act 16, the CPU 11 searches the OTC drug setting file 145 for the product code and checks whether the same product code is set in the OTC drug setting file 145. If the product sales data to be analyzed is not sales data for OTC drugs, the same product code is not set in the OTC drug setting file 145. In this case (NO in Act 16), the CPU 11 ends the analysis.

On the other hand, if the product sales data to be analyzed is sales data for OTC drugs, the same product code is set in the OTC drug setting file 145. In this case (YES in Act 16), the CPU 11 searches the store information file 142 for the store code included in the receipt data 24 in Act 17, and checks whether the store identified by the store code is a store that charges product prices exclusive of tax or inclusive of tax. If the store charges product prices exclusive of tax (YES in Act 17), the price included in the product sales data to be analyzed is a price excluding tax, so the CPU 11 converts the price included in the product sales data to be analyzed into a price including tax in Act 18. If the store charges product prices including tax (NO in Act 17), the price included in the product sales data to be analyzed is a price including tax, so the CPU 11 does not execute the process of Act 18.

Then, the CPU 11 generates OTC drug detail data D1 in Act 19. The OTC drug detail data D1 consists of the transaction date and time, store code, and transaction number contained in the receipt data 24, and the product code, product name, and price contained in the product sales data to be analyzed. However, if the processing of Act 18 is executed, the price will be the price including tax calculated in that processing.

When the OTC drug detail data D1 is generated, the CPU 11 saves the OTC drug detail data D1 in the OTC drug summary file 146 in Act 20. That is, the CPU 11 adds the OTC drug detail data D1 to the OTC drug summary data 146R, which includes the membership number and the year of the transaction date and time in the receipt data 24. The CPU 11 also updates the yearly total of the OTC drug summary data 146R in Act 21. That is, the CPU 11 adds the price of the OTC drug detail data D1 to the yearly total.

Next, the CPU 11 checks whether the deduction flag is set to "1" in Act 22. If the deduction flag is set to "1" (YES in Act 22), the CPU 11 ends the analysis.

If the deduction flag is not set to "1" (NO in Act 22), the CPU 11 checks in Act 23 whether the updated annual total exceeds the lower limit of the deduction target. If the annual total does not exceed the lower limit (NO in Act 23), the CPU 11 ends the analysis process. On the other hand, if the annual total exceeds the lower limit (YES in Act 23), the CPU 11 sets the deduction flag of the OTC drug summary data 146R to "1" in Act 24. With this, the CPU 11 ends the analysis.

In this way, every time the electronic receipt management server 10 receives receipt data 24 from the POS system 20, it saves the receipt data 24 in the electronic receipt file 143 (AAct 8). The electronic receipt management server 10 also updates the monthly tally file 144 identified from the member ID and transaction date and time included in the receipt data 24 (Acts 2 to 7, Acts 11 to 14).

Furthermore, the electronic receipt management server 10 checks whether the receipt data 24 includes product sales data for OTC drugs (Acts 15 to 16). If the product sales data for OTC drugs is included, the electronic receipt management server 10 updates the OTC drug tally file 146 based on the product sales data for the OTC drugs. Specifically, first, if the price included in the product sales data for the OTC drugs is a tax-excluded price, the electronic receipt management server 10 converts the tax-excluded price to a tax-inclusive price (Acts 17 to 18). Next, the electronic receipt management server 10 adds the purchase details data D1 for the OTC drugs generated based on the receipt data 24 to the OTC drug tally data 146R identified from the member ID and the fiscal year of the transaction date and time included in the receipt data 24 (Acts 19 to 20). In addition, the annual total of the OTC drug summary data 146R is updated to the amount including the tax-inclusive price of the OTC drug (Act 21).

The electronic receipt management server 10 constitutes a detection means by a computer mainly made up of the CPU 11 executing the processes of Act 15 to Act 16 in FIG. 10. The electronic receipt management server 10 also constitutes a conversion means by a computer mainly made up of the CPU 11 executing the processes of Act 17 to Act 18 in FIG. 10. The electronic receipt management server 10 also constitutes a storage means by a computer mainly made up of the CPU 11 cooperating with the auxiliary storage device 14 to execute the processes of Act 19 to Act 20 in FIG. 10.

Next, a case where a viewer who is a member of an electronic receipt service uses an information terminal 50 to view purchase information for OTC drugs, which are tax-deductible products, will be described with reference to Figures 11 to 18.

Figures 11 to 13 are flow charts showing information processing procedures executed by the CPU 11 of the electronic receipt management server 10 in accordance with a control program, which is a type of application program stored in the ROM 12 or the auxiliary storage device 14. Also, Figures 14 to 18 are examples of screen transitions displayed on the display device (touch panel) of the information terminal 50. Note that the contents of the processes shown in Figures 11 to 13 and described below are merely examples, and the processing procedures and contents are not particularly limited as long as similar results can be obtained. Also, the contents of the screens shown in Figures 14 to 18 and described below are merely examples, and the contents are not particularly limited as long as the viewer, who is the user of the information terminal 50, can obtain the necessary information from the screen.

A user who wishes to view purchasing information for OTC drugs first starts an electronic receipt viewing program installed in the information terminal 50. Then, a home screen SC1 (see FIG. 14) is displayed on the display device of the information terminal 50.
An example of the home screen SC1 is shown in Fig. 14. As shown in the figure, a barcode BC representing a member ID is displayed on the home screen SC1. Also displayed are a home icon IC1, a receipt icon IC2, and other icons IC3. The home icon IC1 is selected, while the receipt icon IC2 and other icons IC3 are not selected. Incidentally, by scanning the barcode BC on the home screen SC1 with a scanner connected to the POS terminal 21, the POS terminal 21 can input the member ID.

After checking the home screen SC1, the viewer touches the receipt icon IC2. This causes a receipt list request command to be sent from the information terminal 50 to the electronic receipt management server 10. This command, as well as various other commands from the information terminal 50 described below, contain the member ID set in the information terminal 50. Note that it is not necessary for all commands to contain the member ID. Commands that do not require the electronic receipt management server 10 to be notified of the member ID do not need to contain the member ID.

The CPU 11 of the electronic receipt management server 10 that receives 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. The CPU 11 then creates a receipt list image based on the detected receipt data 24, and sends the created receipt list image to the information terminal 50 that sent the command. Thus, on the information terminal 50, the display device screen switches from the home screen SC1 to the receipt list screen SC2 (see FIG. 15).

An example of the receipt list screen SC2 is shown in FIG. 15. As shown in the figure, a receipt list image is displayed on the receipt list screen SC2. In addition, the receipt icon IC2 is selected, and the home icon IC1 and other icons IC3 are unselected.

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

After checking the receipt list screen SC2, the viewer touches the monthly tally button BT1. When the monthly tally button BT1 is touched, a monthly tally request command is sent 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 tally request command starts information processing according to the procedures shown in the flowcharts of FIGS.
11, the CPU 11 detects the current year and month from the date and time data kept by the clock unit 15. Next, the CPU 11 searches the monthly tally file 144 in Act 32 to detect monthly tally data 144R having the member ID included in the monthly tally request command and the year and month detected in the processing of Act 31 as header information.

If monthly tally data 144R is detected, the CPU 11 generates a monthly tally image based on the monthly tally data 144R in Act 33. Then, the CPU 11 transmits the monthly tally image to the information terminal 50 that sent the command in Act 34. Thus, the screen of the display device of the information terminal 50 switches from the receipt list screen SC2 to the monthly tally screen SC3 (see FIG. 16).

An example of the monthly tally screen SC3 is shown in Fig. 16. As shown in the figure, the monthly tally screen SC3 displays a monthly tally image. The states of the receipt icon IC, home icon IC1 and other icons IC3 do not change.
The monthly summary image includes the total amount for the month ("99,999" in FIG. 16), a list L1 of the names and total amounts by classification code, and arrow icons M5 and M6. An end view button BT2 is also displayed on the screen SC3. In the list L1, the subcategory name "OTC Drugs" for the subcategory code of OTC drugs is accompanied by the text "List view."

Viewers can check the monthly summary image to see the total amount of products purchased at affiliated stores of the electronic receipt service during the month, as well as the total amount by category.

When the viewer wishes to view the monthly aggregated data for the previous month, the viewer touches the arrow icon M5. When the arrow icon M5 is touched, the information terminal 50 transmits a first year/month change command to the electronic receipt management server 10.
When the viewer wishes to view the monthly aggregated data for 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. Note that if the monthly aggregated data 144R for the next month does not exist, the arrow icon M6 is disabled and the second year/month change command is not transmitted even if the arrow icon M6 is touched.

When the viewer wishes to view the purchase information of OTC drugs, 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.
When the user wants to end the viewing, the user touches the end viewing button BT2. When the end viewing button BT2 is touched, the information terminal 50 transmits a command to end viewing to the electronic receipt management server 10.

After transmitting the monthly summary image, the CPU 11 determines whether or not the first or second year/month change command has been received in Act 35. If the first or second year/month change command has not been received (NO in Act 35), the CPU 11 determines whether or not the list display command has been received in Act 36. If the list display command has not been received (NO in Act 36), the CPU 11 determines whether or not the end browsing command has been received in Act 37. If the end browsing command has not been received (NO in Act 37), the CPU 11 returns to the processing of Act 35. Therefore, the CPU 11 waits to receive the first or second year/month change command, the list display command, or the end browsing command through the processing of Acts 35 to 37.

When the first or second year/month change command is received during the standby state of Act 35 to Act 37 (YES in Act 35), the CPU 11 returns to the process of Act 32. In the case of the first year/month change command, the CPU 11 detects the monthly summary data 144R of the previous month from the monthly summary file 144, and executes the process from Act 33 onwards. In the case of the second year/month change command, the CPU 11 detects the monthly summary data 144R of the next month from the monthly summary file 144, and executes the process from Act 33 onwards. As a result, in the information terminal 50, the image displayed on the monthly summary screen SC3 is switched to the monthly summary image of the previous month or the next month.

When the CPU 11 receives a viewing end command in the standby state of Act 35 to Act 37 (YES in Act 37), the CPU 11 outputs a delete command to the information terminal 50 that sent the command in Act 38. With this, the CPU 11 ends the process when the monthly tally command is received. Incidentally, in the information terminal 50 that received the delete command, the screen of the display device returns to the home screen SC1.

When a list display command is received during the standby state of Acts 35 to 37 (YES in Act 36), the CPU 11 detects the year from the month and year of the monthly total data 144R detected in Act 32 (Act 39). Then, the CPU 11 searches the OTC drug total file 146 (Act 40) to detect OTC drug total data 146R whose header information is the member ID included in the monthly total request command, the OTC drug subcategory code, and the year detected in the processing of Act 39.

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 in Act 41. The CPU 11 also checks the deduction flag of the OTC drug summary data 146R in Act 42. If the deduction flag is set to "1" (YES in Act 42), that is, if the total amount for the year exceeds the lower limit of the deduction, the CPU 11 adds a message to the OTC drug list image to inform the viewer that the self-medication tax system deduction is available in Act 43. Examples of messages that can be considered include "You are eligible for medical expenses deduction" and "You can receive deduction under the self-medication tax system." If the deduction flag is reset to "0" (NO in Act 42), that is, if the total amount for the year does not exceed the lower limit of the deduction, the CPU 11 does not execute the process of Act 43.

Then, the CPU 11 transmits the OTC drug list image to the information terminal 50 that transmitted the command (Act 44). Thus, the screen of the display device of the information terminal 50 switches from the monthly summary screen SC3 to the OTC drug list screen SC4 (see FIG. 17).

An example of the display of the OTC drug list screen SC4 is shown in FIG. 17. As shown in the figure, the OTC drug list screen SC4 displays an image of the OTC drug list. The states of the receipt icon IC, home icon IC1, and other icons IC3 do not change.

The OTC drug list image includes the total amount for the year ("Total: \99,999" in FIG. 17) A, a detailed purchase list of OTC drugs L2, and arrow icons M7 and M8. A list send button B3 and an end view button BT4 are also displayed on screen SC4. Screen SC4 in FIG. 17 shows a case where the total amount for the year exceeds the lower limit of the deduction. In other words, the OTC drug list image includes a message MS1.

The detailed purchase list L2 is created from each purchase detail data D1 included in the OTC drug summary data 146R. That is, the transaction date and time, product name, and tax-inclusive price for one purchase detail data D1 are represented in one line (called a detail line), and the detailed purchase list L2 is created by arranging this detail line in the column direction for each purchase detail data D1. Note that with regard to the transaction date and time, as shown in FIG. 17, only the date may be displayed on the detail line, or the time may also be displayed on the detail line.

Viewers can use the OTC drug list image to check OTC drug purchase information showing the total amount of OTC drugs purchased at affiliated stores of the electronic receipt service over the past year, as well as individual details (transaction date and time, product name, and price including tax).

When the viewer wishes to view the OTC drug purchasing information for the previous year, the viewer touches the arrow icon M7. When the arrow icon M7 is touched, the information terminal 50 transmits a first year change command to the electronic receipt management server 10.
If the viewer wishes to view the OTC drug purchasing information for the following 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. Note that if there is no OTC drug summary data 146R for the following year, the arrow icon M8 is disabled, and the second year change command is not transmitted even if it is touched.

If the viewer wishes to obtain a list of OTC drug purchasing information, the viewer touches the list send button RT3. When the list send button RT3 is touched, the information terminal 50 sends a list send command to the electronic receipt management server 10.

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

To end viewing, the viewer touches the End View button BT4. When the End View button BT2 is touched, the information terminal 50 sends an end view command to the electronic receipt management server 10.

After transmitting the OTC drug list image, the CPU 11 determines whether or not it has received a viewing end command in Act 51 of FIG. 12. If it has not received a viewing end command (NO in Act 51), the CPU 11 determines whether or not it has received a first or second year change command in Act 52. If it has not received a first or second year change command (NO in Act 52), the CPU 11 determines whether or not it has received a details selection command in Act 53. If it has not received a details selection command (NO in Act 53), the CPU 11 determines whether or not it has received a list transmission command in Act 54. If it has not received a list transmission command (NO in Act 54), the CPU 11 returns to the processing of Act 51. Therefore, the CPU 11 waits for the viewing end command, the first or second year change command, the details selection command, or the list transmission command to be received by the processing of Acts 51 to 54.

When the CPU 11 receives a viewing end command in the standby state of Act 51 to Act 54 (YES in Act 51), the CPU 11 returns to the processing of Act 32 in FIG. 11. 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 summary screen SC3.

When the first or second year change command is received during the standby state of Act 51 to Act 54 (YES in Act 52), the CPU 11 returns to the process of Act 40 in FIG. 11. In the case of the first year change command, the CPU 11 detects the OTC drug summary data 146R for the previous year and executes the process from Act 41 onwards. In the case of the second year change command, the CPU 11 detects the OTC drug summary data 146R for the next year and executes the process from Act 41 onwards. As a result, on the information terminal 50, the image displayed on the OTC drug list screen SC4 is switched to the OTC drug list image for the previous year or the next year.

When a detail selection command is received in the standby state of Act 51 to Act 54 (YES in Act 53), the CPU 11 detects purchase detail data D1 including the transaction date and time, product name, and price included in the detail selection command from the OTC drug summary data 146R in Act 60 of FIG. 13. Next, the CPU 11 searches the electronic receipt file 143 in Act 61 to detect one receipt data 24 identified from the purchase detail data D1. Then, the CPU 11 generates an electronic receipt image based on the detected receipt data 24 in Act 62.

When the electronic receipt image is generated, the CPU 11 transmits the electronic receipt image to the information terminal 50 that transmitted the command (Act 63). Thus, on 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).

A display example of the electronic receipt screen SC5 is shown in FIG. 18. As shown in the figure, the electronic receipt screen SC5 displays an electronic receipt image R. The states of the receipt icon IC, home icon IC1, and other icons IC3 do not change. In addition, a send button BT5 and an end viewing button BT6 are displayed on the electronic receipt screen SC5.

The viewer can check the receipt issued by the store when purchasing an OTC drug with a mark indicating that it is a self-medication eligible product on the electronic receipt image R. If the viewer wishes to obtain the receipt, he or she touches the send button BT5. When the send button BT5 is touched, the information terminal 50 sends a send command to the electronic receipt management server 10.

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

After transmitting the electronic receipt image, the CPU 11 determines whether or not a viewing end command has been received in Act 64. If a viewing end command has not been received (NO in Act 64), the CPU 11 determines whether or not a transmission command has been received in Act 65. If a transmission command has not been received, the CPU 11 returns to the processing of Act 64. Therefore, the CPU 11 waits to receive a viewing end command or a transmission command by processing Act 64 and Act 65.

When the CPU 11 receives a viewing end command in the standby state of Act 64 and Act 65 (YES in Act 64), the CPU 11 returns to the processing of Act 40 in FIG. 11. 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 Act 64 and Act 65 (YES in Act 65), the CPU 11 detects an email address from the member setting data 141R specified by the member ID included in the transmission command in Act 67. Then, the CPU 11 converts the electronic receipt image generated in the process of Act 62 into data of a portable document format (PDF) file in Act 68. Then, the CPU 11 starts an email software in Act 69, creates an email with the electronic receipt image converted into the PDF file data as an attachment, and sends the email to the email address obtained in the process of Act 67. After that, the CPU 11 returns to the process of Act 40 in FIG. 11. As a result, the screen of the display device of the information terminal 50 returns from the electronic receipt screen SC5 to the OTC drug list screen SC4.

When the CPU 11 receives a list sending command in the standby state of Act 51 to Act 54 in FIG. 12 (YES in Act 54), the CPU 11 detects an email address from the member setting data 141R specified by the member ID included in the sending command in Act 55. The CPU 11 also generates an image of an OTC drug purchase list based on the OTC drug summary data 146R detected in the processing of Act 40 in Act 56. The items included in this OTC drug purchase list are arbitrary. For example, it may include a list of the member ID, the year, and the year total, and the transaction date and time, store code, transaction number, product code, product name, and tax-inclusive price of each purchase detail data D1. The product code may also be omitted from the list. Instead of the store code in the list, the store name set in association with the store code in the store information file 142 may also be included.

After generating the image of the OTC drug purchase list, the CPU 11 converts the image of the OTC drug purchase list into PDF (Portable Document Format) file data in Act 57. Then, the CPU 11 starts up an email software in Act 58 to create an email with the image of the OTC drug purchase list converted into PDF file data as an attachment, and sends the email to the email address obtained in the process of Act 55. After that, the CPU 11 returns to the standby state of Acts 51 to 54.

The electronic receipt management server 10 constitutes an information output means by the computer having the CPU 11 as the main component executing the processes of Act 39 to Act 44 in FIG. 11. The electronic receipt management server 10 also constitutes a list output means by the computer having the CPU 11 as the main component executing the processes of Act 54 to Act 58 in FIG. 12. The electronic receipt management server 10 also constitutes a receipt output means by the computer having the CPU 11 as the main component executing the processes of Act 65 to Act 69 in FIG. 12.

Thus, according to this embodiment, a viewer who is a member of the electronic receipt service can use an information terminal 50 with an electronic receipt viewing program installed to check information related to OTC drugs purchased during a desired year. Here, information related to OTC drugs includes at least the total amount of OTC drugs purchased during that year. If this total amount exceeds the lower limit of the deduction, the viewer can receive a deduction under the self-medication tax system. Therefore, by viewing information related to OTC drugs, the viewer can easily check whether or not he or she is eligible for a deduction under the self-medication tax system.

The information on OTC drugs may include a detailed purchase list L2 that includes the transaction date, product name, and tax-inclusive price for each OTC drug purchased during the year. By including a detailed purchase list L2 in the information on OTC drugs, viewers can easily check the purchase history of each OTC drug.

In this embodiment, when a detail line in the detailed purchase list L2 is touched, an image of the receipt issued by the store when the OTC drug displayed on that detail line was purchased is displayed on the display device of the information terminal 50. Therefore, the viewer can easily check the receipt issued by the store when the OTC drug was purchased in the form of an electronic receipt.

In addition, in this 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 to PDF format, attached to an email, and sent to the email address specified by the viewer. Therefore, the viewer can obtain, for example, a paper copy of the receipt issued by the store when purchasing the OTC drug.

In addition, in this embodiment, when the viewer touches the list send button BT3 on the OTC drug list screen SC4, which displays an image of the OTC drug list including the detailed purchase list L2, the image of the OTC drug purchase list is converted to PDF format, attached to an email, and sent to the email address specified by the viewer. Therefore, the viewer can obtain, for example, on a paper medium, an OTC drug purchase list that lists the purchase history (transaction date and time, store name, product name, price including tax, etc.) of OTC drugs purchased over the year together with the total amount.

In the electronic receipt management server 10 of this embodiment, the process of Act 17 in FIG. 10 determines whether the store that sold the OTC drug uses the tax-exclusive or tax-inclusive system. If the store uses the tax-exclusive system, the price of the OTC drug is converted to a tax-inclusive price and is tallied in the OTC drug tally file 146. Therefore, even if there are a mixture of stores that use the tax-exclusive system and stores that use the tax-inclusive system, this embodiment can accommodate the self-medication tax system.

Modifications of the embodiment will be described below.
In the above embodiment, the CPU 11 of the electronic receipt management server 10 checks the deduction flag in Act 42 of Fig. 11, and if the deduction flag is set to "1", adds a predetermined message as Act 43. The processing of Act 42 and Act 43 may be executed between Act 33 and Act 34 of Fig. 11. In this way, it is possible to inform the viewer on the monthly tally screen SC3 that they are eligible for deduction under the self-medication tax system.

In the above embodiment, the CPU 11 of the electronic receipt management server 10 converted the receipt image and the list image of OTC drug purchasing information into a PDF file and sent it by email. The file is not limited to a PDF file. For example, the list of OTC drug purchasing information may be converted into a CSV file format and sent by email. This allows the viewer to process the list of OTC drug purchasing information using an Excel file or the like.

In addition, receipt images and list images of OTC drug purchasing information may be downloaded to the information terminal 50, rather than being emailed to a specified email address. Alternatively, they may be output to a printer and printed directly. In the case of downloading, a PDF file or CSV file may be downloaded directly to the information terminal 50 when a download instruction is given. In the case of printing, a PDF file or CSV file may be printed on a printer specified on the information terminal 50 when a print instruction is given.

In the above embodiment, in Act 56 of FIG. 12, the CPU 11 of the electronic receipt management server 10 generates an image of the OTC drug purchase list based on the OTC drug summary data 146R detected in the process of Act 40. In this Act 56, an electronic receipt image may be generated based on receipt data identified from each purchase detail data D1 instead of the OTC drug purchase list. In this way, the viewer can obtain receipts issued by the store when purchasing OTC drugs all at once. It goes without saying that in Act 56, both the OTC drug purchase list and the electronic receipt image may be created and both may be sent by email.

In addition, in the above embodiment, the products eligible for tax deduction are OTC drugs, but the product classification is not particularly limited.

In addition, the electronic receipt management server 10 is generally transferred with programs such as the control program stored in the ROM 12. However, this is not limited to the above, and the control program, etc. transferred separately from the electronic receipt management server 10 may be written to the auxiliary storage device 14 of the electronic receipt management server 10 in response to an operation by a user, etc. The control program, etc. may be transferred by recording it on a removable recording medium or by communication via a network. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device. In addition, the function obtained by installing or downloading the program may be realized in cooperation with an OS (operating system) or the like in the device.

Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims.
The invention as originally claimed in the present application is set forth below.
[1] A receipt data management device comprising: a detection means for detecting sales data of goods eligible for tax deductions from receipt data including sales data of goods purchased by a customer; a storage means for storing the sales data of the goods eligible for tax deductions detected by the detection means in association with customer identification information associated with the receipt data including the sales data; and an information output means for, in response to a viewing request including the customer identification information, outputting to a device that originated the viewing request the total amount of the goods eligible for tax deductions that were bought and sold within a specified period based on the sales data of the goods eligible for tax deductions that is stored in association with the customer identification information.
[2] The receipt data management device according to claim [1], wherein the information output means further outputs a list of the products eligible for the tax deduction that were bought and sold within the specified period.
[3] The receipt data management device described in appendix [2] further includes a list output means for outputting data based on the list output by the information output means in a predetermined output method when a command to transmit the list is received from the device that sent the viewing request.
[4] The receipt data management device according to appendix [2], further comprising a receipt output means for, when a command is received from the device which has issued the viewing request to select a product displayed in the list, outputting receipt data including sales data of the selected product to the device which has issued the viewing request. [5] The receipt data management device according to any one of appendices [1] to [4], further comprising a conversion means for converting a price excluding tax included in the sales data of the product eligible for tax deduction if the price included in the sales data is a price excluding tax, and the total amount output by the information output means is the total of the prices including tax of the products eligible for tax deduction that have been bought and sold within a specified period.
[6] A program for enabling a computer having a means of communication with an information terminal and which imports and processes receipt data including sales data of products purchased by a customer to realize the following functions: detect sales data of products eligible for tax deductions from the receipt data; store the detected sales data of products eligible for tax deductions in association with customer identification information associated with the receipt data including the sales data; and, in response to a viewing request including the customer identification information, output to the device which sent the viewing request the total amount of the products eligible for tax deductions that were bought and sold within a specified period based on the sales data of the products eligible for tax deductions that is stored in association with the customer identification information.
[7] A receipt data management method in which a server detects sales data of products eligible for tax deductions from receipt data including sales data of products purchased by a customer, the server stores the detected sales data of the products eligible for tax deductions in a memory unit in association with customer identification information associated with the receipt data including the sales data, and in response to a viewing request including the customer identification information, the server outputs to the device that originated the viewing request the total amount of the products eligible for tax deductions that were bought and sold within a specified period, based on the sales data of the products eligible for tax deductions that are stored in association with the customer identification information in the memory unit.

10...electronic receipt management server, 11...CPU, 12...ROM, 13...RAM, 14...auxiliary storage device, 15...clock unit, 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 (7)

A detection means for detecting sales data of products eligible for tax deduction from receipt data including sales data of products purchased by a customer;
A collection means for collecting sales data of the products eligible for the tax deduction purchased by each customer by year;
an output means for outputting to the device which has made the viewing request an image displaying a total amount of the products which are eligible for the tax deduction and which have been purchased by the customer during the year, and a button for instructing to send sales data of the products which are eligible for the tax deduction and which have been purchased by the customer during the year, as an attachment to an e-mail ;
a transmission means for, when receiving an instruction from the device which has made the browsing request to attach sales data of products which are eligible for tax deduction and which have been purchased by the customer during the year to an e-mail and transmitting the same, a list image or list of the sales data of the products which are eligible for tax deduction and which have been purchased by the customer during the year, attaching the same to an e-mail address of the customer;
A receipt data management device comprising: The receipt data management device according to claim 1 , wherein the image further displays sales data of the products that are eligible for the tax exemption and that were purchased during the year. 3. The receipt data management device according to claim 1 , wherein the image further displays an operator for instructing switching of years . 2. The receipt data management device according to claim 1 , wherein the total amount includes tax . A computer that imports and processes receipt data including sales data for products purchased by customers.
A function of detecting sales data of products eligible for tax deduction from the receipt data;
A function for annually aggregating sales data of the products eligible for the tax deduction purchased by each customer;
a function of outputting to the device which has made the viewing request an image showing the total amount of the products which the customer has purchased during the year and which are eligible for the tax deduction, and a button for instructing the customer to attach sales data of the products which the customer has purchased during the year and send the data by email;
a function of, when receiving an instruction from the device which has made the viewing request to attach sales data of products which are eligible for tax deduction and which have been purchased by a customer during a year to an e-mail and sending the attached list image or list of sales data of products which are eligible for tax deduction and which have been purchased by the customer during that year to the e-mail address of the customer;
A program to achieve this. The server detects sales data of products eligible for tax deduction from receipt data including sales data of products purchased by the customer,
The server collects sales data of the products eligible for the tax deduction purchased by each customer by year,
the server outputs to the device which has made the viewing request an image displaying the total amount of the products which are eligible for the tax deduction and which have been purchased by the customer during the year, and a button for instructing the customer to attach sales data of the products which are eligible for the tax deduction and send the data to an e-mail;
In this receipt data management method, when the server receives an instruction from the device which originated the viewing request to attach sales data of products which are eligible for tax deduction and which the customer purchased during the year to an e-mail and send it, the server attaches a list image or list of sales data of products which are eligible for tax deduction and which the customer purchased during the year to an e-mail address of the customer and sends it. a receipt data management device comprising: a detection means for detecting sales data of products eligible for tax deduction from receipt data including sales data of products purchased by a customer; a compilation means for compiling sales data of the products eligible for tax deduction purchased by the customer by year for each customer; an output means for outputting to a device which has issued a viewing request an image displaying a total amount of the products eligible for tax deduction purchased by the customer for the year and a button for issuing an instruction to attach the sales data of the products eligible for tax deduction purchased by the customer during the year to an e-mail and send it; and a transmission means for, when an instruction is received from the device which has issued the viewing request to attach the sales data of the products eligible for tax deduction purchased by the customer during the year to an e-mail and send it, attaching a list image or list of the sales data of the products eligible for tax deduction purchased by the customer during the year to an e-mail address of the customer;
An apparatus including a receiving means for receiving the image output by the output means, and a display means for displaying the received image;
A receipt data management system including: