CN110765114A - Transaction receipt data merging method - Google Patents
Transaction receipt data merging method Download PDFInfo
- Publication number
- CN110765114A CN110765114A CN201910890511.8A CN201910890511A CN110765114A CN 110765114 A CN110765114 A CN 110765114A CN 201910890511 A CN201910890511 A CN 201910890511A CN 110765114 A CN110765114 A CN 110765114A
- Authority
- CN
- China
- Prior art keywords
- receipt
- data
- serial number
- merging
- database
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Human Resources & Organizations (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Quality & Reliability (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Entrepreneurship & Innovation (AREA)
- Technology Law (AREA)
- General Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a method for merging transaction receipt data, which comprises a general compromise model, a hotel model and a catering model, wherein the method comprises the steps of filtering and checking receipt data after the receipt data and the receipt model conditions are obtained, judging whether the flow number of the receipt is an effective flow number, matching a corresponding merging processing judgment condition according to the receipt model and comparing the merging processing judgment condition with corresponding transaction data in a database when the flow number is the effective flow number, judging whether the flow number is consistent, carrying out corresponding merging processing according to the characteristics of different receipts, and setting corresponding merging processing conditions and merging processing modes according to the characteristics of the receipts in the industries for the hotel class receipt without the effective flow number and the catering class receipt with the effective flow number. The invention can uniformly clean the transaction data before the transaction receipt data enters the storage system, and the data analysis is only performed on the cleaned data, thereby reducing the complexity of data processing of the data analysis.
Description
Technical Field
The invention relates to a transaction receipt data merging method, and belongs to the technical field of electronic information.
Background
The transaction receipt data can be used for the merchant or the consumer to perform required data analysis, and the data of each transaction receipt can be acquired from a transaction system by adopting the prior art such as data bridging and the like. However, in the process of generating the off-line transaction data, the receipt may be printed again due to erroneous input, and the catering industry may additionally print a plurality of receipts due to dining, which all result in the collection of a plurality of transaction data generated in the same transaction, so that a plurality of transaction data belonging to the same transaction need to be combined to form one transaction data, and the data collection technology of the existing transaction receipt cannot realize the combination.
Disclosure of Invention
In order to solve the technical problem, the invention provides a transaction receipt data merging method, which is used for merging a plurality of transaction data belonging to the same transaction into one transaction data.
The technical scheme of the invention is as follows: a transaction receipt data merging method of a general compromise model adopts the following modes to perform data processing:
the data of the receipt is acquired and,
the conditions of the receipt model are obtained,
filtering and checking the receipt data according to the receipt model conditions,
discarding the ticket which is not passed by the filtering and checking as a waste ticket, ending the processing flow of the receipt data,
comparing the filtered and verified receipt data with the corresponding transaction data in the database to determine whether the receipt data is consistent with the corresponding transaction data in the database,
when the bill file name and the bill type in the receipt data are consistent with the corresponding transaction data in the database, the receipt data are judged to be the repeated bill and discarded, the processing flow of the receipt data is ended,
when the bill file name and the bill type in the bill data are not consistent with the corresponding transaction data in the database, judging whether the serial number of the bill in the bill model condition is an effective serial number or not,
when the ticket serial number in the ticket model condition is a fixed value or is empty, the ticket serial number in the ticket model condition is judged to be an invalid serial number,
when the ticket serial number in the ticket model condition is the effective serial number, judging whether the ticket serial number in the ticket data is empty or not,
when the serial number of the receipt in the receipt model condition is the effective serial number and the serial number of the receipt in the receipt data is not empty, matching the corresponding merging processing judgment condition according to the receipt model, comparing the matched merging processing judgment condition with the corresponding transaction data in the database, judging whether the matching is consistent,
when the matched merging judgment condition is consistent with the corresponding transaction data in the database, merging the bill data of the receipt and the corresponding data in the database according to the sale time, recording the merged bill data and the corresponding data in the database, ending the processing flow of the receipt data,
when the matched merging processing judgment condition is inconsistent with the corresponding transaction data in the database, the receipt data is directly recorded into the database according to the warehousing rule, the processing flow of the receipt data is finished,
when the flow number of the receipt in the receipt model condition is the effective flow number and the flow number of the receipt in the receipt data is null, the receipt is judged to be a defective receipt, the defective receipt is recorded into a defective bill database or discarded, the processing flow of the receipt data is finished,
when the serial number of the receipt in the receipt model condition is an invalid serial number, acquiring an industry class model of the receipt, judging whether the industry class model in the receipt data is empty or not,
when the industry category model in the receipt data is not empty, executing data merging processing under the corresponding industry category model, ending the processing flow of the receipt data,
and when the industry category model in the receipt data is empty, directly storing the receipt data in a warehouse (logging into a database), and finishing the processing flow of the receipt data.
The manner of matching the corresponding merging processing judgment condition according to the receipt model may be:
when the number of the slip stream is not repeated in days with mac level, the following data are used as the judgment conditions of the merging process: merchant id, entity store id, mac address, coupon serial number, sale date and coupon type;
when the serial number of the receipt is mac-level never-repeat, the following data are taken as the judgment conditions of the merging processing: merchant id, entity store id, mac address, coupon serial number and coupon type;
when the serial number of the receipt is never repeated at the entity store level, the merging processing judgment condition is as follows: merchant id, entity store id, ticket serial number and ticket type;
when the serial number of the receipt is never repeated at the merchant level, the following data are taken as the judgment conditions of the merging processing: merchant id, slip serial number and slip type;
when the number of the slip stream is not repeated in days at the physical store level, the following data are used as the merging processing judgment condition: merchant id, entity store id, coupon serial number, sale date and coupon type;
when the serial number of the receipt is not repeated in days as the merchant level, the following data are taken as the judgment conditions of the merging processing: merchant id, slip serial number, sale date and slip type,
and when the sales date does not exist in the receipt data, taking the data interception date as the sales date.
The manner of executing data merging processing under the corresponding industry category model may be:
for the transaction of hotel class involving the clock room, when there is no coupon serial number and the unit of day, the following data are taken as the merging processing judgment condition: the method comprises the steps that a merchant id, an entity store id, a room number, a name of a person who stays in, stay-in time, departure time and a receipt type are compared, whether a combination processing judgment condition is consistent with corresponding transaction data in a database is judged, when the combination processing judgment condition is consistent with the corresponding transaction data in the database, a repeated bill is judged, the repeated bill is discarded, and the processing flow of receipt data is ended; when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, and ending the processing flow of the receipt data;
for the transaction of the hotel class which does not relate to the clock house, when no receipt serial number exists and the unit is day, the following data are taken as the merging processing judgment condition: the method comprises the steps that a merchant id, an entity store id, a room number, a name of a check-in person, check-in time and a receipt type are compared, whether a combination processing judgment condition is consistent with corresponding transaction data in a database is judged, when the combination processing judgment condition is consistent with the corresponding transaction data in the database, a repeated bill is judged and discarded, and the processing flow of receipt data is ended; and when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, and finishing the processing flow of the receipt data.
A transaction receipt data merging method for a hotel model adopts the following modes to perform data processing:
the data of the receipt is acquired and,
the conditions of the receipt model are obtained,
filtering and checking the receipt data according to the receipt model conditions,
discarding the ticket which is not passed by the filtering and checking as a waste ticket, ending the processing flow of the receipt data,
matching the filtered and verified receipt data with corresponding merging judgment conditions according to the receipt model, comparing the matched merging judgment conditions with corresponding transaction data in the database, judging whether the matching conditions are consistent,
when the merging processing judgment condition is consistent with the corresponding transaction data in the database, the bill is judged to be repeated and discarded, the processing flow of the receipt data is ended,
when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, ending the processing flow of the receipt data,
for a transaction involving a clockhouse, when there is no coupon serial number and the unit is day, the following data is taken as a merging processing determination condition: merchant id, entity store id, room number, name of the person who checked in, time of check in, time of departure from the store, and type of receipt; for transactions that do not involve a clockhouse, when there is no coupon serial number and the unit is day, the following data is taken as the merging processing determination condition: merchant id, brick and mortar store id, room number, check-in name, check-in time, and ticket type.
A transaction receipt data merging method for catering models adopts the following modes to perform data processing:
the data of the receipt is acquired and,
the conditions of the receipt model are obtained,
filtering and checking the receipt data according to the receipt model conditions,
discarding the ticket which is not passed by the filtering and checking as a waste ticket, ending the processing flow of the receipt data,
matching the filtered and verified receipt data with corresponding merging judgment conditions according to the receipt model, comparing the matched merging judgment conditions with corresponding transaction data in the database, judging whether the matching conditions are consistent,
when the merging judgment condition is consistent with the corresponding transaction data in the database, the transaction is judged to be the same transaction, the bill data of the receipt and the corresponding data in the database are merged and recorded into the database, the processing flow of the receipt data is ended,
when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, ending the processing flow of the receipt data,
when the flow number of the receipt is mac level and the flow number of the snack is repeated, the following data are taken as the judgment conditions of the merging processing: merchant id, entity store id, mac address, coupon serial number, sale date and coupon type;
when the coupon serial number is the unit of day of the physical store level and the snack serial number is repeated, the following data are taken as the judgment conditions of the merging processing: merchant id, entity store id, coupon serial number, sale date and coupon type;
when the coupon serial number is the merchant level and the day is the unit, and the dining serial number is repeated, taking the following data as a merging processing judgment condition: merchant id, slip serial number, sale date and slip type,
and when the sales date does not exist in the receipt data, taking the data interception date as the sales date.
The invention has the beneficial effects that: the transaction data can be uniformly cleaned before the transaction receipt data enters the storage system, and the data analysis is only carried out on the cleaned data, so that the complexity of data processing by the data analysis is reduced.
Drawings
FIG. 1 is a flow chart of the present invention relating to a generic compromise model;
FIG. 2 is a flow chart of the present invention relating to a hotel class model;
FIG. 3 is a flow chart of the present invention relating to a restaurant model.
Detailed Description
Description of one, small ticket business terms
1) The merchant: the primary unit comprises one or more physical stores. Such as a shopping mall;
2) the physical store: and the secondary unit comprises one or more acquisition terminals. A store in a shopping mall, for example;
3) mac: the method comprises the steps that a collection terminal or a collection terminal number is obtained, and the collection terminal is a source of transaction data, such as a cash register;
4) number of the slip stream: the number recorded on the receipt, the unique identifier usually used for the same transaction;
5) effective flow number: according to the numbering rule of the serial numbers of the small tickets, whether the bill data is the serial number of the small ticket of a transaction bill (which can be realized only under the condition that the serial number of the small ticket is not repeated for different transactions) can be judged under the same basic numbering unit (for example, the same mac, or the same physical store, or the same merchant), for example, the serial number generated on the day under the 0001 mac is 0001-1000 bills (small tickets), wherein each serial number can represent a transaction, and if the serial numbers of two bills are 0002, the two bills are the bill of the same transaction;
6) invalid flow number: according to the serial number rule of the small ticket, under the same basic numbering unit (for example, the same mac, the same physical store or the same merchant), the serial number of the small ticket which cannot be used for judging whether the bill is the same transaction (for example, when the serial number of each small ticket appears in a fixed value or the serial number on the small ticket is empty) is always 0001, for example, the serial number generated on the day under 0001 mac is always 0001, and the serial number of the small ticket is an invalid serial number; similarly, the serial number generated on the day under 0001 mac is null, and the serial number of the receipt is also an invalid serial number;
7) type of receipt: representing the type of ticket, e.g., bill balance, pre-balance, daily balance, return order, etc.
Second, model classification
According to the characteristics of the receipt in the current practice, the method for combining the data of the receipt is divided into three models:
1) general compromise model: the method is suitable for merging the general transaction tickets;
2) the hotel model comprises: the method is suitable for merging the small transaction tickets of hotel accommodations;
3) catering type models: is suitable for combining catering trade tickets.
Thirdly, the process of the invention
1. Universal compromise model
1) The applicable conditions are as follows:
an active flow number and/or an inactive flow number.
The following numbering rules or patterns may be used, or the transaction statistics or confirmations may be made in terms of the following time units:
(1) the serial number is not repeated in a mac level (by taking mac as a basic numbering unit, tickets generated by different macs are respectively and independently and distinctively numbered), and by taking a day as a unit (a repeating cycle of numbering);
(2) mac grade, serial number never repeats;
(3) the serial number is never repeated at the physical store level (the physical store is used as a basic numbering unit, and tickets generated by different physical stores are respectively and independently numbered;
(4) the serial number is never repeated at a merchant level (with merchants as basic numbering units, tickets generated by different merchants are respectively and independently numbered in a distinguishing way);
(5) the physical store level, the serial number is not repeated by taking the day as a unit;
(6) merchant-level, no repeat of serial numbers in units of days;
2) merging processing judgment conditions under different adaptive conditions:
(1) mac grade, no repetition of serial number in days: merchant id and entity store id and mac address and ticket serial number and sale date (i.e. taking sale time to day unit [ yyyyyMMdd ]) and ticket type, and capture date without sale date as sale date (the same below);
(2) mac level, serial number never repeats: merchant id and entity store id and mac address and ticket serial number and ticket type;
(3) the brick-and-mortar store level, the serial number never repeats: merchant id and entity store id and ticket serial number and ticket type;
(4) merchant level, serial number never repeats: merchant id and slip serial number and type;
(5) brick-and-mortar stores, water flow number not repeated in days: merchant id and entity store id and coupon serial number and sales day and coupon type;
(6) merchant level, serial no duplication in days: merchant id and ticket serial number and sales day and ticket type.
3) Merging process description:
if the time of sale is empty, the intercepted time is padded into the time of sale field.
Comparing the sales time of the receipt data with the sales time in the database, if the sales time of the receipt data is newer than the sales time in the database, replacing the data in the database by using the latest sales time data, not performing replacement processing on the sales time in the database, and reserving the sales time in the database; if the sales time of the receipt data is older than the sales time in the database, the bill file name is added to a historical bill file name field in the database, and the sales time replaces the sales time in the database; if the sales time of the receipt data is the same as the sales time in the database, replacing the data in the database with the latest data of the intercepted time.
4) The flow chart is as follows: see fig. 1.
2. Hotel model
1) The applicable conditions are as follows:
invalid serial number. The method comprises the following steps:
(1) the hotel class relates to the clock room service, and the transaction statistics or confirmation is carried out by taking the day as a unit;
(2) the hotel class relates to non-clockwork services, and transaction statistics or confirmation is carried out by taking days as units.
2) Merging processing judgment conditions under different adaptive conditions:
(1) the clock-point house service related to the hotel class takes the day as a unit: merchant id and entity store id and room number and check-in name and check-in time and departure time and ticket type;
(2) the hotel class relates to non-clockroom services, taking days as units: merchant id and entity store id and room number and check-in name and time of check-in and type of ticket.
3) Merging process description:
and adding the bill file name into a warehouse, and not replacing the data.
When the general compromise model is adopted to identify that the coupon serial number is an invalid serial number and the industry class model is a hotel class model, the follow-up processing can be carried out according to the method.
4) The flow chart is as follows: see fig. 2.
3. Catering model
1) Application conditions
The effective serial numbers are usually never repeated for serial numbers of different transactions, and when the number of meals is increased in the same transaction, the serial numbers are repeated, and the same receipt serial number is adopted in the same transaction. Typically, this type of restaurant does not print an overall invoice.
The following numbering rules or patterns may be used, or the transaction statistics or confirmations may be made in terms of the following time units:
(1) mac grade, taking day as unit, adding the serial number of the meal repeatedly;
(2) at the physical store level, the number of the added meals is repeated by taking days as a unit;
(3) at merchant level, in days, the order of the food serving is repeated.
2) Merging processing judgment conditions under different adaptive conditions:
(1) mac grade, in days, with the addition of a water line number repeat: merchant id and entity store id and mac address and coupon serial number and sales day and coupon type;
(2) at the brick-and-mortar store level, in days, the number of the added food stream is repeated: merchant id and entity store id and coupon serial number and sales day and coupon type;
(3) merchant level, in days, with the addition of a running water number repeat: merchant id and ticket serial number and sales day and ticket type.
3) Merging process description:
and uploading the latest data of the bill and merging the data in the database. And accumulating the total amount, the discount amount and the amount to be received, and splicing the bill details. The billing filename is appended into the library (historical billing field).
4) The flow chart is as follows: see fig. 3.
The technical means disclosed by the invention can be combined arbitrarily to form a plurality of different technical schemes except for special description and the further limitation that one technical means is another technical means.
Claims (5)
1. A transaction receipt data merging method of a general compromise model is characterized by comprising the following steps:
the data of the receipt is acquired and,
the conditions of the receipt model are obtained,
filtering and checking the receipt data according to the receipt model conditions,
discarding the ticket which is not passed by the filtering and checking as a waste ticket, ending the processing flow of the receipt data,
comparing the filtered and verified receipt data with the corresponding transaction data in the database to determine whether the receipt data is consistent with the corresponding transaction data in the database,
when the bill file name and the bill type in the receipt data are consistent with the corresponding transaction data in the database, the receipt data are judged to be the repeated bill and discarded, the processing flow of the receipt data is ended,
when the bill file name and the bill type in the bill data are not consistent with the corresponding transaction data in the database, judging whether the serial number of the bill in the bill model condition is an effective serial number or not,
when the ticket serial number in the ticket model condition is a fixed value or is empty, the ticket serial number in the ticket model condition is judged to be an invalid serial number,
when the ticket serial number in the ticket model condition is the effective serial number, judging whether the ticket serial number in the ticket data is empty or not,
when the serial number of the receipt in the receipt model condition is the effective serial number and the serial number of the receipt in the receipt data is not empty, matching the corresponding merging processing judgment condition according to the receipt model, comparing the matched merging processing judgment condition with the corresponding transaction data in the database, judging whether the matching is consistent,
when the matched merging judgment condition is consistent with the corresponding transaction data in the database, merging the bill data of the receipt and the corresponding data in the database according to the sale time, recording the merged bill data and the corresponding data in the database, ending the processing flow of the receipt data,
when the matched merging processing judgment condition is inconsistent with the corresponding transaction data in the database, the receipt data is directly recorded into the database according to the warehousing rule, the processing flow of the receipt data is finished,
when the flow number of the receipt in the receipt model condition is the effective flow number and the flow number of the receipt in the receipt data is null, the receipt is judged to be a defective receipt, the defective receipt is recorded into a defective bill database or discarded, the processing flow of the receipt data is finished,
when the serial number of the receipt in the receipt model condition is an invalid serial number, acquiring an industry class model of the receipt, judging whether the industry class model in the receipt data is empty or not,
when the industry category model in the receipt data is not empty, executing data merging processing under the corresponding industry category model, ending the processing flow of the receipt data,
and when the industry category model in the receipt data is empty, directly storing the receipt data in a warehouse (logging into a database), and finishing the processing flow of the receipt data.
2. The method of claim 1, wherein matching the respective merge processing decision conditions according to the receipt model is by:
when the number of the slip stream is not repeated in days with mac level, the following data are used as the judgment conditions of the merging process: merchant id, entity store id, mac address, coupon serial number, sale date and coupon type;
when the serial number of the receipt is mac-level never-repeat, the following data are taken as the judgment conditions of the merging processing: merchant id, entity store id, mac address, coupon serial number and coupon type;
when the serial number of the receipt is never repeated at the entity store level, the merging processing judgment condition is as follows: merchant id, entity store id, ticket serial number and ticket type;
when the serial number of the receipt is never repeated at the merchant level, the following data are taken as the judgment conditions of the merging processing: merchant id, slip serial number and slip type;
when the number of the slip stream is not repeated in days at the physical store level, the following data are used as the merging processing judgment condition: merchant id, entity store id, coupon serial number, sale date and coupon type;
when the serial number of the receipt is not repeated in days as the merchant level, the following data are taken as the judgment conditions of the merging processing: merchant id, slip serial number, sale date and slip type,
and when the sales date does not exist in the receipt data, taking the data interception date as the sales date.
3. The method of claim 1, wherein the data merging process under the corresponding industry class model is performed by:
for the transaction of hotel class involving the clock room, when there is no coupon serial number and the unit of day, the following data are taken as the merging processing judgment condition: the method comprises the steps that a merchant id, an entity store id, a room number, a name of a person who stays in, stay-in time, departure time and a receipt type are compared, whether a combination processing judgment condition is consistent with corresponding transaction data in a database is judged, when the combination processing judgment condition is consistent with the corresponding transaction data in the database, a repeated bill is judged, the repeated bill is discarded, and the processing flow of receipt data is ended; when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, and ending the processing flow of the receipt data;
for the transaction of the hotel class which does not relate to the clock house, when no receipt serial number exists and the unit is day, the following data are taken as the merging processing judgment condition: the method comprises the steps that a merchant id, an entity store id, a room number, a name of a check-in person, check-in time and a receipt type are compared, whether a combination processing judgment condition is consistent with corresponding transaction data in a database is judged, when the combination processing judgment condition is consistent with the corresponding transaction data in the database, a repeated bill is judged and discarded, and the processing flow of receipt data is ended; and when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, and finishing the processing flow of the receipt data.
4. A transaction receipt data merging method of a hotel model is characterized by comprising the following steps:
the data of the receipt is acquired and,
the conditions of the receipt model are obtained,
filtering and checking the receipt data according to the receipt model conditions,
discarding the ticket which is not passed by the filtering and checking as a waste ticket, ending the processing flow of the receipt data,
matching the filtered and verified receipt data with corresponding merging judgment conditions according to the receipt model, comparing the matched merging judgment conditions with corresponding transaction data in the database, judging whether the matching conditions are consistent,
when the merging processing judgment condition is consistent with the corresponding transaction data in the database, the bill is judged to be repeated and discarded, the processing flow of the receipt data is ended,
when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, ending the processing flow of the receipt data,
for a transaction involving a clockhouse, when there is no coupon serial number and the unit is day, the following data is taken as a merging processing determination condition: merchant id, entity store id, room number, name of the person who checked in, time of check in, time of departure from the store, and type of receipt; for transactions that do not involve a clockhouse, when there is no coupon serial number and the unit is day, the following data is taken as the merging processing determination condition: merchant id, brick and mortar store id, room number, check-in name, check-in time, and ticket type.
5. A transaction receipt data merging method of a catering model is characterized by comprising the following steps:
the data of the receipt is acquired and,
the conditions of the receipt model are obtained,
filtering and checking the receipt data according to the receipt model conditions,
discarding the ticket which is not passed by the filtering and checking as a waste ticket, ending the processing flow of the receipt data,
matching the filtered and verified receipt data with corresponding merging judgment conditions according to the receipt model, comparing the matched merging judgment conditions with corresponding transaction data in the database, judging whether the matching conditions are consistent,
when the merging judgment condition is consistent with the corresponding transaction data in the database, the transaction is judged to be the same transaction, the bill data of the receipt and the corresponding data in the database are merged and recorded into the database, the processing flow of the receipt data is ended,
when the merging processing judgment condition is inconsistent with the corresponding transaction data in the database, judging the bill to be a new bill, directly storing the receipt data in a warehouse, ending the processing flow of the receipt data,
when the flow number of the receipt is mac level and the flow number of the snack is repeated, the following data are taken as the judgment conditions of the merging processing: merchant id, entity store id, mac address, coupon serial number, sale date and coupon type;
when the coupon serial number is the unit of day of the physical store level and the snack serial number is repeated, the following data are taken as the judgment conditions of the merging processing: merchant id, entity store id, coupon serial number, sale date and coupon type;
when the coupon serial number is the merchant level and the day is the unit, and the dining serial number is repeated, taking the following data as a merging processing judgment condition: merchant id, slip serial number, sale date and slip type,
and when the sales date does not exist in the receipt data, taking the data interception date as the sales date.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910890511.8A CN110765114A (en) | 2019-09-20 | 2019-09-20 | Transaction receipt data merging method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910890511.8A CN110765114A (en) | 2019-09-20 | 2019-09-20 | Transaction receipt data merging method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110765114A true CN110765114A (en) | 2020-02-07 |
Family
ID=69330482
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910890511.8A Pending CN110765114A (en) | 2019-09-20 | 2019-09-20 | Transaction receipt data merging method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110765114A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112561530A (en) * | 2020-12-25 | 2021-03-26 | 民生科技有限责任公司 | Transaction flow processing method and system based on multi-model fusion |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101315692A (en) * | 2007-05-29 | 2008-12-03 | 阿里巴巴集团控股有限公司 | Receipt processing system and method based on internet trade |
| CN103778532A (en) * | 2014-02-21 | 2014-05-07 | 北京购阿购技术服务有限公司 | All-dimensional safety positioning trade information integration system |
| CN104424581A (en) * | 2013-09-09 | 2015-03-18 | 陕西易云网络科技有限公司 | Method for carrying out consumption tracking survey and information spreading by utilizing two-dimensional code |
| CN106934675A (en) * | 2015-12-30 | 2017-07-07 | 航天信息股份有限公司 | A kind of invoice issuing method and system based on sales data collection |
| CN107851276A (en) * | 2015-06-12 | 2018-03-27 | 比尔交易私人有限公司 | The computer implemented more collection of currency invoice, transaction, access and payment systems |
| CN108734528A (en) * | 2018-05-18 | 2018-11-02 | 北京大账房网络科技股份有限公司 | A kind of electronic invoice keeps accounts method automatically |
-
2019
- 2019-09-20 CN CN201910890511.8A patent/CN110765114A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101315692A (en) * | 2007-05-29 | 2008-12-03 | 阿里巴巴集团控股有限公司 | Receipt processing system and method based on internet trade |
| CN104424581A (en) * | 2013-09-09 | 2015-03-18 | 陕西易云网络科技有限公司 | Method for carrying out consumption tracking survey and information spreading by utilizing two-dimensional code |
| CN103778532A (en) * | 2014-02-21 | 2014-05-07 | 北京购阿购技术服务有限公司 | All-dimensional safety positioning trade information integration system |
| CN107851276A (en) * | 2015-06-12 | 2018-03-27 | 比尔交易私人有限公司 | The computer implemented more collection of currency invoice, transaction, access and payment systems |
| CN106934675A (en) * | 2015-12-30 | 2017-07-07 | 航天信息股份有限公司 | A kind of invoice issuing method and system based on sales data collection |
| CN108734528A (en) * | 2018-05-18 | 2018-11-02 | 北京大账房网络科技股份有限公司 | A kind of electronic invoice keeps accounts method automatically |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112561530A (en) * | 2020-12-25 | 2021-03-26 | 民生科技有限责任公司 | Transaction flow processing method and system based on multi-model fusion |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9892389B2 (en) | Method, system, and computer program product for customer-level data verification | |
| US7475807B2 (en) | Method and apparatus for processing checks | |
| JP5166463B2 (en) | Point management system | |
| US7881997B2 (en) | System and method for quantitative peer travel and expense benchmarking analysis | |
| CN104636338B (en) | A kind of data cleansing storage method for the monitoring of value-added tax negative and positive ticket | |
| CN106384273A (en) | Malicious order scalping detection system and method | |
| WO2004044822B1 (en) | Time-of-transaction foreign currency conversion | |
| US20080314977A1 (en) | Method, System, and Computer Program Product for Customer-Level Data Verification | |
| EP3637347B1 (en) | Method and system for processing environmental impact | |
| CN104636337B (en) | A kind of data cleansing storage method for value-added tax | |
| CN110019324B (en) | Method and system for generating taxpayer fund loop | |
| US20090287536A1 (en) | Method for determining consumer purchase behavior | |
| JPH07249075A (en) | Terminal device, method, and medium for customer management | |
| CN106296277A (en) | A kind of consumption rebating management system | |
| CN112184334A (en) | Method, apparatus, device and medium for determining problem users | |
| US20130006820A1 (en) | System and Method of Determining the Quality of Enhanced Transaction Data | |
| CN104636341B (en) | A kind of data cleansing storage method for the several monitoring of value-added tax No.1 | |
| CN110765114A (en) | Transaction receipt data merging method | |
| JP6563734B2 (en) | Sales remittance system and sales remittance method | |
| CN111325540B (en) | POS system based on block chain | |
| CN117094764A (en) | Bank integral processing method and device | |
| US20100257073A1 (en) | Duplicate Payment Prevention | |
| JP6279782B1 (en) | Information processing terminal, information processing method, and program | |
| JP5023251B1 (en) | Checkout server and checkout control method | |
| CN108922083A (en) | Smart shopper payment data treating method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |