Batch data account checking method and device, equipment, storage medium and product

Abstract

The invention discloses a batch data reconciliation method and device, equipment, a storage medium and a product, and relates to the technical field of data comparison, and the batch data reconciliation method comprises the steps of obtaining database batch data in response to a batch reconciliation instruction; summarizing the database batch data to obtain first to-be-checked summarized data; obtaining second to-be-checked summarized data, checking the first to-be-checked summarized data with the second to-be-checked summarized data, and determining a checking result; and if the checking result is inconsistent, performing detail checking, confirming difference data, updating and supplementing the first to-be-checked summarized data based on the difference data, and returning to the step of comparing the first to-be-checked summarized data with the second to-be-checked summarized data until the checking result is consistent, and confirming that the batch reconciliation result is a balance reconciliation result. According to the method and the device, the batch data of the database is summarized for checking, and the account checking data is aligned through detail checking and supplementing, so that the account checking efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data comparison technology, and in particular to batch data reconciliation methods, devices, equipment, storage media and products. Background Art

[0002] In financial messaging systems, deploying multiple services in multiple databases is a common solution to improve system availability.

[0003] However, the existing technology relies on scheduled tasks to synchronize the data of each sub-database to a centralized reconciliation database to check massive transaction data, which has significant defects: online transaction interference, scheduled tasks occupy database connection resources during peak transaction periods, resulting in degraded online transaction performance; high storage costs, and synchronizing the full amount of detailed data results in redundant storage. For example, hundreds of millions of transaction records require additional TB-level storage space; high management complexity, requiring regular cleaning and verification of data and optimization of database fragmentation, increasing operation and maintenance costs; low verification efficiency, and single-threaded verification of massive data takes up to several hours, which cannot meet real-time requirements.

[0004] Therefore, how to improve the reconciliation efficiency of financial messages is an urgent problem to be solved. Summary of the Invention

[0005] The main purpose of this application is to provide a batch data reconciliation method, device, equipment, storage medium and product, aiming to solve the technical problem of low reconciliation efficiency of financial messages.

[0006] To achieve the above objectives, the present application proposes a batch data reconciliation method, which includes:

[0007] Responding to a batch reconciliation instruction, obtaining database batch data;

[0008] Summarizing the batch data in the database to obtain first summary data to be verified;

[0009] Acquire the second summary data to be verified, and verify the first summary data to be verified with the second summary data to be verified to determine a verification result;

[0010] If the verification result is inconsistent, a detailed verification is performed to confirm the difference data, and the first summary data to be verified is updated and supplemented based on the difference data. The process returns to the step of comparing the first summary data to be verified with the second summary data to be verified, until the verification result is consistent, and the batch reconciliation result is confirmed to be balanced.

[0011] In one embodiment, the step of aggregating the database batch data to obtain first aggregated data to be verified includes:

[0012] According to the preset business classification, the batch reconciliation data in the pre-configured database of each business classification is summarized in parallel, and the summarized batch reconciliation data is stored in the preset sub-database summary intermediate table;

[0013] The batch reconciliation data in the sub-library summary intermediate table is summarized to obtain first summary data to be checked.

[0014] In one embodiment, the step of aggregating batch reconciliation data in pre-configured databases for each business classification in parallel according to the preset business classification, and storing the aggregated batch reconciliation data in a preset sub-database summary intermediate table includes:

[0015] Through the preset database connection pool, dynamically switch the business sub-database corresponding to the preset business classification;

[0016] Without pre-synchronizing the full verification data to the centralized storage, perform real-time statistical operations on each of the business sub-databases and generate sub-database summary data in parallel;

[0017] The sub-library summary data is written into the sub-library summary intermediate table, wherein the intermediate table only stores the sub-library statistical values ​​without retaining the original transaction details.

[0018] In one embodiment, the steps of performing detailed verification, confirming difference data, and updating and supplementing the first summary data to be verified based on the difference data include:

[0019] If the transaction status in the second summary data to be verified is inconsistent with the transaction status in the first summary data to be verified, automatically adjusting the transaction status of the first summary data to be verified to the transaction status of the second summary data to be verified;

[0020] If the amount of the second summary data to be verified is greater than the amount of the first summary data to be verified, the operator's reissue process is triggered.

[0021] In one embodiment, after the step of triggering the operator reissue process, the following steps are further included:

[0022] Obtain detailed data of reissues from the external system through the preset batch reissue synchronization application;

[0023] Synchronize the reissued detailed data to the preset reconciliation cluster database;

[0024] The detailed verification process is re-executed based on the reissued detailed data until the first summary data to be verified is consistent with the second summary data to be verified.

[0025] In one embodiment, if the verification result is inconsistent, the step of performing detailed verification further includes:

[0026] The comprehensive query front end provides operators with a visual operation interface, which includes:

[0027] Check the abnormal data display module, which is used to classify and display detailed records of inconsistent status, missing data and redundant data;

[0028] A manual account adjustment operation module supports manual adjustment of the transaction status in the first summary data to be verified;

[0029] The reissue instruction initiation module is used to initiate a data reissue request for a specified transaction to an external system;

[0030] The check restart trigger module re-executes the step of checking the first summary data to be checked with the second summary data to be checked if a manual intervention operation is detected.

[0031] In one embodiment, the step of obtaining database batch data in response to the batch reconciliation instruction includes:

[0032] Receive reconciliation messages from external systems and write them into the database;

[0033] After writing is completed, a response is returned immediately, and the batch reconciliation instruction is triggered through an asynchronous call mechanism to avoid occupying online database connection resources.

[0034] In addition, to achieve the above-mentioned purpose, the present application also proposes a batch data reconciliation device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the computer program is configured to implement the steps of the batch data reconciliation method as described above.

[0035] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the batch data reconciliation method described above are implemented.

[0036] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the batch data reconciliation method as described above.

[0037] One or more technical solutions proposed in this application have at least the following technical effects:

[0038] Compared with the related art that relies on scheduled tasks to synchronize the data of each sub-database to a centralized reconciliation database, the present application obtains database batch data by responding to batch reconciliation instructions; summarizes the database batch data to obtain first summary data to be checked; obtains second summary data to be checked, and checks the first summary data to be checked with the second summary data to be checked to determine the reconciliation result; if the reconciliation result is inconsistent, a detailed check is performed to confirm the difference data, and the first summary data to be checked is updated and supplemented based on the difference data, and the step of comparing the first summary data to be checked with the second summary data to be checked is returned until the check result is consistent, and the batch reconciliation result is confirmed to be balanced. It can be understood that the present application uses the summary database batch data for reconciliation, and when the reconciliation results are inconsistent, the reconciliation data is quickly aligned through the detailed check and supplement mechanism, thereby improving the reconciliation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0041] Figure 1 A flowchart of the first embodiment of the batch data reconciliation method of this application is provided;

[0042] Figure 2 A flow chart illustrating the second embodiment of the batch data reconciliation method of this application;

[0043] Figure 3 A schematic diagram of a simplified process of the batch data reconciliation method provided in Example 2 of this application;

[0044] Figure 4 This is a schematic diagram of the module structure of the batch data reconciliation device according to an embodiment of the present application;

[0045] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the batch data reconciliation method in the embodiment of the present application.

[0046] The purpose, features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0047] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0048] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0049] The main solutions of the embodiments of this application are:

[0050] Responding to a batch reconciliation instruction, obtaining database batch data;

[0051] Summarizing the batch data in the database to obtain first summary data to be verified;

[0052] Acquire the second summary data to be verified, and verify the first summary data to be verified with the second summary data to be verified to determine a verification result;

[0053] If the verification result is inconsistent, a detailed verification is performed to confirm the difference data, and the first summary data to be verified is updated and supplemented based on the difference data. The process returns to the step of comparing the first summary data to be verified with the second summary data to be verified, until the verification result is consistent, and the batch reconciliation result is confirmed to be balanced.

[0054] In this embodiment, the present application uses a batch data reconciliation device as the execution subject. For ease of description, it is specifically described below as "device".

[0055] Since the existing technology relies on scheduled tasks to synchronize the data of each sub-database to a centralized reconciliation database to check massive transaction data, there are significant defects.

[0056] The present application provides a solution, which obtains database batch data in response to a batch reconciliation instruction; summarizes the database batch data to obtain first summary data to be checked; obtains second summary data to be checked, and checks the first summary data to be checked with the second summary data to be checked to determine the reconciliation result; if the reconciliation result is inconsistent, a detailed check is performed to confirm the difference data, and the first summary data to be checked is updated and supplemented based on the difference data, and the step of comparing the first summary data to be checked with the second summary data to be checked is returned until the check result is consistent, and the batch reconciliation result is confirmed to be balanced. It can be understood that the present application uses the method of summarizing database batch data for reconciliation. When the reconciliation results are inconsistent, the reconciliation data is quickly aligned through the detailed check and supplement mechanism, thereby improving the reconciliation efficiency.

[0057] Based on this, the present application embodiment provides a batch data reconciliation method, referring to Figure 1 , Figure 1This is a flow chart of the first embodiment of the batch data reconciliation method of this application.

[0058] In this embodiment, the batch data reconciliation method includes steps S10 to S40:

[0059] Step S10, in response to the batch reconciliation instruction, obtaining batch data from the database;

[0060] In messaging systems, batch reconciliation instructions are typically triggered by a system schedule or initiated manually by an operator. Upon receiving this instruction, the system retrieves the batch data to be reconciled from multiple business sub-databases. These sub-databases are divided by business type, such as cross-border treasury business databases and domestic treasury business databases, and each sub-database stores transaction records for a specific business.

[0061] It should be noted that responding to a batch reconciliation instruction means that the system reacts to receiving a trigger signal for batch reconciliation and starts executing the reconciliation process. Batch reconciliation instructions are usually triggered by the system at a scheduled time or manually initiated by an operator.

[0062] Database batch data refers to the large amount of data stored in the database awaiting reconciliation. In messaging systems, this data is typically distributed across multiple business sub-databases, such as the cross-border treasury business database and the domestic treasury business database. Each sub-database stores transaction records for a specific business. This data needs to be aggregated and reconciled to ensure consistency between the system's internal data and external systems (such as the People's Bank of China).

[0063] Understandably, the process of acquiring batch data from the database needs to be efficient and accurate. The system uses a pre-set database connection pool to quickly connect to each shard and retrieve the required batch reconciliation data. This is intended to reduce data acquisition time and improve the efficiency of the entire reconciliation process.

[0064] In a feasible implementation, the step of obtaining database batch data in response to the batch reconciliation instruction includes:

[0065] Receive reconciliation messages from external systems and write them into the database;

[0066] After writing is completed, a response is returned immediately, and the batch reconciliation instruction is triggered through an asynchronous call mechanism to avoid occupying online database connection resources.

[0067] It's important to note that the asynchronous call mechanism means that after receiving a reconciliation message from an external system and writing it to the database, the system immediately returns a response to the external system without waiting for the reconciliation process to complete. This mechanism also triggers batch reconciliation instructions. This approach avoids consuming online database connection resources and improves system efficiency.

[0068] For example, suppose the messaging system receives a reconciliation message from the People's Bank of China. The system first receives the message and writes it to the database. After the write operation is complete, the system immediately returns a successful receipt response to the People's Bank of China, rather than waiting for the entire reconciliation process to complete. Simultaneously, the system triggers a batch reconciliation instruction through an asynchronous call mechanism, initiating the reconciliation process. This allows the reconciliation process to proceed in the background, without affecting external response speed or consuming online database connection resources, thus ensuring efficient system operation.

[0069] Step S20, summarizing the batch data in the database to obtain first summary data to be checked;

[0070] After acquiring batch data from each shard, the system needs to aggregate this data. The purpose of aggregation is to integrate the data scattered across different shards into a single, integrated view for comparison with data from external systems.

[0071] It should be noted that summarizing the batch data of the database involves summarizing the data of different business types separately according to the preset business classification rules. For example, cross-border capital business, domestic capital business, etc. each have their own aggregation logic. The system will classify and summarize the data according to these logics to generate a sub-database summary intermediate table. Summarization refers to the process of collecting and integrating scattered and detailed data to form a more concentrated and summarized data result. Here, the batch reconciliation data in each business sub-database is counted and merged according to certain rules and dimensions so that it can be presented in a more concise form to facilitate subsequent verification operations.

[0072] The first summary data to be verified is the preliminary data obtained after the aforementioned aggregation operation, used internally by the system for comparison and verification with external system data. It is the result of integrating batch data extracted from multiple sub-databases and contains aggregate information under specific business categories. This information will serve as one of the benchmark data in the subsequent verification process, and will be compared with the second summary data to be verified provided by the external system to determine data consistency or inconsistency.

[0073] It's understandable that by parallelizing the batch reconciliation data from pre-configured databases for each business category, aggregation efficiency can be significantly improved. This parallel processing approach fully leverages the advantages of a multi-shard database architecture, allowing data aggregation operations to be performed simultaneously across all shards, thereby shortening the overall aggregation process.

[0074] In a feasible implementation manner, the step of aggregating the database batch data to obtain first aggregated data to be verified includes:

[0075] According to the preset business classification, the batch reconciliation data in the pre-configured database of each business classification is summarized in parallel, and the summarized batch reconciliation data is stored in the preset sub-database summary intermediate table;

[0076] The batch reconciliation data in the sub-library summary intermediate table is summarized to obtain first summary data to be checked.

[0077] It should be noted that the preset business categories are based on the business types in the message system. Common examples include cross-border treasury business, domestic treasury business, and information business. Each business type has its own specific processing logic and data characteristics. The system manages and aggregates data based on these preset business categories.

[0078] Parallel aggregation refers to the simultaneous execution of database aggregation operations for different business categories. Using multi-threading or multi-process technology, multiple aggregation tasks can be executed simultaneously, thereby improving aggregation efficiency and shortening aggregation time.

[0079] Pre-configured databases are specific databases designated for different business categories. These databases are determined during system initialization, and each database stores transaction records for a specific type of business.

[0080] The intermediate table for shard summary is used to store aggregated data from each business shard. This table only stores shard statistics and does not retain original transaction details. This reduces data storage and improves data processing efficiency.

[0081] For example, let's assume the messaging system has three business sub-databases: a cross-border treasury database, a domestic treasury database, and an information database. The system pre-configures the connection information for these three databases and, before aggregation begins, sets up three parallel aggregation tasks based on the business type.

[0082] When the system receives a batch reconciliation instruction, it first initiates three parallel aggregation tasks based on pre-defined business categories, simultaneously aggregating data from the three business sub-databases. Each task reads data from its corresponding database, calculates summary information for that business sub-database (such as total transaction amount, number of transactions, etc.), and stores this summary information in its respective sub-database summary intermediate table.

[0083] Finally, the system summarizes the data in the intermediate tables of the three sub-databases to obtain the first summary data to be verified, which is used for comparison and verification with the second summary data to be verified in the external system.

[0084] In a feasible embodiment, the steps of aggregating batch reconciliation data in pre-configured databases for each business classification in parallel according to the preset business classification, and storing the aggregated batch reconciliation data in a preset sub-library summary intermediate table include:

[0085] Through the preset database connection pool, dynamically switch the business sub-database corresponding to the preset business classification;

[0086] Without pre-synchronizing the full verification data to the centralized storage, perform real-time statistical operations on each of the business sub-databases and generate sub-database summary data in parallel;

[0087] The sub-library summary data is written into the sub-library summary intermediate table, wherein the intermediate table only stores the sub-library statistical values ​​without retaining the original transaction details.

[0088] It should be noted that the preset database connection pool is a collection of database connection resources preconfigured by the system. The connection pool manages the creation, allocation, and release of database connections, improving database access efficiency and reducing the overhead of frequent connection creation and closure. Dynamic switching allows flexible switching between different business sub-databases based on business classification. The system selects the corresponding business sub-database for data access based on pre-set mappings. Business sub-databases are databases divided by business type and used to store transaction records for specific businesses. For example, cross-border treasury business databases and domestic treasury business databases. Failure to pre-synchronize full reconciliation data to centralized storage means that reconciliation data is not synchronized to a centralized repository beforehand. This reduces redundant storage and saves storage space. Real-time statistical operations perform statistical calculations directly on the business sub-databases as data is acquired, rather than relying on pre-stored summary data. This approach ensures real-time and accurate data. Sub-database summary data is aggregated from each business sub-database, reflecting aggregated business information for that sub-database, such as total transaction amount and total number of transactions. The sub-database summary intermediate table is an intermediate table used to store the summary data of each business sub-database. It only provides basic data for subsequent summary operations and does not retain the original transaction details.

[0089] For example, referring to Figure 2 , assuming that there are four business sub-databases in the message system, namely the cross-border fund business database, the domestic fund business database, the domestic agreement business database and the overseas agreement business database. The system pre-configures the connection pools for these four databases and establishes a mapping relationship between business classifications and sub-databases. When the batch reconciliation instruction is triggered, the system obtains connection resources according to the preset database connection pool, and then dynamically switches to the cross-border fund business database, performs real-time statistical operations, and obtains the summary data of the sub-database, such as the total transaction amount is 10 million yuan and the total number of transactions is 1,000. Afterwards, these summary data are written into the sub-database summary intermediate table (i.e., the reconciliation database). Next, the system repeats this process, and performs summary statistics on the domestic fund business database, the domestic agreement business database and the overseas agreement business database respectively, and writes the results into the intermediate table. Finally, the system summarizes the data in the intermediate table to obtain the first summary data to be checked, which is used for comparison and verification with the second summary data to be checked issued by the clearing center.

[0090] Step S30, obtaining second summary data to be verified, and verifying the first summary data to be verified with the second summary data to be verified to determine a verification result;

[0091] The second summary data to be reconciled typically comes from an external system, such as the People's Bank of China's reconciliation data. The system needs to compare the first summary data to be reconciled, generated internally, with the second summary data to be reconciled from the external system, item by item, to check for any discrepancies.

[0092] It should be noted that the second summary data to be verified usually refers to the summary data obtained from an external system (such as the People's Bank of China), which is used to compare and verify with the first summary data to be verified within the system. It contains the total transaction information recorded by the external system and is the benchmark data for verifying the accuracy and completeness of the data within the system. Verification refers to the process of comparing and verifying the first summary data to be verified within the system with the second external summary data to be verified. By comparing key information such as the number of transactions, amount, and status between the two, it is determined whether the data is consistent, so as to find out possible differences and problems. The verification result is the conclusion drawn after the verification process, indicating whether the first summary data to be verified is consistent with the second summary data to be verified. The verification result can be "consistent", indicating that the data verification has passed and the internal data of the system is consistent with the external data; it can also be "inconsistent", indicating that there are differences and further detailed verification and processing are required.

[0093] Understandably, the verification process needs to be precise and efficient. Using pre-set verification rules, the system compares key information such as transaction counts, amounts, and status between the two sets of data. If any discrepancies are found, further analysis is required to determine the cause of the discrepancy.

[0094] In step S40, if the verification result is inconsistent, a detailed verification is performed to confirm the difference data, and the first summary data to be verified is updated and supplemented based on the difference data. The process returns to the step of comparing the first summary data to be verified with the second summary data to be verified until the verification result is consistent and the batch reconciliation result is confirmed to be balanced.

[0095] If the summary data is inconsistent, the system automatically enters the detailed verification stage. At this time, the system will compare the detailed information of each transaction in detail to find the specific data records with discrepancies.

[0096] It's important to note that detailed verification involves comparing and checking the detailed information of each transaction item by item if the summary verification results are inconsistent. The purpose of detailed verification is to identify specific discrepancies in the data records so that subsequent processing and adjustments can be made to ensure data accuracy and consistency.

[0097] Discrepant data refers to inconsistent transaction records between the system's internal first-pending-check summary data and the external second-pending-check summary data during the verification process. This data may contain discrepancies in transaction status, transaction amount, transaction time, and other aspects, requiring further analysis and resolution.

[0098] Updates and supplements refer to modifying and supplementing the first pending verification summary data within the system based on the discrepancies identified during detailed verification. This may include adjusting transaction status and supplementing missing transaction records to ensure consistency between internal and external data.

[0099] Reconciliation means that after a series of verifications and adjustments, the first summary data to be reconciled within the system is completely consistent with the second summary data to be reconciled externally, confirming that the batch reconciliation result is reconciled. Reconciliation signifies the successful completion of the reconciliation process, achieving business and financial balance and consistency between the internal and external system data.

[0100] As you can understand, after identifying discrepancies, the system will update or supplement the internal summary data according to pre-set rules. For example, if the status of a transaction in the internal system is found to be inconsistent with the external system, the system will automatically adjust the internal status to match the external system record. After the adjustment is completed, the system will re-compare the summary data until the two are consistent, and finally confirm the batch reconciliation results as balanced. This cyclical reconciliation mechanism ensures the accuracy and thoroughness of reconciliation.

[0101] In a feasible implementation, the steps of performing detailed verification, confirming difference data, and updating and supplementing the first summary data to be verified based on the difference data include:

[0102] If the transaction status in the second summary data to be verified is inconsistent with the transaction status in the first summary data to be verified, automatically adjusting the transaction status of the first summary data to be verified to the transaction status of the second summary data to be verified;

[0103] If the amount of the second summary data to be verified is greater than the amount of the first summary data to be verified, the operator's reissue process is triggered.

[0104] It should be noted that the transaction status refers to the processing status of the transaction in the system, such as successful, failed, pending confirmation, etc. Different transaction statuses reflect the status of the transaction at different stages.

[0105] Data volume refers to the amount of data, usually measured by the number of data items or records. In the reconciliation scenario, data volume can refer to the number of transaction records.

[0106] Automatic adjustment means that the system automatically modifies information such as transaction status according to preset rules to ensure that internal data is consistent with external data.

[0107] The reissue process is triggered when missing internal data is discovered, and the missing data is retrieved from the external system. This usually requires application and coordination by operations personnel.

[0108] For example, assume that during the reconciliation process, the system discovers inconsistencies between the internal first summary data to be reconciled and the external second summary data to be reconciled:

[0109] If the transaction status in the external system is "Successful" but in the internal system is "Pending Confirmation," the system will automatically adjust the internal system's status to "Successful" to maintain consistency with the external system. For example, if a cross-border fund transaction is displayed as "Successful" in the PBOC system but "Pending Confirmation" in the internal system due to network latency or other reasons, the system will automatically adjust the internal status to "Successful."

[0110] If the amount of data in the external system exceeds that in the internal system, this indicates missing data in the internal system. In this case, the system triggers a reissue process, prompting operations staff to request reissue of the missing transaction data from the external system. For example, if the PBOC system records 100 transactions, but the internal system, for some reason, only records 90, the system triggers a reissue process, and operations staff then request reissue of the missing 10 transactions from the PBOC.

[0111] In a feasible implementation manner, after the step of triggering the operator reissue process, the following steps are further included:

[0112] Obtain detailed data of reissues from the external system through the preset batch reissue synchronization application;

[0113] Synchronize the reissued detailed data to the preset reconciliation cluster database;

[0114] The detailed verification process is re-executed based on the reissued detailed data until the first summary data to be verified is consistent with the second summary data to be verified.

[0115] It's important to note that the pre-configured batch reissue synchronization application is a pre-configured application within the system specifically designed to handle synchronization operations during data reissue. It's responsible for obtaining reissued details from the external system and synchronizing them with the internal reconciliation cluster database.

[0116] The detailed data reissued by the external system refers to the detailed transaction records provided by the external system (such as the People's Bank of China) when reissuing the data missing from the internal system during the data verification process.

[0117] The reconciliation cluster database refers to a database cluster used to store reconciliation-related data. It has high availability and scalability, can handle the storage and query of large-scale data, and is the basic data platform for data verification and adjustment.

[0118] For example, referring to Figure 3 During the reconciliation process, the system discovered that there were discrepancies between the internal data and the external system data, and that the amount of data in the external system was larger than that in the internal system. This triggered the reissue process. Assume that the external system reissued three missing transaction details. The preset batch reissue synchronization application received the three details reissued by the external system, and performed parsing and verification to ensure the integrity and accuracy of the data. These three reissued details were synchronized to the internal reconciliation cluster database. After the synchronization operation was completed, the data in the reconciliation cluster database was updated to include the latest reissued data. Based on the reissued data, the system restarted the detail reconciliation process. At this point, the first summary data to be reconciled in the internal system included the three reissued records, which were re-compared with the second summary data to be reconciled in the external system. If the data is consistent, the batch reconciliation result is confirmed to be settled; if there are still differences, the corresponding processing continues until the data is consistent.

[0119] In a feasible implementation manner, if the verification result is inconsistent, the step of performing detailed verification further includes:

[0120] The comprehensive query front end provides operators with a visual operation interface, which includes:

[0121] Check the abnormal data display module, which is used to classify and display detailed records of inconsistent status, missing data and redundant data;

[0122] A manual account adjustment operation module supports manual adjustment of the transaction status in the first summary data to be verified;

[0123] The reissue instruction initiation module is used to initiate a data reissue request for a specified transaction to an external system;

[0124] The check restart trigger module re-executes the step of checking the first summary data to be checked with the second summary data to be checked if a manual intervention operation is detected.

[0125] It should be noted that the comprehensive query front-end refers to the front-end system that provides operators with a data query and operation interface. Operators can use this interface to query and display abnormal data, manually adjust accounts, and initiate reissue instructions.

[0126] The abnormal data display module is used to display detailed records of inconsistent status, missing data, and redundant data. This module helps operators quickly locate and view detailed information about abnormal data.

[0127] The Manual Account Adjustment module allows operators to manually adjust the transaction status in the first pending verification summary. This module allows operators to manually intervene when the system cannot automatically handle certain exceptions.

[0128] The Reissue Initiation Module is used to initiate a data reissue request to an external system for a specific transaction. When data in the internal system is missing, operators can use this module to request that the external system reissue the data.

[0129] The Verification Restart Trigger Module is used to re-compare the first summary data to be verified with the second summary data to be verified after manual intervention. This module ensures that after manual adjustment or reissue of data, re-verification is performed to verify data consistency.

[0130] For example, suppose that during the reconciliation process, the system discovers anomalies in some cross-border funds transaction data, manifested as inconsistent transaction status and missing data. An operator performs the following operations through the comprehensive query front-end: The operator logs in to the front-end and accesses the reconciliation anomaly data display module. The operator discovers that the status of 10 transactions is inconsistent between the internal and external systems, including five transactions missing from the internal system. For these five inconsistent transactions, the operator uses the manual reconciliation module to manually adjust the transaction status in the internal system to be consistent with the external system. For the five missing transactions, the operator uses the reissue instruction initiation module to request reissue of these transaction data from the external system. Upon receiving the reissue request, the external system reissues the missing data for the five transactions to the internal system. The pre-configured batch reissue synchronization application synchronizes this reissued data to the reconciliation cluster database. The operator uses the reconciliation restart trigger module to re-execute the reconciliation process. The system compares the updated first pending reconciliation summary data with the second pending reconciliation summary data to confirm data consistency. If the data is consistent, the batch reconciliation result is confirmed as balanced; if there are still differences, the operator will continue to perform corresponding processing.

[0131] Through the above operations, operators can effectively handle verification anomalies and ensure the accuracy and consistency of system data.

[0132] This embodiment provides a batch data reconciliation method that uses batch data from a summary database for reconciliation. When the reconciliation results are inconsistent, the reconciliation data is quickly aligned through a detailed reconciliation and supplementation mechanism, thereby improving reconciliation efficiency.

[0133] It should be noted that the above examples are only used to understand this application and do not constitute a limitation on the batch data reconciliation method of this application. More simple transformations based on this technical concept are all within the scope of protection of this application.

[0134] This application also provides a batch data reconciliation device, please refer to Figure 4 , the batch data reconciliation device includes:

[0135] An acquisition module, configured to acquire batch data from a database in response to a batch reconciliation instruction;

[0136] A summarizing module, configured to summarize the batch data in the database to obtain first summary data to be checked;

[0137] a checking module, configured to obtain the second summary data to be checked, and check the first summary data to be checked with the second summary data to be checked to determine a checking result;

[0138] The reconciliation module is used to perform detailed verification if the verification result is inconsistent, confirm the difference data, and update and supplement the first summary data to be verified based on the difference data, and return to the step of comparing the first summary data to be verified with the second summary data to be verified until the verification result is consistent and the batch reconciliation result is confirmed to be balanced.

[0139] And / or, the summarizing module includes:

[0140] A first aggregation module is configured to aggregate, in parallel, batch reconciliation data in pre-configured databases for each business classification according to the preset business classification, and store the aggregated batch reconciliation data in a preset sub-database aggregation intermediate table;

[0141] The second summarizing module is used to summarize the batch reconciliation data in the sub-library summary intermediate table to obtain first summary data to be checked.

[0142] And / or, the first aggregation module includes:

[0143] The first switching module is used to dynamically switch the business sub-database corresponding to the preset business classification through the preset database connection pool;

[0144] The first statistical module is used to perform real-time statistical operations on each of the business sub-databases and generate sub-database summary data in parallel without pre-synchronizing the full verification data to the centralized storage;

[0145] The first writing module is used to write the sub-library summary data into the sub-library summary intermediate table, wherein the intermediate table only stores the sub-library statistical values ​​without retaining the original transaction details.

[0146] And / or, the reconciliation module includes:

[0147] a first adjustment module configured to automatically adjust the transaction status of the first summary data to be verified to the transaction status of the second summary data to be verified if the transaction status in the second summary data to be verified is inconsistent with the transaction status in the first summary data to be verified;

[0148] The first reissuing module is configured to trigger a reissuing process for an operator if the amount of the second summary data to be verified is greater than the amount of the first summary data to be verified.

[0149] And / or, the first reissue module includes:

[0150] The first acquisition module is used to obtain the detailed data of reissues from the external system through a preset batch reissue synchronization application;

[0151] A first synchronization module is used to synchronize the reissued detailed data to a preset reconciliation cluster database;

[0152] The first loop module is used to re-execute the detailed verification process based on the reissued detailed data until the first summary data to be verified is consistent with the second summary data to be verified.

[0153] And / or, the batch data reconciliation device includes:

[0154] The comprehensive query front end provides operators with a visual operation interface, which includes:

[0155] Check the abnormal data display module, which is used to classify and display detailed records of inconsistent status, missing data and redundant data;

[0156] A manual account adjustment operation module, used to support manual adjustment of the transaction status in the first summary data to be verified;

[0157] The reissue instruction initiation module is used to initiate a data reissue request for a specified transaction to an external system;

[0158] The verification restart trigger module is used to re-execute the step of verifying the first summary data to be verified with the second summary data to be verified if a manual intervention operation is detected.

[0159] And / or, the acquisition module includes:

[0160] The second writing module is used to receive the reconciliation message sent by the external system and write it into the database;

[0161] The first trigger module is configured to return a response immediately after writing is completed, and trigger the batch reconciliation instruction through an asynchronous call mechanism to avoid occupying online database connection resources.

[0162] The batch data reconciliation device provided in this application, employing the batch data reconciliation method of the aforementioned embodiment, can address the technical issue of low financial message reconciliation efficiency. Compared to the prior art, the batch data reconciliation device provided in this application has the same beneficial effects as the batch data reconciliation method of the aforementioned embodiment. Other technical features of the batch data reconciliation device are the same as those disclosed in the aforementioned embodiment and are not further elaborated here.

[0163] The present application provides a batch data reconciliation device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the batch data reconciliation method in the above-mentioned embodiment 1.

[0164] Reference below Figure 5 , which shows a schematic diagram of the structure of a batch data reconciliation device suitable for implementing the embodiments of the present application. The batch data reconciliation device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, tablet computers, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital televisions and desktop computers. Figure 5 The batch data reconciliation device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0165] like Figure 5As shown, the batch data reconciliation device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 1002 or programs loaded from a storage device 1003 into a random access memory (RAM) 1004. RAM 1004 also stores various programs and data required for the operation of the batch data reconciliation device. Processing device 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to I / O interface 1006: input device 1007, such as a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output device 1008, such as a liquid crystal display (LCD), speaker, vibrator, etc.; storage device 1003, such as a magnetic tape or hard disk; and communication device 1009. The communication device 1009 can allow the batch data reconciliation device to communicate with other devices wirelessly or by wire to exchange data. Although the figures show a batch data reconciliation device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented or have alternatively.

[0166] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0167] The batch data reconciliation device provided in this application, employing the batch data reconciliation method of the aforementioned embodiment, can resolve the technical problem of low reconciliation efficiency in financial messages. Compared to the prior art, the batch data reconciliation device provided in this application has the same beneficial effects as the batch data reconciliation method provided in the aforementioned embodiment. Other technical features of the batch data reconciliation device are the same as those disclosed in the aforementioned embodiment and are not further described here.

[0168] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0169] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0170] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, a computer program) stored thereon, the computer-readable program instructions being used to execute the batch data reconciliation method in the above-mentioned embodiment.

[0171] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0172] The computer-readable storage medium may be included in the batch data reconciliation device, or may exist independently without being incorporated into the batch data reconciliation device.

[0173] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the batch data reconciliation device, the batch data reconciliation device: obtains database batch data in response to the batch reconciliation instruction;

[0174] Summarizing the batch data in the database to obtain first summary data to be verified;

[0175] Acquire the second summary data to be verified, and verify the first summary data to be verified with the second summary data to be verified to determine a verification result;

[0176] If the verification result is inconsistent, a detailed verification is performed to confirm the difference data, and the first summary data to be verified is updated and supplemented based on the difference data. The process returns to the step of comparing the first summary data to be verified with the second summary data to be verified, until the verification result is consistent, and the batch reconciliation result is confirmed to be balanced.

[0177] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0178] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0179] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.

[0180] The computer-readable storage medium provided in this application stores computer-readable program instructions (i.e., a computer program) for executing the aforementioned batch data reconciliation method, thereby resolving the technical issue of low financial message reconciliation efficiency. Compared to the prior art, the beneficial effects of the computer-readable storage medium provided in this application are similar to those of the batch data reconciliation method provided in the aforementioned embodiments, and are not further elaborated here.

[0181] The present application also provides a computer program product, including a computer program, which implements the steps of the batch data reconciliation method as described above when executed by a processor.

[0182] The computer program product provided in this application can solve the technical problem of low reconciliation efficiency of financial messages. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the batch data reconciliation method provided in the above embodiment, and will not be repeated here.

[0183] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A batch data reconciliation method, characterized in that: The method includes: Responding to a batch reconciliation instruction, obtaining database batch data; Summarizing the batch data in the database to obtain first summary data to be verified; Acquire the second summary data to be verified, and verify the first summary data to be verified with the second summary data to be verified to determine a verification result; If the verification result is inconsistent, a detailed verification is performed to confirm the difference data, and the first summary data to be verified is updated and supplemented based on the difference data. The process returns to the step of comparing the first summary data to be verified with the second summary data to be verified, until the verification result is consistent, and the batch reconciliation result is confirmed to be balanced.

2. The method according to claim 1, wherein The step of aggregating the database batch data to obtain first aggregated data to be checked includes: According to the preset business classification, the batch reconciliation data in the pre-configured database of each business classification is summarized in parallel, and the summarized batch reconciliation data is stored in the preset sub-database summary intermediate table; The batch reconciliation data in the sub-library summary intermediate table is summarized to obtain first summary data to be checked.

3. The method according to claim 2, wherein The step of aggregating the batch reconciliation data in the pre-configured databases for each business classification in parallel according to the preset business classification, and storing the aggregated batch reconciliation data in the preset sub-database summary intermediate table includes: Through the preset database connection pool, dynamically switch the business sub-database corresponding to the preset business classification; Without pre-synchronizing the full verification data to the centralized storage, perform real-time statistical operations on each of the business sub-databases and generate sub-database summary data in parallel; The sub-library summary data is written into the sub-library summary intermediate table, wherein the intermediate table only stores the sub-library statistical values ​​without retaining the original transaction details.

4. The method according to claim 1, wherein The steps of performing detailed verification, confirming difference data, and updating and supplementing the first summary data to be verified based on the difference data include: If the transaction status in the second summary data to be verified is inconsistent with the transaction status in the first summary data to be verified, automatically adjusting the transaction status of the first summary data to be verified to the transaction status of the second summary data to be verified; If the amount of the second summary data to be verified is greater than the amount of the first summary data to be verified, the operator's reissue process is triggered.

5. The method according to claim 4, wherein The step of triggering the operator reissue process also includes: Obtain detailed data of reissues from the external system through the preset batch reissue synchronization application; Synchronize the reissued detailed data to the preset reconciliation cluster database; The detailed verification process is re-executed based on the reissued detailed data until the first summary data to be verified is consistent with the second summary data to be verified.

6. The method according to claim 1, wherein If the verification result is inconsistent, the detailed verification step further includes: The comprehensive query front end provides operators with a visual operation interface, which includes: Check the abnormal data display module, which is used to classify and display detailed records of inconsistent status, missing data and redundant data; A manual account adjustment operation module supports manual adjustment of the transaction status in the first summary data to be verified; The reissue instruction initiation module is used to initiate a data reissue request for a specified transaction to an external system; The check restart trigger module re-executes the step of checking the first summary data to be checked with the second summary data to be checked if a manual intervention operation is detected.

7. The method according to claim 1, wherein The step of obtaining database batch data in response to the batch reconciliation instruction includes: Receive reconciliation messages from external systems and write them into the database; After writing is completed, a response is returned immediately, and the batch reconciliation instruction is triggered through an asynchronous call mechanism to avoid occupying online database connection resources.

8. A batch data reconciliation device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the batch data reconciliation method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the batch data reconciliation method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the batch data reconciliation method according to any one of claims 1 to 6 are implemented.

Images