JP2024052989A - Terminal and its program - Google Patents

Abstract

An object of the present invention is to accurately extract OTC drugs whose information is not reflected in a data file for storing information on OTC drugs, based on receipt data.
[Solution] An information processing device detects, from information about a purchased item contained in receipt data, information indicating that the purchased item is a target item of a tax system under which the purchased item can be tax-deducted when the annual purchase amount is within a predetermined range. If data identifying a purchased item for which information indicating that the purchased item is a target item has been detected from the information about the purchased item is not present in a first storage unit that stores data identifying the target item, the information processing device stores the data identifying the purchased item in a second storage unit.
[Selection diagram] Figure 11

Description

An embodiment of the present invention relates to an information processing device and a program.

In Japan, the self-medication tax system has been introduced to promote self-medication. The self-medication tax system allows for income deductions for the purchase of prescription drugs and over-the-counter drugs that have been diverted from medical use, so-called switch OTC (over-the-counter) drugs (hereinafter simply referred to as OTC drugs). For example, from January 1, 2017 to December 31, 2021, if the total amount (including consumption tax) of OTC drugs purchased by a household in a year exceeds 12,000 yen, the amount A (A = total - 12,000 yen: A is limited to 88,000 yen) that exceeds the total amount can be deducted from income. In order to comply with this tax system, consumers need to keep receipts issued by pharmacies, etc. when they purchase OTC drugs.

An electronic receipt system is effective for managing such receipts. An electronic receipt system stores receipt data, including sales data for products purchased by a consumer in a single transaction, in association with each individual consumer, for example, on a server. Then, receipts for transactions desired by the consumer can be viewed on the information terminal used by that consumer.

When using such an electronic receipt system to comply with the self-medication tax system, a data file that stores information on OTC drugs is required. For example, a server that stores receipt data detects the products purchased by consumers from the stored receipt data and checks whether information on those products exists in the data file. If it does exist, the server manages the purchasing information for that product as OTC drug purchasing information for each consumer. The server can provide consumers with tax return forms that comply with the self-medication tax system from the OTC drug purchasing information managed for each consumer.

Data files for OTC drugs are updated periodically, for example once every two months, based on information on the start and end of sales of OTC drugs provided by manufacturers and distributors. In contrast, product files that serve as the master for each product included in the receipt for each transaction and are queried by POS terminals and the like when products are sold in stores are updated more frequently over a shorter period of time. For this reason, in the case of newly sold OTC drugs, even if the drug is treated as an OTC drug in the receipt data, the information may not be reflected in the data file. In such cases, the data for the OTC drug will be missing from the consumer-specific management data.

International Publication No. 2017/056443

The problem that the embodiment of the present invention aims to solve is to provide an information processing device that can accurately extract OTC drugs whose information is not reflected in a data file for storing information on OTC drugs, based on receipt data.

In one embodiment, the information processing device includes a detection means and a storage means. The detection means detects, from information about the purchased item included in the receipt data, information indicating that the purchased item is a subject item of a tax system that allows tax deductions when the annual purchase amount is within a predetermined amount range. The storage means stores the data identifying the purchased item in the second storage unit when data identifying the subject item is not present in the first storage unit that stores data identifying the subject item, if data identifying the purchased item for which information indicating that the purchased item is detected from the information about the purchased item is not present in the first storage unit that stores data identifying the subject item.

FIG. 1 is a schematic diagram showing a schematic configuration of an electronic receipt system. FIG. 4 is a schematic diagram showing the structure of receipt data. FIG. 4 is a schematic diagram showing an example of a product master file. 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 formed in an auxiliary storage device of the electronic receipt management server. FIG. 6 is a schematic diagram showing the structure of store data stored in the store file of FIG. 5 . 6 is a schematic diagram showing the structure of product data stored in the OTC drug setting file of FIG. 5 . 6 is a schematic diagram showing the structure of maintenance data stored in the maintenance file of FIG. 5 . 11 is a flowchart showing the main steps of a process for tallying up purchase amounts for OTC medicines by member, which is executed by the CPU of the electronic receipt management server. 11 is a flowchart showing the main steps of a process for tallying up purchase amounts for OTC medicines by member, which is executed by the CPU of the electronic receipt management server. 4 is a flowchart showing the main steps of an OTC drug check process executed by a CPU of the electronic receipt management server. 11 is a flowchart showing a main procedure of a maintenance process for an OTC drug setting file executed by a CPU of the electronic receipt management server. FIG. 4 is a schematic diagram showing a display example of a maintenance screen SC.

The following describes an embodiment of an information processing device that can accurately extract OTC drugs whose information is not reflected in a data file for storing information on OTC drugs based on receipt data, with reference to the drawings. Note that this embodiment is a case in which the electronic receipt management server 10 of the electronic receipt system 100 shown in FIG. 1 is provided with the functionality of the information processing 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 network 30 such as the Internet, multiple base stations 40 connected to the network 30, multiple information terminals 50 capable of wireless communication with the base stations 40, and an administrator terminal 60. The electronic receipt management server 10 is constructed in an electronic receipt management center that manages the electronic receipt service. The POS systems 20 are constructed 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 administrator terminal 60 is used by the administrator of the electronic receipt management server 10.

The POS system 20 includes multiple POS terminals 21, a store server 22, and a printer 23, which are connected by a communication line 24 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 printer 23 is capable of printing various types of forms. The printer 23 may be a dedicated printer, or a multifunction machine with multiple functions such as copying and faxing.

The POS system 20, which functions as part of the electronic receipt system 100, has a member ID reception function and a receipt data generation function. A member ID is personal identification information issued to a consumer who has registered as a member to receive the electronic receipt service. The member ID reception function is provided by the POS terminal 21.

When the POS system 20 accepts input of a member ID at the POS terminal 21, it converts receipt print data, which indicates the details of a commercial transaction with the consumer identified by the member ID, into a structured format to create electronic receipt data 25 (see FIG. 2). The POS system 20 then outputs the receipt data 25 together with the member ID to the electronic receipt management server 10 via the network 30. The process of converting the receipt print data into a structured format may be performed by the POS terminal 21 or by the store server 22. When the process of converting the receipt print data into a structured format is performed by the POS terminal 21, the receipt data 25 may be output directly from the POS terminal 21 to the electronic receipt management server 10 via the network 30, or may be output via the store server 22. When the process of converting the receipt print data into a structured format is performed by the store server 22, the receipt data 25 is output from the store server 22 to the electronic receipt management server 10 via the network 30. The process of converting receipt print data into a structured format is a well-known technique, so a detailed explanation will be omitted here.

Figure 2 is a schematic diagram showing the structure of receipt data 25. Receipt data 25 includes a member ID, a store code, a transaction date and time, a transaction number, product sales data, and payment data. Product sales data includes product code, classification code, product name, unit price, number of items, amount, etc. Payment data includes payment amount, payment type, payment information, etc.

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 transaction is started or settled at the POS terminal 21. The transaction number is a unique number issued for each transaction. The product code is a unique code set for each product to identify each product. The classification code is a unique code set for each product classification to identify the product classification (food, daily necessities, medical supplies, clothing, etc.) based on the attributes of each product. The product name is the name given to the product identified by the corresponding product code, and the unit price is the price per item. The points are the number of the same product purchased in one transaction, and the amount is a value calculated by multiplying the points by the unit price. The payment amount is the amount paid by the member to settle the transaction. The payment type is information that specifies the type of payment (cash, credit card, points, gift certificate, etc.) for the payment amount, and the payment information is the payment amount for that payment type.

Returning to FIG.
The store server 22 manages a product master file 26. The product master file 26 stores basic information about each product sold in the store. The basic information includes items such as product code, classification code, product name, and unit price.

Figure 3 is a schematic diagram showing an example of a product master file 26. In Figure 3, product master file 26A is managed by the store server 22 of the first store. Product master file 26B is managed by the store server 22 of the second store. The first store and the second store are both pharmacies, drug stores, dispensing pharmacies, etc. that sell OTC drugs. The first store and the second store are each operated by a different business entity.

In FIG. 3, product "Drug B" with product code "2222222222" is an OTC drug. In product master file 26A, a star mark is added to the beginning of the product name of product "Drug B". In product master file 26B, a double circle mark is added to the beginning of the product name of product "Drug B". The star mark is a mark determined by the corporate entity operating the first store as information to identify the product as an OTC drug, that is, a product subject to a tax system that allows tax deductions when the annual purchase amount is within a specified amount range. Similarly, the double circle mark is a mark determined by the corporate entity operating the second store as information to identify the product as the same.

Incidentally, when the self-medication tax system is introduced, receipts and other proof documents must state that the product is an OTC drug, along with the product name, price, store name, and purchase date. Methods for indicating that a product is an OTC drug include placing a mark like the one above before the product name and stating on the proof that the product with that mark is an OTC drug, or listing the total price separately for OTC drugs only.

Returning to FIG.
The information terminal 50 includes at least a display device, an input device, and a wireless communication device. The information terminal 50 also includes 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, view receipt images, and output forms for tax returns that correspond to the self-medication tax system. 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 25 output from the POS system 20 of each store for a certain period of time. In response to a viewing request from the information terminal 50, the electronic receipt management server 10 transmits receipt image data created based on the receipt data 25 to the information terminal 50 that has made the viewing request. In response to a creation request from the information terminal 50, the electronic receipt management server 10 also creates a tax return form that complies with the self-medication tax system. The form can be printed out, for example, via the printer 23 of the POS system 20.

The administrator terminal 60 includes at least a display device, an input device, and a communication unit for the network 30. The administrator terminal 60 is capable of data communication with the electronic receipt management server 10 via the network 30. The administrator terminal 60 is used for maintenance of data files managed by the electronic receipt management server 10. In other words, an application program for controlling the maintenance of the data files is installed in the administrator terminal 60. The data files to be maintained will be described later. The maintenance processing procedure will also be described later. A personal computer, a smartphone, a tablet terminal, etc. can be used as this type of administrator terminal 60.

Figure 4 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 (Random Access Memory) 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 according to 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, the information terminal 50, or the manager terminal 60 via the network 30 using a predetermined protocol.

As shown in FIG. 5, the electronic receipt management server 10 configured in this way uses part of the memory area of the auxiliary memory device 14 as a member file 141, a store file 142, an electronic receipt file 143, a monthly tally file 144, an OTC drug setting file 145, and a maintenance file 146.

The member file 141 is an area for storing member data created for each consumer who has registered as a member to receive the electronic receipt service. The member data 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 file 142 is an area for storing store 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 data 142R includes information such as a store code, a company code, an OTC drug identification mark, and a printer address. The company code is information specific to the business entity that operates the store identified by the store code. The OTC drug identification mark is a mark determined by the business entity that operates the store identified by the store code as information for identifying an OTC drug. The printer address is a communication address for identifying the printer 23 built into the POS system 20 of the store identified by the store code. The printer 23 is designated by the store as a device for printing tax return forms that correspond to the self-medication tax system.

The electronic receipt file 143 is an area for storing receipt data 25 received from each POS system 20 via the network 30 for a certain period of time by member ID.

The monthly tally file 144 is an area for storing monthly tally data created by year and month for each consumer who has registered as a member to receive the electronic receipt service. The monthly tally data is data that totals the purchase amounts of products belonging to each product category for each month. The monthly tally data also includes data that totals the purchase amounts of OTC medicines for each month.

The OTC drug setting file 145 is an area for storing product data 145R (see FIG. 7) of OTC drugs that have been announced by the Ministry of Health, Labor and Welfare as items subject to the self-medication tax system. As shown in FIG. 7, the product data 145R includes information such as a product code, a product name, and a validity flag. The validity flag is 2-bit information that identifies whether a product identified by a product code is valid as an OTC drug. For example, when the validity flag is "1", the product is valid as an OTC drug. For example, when the validity flag is "0", the product is invalid as an OTC drug. The product data 145R of the OTC drug setting file 145 is updated periodically, for example, once every two months, based on information such as the start and end of sales of OTC drugs provided to the Ministry of Health, Labor and Welfare by manufacturers and distributors. In this embodiment, the OTC drug setting file 145 is a data file that is subject to maintenance.

The maintenance file 146 is an area for storing maintenance data 146R (see FIG. 8) for the OTC drug setting file 145 that is the target of maintenance. As shown in FIG. 8, the maintenance data 146R includes a product code, a product name, a status, a registration date and time, and an update date and time. The status is information that indicates the reflection status of the maintenance data 146R, and the reflection status can be "unprocessed", "registered", or "not registered". For example, status = 0 indicates the reflection status "unprocessed", status = 1 indicates the reflection status "registered", and status = 9 indicates the reflection status "not registered". The registration date and time is the date and time when the maintenance data 146R is registered in the maintenance file 146. The update date and time is the date and time when the reflection status of the maintenance data 146R is updated.

Here, the OTC drug setting file 145 constitutes a first storage unit, and the maintenance file 146 constitutes a second storage unit.
The data items stored in each of the files 141 to 146 are not limited to the above items, and the data may further include other items.

Next, the main information processing executed by the CPU 11 of the electronic receipt management server 10 will be described. First, the process of tabulating the purchase amounts for OTC medicines by member will be described with reference to Figures 9 and 10. Note that the contents of the process shown in Figures 9 and 10 and described below are merely examples. As long as similar results can be obtained, the procedure and contents are not particularly limited.

When the time kept by the clock unit 15 reaches a predetermined time, the CPU 11 starts information processing according to the procedure shown in the flow charts of Figures 9 and 10. Note that the time can be any time. Also, the number of times set per day is not limited to one. Two or more times may be set.

When the information processing is started, the CPU 11 first resets the counter n to "0" as Act 1 in FIG. 9. The counter n is formed in the RAM 13, for example. After resetting the counter n, the CPU 11 counts up the counter n by "1" as Act 2. Then, the CPU 11 detects the nth member data (n is the count value of the counter n) from the member file 141 as Act 3.

In Act 4, the CPU 11 checks whether the nth member data has been detected from the member file 141. If it has been detected (Act 4, YES), the CPU 11 detects the member ID from the nth member data in Act 5.

Next, in Act 6, the CPU 11 searches the electronic receipt file 143 and sequentially reads the receipt data 25 that was newly added to the electronic receipt file 143 after the previous processing. Then, in Act 7, the CPU 11 determines whether the member ID of the receipt data 25 matches the member ID detected in the processing of Act 5. If they do not match, in Act 8, the CPU 11 determines whether the search of the electronic receipt file 143 has ended. If the search has not ended (Act 8, NO), the CPU 11 returns to Act 6 and continues searching the electronic receipt file 143.

When the CPU 11 reads the receipt data 25 including the member ID detected in the processing of Act 5 from the electronic receipt file 143 (Act 7, YES), in Act 11 of FIG. 10, the CPU 11 detects the store code from the receipt data 25. Then, in Act 12, the CPU 11 searches the store file 142, acquires store data 142R including the store code detected in the processing of Act 9, and detects the OTC drug identification mark from the store data 142R.

Next, in Act 13, the CPU 11 sequentially detects the product sales data from the receipt data 25. Then, in Act 14, the CPU 11 determines whether the OTC drug identification mark detected in the processing of Act 10 is added to the product name included in the product sales data.

When the CPU 11 detects product sales data with an OTC drug identification mark added to the product name (Act 14, YES), it checks whether valid product data 145R including the product code included in the product sales data exists in the OTC drug setting file 145 (Act 15). Here, valid product data 145R refers to product data 145R whose valid flag is set to "1".

If the corresponding product data 145R exists in the OTC drug setting file 145 (Act 16, YES), the product sales data detected in the processing of Act 13 is data on OTC drugs purchased by the member identified by the member ID after the previous processing. In Act 17, the CPU 11 stores the product sales data in the work area of the RAM 13. Then, the CPU 11 proceeds to Act 18.

On the other hand, if the OTC drug identification mark is not added to the product name (Act 14, NO), the CPU 11 skips the processing of Act 15 to Act 17 and proceeds to Act 18. Also, if the OTC drug identification mark is added to the product name but the corresponding product data 145R does not exist in the OTC drug setting file 145 (Act 16, NO), the CPU 11 skips the processing of Act 17 and proceeds to Act 18.

In Act 18, the CPU 11 determines whether or not the detection of the product sales data has been completed from the receipt data 25 read from the electronic receipt file 143. If the detection has not been completed (Act 18, NO), the CPU 11 returns to the processing of Act 13. Then, the CPU 11 repeats the processing of Act 13 to Act 18 in the same manner as described above.

When all product sales data has been detected from the receipt data 25 (Act 18, YES), the CPU 11 proceeds to Act 8 in FIG. 9. That is, the CPU 11 determines whether the search of the electronic receipt file 143 is complete. If the search is not complete (Act 8, NO), the CPU 11 returns to Act 6 and continues searching the electronic receipt file 143.

When the search of the electronic receipt file 143 is thus completed (Act 8, YES), the CPU 11 performs a tallying process for each member based on the product sales data of OTC drugs stored in the work area. That is, the CPU 11 searches the monthly tally file 144 for the member ID acquired in the processing of Act 5, and adds the amount of the product sales data stored in the work area to the total purchase amount of OTC drugs included in the monthly tally data set for that member ID.

When the tallying process is completed, the CPU 11 returns to Act 2. That is, the CPU 11 further counts up the counter n by "1". Then, the CPU 11 detects the nth member data from the member file 141.

If the CPU 11 cannot detect the nth member data from the member file 141 (Act 4, NO), that is, if it has completed processing from Act 5 onwards for all member data stored in the member file 141, it ends this information processing.

Next, the OTC drug check process executed by the CPU 11 each time receipt data 25 is received from the POS system 20 will be described with reference to FIG. 11. Note that the content of the process shown in FIG. 11 and described below is an example. The procedure and content are not particularly limited as long as similar results can be obtained.

In Act 21, the CPU 11 waits to receive receipt data. When receipt data 25 is received via the communication unit 16 (Act 21, YES), the CPU 11 resets the determination flag F to "0" in Act 22. The determination flag F is stored in the RAM 13.

In Act 23, the CPU 11 detects the store code from the receipt data 25. Then, in Act 24, the CPU 11 searches the store file 142 and detects the OTC drug identification mark from the store data 142R that includes the store code detected in the processing of Act 23.

Next, in Act 25, the CPU 11 sequentially detects the product sales data from the receipt data 25. Then, in Act 26, the CPU 11 determines whether the OTC drug identification mark detected in the process of Act 24 is added to the product name included in the product sales data. If the OTC drug identification mark is not added (Act 26, NO), the CPU 11 proceeds to the process of Act 33.

When product sales data with an OTC drug identification mark added to the product name is detected (Act 26, YES), the CPU 11 checks in Act 27 whether or not valid product data 145R including the product code included in the product sales data exists in the OTC drug setting file 145. If valid product data 145R exists (Act 28, YES), the CPU 11 proceeds to the processing of Act 33.

In contrast, if the corresponding product data 145R does not exist in the OTC drug setting file 145 (Act 28, NO), the CPU 11 checks in Act 29 whether maintenance data 146R including the product code and product name of the product sales data to which the OTC drug identification mark has been added is already stored in the maintenance file 146. If the duplicate maintenance data 146R is already stored in the maintenance file 146 (Act 29, YES), the CPU 11 proceeds to the processing of Act 33.

In contrast, if the duplicated maintenance data 146R is not stored in the maintenance file 146 (Act 29, NO), the CPU 11 writes and stores the maintenance data 146R including the product code and product name of the product sales data to which the OTC drug identification mark has been added in the maintenance file 146 (Act 30). At this time, the registration date and time and update date and time of the maintenance data 146R are set to the current date and time measured by the clock unit 15.

When writing to the maintenance file 146 is completed, the CPU 11 checks whether the determination flag F is set to "1" in Act 31. If the determination flag F is not set (Act 31, NO), the CPU 11 sets the determination flag F to "1" in Act 32. If the determination flag F is already set to "1" (Act 31, NO) or is set to "1" in Act 32, the CPU 11 proceeds to Act 33.

In Act 33, the CPU 11 determines whether or not the detection of the product sales data from the receipt data 25 has been completed. If the detection has not been completed (Act 33, NO), the CPU 11 returns to the processing of Act 25. Then, the CPU 11 repeats the processing of Acts 25 to 33 in the same manner as described above.

When all the product sales data has been detected from the receipt data 25 (Act 33, YES), the CPU 11 checks whether the determination flag F is set to "1" in Act 34. If the determination flag F is set to "1" (Act 33, YES), the CPU 11 notifies the maintenance operator that the maintenance data 146R has been written to the maintenance file 146 in Act 35. Specifically, the CPU 11 automatically sends an email to the administrator terminal 60, and notifies the administrator terminal 60 in the body of the email that the maintenance data has been written to the maintenance file 146. Note that, if the determination flag F is reset to "0" in Act 34 (Act 34, NO), the maintenance data 146R has not been written to the maintenance file 146. In this case, the CPU 11 skips the process of Act 35. With this, the CPU 11 ends the process after receiving the receipt data.

The computer of the electronic receipt management server 10, which is mainly composed of the CPU 11, constitutes a detection means by executing the processes of Acts 21 to 26 in FIG. 11. The computer also constitutes a storage means by executing the processes of Acts 27 to 30 in FIG. 11. The computer also constitutes a notification means by executing the processes of Acts 31 to 32 in FIG. 11.

Thus, if product data 145R including the product code and product name of product sales data with a mark added to the product name is not present in the OTC drug setting file 145, maintenance data 146R related to that product sales data is stored in the maintenance file 146.

Generally, when a manufacturer or distributor provides information regarding the start of sales of OTC drugs, the product master file 26 is updated at each store. The electronic receipt management center also updates the OTC drug setting file 145. However, the timing at which the product master file 26 is updated and the timing at which the OTC drug setting file 145 is updated are not synchronized. For this reason, as described above, there may be cases where product data 145R including the product code and product name of the product sales data with a mark added to the product name does not exist in the OTC drug setting file 145. In such cases, in this embodiment, maintenance data 146R including the product code and product name is stored in the maintenance file 146.

Next, the maintenance process of the OTC drug setting file 145 executed by the CPU 11 will be described with reference to FIG. 12. Note that the content of the process shown in FIG. 12 and described below is an example. The procedure and content are not particularly limited as long as similar results can be obtained.

The operator of the administrator terminal 60, who has confirmed the email notifying that the maintenance data 146R has been written to the maintenance file 146, operates the administrator terminal 60 to start a maintenance application program. This starts up a maintenance command that is sent from the administrator terminal 60 to the electronic receipt management server 10.

In Act 41 of FIG. 12, the CPU 11 of the electronic receipt management server 10 waits for a maintenance command. Then, when the CPU 11 detects that a maintenance command has been received via the communication unit 16 (Act 41, YES), in Act 42, the CPU 11 creates display data of a maintenance list based on the maintenance data 146R stored in the maintenance file 146. The maintenance list is a list of maintenance data 146R whose reflection status is "unprocessed." In Act 43, the CPU 11 controls the communication unit 16 to send this display data to the administrator terminal 60. Through this control, the display data of the maintenance list is sent to the administrator terminal 60 via the network 30. In the administrator terminal 60 that has received this display data, a maintenance screen SC (see FIG. 13) is displayed on the display device.

Figure 13 is an example of a maintenance screen SC. As shown in Figure 13, the maintenance screen SC displays a maintenance list L, a registration button B1, and a cancel button B2. The maintenance list L lists the product codes and product names that make up the maintenance data 146R, as well as the registration date and time, update date and time, and reflection status. The registration date and time is the date and time when the data was written to the maintenance file 146 in Act 30 of Figure 11. The update date and time is the date and time when the reflection status was updated. The maintenance list L displays check boxes CB in association with each product code.

After checking the maintenance screen SC, the operator selects a product that is publicly announced as an OTC drug from the maintenance list L and checks the corresponding check box CB. The operator then inputs the registration button B1. When the registration button B1 is input, a registration command is sent from the administrator terminal 60 to the electronic receipt management server 10. The registration command includes paired data of the product code and product name that are checked in the corresponding check box CB in the maintenance list L. Note that if the operator wishes to end the maintenance work without inputting the registration button B1, he or she inputs the stop button B2. When the stop button B2 is input, a stop command is sent from the administrator terminal 60 to the electronic receipt management server 10.

The CPU 11 of the electronic receipt management server 10 that has transmitted the display data of the maintenance list checks whether or not a stop command has been received in Act 44. If a stop command has not been received (Act 44, NO), the CPU 11 checks whether or not a registration command has been received in Act 45. If a registration command has not been received (Act 45, NO), the CPU 11 returns to Act 44. Thus, the CPU 11 waits to receive a stop command or a registration command by processing Act 44 and Act 45.

In this standby state, if it is detected that a stop command has been received via the communication unit 16 (Act 44, YES), the CPU 11 ends this process.

On the other hand, when it is detected that a registration command has been received (Act 45, YES), the CPU 11 detects paired data of a product code and a product name from the registration command (Act 46). The CPU 11 then creates product data 145R for the OTC drug that includes this paired data, and adds it to the OTC drug setting file 145. At this time, the valid flag of the product data 145R is set to "1" indicating a valid state.

Once the product data 145R, including the product code and product name of the paired data included in the registration command, has been added to the OTC drug setting file 145 in this manner, the CPU 11 updates the status of the maintenance data 146R in Act 47. Specifically, for the maintenance data 146R that was added to the OTC drug setting file 145, the reflection status is also updated from "unprocessed" to "registered". On the other hand, for the maintenance data 146R that was not added to the OTC drug setting file 145, the reflection status is updated from "unprocessed" to "not registered". With this, the CPU 11 ends this process.

The computer of the electronic receipt management server 10, which is mainly composed of the CPU 11, constitutes an additional means by executing the processes of Act 45 and Act 46 in FIG. 12. The computer also constitutes a receiving means by executing the processes of Act 42 and Act 43 in FIG. 12.

In this way, the electronic receipt management server 10 of this embodiment can accurately extract OTC drugs whose information is not reflected in the OTC drug setting file 145 based on the receipt data received from the POS system 20 of each store.

In addition, the electronic receipt management server 10 can notify the maintenance operator that an OTC drug has been extracted whose information is not reflected in the OTC drug setting file 145.

In addition, according to the electronic receipt management server 10, information on OTC drugs that is not reflected in the OTC drug setting file 145 can be added to the OTC drug setting file 145 in response to instructions from an operator in charge of maintenance. Therefore, by adding the missing information to the OTC drug setting file 145 before the member-by-member aggregation process for OTC drug purchase amounts is started, the electronic receipt management server 10 can accurately manage the purchase information of OTC drugs for each consumer.

However, when updating the product master file 26 at each store, there may be cases where a mark is mistakenly applied to a product other than an OTC drug. In such cases, in this embodiment, data on the product that is not an OTC drug is stored in the maintenance file 146. However, in this embodiment, the electronic receipt management server 10 creates a maintenance list L based on the data stored in the maintenance file 146, displays this maintenance list L on the display device of the administrator terminal 60, and accepts a selection of whether or not to add the list to the OTC drug setting file 145. This makes it possible to prevent data related to products other than OTC drugs from being mistakenly added to the OTC drug setting file 145.

Next, we will explain the transformation sequence of this embodiment.

In the above embodiment, the electronic receipt management server 10 is provided with the function of the information processing device. In this regard, the function of the information processing device may be provided in a computer device other than the electronic receipt management server 10. In this case, the computer device having the function of the information processing device is connected to the electronic receipt management server 10 via a communication means and has a maintenance file 146. The computer device then imports the receipt data 25 received by the electronic receipt management server 10 and executes the information processing shown in the flow charts of FIG. 11 and FIG. 12. In this way, a computer device that can accurately extract OTC drugs whose information is not reflected in the OTC drug setting file 145 can be realized. Such a computer device may be, for example, the administrator terminal 60.

In the above embodiment, the store data stored in the store file 142 includes an OTC drug identification mark. The electronic receipt management server 10 then searches the store file 142 using the store code included in the receipt data to obtain the mark used at that store. In this regard, the following may be done. That is, the receipt data includes a mark added to the product name of an OTC drug, as well as text indicating that the product to which the mark is attached is an OTC drug. The electronic receipt management server 10 then analyzes this text to obtain the mark. This eliminates the need to store an OTC drug identification mark for each store in the store file 142.

In the above embodiment, an OTC drug identification mark is set for each store in the store file 142, but an OTC drug identification mark may be set for each business entity that operates the store. In this case, a business entity code that identifies the business entity is included in the receipt data 25. A data file that centrally manages OTC drug identification marks for each business entity code is then provided in the electronic receipt management server 10. This allows an OTC drug identification mark to be set for each business entity. Also, by incorporating a store code into the data file, it is possible to set an OTC drug identification mark by a combination of a business entity code and a store code.

In addition, the information indicating that the purchased product is an OTC drug does not necessarily have to be a mark. The product sales data included in the receipt data may contain information other than a mark indicating that the product is an OTC drug.

In the above embodiment, the operator who has checked the maintenance screen SC checks the check boxes CB corresponding to products that are publicly announced as OTC drugs from the maintenance list L. In this regard, the check boxes CB are checked as a default, and check boxes CB corresponding to products other than OTC drugs may be unchecked.

In the above embodiment, OTC medicines are subject to a tax system that allows tax deductions when the annual purchase amount is within a specified range. The subject products are not necessarily limited to OTC medicines. This embodiment can be similarly applied to similar tax-subject products.

The information processing device is generally transferred with the program stored in ROM 12 or auxiliary storage device 14. However, the present invention is not limited to this, and the program may be transferred without being stored in ROM 12 or auxiliary storage device 14. In this case, the program transferred separately from the information processing device is written to a writable storage device of the information processing device in response to an operation by the user or the like. The program can 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 can be read by the device. 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 embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included within the scope and gist of the invention, and are included in the scope of the invention and its equivalents as set forth in the claims.

10...electronic receipt management server, 20...POS system, 21...POS terminal, 22...store server, 23...printer, 25...receipt data, 26...product master file, 30...network, 40...base station, 50...information terminal, 60...administrator terminal, 100...electronic receipt system, 141...membership file, 142...store file, 143...electronic receipt file, 144...monthly summary file, 145...OTC drug setting file, 146...maintenance file.

An embodiment of the present invention relates to a terminal and a program therefor .

The problem that an embodiment of the present invention aims to solve is to provide a terminal for an electronic receipt system that can accurately extract OTC drugs whose information is not reflected in a data file for storing information on OTC drugs, based on receipt data.

In one embodiment, the terminal includes a display device, a transmission means, a reception means, and a display control means . The transmission means transmits to the electronic receipt management server a maintenance command requesting the creation of a maintenance list including data identifying a purchased product for which information indicating that the purchased product is subject to a tax system that allows tax deduction when the annual purchase amount is within a predetermined amount range has been detected from information on the purchased product included in the receipt data, and data identifying a purchased product that does not exist in a storage unit that stores the data identifying the subject product, the maintenance list including the product name of the purchased product and the date on which it was confirmed that the purchased product does not exist in the storage unit. The reception means receives display data of the maintenance list from the electronic receipt management server that transmitted the maintenance command. The display control means causes the display device to display the maintenance list based on the received display data.

Hereinafter, an embodiment of an information processing device that can accurately extract OTC drugs whose information is not reflected in a data file for storing information on OTC drugs based on receipt data will be described with reference to the drawings. Note that this embodiment is a case where the electronic receipt management server 10 of the electronic receipt system 100 shown in FIG. 1 is provided with a function as the information processing 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] An information processing device comprising: a detection means for detecting, from information regarding a purchased item contained in receipt data, information indicating that the purchased item is a product subject to a tax system under which the purchased item can receive a tax deduction when the annual purchase amount is within a specified amount range; and a storage means for storing, in a second storage unit, data identifying the purchased item for which information indicating that the purchased item is a product subject to a tax system has been detected from the information regarding the purchased item, if the data identifying the purchased item is not present in a first storage unit which stores data identifying the product subject to the tax.
[2] The information processing device according to appendix [1], further comprising a notification means for notifying an external party that the data identifying the purchased product has been stored in the second memory unit.
[3] An information processing device according to appendix [1] or [2], further comprising an adding means for adding data identifying the purchased product stored in the second memory unit to the first memory unit.
[4] An information processing device as described in Appendix [3], further comprising a receiving means for receiving whether or not to add the data identifying the purchased product stored in the second memory unit to the first memory unit, wherein the adding means adds the data identifying the purchased product for which the request to add has been accepted to the first memory unit.
[5] An information processing device described in any one of appendices [1] to [4], wherein the detection means checks whether a predetermined mark is attached to the product name included in the information regarding the purchased product, and if so, detects the mark as information indicating that it is the target product.
[6] A program for causing a computer to function as a detection means for detecting, from information about a purchased item contained in receipt data, information indicating that the purchased item is subject to a tax system under which the annual purchase amount is within a specified range of amounts, and a storage means for storing, in a second storage unit, data identifying the purchased item for which information indicating that the purchased item is a subject item has been detected from the information about the purchased item, if the data identifying the purchased item is not present in a first storage unit that stores data identifying the subject item.

Claims (6)

a detection means for detecting, from information on the purchased goods included in the receipt data, information indicating that the purchased goods are subject to a tax system under which the purchased goods can be tax-deducted when the annual purchase amount is within a predetermined amount range;
an information processing device comprising: a storage means for storing data identifying the purchased product in a second storage unit when data identifying the purchased product, for which information indicating that it is the target product is detected from information regarding the purchased product, is not present in a first storage unit that stores data identifying the target product. The information processing device according to claim 1, further comprising a notification means for notifying an external device that the data identifying the purchased product has been stored in the second storage unit. The information processing device according to claim 1 or 2, further comprising an adding means for adding data identifying the purchased product stored in the second storage unit to the first storage unit. The method further includes a reception unit for receiving a request for whether or not to add the data identifying the purchased product stored in the second storage unit to the first storage unit,
The information processing apparatus according to claim 3 , wherein said adding means adds data identifying said purchased product that has been accepted for addition to said first storage section. The information processing device according to any one of claims 1 to 4, wherein the detection means checks whether a predetermined mark is attached to the product name included in the information about the purchased product, and if so, detects the mark as information indicating that the product is the target product. Computer,
A detection means for detecting, from information on the purchased goods included in the receipt data, information indicating that the purchased goods are subject to a tax system under which the purchased goods can be tax-deducted when the annual purchase amount is within a predetermined amount range; and
A program for functioning as a storage means for storing data identifying a purchased product in a second storage unit when data identifying the purchased product, for which information indicating that it is the target product has been detected from information regarding the purchased product, is not present in a first storage unit that stores data identifying the target product.