Processing terminal and its program

Abstract

To easily manage data of receipts issued at a plurality of stores.SOLUTION: A data management device comprises a reception section and a control section. The reception section receives receipt data in which a receipt including information of a transaction settled as one transaction is digitalized. If subject person identification information for identifying a subject person of a transaction is attached to receipt data received at the reception section, the control section stores the receipt data to a first storage section and a second storage section. If the subject person identification information is unattached thereto, the control section stores the receipt data in the first storage section and does not store it in the second storage section.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] An embodiment of the present invention is a data management system. Processing terminal and its Regarding the program. [Background technology]

[0002] The business entities that operate shopping centers, known as developers, enter into lease agreements with each tenant store and generate revenue primarily through rent. Therefore, developers track the total sales of each store and reflect this in rent. However, due to intensifying competition and sluggish sales, developers have recently expressed a desire to analyze product sales at each store.

[0003] This need can be met, for example, by managing the data of receipts issued by each tenant. However, the POS (Point of Sales) systems built in each store are self-contained within that store. Furthermore, the manufacturers of the store servers and POS terminals that make up the POS systems are not standardized. For these reasons, existing technology makes it difficult to easily manage the data of receipts issued at multiple stores. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-230545 Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the embodiments of the present invention is to provide a data management system that can easily manage data on receipts issued at multiple stores. Processing terminal The aim is to provide the following. [Means for solving the problem]

[0006] In one embodiment, The processing terminal includes a creation means, an acquisition means, a communication means, and a transmission control means. The creation means creates receipt data by digitizing a receipt containing information about a transaction that has been settled as one transaction. The acquisition means acquires target person identification information that identifies the target person of the transaction. The communication means communicates with a data management device, storing the receipt data in a first memory unit and a second memory unit if target person identification information is added to the receipt data, and storing the receipt data in the first memory unit but not in the second memory unit if target person identification information is not added to the receipt data. The transmission control means, if the acquisition means acquires target person identification information, adds the target person identification information to the receipt data created by the creation means and transmits the receipt data to the data management device; if the acquisition means does not acquire target person identification information, transmits the receipt data created by the creation means to the data management device without adding the target person identification information. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a configuration diagram of an entire system including a data management system according to a first embodiment. [Figure 2] FIG. 2 is a block diagram showing the main circuit configuration of a processing terminal included in the data management system. [Figure 3] FIG. 2 is a block diagram showing the main circuit configuration of an electronic receipt server included in the data management system. [Figure 4] 3 is a flowchart showing the main steps of information processing executed by a processor of the processing terminal based on a control program. [Figure 5] FIG. 4 is a diagram showing an example of a screen displayed on a touch panel of the processing terminal. [Figure 6] 10 is a flowchart showing the main steps of an electronic receipt data receiving process executed by a processor of the electronic receipt server based on a data management program. [Figure 7] 10 is a flowchart showing the main steps of a request command receiving process executed by a processor of the electronic receipt server based on a data management program. [Figure 8] FIG. 10 is a configuration diagram of an entire system including a data management system according to a second embodiment. [Figure 9] FIG. 2 is a block diagram showing the main circuit configuration of an electronic receipt server included in the data management system. [Figure 10] FIG. 4 is a schematic diagram showing an example of the configuration of receipt data. [Figure 11] 10 is a flowchart showing the main steps of an electronic receipt data receiving process executed by a processor of the electronic receipt server based on a data management program. [Figure 12] 10 is a flowchart illustrating an extracted portion of a request command receiving process that is executed by a processor of the electronic receipt server based on a data management program, the portion being different from the first embodiment. [Figure 13] 10 is a flowchart showing the main steps of the information processing executed by the processor of the processing terminal based on the control program in the third embodiment. [Figure 14] 11 is a flowchart showing the main steps of an electronic receipt data receiving process executed by a processor of the electronic receipt server based on a data management program in the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, an embodiment of a data management system that can easily manage data on receipts issued at multiple stores and a data management device for this system will be described with reference to the drawings. In the embodiment described below, we will exemplify a data management system that allows the developer of a single shopping center to easily manage data on receipts issued by multiple stores that are tenants in the shopping center.

[0009] [First embodiment] FIG. 1 is a configuration diagram of an entire system including a data management system according to a first embodiment. The data management system includes a plurality of processing terminals 2 connected to a plurality of POS terminals 1, respectively, an electronic receipt server 3, and a communication network 4. The communication network 4 is, for example, an Internet Virtual Private Network (VPN). In addition to the processing terminals 2 and the electronic receipt server 3, a center server 5 is also connected to the communication network 4. The center server 5 is a computer managed by a developer of a shopping center. A client terminal 7 is connected to the center server 5 via a communication line 6. The electronic receipt server 3 and the center server 5 may be on a cloud.

[0010] The POS terminal 1 and the processing terminal 2 are installed in each store that is a tenant in the shopping center. The POS terminal 1 and the processing terminal 2 are connected by a communication line that conforms to the RS232C interface standard, for example. The communication line may be wired or wireless. The number of POS terminals 1 installed in each store is arbitrary. The number of processing terminals 2 is also arbitrary. There does not necessarily have to be a one-to-one correspondence between the POS terminal 1 and the processing terminal 2. Multiple POS terminals 1 may be connected to one processing terminal 2. It is sufficient that at least one processing terminal 2 is connected to one POS terminal 1.

[0011] Each POS terminal 1 has an acquisition program P1 installed. The acquisition program P1 is an agent program specialized for acquiring print data for receipts created by the POS terminal 1 and outputting it to the processing terminal 2. The POS terminal 1 has a printer for printing receipts. The POS terminal 1 issues paper receipts by printing the print data for receipts on the printer. The paper receipt prints the product name, price, total amount, etc. of the product registered as one transaction, as well as the transaction date and time, transaction number, register number, etc. Such POS terminals 1 are well known. Therefore, a detailed description will be omitted here.

[0012] A creation program P2 is installed on each processing terminal 2. The creation program P2 is a program specialized for the process of creating structured electronic receipt data from unstructured receipt print data received from the POS terminal 1. Well-known technology can be used to create electronic receipt data from receipt print data, so a detailed explanation will be omitted here.

[0013] 2 is a block diagram showing the main circuit configuration of the processing terminal 2. The processing terminal 2 includes a processor 21, a main memory 22, an auxiliary storage device 23, a first communication interface 24, a second communication interface 25, a touch panel 26, a reader 27, and a system transmission path 28. The system transmission path 28 includes an address bus, a data bus, a control signal line, etc. The processing terminal 2 connects the processor 21, the main memory 22, the auxiliary storage device 23, the first communication interface 24, the second communication interface 25, the touch panel 26, and the reader 27 to the system transmission path 28. In the processing terminal 2, the processor 21, the main memory 22, the auxiliary storage device 23, and the system transmission path 28 connecting these components form a computer.

[0014] The processor 21 corresponds to the central part of the computer. The processor 21 controls each part in accordance with an operating system or an application program to realize various functions of the processing terminal 2. The processor 21 is, for example, a CPU (Central Processing Unit).

[0015] The main memory 22 corresponds to the main storage portion of the computer. The main memory 22 includes a nonvolatile memory area and a volatile memory area. The main memory 22 stores an operating system or application programs in the nonvolatile memory area. The main memory 22 may store data required for the processor 21 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is rewritten by the processor 21 as appropriate. The nonvolatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

[0016] The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 23. The auxiliary storage device 23 stores data used by the processor 21 when performing various processes, or data created by the processes of the processor 21. The auxiliary storage device 23 may also store the application programs described above.

[0017] The application programs stored in the main memory 22 or the auxiliary storage device 23 include control programs that describe information processing to be executed by the processing terminal 2. The control programs also include the creation program P2 described above. There are no particular limitations on the method for installing the control programs, including the creation program P2, into the main memory 22 or the auxiliary storage device 23. The control program can be installed into the main memory 22 or the auxiliary storage device 23 by recording it on a removable recording medium or by distributing it via communication over a network. The recording medium can be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device.

[0018] The first communication interface 24 is for performing data communication with the POS terminal 1. The data communication may be performed, for example, via a wired LAN (Local Area Network) or a wireless LAN.

[0019] The second communication interface 25 is for communicating data with the electronic receipt server 3 via the communication network 4. The second communication interface 25 may also communicate data with the center server 5 via the communication network 4.

[0020] The touch panel 26 is a device that functions as an input device and a display device for the processing terminal 2. The reader 27 is a device for reading data recorded on a medium. If the medium is an IC card, the reader 27 is an IC card reader. If the medium is a magnetic card, the reader 27 is a magnetic card reader. If the medium is a non-contact type RFID (Radio Frequency Identification), the reader 27 is an RFID reader.

[0021] Returning to the explanation of Figure 1. The electronic receipt server 3 is a computer managed by a business entity that provides the electronic receipt service. The business entity is a separate entity from the developer of the shopping center. The business entity may be operated by the developer of the shopping center.

[0022] The electronic receipt server 3 collects electronic receipt data created by each processing terminal 2 via the communication network 4 and stores it in a database. The electronic receipt server 3 also accepts access from an information terminal 9 connected via the Internet 8, obtains the requested electronic receipt data from the database, and downloads it to the information terminal 9. The electronic receipt server 3 functions as a data management device of the data management system.

[0023] The information terminal 9 is an electronic device owned by a consumer who has registered as a member to receive the electronic receipt service. An application program required to receive the electronic receipt service, a so-called electronic receipt app, is installed in the information terminal 9. By installing the electronic receipt app in the information terminal 9, a unique electronic receipt ID is set for the information terminal 9. When the electronic receipt app is started on the information terminal 9 in which the electronic receipt ID is set, a barcode indicating the electronic receipt ID is displayed on the display of the information terminal. The information terminal 9 is typically a smartphone. The information terminal 9 may also be a tablet terminal, a laptop computer, etc.

[0024] 3 is a block diagram showing the main circuit configuration of the electronic receipt server 3. The electronic receipt server 3 includes a processor 31, a main memory 32, an auxiliary storage device 33, a first communication interface 34, a second communication interface 35, and a system transmission path 36. The system transmission path 36 includes an address bus, a data bus, a control signal line, etc. The electronic receipt server 3 connects the processor 31, the main memory 32, the auxiliary storage device 33, the first communication interface 34, and the second communication interface 35 to the system transmission path 36. In the electronic receipt server 3, the processor 31, the main memory 32, the auxiliary storage device 33, and the system transmission path 36 that connects them together constitute a computer.

[0025] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part in accordance with an operating system or an application program to realize various functions of the electronic receipt server 3. The processor 31 is, for example, a CPU.

[0026] The main memory 32 corresponds to the main storage portion of the computer. The main memory 32 includes a nonvolatile memory area and a volatile memory area. The main memory 32 stores an operating system or application programs in the nonvolatile memory area. The main memory 32 may store data required for the processor 31 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 32 uses the volatile memory area as a work area where data is rewritten by the processor 31 as appropriate. The nonvolatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0027] The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, HDD, or SSD can be the auxiliary storage device 33. The auxiliary storage device 33 stores data used by the processor 31 when performing various processes, or data created by the processes in the processor 31. The auxiliary storage device 33 may also store the application programs described above.

[0028] The application programs stored in the main memory 32 or the auxiliary storage device 33 include control programs that describe information processing executed by the electronic receipt server 3. The control programs also include a data management program, which will be described later. There are no particular limitations on the method for installing the control programs, including the data management program, into the main memory 32 or the auxiliary storage device 33. The control program can be recorded on a removable recording medium, or can be distributed via communication over a network and installed in the main memory 32 or the auxiliary storage device 33. The recording medium can be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device.

[0029] The first communication interface 34 is for performing data communication with an information terminal 9 connected via the Internet 8.

[0030] The second communication interface 35 is for communicating data with each processing terminal 2 via the communication network 4. Here, the second communication interface 35 functions as a receiving unit that receives electronic receipt data created by each processing terminal 2.

[0031] The electronic receipt server 3 configured as described above uses a portion of the storage area of ​​the auxiliary storage device 33 as an electronic receipt database 331, and another portion of the storage area as a total receipt database 332. The electronic receipt database 331 is an area for storing receipt data obtained by digitizing receipts that include information on transactions settled as one transaction with an electronic receipt member, i.e., so-called electronic receipt data. The total receipt database 332 is an area for storing electronic receipt data obtained by digitizing receipts that include information on transactions settled as one transaction with all consumers, including electronic receipt members. Here, the total receipt database 332 functions as a first storage unit. The electronic receipt database 331 functions as a second storage unit.

[0032] FIG. 4 is a flowchart showing the main steps of the main information processing executed by the processor 21 of the processing terminal 2 based on the control program. FIG. 5 is an example of a screen SC1 displayed on the touch panel 26 of the processing terminal 2. FIG. 6 is a flowchart showing the main steps of the receipt data reception processing executed by the processor 31 of the electronic receipt server 3 based on the data management program. FIG. 7 is a flowchart showing the main steps of the request command reception processing executed by the processor 31 of the electronic receipt server 3 based on the data management program. The operation of the data processing system will be explained below using each diagram. The data management method will become clear from the following explanation. Note that the content of the operation explained below is an example. Data processing according to the data management program may be executed with other operation content as long as similar effects can be obtained.

[0033] As shown in Figure 4, the processor 21 of the processing terminal 2 waits as ACT1 to receive receipt print data from the POS terminal 1. When a transaction with a consumer is settled at the POS terminal 1, receipt print data including information about the products purchased in that transaction is created. This receipt print data is then sent to the processing terminal 2 via a communication line by the operation of the acquisition program P1.

[0034] When the processor 21 of the processing terminal 2 receives the receipt print data created by the POS terminal 1 via the first communication interface 24, it determines YES in ACT1 and proceeds to ACT2. In ACT2, the processor 21 converts the unstructured receipt print data into structured electronic receipt data in accordance with the creation program P2. In ACT3, the processor 21 also displays screen SC1 shown in FIG. 5 on the touch panel 26. Screen SC1 displays a message MS1 inquiring whether the user is an electronic receipt member, along with a "Yes" button BT1 indicating yes and a "No" button BT2 indicating no.

[0035] After checking screen SC1, the operator touches the "No" button BT2 if the consumer who is the subject of the transaction is not an electronic receipt member. On the other hand, if the consumer is an electronic receipt member, the operator touches the "Yes" button BT1. Then, the operator has the reader 27 read the barcode of the electronic receipt ID displayed on the display of the information terminal 9 owned by the consumer.

[0036] Incidentally, the operator is typically a store clerk, a so-called cashier, who settles the transaction with the consumer by operating the POS terminal 1. The operator may also be a store clerk other than a cashier or the consumer himself.

[0037] When the processor 21 of the processing terminal 2 displays screen SC1 on the touch panel 26, it checks in ACT4 whether the member ID of the electronic receipt member has been entered. When the member ID is read via the reader 27, the processor 21 determines YES in ACT4 and proceeds to ACT5. In ACT5, the processor 21 adds the member ID to the electronic receipt data created in the processing of ACT2. The processor 21 then proceeds to the processing of ACT6. On the other hand, if it is confirmed by a signal from the touch panel 26 that the "No" button BT2 has been touched, the processor 21 determines NO in ACT4, skips the processing of ACT5, and proceeds to ACT6.

[0038] The processor 21 controls the second communication interface 25 as ACT6 to send the electronic receipt data to the electronic receipt server 3. By this control, the electronic receipt data is sent to the electronic receipt server 3 via the communication network 4. Therefore, when the "Yes" button BT1 on the screen SC1 is touched and the member ID is read by the reader 27, the electronic receipt data with the member ID added is sent to the electronic receipt server 3. When the "No" button BT2 on the screen SC1 is touched, the electronic receipt data without the member ID added is sent to the electronic receipt server 3.

[0039] Here, the processor 21, which is the main component of the computer provided in the processing terminal 2, configures creation means that creates electronic receipt data by executing the process in ACT2. The processor 21 also configures acquisition means that acquires a member ID, which is target person identification information, by executing the processes in ACT3 and ACT4 in cooperation with the touch panel 26. The processor 21 also configures transmission control means by executing the processes in ACT5 and ACT6 in cooperation with the second communication interface 25. That is, when the processor 21 acquires a member ID, it adds the member ID to the electronic receipt data and transmits it to the electronic receipt server 3, which is a data management device. When the processor 21 does not acquire a member ID, it transmits the electronic receipt data to the electronic receipt server 3 without adding the member ID.

[0040] As shown in FIG. 6, the processor 31 of the electronic receipt server 3 waits to receive electronic receipt data in ACT11. When electronic receipt data transmitted from any of the processing terminals 2 via the second communication interface 35 is received, the processor 31 determines YES in ACT11 and proceeds to ACT12. The processor 31 checks whether a member ID is added to the electronic receipt data in ACT12. If a member ID is added, the processor 31 determines YES in ACT12 and proceeds to ACT13. The processor 31 saves the electronic receipt data with the member ID added in the electronic receipt database 331 in ACT13. After that, the processor 31 proceeds to ACT14.

[0041] On the other hand, if a member ID is not added to the electronic receipt data, the processor 31 determines NO in ACT12 and skips the processing in ACT13. In other words, the processor 31 does not store the electronic receipt data to which a member ID is not added in the electronic receipt database 331. The processor 31 proceeds to ACT14.

[0042] The processor 31 stores the electronic receipt data with or without the member ID added in ACT14 in the all receipt database 332. This completes the information processing performed by the processor 31 when receiving electronic receipt data.

[0043] Here, the processor 31, which is the main component of the computer provided in the electronic receipt server 3, configures a control unit by executing the processing of the procedure shown in the flowchart of Fig. 6 in accordance with a data management program. That is, if a member ID, which is target person identification information, is added to electronic receipt data received by the second communication interface 35, which is a receiving unit, the processor 31 stores the electronic receipt data in the all receipt database 332, which is a first storage unit, and the electronic receipt database 331, which is a second storage unit. Furthermore, if a member ID is not added, the processor 31 stores the electronic receipt data in the all receipt database 332, but does not store it in the electronic receipt database 331.

[0044] As shown in FIG. 7, the processor 31 of the electronic receipt server 3 waits for a data request command as ACT21. The data request command is classified into an electronic receipt request command output from the information terminal 9 and an all-receipt request command output from the center server 5. The electronic receipt request command includes the member ID set in the information terminal 9 that sent the command. The all-receipt request command includes condition data input by operating the client terminal 7, for example. The condition data is data that specifies, for example, each tenant store. The condition data is data that specifies, for example, all stores collectively.

[0045] When the processor 31 receives a data request command, it determines YES in ACT21 and proceeds to ACT22. In ACT22, the processor 31 checks whether the received command is an electronic receipt request command. If it is not an electronic receipt request command, the processor 31 determines NO in ACT22 and proceeds to ACT23. In ACT23, the processor 31 checks whether the received command is a full receipt request command. Incidentally, if the received command is not a full receipt request command, the processor 31 determines NO in ACT23 and executes processing based on another request command.

[0046] When an electronic receipt request command is received from the information terminal 9 via the first communication interface 34, the processor 31 determines YES in ACT 22 and proceeds to ACT 24. In ACT 24, the processor 31 searches the electronic receipt database 331. Then, in ACT 25, the processor 31 checks whether the member ID added to the electronic receipt data stored in the electronic receipt database 331 matches the member ID included in the electronic receipt request command.

[0047] If the two member IDs do not match, the processor 31 determines NO in ACT25, skips the processing of ACT26, and proceeds to ACT27. In ACT27, the processor 31 checks whether the search of the electronic receipt database 331 has ended. If the search has not ended, the processor 31 determines NO in ACT27 and returns to ACT24. That is, the processor 31 continues searching the electronic receipt database 331.

[0048] If, as a result of searching the electronic receipt database 331, electronic receipt data to which a member ID that matches the member ID included in the electronic receipt request command is added is detected, the processor 31 determines YES in ACT 25 and proceeds to ACT 26. In ACT 26, the processor 31 obtains the electronic receipt data with the matching member ID from the electronic receipt database 331 and stores it in the receipt memory. The receipt memory is formed, for example, in a volatile area of ​​the main memory 32.

[0049] After storing the electronic receipt data with a matching member ID in the receipt memory, the processor 31 checks whether or not the search of the electronic receipt database 331 is complete in ACT 27. If the search is not complete, the processor 31 returns to ACT 24 and continues searching the electronic receipt database 331.

[0050] In this way, upon receiving the electronic receipt request command, the processor 31 searches the electronic receipt database 331. Then, every time the processor 31 detects electronic receipt data to which the member ID included in the electronic receipt request command is added, the processor 31 stores the electronic receipt data in the receipt memory. Then, upon finishing the search of the electronic receipt database 331, the processor 31 determines YES in ACT27 and proceeds to ACT28. The processor 31 controls the first communication interface 34 to transmit all electronic receipt data stored in the receipt memory in ACT28 to the information terminal 9 that transmitted the electronic receipt request command. By this control, the electronic receipt data is transmitted from the first communication interface 34 to the information terminal 9 via the Internet 8. That is, the electronic receipt data to which the member ID set in the information terminal 9 is added is transmitted to the information terminal 9 that transmitted the electronic receipt request command. In this way, the information terminal 9 can display the digitized receipt on its display, and the electronic receipt member, who is a consumer, can receive a receipt showing information about the transaction made at the store as an electronic receipt.

[0051] On the other hand, if a full receipt request command is received from the center server 5 via the second communication interface 35, the processor 31 determines YES in ACT 23 and proceeds to ACT 29. In ACT 29, the processor 31 searches the full receipt database 332. Then, in ACT 30, the processor 31 checks whether the electronic receipt data stored in the full receipt database 332 satisfies the condition data included in the full receipt request command.

[0052] For example, if the condition data specifies an individual store, the processor 31 determines that the electronic receipt data of a receipt issued by that store satisfies the condition. Since the electronic receipt data includes store identification information that identifies the store, the processor 31 determines whether the condition is satisfied based on this store identification information.

[0053] For example, if the condition data specifies all stores, the processor 31 determines that all electronic receipt data stored in the all receipt database 332 satisfies the condition.

[0054] If the condition is not satisfied, the processor 31 determines NO in ACT 30, skips the processing of ACT 31 through ACT 34, and proceeds to ACT 35. In ACT 35, the processor 31 checks whether the search of the entire receipt database 332 is complete. If the search is not complete, the processor 31 determines NO in ACT 35 and returns to ACT 29. That is, the processor 31 continues searching the entire receipt database 332.

[0055] If, as a result of searching the all receipt database 332, electronic receipt data that satisfies the condition data included in the all receipt request command is found, the processor 31 determines YES in ACT30 and proceeds to ACT31.

[0056] In ACT 31, the processor 31 obtains the electronic receipt data from the electronic receipt database 331. Then, in ACT 32, the processor 31 checks whether a member ID has been added to the electronic receipt data. If a member ID has been added to the electronic receipt data, the processor 31 determines YES in ACT 32 and proceeds to ACT 33. In ACT 33, the processor 31 deletes the member ID from the electronic receipt data. Then, in ACT 34, the processor 31 saves the electronic receipt data from which the member ID has been deleted in the receipt memory described above.

[0057] On the other hand, if a member ID is not added to the electronic receipt data, the processor 31 determines NO in ACT 32, skips the processing of ACT 33, and proceeds to ACT 34. That is, the processor 31 stores the electronic receipt data acquired from the total receipt database 332 in the receipt memory.

[0058] Thereafter, the processor 31 checks whether or not the search of the electronic receipt database 331 has ended in ACT 35. If the search has not ended, the processor 31 continues searching the entire receipt database 332.

[0059] In this way, upon receiving the all receipt request command, the processor 31 searches the all receipt database 332. Then, every time the processor 31 detects electronic receipt data that satisfies the condition data included in the all receipt request command, the processor 31 saves the electronic receipt data in the receipt memory. At this time, if a member ID is added to the electronic receipt data, the member ID is deleted and the electronic receipt data is saved in the receipt memory. After completing the search of the all receipt database 332, the processor 31 determines YES in ACT 35 and proceeds to ACT 36. The processor 31 controls the second communication interface 35 to send all electronic receipt data saved in the receipt memory in ACT 36 to the center server 5 that sent the all receipt request command. This control causes the second communication interface 35 to send the electronic receipt data addressed to the center server 5 via the communication network 4. At this time, the electronic receipt data is converted into, for example, a CSV format and sent to the center server 5. Therefore, the client terminal 7 connected to the center server 5 can acquire, view, or process receipt data that satisfies the specified conditions.

[0060] As described above, according to the first embodiment, it is possible to provide an electronic receipt server 3 that can easily manage data of receipts issued not only to consumers who are electronic receipt members but also to non-member consumers as electronic receipt data in a plurality of stores that are tenants of a shopping center.

[0061] Furthermore, according to the first embodiment, the acquisition program P1 is installed in the POS terminal 1 installed in each store, and the processing terminal 2 on which the creation program P2 is installed is connected to the POS terminal 1. The processing terminal 2 is then connected to the electronic receipt server 3 via the communication network 4, thereby configuring a data management system that provides the above-mentioned effects. Therefore, even in a shopping center where each store has an existing POP system, a data management system that provides the above-mentioned effects at a relatively low cost can be realized by simply adding a component. Moreover, it does not matter if the manufacturers of the POS systems installed in each store are different.

[0062] [Second embodiment] Next, a second embodiment will be described. In the first embodiment, an example is shown in which data of receipts issued at multiple stores included as tenants in one shopping center is managed by the electronic receipt server 3. In the second embodiment, an example is shown in which data of receipts issued at a large number of stores included as tenants in multiple shopping centers owned by different developers is managed by the electronic receipt server 30. For ease of explanation, in the second embodiment, the number of shopping centers is assumed to be two.

[0063] Fig. 8 is a configuration diagram of an entire system including the data management system of the second embodiment. In Fig. 8, parts common to Fig. 1 showing the data management system of the first embodiment are given the same reference numerals, and detailed explanations thereof will be omitted.

[0064] In the second embodiment, the data management system includes a plurality of processing terminals 2 connected to a plurality of POS terminals 1, respectively, an electronic receipt server 30, and a communication network 4. Two center servers 5A and 5B are connected to the communication network 4. One of the center servers 5A is a computer managed by a developer of a first shopping center A. A client terminal 7A is connected to the center server 5A via a communication line 6A. The other center server 5B is a computer managed by a developer of a second shopping center B. A client terminal 7B is connected to the center server 5B via the communication line 6B.

[0065] The POS terminal 1 and the processing terminal 2 are installed in each store that is a tenant in shopping center A or shopping center B. The POS terminal 1 and the processing terminal 2 are connected by a communication line that conforms to the RS232C interface standard, for example. The communication line may be wired or wireless. The POS terminal 1 and the processing terminal 2 are as described in the first embodiment. Therefore, further description will be omitted.

[0066] FIG. 9 is a block diagram showing the main circuit configuration of the electronic receipt server 30. As is clear from comparing FIG. 9 with FIG. 3, the electronic receipt server 30 differs from the electronic receipt server 3 of the first embodiment in the number of total receipt databases 332. That is, in the second embodiment, the total receipt database 332 that uses a portion of the storage area of ​​the auxiliary storage device 33 is divided into a first total receipt database 332A and a second total receipt database 332B. The first total receipt database 332A is the total receipt database 332 corresponding to shopping center A. The second total receipt database 332B is the total receipt database 332 corresponding to shopping center B.

[0067] Figure 10 is a schematic diagram showing the main data structure of receipts issued by each store that is a tenant in both shopping centers A and B. As shown in Figure 10, a receipt has a data structure that includes transaction data such as the product name, price, and total amount of the product registered as one transaction, as well as a company code, store code, terminal number, and transaction number. The company code is a unique code used to identify the developer. The store code is a unique code used to identify the store. The terminal number is a unique code used to identify the POS terminal 1. The transaction number is a consecutive number that is issued each time a transaction is processed at the POS terminal 1 identified by the terminal number. Therefore, transaction data can be identified as unique data by the combination of the company code, store code, terminal number, and transaction number.

[0068] FIG. 11 is a flowchart showing the main steps of the receipt data reception process executed by the processor 31 of the electronic receipt server 30 based on the data management program. As shown in FIG. 11, the processor 31 of the electronic receipt server 30 waits to receive electronic receipt data in ACT41. When electronic receipt data transmitted from any of the processing terminals 2 via the second communication interface 35 is received, the processor 31 determines YES in ACT41 and proceeds to ACT42. The processor 31 checks whether a member ID is added to the electronic receipt data in ACT42. If a member ID is added, the processor 31 determines YES in ACT42 and proceeds to ACT43. The processor 31 saves the electronic receipt data with the member ID added in the electronic receipt database 331 in ACT43. After that, the processor 31 proceeds to ACT44.

[0069] On the other hand, if a member ID is not added to the electronic receipt data, the processor 31 determines NO in ACT42 and skips the processing of ACT43. In other words, the processor 31 does not store the electronic receipt data without a member ID added in the electronic receipt database 331. The processor 31 proceeds to ACT44.

[0070] The processor 31 acquires a company code from electronic receipt data with a member ID added as ACT44 or from electronic receipt data without a member ID added. The processor 31 then selects the all-receipt database 332 corresponding to the shopping center operated by the developer identified by the company code. That is, if the company code is the code of the developer that operates shopping center A, the processor 31 selects the first all-receipt database 332A. If the company code is the code of the developer that operates shopping center B, the processor 31 selects the second all-receipt database 332B.

[0071] When the processor 31 selects the first all receipt database 332A or the second all receipt database 332B, the processor 31 proceeds to ACT 46. In ACT 46, the processor 31 saves the electronic receipt data with the member ID added or the electronic receipt data without the member ID added in the first all receipt database 332A or the second all receipt database 332B selected in the processing of ACT 45. This completes the information processing performed by the processor 31 when electronic receipt data is received.

[0072] 12 is a flowchart showing parts of the request command reception process executed by the processor 31 of the electronic receipt server 30 based on the data management program that differ from the first embodiment. Specifically, FIG. 12 shows the process after the request command is a full receipt request command and ACT23 returns YES. If ACT23 returns YES, the processor 31 proceeds to ACT51. The processor 31 acquires the company code from the full receipt request command.

[0073] As explained in the first embodiment, the all receipt request command is output from the center server 5. That is, in the second embodiment, the center server 5A outputs the all receipt request command together with the company code identifying the developer of shopping center A. The center server 5B outputs the all receipt request command together with the company code identifying the developer of shopping center B.

[0074] Having obtained the company code from the all receipts request command, processor 31 proceeds to ACT52. In ACT52, processor 31 selects the all receipt database 332 corresponding to the shopping center operated by the developer identified by the company code. That is, if the company code is the code of the developer that operates shopping center A, processor 31 selects the first all receipt database 332A. If the company code is the code of the developer that operates shopping center B, processor 31 selects the second all receipt database 332B.

[0075] Once the processor 31 selects the first full receipt database 332A or the second full receipt database 332B, the processor 31 proceeds to ACT 29. In ACT 29, the processor 31 searches the selected first full receipt database 332A or second full receipt database 332B. Then, in ACT 30, the processor 31 checks whether the electronic receipt data stored in the first full receipt database 332A or the second full receipt database 332B satisfies the condition data included in the full receipt request command. The subsequent processing procedures are the same as in the first embodiment.

[0076] According to the second embodiment configured as described above, it is possible to provide an electronic receipt server 30 that can easily manage data of receipts issued not only to consumers who are electronic receipt members but also to non-member consumers at multiple tenant stores in each of shopping centers A and B operated by different developers as electronic receipt data.

[0077] In the second embodiment, an example was given in which there are two shopping centers, but it goes without saying that similar effects can be achieved even in cases in which there are three or more shopping centers by dividing the total receipt database 332 into sections for each of the centers and managing them on the electronic receipt server 30. Furthermore, if the same developer operates multiple shopping centers, it is clear that similar effects can be achieved by dividing the total receipt database 332 into sections for each of the developers and managing them on the electronic receipt server 30.

[0078] [Third embodiment] Next, a third embodiment will be described. The overall configuration of the data management system in the third embodiment is the same as that of the first embodiment shown in Fig. 1. The overall configuration of the data management system in the third embodiment can also be that of the second embodiment shown in Fig. 8.

[0079] 13 is a flowchart showing the main steps of the main information processing executed by the processor 21 of the processing terminal 2 based on the control program in the third embodiment. In Fig. 13, the same processing steps as those in Fig. 4 showing the same processing in the first embodiment are denoted by the same reference numerals.

[0080] As shown in FIG. 13, the processor 21 executes the same processes as those in the first embodiment from ACT1 to ACT4. That is, in ACT4, the processor 21 checks whether the member ID of the electronic receipt member has been input. If the member ID is read via the reader 27, the processor 21 determines YES in ACT4 and proceeds to ACT5. In ACT5, the processor 21 adds the member ID to the electronic receipt data created in the processing of ACT2. Then, the processor 21 proceeds to the processing of ACT6. On the other hand, if the processor 21 confirms that the "No" button BT2 has been touched based on a signal from the touch panel 26, the processor 21 determines NO in ACT4 and proceeds to ACT7. In ACT7, the processor 21 adds a specific member ID to the electronic receipt data created in the processing of ACT2. Then, the processor 21 proceeds to the processing of ACT6.

[0081] The processor 21 controls the second communication interface 25 as ACT6 to send the electronic receipt data to the electronic receipt server 3. By this control, the electronic receipt data is sent to the electronic receipt server 3 via the communication network 4. Therefore, when the "Yes" button BT1 on the screen SC1 is touched and the member ID is read by the reader 27, the electronic receipt data with the member ID added is sent to the electronic receipt server 3. When the "No" button BT2 on the screen SC1 is touched, the electronic receipt data with the specific member ID added is sent to the electronic receipt server 3.

[0082] Here, a specific member ID is a code that has the same number of digits as the member ID issued to electronic receipt members, but is made up of a combination of numbers, letters, symbols, etc. that are not used as a member ID. For example, if a member ID is 10 digits long and there is no member ID consisting of a string of all 9s, the specific member code would be "99999999999."

[0083] 14 is a flowchart showing the main steps of the receipt data reception process executed by the processor 31 of the electronic receipt server 30 based on the data management program in the third embodiment. As shown in FIG. 14, the processor 31 of the electronic receipt server 30 waits to receive electronic receipt data in ACT51. When electronic receipt data transmitted from any of the processing terminals 2 via the second communication interface 35 is received, the processor 31 determines YES in ACT51 and proceeds to ACT52. The processor 31 acquires the member ID added to the electronic receipt data in ACT52. Then, the processor 31 checks whether the member ID is the specific member ID described above in ACT53.

[0084] If the member ID added to the electronic receipt data is not a specific member ID, the processor 31 determines NO in ACT53 and proceeds to ACT54. In ACT54, the processor 31 stores the electronic receipt data to which the member ID that is not a specific member ID is added in the electronic receipt database 331. After that, the processor 31 proceeds to ACT55.

[0085] On the other hand, if a specific member ID is added to the electronic receipt data, the processor 31 determines YES in ACT53 and skips the processing of ACT54. In other words, the processor 31 does not store the electronic receipt data with the specific member ID added in the electronic receipt database 331. The processor 31 proceeds to ACT55.

[0086] The processor 31 stores the electronic receipt data to which a member ID other than a specific member ID is added or the electronic receipt data to which a specific member ID is added as ACT55 in the all receipt database 332. This completes the information processing performed by the processor 31 when receiving electronic receipt data.

[0087] It is clear that the third embodiment configured as described above can also achieve the same effects as the first embodiment. Furthermore, the third embodiment has the advantage of being able to unify the format of electronic receipt data transmitted from the processing terminal 2 to the electronic receipt server 3.

[0088] The first to third embodiments have been described above as embodiments of a data management system that can easily manage data on receipts issued at multiple stores, but the embodiments are not limited to these.

[0089] For example, in the above embodiment, the acquisition program P1 is installed in the POS terminal 1, and the processing terminal 2 on which the creation program P2 is installed is connected to the POS terminal 1. In another embodiment, the acquisition program P1 and the creation program P2 may be installed in the POS terminal 1, and a device equivalent to the reader 27 of the processing terminal 2 may be connected to the POS terminal 1, so that the POS terminal 1 performs the functions of the processing terminal 2. This makes the processing terminal 2 unnecessary, and eliminates the need to consider where to install the processing terminal 2 in each store.

[0090] For example, in the first embodiment, the processor 31 of the electronic receipt server 3 determines YES in ACT11 of Fig. 4 and then executes the process in ACT12. In this regard, the processor 31 may execute the process in ACT14 first after determining YES in ACT11 of Fig. 4. Then, the processor 31 may execute the process in ACT12, and then execute the process in ACT13 if a member ID is added to the electronic receipt data.

[0091] For example, in the first embodiment, the processor 31 of the electronic receipt server 3 checks whether the received command is an electronic receipt request command in ACT22 of Fig. 7, and if it is not an electronic receipt request command, checks whether it is an all-receipt request command. In this regard, it may be possible to first check whether the received command is an all-receipt request command, and then check whether the received command is an electronic receipt request command.

[0092] 7, if a member ID is added to the electronic receipt data, the processor 31 deletes the member ID in ACT 33 and ACT 34 before saving the electronic receipt data in the receipt memory. In this regard, the processor 31 omits the processes in ACT 32 and ACT 33 and saves the electronic receipt data in the receipt memory regardless of whether a member ID is added or not. Then, when the search of the entire receipt database 332 is completed in ACT 35, the processor 31 may delete the member ID all at once from the electronic receipt data saved in the receipt memory and send it to the center server 5.

[0093] Although several 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 spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the inventions and their equivalents as defined in the claims. The inventions described in the original claims of this application are set forth below. [1] A data management device comprising: a receiving unit that receives receipt data that is an electronic version of a receipt containing information about a transaction settled as a single transaction; and a control unit that, if the receipt data received by the receiving unit has target identification information that identifies the target of the transaction added to it, stores the receipt data in a first memory unit and a second memory unit; and, if the target identification information is not added, stores the receipt data in the first memory unit but does not store it in the second memory unit. [2] The receipt data includes sender identification information that identifies the sender of the receipt data, and the control unit stores the receipt data in the second memory unit according to the sender identification information included in the receipt data. [3] The data management device according to appendix [2], wherein the second memory unit is provided for each of the sender identification information. [4] A data management system including a data management device according to any one of appendices [1] to [3] and a processing terminal connected to the data management device via a network, wherein the processing terminal is equipped with a creation means for creating receipt data by digitizing receipts, an acquisition means for acquiring the target person identification information, and a transmission control means for, if the target person identification information is acquired by the acquisition means, adding the target person identification information to the receipt data and sending it to the data management device, and, if the target person identification information is not acquired, sending the receipt data to the data management device without adding the target person identification information. [5] A data management system as described in appendix [4], wherein the transmission control means of the processing terminal, if the target person identification information has not been acquired, adds specific target person identification information and sends the receipt data to the data management device, and the control unit of the data management device, if the target person identification information added to the receipt data is not the specific target person identification information, stores the receipt data in a first memory unit and a second memory unit, and if the target person identification information is the specific target person identification information, stores the receipt data in the first memory unit and does not store it in the second memory unit. [6] A data management program for realizing the following function in a computer of a data management device having a receiving unit that receives receipt data that has been digitized from a receipt containing information about a transaction settled as a single transaction: if the receipt data received by the receiving unit has target person identification information that identifies the target person of the transaction added to it, the receipt data is stored in a first memory unit and a second memory unit; if the target person identification information is not added, the receipt data is stored in the first memory unit and not stored in the second memory unit. [Explanation of symbols]

[0094] 1...POS terminal, 2...processing terminal, 3,30...electronic receipt server, 4...communication network, 5,5A,5B...center server, 7,7A,7B...client terminal, 8...Internet, 9...information terminal, 21,31...processor, 22,32...main memory, 23,33...auxiliary storage device, 24,34...first communication interface, 25,35...second communication interface, 26...touch panel 26...reader, 331...electronic receipt database, 332,332A,332B...total receipt database, P1...acquisition program, P2...creation program.

Claims

1. A means for generating receipt data by digitizing a receipt including information on a transaction settled as one transaction; an acquisition means for acquiring target identification information that identifies the target of the transaction; a communication means for communicating with a data management device having a first storage unit and a second storage unit; a transmission control means for, when the target person identification information is acquired by the acquisition means, adding the target person identification information to receipt data created by the creation means and transmitting the receipt data to the data management device, which stores the receipt data in the first storage unit and the second storage unit; and, when the target person identification information is not acquired, adding specific target person identification information that is not used as the target person identification information to the receipt data created by the creation means, storing the receipt data in the first storage unit, and transmitting the receipt data to the data management device, which does not store the receipt data in the second storage unit; A processing terminal comprising:

2. receiving means for receiving receipt print data from a terminal for settling a transaction; Further comprising:

2. The processing terminal according to claim 1, wherein said creating means creates said receipt data based on said receipt print data received by said receiving means.

3. a display control means for displaying on a display unit a screen inquiring whether or not the person to whom the transaction is made is an electronic receipt member who receives the receipt as an electronic receipt; Further comprising: The processing terminal according to claim 1 , wherein the acquiring unit acquires the target person identification information when the target person of the transaction is the electronic receipt member.

4. a processing terminal computer that communicates with a data management device having a first storage unit and a second storage unit; A means for generating receipt data by digitizing a receipt including information on a transaction settled as one transaction; An acquisition means for acquiring target identification information that identifies a target of the settled transaction; and a transmission control means for, when the target person identification information is acquired by the acquisition means, adding the target person identification information to receipt data created by the creation means and transmitting the receipt data to the data management device, which stores the receipt data in the first storage unit and the second storage unit; and, when the target person identification information is not acquired, adding specific target person identification information that is not used as the target person identification information to the receipt data created by the creation means, storing the receipt data in the first storage unit, and transmitting the receipt data to the data management device, which does not store the receipt data in the second storage unit; A program to function as a

5. The processing terminal computer, receiving means for receiving receipt print data from a terminal for settling a transaction; It further functions as 5. The program according to claim 4, wherein the creating means functions as a means for creating the receipt data based on the receipt print data received by the receiving means.

6. The processing terminal computer, a display control means for displaying on a display unit a screen inquiring whether or not the person to whom the transaction is made is an electronic receipt member who receives the receipt as an electronic receipt; It further functions as The program according to claim 4 , wherein the acquisition means functions as a means for acquiring target person identification information when the target person of the transaction is the electronic receipt member.

Images