Data processing device and data processing method

Abstract

To provide a data processing device that enables construction of set data without using unique information.SOLUTION: The data processing device includes a retrieval unit as a comparison unit, and a set data processing unit. The comparison unit compares first transaction information acquired by a transaction terminal to be used in a transaction at a shop and second transaction information acquired by a terminal other than the transaction terminal with non-unique information to which the first transaction information and the second transaction information correspond and which is not unique individually. The set data processing unit registers the first transaction information as set data in a set database. When the second transaction information does not correspond to the first transaction information as a result of comparison performed by the comparison unit, the set data processing unit registers the second transaction information as set data in the set database. When the second transaction information corresponds to the first transaction information as a result of comparison performed by the comparison unit, the set data processing unit registers, as set data, a difference of the second transaction information from the set data from the first transaction information registered in the set database.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] FIELD OF THE INVENTION An embodiment of the present invention relates to a data processing device. [Background technology]

[0002] Conventionally, an analysis system has been proposed that integrates POS (Point Of Sales) data, which is transaction information from multiple alliance stores in the same or different industries, and analyzes purchasing trends using the integrated transaction information.

[0003] In recent years, services have also begun to be developed that use applications for information processing devices such as personal computers and smartphones to collect information about products purchased by customers in stores and provide analysis results using the collected information.Applications used in such services include household accounting applications that use character recognition to read and automatically input product names and amounts from images of receipts issued in stores, and receipt buyback applications that offer rewards for uploading images of receipts. [Prior art documents] [Patent documents]

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

[0005] By linking transaction information with receipt information obtained from receipt images, it is possible to build aggregate data that can be used in multiple ways. For example, using aggregate data can be expected to broaden the types of analysis and shorten response times to customer inquiries.

[0006] When identifying receipt information, some specific unique information such as member identification information is often used. However, the handling of such information is often required by law to be strict. In particular, there are stricter requirements when providing information to and linking with external systems.

[0007] The problem to be solved by the embodiments of the present invention is to provide a technique that enables the construction of aggregate data without using unique information. [Means for solving the problem]

[0008] In one embodiment, the data processing device includes a comparison unit and a set data processing unit. The comparison unit compares first transaction information acquired from a transaction terminal used for transactions at a store with second transaction information acquired from a source other than the transaction terminal, using non-unique information that corresponds between the first transaction information and the second transaction information but is not unique individually. The set data processing unit registers the first transaction information as set data in the set database. Furthermore, when the comparison by the comparison unit shows that the second transaction information does not correspond to the first transaction information, the set data processing unit registers the second transaction information as set data in the set database. Furthermore, when the comparison by the comparison unit shows that the second transaction information corresponds to the first transaction information, the set data processing unit registers, in the set data, difference data between the second transaction information and set data based on the first transaction information already registered in the set database. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram illustrating a data processing system including a data processing device according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the record contents of a POS information record in the integrated POS information database of the data processing device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of the record contents of a receipt information record in the integrated receipt information database of the data processing device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a receipt issued to a customer when making a transaction at a store. [Figure 5] FIG. 5 is a diagram illustrating the correspondence between POS information and receipt information and inquiry items in the data processing device according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of record contents of a set data record in the set information database of the data processing device according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of record contents of an inquiry history record in an inquiry archive of a data processing device according to an embodiment. [Figure 8] FIG. 8 is a flowchart illustrating a data processing procedure executed by the processor of the data processing device according to the embodiment. [Figure 9] FIG. 9 is a schematic diagram for explaining the linking of POS information and receipt information. [Figure 10] FIG. 10 is a schematic diagram illustrating an inquiry screen on an inquiry terminal. [Figure 11] FIG. 11 is a diagram showing another example of the record contents of a set data record in the set information database. [Figure 12] FIG. 12 is a flowchart showing another example of a data processing procedure. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment will be described with reference to the drawings.

[0011] FIG. 1 is a block diagram illustrating a data processing system including a data processing device 1 according to the embodiment.

[0012] The data processing device 1 is a computer including a processor 2, a main memory 3, an auxiliary storage device 4, and a communication interface 5. The components that make up the data processing device 1 are connected to each other so that signals can be input and output. The data processing device 1 is, for example, a server device connected to a POS server 6 and a receipt server 7 via a communication network NW.

[0013] The processor 2 corresponds to the central part of the data processing device 1. For example, the processor 2 is a CPU (Central Processing Unit), but is not limited to this. The processor 2 may be composed of various circuits. The processor 2 loads a program stored in advance in the main memory 3 or the auxiliary storage device 4 into the main memory 3. The program is a program that causes the processor 2 of the data processing device 1 to realize each unit described below. The processor 2 performs various operations by executing the program loaded into the main memory 3.

[0014] The main memory 3 corresponds to the main storage portion of the data processing device 1. The main memory 3 includes a nonvolatile memory area and a volatile memory area. The main memory 3 stores an OS (Operating System) or programs in the nonvolatile memory area. The main memory 3 uses the volatile memory area as a work area where data is rewritten by the processor 2 as appropriate. For example, the main memory 3 includes a ROM (Read Only Memory) as a nonvolatile memory area. For example, the main memory 3 includes a RAM (Random Access Memory) as a volatile memory area.

[0015] The auxiliary storage device 4 corresponds to the auxiliary storage portion of the data processing device 1. For example, the auxiliary storage device 4 is an EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disc Drive), an SSD (Solid State Drive), etc. The auxiliary storage device 4 stores the above-mentioned programs, data used by the processor 2 when performing various processes, and data generated by the processes in the processor 2.

[0016] The communication interface 5 includes various interfaces that communicatively connect the data processing device 1 to other devices via the communication network NW in accordance with a predetermined communication protocol. As the communication interface 5, for example, a well-known internet connection device can be applied.

[0017] The hardware configuration of the data processing device 1 is not limited to the above configuration, and the data processing device 1 allows the above components to be omitted or changed, and new components to be added, as appropriate.

[0018] The data processing system includes one or more POS servers 6, one or more receipt servers 7, and one or more inquiry terminals 8 as other devices connected via the communication network NW.

[0019] The POS server 6 is a transaction information management server provided for each store or for each company that includes multiple stores. The POS server 6 accumulates transaction information generated by one or more transaction terminals, such as a registration / accounting machine, installed in the store. The transaction information, which will be described in detail later, includes, for example, terminal information identifying each transaction terminal, date and time information indicating the time of purchase (i.e., the time of transaction), the total amount of the transaction, etc. The transaction information can also be referred to as first transaction information acquired from the transaction terminal used for transactions at the store.

[0020] The receipt server 7 is a receipt information management server provided for the provider of the household accounting application or the receipt redemption company. The receipt server 7 stores receipt information entered by customers using the household accounting application or the receipt redemption application. Receipt information, which will be described in detail later, includes, for example, a receipt image, which is an image of the receipt issued to the customer at the time of purchase (i.e., transaction) at the store; receipt read information, such as terminal information, date and time information, and the total amount of the transaction, read from the receipt image using a character recognition function; and member information, which is information about the customer. Receipt information can also be considered second transaction information obtained from a source other than the transaction terminal. The receipt server 7 has a user database that stores information about members who are users of the application. The receipt server 7 may also be an electronic receipt server that stores electronic receipts issued at stores instead of paper receipts. In this case, the receipt information does not include receipt images.

[0021] The inquiry terminal 8 is an information processing terminal such as a personal computer provided for each credit card company and receipt purchasing company. For example, the inquiry terminal 8 of a credit card company can inquire about transaction details to the data processing device 1 in response to an inquiry from a customer about the details of a withdrawal. Furthermore, the inquiry terminal 8 of a receipt purchasing company can inquire about POS information, which is the first transaction information, corresponding to receipt information, which is the second transaction information, to the data processing device 1.

[0022] Here, we will explain each unit configured in the auxiliary storage device 4 of the data processing device 1. The auxiliary storage device 4 stores, for example, an integrated POS information database 41, an integrated receipt information database 42, a collection database 43, and a user database 44. Note that in Figure 1, "database" is abbreviated as "DB."

[0023] The integrated POS information database 41 stores the integrated POS information, which includes the POS information that is the first transaction information collected from each of the POS servers 6.

[0024] The integrated receipt information database 42 stores integrated receipt information. This integrated receipt information includes receipt information, which is second transaction information collected from each receipt server 7.

[0025] The aggregate database 43 stores aggregate data. This aggregate data includes the integrated POS information stored in the integrated POS information database 41 and the integrated receipt information stored in the integrated receipt information database 42. The aggregate database 43 includes an aggregate information database 431 that stores this aggregate data. The aggregate database 43 also stores an inquiry history. This inquiry history is information related to inquiries from the inquiry terminal 8, and can include, for example, at least the user who made the inquiry, the date and time of the inquiry, and the results of the search (whether successful or unsuccessful). The aggregate database 43 includes an inquiry archive 432 that stores this inquiry history.

[0026] The user database 44 stores user information, which is information relating to credit card companies and receipt purchasing companies that make inquiries from the inquiry terminal 8.

[0027] Next, we will explain each unit implemented in the processor 2 of the data processing device 1. The processor 2 implements, for example, a data collection unit 21, a search unit 22, and a collective data processing unit 23. Each unit implemented in the processor 2 can also be referred to as each function. Each unit implemented in the processor 2 can also be referred to as being implemented in a control unit including the processor 2 and main memory 3.

[0028] The data collection unit 21 collects POS information, which is the first transaction information, from the POS server 6 and stores it as integrated POS information in the integrated POS information database 41. The data collection unit 21 also collects receipt information, which is the second transaction information, from the receipt server 7 and stores it as integrated receipt information in the integrated receipt information database 42.

[0029] The search unit 22 searches the integrated POS information database 41 for POS information corresponding to receipt information stored in the integrated receipt information database 42, for example. Specifically, the search unit 22 compares the receipt information stored in the integrated receipt information database 42 with the POS information stored in the integrated POS information database 41 using information that is not specific unique information, such as a membership number, in other words, non-unique information that is not unique individually. Non-unique information includes, for example, store information indicating the store where the transaction took place, date and time information indicating the time of the transaction, terminal information indicating the transaction terminal used for the transaction, the total transaction amount, etc. The search unit 22 can also be described as a comparison unit that compares POS information, which is the first transaction information, with receipt information, which is the second transaction information, using non-unique information.

[0030] The aggregate data processing unit 23 generates aggregate data and stores it in the aggregate information database 431 of the aggregate database 43. That is, the aggregate data processing unit 23 stores the POS information, which is the first transaction information, stored in the integrated POS information database 41, as aggregate data in the aggregate information database 431. The aggregate data processing unit 23 also stores the receipt information, which is the second transaction information, as aggregate data in the aggregate information database 431. However, the information to be stored differs depending on the search result by the search unit 22, that is, the comparison result by the comparison unit. When the search unit 22 does not find POS information corresponding to the receipt information, which is the second transaction information, that is, when the receipt information does not correspond to the POS information, the aggregate data processing unit 23 stores the receipt information as aggregate data in the aggregate information database 431. Furthermore, when the search unit 22 searches for POS information corresponding to the receipt information, which is the second transaction information, that is, when the receipt information corresponds to the POS information, the aggregate data processing unit 23 adds differential data from the receipt information and aggregate data based on the POS information already registered in the aggregate information database 431 to the aggregate data. This differential data will be described later.

[0031] Furthermore, aggregate data processing unit 23 searches aggregate information database 431 in response to an inquiry using specified information designated from inquiry terminal 8 as a search key, and returns specific information in the searched aggregate data to inquiry terminal 8 that made the inquiry. The specific information can be, for example, a receipt image included in the aggregate data or a JAN (Japanese Article Number) code representing the transacted product. Furthermore, aggregate data processing unit 23 stores the inquiry history of the inquiry from inquiry terminal 8 in inquiry archive 432.

[0032] 2 is a diagram illustrating the contents of a POS information record 411 for each piece of POS information stored as integrated POS information in the integrated POS information database 41. The POS information record 411 includes information items such as the store code, transaction date and time, terminal number, sales items, total sales amount, card company name, approval number, receipt number, transaction sequence number, cash register minus mode, and return transaction. The POS information record 411 can also include information about each item traded, such as the JAN code and unit price of the item.

[0033] The store code is store information indicating the store where the transaction took place. This store code is not unique and may overlap between a store and another company's store. The transaction date and time is date and time information indicating the time of the transaction. The terminal number is terminal information indicating the transaction terminal. The sales points are information indicating the number of items traded. The total sales amount is information indicating the total transaction amount. The card company name is information indicating the credit company of the credit card that paid for the transaction. The authorization number is information indicating the number assigned by the credit company upon approval. The card company name and authorization number are information included when the transaction is paid for by credit card and are not necessarily included in all POS information. The receipt number is information indicating the number of the receipt issued for the transaction. The transaction sequence number is information indicating the number assigned to the transaction. The cashier minus mode is information indicating the cancellation of a transaction that was previously registered as a sale. The return transaction is information indicating the POS information related to the return of a product. The cashier minus mode and return transaction are related to special transactions and are not necessarily included in all POS information. It should be noted that for each POS server 6, there may be some information items that are not included in the POS information.

[0034] 3 is a diagram showing an example of the record contents of a receipt information record 421 for each piece of receipt information stored in the integrated receipt information database 42. The receipt information record 421 includes a receipt image 4211, receipt read information 4212, and member information 4213.

[0035] The receipt image 4211 is image information obtained by capturing a photograph of a receipt issued at a store. Fig. 4 is a diagram showing an example of a captured receipt 9.

[0036] The receipt read information 4212 is information printed on the receipt 9 that has been read by character recognition processing from the receipt image 4211. The receipt read information 4212 includes information items such as the company name, store name (store number), store phone number, year, month, day, hour, minute, register number, points, total amount, company code, card approval number, receipt number, transaction number, etc. The receipt information record 421 can also include information about each item traded, such as the product name and unit price.

[0037] The company name is the information obtained by reading the company name 91 on the receipt 9. The store name (store number) is the information obtained by reading the store number 92 on the receipt 9. The store phone number is the information obtained by reading the store phone number 93 on the receipt 9. The year, month, day, hour, minute is the information obtained by reading the year, month, day, hour, minute 94 on the receipt 9. The register number is the information obtained by reading the register number 95 on the receipt 9. The points is the information obtained by reading the points 96 on the receipt 9. The total amount is the information obtained by reading the total amount 97 on the receipt 9. The company code is the information obtained by reading the company code 98 on the receipt 9. The card approval number is the information obtained by reading the card approval number 99 on the receipt 9. The receipt number is the information obtained by reading the receipt number 910 on the receipt 9. The transaction number is the information obtained by reading the transaction number 911 on the receipt 9. The product name is information obtained by reading the product name 912 on the receipt 9. The product unit price is information obtained by reading the product unit price 913 on the receipt 9.

[0038] The member information 4213 is information about the customer who provided the receipt image 4211. This information is generated by the receipt server 7 based on information about the member stored in the user database and added to the receipt information. The member information 4213 includes information items such as the member number, gender, number of people in the household, and annual household income.

[0039] The membership number is a specific unique number assigned to each member of each application corresponding to the receipt server 7, and is identification information that uniquely identifies the customer to whom the receipt 9 is issued. Note that although it is referred to as a number here, it can also be a symbol. The membership number is unique within each application or the company related to that application, but there is a possibility that it may be duplicated between different companies. Gender is information that indicates the gender of the member. Number of people in household is information that indicates the number of people in the household to which the member belongs. Annual household income is information that indicates the annual income of the household to which the member belongs.

[0040] FIG. 5 is a diagram illustrating the correspondence between POS information and receipt information. FIG. 5 also shows inquiry items from the inquiry terminal 8. The store code, transaction date and time, terminal number, sales points, total sales amount, card company name, approval number, receipt number, and transaction sequence number in the POS information correspond to the store name (store number), year / month / day / hour / minute, register number, points, total amount, company code, card approval number, receipt number, and transaction number in the receipt information, respectively. The register minus mode and return transaction in the POS information do not have corresponding entries in the receipt information. Conversely, the receipt image, company name, and store phone number in the receipt information do not have corresponding entries in the POS information. Although not shown in FIG. 5, the JAN code and product unit price in the POS information correspond to the product name and product unit price in the receipt information.

[0041] When the search unit 22 performs a search, it simply uses information items that correspond to each other in the POS information and receipt information. Examples of information that is always present include store information indicating the store where the transaction took place, date and time information indicating the time of the transaction, terminal information indicating the transaction terminal used for the transaction, and the total transaction amount. Store information is the store code in the POS information and the store number in the receipt information. Date and time information is the transaction date and time in the POS information and the year, month, day, hour, and minute in the receipt information. Terminal information is the terminal number in the POS information and the cash register number in the receipt information. The total transaction amount is the total sales amount in the POS information and the total amount in the receipt information.

[0042] When making an inquiry at the credit card company's inquiry terminal 8, the required information is, of course, card company information (card company name / company code) indicating the credit card company and approval number information (approval number / card approval number) indicating the credit card's approval number. Furthermore, the required information also includes store information (store code / store name (store number)), date and time information (transaction date and time / year / month / day / minute), and total transaction amount (total sales amount / total amount). In this case, the information on cash register minus mode and return transactions are optional items in the specified information.

[0043] When making an inquiry at the receipt purchasing company's inquiry terminal 8, required information to be specified includes receipt identification information (receipt number) for identifying the receipt 9, as well as store information (store code / store name (store number)), date and time information (transaction date and time / year / month / day / minute), and terminal information (terminal number / cash register number).Even in this case, the cash register minus mode and return transaction information are optional items in the specified information.

[0044] 6 is a diagram illustrating the record contents of a group data record 4311 for each group data stored in the group information database 431 of the group database 43. The group data record 4311 includes POS and common information 43111, receipt-specific information 43112, member information 43113, and an identification code 43114.

[0045] The POS and common information 43111 includes information items of aggregate data corresponding to the POS information, which is the first transaction information stored in the integrated POS information database 41. That is, the POS and common information 43111 includes information items such as the store code, transaction date and time, terminal number, sales items, total sales amount, card company name, approval number, receipt number, transaction sequence number, cash register minus mode, return transaction, JAN code, and product unit price.

[0046] The receipt-specific information 43112 includes information items from the receipt read information 4212 in the receipt information, which is the second transaction information stored in the integrated receipt information database 42, other than the information items corresponding to the POS information included in the POS and common information 43111. In other words, the receipt-specific information 43112 includes information items such as the receipt image, company name, store name (store number), store phone number, product name, etc. Therefore, it can also be said that the POS and common information 43111 includes information from the receipt read information 4212 that corresponds to the POS information, as shown in FIG.

[0047] The member information 43113 includes information items corresponding to the member information 4213 in the receipt information. That is, the member information 43113 includes information items such as the member number, gender, number of people in the household, and annual household income.

[0048] The receipt-specific information 43112 and member information 43113 can also be said to be differential data between the receipt information (second transaction information) and the aggregate data based on the POS information (first transaction information) that has already been registered in the aggregate information database 431. Therefore, differential data can also be said to be information about information items that do not correspond to each other between the POS information (first transaction information) and the receipt information (second transaction information).

[0049] Identification code 43114 is provided for each information item and indicates whether the information for the corresponding information item is based on POS information (first transaction information), receipt information (second transaction information), or common to both POS information and receipt information. In this example, "1" indicates POS information, "2" indicates receipt information, and "3" indicates common.

[0050] For example, when the data collection unit 21 collects POS information, which is the first transaction information, in the integrated POS information database 41, the aggregate data processing unit 23 registers each piece of information included in the POS information in each information item of the POS and common information 43111 in the aggregate data record 4311. At this time, the identification code of each information item in which information is registered is set to "1".

[0051] Also, for example, when the data collection unit 21 collects receipt information, which is the second transaction information, in the integrated receipt information database 42, the search unit 22 searches the integrated POS information database 41 for POS information corresponding to the receipt information using non-unique information.

[0052] If the search unit 22 does not find POS information corresponding to the receipt information, the POS information is not registered as aggregate data in the aggregate information database 431. Therefore, in this case, the aggregate data processing unit 23 registers the receipt information as aggregate data in each of the information items of the POS and common information 43111, receipt-specific information 43112, and member information 43113 of the aggregate data record 4311. At this time, the identification code of each information item is set to "2." Note that the store name (store number), year / month / day / hour / minute, register number, number of items, total amount, company code, card approval number, receipt number, transaction number, product unit price, etc. in the receipt read information 4212 are registered in the POS and common information 43111 as the store code, transaction date and time, terminal number, sales items, total sales amount, card company name, approval number, receipt number, transaction sequence number, product unit price, etc.

[0053] Furthermore, when the search unit 22 searches for POS information corresponding to the receipt information, the POS information is already registered as aggregate data in the POS and common information 43111 of the aggregate information database 431. Therefore, in this case, the aggregate data processing unit 23 adds each information item of the receipt-specific information 43112 and member information 43113, which are differential data obtained from the receipt information, to the already registered aggregate data. At this time, the identification code of each information item of the receipt-specific information 43112 and member information 43113 to which information has been newly added is set to "2." Furthermore, the identification code of each information item in the POS and common information 43111 that corresponds to the receipt information and POS information already stored therein is set to "3."

[0054] 7 is a diagram illustrating an example of the record contents of each inquiry history record 4321 stored in the inquiry archive 432 of the collective database 43. The inquiry history record 4321 includes information items such as a verification number, purpose, success / failure, user ID, date and time, and expense usage.

[0055] The verification number is identification information for distinguishing each inquiry. The purpose is information indicating the content desired to be returned as a result of the inquiry. Success / failure is information indicating whether specific information corresponding to the purpose was returned to the inquiry terminal 8 that made the inquiry. The user ID is identification information that uniquely identifies the inquiry source. The date and time is information indicating the year, month, day, hour, and minute when the inquiry was made. The expense usage is information indicating whether a fee will be charged for the inquiry from the inquiry terminal 8. For example, if the inquiry source is a receipt purchasing company that provides receipt information, no fee will be charged, but if the inquiry source is a credit card company, a fee will be charged. Various billing policies can be set, such as being able to set whether or not to charge for each individual user, or only charging if specific information is successfully returned in response to the inquiry. The aggregate data processing unit 23 can generate an inquiry history in accordance with this policy and store it in the inquiry archive 432.

[0056] Next, the procedure of data processing by the data processing device 1 will be described. 8 is a flowchart illustrating a data processing procedure executed by the processor 2 of the data processing device 1. The processor 2 loads a program stored in advance in the main memory 3 or the auxiliary storage device 4 into the main memory 3 and executes it, thereby performing operations according to the processing procedure shown in the flowchart.

[0057] In ACT1, the processor 2 determines whether to collect data from the POS server 6 or the receipt server 7. If data collection is configured to occur at regular intervals, such as every minute, the processor 2 makes this determination by determining whether the data collection time has arrived. In this case, the regular intervals for collecting data from the POS server 6 and the receipt server 7 may be different. Alternatively, the regular intervals may be the same, but the collection timing may be different. If additional data is transmitted from the POS server 6 or the receipt server 7 periodically or upon each update, the processor 2 can make this determination by determining whether data transmitted from the POS server 6 or the receipt server 7 has been received via the communication interface 5. If it is determined not to collect data, the result in ACT1 is NO, and the processor 2 proceeds to processing in ACT2. If it is determined to collect data, the result in ACT1 is YES, and the processor 2 proceeds to processing in ACT3.

[0058] In ACT2, the processor 2 determines whether or not an inquiry has been received from the inquiry terminal 8 via the communication interface 5. If it is determined that an inquiry has not been received, the result is NO in ACT2, and the processor 2 proceeds to the processing of ACT1. If it is determined that an inquiry has been received, the result is YES in ACT2, and the processor 2 proceeds to the processing of ACT11.

[0059] In ACT3, the processor 2 collects data. That is, the processor 2 receives POS information, which is the first transaction information, from the POS server 6 via the communication interface 5 and stores it in the integrated POS information database 41. Alternatively, the processor 2 receives receipt information, which is the second transaction information, from the receipt server 7 via the communication interface 5 and stores it in the integrated receipt information database 42. If the system is configured to collect data at regular intervals, the processor 2 will request the POS server 6 or receipt server 7 to send new data via the communication interface 5, and will receive the POS information or receipt information sent in response via the communication interface 5. The processor 2 then proceeds to the processing of ACT4.

[0060] In ACT4, processor 2 determines whether POS information has been collected. If it is determined that POS information has been collected, the result is YES in ACT4, and processor 2 proceeds to processing in ACT5. If it is determined that POS information has not been collected, that is, that receipt information has been collected, the result is NO in ACT4, and processor 2 proceeds to processing in ACT6.

[0061] In ACT5, the processor 2 newly registers the POS information newly accumulated in the integrated POS information database 41 as aggregate data in the aggregate information database 431. In this case, each piece of POS information is registered in the corresponding information item of the POS and common information 43111 of the aggregate data record 4311 in the aggregate information database 431. At this time, the processor 2 sets "1" to the identification code of each information item of the POS and common information 43111. Thereafter, the processor 2 proceeds to the processing of ACT1 above.

[0062] In ACT6, processor 2 searches the integrated POS information database 41 for POS information corresponding to the receipt information newly stored in the integrated receipt information database 42. In this search, processor 2 compares, for example, at least store information, date and time information, terminal information, and amount information, which are non-unique information that is not individually unique. That is, processor 2 searches for POS information corresponding to the receipt information by comparing at least the data in the information items of store name (store number), year / month / day / hour / minute, register number, and total amount in the receipt information with the data in the information items of store code, transaction date and time, terminal number, and total sales amount in each POS information. Then, processor 2 proceeds to the processing of ACT7.

[0063] In ACT7, processor 2 determines whether there is POS information corresponding to the receipt information. If it is determined that there is POS information corresponding to the receipt information, the result is YES in ACT7, and processor 2 proceeds to processing ACT8. If it is determined that there is no POS information corresponding to the receipt information, the result is NO in ACT7, and processor 2 proceeds to processing ACT5 above. In ACT5, processor 2 newly registers the receipt information newly accumulated in the integrated receipt information database 42 as aggregate data in the aggregate information database 431. In this case, each piece of receipt information is stored in the corresponding information items of POS and common information 43111, receipt-specific information 43112, and member information 43113 in the aggregate data record 4311 in the aggregate information database 431. At this time, processor 2 sets "2" to the identification code of each corresponding information item of POS and common information 43111, receipt-specific information 43112, and member information 43113.

[0064] In ACT 8, the processor 2 adds differential data from the aggregate data from the receipt information newly accumulated in the integrated receipt information database 42 to the aggregate information database 431. In other words, in this case, the POS information was stored as aggregate data in ACT 5 in the POS and common information 43111 of the aggregate data record 4311 in the aggregate information database 431. Therefore, the processor 2 extracts information from the receipt information that corresponds to the information items of the receipt-specific information 43112 and member information 43113 of the aggregate data record 4311, which are differential data, and stores this information in the aggregate information database 431. At this time, the processor 2 rewrites the identification code of each corresponding information item in the POS and common information 43111 from "1" to "3." This links the POS information and the receipt information. The processor 2 discards any receipt information that has already been stored in the POS and common information 43111 of the aggregate data record 4311. The processor 2 then proceeds to the processing of ACT 9.

[0065] FIG. 9 is a schematic diagram illustrating the linking of POS information and receipt information. In the figure, multiple pieces of POS information enclosed by dotted lines represent POS information for one customer collected from the POS server 6 of a supermarket company with multiple stores and stored in the integrated POS information database 41. Each piece of POS information is linked by the customer's membership number. Also in the figure, multiple pieces of receipt information enclosed by dashed lines represent receipt information for one customer collected from the receipt server 7 of a receipt purchasing company and stored in the integrated receipt information database 42. Each piece of receipt information is linked by the membership number of the user of the receipt purchasing application, which is not shown in the figure. The membership number shown in the receipt information is the number of the member related to the store and is unrelated to the membership number of the application user.

[0066] For example, when receipt information with a store name (store number) of "0001," a date of "July 1, 2021," a register number of "0001," and a total amount of "¥300" is collected, the processor 2 searches the integrated POS information database 41 for POS information with a store code of "0001," a transaction date and time of "July 1, 2021," a terminal number of "0001," and a total sales amount of "¥300." The processor 2 then adds and records the relevant information from the receipt information in the receipt-specific information 43112 and member information 43113 fields in the aggregate data record 4311 of the aggregate information database 431 corresponding to the retrieved POS information. In this way, as shown by the dashed-dotted lines in FIG. 9, the POS information and receipt information are linked using store information, date and time information, terminal information, and amount information, which are not individually unique.

[0067] In ACT9, processor 2 generates specific information using the stored contents of the aggregate information database 431. For example, processor 2 extracts the JAN code for each product whose receipt information contains only the product name from the correspondence between the JAN code in the POS and common information 43111 and the product name in the receipt-specific information 43112 in the corresponding aggregate data record 4311 in the aggregate information database 431, and uses this as specific information. Processor 2 then proceeds to the processing of ACT10.

[0068] In ACT10, the processor 2 sends the generated specific information to the receipt server 7, which is the source of the receipt information, via the communication interface 5. After that, the processor 2 proceeds to the processing of ACT1 above.

[0069] As indicated by the broken lines in FIG. 8, the processes in ACT9 and ACT10 are optional and may be omitted.

[0070] In ACT11, the processor 2 performs a query in response to the query. That is, the processor 2 searches the set information database 431 using the specified information included in the query from the query terminal 8 as a search key.

[0071] Fig. 10 is a schematic diagram illustrating an inquiry screen 81 on the inquiry terminal 8. The inquiry screen 81 includes an input field 811 for inputting a user ID. Although omitted from the flowchart of Fig. 8, the inquiry terminal 8 communicates with the data processing device 1, logs in using the user ID input in this input field 811, and then makes an inquiry.

[0072] The inquiry screen 81 further includes an inquiry purpose input field 812, multiple condition selection buttons 813, multiple condition input fields 814, an inquiry button 815, and a result display area 816. The inquiry purpose input field 812 is an input field for inputting the inquiry purpose. The condition selection button 813 is a button for specifying search conditions. The condition input field 814 is arranged corresponding to the condition selection button 813 and is an input field for inputting search conditions. The inquiry button 815 is a button for instructing the start of a search. When this inquiry button 815 is operated, the inquiry terminal 8 transmits an inquiry including specified information including multiple search conditions and the inquiry purpose to the data processing device 1. The result display area 816 is an area for displaying specific information corresponding to the inquiry purpose that is returned from the data processing device 1 as the inquiry result for this inquiry.

[0073] FIG. 10 is an example of an inquiry screen 81 on an inquiry terminal 8 of a credit card company. In an inquiry from a credit card company, as explained with reference to FIG. 5, the specified information includes at least card company information, approval number information, store information, date and time information, and the total transaction amount. Of this specified information, the card company information can be identified by the data processing device 1 using the user ID entered at the time of login. The inquiry terminal 8 may automatically select the remaining required information, namely, approval number information, store information, date and time information, and the total transaction amount, as condition selection buttons 813 on the initial screen of the inquiry screen 81. The user of the credit card company can select conditions using the remaining condition selection buttons 813. In this case, as explained with reference to FIG. 5, it may be possible to select only arbitrary specified conditions.

[0074] In ACT12, the processor 2 generates specific information according to the query purpose included in the query based on the information of the aggregate data record 4311 retrieved from the aggregate information database 431. Thereafter, the processor 2 proceeds to the processing of ACT13.

[0075] For example, in response to an inquiry from a credit card company as shown in FIG. 10, the specific information is the receipt image registered in the information item of receipt image 4211 designated for the purpose of the inquiry.

[0076] Furthermore, for example, in response to an inquiry from inquiry terminal 8 of a receipt purchasing company requesting a product's JAN code, processor 2 generates, as identification information, the JAN code registered in the product's JAN code information item in POS and common information 43111. Alternatively, if the inquiry purpose is to analyze the matching user's shopping habits, processor 2 further identifies other aggregate data records 4311 from aggregate information database 431 based on the information in searched aggregate data record 4311, sets a persona based on shopping habits, day of the week behavior, basket unit price, etc., and generates a promotion proposal as identification information. Alternatively, if the inquiry purpose is to analyze the matching user's purchases, processor 2 further identifies other aggregate data records 4311 from aggregate information database 431 based on the information in searched aggregate data record 4311, analyzes weak categories and missing categories from the shopping category results, breaks them down into individual items, and generates specific product proposals as identification information.

[0077] In ACT13, the processor 2 transmits the specific information generated in ACT12 to the inquiry terminal 8 that made the inquiry via the communication interface 5. As a result, a receipt image is displayed in the result display area 816 on the inquiry screen 81 of the inquiry terminal 8 of the credit card company that made the inquiry, as shown in Figure 10, for example. The processor 2 then proceeds to processing in ACT14.

[0078] In ACT14, the processor 2 registers the inquiry history in the inquiry archive 432. Thereafter, the processor 2 proceeds to the processing of ACT1 above. The processor 2 executes a billing program different from the program shown in the flowchart of Fig. 8, thereby determining the amount to be billed to the user who made the inquiry through the inquiry terminal 8 based on the inquiry history registered in the inquiry archive 432, and performing billing processing to the billing destination listed in the user information stored in the user database 44.

[0079] According to the embodiment described above, the data processing device 1 registers the POS information, which is the first transaction information, as aggregate data in the aggregate information database 431. Furthermore, when the data processing device 1 compares the POS information, which is the second transaction information, with the receipt information using non-unique information such as store information, date and time information, terminal information, and amount information, if there is no corresponding POS information, it registers the receipt information as aggregate data in the aggregate information database 431. If there is corresponding POS information, it additionally registers the differential data between the receipt information and the aggregate data based on the POS information already registered in the aggregate information database 431. In this way, it is possible to search for corresponding POS information and receipt information even when using information that is not individually unique and is not required by law. Therefore, the data processing device 1 can link POS information and receipt information and build aggregate data without using any specific unique information such as member identification information.

[0080] In the above embodiment, the data processing device 1 collects each piece of POS information as the first transaction information generated during a transaction at a store, but the collected first transaction information does not have to be each piece of POS information as long as it can acquire information on the information items shown in Fig. 2. For example, the first transaction information may be transaction information or journal information, which is transaction history information generated in the POS server 6 based on multiple pieces of POS information.

[0081] Furthermore, the data processing device 1 does not need to include the integrated POS information database 41 or the integrated receipt information database 42. That is, the data processing device 1 does not need to acquire and store information from the POS server 6 and the receipt server 7. For example, the processor 2 can store aggregate data in the aggregate information database 431 using the following processing procedure. First, the processor 2 queries the POS server 6 or the receipt server 7 for new information and acquires POS information, which is new first transaction information, or receipt information, which is new second transaction information. The processor 2 then extracts non-unique information from the acquired information and queries the receipt server 7 or the POS server 6 for corresponding information using the non-unique information, thereby acquiring the corresponding receipt information or POS information. In this way, some of the functions of the comparison unit may be assigned to the POS server 6 or the receipt server 7. The processor 2 stores the acquired POS information and / or receipt information in the aggregate information database 431 as aggregate data.

[0082] 6, the aggregate data record 4311 of the aggregate information database 431 includes POS and common information 43111, receipt-specific information 43112, and member information 43113, but this storage format is not limited to this. For example, as shown in FIG. 11, the aggregate data record 4311 can be a combination of the information items of the POS information record 411 shown in FIG. 2 and the receipt information record 421 shown in FIG. 3, with an identification code 43114 assigned to each information item.

[0083] 8 is an example, and is not limited to this order. For example, in ACT3, after data is collected in the integrated POS information database 41 or the integrated receipt information database 42, the aggregate data is immediately stored in the aggregate database 43, but the accumulation of aggregate data in the aggregate database 43 may be performed as a batch process, such as once a day.

[0084] Furthermore, any one of the processes may be performed in parallel with another process, and the order of the processes may be changed as long as there is no conflict with the preceding or succeeding process.

[0085] Furthermore, other processes may also be omitted, similar to the processes in ACT 9 and ACT 10. For example, as shown in Fig. 12, the determination process in ACT 4 in the processing procedure in Fig. 8 may be omitted.

[0086] If the processing in ACT4 is omitted in this way, in ACT6, if the data collected in ACT3 is receipt information, which is the second transaction information, the processor 2 performs the processing described above. That is, in ACT6, the processor 2 uses the non-unique information to search the integrated POS information database 41 for POS information corresponding to the receipt information newly stored in the integrated receipt information database 42. If the processor 2 determines in ACT7 that there is no POS information corresponding to the receipt information, in ACT5 the processor 2 newly registers the receipt information newly stored in the integrated receipt information database 42 as aggregate data in the aggregate information database 431. Furthermore, if the processor 2 determines in ACT7 that there is POS information corresponding to the receipt information, in ACT8 the processor 2 adds differential data from the aggregate data from the receipt information newly stored in the integrated receipt information database 42 to the aggregate information database 431 and stores it there.

[0087] Furthermore, if the data collected in ACT 3 is POS information, which is the first transaction information, then in ACT 6 the processor 2 uses the non-unique information to search the integrated receipt information database 42 for receipt information corresponding to the POS information newly stored in the integrated POS information database 41. If it is determined in ACT 7 that there is no receipt information corresponding to the POS information, then in ACT 5 the processor 2 newly registers the POS information newly stored in the integrated POS information database 41 as aggregate data in the aggregate information database 431. If it is determined in ACT 7 that there is receipt information corresponding to the POS information, then in ACT 8 the processor 2 adds differential data from the aggregate data from the POS information newly stored in the integrated POS information database 41 to the aggregate information database 431 and stores it there.

[0088] That is, the processor 2 operates as a first comparison unit that compares the POS information, which is the first transaction information, with the receipt information, which is the second transaction information, using non-unique information that corresponds to the POS information and is not unique individually, and a second comparison unit that conversely compares the receipt information with the POS information using the non-unique information. Furthermore, when the result of the comparison by the first comparison unit shows that the POS information does not correspond to the receipt information, the processor 2 operates as a first data processing unit that registers the POS information as aggregate data in the aggregate information database 431. When the result of the comparison by the second comparison unit shows that the receipt information does not correspond to the POS information, the processor 2 operates as a first data processing unit that registers the receipt information as aggregate data in the aggregate information database 431. The data processing device 1 can operate as a second data processing unit that registers the POS information in the aggregate information database 431 as aggregate data, and a third data processing unit that, when the comparison by the first comparison unit shows that the POS information corresponds to the receipt information, adds to the aggregate data differential data between the receipt information and aggregate data based on the POS information already registered in the aggregate information database 431, and, when the comparison by the second comparison unit shows that the receipt information corresponds to the POS information, adds to the aggregate data differential data between the POS information and aggregate data based on the receipt information already registered in the aggregate information database 431. In this way, corresponding POS information and receipt information can be searched for even if they are not individually unique and are not required by law. Therefore, the data processing device 1 can link POS information and receipt information and build aggregate data without using any specific unique information such as member identification information.

[0089] Furthermore, even if the determination process of ACT4 is eliminated in this way, it goes without saying that the storage format of the set data record 4311 of the set information database 431 may be as shown in FIG.

[0090] The data processing device 1 is generally transferred with the program stored in the main memory 3 or the auxiliary storage device 4. However, this is not limiting, and the program may be transferred without being stored in the main memory 3 or the auxiliary storage device 4. In this case, the transferred program is written to a writable storage device provided in the data processing device 1, separately from the data processing device 1, in response to an operation by a user or the like. The program can be transferred by recording it on a removable recording medium or by communication via a network. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device. Furthermore, the function obtained by installing or downloading the program may be realized in cooperation with an operating system or the like within the device.

[0091] 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 and spirit of the invention, and are also included in the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0092] 1...data processing device, 2...processor, 21...data collection unit, 22...search unit, 23...collective data processing unit, 3...main memory, 4...auxiliary storage device, 41...integrated POS information database, 411...POS information record, 42...integrated receipt information database, 421...receipt information record, 4211...receipt image, 4212...receipt read information, 4213...membership information, 43...collective database, 431...collective information database, 4311...collective data record, 43111...common information, 43112...receipt-specific information, 43113...membership information, 43114...identification code, 432...inquiry archive, 4321...history record, 44...user database, 5...communication interface, 6...POS server, 7...receipt server, 8...inquiry terminal, 81...inquiry screen, 811...input field, 812...inquiry purpose input field, 813...condition selection button, 814...condition input field, 815...inquiry button, 816...results display area, 9...receipt, 91...company name, 92...store number, 93...store telephone number, 94...year, month, day, hour, minute, 95...register number, 96...points, 97...total amount, 98...company code, 99...card approval number, 910...receipt number, 911...transaction number, 912...product name, 913...product unit price, NW...communication network.

Claims

1. a comparison unit that compares first transaction information acquired from a transaction terminal used for transactions at a store with second transaction information acquired from a terminal other than the transaction terminal, using non-unique information that corresponds between the first transaction information and the second transaction information and is not unique individually; a collective data processing unit that stores collective data including the first transaction information and the second transaction information related to the same transaction in a collective database, registering the first transaction information as the aggregate data in the aggregate database; When the comparison result by the comparison unit indicates that the second transaction information does not correspond to the first transaction information, the second transaction information is registered in the aggregate database as the aggregate data; When the comparison result by the comparison unit indicates that the second transaction information corresponds to the first transaction information, difference data between the second transaction information and the collective data based on the first transaction information already registered in the collective database is registered in the collective data. a collective data processing unit; A data processing device comprising:

2. The non-unique information includes store information indicating the store, date and time information indicating the time of the transaction, terminal information indicating the transaction terminal, and amount information indicating the total amount of the transaction, 2. The data processing device according to claim 1, wherein the comparison unit compares the store information, the date and time information, the terminal information, and the amount information in the second transaction information with each of the first transaction information obtained from the transaction terminal of each store.

3. 3. The data processing device according to claim 1, wherein the set data processing unit further receives an inquiry using specific information specified by an inquiry source as a search key, searches the set database, and returns specific information in the searched set data to the inquiry source.

4. 4. The data processing device according to claim 3, wherein said aggregate data processing unit further accumulates an inquiry history in said aggregate database, said inquiry history including at least the source of the inquiry, the inquiry date and time, and the search success or failure result for said inquiry.

5. 5. The data processing device according to claim 1, wherein the differential data includes at least identification information that uniquely identifies a customer who has made the transaction at the store.

6. a collection database that stores collection data including first transaction information acquired from a transaction terminal used for transactions at the store and second transaction information acquired from a terminal other than the transaction terminal and relating to the same transaction as the first transaction information; a first comparison unit that compares the first transaction information with the second transaction information using non-unique information that corresponds to the first transaction information and the second transaction information and is not unique to each other; a second comparison unit that compares the second transaction information with the first transaction information using the non-unique information; a first data processing unit that registers the first transaction information as the aggregate data in the aggregate database when the first transaction information does not correspond to the second transaction information as a result of the comparison by the first comparison unit; a second data processing unit that registers the second transaction information as the aggregate data in the aggregate database when the second transaction information does not correspond to the first transaction information as a result of the comparison by the second comparison unit; a third data processing unit that, when the first comparison unit determines that the first transaction information corresponds to the second transaction information, additionally registers, in the collective data, difference data between the second transaction information and the collective data based on the first transaction information already registered in the collective database, and, when the second comparison unit determines that the second transaction information corresponds to the first transaction information, registers, in the collective data, difference data between the first transaction information and the collective data based on the second transaction information already registered in the collective database; A data processing device comprising:

Images