JP6808661B2 - Information processing equipment and programs - Google Patents

Description

Embodiments of the present invention relate to information processing devices and programs.

In Japan, a self-medication tax system has been introduced to promote self-medication (self-medication). The self-medication tax system receives an income deduction for the purchase cost of drugs requiring guidance 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). It is a system that can be used. For example, from January 1, 2017 to December 31, 2021, if the total amount of OTC drugs purchased by one household in a year (including consumption tax) exceeds 12,000 yen, the excess amount will be exceeded. A (A = total-12,000 yen: A is limited to 88,000 yen) can be subject to income deduction. In order to comply with such a tax system, consumers need to manage receipts issued by pharmacies and the like when they purchase OTC drugs.

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

When dealing with the self-medication tax system using such an electronic receipt system, a data file storing information on OTC drugs is required. For example, a server that stores receipt data detects a product purchased by a consumer from the stored receipt data and confirms whether the information of the product exists in the data file. If it exists, the server manages the purchase information of the product as the purchase information of the OTC drug for each consumer. The server can provide consumers with a tax return form corresponding to the self-medication tax system from the purchase information of OTC drugs managed for each consumer.

The data file of the OTC drug is regularly updated, for example, once every two months, based on the information such as the start of sales and the discontinuation of the sale of the OTC drug provided by the manufacturer / distributor. On the other hand, when a product is sold at a store, the product file that is inquired by a POS terminal or the like and is a master of each product included in the receipt of each transaction is updated frequently in a shorter period of time. Therefore, in the case of a newly sold OTC drug, even if it is treated as an OTC drug in the receipt data, the information may not be reflected in the data file. In such a case, the data of the OTC drug is leaked from the management data for each consumer.

International Publication No. 2017/05/6443

The problem to be solved by the embodiment of the present invention is an information processing device capable of accurately extracting an OTC drug whose information is not reflected in a day file for storing information on the OTC drug based on the receipt data. It is what we are trying to provide.

In one embodiment, the information processing device comprises detection means, storage means, and additional means . The detection means detects information indicating that the purchased product is a tax-deductible product when the annual purchase amount is within a predetermined amount range from the information on the purchased product included in the receipt data. To do. When the data for identifying the purchased product in which the information indicating that the product is the target product is detected from the information about the purchased product does not exist in the first storage unit that stores the data for identifying the target product, the storage means is the purchased product. The data for identifying the above is stored in the second storage unit for storing the maintenance data for the first storage unit . The additional means adds data for identifying the purchased product stored in the second storage unit to the first storage unit.

The schematic diagram which shows the schematic structure of the electronic receipt system. The schematic diagram which shows the structure of the receipt data. The schematic diagram which shows an example of the product master file. A block diagram showing a circuit configuration of a main part of an electronic receipt management server. The schematic diagram which shows the main data file formed in the auxiliary storage device of an electronic receipt management server. The schematic diagram which shows the structure of the store data stored in the store file of FIG. The schematic diagram which shows the structure of the product data stored in the OTC drug setting file of FIG. The schematic diagram which shows the structure of the maintenance data stored in the maintenance file of FIG. The flow chart which shows the main part procedure of the member-specific aggregation processing of the purchase amount related to the OTC drug executed by the CPU of the electronic receipt management server. The flow chart which shows the main part procedure of the member-specific aggregation processing of the purchase amount related to the OTC drug executed by the CPU of the electronic receipt management server. The flow chart which shows the main part procedure of the OTC drug check process executed by the CPU of the electronic receipt management server. The flow chart which shows the main part procedure of the maintenance process of the OTC drug setting file executed by the CPU of the electronic receipt management server. The schematic diagram which shows one display example of maintenance screen SC.

Hereinafter, an embodiment of an information processing apparatus capable of accurately extracting an OTC drug whose information is not reflected in a day file for storing information on the OTC drug based on the receipt data will be described with reference to the drawings. In this embodiment, 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.

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

The POS system 20 includes a plurality of POS terminals 21, a store server 22, and a printer 23, and these are connected by a communication line 24 such as a LAN (Local Area Network). The POS terminal 21 functions as a settlement terminal for commercial transactions. The store server 22 manages sales, inventory, and the like of the entire store based on the data of commercial transactions settled by each POS terminal 21. The printer 23 is compatible with printing various forms. The printer 23 may be a dedicated printing machine, or may be a multifunction device having multiple functions such as copying and facsimile.

The POS system 20 has a member ID reception function and a receipt data generation function in order to play a part of the electronic receipt system 100. The member ID is personal identification information issued to a consumer who has registered as a member in order to receive the electronic receipt service. The POS terminal 21 has a member ID reception function.

When the POS system 20 receives the input of the member ID on the POS terminal 21, the POS system 20 converts the receipt print data representing the contents of the commercial transaction for the consumer identified by the member ID into a structured format, and electronically receives the receipt data 25. (See Figure 2). Then, the POS system 20 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 the structured format may be performed by the POS terminal 21 or the store server 22. When the POS terminal 21 performs the process of converting the receipt print data into the structured format, the receipt data 25 may be directly output from the POS terminal 21 to the electronic receipt management server 10 via the network 30, or the store server 22 may be output. It may be output via. When the store server 22 performs a process of converting the receipt print data into a structured format, the receipt data 25 is output from the store server 22 to the electronic receipt management server 10 via the network 30. Since the process of converting the receipt print data into the structured format is a well-known technique, detailed description thereof will be omitted here.

FIG. 2 is a schematic view showing the structure of the receipt data 25. The receipt data 25 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, points, an amount of money, and the like. The payment data includes the payment amount, payment type, payment information, and the like.

The store code is a unique code set for each store to identify each store. The transaction date and time is, for example, the date and time when the commercial transaction is started or settled on the POS terminal 21. The transaction number is a unique number issued for each commercial transaction. The product code is a unique code set for each product in order to identify each product. The classification code is a unique code set for each product classification in order to identify the product classification (food, daily necessities, medical products, clothing, etc.) based on the attributes of each product. The product name is the name given to the product identified by the corresponding product code, and the unit price is the price per product. The score is the number of items purchased for the same product in one commercial transaction, and the amount is a value calculated by multiplying the unit price by the score. The settlement amount is the amount paid by the member to settle a commercial transaction. The payment type is information that specifies the type of payment (cash, credit card, points, cash voucher, etc.) for the payment amount, and the payment information is the payment amount in the payment type.

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

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

In FIG. 3, the product “Pharmaceutical B” of the product code “2222222222” is an OTC drug. In the product master file 26A, a star mark is added to the beginning of the product name of the product "pharmaceutical product B". In the product master file 26B, a double circle mark is added to the beginning of the product name of the product "pharmaceutical product B". The star mark is defined as information to identify that the business entity that operates the first store is an OTC drug, that is, a product subject to tax deduction that can be deducted when the annual purchase amount is within the specified amount range. It is a mark. Similarly, the double circle mark is a mark defined as information for identifying that the business entity operating the second store is the same target product.

Incidentally, when introducing the self-medication tax system, it is stipulated that the certificate such as the receipt clearly states that the product is an OTC drug together with the product name, amount, store name, and purchase date. Then, as a method of clearly indicating that the product is an OTC drug, a method of adding the above mark in front of the product name and stating that the product with the mark is an OTC drug, or a method of stating that the product is an OTC drug, or , There is a method of listing the total amount separately only for OTC drugs.

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

The electronic receipt management server 10 stores the receipt data 25 output from the POS system 20 of each store for a certain period of time. Then, the electronic receipt management server 10 responds to the browsing request from the information terminal 50 and transmits the data of the receipt image created based on the receipt data 25 to the information terminal 50 of the browsing request source. Further, the electronic receipt management server 10 prepares a form for final tax return corresponding to the self-medication tax system in response to the preparation request from the information terminal 50. 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 can perform data communication with the electronic receipt management server 10 via the network 30. The administrator terminal 60 is used for maintenance of the data file managed by the electronic receipt management server 10. In other words, an application program for controlling the maintenance of the data file 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. As the administrator terminal 60 of this type, a personal computer, a smartphone, a tablet terminal, or the like is used.

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

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

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

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

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

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

As shown in FIG. 5, the electronic receipt management server 10 having such a configuration sets a part of the storage area of the auxiliary storage device 14 as a member file 141, a store file 142, an electronic receipt file 143, a monthly total file 144, and an OTC drug setting. Used as file 145 and maintenance file 146.

The member file 141 is an area for storing member data created for each consumer who has registered as a member in order to receive the electronic receipt service. The member data includes information such as a member ID, an e-mail address, and a password. The e-mail address and password are information arbitrarily set by the consumer identified by the member ID by operating the information terminal 50.

The store 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 unique to the company that operates the store identified by the store code. The OTC drug identification mark is a mark defined as information for identifying an OTC drug by a business entity that operates a store identified by a store code. The printer address is a communication address for identifying the printer 23 incorporated in 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 a tax return form corresponding to the self-medication tax system.

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

The monthly total file 144 is an area for storing monthly total data created for each consumer who has registered as a member in order to receive the electronic receipt service. Monthly aggregated data is data obtained by totaling the purchase amount of products belonging to each product category in units of one month. In addition, the monthly aggregated data includes data obtained by totaling the purchase amount of OTC drugs in units of one month.

The OTC drug setting file 145 is an area for storing the product data 145R (see FIG. 7) of the OTC drug published by the Ministry of Health, Labor and Welfare as an item 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 valid flag. The valid flag is 2-bit information that identifies whether or not the product identified by the product code is valid as an OTC drug. For example, when the effective flag is "1", the product is effective as an OTC drug. For example, when the valid flag is "0", the product is invalid as an OTC drug. The OTC drug setting file 145 is based on information provided by manufacturers and distributors to the Ministry of Health, Labor and Welfare regarding the start and discontinuation of sales of OTC drugs, for example, the product data 145R is periodically once every two months. Is updated. In the present embodiment, the OTC drug setting file 145 is a data file to be maintained.

The maintenance file 146 is an area for storing maintenance data 146R (see FIG. 8) for the OTC drug setting file 145 to be maintained. 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 indicating the reflection status of the maintenance data 146R, and the reflection status includes "unprocessed", "registered", and "not registered". For example, status = 0 represents the reflection status "unprocessed", status = 1 represents the reflection status "registered", and status = 9 represents 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 state of the maintenance data 146R is updated.

Here, the OTC drug setting file 145 constitutes the first storage unit, and the maintenance file 146 constitutes the second storage unit.
The data items stored in the files 141 to 146 are not limited to the above-mentioned items. The data may be composed by further including other items.

Next, the main information processing executed by the CPU 11 of the electronic receipt management server 10 will be described. First, the member-by-member aggregation process of the purchase amount of OTC drugs will be described with reference to FIGS. 9 and 10. The contents of the processes shown in FIGS. 9 and 10 and described below are examples. The procedure and contents are not particularly limited as long as similar results can be obtained.

When the time measured by the clock unit 15 reaches a predetermined time, the CPU 11 starts information processing of the procedure shown in the flow charts of FIGS. 9 and 10. The time is arbitrary. Also, the time set for one 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 Act1 in FIG. The counter n is formed in, for example, the RAM 13. After resetting the counter n, the CPU 11 sets the counter n as Act2 and counts up the counter n by “1”. Then, the CPU 11 detects the nth member data (n is the count value of the counter n) from the member file 141 as Act3.

The CPU 11 confirms whether or not the nth member data from the member file 141 could be detected as Act4. If it can be detected (Act4, YES), the CPU 11 detects the member ID from the nth member data as Act5.

Next, the CPU 11 searches the electronic receipt file 143 as Act6, and sequentially reads the receipt data 25 newly added to the electronic receipt file 143 after the previous processing. Then, the CPU 11 determines whether or not the member ID of the receipt data 25 matches the member ID detected in the process of Act5 as Act7. If they do not match, the CPU 11 determines whether or not the search for the electronic receipt file 143 has been completed as Act8. If it is not finished (Act8, NO), the CPU 11 returns to Act6 and continues the search for the electronic receipt file 143.

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

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

When the CPU 11 detects the product sales data in which the OTC drug identification mark is added to the product name (Act14, YES), as Act15, the valid product data 145R including the product code included in the product sales data is the OTC drug setting file. Check if it exists at 145. Here, the valid product data 145R indicates the product data 145R in which the valid flag is set to "1".

When the corresponding product data 145R exists in the OTC drug setting file 145 (Act16, YES), the product sales data detected in the processing of Act13 is the OTC drug purchased by the member specified by the member ID after the previous processing. It is data. The CPU 11 stores the product sales data in the work area of the RAM 13 as Act17. After that, the CPU 11 proceeds to Act18.

On the other hand, when the OTC drug identification mark is not added to the trade name (Act14, NO), the CPU 11 skips the processing of Act15 to Act17 and proceeds to Act18. Further, even when 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 (Act16, NO), the CPU 11 skips the process of Act17 and skips the process of Act17. Proceed to Act18.

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

In this way, when all the product sales data has been detected from the receipt data 25 (Act18, YES), the CPU 11 proceeds to Act8 in FIG. That is, the CPU 11 determines whether or not the search for the electronic receipt file 143 has been completed. If it is not finished (Act8, NO), the CPU 11 returns to Act6 and continues the search for the electronic receipt file 143.

When the search for the electronic receipt file 143 is completed in this way (Act8, YES), the CPU 11 performs the aggregation processing for each member based on the product sales data of the OTC drug stored in the work area. That is, the CPU 11 searches the monthly total file 144 with the member ID acquired in the process of Act 5, and stores it in the work area in the total purchase amount of the OTC drug included in the monthly total data in which the member ID is set. Add the amount of product sales data.

When the aggregation process is completed, the CPU 11 returns to Act2. 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.

This information processing is performed when the CPU 11 cannot detect the nth member data from the member file 141 (Act4, NO), that is, when all the member data stored in the member file 141 finishes the processing after Act5. To finish.

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

The CPU 11 is waiting for receipt data as Act21. When the receipt data 25 is received via the communication unit 16 (Act21, YES), the CPU 11 resets the determination flag F to “0” as Act22. The determination flag F is stored in the RAM 13.

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

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

When the product sales data with the OTC drug identification mark added to the product name is detected (Act26, YES), the CPU 11 sets the valid product data 145R including the product code included in the product sales data as the Act27 as the OTC drug. Check if it exists in file 145. Then, if it exists (Act 28, YES), the CPU 11 proceeds to the process of Act 33.

On the other hand, when the corresponding product data 145R does not exist in the OTC drug setting file 145 (Act28, NO), the CPU 11 sets the product code and product name of the product sales data to which the OTC drug identification mark is added as Act29. It is confirmed whether or not the maintenance data 146R including the above is already saved in the maintenance file 146. If the duplicate maintenance data 146R is already stored in the maintenance file 146 (Act29, YES), the CPU 11 proceeds to the process of Act33.

On the other hand, when the duplicated maintenance data 146R is not saved in the maintenance file 146 (Act 29, NO), the CPU 11 sets the product code and product name of the product sales data to which the OTC drug identification mark is added as Act 30. The maintenance data 146R including the above is written in the maintenance file 146 and saved. At this time, the registration date and time and the update date and time of the maintenance data 146R are the current date and time measured by the clock unit 15.

When the writing to the maintenance file 146 is completed, the CPU 11 confirms whether or not the determination flag F is set to "1" as Act31. If it is not set (Act31, NO), the CPU 11 sets the determination flag F to “1” as Act32. If the determination flag F is already set to "1" (Act31, NO) or is set to "1" in Act32, the CPU 11 proceeds to Act33.

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

In this way, when all the product sales data has been detected from the receipt data 25 (Act 33, YES), the CPU 11 confirms whether or not the determination flag F is set to “1” as Act 34. Then, when it is set (Act33, YES), the CPU 11 notifies the operator in charge of maintenance that the maintenance data 146R has been written to the maintenance file 146 as Act35. Specifically, the CPU 11 automatically sends an e-mail addressed to the administrator terminal 60, and notifies that the maintenance file 146 has been written by the body of the e-mail. In Act34, when the determination flag F is reset to “0” (Act34, NO), the maintenance data 146R is not written in the maintenance file 146. In this case, the CPU 11 skips the process of Act35. With the above, the CPU 11 ends the process after receiving the receipt data.

Here, the computer of the electronic receipt management server 10 mainly composed of the CPU 11 constitutes the detection means by executing the processes of Act 21 to Act 26 of FIG. Further, the computer constitutes a storage means by executing the processes of Acts 27 to 30 of FIG. In addition, the computer configures the notification means by executing the processes of Act31 to Act32 of FIG.

Thus, when the product data 145R including the product code and the product name of the product sales data with the mark added to the product name does not exist in the OTC drug setting file 145, the maintenance data 146R related to the product sales data is the maintenance file 146. Is remembered in.

Generally, when the manufacturer / distributor or the like provides information on the start of sales of an OTC drug, the product master file 26 is updated at each store. In addition, the OTC drug setting file 145 is also updated at the electronic receipt management center. However, the timing when the product master file 26 is updated and the timing when the OTC drug setting file 145 is updated are not synchronized. Therefore, as described above, there may be a case where the product data 145R including the product code and the product name of the product sales data in which the mark is added to the product name does not exist in the OTC drug setting file 145. In such a case, in the present embodiment, the maintenance data 146R including the product code and the 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. The contents of the processes shown in FIG. 12 and described below are examples. The procedure and contents are not particularly limited as long as similar results can be obtained.

The operator of the administrator terminal 60 who has confirmed the e-mail notifying that the maintenance data 146R has been written to the maintenance file 146 operates the administrator terminal 60 to start the application program for maintenance. By this activation, the maintenance command is transmitted from the administrator terminal 60 to the electronic receipt management server 10.

The CPU 11 of the electronic receipt management server 10 is waiting for a maintenance command as Act 41 in FIG. The CPU11, when detecting the reception of the maintenance command through the communication unit 16 (ACT 41, YES), the ACT 42, based on the maintenance data 146R stored in the maintenance file 146, creates display data of the maintenance list. The maintenance list is a list of maintenance data 146R whose reflection state is "unprocessed". As Act 43, the CPU 11 controls the communication unit 16 so as to transmit this display data to the administrator terminal 60. By this control, the display data of the maintenance list is transmitted to the administrator terminal 60 via the network 30. On the administrator terminal 60 that has received this display data, the maintenance screen SC (see FIG. 13 ) is displayed on the display device.

FIG. 13 is an example of the maintenance screen SC. As shown in FIG. 13, the maintenance list L, the registration button B1, and the stop button B2 are displayed on the maintenance screen SC. The maintenance list L is a list of product codes and product names constituting the maintenance data 146R, registration date and time, update date and time, and reflection status. The registration date and time is the date and time when the maintenance file 146 is written in Act 30 of FIG. The update date and time is the date and time when the reflection status is updated. In the maintenance list L, a check box CB is displayed in association with each product code.

The operator who confirms the maintenance screen SC selects a product published as an OTC drug from the maintenance list L and checks the corresponding check box CB. Then, the operator inputs the registration button B1. When the registration button B1 is input, a registration command is transmitted from the administrator terminal 60 to the electronic receipt management server 10. The registration command includes paired data of the product code and the product name in which the corresponding check box CB is checked in the maintenance list L. When the maintenance work is completed without inputting the registration button B1, the operator inputs the stop button B2. When the cancel button B2 is input, the cancel command is transmitted 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 maintenance list display data confirms whether or not the stop command has been received as Act44. When the stop command has not been received (Act44, NO), the CPU 11 confirms whether or not the registration command has been received as Act45. If the registration command has not been received (Act45, NO), the CPU 11 returns to Act44. Thus, the CPU 11 waits for the stop command or the registration command to be received by the processing of Act44 and Act45.

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

On the other hand, when it is detected that the registration command has been received (Act45, YES), the CPU 11 detects the paired data of the product code and the product name from the registration command as Act46. Then, the CPU 11 creates the product data 145R of the OTC drug including this pair 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 the valid state.

In this way, when the product data 145R including the product code and the product name of the pair data included in the registration command has been added to the OTC drug setting file 145, the CPU 11 updates the status of the maintenance data 146R as Act47. To do. Specifically, for the maintenance data 146R added to the OTC drug setting file 145, the reflection status is 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". Further, the CPU 11 ends this process.

Here, the computer of the electronic receipt management server 10 mainly composed of the CPU 11 constitutes additional means by executing the processes of Act 45 and Act 46 of FIG. The same computer, by executing the processing of Act42 and Act43 of 12, constituting the receiving means.

As described above, according to the electronic receipt management server 10 of the present embodiment, the OTC drug whose information is not reflected in the OTC drug setting file 145 is accurately extracted based on the receipt data received from the POS system 20 of each store. Can be done.

Further, according to the electronic receipt management server 10, it is possible to notify the operator in charge of maintenance that the OTC drug whose information is not reflected in the OTC drug setting file 145 has been extracted.

Further, according to the electronic receipt management server 10, information on the OTC drug whose information is not reflected in the OTC drug setting file 145 can be added to the OTC drug setting file 145 in response to an instruction from the operator in charge of maintenance. .. Therefore, by adding the missing information to the OTC drug setting file 145 before the member-specific aggregation processing of the purchase amount related to the OTC drug is started, the electronic receipt management server 10 can use the OTC drug for each consumer. It is possible to manage the purchase information of.

By the way, when updating the product master file 26 at each store, it is possible that a mark is mistakenly added to a product other than an OTC drug. In that case, in the present embodiment, the data of the product that is not an OTC drug is stored in the maintenance file 146. However, in the present embodiment, the electronic receipt management server 10 creates a maintenance list L based on the data stored in the maintenance file 146, displays the maintenance list L on the display device of the administrator terminal 60, and displays the OTC drug. The selection of whether to add to the setting file 145 is accepted. Therefore, it is possible to prevent data related to products other than OTC drugs from being accidentally added to the OTC drug setting file 145.

Next, the modified sequence of the present embodiment will be described.

In the above embodiment, the case where the electronic receipt management server 10 is provided with the function as the information processing device is shown. Regarding this point, a computer device other than the electronic receipt management server 10 may be provided with a function as the information processing device. In this case, the computer device having a function as an information processing device is connected to the electronic receipt management server 10 via a communication means and includes a maintenance file 146. Then, the computer device takes in the receipt data 25 received by the electronic receipt management server 10 and executes the information processing shown in the flow charts of FIGS. 11 and 12. By doing so, it is possible to realize a computer device capable of accurately extracting OTC drugs whose information is not reflected in the OTC drug setting file 145. Such a computer device may be, for example, an administrator terminal 60.

In the above embodiment, the store data stored in the store file 142 includes the OTC drug identification mark. Then, the electronic receipt management server 10 searches the store file 142 with the store code included in the receipt data, and acquires the mark used in the store. In this regard, the following may be done. That is, the receipt data includes a mark added to the product name of the OTC drug and a text indicating that the product with the mark is an OTC drug. Therefore, the electronic receipt management server 10 analyzes this text and acquires the mark. By doing so, it is not necessary to store the OTC drug identification mark for each store in the store file 142.

In the above-described embodiment, the case where the OTC drug identification mark is set for each store in the store file 142 is shown, but the OTC drug identification mark may be set for each company that operates the store. In this case, the receipt data 25 includes a business entity code that identifies the business entity. Then, a data file for centrally managing the OTC drug identification mark for each company code of each company is provided in the electronic receipt management server 10. By doing so, the OTC drug identification mark can be set for each business entity. In addition, by incorporating the store code into the data file, it is possible to set the OTC drug identification mark by combining the company code and the 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 include information other than the mark indicating that the drug is an OTC drug.

In the above embodiment, the operator who confirms the maintenance screen SC checks the check box CB corresponding to the product published as an OTC drug from the maintenance list L. Regarding this point, the check box CB is checked by default, and the check box CB corresponding to products other than OTC drugs may be unchecked.

In the above-described embodiment, an OTC drug is a product subject to a tax system that can receive a tax deduction when the annual purchase amount is within a predetermined amount range. The target products are not necessarily limited to OTC drugs. The present embodiment can be similarly applied to similar taxable products.

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

In addition, although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other embodiments, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are also included in the scope of the invention described in the claims and the equivalent scope thereof.
Hereinafter, the inventions described in the claims of the original application of the present application will be added.
[1] From the information on the purchased product included in the receipt data, the information indicating that the purchased product is a product subject to the tax system that can receive a tax deduction when the annual purchase amount is within the predetermined amount range is detected. When the detection means and the data for identifying the purchased product in which the information indicating the target product is detected from the information about the purchased product does not exist in the first storage unit that stores the data for identifying the target product. An information processing device including a storage means for storing data identifying the purchased product in a second storage unit.
[2] The information processing device according to the appendix [1], further comprising a notification means for notifying the outside that data identifying the purchased product is stored in the second storage unit.
[3] The information processing apparatus according to the appendix [1] or [2], further comprising an additional means for adding data for identifying the purchased product stored in the second storage unit to the first storage unit.
[4] The receiving means for receiving whether or not to add the data for identifying the purchased product stored in the second storage unit to the first storage unit is further provided, and the additional means is added. The information processing device according to the appendix [3], which adds data for identifying the purchased product that has received the above to the first storage unit.
[5] The detection means confirms whether or not a predetermined mark is given to the product name included in the information about the purchased product, and if it is given, detects the mark as information indicating that the product is the target product. The information processing apparatus according to any one of the appendices [1] to [4].
[6] Information indicating from the information about the purchased product included in the receipt data that the purchased product is a product subject to the tax system that can receive a tax deduction when the annual purchase amount is within the predetermined amount range. In the first storage unit that stores the data for identifying the target product, the detection means for detecting the target product and the data for identifying the purchased product in which the information indicating that the product is the target product is detected from the information about the purchased product A program for functioning as a storage means for storing data for identifying the purchased product in the second storage unit when the product does not exist.

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 ... member file, 142 ... store file, 143 ... electronic receipt file, 144 ... monthly total file, 145 ... OTC drug setting file, 146 ... maintenance file.

Claims (5)

A detection means for detecting information indicating that the purchased product is a tax-deductible product when the annual purchase amount is within a predetermined amount range from the information on the purchased product included in the receipt data. ,
When the data for identifying the purchased product in which the information indicating the target product is detected from the information about the purchased product does not exist in the first storage unit that stores the data for identifying the target product, the purchased product is stored. A storage means for storing the identification data in the second storage unit for storing the maintenance data for the first storage unit, and
An additional means for adding data for identifying the purchased product stored in the second storage unit to the first storage unit, and
Information processing device equipped with. The information processing device according to claim 1, further comprising a notification means for notifying the outside that the data identifying the purchased product is stored in the second storage unit. Further provided with a receiving means for receiving whether or not to add the data for identifying the purchased product stored in the second storage unit to the first storage unit.
The information processing device according to claim 1 or 2 , wherein the additional means adds data identifying the purchased product that has been accepted to be added to the first storage unit. The detection means confirms whether or not a predetermined mark is given to the product name included in the information about the purchased product, and if it is given, detects the mark as information indicating that the product is the target product. The information processing apparatus according to any one of items 1 to 3 . Computer,
From the information on the purchase products included in the receipt data, the purchase products, detection means to detect the information indicating that the annual purchases are Shipping tax that can receive tax credits when within a predetermined amount range ,
If information indicating that the information for the previous SL purchased merchandise is the target item data identifying the purchased merchandise that is detected is not present in the first storage unit storing data identifying the Shipping, the purchased merchandise A storage means for storing the data for identifying the above in the second storage unit for storing the maintenance data for the first storage unit , and
An additional means for adding data for identifying the purchased product stored in the second storage unit to the first storage unit,
A program to function as.