Data processing method and device and electronic equipment

Abstract

The embodiment of the invention provides a data processing method and device and electronic equipment, and relates to the technical field of data processing, and the method comprises the steps: carrying out the standardization processing of transaction data in a bookkeeping system, and obtaining a first flow record; combining the first pipeline records with the same data values of the target fields in the plurality of first pipeline records to obtain to-be-checked records corresponding to the first pipeline records; determining a reference pipeline record with the same data value as each target field in the to-be-checked record; analyzing whether the to-be-checked record and the corresponding reference pipeline record have a numerical value difference or not; and when the numerical value difference exists, correcting each first flow record corresponding to the to-be-checked record, and according to the corrected data content, adjusting the data content which is indicated by each first flow record corresponding to the to-be-checked record and stored in the bookkeeping system. According to the scheme, the reliability of the transaction data in the bookkeeping system can be improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data processing method, device and electronic equipment. Background Art

[0002] Normally, users can use corresponding user accounts to conduct securities transactions such as stocks, bonds, options, etc. in different trading systems. During this period, the transaction data generated under the user account will be stored in the trading system and the bookkeeping system respectively.

[0003] Among them, the trading system will count the transaction data of each user account in the fund account linked to the trading system, and different types of data in the transaction data can be stored in different data tables of the trading system; and the transaction data in the trading system is automatically generated when any user conducts securities trading, so the reliability of the transaction data counted in the trading system is relatively high. The bookkeeping system will count the transaction data of all fund accounts under each user account after the securities transaction is completed; since most of the transaction data in the bookkeeping system relies on manual entry, the transaction data recorded in the bookkeeping system has reliability issues.

[0004] The transaction data stored in the trading system and the bookkeeping system should reflect the same transaction situation. Therefore, there is a need to check and correct the transaction data in the bookkeeping system. In the related art, manual review is usually used to check and correct the transaction data in the bookkeeping system based on the transaction data stored in the trading system. However, manual review may still result in errors or omissions, resulting in low reliability of the transaction data in the bookkeeping system.

[0005] Based on this, how to check and correct the transaction data in the bookkeeping system to improve the reliability of the transaction data has become a technical problem that needs to be solved urgently. Summary of the invention

[0006] The purpose of the embodiments of the present application is to provide a data processing method, device and electronic device to check and correct the transaction data stored in the bookkeeping system, thereby improving the reliability of the transaction data in the bookkeeping system. The specific technical solution is as follows:

[0007] In a first aspect, an embodiment of the present application provides a data processing method, the method comprising:

[0008] Standardizing the transaction data stored in the bookkeeping system to obtain a plurality of first flow records containing data values ​​of various specified fields; wherein the various specified fields include various target fields, a first field for representing the transaction quantity, and a second field for representing the amount information, and the various target fields are used to uniquely represent a fund account;

[0009] Merging the first transaction records in which the data values ​​of the target fields are the same among the plurality of first transaction records to obtain the to-be-checked records corresponding to the first transaction records;

[0010] Determine, from the pre-generated multiple reference transaction records, reference transaction records having the same data values ​​as the target fields in the record to be checked as reference transaction records corresponding to the record to be checked; wherein the multiple reference transaction records are transaction records determined based on transaction data of the transaction system and containing the data values ​​of the designated fields;

[0011] Analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtain an analysis result;

[0012] In response to the analysis result indicating the existence of numerical differences, the first transaction records corresponding to the records to be checked are corrected, and according to the data content in the corrected first transaction records, the data content indicated by the first transaction records corresponding to the records to be checked and stored in the bookkeeping system is adjusted.

[0013] In a second aspect, an embodiment of the present application provides a data processing device, the device comprising:

[0014] A first processing module is used to perform standardized processing on the transaction data stored in the bookkeeping system to obtain a plurality of first flow records containing data values ​​of various specified fields; wherein the various specified fields include various target fields, a first field for representing the transaction quantity, and a second field for representing the amount information, and the various target fields are used to uniquely represent a fund account;

[0015] A first merging module, configured to merge the first transaction records in which the data values ​​of the target fields are the same among the plurality of first transaction records, to obtain the to-be-checked records corresponding to the first transaction records;

[0016] A transaction flow determination module, configured to determine, from a plurality of pre-generated reference transaction flow records, reference transaction flow records having the same data values ​​as the target fields in the record to be checked, as reference transaction flow records corresponding to the record to be checked; wherein the plurality of reference transaction flow records are transaction flow records determined based on transaction data of a transaction system and containing the data values ​​of the designated fields;

[0017] A result analysis module is used to analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtain an analysis result;

[0018] A data correction module is used to correct each first transaction record corresponding to the record to be checked in response to the analysis result indicating the existence of a numerical difference, and to adjust the data content indicated by each first transaction record corresponding to the record to be checked and stored in the bookkeeping system according to the data content in the corrected first transaction records.

[0019] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory for storing computer programs; and a processor for implementing any of the data processing methods described above when executing the programs stored in the memory.

[0020] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any of the data processing methods described above is implemented.

[0021] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute any of the above-mentioned data processing methods.

[0022] Beneficial effects of the embodiments of the present application:

[0023] In a data processing method provided in an embodiment of the present application, a transaction record containing data values ​​of various specified fields can be generated in advance based on the transaction data of the transaction system as a benchmark transaction record, wherein the above-mentioned each specified field includes each target field, a first field for representing the transaction quantity and a second field for representing the amount information, and the above-mentioned each target field is used to uniquely represent a fund account.

[0024] In this way, after the transaction data stored in the bookkeeping system is standardized to obtain multiple first flow records containing data values ​​of each specified field, and after merging the first flow records with the same data values ​​of each target field in the multiple first flow records to obtain the to-be-checked records corresponding to the first flow records, a reference flow record with the same data values ​​of each target field in the to-be-checked record can be determined from the above-mentioned multiple predetermined reference flow records as the reference flow record corresponding to the to-be-checked record. Thus, by analyzing whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the to-be-checked record and the corresponding reference flow record, it is determined whether the transaction data in the bookkeeping system needs to be corrected. When the obtained analysis result indicates that there is a numerical difference, the first flow records corresponding to the to-be-checked record are corrected. Then, according to the data content in the corrected first flow records, the data content stored in the bookkeeping system indicated by the first flow records corresponding to the to-be-checked record is adjusted.

[0025] Based on this, in the method provided in the embodiment of the present application, by processing the transaction data stored in the bookkeeping system and the transaction system respectively, the records to be checked and their corresponding reference flow records that are convenient for data comparison are obtained. Then, by comparing the records to be checked and their corresponding reference flow records, it is determined whether there is a need for data correction of the transaction data in the bookkeeping system. Thus, if there is a need, the first flow records corresponding to the records to be checked are corrected, and according to the data content in the corrected first flow records, the corresponding data content stored in the bookkeeping system is adjusted. It can be seen that the method provided in the embodiment of the present application can realize the verification and correction of the transaction data stored in the bookkeeping system, so as to improve the reliability of the transaction data in the bookkeeping system. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0027] Figure 1 A schematic diagram of a flow chart of a first data processing method provided in an embodiment of the present application;

[0028] Figure 2 A schematic diagram of a second data processing method provided in an embodiment of the present application;

[0029] Figure 3A schematic diagram of a third data processing method provided in an embodiment of the present application;

[0030] Figure 4 A schematic diagram of a structure of a specific embodiment provided for the present application;

[0031] Figure 5 A flowchart of a process executed in a difference update module provided in an embodiment of the present application;

[0032] Figure 6 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application;

[0033] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field based on the present application belong to the scope of protection of the present application.

[0035] In order to solve the above-mentioned problem of how to check and correct the transaction data in the bookkeeping system to improve the reliability of the transaction data, the embodiments of the present application provide a data processing method, device and electronic device.

[0036] Among them, the method is applicable to various application scenarios for checking and correcting transaction data. For example, checking and correcting the company's account flow, and for another example, checking and correcting an individual's transaction data. In addition, the method can be applied to various electronic devices such as laptops and desktop computers, hereinafter referred to as electronic devices. Based on this, the embodiment of the present application does not limit the application scenarios and execution subjects of the method.

[0037] A data processing method provided in an embodiment of the present application may include the following steps:

[0038] Standardizing the transaction data stored in the bookkeeping system to obtain a plurality of first flow records containing data values ​​of various specified fields; wherein the various specified fields include various target fields, a first field for representing the transaction quantity, and a second field for representing the amount information, and the various target fields are used to uniquely represent a fund account;

[0039] Merging the first transaction records in which the data values ​​of the target fields are the same among the plurality of first transaction records to obtain the to-be-checked records corresponding to the first transaction records;

[0040] Determine, from the pre-generated multiple reference transaction records, reference transaction records having the same data values ​​as the target fields in the record to be checked as reference transaction records corresponding to the record to be checked; wherein the multiple reference transaction records are transaction records determined based on transaction data of the transaction system and containing the data values ​​of the designated fields;

[0041] Analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtain an analysis result;

[0042] In response to the analysis result indicating the existence of numerical differences, the first transaction records corresponding to the records to be checked are corrected, and according to the data content in the corrected first transaction records, the data content indicated by the first transaction records corresponding to the records to be checked and stored in the bookkeeping system is adjusted.

[0043] It can be seen from the above that in a data processing method provided in an embodiment of the present application, a transaction record containing data values ​​of various specified fields can be generated in advance based on the transaction data of the transaction system as a benchmark transaction record, wherein the above-mentioned each specified field includes each target field, a first field for representing the transaction quantity and a second field for representing the amount information, and the above-mentioned each target field is used to uniquely represent a fund account.

[0044] In this way, after the transaction data stored in the bookkeeping system is standardized to obtain multiple first flow records containing data values ​​of each specified field, and after merging the first flow records with the same data values ​​of each target field in the multiple first flow records to obtain the to-be-checked records corresponding to the first flow records, a reference flow record with the same data values ​​of each target field in the to-be-checked record can be determined from the above-mentioned multiple predetermined reference flow records as the reference flow record corresponding to the to-be-checked record. Thus, by analyzing whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the to-be-checked record and the corresponding reference flow record, it is determined whether the transaction data in the bookkeeping system needs to be corrected. When the obtained analysis result indicates that there is a numerical difference, the first flow records corresponding to the to-be-checked record are corrected. Then, according to the data content in the corrected first flow records, the data content stored in the bookkeeping system indicated by the first flow records corresponding to the to-be-checked record is adjusted.

[0045] Based on this, in the method provided in the embodiment of the present application, by processing the transaction data stored in the bookkeeping system and the transaction system respectively, the records to be checked and their corresponding reference flow records that are convenient for data comparison are obtained. Then, by comparing the records to be checked and their corresponding reference flow records, it is determined whether there is a need for data correction of the transaction data in the bookkeeping system. Thus, if there is a need, the first flow records corresponding to the records to be checked are corrected, and according to the data content in the corrected first flow records, the corresponding data content stored in the bookkeeping system is adjusted. It can be seen that the method provided in the embodiment of the present application can realize the verification and correction of the transaction data stored in the bookkeeping system, so as to improve the reliability of the transaction data in the bookkeeping system.

[0046] A data processing method provided by an embodiment of the present application is described in detail below with reference to the accompanying drawings. Figure 1 A flowchart of a data processing method provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the method may include the following steps:

[0047] S101: Standardize the transaction data stored in the bookkeeping system to obtain a plurality of first transaction records containing data values ​​of various specified fields.

[0048] Each designated field includes each target field, a first field for representing the transaction quantity, and a second field for representing the amount information. Each target field is used to uniquely represent a fund account.

[0049] Typically, the data dimensions and data storage categories of the transaction data stored in the trading system and the bookkeeping system are different. For example, the transaction data in the trading system is recorded in units of fund accounts, while the transaction data in the bookkeeping system is recorded in units of internal company accounts (i.e., the institutions to which the fund accounts belong). For another example, the same transaction data is stored in different types of data tables in the trading system and the bookkeeping system (the same data a is stored in data table 1 in the trading system and data table 2 in the bookkeeping system, and data table 1 and data table 2 correspond to different data table categories), etc. As a result, it is impossible to automatically verify the transaction data in the bookkeeping system based on the transaction data in the trading system.

[0050] Exemplarily, the data tables in which the transaction data in the transaction system A is stored may include: a flow data table, a business type definition table, an account information table, a department information table, a stock information table, a bond information table, an ETF (Exchange Traded Fund, i.e., an exchange-traded open-end index fund) basic information table, etc. Among them, the flow data table: stores the most original transaction flow data, which contains various amounts, quantities, securities codes, business type codes, system accounts used for transactions, and fund accounts used for transactions. Business type definition table: records the Chinese meanings of different business type codes, as well as the funding direction corresponding to the business, and is used to standardize the positive and negative flow amounts. Account information table: used to query the department account corresponding to the system account (the same system account has only one corresponding department account, and one department account may correspond to multiple system accounts, that is, there is a many-to-one correspondence in the account information table). Stock information table, bond information table, ETF basic information table: The system security code in the transaction data is an internal code designed independently within the system. The internal code is stored in the above three types of information tables, and the mapping relationship between the internal code and the external security code and trading market is used for the subsequent association of transaction records in the bookkeeping system with external security codes and trading markets.

[0051] The data tables in which transaction data is stored in the bookkeeping system may include: transaction flow table, buy-back table, pledged repo table, bond forward transaction table, pledged bond table, secondary securities account table, etc. Among them, transaction flow table: stores the most original flow data in the bookkeeping system, which contains amount, quantity, external securities code (or contract number), business type code, secondary securities account number, fund account number, etc. Secondary securities account table: records the department code corresponding to the secondary securities account, which is used for flow records in subsequent related transaction systems. Buy-back table, pledged repo table, bond forward transaction table, pledged bond table: the flow data of the contract type stored in the transaction flow table only records the contract number, and does not record the securities code involved in the contract. The above four types of information tables store the external securities code in the contract, which is used for flow records in subsequent related transaction systems.

[0052] The transaction situations reflected in the different types of data tables stored in the above two systems are consistent. Among them, the data tables in which the transaction data of the above trading system is stored may also include: transaction combination table, fund information table, position information table, etc., and the data tables in which the transaction data of the above bookkeeping system is stored may also include: interest rate swap information table, non-standard product information table, commodity lending contract table, etc., and this embodiment of the application does not make specific limitations on this.

[0053] Therefore, in this application, after obtaining the transaction data stored in the bookkeeping system, the obtained transaction data can be standardized, that is, each data element (data category) of the transaction data in the bookkeeping system is mapped according to a predetermined mapping relationship to generate multiple first flow records containing data values ​​of each specified field, wherein each specified field includes each target field, a first field for representing the transaction quantity, and a second field for representing the amount information, wherein each target field is used to uniquely represent a fund account. In other words, the fund account to which the first flow record belongs can be clearly identified through the above-mentioned target fields.

[0054] It should be noted that the above-mentioned designated fields are fields corresponding to the transaction data contained in both the transaction system and the bookkeeping system, for example, fields used to characterize the transaction type, fund account, department code, market code, securities code, number of transactions, net price amount, interest amount, and handling fee. The above-mentioned designated fields may also include transaction date, asset category or serial number, etc., which are not specifically limited in the embodiments of the present application.

[0055] Each field in the above-mentioned designated fields used to represent a unique fund account is used as each target field, for example, a field used to represent a transaction type, a security code, a market code, a fund account and a department code. By way of example, a first transaction record can be identified through the above-mentioned target fields, which is a transaction record for option trading conducted by fund account a1 with department code xxx1 under market code xx1, and the specific security code is xxxyyy1.

[0056] The field used to represent the transaction quantity in the above-mentioned designated fields is used as the first field, and the fields used to represent the amount information in the above-mentioned designated fields are used as the second fields. That is to say, the number of second fields in the first transaction record can be one or more. When the number of second fields in the first transaction record is more than one, the second field can be a field used to represent the net price amount, a field used to represent the interest amount, or a field used to represent the handling fee.

[0057] S102: merging first transaction records in which data values ​​of respective target fields are the same among the plurality of first transaction records to obtain records to be checked corresponding to the first transaction records.

[0058] In the present application, after obtaining multiple first flow records, the first flow records with the same data values ​​of each target field in the multiple first flow records are merged, thereby obtaining the corresponding records to be checked by summarizing and statistically analyzing the multiple first flow records. Exemplarily, when the transaction type, securities code, market code, fund account number and department code of multiple first flow records are the same, the data values ​​of each field represented by each field other than each target field in the multiple first flow records that can be added are added to obtain a merged record corresponding to the multiple first flow records as the record to be checked corresponding to the multiple first flow records, and the record to be checked is a merged record of multiple first flow records for the fund account number represented by the above-mentioned target fields.

[0059] Optionally, in one implementation, the above step S102, merging the first transaction records in which the data values ​​of the target fields are the same among the multiple first transaction records to obtain the records to be checked corresponding to the first transaction records, may include the following steps:

[0060] Step A1: among a plurality of first transaction records, determining first transaction records in which data values ​​of respective target fields are the same;

[0061] Step A2: adding the data values ​​of the first field in each of the first log records to obtain a first data value of the first field, and adding the data values ​​of the second field in each of the first log records to obtain a second data value of the second field;

[0062] Step A3: The data value of each target field in each first transaction record, the first data value of the first field and the second data value of the second field constitute a transaction record as a to-be-checked record corresponding to each first transaction record.

[0063] In the present implementation, first, among multiple first flow records, first flow records whose data values ​​of respective target fields are the same are determined, then, the data values ​​of the first fields in the respective first flow records are added to obtain the first data value of the first field, and the data values ​​of the second fields in the respective first flow records are added to obtain the second data value of the second field, and finally, the data values ​​of the respective target fields in the respective first flow records, the first data value of the first field, and the second data value of the second field are combined to form a flow record as the record to be checked corresponding to the respective first flow records.

[0064] Optionally, the above-mentioned second field can be a field for representing the net price amount, or a field for representing the interest amount, or a field for representing the handling fee. Therefore, when adding the data values ​​of the second fields in each of the first transaction records, the data values ​​corresponding to the second field used to represent the net price amount can be added to obtain the first type of second data value, the data values ​​corresponding to the second field used to represent the interest amount can be added to obtain the second type of second data value, and the data values ​​corresponding to the second field used to represent the handling fee can be added to obtain the third type of second data value. Thus, the data values ​​of each target field in each of the first transaction records, the first data value of the first field, the first type of second data value of the second field, the second type of second data value of the second field, and the third type of data value of the second field constitute a transaction record as the record to be checked corresponding to each of the first transaction records.

[0065] That is, the data represented by the second field may have different meanings. When adding the data values ​​in the second field in each first flow record, the data values ​​corresponding to the second fields representing the same data meaning are added.

[0066] Exemplarily, it is determined that the transaction type conducted by the capital account a1 with the department code xxx1 under the market code xx1 is option trading, and the specific first transaction records with the securities code xxxyyy1 are then added together to obtain a first data value of 10, that is, the total number of transaction in the first transaction records is 10; the net price amounts in the first transaction records are added together to obtain a first category second data value of 50, that is, the total net price amounts in the first transaction records is 50; the interest amounts in the first transaction records are added together to obtain a second category second data value of 70, that is, the total interest amounts in the first transaction records is 70; the handling fees in the first transaction records are added together to obtain a third category second data value of 90, that is, the total handling fees in the first transaction records is 90. Then, the transaction type of the fund account a1 with department code xxx1 under market code xx1 is option transaction, the specific securities code is xxxyyy1, the number of transaction is 10, the net price is 50, the interest is 70, and the handling fee is 90, forming a transaction record as the record to be checked corresponding to each first transaction record.

[0067] In this implementation, by merging the first transaction records with the same data values ​​in each target field, a record to be verified for the same fund account is obtained, thereby reducing the amount of data required to be processed during subsequent data verification. In addition, the above-mentioned transaction merging process can classify and summarize the first transaction records for the same fund account among multiple first transaction records to facilitate subsequent data verification.

[0068] S103: Determine, from among the pre-generated multiple reference log records, a reference log record having the same data value as that of each target field in the record to be checked as the reference log record corresponding to the record to be checked;

[0069] The plurality of reference transaction records are transaction records determined based on transaction data of a transaction system and containing data values ​​of various designated fields.

[0070] As mentioned above, the data dimensions and data storage categories of the transaction data stored in the transaction system and the bookkeeping system are different, which makes it impossible to automatically check the transaction data in the bookkeeping system based on the transaction data in the transaction system. Therefore, in this application, a running record containing the data values ​​of each specified field can be determined in advance based on the transaction data of the transaction system as a reference running record, that is, a running record with the same structure and constituent elements as the record to be checked is generated in advance based on the transaction data of the transaction system to facilitate subsequent running verification.

[0071] It should be noted that different exchanges correspond to different trading systems. This application does not limit the number of trading systems and the categories of exchanges to which they belong. When there are multiple trading systems, the above-mentioned designated fields may also include fields for characterizing the source distinction of the systems, for example, trading system 00L1, trading system 00L2, and trading system 00L3, etc.

[0072] Optionally, in one implementation, a method for determining multiple reference flow records provided in an embodiment of the present application may include the following steps:

[0073] Step B1: Standardizing the transaction data stored in the transaction system to obtain a plurality of second flow records containing data values ​​of various specified fields;

[0074] Step B2: merging the second transaction records in which the data values ​​of the target fields are the same among the plurality of second transaction records to obtain reference transaction records corresponding to the second transaction records.

[0075] In this implementation, after acquiring the transaction data stored in the transaction system, the acquired transaction data is subjected to the same standardization processing as the above-mentioned step S101, that is, each data element of the transaction data in the transaction system is mapped according to a predetermined mapping relationship to generate multiple second transaction records containing data values ​​of each specified field, and then, the second transaction records in which the data values ​​of each target field are the same are merged to obtain the reference transaction records corresponding to each second transaction record.

[0076] In this implementation, by processing the data stored in the transaction system, a reference transaction record having the same structure and elements as the record to be checked is generated. In addition, the transaction merging process can classify and aggregate the second transaction records of the same fund account among the multiple second transaction records to facilitate subsequent transaction verification.

[0077] In this way, when the constituent structures and constituent elements of the multiple pre-generated benchmark transaction records are the same as those of the records to be checked, after obtaining the records to be checked, the data values ​​of the various target fields can be directly compared to see if they are the same. From the above multiple benchmark transaction records, the benchmark transaction records whose data values ​​are the same as those of the various target fields in the records to be checked can be determined as the benchmark transaction records corresponding to the records to be checked.

[0078] S104: Analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtain an analysis result.

[0079] In actual applications, the transaction situations reflected by the transaction data stored in the transaction system and the bookkeeping system should be consistent. If they are inconsistent, the bookkeeping system that represents the manual entry of transaction data may have errors or omissions, resulting in differences in transaction data. Most of the manually entered transaction data are related to the transaction quantity and amount information. Therefore, the data values ​​of the first field used to represent the transaction quantity and the second field used to represent the amount information can be used as verification elements for data verification.

[0080] In the present application, after determining the reference flow record corresponding to the record to be checked, it is possible to analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record to obtain an analysis result.

[0081] If there is a numerical difference, it indicates that there is a data anomaly in the transaction data stored in the bookkeeping system, and the transaction situation reflected by it is inconsistent with the transaction situation reflected by the transaction data in the transaction system. At this time, the analysis result obtained indicates that there is a numerical difference, and the transaction data in the bookkeeping system needs to be corrected; if there is no numerical difference, it indicates that there is no data anomaly in the transaction data stored in the bookkeeping system, and the transaction situation reflected by it is consistent with the transaction situation reflected by the transaction data in the transaction system. At this time, the analysis result obtained indicates that there is no numerical difference, and the transaction data in the bookkeeping system does not need to be corrected.

[0082] S105: In response to the analysis result indicating the existence of numerical differences, each first transaction record corresponding to the record to be checked is corrected, and according to the data content in the corrected first transaction records, the data content indicated by each first transaction record corresponding to the record to be checked and stored in the bookkeeping system is adjusted.

[0083] In the present application, when the obtained analysis results indicate that there are numerical differences, what needs to be adjusted is the transaction data stored in the bookkeeping system. Therefore, after correcting the first transaction records corresponding to the records to be checked, the data content stored in the bookkeeping system indicated by the first transaction records corresponding to the records to be checked can be adjusted according to the data content in the corrected first transaction records, so as to realize automatic verification and correction of the transaction data in the bookkeeping system. Compared with the process of manually verifying and correcting the transaction data in the bookkeeping system in the prior art, the processing efficiency of the data verification and correction process in the data processing method provided in the embodiment of the present application is significantly improved, and the automated data verification and correction can further improve the reliability of the transaction data in the bookkeeping system compared with the manual data verification and correction.

[0084] Optionally, after adjusting the data content indicated by each first transaction record corresponding to the record to be checked and stored in the bookkeeping system, return to the above step S102, and re-execute the above steps S102-S105 based on the first transaction records corresponding to the corrected record to be checked, and verify the corrected record to be checked to further improve the reliability of the transaction data in the bookkeeping system.

[0085] It can be seen from the above that in a data processing method provided in an embodiment of the present application, a transaction record containing data values ​​of various specified fields can be generated in advance based on the transaction data of the transaction system as a benchmark transaction record, wherein the above-mentioned each specified field includes each target field, a first field for representing the transaction quantity and a second field for representing the amount information, and the above-mentioned each target field is used to uniquely represent a fund account.

[0086] In this way, after the transaction data stored in the bookkeeping system is standardized to obtain multiple first flow records containing data values ​​of each specified field, and after merging the first flow records with the same data values ​​of each target field in the multiple first flow records to obtain the to-be-checked records corresponding to the first flow records, a reference flow record with the same data values ​​of each target field in the to-be-checked record can be determined from the above-mentioned multiple predetermined reference flow records as the reference flow record corresponding to the to-be-checked record. Thus, by analyzing whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the to-be-checked record and the corresponding reference flow record, it is determined whether the transaction data in the bookkeeping system needs to be corrected. When the obtained analysis result indicates that there is a numerical difference, the first flow records corresponding to the to-be-checked record are corrected. Then, according to the data content in the corrected first flow records, the data content stored in the bookkeeping system indicated by the first flow records corresponding to the to-be-checked record is adjusted.

[0087] Based on this, in the method provided in the embodiment of the present application, by processing the transaction data stored in the bookkeeping system and the transaction system respectively, the records to be checked and their corresponding reference flow records that are convenient for data comparison are obtained. Then, by comparing the records to be checked and their corresponding reference flow records, it is determined whether there is a need for data correction of the transaction data in the bookkeeping system. Thus, if there is a need, the first flow records corresponding to the records to be checked are corrected, and according to the data content in the corrected first flow records, the corresponding data content stored in the bookkeeping system is adjusted. It can be seen that the method provided in the embodiment of the present application can realize the verification and correction of the transaction data stored in the bookkeeping system, so as to improve the reliability of the transaction data in the bookkeeping system.

[0088] Optionally, in one implementation, Figure 2 A flowchart of a data processing method provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, in Figure 1 On the basis of steps S101-S103 and step S105 shown in the figure, the above step S104, analyzing whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtaining the analysis result, may include the following steps:

[0089] S1041: Determine whether the data value of the first field in the record to be checked is the same as that in the corresponding reference record; if they are the same, execute step S1042; if they are not the same, execute step S1044;

[0090] S1042: Determine whether the data value of the second field in the record to be checked is the same as that in the corresponding reference record. If not, execute step S1043;

[0091] S1043: taking the first result used to characterize the existence of numerical differences in the amount information as the analysis result;

[0092] S1044: The second result used to characterize the numerical difference in the transaction quantity is used as the analysis result.

[0093] In the present implementation, after determining the reference flow record corresponding to the record to be checked, first, determine whether the data value of the first field in the record to be checked and the corresponding reference flow record is the same. If the data value of the first field in the two records is different, it indicates that the transaction quantities in the two records are inconsistent. This may be caused by an incorrect recording of the transaction quantity in the bookkeeping system, or the omission of the entire flow record. At this time, the second result used to characterize the numerical difference in the transaction quantity can be used as the analysis result, and through manual intervention, the first flow records corresponding to the record to be checked in the bookkeeping system can be checked and corrected.

[0094] If the data value of the first field in the two records is the same, it indicates that the transaction quantities in the two records are consistent. We can further determine whether the data value of the second field in the record to be checked and the corresponding reference transaction record is the same to determine whether the data values ​​related to the amount information in the two records are consistent.

[0095] If the data value of the second field in the two records is the same, then the data values ​​regarding the transaction quantity and the data values ​​related to the amount information in the two records are the same, and the data stored in the bookkeeping system indicated by each first transaction record corresponding to the record to be checked is correct.

[0096] If the data value of the second field in the two records is different, it means that the data values ​​about the transaction quantity in the two records are the same, but the data values ​​related to the amount information are different. This may be due to errors in the amount information being recorded incorrectly in the bookkeeping system. At this time, the first result used to represent the numerical difference in the amount information can be used as the analysis result, and by calculating the data difference, each first transaction record corresponding to the record to be checked in the bookkeeping system can be automatically checked and corrected.

[0097] In this implementation, different classification results are set according to different fields with existing numerical differences, so that when data is subsequently corrected, corrections can be made according to corresponding data processing methods to improve the reliability of transaction data stored in the revised bookkeeping system.

[0098] Optionally, in one implementation, Figure 3A flowchart of a data processing method provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, in Figure 2 On the basis of steps S101-S103 and steps S1041-S1044 shown in the figure, the above step S105, in response to the analysis result indicating that there is a numerical difference, corrects each first transaction record corresponding to the record to be checked, and may include the following steps:

[0099] S1051: In response to the analysis result being the first result, based on the transaction quantities in the first transaction records corresponding to the record to be checked, determining the transaction quantity ratio of the first transaction records corresponding to the record to be checked; determining the data difference of the second field in the record to be checked and the corresponding reference transaction record, and based on the determined data difference and according to the transaction quantity ratio, correcting the data value of the second field in the first transaction records corresponding to the record to be checked;

[0100] S1052: In response to the analysis result being the second result, output each first transaction record corresponding to the record to be checked and target prompt information; and obtain each first transaction record corresponding to the record to be checked that has been manually corrected; wherein the target prompt information is used to indicate manual correction of each first transaction record corresponding to the record to be checked.

[0101] In this implementation, corresponding data processing methods are set for different types of analysis results, and each first transaction record corresponding to the record to be checked in the bookkeeping system is checked and corrected, specifically:

[0102] In response to the analysis result being the first result, based on the number of transactions in each first transaction record corresponding to the record to be checked, determine the transaction quantity ratio of each first transaction record corresponding to the record to be checked, then determine the data difference of the second field in the record to be checked and the corresponding benchmark transaction record, and based on the determined data difference, correct the data value of the second field in each first transaction record corresponding to the record to be checked according to the transaction quantity ratio.

[0103] Exemplarily, the first transaction records corresponding to the record P to be checked are the first transaction record P1, the first transaction record P2, and the first transaction record P3, wherein the data value of the first field of the first transaction record P1 is 15, and the data value of the second field is 150; the data value of the first field of the first transaction record P2 is 10, and the data value of the second field is 100; the data value of the first field of the first transaction record P3 is 5, and the data value of the second field is 50, then the transaction quantity ratio of the first transaction records corresponding to the record to be checked is 3:2:1. If the data difference between the determined record P to be checked and the corresponding reference transaction record in the second field is 60, for example, the reference transaction record has 60 less amount information than the second field in the record to be checked, then according to the above-mentioned transaction quantity ratio of 3:2:1, the data value of the second field in the first transaction record P1 is reduced by 30, and the data value of the second field is corrected to 120; the data value of the second field in the first transaction record P2 is reduced by 20, and the data value of the second field is corrected to 80; the data value of the second field in the first transaction record P3 is reduced by 10, and the data value of the second field is corrected to 40.

[0104] For another example, if the amount information in the second field of the benchmark transaction record is 60 more than that in the record to be verified, then according to the above-mentioned transaction quantity ratio of 3:2:1, the data value of the second field in the first transaction record P1 is increased by 30, and the data value of the second field is corrected to 180; the data value of the second field in the first transaction record P2 is increased by 20, and the data value of the second field is corrected to 120; the data value of the second field in the first transaction record P3 is increased by 10, and the data value of the second field is corrected to 60.

[0105] Normally, there is a certain proportional relationship between the net price amount, interest amount and handling fee in securities transactions. Therefore, optionally, when there is a second field for representing the net price amount, a second field for representing the interest amount, and a second field for representing the handling fee in the first transaction record, the data values ​​of the other second fields can be adjusted according to the data value that needs to be adjusted for any second field and the above-mentioned proportional relationship.

[0106] When the analysis result is the second result, each first transaction record corresponding to the record to be checked in the bookkeeping system can be checked and corrected through manual intervention. At this time, each first transaction record corresponding to the record to be checked and target prompt information for indicating manual correction of each first transaction record corresponding to the record to be checked can be output. In this way, after receiving the above target prompt information, the user manually checks and corrects each first transaction record corresponding to the record to be checked, and then re-enters the checked and corrected first transaction records corresponding to the record to be checked into the electronic device, so that the electronic device obtains each first transaction record corresponding to the record to be checked after the manual correction.

[0107] Exemplarily, the data value of the first field of the record to be checked P is 109, and the data value of the first field of the reference transaction record corresponding to the record to be checked P is 110, wherein the first transaction records corresponding to the record to be checked P are the first transaction record P1, the first transaction record P2, and the first transaction record P3. At this time, it can be determined that there are data errors and data omissions in the transaction data in the bookkeeping system, and the first transaction records corresponding to the record to be checked P are manually checked and corrected.

[0108] In this implementation, by classifying the analysis results, that is, classifying the analysis results into a first result for characterizing the existence of numerical differences in the amount information, and a second result for characterizing the existence of numerical differences in the transaction quantity, a corresponding data processing method is set to check and correct each first flow record corresponding to the record to be checked in the bookkeeping system. In this way, through the set targeted data processing method, targeted data verification and data correction can be performed for different situations where the data is incorrect, so as to improve the reliability of the transaction data stored in the bookkeeping system after correction, thereby further improving the applicability of a data processing method provided in the embodiment of the present application.

[0109] Optionally, in an embodiment, a data processing method provided in an embodiment of the present application may further include the following steps:

[0110] Step C1: in response to the analysis result indicating that there is no numerical difference, setting a first label for indicating that the data is correct for the record to be checked;

[0111] Step C2: after correcting the data value of the second field in each first flow record corresponding to the record to be checked, setting a second label for indicating that the record to be checked has been corrected;

[0112] Step C3: after obtaining each first transaction record corresponding to the record to be checked that has been manually corrected, setting a second label for the record to be checked.

[0113] In this embodiment, a data tag for representing the data status may be set in the record to be checked, specifically:

[0114] When the analysis result indicates that there is no numerical difference between the record to be checked and the corresponding reference flow record, a first label for indicating that the data is correct is set for the record to be checked;

[0115] When the analysis result indicates that there is a numerical difference between the record to be checked and the corresponding reference log record, and the analysis result is the first result, after correcting the data value of the second field in each first log record corresponding to the record to be checked, a second tag for indicating that the record to be checked has been corrected is set for the record to be checked;

[0116] When the analysis result indicates that there is a numerical difference between the record to be checked and the corresponding reference flow record, and the analysis result is the second result, after obtaining each first flow record corresponding to the record to be checked that has been corrected manually, a second label is set for the record to be checked to indicate that it has been corrected.

[0117] Optionally, when the analysis result indicates that there is a numerical difference between the record to be checked and the corresponding reference flow record, and the analysis result is the second result, a designated label indicating that manual correction is to be performed is set for the record to be checked. In this way, after all the records to be checked are checked and the records to be checked whose analysis result is the first result are corrected, the records to be checked with the designated label are checked and corrected, so as to improve the process of automatic checking and correction, and further improve the processing efficiency of data processing.

[0118] Optionally, each record to be checked and its corresponding label are output to a predetermined interface, so that the user can determine which records to be checked have excessive numerical differences through the data content displayed in the above predetermined interface, so that the user can standardize subsequent data entry operations and promptly correct the uncorrected records to be checked to reduce the possibility of missed detection, until the labels set for all records to be checked in the above predetermined interface are the first label or the second label, thereby improving the accuracy of data processing.

[0119] Optionally, in one implementation, a data tag for indicating that no verification is required may be provided in the first transaction record. In the above step S102, before merging the first transaction records in which the data values ​​of the target fields are the same in the plurality of first transaction records to obtain the records to be verified corresponding to the first transaction records, a data processing method provided in an embodiment of the present application further includes the following steps:

[0120] Step D1: filtering each first transaction record provided with a data tag for indicating that no verification is required;

[0121] The above step S102 may include the following steps:

[0122] Step D2: first transaction records whose data values ​​of target fields are the same among the plurality of first transaction records remaining after filtering are merged to obtain records to be checked corresponding to the first transaction records.

[0123] In this implementation, considering that there are some automatically generated transaction data in the bookkeeping system that are not manually entered, as well as some transaction data that do not affect the asset accounting results after subsequent corrections, the above-mentioned data tags for representing that no verification is required can be used to mark this type of first transaction record. In this way, before the transaction merge is performed, by identifying the above-mentioned data tags for representing that no verification is required, the amount of data that needs to be processed in subsequent processes such as transaction merge can be reduced, thereby improving data processing efficiency.

[0124] The data labels used to represent data that do not need to be checked may be manually labeled, or the data labels may be set for the first transaction records by identifying special fields in the first transaction records of this type, which is reasonable.

[0125] Exemplarily, by determining whether the market type and business type in the first transaction record are preset types, it is determined whether to set the above-mentioned data label for the first transaction record. Specifically: if yes, it indicates that the first transaction record will not affect the asset accounting results performed after subsequent revisions. In this case, the above-mentioned data label is set for the first transaction record; if no, it indicates that the first transaction record will affect the asset accounting results performed after subsequent revisions. In this case, the above-mentioned data label is not set for the first transaction record.

[0126] Optionally, in one implementation, the first transaction record further includes: a data value of a predetermined field, the predetermined field being used to characterize the institution to which the fund account belongs; the above step S102, merging the first transaction records having the same data values ​​of the target fields in the plurality of first transaction records to obtain the records to be checked corresponding to the first transaction records, may include the following steps:

[0127] Step E: merging the first transaction records in which the data values ​​of the target fields and the predetermined fields are the same among the plurality of first transaction records to obtain the to-be-checked records corresponding to the first transaction records.

[0128] In this implementation, in order to facilitate the asset accounting based on the corrected data after data processing, such accounting is usually performed in units of internal company accounts, and considering that the transaction data in the bookkeeping system is recorded in units of internal company accounts, illustratively, there are two account elements stored in the bookkeeping system, namely, the capital account and the secondary securities account, wherein the secondary securities account is the internal company account, that is, there is a corresponding relationship between the capital account and the institution (internal company account) to which the capital account belongs in the bookkeeping system, in order to reflect the above-mentioned corresponding relationship in the first flow record, when the transaction data in the bookkeeping system is standardized, the code corresponding to the institution to which the secondary securities account belongs is queried as the data value used to characterize the institution to which the capital account belongs, that is, the institution to which the capital account belongs is substantially used to reflect the institution to which the secondary securities account belongs in the first flow record. Therefore, the first flow record may also include a data value of a predetermined field, and the predetermined field is used to characterize the institution to which the capital account belongs.

[0129] In this way, when merging the flow records, the first flow records in which the data values ​​of the target fields and the predetermined fields are the same in the multiple first flow records can be merged to obtain the records to be checked corresponding to the first flow records. Exemplarily, when the transaction type, securities code, market code, fund account number, department code and institution to which the fund account belongs in the multiple first flow records are the same, the data values ​​of the fields represented by the data values ​​that can be added in the fields other than the above fields in the multiple first flow records are added to obtain the merged record corresponding to the multiple first flow records as the record to be checked corresponding to the multiple first flow records, and the record to be checked is the merged record of the multiple first flow records for the fund account number represented by the above target fields.

[0130] Among them, the above-mentioned predetermined fields may include fields for representing the company's internal account code, associated serial number, associated serial account code, settlement method, etc., and this embodiment of the present application does not make specific limitations on this.

[0131] In this implementation, by merging the first transaction records with the same data values ​​of the target fields and the predetermined fields, a record to be verified for the same fund account under one institution is obtained, so as to reduce the amount of data required to be processed in the subsequent data verification. In addition, the above-mentioned transaction merging process can classify and summarize the first transaction records for the same fund account under one institution among multiple first transaction records, so as to facilitate the subsequent asset accounting based on the institution to which the fund account belongs.

[0132] For ease of understanding, a data processing method provided in an embodiment of the present application is described in detail below in combination with a specific embodiment.

[0133] Currently, securities trading information related to stocks, bonds, options, etc. exists in both the trading system and the bookkeeping system. The trading system's trading data is automatically generated during trading, with high accuracy, but lacks information on the company's account dimensions (i.e., data values ​​used to characterize the institution to which the fund account belongs). The bookkeeping system's data contains information on the company's internal account dimensions (i.e., data values ​​used to characterize the institution to which the fund account belongs), which can be used for asset accounting of various fund accounts within the company. However, most of the bookkeeping system's transaction flows rely on manual entry, and manually entered data has reliability issues, such as wrong entry and missing entry, which affects data accuracy and subsequent data analysis.

[0134] The solution in the prior art is to manually review the data in the bookkeeping system. If there is any possible erroneous transaction data, the data is confirmed with the employee who entered the data or the corresponding data is manually queried in the transaction system, so as to check and correct the data in the bookkeeping system. The problem with the solution in the prior art is that it takes a lot of time to manually review and correct the data in the bookkeeping system, and there is still the possibility of human error.

[0135] Based on this, the present application provides a method and system for automatically checking and correcting securities trading information (i.e., a data processing method provided in the embodiments of the present application), so as to solve the problems of wrong entry and missing entry in manually entered trading information through data processing of trading data, reduce the cost and time of manual review, and improve the accuracy of trading data based on companies. Among them, the system for executing the above method may include a data acquisition module, a flow analysis module, a flow matching module, a difference update module, and a result display module.

[0136] Among them, the data collection module is responsible for collecting transaction information from each system (transaction data in the transaction system and transaction data in the bookkeeping system in this application) and outputting it to the parsing module. The transaction flow parsing module is responsible for parsing the transaction information, generating standardized transaction flows (the first transaction record and the second transaction record in this application) and outputting them to the matching module. The transaction flow matching module is responsible for associating and matching the transaction flows in the transaction system (the reference transaction record in this application) with the transaction flows in the bookkeeping system (the records to be verified in this application). The difference update module is responsible for automatically verifying and correcting the data in the bookkeeping system with the data in the transaction system after matching, so as to obtain accurate transaction flows for subsequent asset accounting. The result display module is responsible for displaying the flow status and flow information after automatic verification and correction, which is used to determine whether all flows have been verified and to display the data difference between the bookkeeping system flows that have not been verified and the transaction system flows.

[0137] Exemplary, combined Figure 4The processes executed by each module in the execution system for executing the data processing method provided in the above embodiment are described in detail. Figure 4 The schematic diagram of the structure of a specific embodiment provided by the present application, wherein the number of transaction systems in this specific embodiment is n. The execution system for executing the data processing method provided by the above embodiment includes a data acquisition module, a data analysis module, a flow matching module, a difference update module and a result display module, specifically:

[0138] (1) Data collection module 410, used to collect required transaction information from various systems, specifically:

[0139] Collect the required transaction information from various trading systems and bookkeeping systems. The data tables where the data to be collected in the trading system are stored include the flow data table, stock information table, ETF basic information table, bond information table, business type definition table, department information table, account information table, etc. The data tables where the data to be collected in the bookkeeping system are stored include the transaction flow table, buyout repo table, pledge repo table, bond forward transaction table, pledge bond table, transaction grouping table, transaction order table, primary securities account table, secondary securities account table, primary and secondary securities account correspondence table, secondary fund account table, etc.

[0140] Then, the data collection module 410 outputs the collected transaction information to the data analysis module 420 .

[0141] (2) Data analysis module 420, used to analyze transaction information of each system and generate standardized transaction flow data, specifically:

[0142] Analyze the collected transaction information, map the various elements of the transaction in the transaction system and the bookkeeping system using unified rules, and generate standardized transaction flow data to facilitate subsequent flow matching. The above-mentioned standardized transaction flow data is the first flow record and the second flow record in this application.

[0143] For the trading system, the standardized transaction flow should include the transaction date, asset category, transaction type, fund account, department code, market code, securities code, system source distinction, serial number, transaction quantity, net price amount, interest amount, handling fee, etc. Among them, the fields corresponding to the above transaction date, asset category, transaction type, fund account, department code, market code, securities code, system source distinction, serial number, transaction quantity, net price amount, interest amount, and handling fee are the designated fields in the embodiment of this application. For the bookkeeping system, the standardized transaction flow should also have the elements such as the company's internal account code, associated serial number, associated serial account code, and settlement method on the basis of the above. Among them, the fields corresponding to the elements such as the above company's internal account code, associated serial number, associated serial account code, and settlement method are the predetermined fields in the embodiment of this application.

[0144] Then, the data parsing module 420 outputs the generated standardized transaction flow data to the flow matching module 430 .

[0145] (3) The transaction flow matching module 430 is used to match the transaction flow data of the transaction system and the bookkeeping system. Specifically:

[0146] Using the generated standardized transaction flow data, the transaction system's flow is correlated and matched with the bookkeeping system's flow.

[0147] It should be noted that before matching, the transaction flow data of the bookkeeping system that does not need to be matched is first screened out. This type of transaction flow data is generally a small part of the automatically generated flow data in the bookkeeping system that is not manually entered, as well as some internal transaction flow data that does not affect the subsequent asset accounting results. The data status of these transaction flow data is set to "no need to match" (that is, the data label used to represent the data that does not need to be checked in the embodiment of the present application).

[0148] When performing association matching, since the transaction flow data in the trading system is generated based on the capital account, and the transaction flow data in the bookkeeping system is generated based on the company's internal account, and multiple different company internal accounts can use the same capital account, and at the same time, the same company internal account can also use multiple different capital accounts, the transaction flow data in the trading system cannot be one-to-one corresponded with the transaction flow data in the bookkeeping system, but there is a one-to-many, many-to-one, or many-to-many situation.

[0149] Therefore, the transaction flow matching module in this specific embodiment can use the transaction type, securities code, market code, fund account number, and department code as the primary key (i.e., each target field in the embodiment of the present application) to summarize the transaction flow data of the trading system and the bookkeeping system respectively, that is, the transaction quantity, net price amount, interest amount, and handling fee of multiple flow records with the same primary key in a single system are added together into one flow. The merged flow is called a virtual merged flow, which is only used for verification and correction after matching and does not participate in subsequent asset accounting. The virtual merged flow with the same primary key between different systems is regarded as the same transaction, and the virtual merged flow of the same transaction in the two systems is associated and matched one-to-one, thereby realizing the association and matching of transaction data of different dimensions in the two systems. Among them, the virtual merged flow in the trading system is the benchmark flow record in this application, and the virtual merged flow in the bookkeeping system is the record to be verified in this application.

[0150] Then, the transaction matching module 430 inputs the matched virtual combined transaction flow of the bookkeeping system and the virtual combined transaction flow of the corresponding trading system into the difference updating module 440 .

[0151] (4) A difference update module 440 is used to calculate the difference based on the matching virtual merged transactions in the two systems, and to update the transaction information in the bookkeeping system based on the difference; wherein the above-mentioned difference is the data difference in this application.

[0152] For example, Figure 5 A flowchart of a process executed in a balance update module provided in an embodiment of the present application, the process may include the following steps:

[0153] S501: virtual merged flow of the bookkeeping system after matching;

[0154] S502: Determine whether there is a flow in the virtual combined flow of the trading system that matches the virtual combined flow of the bookkeeping system; if so, execute step S503; if not, execute step S509;

[0155] S503: Compare the transaction quantities of the virtual combined flow of the bookkeeping system and the virtual combined flow of the matching trading system;

[0156] S504: Determine whether the transaction quantities of the two transactions are the same; if so, execute step S505; if not, execute step S509;

[0157] S505: If the match is successful, the amount information and other elements of the two transactions are compared;

[0158] S506: Check whether the amount information and other elements of the two transaction records are the same; if yes, execute step S507; if no, execute step S508;

[0159] S507: Verification and correction are completed, and the pipeline status is changed to verified and corrected;

[0160] S508: Automatically calculate the difference value, and update the transaction data in the bookkeeping system based on the difference data;

[0161] S509: modifying the status of transaction data corresponding to the virtual merged flow of the bookkeeping system to a matching error;

[0162] S510: Display the flow status on the front-end interface.

[0163] In the above steps S501-S510, for each matched virtual merged flow of the bookkeeping system, first determine whether its transaction quantity is consistent with the virtual merged flow of the matched transaction system. If inconsistent, it means that the bookkeeping system has an incorrect transaction quantity or the entire flow is missed. The status of the flow transaction data corresponding to the virtual merged flow of the bookkeeping system is modified to a matching error, that is, the status of all original flows (that is, the real flows before the merger) under the virtual merged flow of the bookkeeping system is modified to "matching error" (that is, the designated label in this application).

[0164] If the virtual merged flow of the bookkeeping system cannot find the virtual merged flow of the trading system that can match it, the status of all original flow under the unmatched virtual merged flow of the bookkeeping system will also be modified to "matching error" (that is, the specified label in this application), and the status of the remaining matched flow will be updated to "matching success".

[0165] For all successfully matched virtual merged flows, compare the virtual merged flows of the bookkeeping system with the virtual merged flows of the trading system to see if there are any differences in the net price amount, interest amount, handling fee and other amount information. If there are no differences, it means that the data in the bookkeeping system is correct and does not need to be corrected; if there are differences, it means that the amount information and other data in the bookkeeping system are recorded incorrectly. At this time, the difference value is automatically calculated, and the difference value is updated to each original flow of the bookkeeping system in proportion to the number of transactions, and the flow status is modified to "verified and corrected" (that is, the second label in this application). Then, the flow status of each bookkeeping system is displayed on the front-end interface.

[0166] (5) Result display module 450, used to display the transaction status, transaction quantity, net price amount, interest amount, transaction data of the matching transaction system, and other elements of each bookkeeping system on the front-end interface.

[0167] When the status of all transactions is "verified and revised" or "no need to match", the subsequent asset accounting will begin. When the status of all transactions is "verified and revised" or "no need to match", it means that all transaction information in the bookkeeping system is correct.

[0168] When there is transaction data with a status of "matching error", the transaction data with problems is manually reviewed and corrected, and then, after the correction, it returns to the transaction matching module 430 and the transaction matching step is performed again until all transaction data are "verified and corrected" or "no need to match".

[0169] In this specific embodiment, through automatic verification and correction of data, erroneous transaction information in the bookkeeping system is effectively corrected, significantly improving the accuracy and reliability of the transaction data in the bookkeeping system. In addition, by effectively identifying and processing the omissions of transaction data in the bookkeeping system and making timely adjustments, the financial risks and potential losses caused by data errors are reduced. In addition, the automation of data processing can reduce the workload of manual review and improve work efficiency. In this way, when checking and correcting data, the user only needs to check whether there are matching errors in the front-end interface, and check whether there are any missing records and make up for them.

[0170] Corresponding to the above method embodiment, the present application embodiment also provides a data processing device, such as Figure 6 As shown, the device comprises:

[0171] The first processing module 610 is used to perform standardization processing on the transaction data stored in the bookkeeping system to obtain a plurality of first flow records containing data values ​​of various specified fields; wherein the various specified fields include various target fields, a first field for representing the transaction quantity, and a second field for representing the amount information, and the various target fields are used to uniquely represent a fund account;

[0172] A first merging module 620 is used to merge the first transaction records in which the data values ​​of the target fields are the same among the plurality of first transaction records to obtain the to-be-checked records corresponding to the first transaction records;

[0173] The transaction determination module 630 is used to determine, from a plurality of pre-generated reference transaction records, reference transaction records having the same data values ​​as the target fields in the record to be checked, as reference transaction records corresponding to the record to be checked; wherein the plurality of reference transaction records are transaction records determined based on transaction data of the transaction system and containing the data values ​​of the designated fields;

[0174] A result analysis module 640 is used to analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtain an analysis result;

[0175] The data correction module 650 is used to correct each first transaction record corresponding to the record to be checked in response to the analysis result indicating the existence of numerical differences, and adjust the data content stored in the bookkeeping system indicated by each first transaction record corresponding to the record to be checked according to the data content in the corrected first transaction records.

[0176] Optionally, in one implementation, the method for determining the plurality of reference flow records includes:

[0177] Standardizing the transaction data stored in the transaction system to obtain a plurality of second flow records containing data values ​​of various specified fields;

[0178] The second transaction records in which the data values ​​of the target fields are the same among the plurality of second transaction records are merged to obtain reference transaction records corresponding to the second transaction records.

[0179] Optionally, in an implementation, the first merging module 620 is specifically configured to:

[0180] Among the plurality of first transaction records, determining first transaction records in which data values ​​of the respective target fields are the same;

[0181] Adding the data values ​​of the first field in each of the first log records to obtain a first data value of the first field, and adding the data values ​​of the second field in each of the first log records to obtain a second data value of the second field;

[0182] The data values ​​of the target fields, the first data value of the first field and the second data value of the second field in the first transaction records constitute a transaction record as a to-be-checked record corresponding to the first transaction records.

[0183] Optionally, in one implementation, the result analysis module 640 is specifically configured to:

[0184] Determine whether the data value of the first field in the record to be checked and the corresponding reference log record is the same;

[0185] If they are the same, determining whether the data value of the second field in the record to be checked and the corresponding reference record is the same; if they are not the same, taking the first result for indicating that there is a numerical difference in the amount information as the analysis result;

[0186] If they are not the same, the second result used to characterize the numerical difference in the transaction quantity will be used as the analysis result.

[0187] Optionally, in one implementation, the data correction module 650 is specifically used to:

[0188] In response to the analysis result being the first result, determining the transaction quantity ratio of each first transaction record corresponding to the record to be checked based on the transaction quantity in each first transaction record corresponding to the record to be checked; determining the data difference of the second field in the record to be checked and the corresponding reference transaction record, and based on the determined data difference and according to the transaction quantity ratio, correcting the data value of the second field in each first transaction record corresponding to the record to be checked;

[0189] In response to the analysis result being the second result, the first transaction records corresponding to the records to be checked and the target prompt information are output; wherein the target prompt information is used to indicate manual correction of the first transaction records corresponding to the records to be checked; and, the first transaction records corresponding to the records to be checked after manual correction are obtained.

[0190] Optionally, in an implementation manner, the device further includes:

[0191] A first setting module is used for setting a first label for indicating that the data is correct for the record to be checked in response to the analysis result indicating that there is no numerical difference;

[0192] A second setting module is used to set a second label for indicating that the record to be checked has been corrected after correcting the data value of the second field in each first flow record corresponding to the record to be checked;

[0193] After obtaining each first transaction record corresponding to the record to be checked that is corrected manually, the second label is set for the record to be checked.

[0194] Optionally, in one implementation, the first transaction record further includes: a data value of a predetermined field, the predetermined field being used to represent the institution to which the fund account belongs;

[0195] The first merging module 620 is specifically used for:

[0196] The first transaction records in which the data values ​​of the target fields and the predetermined fields are the same among the plurality of first transaction records are merged to obtain the to-be-checked records corresponding to the first transaction records.

[0197] The present application also provides an electronic device, such as Figure 7 As shown, it includes a processor 701 , a communication interface 702 , a memory 703 and a communication bus 704 , wherein the processor 701 , the communication interface 702 , and the memory 703 communicate with each other via the communication bus 704 .

[0198] Memory 703, used for storing computer programs;

[0199] The processor 701 is used to implement any data processing method described in the above embodiments when executing the program stored in the memory 703.

[0200] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0201] The communication interface is used for communication between the above electronic device and other devices.

[0202] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0203] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0204] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned data processing methods are implemented.

[0205] In another embodiment provided in the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute any of the data processing methods in the above embodiments.

[0206] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0207] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0208] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, electronic device embodiment, computer-readable storage medium embodiment, and computer program product embodiment, since they are basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0209] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A data processing method, characterized in that: include: Standardizing the transaction data stored in the bookkeeping system to obtain a plurality of first flow records containing data values ​​of various specified fields; wherein the various specified fields include various target fields, a first field for representing the transaction quantity, and a second field for representing the amount information, and the various target fields are used to uniquely represent a fund account; Merging the first transaction records in which the data values ​​of the target fields are the same among the plurality of first transaction records to obtain the to-be-checked records corresponding to the first transaction records; Determine, from the pre-generated multiple reference transaction records, reference transaction records having the same data values ​​as the target fields in the record to be checked as reference transaction records corresponding to the record to be checked; wherein the multiple reference transaction records are transaction records determined based on transaction data of the transaction system and containing the data values ​​of the designated fields; Analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtain an analysis result; In response to the analysis result indicating the existence of numerical differences, the first transaction records corresponding to the records to be checked are corrected, and according to the data content in the corrected first transaction records, the data content indicated by the first transaction records corresponding to the records to be checked and stored in the bookkeeping system is adjusted.

2. The method according to claim 1, characterized in that The method for determining the plurality of reference flow records includes: Standardizing the transaction data stored in the transaction system to obtain a plurality of second flow records containing data values ​​of various specified fields; The second transaction records in which the data values ​​of the target fields are the same among the plurality of second transaction records are merged to obtain reference transaction records corresponding to the second transaction records.

3. The method according to claim 1 or 2, characterized in that: The step of merging the first flow records in which the data values ​​of the target fields are the same among the plurality of first flow records to obtain the to-be-checked records corresponding to the first flow records includes: Among the plurality of first transaction records, determining first transaction records in which data values ​​of the respective target fields are the same; Adding the data values ​​of the first field in each of the first log records to obtain a first data value of the first field, and adding the data values ​​of the second field in each of the first log records to obtain a second data value of the second field; The data values ​​of the target fields, the first data value of the first field and the second data value of the second field in the first transaction records constitute a transaction record as a to-be-checked record corresponding to the first transaction records.

4. The method according to claim 3, characterized in that The analyzing whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtaining the analysis result, includes: Determine whether the data value of the first field in the record to be checked and the corresponding reference log record is the same; If they are the same, determining whether the data value of the second field in the record to be checked and the corresponding reference record is the same; if they are not the same, taking the first result for indicating that there is a numerical difference in the amount information as the analysis result; If they are not the same, the second result used to characterize the numerical difference in the transaction quantity will be used as the analysis result.

5. The method according to claim 4, characterized in that In response to the analysis result indicating that there is a numerical difference, the first transaction records corresponding to the record to be checked are corrected, including: In response to the analysis result being the first result, determining the transaction quantity ratio of each first transaction record corresponding to the record to be checked based on the transaction quantity in each first transaction record corresponding to the record to be checked; determining the data difference of the second field in the record to be checked and the corresponding reference transaction record, and based on the determined data difference and according to the transaction quantity ratio, correcting the data value of the second field in each first transaction record corresponding to the record to be checked; In response to the analysis result being the second result, the first transaction records corresponding to the records to be checked and the target prompt information are output; wherein the target prompt information is used to indicate manual correction of the first transaction records corresponding to the records to be checked; and, the first transaction records corresponding to the records to be checked after manual correction are obtained.

6. The method according to claim 5, characterized in that The method further comprises: In response to the analysis result indicating that there is no numerical difference, setting a first label for indicating that the data is correct for the record to be verified; After correcting the data value of the second field in each first flow record corresponding to the record to be checked, setting a second label for indicating that the record to be checked has been corrected; After obtaining each first transaction record corresponding to the record to be checked that is corrected manually, the second label is set for the record to be checked.

7. The method according to claim 1 or 2, characterized in that: The first transaction record also includes: a data value of a predetermined field, the predetermined field being used to represent the institution to which the fund account belongs; The step of merging the first flow records in which the data values ​​of the target fields are the same among the plurality of first flow records to obtain the to-be-checked records corresponding to the first flow records includes: The first transaction records in which the data values ​​of the target fields and the predetermined fields are the same among the plurality of first transaction records are merged to obtain the to-be-checked records corresponding to the first transaction records.

8. A data processing device, characterized in that: include: A first processing module is used to perform standardized processing on the transaction data stored in the bookkeeping system to obtain a plurality of first flow records containing data values ​​of various specified fields; wherein the various specified fields include various target fields, a first field for representing the transaction quantity, and a second field for representing the amount information, and the various target fields are used to uniquely represent a fund account; A first merging module, configured to merge the first transaction records in which the data values ​​of the target fields are the same among the plurality of first transaction records, to obtain the to-be-checked records corresponding to the first transaction records; A transaction flow determination module, configured to determine, from a plurality of pre-generated reference transaction flow records, reference transaction flow records having the same data values ​​as the target fields in the record to be checked, as reference transaction flow records corresponding to the record to be checked; wherein the plurality of reference transaction flow records are transaction flow records determined based on transaction data of a transaction system and containing the data values ​​of the designated fields; A result analysis module is used to analyze whether there is a numerical difference between the data values ​​corresponding to the first field and the second field in the record to be checked and the corresponding reference flow record, and obtain an analysis result; A data correction module is used to correct each first transaction record corresponding to the record to be checked in response to the analysis result indicating the existence of a numerical difference, and to adjust the data content indicated by each first transaction record corresponding to the record to be checked and stored in the bookkeeping system according to the data content in the corrected first transaction records.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing any of the methods described in claims 1-7 when executing a program stored in a memory.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images