Data management system, data management device and storage medium

Abstract

This invention discloses a data management system, a data management device, and a storage medium, which can easily manage data of invoices issued by various stores. The data management device includes a receiving unit and a control unit. The receiving unit receives invoice data that has been digitized, containing information about a settled transaction. When the invoice data received by the receiving unit includes recipient identification information, the control unit stores the invoice data in a first storage unit and a second storage unit. When no recipient identification information is attached, the control unit stores the invoice data in the first storage unit and does not store it in the second storage unit.

Description

[0001] This application claims priority from Japanese patent application No. JP2019-164754, filed on September 10, 2019, and cites the contents of the aforementioned application, the disclosure of which is hereby incorporated by reference in its entirety. Technical Field

[0002] An embodiment of the present invention relates to a data management system, a data management device, and a storage medium storing a data management program for causing a computer to function as the data management device. Background Art

[0003] Currently, the business groups that operate shopping malls, so-called developers, sign lease contracts with individual stores as tenants, and maintain sales mainly through rental fees. Therefore, developers grasp the total sales of each store and reflect it in the rental fees. However, recently, due to fierce competition and sluggish sales, there are also requests among developers to analyze the sales of products for each store.

[0004] Such a requirement can be achieved, for example, by managing the data of receipts issued by each tenant. However, the POS (Point Of Sales) system built by each store is completed in the store. In addition, the manufacturers of store servers or POS terminals that constitute the POS system are not unified. For these reasons, it is difficult to simply manage the data of receipts issued by multiple stores in the existing technology. Summary of the invention

[0005] In view of the above problems, the technical problem to be solved by the present invention is to provide a data management system and a data management device and a storage medium of the system, which can simply manage the data of the receipts issued by each store.

[0006] To solve the above problem, one embodiment of the present invention provides a data management device, including a receiving unit and a control unit. The receiving unit receives bill data that is an electronic bill containing information of a transaction that has been settled. When the bill data received by the receiving unit is attached with subject identification information for identifying the subject of the transaction, the control unit stores the bill data in a first storage unit and a second storage unit. When the subject identification information is not attached, the control unit stores the bill data in the first storage unit and does not store it in the second storage unit.

[0007] According to the above-described data management device, it is possible to provide a data management device capable of managing not only electronic receipts having subject identification information but also receipt data not having subject identification information as electronic receipt data.

[0008] In the above-mentioned data management device, the receipt data includes transmission source identification information for identifying a transmission source of the receipt data, and the control unit stores the receipt data in the first storage unit according to the transmission source identification information included in the receipt data.

[0009] According to the above data management device, it is possible to provide a data management device that can manage not only electronic receipts with subject identification information but also receipt data without subject identification information as electronic receipt data in accordance with different transmission source identification information.

[0010] In the above-mentioned data management device, the first storage unit is provided according to the transmission source identification information.

[0011] According to the above-described data management device, electronic receipt data having the same transmission source identification information can be collectively managed.

[0012] In the above-mentioned data management device, when the subject person identification information for identifying the subject person of the transaction is added to the receipt data received by the receiving unit, the control unit deletes the subject person identification information and stores the receipt data in the first storage unit.

[0013] According to the above-mentioned data management device, the format of the receipt data stored in the first storage unit can be unified.

[0014] The above-mentioned data management device further includes: a sending control unit, when receiving a command to send the ticket data in the first storage unit, sending the ticket data in the first storage unit to the sending source of the command.

[0015] According to the above-mentioned data management device, the receipt data in the first storage unit can be transmitted in response to a request.

[0016] In the above-mentioned data management device, the transmission control unit deletes the subject person identification information before transmitting the receipt data in the first storage unit.

[0017] According to the above-mentioned data management device, it is possible to prevent personal information from being transmitted.

[0018] The above-mentioned data management device also includes: a sending control unit, when receiving a command containing the sending source identification information and requesting to send the ticket data of the first storage unit, sends the ticket data of the first storage unit that is consistent with the sending source information.

[0019] According to the above-mentioned data management device, it is possible to transmit receipt data with designated transmission source identification information.

[0020] The data management system according to another aspect of the present invention comprises: the above-mentioned data management device; and a processing terminal connected to the data management device via a network, wherein the processing terminal comprises: a production unit for producing ticket data that digitizes the ticket; an acquisition unit for acquiring the subject person identification information; and a sending control unit for attaching the subject person identification information to the ticket data and sending the same to the data management device when the subject person identification information is acquired by the acquisition unit, and for sending the ticket data to the data management device without attaching the subject person identification information when the subject person identification information is not acquired.

[0021] According to the above-described data management system, it is possible to provide a data management device capable of managing not only electronic receipts having subject identification information but also receipt data not having subject identification information as electronic receipt data.

[0022] In the above-mentioned data management system, when the object person identification information is not obtained, the sending control unit of the processing terminal adds the specified object person identification information to the ticket data and sends it to the data management device. When the object person identification information attached to the ticket data is not the specified object person identification information, the control unit of the data management device saves the ticket data in the first storage unit and the second storage unit, and when it is the specified object person identification information, the ticket data is saved in the first storage unit and is not saved in the second storage unit.

[0023] According to the above-mentioned data management system, the format of the receipt data transmitted from the processing terminal to the data management device can be unified.

[0024] A computer-readable storage medium in another aspect of the present invention stores a data management program, which enables a computer having a data management device having a receiving unit for receiving electronic bill data containing information about a transaction that has been settled as a transaction to implement the following functions: when the bill data received by the receiving unit is attached with subject identification information that identifies the subject of the transaction, the bill data is stored in a first storage unit and a second storage unit; when the subject identification information is not attached, the bill data is stored in the first storage unit and not stored in the second storage unit.

[0025] According to the computer-readable storage medium, it is possible to provide a computer with a function of managing not only electronic receipts having subject identification information but also receipt data without subject identification information as electronic receipt data. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Below, the data management system, data management device and data management program involved in the embodiment are described with reference to the accompanying drawings. When considered in conjunction with the accompanying drawings, by referring to the detailed description below, the present invention can be more completely and better understood and many of the accompanying advantages can be easily known, but the drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The illustrative embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention, wherein:

[0027] Figure 1 is a diagram showing the overall configuration of a system including a data management system of the first embodiment;

[0028] Figure 2 This is a block diagram showing the main circuit configuration of a processing terminal included in the data management system;

[0029] Figure 3 This is a block diagram showing the main circuit structure of the electronic receipt server included in the data management system;

[0030] Figure 4 is a flowchart showing the main sequence of the main information processing executed by the processor of the processing terminal based on the control program;

[0031] Figure 5 is a diagram showing an example of a screen displayed on the touch panel of the processing terminal;

[0032] Figure 6 is a flowchart showing the main sequence of the electronic receipt data receiving process executed by the processor of the electronic receipt server based on the data management program;

[0033] Figure 7 is a flowchart showing the main sequence of request command reception processing performed by the processor of the electronic receipt server based on the data management program;

[0034] Figure 8 is a diagram showing the overall structure of a data management system including the second embodiment;

[0035] Fig. 9 This is a block diagram showing the main circuit structure of the electronic receipt server included in the data management system;

[0036] Fig.10 It is a schematic diagram showing an example of the composition of bill data;

[0037] Fig.11 is a flowchart showing the main sequence of the electronic receipt data receiving process executed by the processor of the electronic receipt server based on the data management program;

[0038] Fig.12is a flowchart showing a portion of the request command reception process executed by the processor of the electronic receipt server based on the data management program that is different from the first embodiment;

[0039] Fig.13 is a flowchart showing the main sequence of information processing executed by the processor of the processing terminal based on the control program in the third embodiment; and

[0040] Fig.14 1 is a flowchart showing the main procedures of an electronic receipt data receiving process executed by a processor of an electronic receipt server based on a data management program in the third embodiment.

[0041] Description of Reference Numerals

[0042] 1 POS terminal 2 Processing terminal

[0043] 3.30 Electronic receipt server 4 Communication network

[0044] 5, 5A, 5B Central server 7, 7A, 7B Client terminal

[0045] 8 Internet 9 Information Terminal

[0046] 21, 31 Processor 22, 32 Main memory

[0047] 23, 33 auxiliary storage device 24, 34 first communication interface

[0048] 25, 35 Second interface 26 Touch panel

[0049] 27 Reader 331 Electronic Ticket Database

[0050] 332, 332A, 332B full bill database

[0051] P1 Get program P2 Create program DETAILED DESCRIPTION

[0052] Hereinafter, embodiments of a data management system and a data management device of the system that can easily manage data of receipts issued in a plurality of stores will be described with reference to the accompanying drawings.

[0053] In the embodiment described below, a data management system is exemplified in which a developer of a shopping mall can easily manage data of receipts issued by a plurality of stores that rent storefronts and open stores as tenants in the shopping mall.

[0054] (First embodiment)

[0055] Figure 1This is a diagram showing the overall structure of the data management system of the first embodiment. The data management system includes a plurality of processing terminals 2, an electronic receipt server 3, and a communication network 4, each of which is connected to a plurality of POS terminals 1. The communication network 4 is, for example, an Internet VPN (Virtual Private Network). In addition to the processing terminals 2 and the electronic receipt server 3, the communication network 4 is also connected to a central server 5. The central server 5 is a computer managed by the developer of the shopping mall. The central server 5 is connected to a client terminal 7 via a communication line 6. In addition, the electronic receipt server 3 and the central server 5 may also be in the cloud.

[0056] The POS terminal 1 and the processing terminal 2 are provided in each store that rents a storefront as a tenant in the shopping mall. The POS terminal 1 and the processing terminal 2 are connected, for example, via a communication line in accordance with the interface specification of RS232D. The communication line can be either wired or wireless. The number of POS terminals 1 provided in each store is arbitrary. In addition, the number of processing terminals 2 is also arbitrary. The POS terminal 1 and the processing terminal 2 may not necessarily correspond to each other in a one-to-one manner. Multiple POS terminals 1 may be connected to one processing terminal 2. It is sufficient as long as at least one processing terminal 2 is connected to the POS terminal 1.

[0057] Each POS terminal 1 is installed with an acquisition program P1. The acquisition program P1 is an agent program specifically used to acquire the printing data of the receipt created in the POS terminal 1 and output it to the processing terminal 2. The POS terminal 1 has a printer for printing receipts. The POS terminal 1 prints the printing data of the receipt through the printer, thereby issuing a paper receipt. The paper receipt is printed with the name, price, total amount, etc. of the commodity registered as a transaction, and also printed with the transaction date and time, transaction number, cash register number, etc. Such a POS terminal 1 is well known. Therefore, a detailed description here is omitted.

[0058] Each processing terminal 2 is installed with a production program P2. The production program P2 is a program specifically used for processing the production of structured electronic receipt data based on the unstructured receipt printing data received from the POS terminal 1. As the process of producing electronic receipt data based on the receipt printing data can be directly applied to the known technology, the detailed description is omitted here.

[0059] Figure 22 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 line 28. The system transmission line 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 line 28. In the processing terminal 2, a computer is constituted by the processor 21, the main memory 22, the auxiliary storage device 23, and the system transmission line 28 connecting them.

[0060] The processor 21 corresponds to the core part of the above-mentioned computer. The processor 21 controls each part to realize various functions as the processing terminal 2 according to the operating system or application program. The processor 21 is, for example, a CPU (Central Processing Unit).

[0061] The main memory 22 is equivalent to the main storage part of the above-mentioned computer. The main memory 22 includes a non-volatile storage area and a volatile storage area. The main memory 22 stores an operating system or an application program in the non-volatile storage area. The main memory 22 sometimes stores data required for the processor 21 to perform processing for controlling each part in the non-volatile or volatile storage area. The main memory 22 uses the volatile storage area as a work area for rewriting data appropriately by the processor 21. An example of a non-volatile storage area is a ROM (Read Only Memory). An example of a volatile storage area is a RAM (Random Access Memory).

[0062] The auxiliary storage device 23 is equivalent to the auxiliary storage part of the above-mentioned computer. For example, EEPROM (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disc Drive) or SSD (Solid State Drive) can be the auxiliary storage device 23. The auxiliary storage device 23 stores data used when the processor 21 performs various processes or data generated by the processing in the processor 21. The auxiliary storage device 23 sometimes also stores the above-mentioned application program.

[0063] The application programs stored in the main memory 22 or the auxiliary storage device 23 include control programs described in connection with information processing executed in the processing terminal 2. The control programs also include the above-mentioned production program P2. The method of installing the control program including the production program P2 into the main memory 22 or the auxiliary storage device 23 is not particularly limited. The control program can be stored in a removable storage medium, or the control program can be distributed through network communication and then installed in the main memory 22 or the auxiliary storage device 23. The storage medium is not limited in form as long as it can store programs and can be read by a device, such as a CD-ROM or a memory card.

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

[0065] The second communication interface 25 is an interface for performing data communication with the electronic receipt server 3 through the communication interface 4. The second communication interface 25 can also perform data communication with the central server 5 through the communication network 4.

[0066] The touch panel 26 is a device having functions as an input device and a display device of 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 contactless RFID (Radio Frequency IDentification), the reader 27 is an RFID reader.

[0067] Back to Figure 1 Description.

[0068] The electronic receipt server 3 is a computer managed by a corporate group that provides the electronic receipt server. The corporate group is a different corporate group from the developer of the shopping mall. The corporate group may also be managed by the shopping mall.

[0069] The electronic receipt server 3 collects the electronic receipt data generated in each processing terminal 2 through the communication network 4 and saves it in a database (DB). In addition, the electronic receipt server 3 receives 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 has a function as a data management device of a data management system.

[0070] The information terminal 9 is an electronic device owned by a consumer who has registered as a member to receive the electronic receipt service. The information terminal 9 is installed with an application required for receiving the electronic receipt service, the so-called electronic receipt application. By installing the electronic receipt application in the information terminal 9, a unique electronic receipt ID is set for the information terminal 9. When the electronic receipt application is started in 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.

[0071] Figure 3 1 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 line 36. The system transmission line 36 includes an address bus, a data bus, a control signal line, and the like. 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 line 36. In the electronic receipt server 3, the processor 31, the main memory 32, the auxiliary storage device 33, and the system transmission line 36 connecting them constitute a computer.

[0072] The processor 31 corresponds to the core part of the computer. The processor 31 controls each part according to the operating system or application program to realize various functions of the electronic receipt server 3. The processor 31 is, for example, a CPU.

[0073] The main memory 32 is equivalent to the main storage part of the above-mentioned computer. The main memory 32 includes a nonvolatile storage area and a volatile storage area. The main memory 32 stores an operating system or an application program in the nonvolatile storage area. The main memory 32 sometimes stores data required when the processor 31 performs processing for controlling each part in the nonvolatile or volatile storage area. The main memory 32 uses the volatile storage area as a work area for appropriately rewriting data by the processor 31. The nonvolatile storage area is, for example, ROM. The volatile storage area is, for example, RAM.

[0074] The auxiliary storage device 33 is equivalent to the auxiliary storage part of the above-mentioned computer. For example, EEPROM, HDD or SSD can be used as the auxiliary storage device 33. The auxiliary storage device 33 stores data used when the processor 31 performs various processes or data generated by the processing in the processor 31. The auxiliary storage device 33 sometimes also stores the above-mentioned application program.

[0075] The application programs stored in the main memory 32 or the auxiliary storage device 33 include control programs described in relation to information processing executed in the electronic receipt server 3. The control program also includes a data management program described later. The method of installing the control program including the data management program into the main memory 32 or the auxiliary storage device 33 is not particularly limited. The control program can be stored in a removable storage medium, or the control program can be distributed through network communication and then installed in the main memory 32 or the auxiliary storage device 33. The storage medium is not limited in form as long as it can store programs and can be read by a device, such as a CD-ROM or a memory card.

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

[0077] The second communication interface 35 is an interface for performing data communication with each processing terminal 2 via the communication network 4. Here, the second communication interface 35 has a function as a receiving unit for receiving electronic receipt data generated in each processing terminal 2.

[0078] The electronic receipt server 3 of the configuration involved uses a part of the storage area of ​​the auxiliary storage device 33 as an electronic receipt database 331, and uses another part of the storage area as a full receipt database 332. The electronic receipt database 331 is an area for storing electronic receipt data, so-called electronic receipt data, which is a receipt containing information on a transaction that has been settled as a transaction with an electronic receipt member. The full receipt database 332 is an area for storing electronic receipt data, which is a receipt containing information on a transaction that has been settled as a transaction with all consumers including the electronic receipt member. Here, the full receipt database 332 has a function as a first storage unit. The electronic receipt database 331 has a function as a second storage unit.

[0079] Figure 4 This is a flowchart showing the main procedures of the main information processing executed by the processor 21 of the processing terminal 2 based on the control program. Figure 5 This is an example of a screen SC1 displayed on the touch panel 26 of the processing terminal 2 . Figure 6 This is a flowchart showing the main procedures of receipt data reception processing executed by the processor 31 of the electronic receipt server 3 based on the data management program. Figure 7 This is a flowchart showing the main sequence of the request command reception process executed by the processor 31 of the electronic receipt server 3 based on the data management program. Figures 4 to 7, the operation of the data processing system is described, and the data management method can be known through the following description. In addition, the content of the operation described below is an example. If the same effect can be obtained, data processing according to the data management program can also be performed with other operation contents.

[0080] like Figure 4 As shown, the processor 21 of the processing terminal 2 waits as ACT1 to receive receipt printing data from the POS terminal 1. In the POS terminal 1, when a transaction with a consumer is settled, receipt printing data including information on the goods purchased in the transaction is produced. And, the receipt printing data is sent to the processing terminal 2 through the communication line by the action of the acquisition program P1.

[0081] When the processor 21 of the processing terminal 2 receives the receipt printing data generated in the POS terminal 1 through the first communication interface 24, it determines YES in ACT 1 and proceeds to ACT 2. As ACT 2, the processor 21 converts the unstructured receipt printing data into structured electronic receipt data according to the generation program P2. In addition, as ACT 3, the processor 21 causes the touch panel 26 to display Figure 5 The screen SC1 shown. On the screen SC1, a message MS1 is displayed to inquire whether or not the user is an electronic receipt member, and a "yes" button BT1 for affirmative response and a "no" button BT2 for negative response are also displayed.

[0082] The operator who has confirmed the screen SC1 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. The operator then reads the barcode of the electronic receipt ID displayed on the display of the information terminal 9 owned by the consumer through the reader 27.

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

[0084] When the processor 21 of the processing terminal 2 causes the touch panel 26 to display the screen SC1, it confirms as ACT4 whether the member ID of the electronic receipt member has been input. When the member ID is read by the reader 27, the processor 21 determines YES in ACT4 and proceeds to ACT5. As ACT5, the processor 21 adds the member ID to the electronic receipt data generated by the processing of ACT2. And, the processor 21 proceeds to the processing of ACT6. In response to this, when it is confirmed that the "No" button BT2 has been touched based on the signal from the touch panel 26, the processor 21 determines NO in ACT4, skips the processing of ACT5 and proceeds to ACT6.

[0085] The processor 21 controls the second communication interface 25 as ACT 6 to send the electronic receipt data to the electronic receipt server 3. Through this control, the electronic receipt data is sent to the electronic receipt server 3 through the communication network 4. Therefore, when the "Yes" button BT1 of the screen SC1 is touched and the member ID is read by the reader 27, the electronic receipt data attached with the member ID is sent to the electronic receipt server 3. When the "No" button BT2 of the screen SC1 has been touched, the electronic receipt data without the member ID is sent to the electronic receipt server 3.

[0086] Here, the processor 21, which is the main body of the computer of the processing terminal 2, constitutes a production unit for producing electronic receipt data by executing the processing of ACT2. In addition, the processor 21 cooperates with the touch panel 26 to execute the processing of ACT3 and ACT4, thereby constituting an acquisition unit for acquiring a member ID as identification information of the subject. In addition, the processor 21 cooperates with the second communication interface 25 to execute the processing of ACT5 and ACT6, thereby constituting a transmission control unit. That is, when the processor 21 obtains the member ID, it attaches the member ID to the electronic receipt data and sends it to the electronic receipt server 3 as the data management device. When the processor 21 does not obtain the member ID, it sends the electronic receipt data to the electronic receipt server 3 without attaching the member ID.

[0087] like Figure 6As shown, the processor 31 of the electronic receipt server 3 waits for receiving the electronic receipt data as ACT 11. When the electronic receipt data sent from any processing terminal 2 is received through the second communication interface 35, the processor 31 determines YES as ACT 11 and proceeds to ACT 12. The processor 31 confirms whether the member ID is attached to the electronic receipt data as ACT 12. When the member ID is attached, the processor 31 determines YES in ACT 12 and proceeds to ACT 13. The processor 31 saves the electronic receipt data attached with the member ID in the electronic receipt database 331 as ACT 13. After that, the processor 31 proceeds to ACT 14.

[0088] In this regard, when the member ID is not added to the electronic receipt data, the processor 31 determines NO in ACT 12 and skips the processing of ACT 13. In other words, the processor 31 does not store the electronic receipt data without the member ID in the electronic receipt database 331. The processor 31 proceeds to ACT 14.

[0089] The processor 31 stores the electronic receipt data to which the member ID is added or the electronic receipt data to which the member ID is not added in the all-receipt database 332 as ACT 14. In the above, the processor 31 ends the information processing when receiving the electronic receipt data.

[0090] Here, the processor 31 as the main body of the computer of the electronic receipt server 3 executes the data management program. Figure 6 The control unit is constituted by the processing in the order shown in the flowchart. That is, when the electronic receipt data received through the second communication interface 35 as the receiving unit is attached with the member ID as the subject identification information, the processor 31 stores the electronic receipt data in the full receipt database 332 as the first storage unit and the electronic receipt database 331 as the second storage unit. In addition, when the member ID is not attached, the processor 31 stores the electronic receipt data in the full receipt database 332, and does not store it in the electronic receipt database 331.

[0091] like Figure 7 As shown, the processor 31 of the electronic receipt server 3 waits for receiving a data request command as ACT 21. The data request command includes an electronic receipt request command output from the information terminal 9 and a full receipt request command output from the center server 5. The electronic receipt request command includes a member ID set by the information terminal 9 that is the source of the command. The full receipt request command includes, for example, condition data input by operating the client terminal (client) 7. The condition data is data that specifies, for example, a store that is a tenant individually. The condition data is, for example, data that specifies all stores collectively.

[0092] When the processor 31 receives the data request command, it determines YES in ACT21 and proceeds to ACT22. As ACT22, the processor 31 confirms whether the received command is an electronic receipt request command. When it is not an electronic receipt request command, the processor 31 determines NO in ACT22 and proceeds to ACT23. As ACT23, the processor 31 confirms whether the received command is a full receipt request command. In addition, when it is not a full receipt request command, the processor 31 determines NO in ACT23 and executes processing based on other request commands.

[0093] When the first communication interface 34 receives the electronic receipt request command from the information terminal 9, the processor 31 determines YES in ACT 22 and proceeds to ACT 24. The processor 31 searches the electronic receipt database 331 as ACT 24. Furthermore, the processor 31 confirms as ACT 25 whether the member ID attached to the electronic receipt data stored in the electronic receipt database 331 is consistent with the member ID included in the electronic receipt request command.

[0094] If the two member IDs do not match, the processor 31 determines NO in ACT 25, skips ACT 26 and proceeds to ACT 27. The processor 31 confirms whether the search of the electronic receipt database 331 has been completed in ACT 27. If the search has not been completed, the processor 31 determines NO in ACT 27 and returns to ACT 24. In other words, the processor 31 continues to search the electronic receipt database 331.

[0095] As a result of searching the electronic receipt database 331, when the electronic receipt data to which the 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. The processor 31 obtains the electronic receipt data that matches the member ID from the electronic receipt database 331 as ACT 26, and stores it in the receipt memory. The receipt memory is formed in a volatile area of ​​the main memory 32, for example.

[0096] After the electronic receipt data corresponding to the member ID is stored in the receipt memory, the processor 31 confirms whether the search of the electronic receipt database 331 has been completed as ACT 27. If the search has not been completed, the processor 31 returns to ACT 24 and continues to search the electronic receipt database 331.

[0097] In this way, the processor 31 that has received the electronic receipt request command searches the electronic receipt database 331. Moreover, whenever the processor 31 detects the electronic receipt data to which the member ID included in the electronic receipt request command is attached, the processor 31 stores the electronic receipt data in the receipt memory. Moreover, when the search of the electronic receipt database 331 is completed, the processor 31 determines YES in ACT27 and proceeds to ACT28. As ACT28, the processor 31 controls the first communication interface 34 to send all the electronic receipt data stored in the receipt memory to the information terminal 9 that is the source of the electronic receipt request command. Through this control, the electronic receipt data is sent from the first communication interface 34 to the information terminal 9 through the Internet 8. In other words, the electronic receipt data to which the member ID set in the information terminal 9 is attached is sent to the information terminal 9 that is the source of the electronic receipt request command. In this way, in the information terminal 9, the electronic receipt can be displayed on its display, so that the electronic receipt member who is a consumer can receive the receipt that shows the information of the transaction conducted in the store as an electronic receipt.

[0098] On the other hand, when a full receipt request command (a command requesting the receipt data in the first storage unit to be sent) 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. The processor 31 searches the full receipt database 332 as ACT 29. Furthermore, the processor 31 confirms as ACT 30 whether the electronic receipt data stored in the full receipt database 332 satisfies the condition data included in the full receipt request command.

[0099] For example, when the condition data is data of a single designated store, the processor 31 uses the electronic receipt data of the receipt issued by the store as data satisfying the condition. The electronic receipt data contains store identification information for identifying the store, so the processor 31 determines whether the condition is satisfied based on the store identification information.

[0100] For example, when the condition data is data specifying all stores, the processor 31 regards all electronic receipt data stored in the full receipt database 332 as data satisfying the condition.

[0101] If the condition is not satisfied, the processor 31 determines NO in ACT 30, skips ACT 31 to ACT 34, and proceeds to ACT 35. The processor 31 confirms whether the search of the entire receipt database 332 has been completed as ACT 35. If the search has not been completed, the processor 31 determines NO in ACT 35 and returns to ACT 29. That is, the processor 31 continues to search the entire receipt database 332.

[0102] As a result of searching the full receipt database 332, when electronic receipt data satisfying the condition data included in the full receipt request command is detected, the processor 31 determines YES in ACT 30 and proceeds to ACT 31.

[0103] The processor 31 obtains the electronic receipt data from the electronic receipt database 331 as ACT 31. Furthermore, the processor 31 confirms whether the member ID is attached to the electronic receipt data as ACT 32. If the member ID is attached to the electronic receipt data, the processor 31 determines YES in ACT 32 and proceeds to ACT 33. The processor 31 deletes the member ID from the electronic receipt data as ACT 33. Furthermore, the processor 31 stores the electronic receipt data from which the member ID is deleted in the above-mentioned receipt memory as ACT 34.

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

[0105] Thereafter, the processor 31 checks as ACT 35 whether the search of the electronic receipt database 331 has been completed. If the search has not been completed, the processor 31 continues to search the entire receipt database 332.

[0106] In this way, the processor 31 that receives the full invoice request command searches the full invoice database 332. Moreover, whenever the processor 31 detects electronic invoice data that satisfies the condition data included in the full invoice request command, it stores the electronic invoice data in the invoice memory. At this time, when a member ID is attached to the electronic invoice data, the member ID is deleted and stored in the invoice memory. By deleting the member ID, personal information is prevented from being sent to the developer. Moreover, when the search of the full invoice database 332 is completed, the processor 31 determines YES in ACT35 and proceeds to ACT36. As ACT36, the processor 31 controls the second communication interface 35 to send all the electronic invoice data stored in the invoice memory to the central server 5 that is the source of the full invoice request command. The sending control unit is the processor 31 that performs a series of processes from ACT23 to ACT36. Through this control, the electronic invoice data is sent from the second communication interface 35 to the central server 5 through the communication network 4. At this time, the electronic invoice data is converted into CSV format, for example, and then sent to the central server 5. Therefore, the client terminal 7 connected to the center server 5 can acquire the data of the receipt that meets the specified conditions and browse or process it.

[0107] Thus, according to the first embodiment, an electronic receipt server 3 can be provided which can simply manage the data of receipts issued not only to consumers who are electronic receipt members but also to consumers who are not members in a plurality of stores which are tenants of a shopping mall as electronic receipt data.

[0108] 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 installed with the production program P2 is connected to the POS terminal 1. Furthermore, by connecting the processing terminal 2 to the electronic receipt server 3 via the communication network 4, a data management system that achieves the above-mentioned effects is formed. Therefore, even in a shopping mall where each store has introduced an existing POS system, a data management system that achieves the above-mentioned effects can be realized at a low cost by adding a simple structure. Furthermore, there is no problem even if the manufacturers of the POS systems introduced by each store are different.

[0109] (Second embodiment)

[0110] Next, the second embodiment is described. In the first embodiment, the electronic receipt server 3 is used to manage the data of receipts issued by multiple stores included as tenants in one shopping mall. In the second embodiment, the electronic receipt server 30 is used to manage the data of receipts issued by multiple stores included as tenants in multiple shopping malls of different developers. In addition, in the second embodiment, the number of shopping malls is considered to be two for the convenience of explanation.

[0111] Figure 8 FIG. 2 is a diagram showing the overall structure of the data management system including the second embodiment. Figure 8 In the data management system representing the first embodiment, Figure 1 The same reference numerals are used for common parts, and detailed description thereof will be omitted.

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

[0113] The POS terminal 1 and the processing terminal 2 are installed in each store that rents a storefront as a tenant in the shopping center A or the shopping center B. The POS terminal 1 and the processing terminal 2 are connected via a communication line according to the interface specification of RS232, for example. The communication line can be either wired or wireless. The POS terminal 1 and the processing terminal 2 are as described in the first embodiment. Therefore, the above description is omitted.

[0114] Fig. 9 FIG. 2 is a block diagram showing the main circuit structure of the electronic receipt server 30. Fig. 9 and Figure 3 By comparison, it can be seen that the difference between the electronic receipt server 30 and the electronic receipt server 3 of the first embodiment is the number of full receipt databases 332. That is, in the second embodiment, the full receipt database 332 using a part of the storage area of ​​the auxiliary storage device 33 is divided into a first full receipt database 332A and a second full receipt database 332B. The first full receipt database 332A is the full receipt database 332 corresponding to the shopping center A. The second full receipt database 332B is the full receipt database 332 corresponding to the shopping center B.

[0115] Fig.10 : is a schematic diagram showing the main data structure of the tickets issued from each store that is a tenant of two shopping malls A and B. Fig.10 As shown, the receipt is a data structure including not only the name, price, and total amount of the commodity registered as a transaction, but also a company code (source identification information for identifying the source of transmission), a store code, a terminal number, and a transaction number. The company code is a unique code for identifying the developer. The store code is a unique code for identifying the store. The terminal number is a unique code for identifying the POS terminal 1. The transaction number is a continuous number issued every time a transaction is processed in the POS terminal 1 identified by the terminal number. Therefore, the transaction data can be specified as unique data by combining the company code, the store code, the terminal number, and the transaction number.

[0116] Fig.11 1 is a flowchart showing the main sequence of receipt data receiving processing performed by the processor 31 of the electronic receipt server 30 based on the data management program. Fig.11As shown, the processor 31 of the electronic receipt server 30 waits for receiving the electronic receipt data as ACT 41. When the electronic receipt data sent from any processing terminal 2 is received through the second communication interface 35, the processor 31 determines YES as ACT 41 and proceeds to ACT 42. The processor 31 confirms whether the member ID is attached to the electronic receipt data as ACT 42. When the member ID is attached, the processor 31 determines YES in ACT 42 and proceeds to ACT 43. The processor 31 saves the electronic receipt data attached with the member ID in the electronic receipt database 331 as ACT 43. Thereafter, the processor 31 proceeds to ACT 44.

[0117] In this regard, when the member ID is not added to the electronic receipt data, the processor 31 determines NO in ACT 42 and skips the processing of ACT 43. In other words, the processor 31 does not store the electronic receipt data without the member ID in the electronic receipt database 331. The processor 31 proceeds to ACT 44.

[0118] The processor 31 obtains the company code from the electronic receipt data to which the member ID is attached or the electronic receipt data to which the member ID is not attached as ACT 44. Furthermore, the processor 31 selects the full receipt database 332 corresponding to the shopping mall operated by the developer identified by its company code. That is, when the company code is the code of the developer operating the shopping mall A, the processor 31 selects the first full receipt database 332A. When the company code is the code of the developer operating the shopping mall B, the processor 31 selects the second full receipt database 332B.

[0119] When the processor 31 selects the first full receipt database 332A or the second full receipt database 332B, the process proceeds to ACT 46. As ACT 46, the processor 31 stores the electronic receipt data with the member ID attached or the electronic receipt data without the member ID attached in the first full receipt database 332A or the second full receipt database 332B selected by the process of ACT 45. The processor 31 ends the information processing when receiving the electronic receipt data.

[0120] Fig.12 This is a flowchart showing the extracted parts of the request command reception process executed by the processor 31 of the electronic receipt server 30 based on the data management program, which are different from the first embodiment. Fig.12 The request command is a full receipt request command, and the processing after the judgment in ACT 23 is YES. When the processor 31 judges YES in ACT 23 (the command including the company code and requesting the transmission of the electronic receipt data of the full receipt database 332), it proceeds to ACT 51. The processor 31 obtains the company code from the full receipt request command.

[0121] As explained in the first embodiment, the full ticket demand command is output from the center server 5. That is, in the second embodiment, the full ticket demand command is output from the center server 5A together with the company code identifying the developer of the shopping mall A. The full ticket demand command is output from the center server 5B together with the company code identifying the developer of the shopping mall B.

[0122] The processor 31 that has obtained the enterprise code from the full-invoice request command proceeds to ACT 52. As ACT 52, the processor 31 selects the full-invoice database 332 corresponding to the shopping mall operated by the developer identified by its enterprise code. That is, when the enterprise code is the code of the developer operating the shopping mall A, the processor 31 selects the first full-invoice database 332A. When the enterprise code is the code of the developer operating the shopping mall B, the processor 31 selects the second full-invoice database 332B.

[0123] When the processor 31 selects the first full bill database 332A or the second full bill database 332B, the processor 31 proceeds to ACT 29. As ACT 29, the processor 31 retrieves the selected first full bill database 332A or the second full bill database 332B. Furthermore, as ACT 30, the processor 31 confirms whether the electronic bill data stored in the first full bill database 332A or the second full bill database 332B satisfies the condition data included in the full bill request command. The subsequent processing sequence is the same as that of the first embodiment.

[0124] According to the second embodiment constructed in this way, an electronic receipt server 30 can be provided, which can simply manage the data of receipts issued not only to consumers who are electronic receipt members but also to non-member consumers in multiple stores as tenants corresponding to shopping center A or shopping center B operated by different developers as electronic receipt data.

[0125] In addition, in the second embodiment, although the case where the number of shopping malls is two is illustrated, it is needless to say that even when the number is greater than or equal to three, the same effect can be obtained by dividing the full receipt database 332 according to the number of shopping malls and managing it by the electronic receipt server 30. In addition, when the same developer operates multiple shopping malls, it is known that the same effect can be obtained by dividing the full receipt database 332 according to the number of developers and managing it by the electronic receipt server 30.

[0126] (Third Embodiment)

[0127] Next, the third embodiment will be described. In addition, the overall structure of the data management system in the third embodiment is considered to be the same as Figure 1The overall structure of the data management system in the third embodiment can also be applied to Figure 8 The overall structure of the second embodiment is shown.

[0128] Fig.13 1 is a flowchart showing the main sequence of the main information processing executed by the processor 21 of the processing terminal 2 based on the control program in the third embodiment. Fig.13 In the example of the first embodiment, Figure 4 Common processing steps are assigned the same symbols.

[0129] like Fig.13 As shown, the processor 21 performs the same processing as the first embodiment from ACT1 to ACT4. That is, the processor 21 confirms whether the member ID of the electronic receipt member has been input as ACT4. When the member ID is read by the reader 27, the processor 21 determines YES in ACT4 and proceeds to ACT5. The processor 21 attaches the member ID to the electronic receipt data that has been produced in the process of ACT2 as ACT5. And the processor 21 proceeds to the process of ACT6. In response to this, when it is confirmed that the "No" button BT2 has been touched by the signal from the touch panel 26, the processor 21 determines NO in ACT4 and proceeds to ACT7. The processor 21 attaches the specified member ID to the electronic receipt data that has been produced in the process of ACT2 as ACT7. And the processor 21 proceeds to the process of ACT6.

[0130] The processor 21 controls the second communication interface 25 as ACT 6 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 of the screen SC1 has been touched and the member ID has been read by the reader 27, the electronic receipt data attached with the member ID is sent to the electronic receipt server 3. When the "No" button BT2 of the screen SC1 has been touched, the electronic receipt data attached with the designated member ID is sent to the electronic receipt server 3.

[0131] Here, the designated member ID is a code that has the same number of digits as the member ID issued to the electronic receipt member, but is a combination of numbers, letters, or symbols that are not used as a member ID. For example, if the member ID is 10 digits and there is no member ID consisting of all 9 digits, the designated member code is regarded as "9999999999".

[0132] Fig.14 FIG. 2 is a flowchart showing the main sequence of the receipt data receiving process executed by the processor 31 of the electronic receipt server 30 based on the data management program in the third embodiment. Fig.14 As shown, the processor 31 of the electronic receipt server 30 waits for receiving the electronic receipt data as ACT 51. When the electronic receipt data sent from any processing terminal 2 is received through the second communication interface 35, the processor 31 determines YES as ACT 51 and proceeds to ACT 52. The processor 31 obtains the member ID attached to the electronic receipt data as ACT 52. Furthermore, the processor 31 confirms whether the member ID is the designated member ID as described above as ACT 53.

[0133] If the member ID attached to the electronic receipt data is not the designated member ID, the processor 31 determines NO in ACT 53 and proceeds to ACT 54. As ACT 54, the processor 31 stores the electronic receipt data attached with the member ID not being the designated member ID in the electronic receipt database 331. Thereafter, the processor 31 proceeds to ACT 55.

[0134] In this regard, when the designated member ID is added to the electronic receipt data, the processor 31 determines YES in ACT 53 and skips the processing of ACT 54. In other words, the processor 31 does not store the electronic receipt data to which the designated member ID is added in the electronic receipt database 331. The processor 31 proceeds to ACT 55.

[0135] The processor 31 stores, as ACT 55, the electronic receipt data to which a member ID other than the designated member ID is added or the electronic receipt data to which the designated member ID is added in the all-receipt database 332. The processor 31 thus ends the information processing when receiving the electronic receipt data.

[0136] Obviously, even in the third embodiment configured as above, the same effects as those of the first embodiment can be obtained. In addition, according to the third embodiment, there is an advantage that the format of the electronic receipt data transmitted from the processing terminal 2 to the electronic receipt server 3 can be unified.

[0137] Although the first to third embodiments have been described above as embodiments related to the data management system capable of easily managing the data of receipts issued in a plurality of stores, the embodiments concerned are not limited thereto.

[0138] For example, in the above-mentioned embodiment, the acquisition program P1 is installed in the POS terminal 1, and the processing terminal 2 in which the production program P2 is installed is connected to the POS terminal 1. As another embodiment, the production program P2 and the acquisition program P1 may be installed in the POS terminal 1 together, 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 replaces the function of the processing terminal 2. In this way, since the processing terminal 2 is not required, it is not necessary to consider the location of the processing terminal 2 in each store.

[0139] For example, in the first embodiment, the processor 31 of the electronic ticket server 3 Figure 6 After the result of ACT11 is YES, the processing of ACT12 is executed. Figure 6 After the determination of YES in ACT11, the processing of ACT14 is executed first. Moreover, thereafter, the processor 31 may also execute the processing of ACT12, and execute the processing of ACT13 when the member ID is attached to the electronic receipt data.

[0140] In addition, the member ID may be deleted before saving to the full receipt database 332. Figure 6 When it is determined in ACT 12 that a member ID is attached, the processor 31 saves the electronic receipt data to which the member ID is attached in the electronic receipt database 331 in ACT 13. After that, the processor 31 deletes the member ID from the electronic data to which the member ID is attached, and proceeds to ACT 14. In ACT 14, the processor 31 saves the electronic receipt data to which the member ID is not attached in the full receipt database 332.

[0141] In addition, no Figure 7 By doing so, the format of the electronic receipt data stored in the entire receipt database 332 can be unified.

[0142] For example, in the first embodiment, the processor 31 of the electronic ticket server 3 acts as Figure 7 ACT22 confirms whether the received command is an electronic bill request command, and when it is not an electronic bill request command, confirms whether it is a full bill request command. In this regard, it is also possible to first confirm whether the received command is a full bill request command, and then confirm whether the received command is an electronic bill request command.

[0143] In addition, the processor 31 is illustrated as follows: Figure 7In ACT 32, when a member ID is added to the electronic receipt data, the electronic receipt data is stored in the receipt memory after deleting the member ID as ACT 33 and ACT 34. In this regard, the processor 31 omits the processing of ACT 32 and ACT 33, and stores the electronic receipt data in the receipt memory regardless of whether the member ID is added. Furthermore, when the search of the entire receipt database 332 is completed as ACT 35, the processor 31 may delete the member ID from the electronic receipt data stored in the receipt memory and send it to the center server 5.

[0144] In addition, 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 implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. These embodiments and their variations are all included in the scope of the invention, and are included in the invention described in the scope of the claims and their equivalents.

Claims

1. A data management device connected to a central server managed by a developer of a shopping mall having a plurality of stores through a network, managed by a corporate group different from the developer and used to provide electronic ticket services, characterized in that: include: a receiving unit that receives receipt data from the store, the receipt data being electronic receipt data including information on a transaction that has been settled as a transaction; as well as The control unit, when the ticket data received by the receiving unit includes subject identification information of an electronic ticket member, deletes the subject identification information and stores the ticket data in the first storage unit, and stores the ticket data together with the subject identification information in the second storage unit for the electronic ticket member; and when the subject identification information is not included, stores the ticket data in the first storage unit and does not store it in the second storage unit.

2. The data management device according to claim 1, wherein: The receipt data includes transmission source identification information for identifying a transmission source of the receipt data. The control unit stores the receipt data in the first storage unit according to the transmission source identification information included in the receipt data.

3. The data management device according to claim 2, wherein: The first storage unit is provided according to the transmission source identification information.

4. The data management device according to claim 1, wherein: Also includes: The center server transmission control unit, when receiving a command requesting transmission of the receipt data in the first storage unit from the center server, transmits the receipt data in the first storage unit to the center server as the transmission source of the command.

5. The data management device according to claim 4, wherein: Also includes: When receiving an electronic receipt request command including the subject identification information from the electronic receipt member's information terminal, the information terminal transmission control unit detects receipt data matching the subject identification information from the second storage unit and transmits the receipt data to the information terminal.

6. The data management device according to claim 5, wherein: When receiving a command including data specifying the store and requesting transmission of the receipt data of the first storage unit, the center server transmission control unit transmits the receipt data of the corresponding store in the first storage unit to the center server.

7. The data management device according to claim 2, wherein: Also includes: When receiving a command including the transmission source identification information and requesting transmission of the receipt data in the first storage unit, the transmission control unit transmits the receipt data in the first storage unit that matches the transmission source information.

8. A data management system, characterized in that: include: The data management device according to any one of claims 1 to 7; as well as A processing terminal connected to the data management device via a network, wherein: The processing terminal comprises: The production department produces bill data that has been digitized; an acquiring unit that acquires the subject person identification information; and The sending control unit, when the subject person identification information is obtained by the acquisition unit, attaches the subject person identification information to the ticket data and sends it to the data management device; when the subject person identification information is not obtained, the ticket data is sent to the data management device without attaching the subject person identification information.

9. A storage medium storing a data management program, the data management program causing a computer of a data management device for providing electronic receipt services, which is connected to a central server managed by a developer of a shopping mall having a plurality of stores through a network and managed by a corporate group different from the developer, and has a receiving unit for receiving receipt data obtained by electronicizing a receipt containing information on a transaction that has been settled as a transaction from the store, to implement the following functions: When the ticket data received by the receiving unit includes the subject identification information of the electronic ticket member, the ticket data is stored in the first storage unit after deleting the subject identification information, and the ticket data is stored together with the subject identification information in the second storage unit for the electronic ticket member. When the subject identification information is not included, the ticket data is stored in the first storage unit without being stored in the second storage unit.

Images