CN114564663A - Transaction data matching method, enterprise management system and storage medium - Google Patents
Transaction data matching method, enterprise management system and storage medium Download PDFInfo
- Publication number
- CN114564663A CN114564663A CN202111443670.7A CN202111443670A CN114564663A CN 114564663 A CN114564663 A CN 114564663A CN 202111443670 A CN202111443670 A CN 202111443670A CN 114564663 A CN114564663 A CN 114564663A
- Authority
- CN
- China
- Prior art keywords
- transaction data
- transaction
- day
- current
- data
- 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
- 238000000034 method Methods 0.000 title claims abstract description 44
- 230000004044 response Effects 0.000 claims abstract description 15
- 238000012545 processing Methods 0.000 claims description 33
- 238000004422 calculation algorithm Methods 0.000 claims description 28
- 230000000875 corresponding effect Effects 0.000 abstract 2
- 230000002596 correlated effect Effects 0.000 abstract 1
- 238000007726 management method Methods 0.000 description 39
- 238000010586 diagram Methods 0.000 description 25
- 230000002354 daily effect Effects 0.000 description 17
- 230000008569 process Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000004364 calculation method Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000008676 import Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000006073 displacement reaction Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000009545 invasion Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 230000008521 reorganization Effects 0.000 description 1
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/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—Query processing
- G06F16/90344—Query processing by using string matching techniques
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3827—Use of message hashing
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Finance (AREA)
- Computer Security & Cryptography (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application relates to the technical field of financial transactions and discloses a transaction data matching method, an enterprise management system and a computer-readable storage medium, wherein the transaction data matching method comprises the following steps: acquiring current-day transaction data and historical transaction data of a financial management system; the current-day transaction data is real-time transaction data acquired on the current day of the target transaction, and the historical transaction data is final transaction data of the target transaction day acquired after the target transaction day; generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; in response to the second identification matching the first identification, historical transaction data is associated with the current day transaction data. By the mode, the historical transaction data and the current-day transaction data are accurately matched and correlated, the usability of the current-day transaction data and the historical transaction data can be improved, and further the transaction operation of subsequent services is facilitated.
Description
Technical Field
The present application relates to the field of financial transaction technologies, and in particular, to a transaction data matching method, an enterprise management system, and a computer-readable storage medium.
Background
In daily fund management work of an enterprise, transaction streamline data need to be acquired from a bank-enterprise direct connection interface of a bank, and follow-up business processing is carried out according to the acquired transaction streamline data. The bank-enterprise direct connection interface is divided into a current-day transaction data acquisition interface and a historical transaction data acquisition interface and is used for respectively acquiring current-day real-time transaction data and accurate and complete transaction running data after the bank finishes a day.
At present, the timeliness and the accuracy of transaction data output by a bank-enterprise direct connection interface of a bank are not high, and the repeated processing conditions of transaction business are more, so that the usability of the data processing business of the day needs to keep up with the development of the transaction business volume. With the development of business, the requirements of customers on the convenience and accuracy of transaction data are higher and higher, and the requirements on the association processing of subsequent business according to the daily transaction data are stronger.
Disclosure of Invention
In order to solve the above problems, the present application provides a transaction data matching method, an enterprise management system, and a computer-readable storage medium, which can accurately match and associate historical transaction data with current-day transaction data, and improve the availability of the current-day transaction data.
The technical scheme adopted by the application is as follows: provided is a transaction data matching method, including: acquiring current day transaction data and historical transaction data of a financial management system; the current-day transaction data is real-time transaction data acquired on a target transaction day, and the historical transaction data is finished transaction data of the target transaction day acquired after the target transaction day; generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; in response to the second identification matching the first identification, historical transaction data is associated with the current day transaction data.
Optionally, generating the corresponding first identifier according to the current day transaction data includes: analyzing the current day transaction data to obtain current day transaction key information; generating a first identifier according to the key information of the current day transaction;
generating a corresponding second identifier from the historical transaction data includes: analyzing historical transaction data to obtain historical transaction key information; and generating a second identifier according to the historical transaction key information.
Optionally, the current-day transaction key information and the historical transaction key information at least comprise account numbers, serial numbers, transaction dates, transaction times, payment directions, amounts, sub-account numbers, four-digit years and four-digit serial numbers of corresponding transactions; the four-digit serial number is used for distinguishing two special transaction services with the same repetition of the current-day transaction key information and the historical transaction key information. .
Optionally, the generating the first identifier according to the current-day transaction key information includes: converting the key information of the current-day transaction by using a data algorithm to generate a first identifier; the first identification is the only main key of the current-day transaction data;
generating the second identifier according to the historical transaction key information includes: converting the historical transaction key information by using a data algorithm to generate a second identifier; wherein the second identifier is a unique primary key of the historical transaction data.
Optionally, converting the key information of the current day transaction by using a data algorithm to generate the first identifier comprises: converting the key information of the current-day transaction by using an MD5 information abstract algorithm to generate a first identifier; wherein the first identification comprises a current day transaction MD5 code;
converting the historical transaction key information using a data algorithm to generate a second identifier comprises: converting the historical transaction key information by using an MD5 information summarization algorithm to generate a second identifier; wherein the second identifier comprises a historical transaction MD5 code.
Optionally, in response to the second identifier matching the first identifier, associating the historical transaction data with the current day transaction data comprises: determining that the second identifier matches the first identifier in response to the historical transaction MD5 code completely covering the current day transaction MD5 code; historical transaction data is associated with the current day transaction data.
Optionally, associating the historical transaction data with the current day transaction data comprises: and performing association matching on the historical transaction data and the subsequent transaction operation of the current-day transaction data.
Another technical scheme adopted by the application is as follows: there is provided an enterprise management system, comprising:
the data request terminal is used for respectively sending a current-day transaction data request and a historical transaction data request to a financial management system;
the financial management system is used for acquiring current-day transaction data and historical transaction data sent by the financial management system;
the financial management system generates current-day transaction data according to the current-day transaction data request and generates historical transaction data according to the historical transaction data request; the current day transaction data is real-time transaction data acquired on the current day of the target transaction, and the historical transaction data is finalized transaction data of the target transaction day acquired after the target transaction day.
Optionally, the financial management system comprises:
the data processing system is used for acquiring the current-day transaction data and the historical transaction data sent by the financial management system, generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; wherein responsive to the second identification matching the first identification, the historical transaction data is associated with the current day transaction data;
and the database is used for storing the first identification and the second identification.
Another technical scheme adopted by the application is as follows: there is provided a computer readable storage medium having stored therein program data for implementing the method as described above when executed by a processor.
The transaction data matching method provided by the application comprises the following steps: acquiring current day transaction data and historical transaction data of a financial management system; the current-day transaction data is real-time transaction data acquired on the current day of the target transaction, and the historical transaction data is final transaction data of the target transaction day acquired after the target transaction day; generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; in response to the second identifier matching the first identifier, historical transaction data is associated with the current day transaction data. By the method, on one hand, the current-day transaction data and the historical transaction data are accurately matched, so that the repeated processing and matching error probability of the service can be reduced; on the other hand, historical transaction data is associated with the current day transaction data, so that the usability and convenience of the transaction data can be improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts. Wherein:
FIG. 1 is a schematic flow chart diagram illustrating an embodiment of a transaction data matching method provided herein;
FIG. 2 is a schematic flow chart diagram illustrating one embodiment of obtaining current day transaction data and historical transaction data;
FIG. 3 is a schematic flow chart diagram illustrating one embodiment of step 12 of the transaction data matching method of the present application;
FIG. 4 is a schematic diagram of an embodiment of a key information table for a current day transaction;
FIG. 5 is a schematic diagram illustrating an embodiment of a key information table for historical transactions in the present application;
FIG. 6 is a schematic flow chart diagram illustrating one embodiment of step 13 of the transaction data matching method of the present application;
FIG. 7 is a schematic view of an embodiment of a current meter for a current day transaction MD5 in the present application;
FIG. 8 is a schematic diagram illustrating one embodiment of a pipelined MD5 for historical transactions in the present application;
FIG. 9 is a block diagram illustrating an embodiment of an enterprise management system provided herein;
FIG. 10 is a schematic diagram of an embodiment of a financial management system in an enterprise management system;
FIG. 11 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures associated with the present application are shown in the drawings, not all of them. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first", "second", etc. in this application are used to distinguish between different objects and not to describe a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In addition, although the terms "first", "second", etc. are used herein several times to describe various elements (or various thresholds or various applications or various instructions or various operations), etc., these elements (or thresholds or applications or instructions or operations) should not be limited by these terms. These terms are only used to distinguish one element (or threshold or application or instruction or operation) from another element (or threshold or application or instruction or operation). For example, a first operation may be referred to as a second operation, and a second operation may be referred to as a first operation, without departing from the scope of the invention, the first operation and the second operation being operations, except that they are not the same operation.
The steps in the embodiment of the present invention are not necessarily processed according to the described step sequence, and may be optionally rearranged in a random manner, or steps in the embodiment may be deleted, or steps in the embodiment may be added according to requirements.
The term "and/or" in embodiments of the present invention refers to any and all possible combinations including one or more of the associated listed items. It is also to be noted that: when used in this specification, the term "comprises/comprising" specifies the presence of stated features, integers, steps, operations, elements and/or components but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements and/or components and/or groups thereof.
With the development of computer technology, more and more technologies (big data, distributed, Blockchain, artificial intelligence, etc.) are applied to the financial field, and the traditional financial industry is gradually changing to financial technology (Fintech), but higher requirements are also put forward on the technologies due to the requirements of security and real-time performance of the financial industry. At present, when data transaction is carried out, data matching errors or repeated data are caused due to network factors, technical factors, customer factors or compensation means adopted for ensuring distributed consistency of data, and the like, so that normal operation of the data transaction is seriously influenced, but the existing data matching mode carried out aiming at the data matching errors has various limitations (such as poor timeliness of data, need of a complex operation mode or invasion on service codes, and the like), and low availability is caused.
Therefore, the transaction data matching method applied to the enterprise management system can improve the accuracy of data matching and the usability of transaction data.
Referring to fig. 1, fig. 1 is a schematic flow chart of an embodiment of a transaction data matching method provided in the present application, the method including:
step 11: acquiring current day transaction data and historical transaction data of a financial management system; the current-day transaction data is real-time transaction data acquired on the current day of the target transaction, and the historical transaction data is finished transaction data of the target transaction day acquired after the target transaction day.
Specifically, a transaction data request end sends a request for acquiring the current-day transaction data and a request for acquiring the historical transaction data to a transaction data front-end processor respectively, and the transaction data front-end processor sends a current-day transaction message and a historical transaction message to a current-day transaction data acquisition interface respectively according to the received corresponding transaction data request content. The daily transaction message and the historical transaction message respectively contain daily transaction data and historical transaction data.
The transaction data requesting terminal may be a mobile terminal capable of sending corresponding request information to the transaction data front-end processor, such as a mobile phone, a smart phone, a notebook computer, a Personal Digital Assistant (PDA), a tablet computer (PAD), and the like, or a fixed terminal capable of sending corresponding request information to the transaction data front-end processor, such as a Digital broadcast transmitter, a Digital TV, a desktop computer, and the like. The transaction data front-end processor can be a national bank, a private bank or other platform or mechanism which can generate and record transaction data, such as a Payment treasure, a Pidoku, a palm mall and the like.
Optionally, the daily transaction data acquisition interface and the historical transaction data acquisition interface are device integration interfaces or data import interfaces corresponding to the method in the application. In one embodiment, the daily transaction data and the historical transaction data are obtained by importing the daily transaction data and the historical transaction data through a bank and enterprise direct connection interface.
Referring to fig. 2, fig. 2 is a schematic flow chart of an embodiment of obtaining the current-day transaction data and the historical transaction data, and step 11 specifically includes:
step 111: and acquiring the real-time transaction data of the day at any time of the day to obtain the transaction data of the day.
Specifically, the current day transaction data is real-time transaction data acquired on the current day of the target transaction. The real-time transaction data acquired on the current day may include all transaction data on the current day before the acquisition time. For example, at least one of all completed transaction data, incomplete transaction data, cancelled transaction data, or repeated transaction data.
In an embodiment, the transaction data request terminal may set a target time point, and send a request for obtaining the current-day transaction data to the transaction data front-end processor at the target time point every day, so that the current-day transaction data collection interface can receive the current-day transaction data. For example, the target time point may be set to 10:00, 11:00, or 13:00, etc. on the day. In another embodiment, the transaction data requesting end may also send a request for obtaining the transaction data of the current day to the transaction data front-end processor at a certain time point of the current day according to its own needs without setting a target time point.
Step 112: after the bank finishes the day and at any time of the next day, all transaction data of the previous day are acquired to obtain historical transaction data.
Specifically, the historical transaction data is finalized transaction data of a target transaction day acquired after the target transaction day. The transaction data of the target transaction day may include all completed transaction data, incomplete transaction data, cancelled transaction data and repeated transaction data of the target transaction day, or may include only all completed transaction data of the previous day.
For example, in practical applications, some real-time transaction data of the target transaction date is not the complete transaction data of the target transaction date, or some transaction data may be invalidated for special reasons, such as the customer repeatedly deposits a deposit in a bank or cancels the deposit that has generated a single number, thereby resulting in the invalidation of the transaction flow. At this time, the transaction data can be recorded in the current-day real-time transaction data, but the transaction record can not be recorded in the historical transaction data, and the historical transaction data is the date and end data of each day of the bank and covers the complete current-day transaction data. The type of data specifically included in the current date transaction data and the historical transaction data may be determined according to the actual situation, and is not specifically limited herein.
In an embodiment, the transaction data requesting end may also set a target time point, and send a request for obtaining the historical transaction data to the transaction data front-end processor at the target time point of the next day, or may send a request for obtaining the historical transaction data to the transaction data front-end processor at a certain time point of the next day according to self-requirement without setting the target time point.
Step 12: and generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data.
Specifically, by analyzing the current-day transaction data and the historical transaction data, extracting key information in the current-day transaction data and the historical transaction data, recombining and associating the key information according to a preset rule and an algorithm, and generating a unique main key of corresponding transaction data.
Referring to fig. 3, fig. 3 is a schematic flow chart of an embodiment of step 12 in the transaction data matching method of the present application, where step 12 specifically includes:
step 121: the current day transaction data is analyzed to obtain current day transaction key information, and the historical transaction data is analyzed to obtain historical transaction key information.
Specifically, after the daily transaction data acquisition interface receives the daily transaction message, the daily transaction data in the daily transaction message is analyzed through a data processing system, and the daily transaction key information is extracted. And when the historical transaction data acquisition interface receives the historical transaction message, analyzing the historical transaction data in the historical transaction message through the data processing system, and extracting the historical transaction key information.
The current transaction key information and the historical transaction key information are transaction identification codes formed by various transaction data, namely, TRANSID values. The transaction identification code at least comprises a transaction account number, a transaction serial number, a transaction date, a transaction time, a payment direction, an amount, a subaccount, a four-digit year and a four-digit serial number corresponding to the transaction data. The four-digit serial number is used for distinguishing two transactions with the same key information, and the key information repetition condition only occurs aiming at special bank services. And distinguishing two transactions with consistent key information according to the serial numbers 0001 and 0002. When the key information is not repeated, the four bits are all numbered 0001.
Optionally, the data processing system is a system capable of performing data parsing, and includes an Enterprise Resource Planning (ERP) system, a Customer Relationship Management (CRM) system, a database system, or other type of data processing system, where a specific network device may be a server, such as an application server or other type of server.
In an embodiment, the transaction identifier of the current day composed of the transaction key information of the current day may be made into a form of a transaction key information table of the current day and a history transaction identifier composed of the history transaction key information may be made into a form of a history transaction key information table, so as to facilitate subsequent key information reorganization and association operations.
As shown in fig. 4, fig. 4 is a schematic diagram of an embodiment of a key information table for a current day transaction in the present application. Specifically, the current-day transaction key information table includes the current-day transaction account A, B, C, D, an 8-digit transaction serial number, a transaction date of 10 months and 10 days, and a transaction time of 11:00 to 16: 00, the direction of the balance is used for payroll 1 and 2 and customer 1, 2 and 3, the amount, the sub-accounts A1, A2, B1, C1, C2 and D1, the four-digit number is 0001 in 2019 of four-digit years. Wherein, transaction time 11:00 and 13:00 are payroll 1 and 2, sub-account numbers a1 and a2, transaction time 14: 00 and 15: 00, respectively corresponding to the customer 2 in the charging and discharging direction and the sub-account number C1.
Fig. 5 is a schematic diagram of an embodiment of a historical transaction key information table in the present application. Specifically, the historical transaction key information table includes the current transaction account A, B, C, D, 8-digit transaction serial number, transaction date 10 month 10 day, transaction time 11:00 to 17:00, the direction of the balance is used for payroll 1 and 2 and customer 1, 2 and 3, the amount, the sub-accounts A1, A2, B1, C1, C2 and D1, the four-digit number is 0001 in 2019 of four-digit years. Wherein, transaction time 11:00 and 13:00 are payroll 1 and 2, sub-account numbers a1 and a2, transaction time 14: 00. 15: the directions of revenue and expenditure for 00 and 17:00 are customer 2, and the sub-accounts are C1 and C2, respectively.
Step 122: and generating a first identifier according to the current-day transaction key information and generating a second identifier according to the historical transaction key information.
Specifically, the daily transaction key information is converted by a data algorithm to generate a first identifier and the historical transaction key information is converted by a data algorithm to generate a second identifier. The first identification is the only main key of the current-day transaction data, and the second identification is the only main key of the historical transaction data.
Optionally, the current day transaction key information is transformed using MD5 message summarization algorithm to generate the first identifier and the historical transaction key information is transformed using MD5 message summarization algorithm to generate the second identifier. Wherein the first identifier comprises a current day transaction MD5 code, and the second identifier comprises a historical transaction MD5 code.
Specifically, the current-day transaction key information and the historical transaction key information are respectively recombined and converted by using an MD5 (Message-digest) information summarization algorithm to obtain a current-day transaction MD5 code (i.e., a current-day transaction MD5 summary) and a historical transaction MD5 code (i.e., a historical transaction MD5 summary).
The current-day transaction MD5 code and the historical transaction MD5 code are both in the form of numeric strings. The MD5 code uniquely corresponds to the key information, but the key information is not exposed, namely, the current-day transaction MD5 code uniquely corresponds to the current-day transaction unique main key, and the historical transaction MD5 code uniquely corresponds to the historical transaction unique main key.
The acquired daily transaction data and historical transaction data may have a timing problem, which is caused by differences of natural time of each transaction data interface, each transaction data request end and each transaction data output end. For example, when the time difference of the same packet arriving at different application terminals is not large, a phenomenon may occur in which the natural time acquired by the packet with a later timing sequence is earlier than the natural time acquired by the packet with an earlier timing sequence. The MD5 information summarization algorithm is used for respectively recombining and converting the current-day transaction key information and the historical transaction key information, so that on one hand, the same MD5 code generated corresponding to the same transaction data can be ensured to be the same, thereby eliminating possible time sequence problems and reducing error probability of transaction data matching, and on the other hand, whether the transaction data are tampered or damaged can be verified, and the transaction data can be conveniently stored and called.
In one embodiment, the data processing system generates MD5 codes from raw data of the current day transaction key information and historical transaction key information, and then stores the raw data along with its MD5 codes in a database. When the transaction data is verified to be tampered or damaged, the MD5 code is called from the database, the MD5 code is converted back to the corresponding transaction data to be compared with the original data stored at the transaction data output end, or the original data stored at the transaction data output end is converted into the corresponding MD5 code to be compared with the called MD5 code in the database, and if the two data are consistent, the two groups of data are considered to be matched, namely the original data are not modified or damaged.
MD5 is a cryptographic hash function, the literal name of which is the fifth version of the message digest algorithm, a hash function widely used in the field of computer security to provide integrity protection for messages. MD5 may generate a 128 bit (16 byte) hash value. In the present embodiment, the MD5 algorithm is only used for example to calculate the current MD5 code, but the calculation is not limited to the MD5 algorithm.
MD5 is a commonly used summarization algorithm (or fingerprint algorithm) and has several important features: (1) inputting any length information, wherein the output length is fixed, so that data management is facilitated, the MD5 can input any length information, and the output of the MD5 is binary data with fixed length of 128 bits (bit); (2) the operation speed is high, and the operations of the MD5 are 32-bit AND, OR, NOT, displacement and equipotential operations, so the operation speed is high, and the CPU time is hardly consumed; (3) irreversibly, the original data cannot be calculated from the hash result of MD5 (except for the charpy dictionary).
In one embodiment, the calculation process of the MD5 digest algorithm may be as follows: firstly, the MD5 respectively makes the input current-day transaction key information and historical transaction key information into two N x 512bit data packets; dividing each 512-bit group into 16 sub-groups, wherein each sub-group is 32-bit original data corresponding to current-day transaction key information or historical transaction key information; the 16 sub-groups are respectively named as M0-M15; and 4 times of operation are carried out on each sub-group, the operation formulas are respectively an FF formula, a GG formula, an HH formula and a II formula, and the final total operation times are N x 16 x 4 (all operations are bit operations), so that the current-day transaction MD5 code corresponding to the current-day transaction key information and the historical transaction MD5 code corresponding to the historical transaction key information are obtained. The current-day transaction MD5 code uniquely corresponds to the current-day transaction unique main key, and the historical transaction MD5 code uniquely corresponds to the historical transaction unique main key.
Optionally, in an embodiment, after the data processing system, before the MD5 message digest algorithm is performed to recombine and convert the current transaction key information and the historical transaction key information, respectively, it is necessary to set various parameter configurations of the data processing system. Optionally, such as setting a global anti-replay policy configuration table, a transaction MD5 flow meter, an ignore check configuration table, and a repeat transaction special processing policy table, etc., and adding these parameters to the jvm level cache for subsequent data call and access performance. The JVM (Java virtual machine) operates the database by using a data persistence framework based on Java programming language, such as Mybatis or Hibernate. For example, in the financial field, it is often necessary to use JVM to access a financial database table, such as an accounting information table, an account opening information table, a financial transaction information table, etc., and in this process, a caching technology is used to meet the concurrency and access speed requirements of financial services.
Step 13: in response to the second identification matching the first identification, historical transaction data is associated with the current day transaction data.
Referring to fig. 6, fig. 6 is a schematic flow chart of an embodiment of step 13 in the transaction data matching method of the present application, where step 13 specifically includes:
step 131: in response to the historical transaction MD5 code completely covering the current day transaction MD5 code, determining that the second identifier matches the first identifier.
Specifically, in response to the historical transaction MD5 code corresponding to the historical transaction unique key completely covering the current-day transaction MD5 code corresponding to the current-day transaction unique key, the data processing system determines that the first identifier corresponding to the current-day transaction data matches the second identifier corresponding to the historical transaction data.
Step 132: the historical transaction data is associated with the current day transaction data.
Specifically, the historical transaction data is associated and matched with the subsequent transaction operation of the current day transaction data.
In one embodiment, the current-day transaction data acquired on the current day of the target transaction date is used for generating a first identifier, then the current-day transaction MD5 code corresponding to the first identifier is inserted into a current-day summary data table, the historical transaction data acquired after the target transaction date is used for generating a second identifier, then the historical transaction MD5 code corresponding to the second identifier is inserted into a historical summary data table, and if the historical summary data table completely covers the current-day transaction data table, the current-day transaction data is determined to be matched with the historical transaction data. Since the current summary is preferably calculated by the MD5 algorithm in this embodiment, the summary data table of the current day may be a current day transaction MD5 flow meter, and the history summary data table may be a history transaction MD5 flow meter. Namely, the current abstract and the corresponding time range are used as the unique constraint and inserted into the abstract data table in the database, and then the target abstract data table is obtained.
As shown in fig. 7, fig. 7 is a schematic diagram of an embodiment of an MD5 flow meter for daily transaction in the present application. As shown in fig. 8, fig. 8 is a schematic diagram of an embodiment of a historical transaction MD5 pipeline in the present application. Specifically, the current-day transaction MD5 and the historical transaction MD5 include chronological MD5 codes. Wherein each MD5 code represents a transaction data, i.e. a business operation, of the current day. Each business operation is associated according to a unique primary key or unique identifier. For example, a first business operation may generate a first credential and first transaction data, generate its corresponding first MD5 code (i.e., a first unique primary key or first identifier) based on the first transaction data, a second business operation may generate a second credential and second transaction data, and generate its corresponding second MD5 code (i.e., a second unique primary key or second identifier) based on the second transaction data.
According to the current day transaction MD5 flow chart and/or the historical transaction MD5 flow chart, whether primary key uniqueness conflicts and data matching exist in current day transaction data and/or historical transaction data can be detected.
Taking whether the current transaction data or the historical transaction data have primary key uniqueness conflicts as an example:
whether repeated MD5 codes exist in a current-day transaction MD5 flow chart or a historical transaction MD5 flow chart in a corresponding time period or not is detected respectively in a primary key constraint mode (namely if two identical MD5 codes exist, the two identical MD5 codes are determined to be the repeated MD5 codes), and then the primary key uniqueness conflict of the corresponding transaction MD5 flow chart is determined.
Taking whether the current day transaction data and the historical transaction data are matched as an example:
and detecting whether the historical transaction MD5 flow table in the corresponding time period completely covers the current-day transaction MD5 flow meter by using a primary key constraint mode (namely, if all MD5 codes in the current-day transaction MD5 flow meter exist in the historical transaction MD5 flow meter), and determining that the current-day transaction data is matched with the historical transaction data.
Alternatively, when the current day transaction data and the historical transaction data are matched, the current day transaction MD5 flow chart and the historical transaction MD5 flow chart can be integrated together and placed in a database for storage and calling.
Optionally, because the unique key information of the same transaction data is the same, the current-day transaction data and the historical transaction data can be automatically matched, and further the subsequent business processing of the transaction data can be automatically associated according to the same unique key information, so that a user does not need to repeatedly process the same or similar business operation, the availability and the usability of the current-day transaction data can be effectively improved, and the repeated or similar work is greatly reduced.
Unlike the prior art, embodiments in the present application provide transaction data matching including: acquiring current-day transaction data and historical transaction data of a financial management system; the current-day transaction data is real-time transaction data acquired on a target transaction day, and the historical transaction data is finished transaction data of the target transaction day acquired after the target transaction day; generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; in response to the second identification matching the first identification, historical transaction data is associated with the current day transaction data. By the method, the corresponding first identification and the second identification are generated by using the current-day transaction key information and the historical transaction key information in the current-day transaction data and the historical transaction data. On one hand, the business information corresponding to the current-day transaction data can be accurately matched with the business information corresponding to the historical transaction data, so that the probability of repeated processing of the business and data matching errors is reduced, and the usability of the current-day transaction data is improved; on the other hand, the current-day transaction data and the subsequent business information can be associated, so that the repeated work is greatly reduced on the premise of accurate and stable bank data, and the timeliness and usability of business processing are met.
In another embodiment, the present application further provides an enterprise management system 100. Referring to fig. 9, fig. 9 is a schematic structural diagram of an embodiment of an enterprise management system provided by the present application, where the enterprise management system 100 includes a data request terminal 110 and a financial management system 120 connected to the data request terminal 110.
Specifically, the data request terminal 110 is configured to send a current-day transaction data request and a historical transaction data request to a financial management system, respectively. The financial management system machine can be a nationally owned bank, a private bank or other platforms or mechanisms which can generate and record transaction data, such as a Payment treasure, a sharing treasure, a handheld mall and the like. The financial management system 120 is used to obtain the current day transaction data and the historical transaction data sent by the financial management system.
The financial management system generates current-day transaction data according to the current-day transaction data request and generates historical transaction data according to the historical transaction data request. In one embodiment, the financial management system sends the current day transaction data and the historical transaction data to the financial management system 120 by way of a bank-to-enterprise peering interface import. The current-day transaction data is real-time transaction data acquired on the current day of the target transaction, and the historical transaction data is finished transaction data of the target transaction day acquired after the target transaction day.
Referring to fig. 10, fig. 10 is a schematic structural diagram of an embodiment of the financial management system in the enterprise management system, where the financial management system 120 includes a data processing system 121 and a database 122 connected to the data processing system 121.
Specifically, the data processing system 121 is used to obtain the current day transaction data and the historical transaction data sent by the financial management system. The database 122 is used to store the first identification and the second identification generated by the data processing system 121.
Optionally, in an embodiment, the data processing system 121 is configured to execute the program data to implement the following method: acquiring current day transaction data and historical transaction data of a financial management system; the current-day transaction data is real-time transaction data acquired on a target transaction day, and the historical transaction data is finished transaction data of the target transaction day acquired after the target transaction day; generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; in response to the second identification matching the first identification, historical transaction data is associated with the current day transaction data.
Referring to fig. 11, fig. 11 is a schematic structural diagram of an embodiment of a computer-readable storage medium 130 provided by the present application, in which program instructions 131 capable of implementing all the methods described above are stored.
The unit in which the functional units in the embodiments of the present application are integrated may be stored in the computer-readable storage medium 130 if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, and the computer-readable storage medium 130 includes several instructions in a program instruction 131, so as to enable a computer device (which may be a personal computer, a system server, or a network device, etc.), an electronic device (such as MP3, MP4, etc., and may also be a mobile terminal such as a mobile phone, a tablet computer, a wearable device, etc., or a desktop computer, etc.), or a processor (processor) to execute all or part of the steps of the method of the embodiments of the present application.
Optionally, in an embodiment, the program instructions 131, when executed by the processor, are configured to implement the following method: acquiring current day transaction data and historical transaction data of a financial management system; the current-day transaction data is real-time transaction data acquired on a target transaction day, and the historical transaction data is finished transaction data of the target transaction day acquired after the target transaction day; generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; in response to the second identification matching the first identification, historical transaction data is associated with the current day transaction data.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-readable storage media 130 (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It is to be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by the computer-readable storage medium 130. These computer-readable storage media 130 may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the program instructions 131, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer-readable storage media 130 may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the program instructions 131 stored in the computer-readable storage media 130 produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer-readable storage media 130 may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the program instructions 131 executed on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one embodiment, these programmable data processing devices include a processor and memory thereon. The processor may also be referred to as a CPU (Central Processing Unit). The processor may be an electronic chip having signal processing capabilities. The processor may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory may be a memory stick, TF card, etc. that stores and retrieves information based on the location specified by the processor. The memory is classified into a main memory (internal memory) and an auxiliary memory (external memory) according to the purpose, and also into an external memory and an internal memory. The external memory is usually a magnetic medium, an optical disk, or the like, and can store information for a long period of time. The memory refers to a storage component on the main board, which is used for storing data and programs currently being executed, but is only used for temporarily storing the programs and the data, and the data is lost when the power is turned off or the power is cut off.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described embodiment of the enterprise management system 100 is only illustrative, for example, the acquisition manner of the daily transaction data and the historical transaction data, the algorithm and the calculation manner selected by the first identifier and the second identifier are only one set, and there may be another division manner in the actual implementation, for example, the daily transaction key information and the historical transaction key information may be combined or may be set in another system, or some features may be omitted or not executed.
In addition, functional units (such as the data request terminal 110, the financial management system 120, the data processing system 121, and the like) in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made according to the content of the present specification and the accompanying drawings, or which are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A transaction data matching method is applied to an enterprise management system, and comprises the following steps:
acquiring current day transaction data and historical transaction data of a financial management system; wherein the current day transaction data is real-time transaction data acquired on a target transaction day, and the historical transaction data is finalized transaction data of the target transaction day acquired after the target transaction day;
generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data;
in response to the second identification matching the first identification, associating the historical transactional data with the current day transactional data.
2. The transaction data matching method of claim 1,
the generating of the corresponding first identifier according to the current-day transaction data comprises:
analyzing the current day transaction data to obtain current day transaction key information;
generating the first identification according to the current-day transaction key information;
the generating a corresponding second identifier according to the historical transaction data includes:
analyzing the historical transaction data to obtain historical transaction key information;
and generating the second identifier according to the historical transaction key information.
3. The transaction data matching method of claim 2,
the current-day transaction key information and the historical transaction key information at least comprise account numbers, serial numbers, transaction dates, transaction time, payment directions, amounts, sub-account numbers, four-digit years and four-digit serial numbers of corresponding transactions;
the four-digit serial number is used for distinguishing two special transaction services with the same repetition of the current-day transaction key information and the historical transaction key information.
4. The transaction data matching method according to claim 2,
the generating the first identifier according to the current-day transaction key information comprises:
converting the key information of the current-day transaction by using a data algorithm to generate the first identifier;
wherein the first identification is the only main key of the current-day transaction data;
the generating the second identifier according to the historical transaction key information comprises:
converting the historical transaction key information by using the data algorithm to generate the second identifier;
wherein the second identifier is a unique primary key of the historical transaction data.
5. The transaction data matching method of claim 4,
the converting the current-day transaction key information using a data algorithm to generate the first identifier comprises:
converting the key information of the current transaction by using an MD5 information summarization algorithm to generate the first identifier;
wherein the first identification comprises a current day transaction MD5 code;
the converting the historical transaction key information using a data algorithm to generate the second identifier comprises:
converting the historical transaction key information by using an MD5 information summarization algorithm to generate the second identifier;
wherein the second identifier comprises a historical transaction MD5 code.
6. The transaction data matching method of claim 5,
said associating the historical transaction data with the current day transaction data in response to the second identification matching the first identification comprises:
determining that the second identifier matches the first identifier in response to the historical transaction MD5 code fully covering the current-day transaction MD5 code;
associating the historical transaction data with the current day transaction data.
7. The transaction data matching method of claim 6,
said associating said historical transaction data with said current day transaction data comprises:
and performing association matching on the historical transaction data and the subsequent transaction operation of the current-day transaction data.
8. An enterprise management system, comprising:
the data request terminal is used for respectively sending a current-day transaction data request and a historical transaction data request to a financial management system;
the financial management system is used for acquiring current-day transaction data and historical transaction data sent by the financial management system;
the financial management system generates the current-day transaction data according to the current-day transaction data request and generates the historical transaction data according to the historical transaction data request;
the current day transaction data is real-time transaction data acquired on a target transaction day, and the historical transaction data is finalized transaction data of the target transaction day acquired after the target transaction day.
9. The enterprise management system of claim 8,
the financial management system includes:
the data processing system is used for acquiring the current-day transaction data and the historical transaction data sent by the financial management system, generating a corresponding first identifier according to the current-day transaction data, and generating a corresponding second identifier according to the historical transaction data; wherein the historical transaction data is associated with the current day transaction data in response to the second identification matching the first identification;
a database for storing the first identifier and the second identifier.
10. A computer-readable storage medium having stored therein program instructions, the program instructions being executable to implement the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111443670.7A CN114564663A (en) | 2021-11-30 | 2021-11-30 | Transaction data matching method, enterprise management system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111443670.7A CN114564663A (en) | 2021-11-30 | 2021-11-30 | Transaction data matching method, enterprise management system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114564663A true CN114564663A (en) | 2022-05-31 |
Family
ID=81711399
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111443670.7A Pending CN114564663A (en) | 2021-11-30 | 2021-11-30 | Transaction data matching method, enterprise management system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114564663A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110135856A (en) * | 2019-05-16 | 2019-08-16 | 中国银联股份有限公司 | A kind of repeat business risk monitoring method, device and computer readable storage medium |
| CN111767143A (en) * | 2020-06-24 | 2020-10-13 | 中国工商银行股份有限公司 | Transaction data processing method, device, equipment and system |
| CN113609454A (en) * | 2021-08-12 | 2021-11-05 | 中国工商银行股份有限公司 | Abnormal transaction detection method and device |
-
2021
- 2021-11-30 CN CN202111443670.7A patent/CN114564663A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110135856A (en) * | 2019-05-16 | 2019-08-16 | 中国银联股份有限公司 | A kind of repeat business risk monitoring method, device and computer readable storage medium |
| CN111767143A (en) * | 2020-06-24 | 2020-10-13 | 中国工商银行股份有限公司 | Transaction data processing method, device, equipment and system |
| CN113609454A (en) * | 2021-08-12 | 2021-11-05 | 中国工商银行股份有限公司 | Abnormal transaction detection method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200218737A1 (en) | Method, system and program product for matching of transaction records | |
| US11328093B1 (en) | Protecting sensitive data | |
| US20190073646A1 (en) | Consolidated blockchain-based data transfer control method and system | |
| CN112819466B (en) | Digital certificate processing method and device, terminal equipment and storage medium | |
| US11379828B2 (en) | Distributed computing and storage network implementing high integrity, high bandwidth, low latency, secure processing | |
| CN111352902A (en) | Log processing method and device, terminal equipment and storage medium | |
| CN112395300B (en) | Data processing method, device and equipment based on block chain and readable storage medium | |
| CN111309745B (en) | Virtual resource processing method and device, electronic equipment and storage medium | |
| CN109241068B (en) | Method and device for comparing foreground and background data and terminal equipment | |
| US20200364215A1 (en) | Blockchain-based recording and querying operations | |
| CN113420057A (en) | Account checking data processing method and related device | |
| CN112749167A (en) | Method and device for determining broken link data and nonvolatile storage medium | |
| US11222170B2 (en) | Spreadsheet with unit parsing | |
| WO2023091203A1 (en) | Generating cryptographic proof of a series of transactions | |
| CN106156904B (en) | Cross-platform virtual asset tracing method based on eID | |
| CN112667619B (en) | Method, device, terminal equipment and storage medium for auxiliary checking data | |
| CN112884442B (en) | Audit monitoring data acquisition method and system based on audit model | |
| US11838404B2 (en) | Block chain modification correlation | |
| CN114564663A (en) | Transaction data matching method, enterprise management system and storage medium | |
| CN117633835A (en) | Data processing method, device, equipment and storage medium | |
| CN116993523A (en) | Configurable account checking method, device, equipment and storage medium | |
| CN113312410B (en) | Data map construction method, data query method and terminal equipment | |
| US11422993B2 (en) | Duplicate table identification in enterprise database systems for data storage optimization | |
| CN117957528A (en) | Method and system for parallel processing of intelligent contracts in licensed blockchain | |
| CN111367634A (en) | Information processing method, information processing device and terminal equipment |
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 |