A method and device for processing reconciliation data

Abstract

This invention discloses a method and apparatus for processing reconciliation data, relating to the field of computer technology. One specific implementation of the method includes: after receiving a reconciliation file sent by a first reconciliation end, parsing the reconciliation file to obtain transaction detail data; and after receiving business data sent by a second reconciliation end, performing object conversion processing on the business data to obtain converted business objects; scanning for transaction objects currently in an unverified state, generating a reconciliation message queue (MQ) message, and determining the target reconciliation end corresponding to the transaction object; sending the reconciliation MQ message to the target reconciliation end for reconciliation processing, receiving the reconciliation result returned by the target reconciliation end, and changing the status of the transaction detail data and business objects verified this time to "verified". This implementation is based on a message-driven approach, concurrently verifying data to improve verification efficiency, while ensuring that the entire reconciliation process is efficient and the results are reliable.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for processing reconciliation data. Background Technology

[0002] To expand transaction scenarios, some lending companies are partnering with banks. This partnership involves users linking virtual bank savings cards to payment channels for spending, transfers, and top-ups, which deduct from the user's available credit limit. To ensure the consistency of transaction information and the accuracy of the deducted amounts, it is necessary to regularly reconcile transaction data between the bank and the lending company.

[0003] Traditional data reconciliation methods typically involve banks providing reconciliation files, which are then imported into a database and reconciled line by line with the lending company's transaction records. This process is time-consuming if the files are large, and currently, the reconciliation results are not displayed on the backend page. While some reconciliation methods exist to improve efficiency and flexibility, these methods suffer from at least the following problems:

[0004] 1. The reconciliation files need to be sorted based on keywords, which affects efficiency to some extent; it cannot support reconciliation files of multiple business types, and the reconciliation fields cannot be parameterized.

[0005] 2. The original reconciliation file needs to be processed again, which is inefficient; it relies too much on Redis (a key-value database) middleware, which is risky and there is no risk mitigation solution; when the reconciliation file is large, it is easy to cause Redis memory shortage, leading to reconciliation errors and reconciliation anomalies. Summary of the Invention

[0006] In view of this, embodiments of the present invention provide a method and apparatus for processing reconciliation data, which can at least solve the problem of low reconciliation efficiency and flexibility in the prior art.

[0007] To achieve the above objectives, according to one aspect of the present invention, a reconciliation data processing method is provided, applied to a reconciliation system, wherein the reconciliation system is communicatively connected to a first reconciliation terminal and a second reconciliation terminal, comprising:

[0008] After listening to the reconciliation file sent by the first reconciliation end, the reconciliation file is parsed to obtain transaction detail data; and after listening to the business data sent by the second reconciliation end, the business data is processed by object conversion to obtain the converted business object.

[0009] Scan for transaction objects whose current status is unverified, generate a reconciliation message queue (MQ) message, and determine the target reconciliation end corresponding to the transaction object; wherein, the transaction object includes at least one of the transaction detail data and the business object;

[0010] Send a reconciliation MQ message to the target reconciliation terminal for reconciliation processing, receive the reconciliation result returned by the target reconciliation terminal, and change the status of the transaction details data and business objects verified this time to "verified".

[0011] Optionally, the reconciliation system further includes a reconciliation database for storing reconciliation file detail tables and transaction record detail tables. The reconciliation file detail tables are used to store transaction detail data, and the transaction record detail tables are used to store business objects.

[0012] After listening to the reconciliation file sent by the first reconciliation end, it also includes:

[0013] Based on the filename of the reconciliation file, a duplicate check is performed in the cache. If the check result indicates that a duplicate exists, the reconciliation process is stopped; and

[0014] Based on the filename of the reconciliation file, a duplicate filename check is performed in the reconciliation filename table of the reconciliation database. If the check result shows that a duplicate file exists, the reconciliation process is stopped.

[0015] Optional, also includes:

[0016] In response to the detection of a reconciliation file in a preset directory on the server, the system determines the local temporary directory corresponding to the first reconciliation end, downloads the reconciliation file to the local temporary directory, and uploads it to cloud storage; and

[0017] After detecting that the reconciliation file has been verified, the reconciliation file in the local temporary directory is deleted.

[0018] Optionally, parsing the reconciliation file includes:

[0019] The reconciliation file is parsed to obtain the header information and other line information. The total number of transactions and the total transaction amount recorded in the header information are compared with the sum of the number of transactions and the transaction amount recorded in the other line information. If the comparison results are the same, the reconciliation file is determined to be usable; otherwise, it is unusable.

[0020] Optionally, sending the reconciliation MQ message to the target reconciliation client for reconciliation processing and receiving the reconciliation result returned by the target reconciliation client includes performing at least one of the following steps:

[0021] In response to the reconciliation MQ message containing transaction details data, the reconciliation MQ message is sent to the first reconciliation end. After listening to the reconciliation MQ message, the first reconciliation end obtains the business object corresponding to the first transaction serial number in the second reconciliation end based on the first transaction serial number in the transaction details data, and verifies whether the data in the business object is consistent with the transaction details data according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end.

[0022] In response to the reconciliation MQ message containing a business object, the reconciliation MQ message is sent to the second reconciliation end. After listening to the reconciliation MQ message, the second reconciliation end retrieves the transaction details data corresponding to the second transaction serial number in the first reconciliation end based on the second transaction serial number in the business object. Then, based on the pre-configured reconciliation fields, it verifies whether the data in the business object and the transaction details data are consistent and receives the reconciliation result returned by the second reconciliation end.

[0023] Optionally, sending the reconciliation MQ message to the target reconciliation client for reconciliation processing and receiving the reconciliation result returned by the target reconciliation client includes performing at least one of the following steps:

[0024] In response to the reconciliation MQ message containing transaction details data and the business object corresponding to the transaction serial number in the transaction details data, the reconciliation MQ message is sent to the first reconciliation end, so that after listening to the reconciliation MQ message, the first reconciliation end checks whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end.

[0025] In response to a reconciliation MQ message containing a business object and transaction details data corresponding to the transaction serial number in the business object, the reconciliation MQ message is sent to the second reconciliation end. This allows the second reconciliation end to verify the consistency between the data in the business object and the transaction details data based on the pre-configured reconciliation fields after listening to the reconciliation MQ message, and then receive the reconciliation result returned by the second reconciliation end.

[0026] To achieve the above objectives, according to another aspect of the present invention, a reconciliation data processing apparatus is provided, applied to a reconciliation system, the reconciliation system being communicatively connected to a first reconciliation terminal and a second reconciliation terminal, comprising:

[0027] The reconciliation file receiving module is used to parse the reconciliation file sent by the first reconciliation end after listening to it, and obtain transaction detail data.

[0028] The business data receiving module is used to perform object conversion processing on the business data sent by the second reconciliation terminal after listening to it, so as to obtain the converted business object.

[0029] The scanning module is used to scan for transaction objects whose current status is unverified, generate a reconciliation message queue (MQ) message, and determine the target reconciliation end corresponding to the transaction object; wherein, the transaction object includes at least one of the transaction detail data and the business object;

[0030] The processing module is used to send the reconciliation MQ message to the target reconciliation terminal for reconciliation processing, receive the reconciliation result returned by the target reconciliation terminal, and change the status of the transaction details data and business objects verified this time to "verified".

[0031] Optionally, the reconciliation system further includes a reconciliation database for storing reconciliation file detail tables and transaction record detail tables. The reconciliation file detail tables are used to store transaction detail data, and the transaction record detail tables are used to store business objects.

[0032] The reconciliation file receiving module is also used for:

[0033] Based on the filename of the reconciliation file, a duplicate check is performed in the cache. If the check result indicates that a duplicate exists, the reconciliation process is stopped; and

[0034] Based on the filename of the reconciliation file, a duplicate filename check is performed in the reconciliation filename table of the reconciliation database. If the check result shows that a duplicate file exists, the reconciliation process is stopped.

[0035] Optionally, the reconciliation file receiving module is further configured to:

[0036] In response to the detection of a reconciliation file in a preset directory on the server, the system determines the local temporary directory corresponding to the first reconciliation end, downloads the reconciliation file to the local temporary directory, and uploads it to cloud storage; and

[0037] After detecting that the reconciliation file has been verified, the reconciliation file in the local temporary directory is deleted.

[0038] Optionally, the reconciliation file receiving module is used for:

[0039] The reconciliation file is parsed to obtain the header information and other line information. The total number of transactions and the total transaction amount recorded in the header information are compared with the sum of the number of transactions and the transaction amount recorded in the other line information. If the comparison results are the same, the reconciliation file is determined to be usable; otherwise, it is unusable.

[0040] Optionally, the processing module is configured to perform at least one of the following steps:

[0041] In response to the reconciliation MQ message containing transaction details data, the reconciliation MQ message is sent to the first reconciliation end. After listening to the reconciliation MQ message, the first reconciliation end obtains the business object corresponding to the first transaction serial number in the second reconciliation end based on the first transaction serial number in the transaction details data, and verifies whether the data in the business object is consistent with the transaction details data according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end.

[0042] In response to the reconciliation MQ message containing a business object, the reconciliation MQ message is sent to the second reconciliation end. After listening to the reconciliation MQ message, the second reconciliation end retrieves the transaction details data corresponding to the second transaction serial number in the first reconciliation end based on the second transaction serial number in the business object. Then, based on the pre-configured reconciliation fields, it verifies whether the data in the business object and the transaction details data are consistent and receives the reconciliation result returned by the second reconciliation end.

[0043] Optionally, the processing module is configured to perform at least one of the following steps:

[0044] In response to the reconciliation MQ message containing transaction details data and the business object corresponding to the transaction serial number in the transaction details data, the reconciliation MQ message is sent to the first reconciliation end, so that after listening to the reconciliation MQ message, the first reconciliation end checks whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end.

[0045] In response to a reconciliation MQ message containing a business object and transaction detail data corresponding to the transaction serial number in the business object, the reconciliation MQ message is sent to the second reconciliation client. This allows the second reconciliation client, upon receiving the reconciliation MQ message, to verify the consistency between the data in the business object and the transaction detail data based on pre-configured reconciliation fields, and then receive the reconciliation result returned by the second reconciliation client. The reconciliation file receiving module is further configured to...

[0046] To achieve the above objectives, according to another aspect of the present invention, an electronic reconciliation device is provided.

[0047] The electronic device of this invention includes: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement any of the above-described reconciliation data processing methods.

[0048] To achieve the above objectives, according to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements any of the above-described reconciliation data processing methods.

[0049] According to the solution provided by the present invention, one embodiment of the above invention has the following advantages or beneficial effects: when the bank-side file is monitored, it is parsed and written into the reconciliation file detail table; after monitoring the business MQ message, it is written into the transaction detail table; and the two tables are scanned periodically to query the transaction objects whose status is unverified, thereby enabling the corresponding target reconciliation end to perform reconciliation processing on the transaction objects. In this way, the parallel processing batch is improved based on the message-driven method, the reconciliation efficiency is improved, and the batch size is configurable, avoiding the problem of reconciliation being impossible due to excessively large files.

[0050] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0051] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0052] Figure 1 This is a schematic diagram of the main flow of a reconciliation data processing method according to an embodiment of the present invention;

[0053] Figure 2 This is a flowchart illustrating a specific reconciliation data processing method according to an embodiment of the present invention;

[0054] Figure 3 This is a flowchart illustrating another specific reconciliation data processing method according to an embodiment of the present invention;

[0055] Figure 4 This is a schematic diagram of the main modules of an account reconciliation data processing device according to an embodiment of the present invention;

[0056] Figure 5 This is a diagram showing the connection relationships between modules;

[0057] Figure 6 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0058] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing the embodiments of the present invention, such as a mobile device or server. Detailed Implementation

[0059] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0060] The following are explanations of the terms used in this plan:

[0061] A CRON expression is a string, which is separated by 5 or 6 spaces and divided into 6 or 7 fields, each field representing a meaning.

[0062] Redis is an open-source, network-enabled, in-memory or persistent, log-structured key-value database written in ANSI C, which provides APIs for multiple languages.

[0063] Message queue (MQ): A method of communication between applications.

[0064] See Figure 1 The diagram shows the main flowchart of a reconciliation data processing method provided by an embodiment of the present invention, which includes the following steps:

[0065] S101: After listening to the reconciliation file sent by the first reconciliation end, parse the reconciliation file to obtain transaction detail data;

[0066] S102: After listening to the business data sent by the second reconciliation terminal, the business data is processed by object conversion to obtain the converted business object;

[0067] S103: Scan for transaction objects whose current status is unverified, generate a reconciliation message queue (MQ) message, and determine the target reconciliation end corresponding to the transaction object; wherein, the transaction object includes at least one of the transaction detail data and the business object;

[0068] S104: Send the reconciliation MQ message to the target reconciliation terminal for reconciliation processing, receive the reconciliation result returned by the target reconciliation terminal, and change the status of the transaction details data and business object verified this time to "verified".

[0069] In the above implementation, for step S101, this solution uses the bank side as the first reconciliation end and the business side as the second reconciliation end as an example for explanation. Both interact with the reconciliation system. The bank side uploads the reconciliation file to the SFTP (Secure File Transfer Protocol) server in real time. The reconciliation system is equipped with a reconciliation file receiving module to monitor in real time whether the reconciliation file uploaded by the bank side exists in the preset directory of the SFTP server. If the reconciliation file exists, the file name of the reconciliation file is used as the key to perform anti-duplicate verification in the cache to verify whether the reconciliation file already exists in the cache, so as to prevent the bank side from uploading multiple duplicate reconciliation files, which would cause the system to reconcile multiple times.

[0070] Furthermore, the reconciliation system can also use the filename of the reconciliation file as the key to perform anti-duplicate verification in the reconciliation database. It can query whether a relevant record already exists in the reconciliation filename table of the reconciliation database. If the filename of the reconciliation file exists, it means that the reconciliation file has been verified and no further processing is required. This serves as a fallback for preventing duplicates in the reconciliation database.

[0071] In practice, multiple banks may be involved. Therefore, the reconciliation system can pre-set different local temporary directories for different banks. Reconciliation files uploaded by a particular bank are downloaded to the corresponding local temporary directory and then uploaded to cloud storage. This allows the backend to download the reconciliation files for traceability and prevent file loss. It should be noted that the local temporary directory stores reconciliation files in an unverified state. If the status of a reconciliation file changes to verified, it will be deleted immediately or periodically.

[0072] In addition, cloud storage is a must. Without cloud storage, 1) it is difficult for the backend to query and display files, and it is not possible to download specific reconciliation files; 2) file information is not traceable. When the SFTP server is abnormal, the reconciliation files uploaded by the bank cannot be found, causing unnecessary work for staff, long problem-solving cycles, low efficiency and complicated operation; 3) it is not possible to manually upload specific reconciliation files offline.

[0073] According to the file reconciliation rules, the reconciliation file is parsed. These file reconciliation rules refer to the backend configuration of the local temporary file download address, the SFTP server upload file address, the definition of the data separator for each line of the file, the start and end line numbers, and the definition of each line of data.

[0074] For example, the header (first line) of the reconciliation file records the total number of transactions, total transaction amount, transaction date, and transaction account information, such as 3|64.6|20210410|2950000001|, separated by "|". Other lines record: transaction serial number|virtual card number|transaction amount|transaction type (FT0001 purchase, FT0002 cancellation, FT0003 return)|transaction time|original transaction serial number (required for returns)|source channel|transaction category|. For example:

[0075] 8d08acdd0e3d4f7d9b936c7e01ff125b|623185008016391707|33.8|FT0001|20210410|151934||AM||00|

[0076] 8a6341dd4b0b43dc9c6af1fc9029c02d|623185008003078390|6.5|FT0001|20210410|152558||AM||00|

[0077] b560deb214684de8b2c9500e1ab9df31|623185008002349495|24.3|FT0001|20210410|132324||AM||00|

[0078] The data is separated by "|", and each piece of data can only be obtained after parsing the reconciliation file, so a parsing operation is required.

[0079] The total number of transactions and total transaction amount recorded in the header of the bank's reconciliation file are compared with the total number of transactions and total transaction amount recorded in the other lines (excluding the header) to verify the completeness and accuracy of the information contained in the reconciliation file. For example, if the header records 5 total transactions and a total transaction amount of 64.3, but the total number of transactions and transaction amount after summing up the other lines is 4 and 58, it means that the content of the reconciliation file is unusable.

[0080] The bank's reconciliation file contains detailed transaction data. Therefore, after the content of the reconciliation file is verified, this part of the transaction details data needs to be entered into the database (reconciliation database) and stored in the reconciliation file details table for subsequent use.

[0081] In step S102, the business side sends business data MQ to the MQ server. The business data receiving module in the reconciliation system listens for MQ messages sent by the business system in real time, performs object conversion processing on the listened business data, and then stores the converted business objects in the transaction record details table of the reconciliation database. The MQ messages contain consumption data, repayment data, refund data, etc.

[0082] Business data is typically in JSON format, such as merchant information.

[0083]

[0084] The JSON string needs to be converted into a Java object Merchant with attribute fields merchantCode, subMerchantCode, and subMerchantName before the program can use it.

[0085] It should be noted that the business side does not need to upload reconciliation files. After completing each business transaction, it only needs to send the business MQ message to the MQ server, and the business data receiving module will listen for the MQ message and process it into the database.

[0086] For steps S103 and S104, both the bank-side reconciliation file detail table and the business-side transaction record detail table are set in the reconciliation database. The scanning module set up in the reconciliation system scans each row of transaction detail data in the reconciliation file detail table, including at least one of the following: bank-side MQ reconciliation message, scanning each row of business objects in the transaction record detail table, and sending a business-side MQ reconciliation message. A scheduled task is also set for the scanning module; the scheduled task can be set to a CRON expression to scan data every few seconds. Data can also be scanned in batches, with the data volume of each batch configurable, for example, a batch size of 2000 records, to avoid the problem of being unable to reconcile due to excessively large bank-side reconciliation files.

[0087] Example 1: The reconciliation MQ message only contains transaction details.

[0088] Step 1: The reconciliation system responds to the reconciliation MQ message containing transaction details by sending the reconciliation MQ message to the bank.

[0089] Step 2: After the bank receives the reconciliation MQ message, it retrieves the business object corresponding to the first transaction serial number in the transaction details data, and verifies whether the data in the business object is consistent with the transaction details data according to the pre-configured reconciliation fields.

[0090] Step 3: The reconciliation system receives the reconciliation results returned by the bank.

[0091] In this embodiment, the bank-side verification module is used to listen to the bank-side reconciliation MQ messages sent by the timed tasks of the reconciliation system in real time. After listening, it performs internal object conversion (same as the aforementioned business-side object conversion). Based on the transaction serial number in the MQ message body, it searches for the corresponding business object in the transaction record details table. The two have a one-to-one correspondence, and the current status of the business object should be unverified or verification abnormal.

[0092] Based on the pre-configured reconciliation fields, verify the consistency between the bank-side reconciliation MQ and the data in the business object. For example, verify whether user information, transaction amounts, card numbers, and transaction times match. Write the reconciliation results to the results table and update the reconciliation status in the transaction record table to "verified." Write the settlement transaction record to facilitate settlement operations by finance. It should be noted that the reconciliation fields can be pre-configured. For example, a configuration interface can be set up, allowing the business side, bank side, and developers to select and set some reconciliation fields (custom reconciliation fields). Alternatively, developers can set them uniformly (unified reconciliation fields).

[0093] Example 2: The reconciliation MQ message only contains business objects.

[0094] Step 1: The reconciliation system responds to the reconciliation MQ message containing the business object by sending the reconciliation MQ message to the business side;

[0095] Step 2: After the business side listens to the reconciliation MQ message, it retrieves the transaction details data corresponding to the second transaction serial number in the bank side based on the second transaction serial number in the business object, and verifies whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields.

[0096] Step 3: The reconciliation system receives the reconciliation results returned by the business side.

[0097] In this embodiment, the business-side verification module listens in real time for business-side reconciliation MQ messages sent by the scheduled task, and performs internal object conversion upon receiving the message. Based on the transaction serial number in the MQ message body, it retrieves the corresponding transaction details from the reconciliation file detail table. It also verifies the transaction details against the configured reconciliation fields, writes the reconciliation results to the reconciliation result table, and updates the verification status of the reconciliation file detail table.

[0098] Example 3: The reconciliation system sends two-sided reconciliation MQ messages, one of which contains only the business object, and the other contains only the transaction details.

[0099] Step 1: The reconciliation system responds to the reconciliation MQ message containing transaction details by sending the reconciliation MQ message to the bank. After listening to the reconciliation MQ message, the bank retrieves the business object corresponding to the first transaction serial number in the transaction details data, and verifies whether the data in the business object is consistent with the transaction details data according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the bank.

[0100] Step 2: The reconciliation system responds to the reconciliation MQ message containing the business object by sending the reconciliation MQ message to the business side. After listening to the reconciliation MQ message, the business side retrieves the transaction details data corresponding to the second transaction serial number in the bank side based on the second transaction serial number in the business object, and verifies whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the business side.

[0101] Example 4: The reconciliation MQ message includes transaction details and the business object corresponding to the transaction serial number in the transaction details.

[0102] Step 1: The reconciliation system responds to the reconciliation MQ message containing transaction details and the business object corresponding to the transaction serial number in the transaction details, and sends the reconciliation MQ message to the bank.

[0103] Step 2: This allows the bank to verify, after receiving the reconciliation MQ message, whether the data in the business object and the transaction details are consistent based on the pre-configured reconciliation fields.

[0104] Step 3: Receive the reconciliation results returned by the bank.

[0105] In the aforementioned embodiments, both the bank-side reconciliation module and the business-side reconciliation module, upon receiving the MQ reconciliation message, need to retrieve the corresponding information of the other party based on the transaction serial number of the transaction object in the message body for verification. In this embodiment, when the reconciliation system generates the reconciliation MQ message, it has already retrieved the corresponding business object on the business side based on the transaction serial number of the transaction details data. Therefore, the bank side does not need to query the business object again and can directly perform the reconciliation, thereby improving reconciliation efficiency.

[0106] Example 5: The reconciliation MQ message includes a business object and transaction detail data corresponding to the transaction serial number in the business object.

[0107] Step 1: The reconciliation system responds to the reconciliation MQ message containing the business object and the transaction details data corresponding to the transaction serial number in the business object, and sends the reconciliation MQ message to the business side;

[0108] Step 2: After the business side receives the reconciliation MQ message, it checks whether the data in the business object and the transaction details are consistent according to the pre-configured reconciliation fields.

[0109] Step 3: The reconciliation system receives the reconciliation results returned by the business side.

[0110] In this embodiment, when the reconciliation system generates the reconciliation MQ message, it has already obtained the corresponding transaction details data from the bank based on the transaction serial number in the transaction object. Therefore, the business side does not need to query the transaction details data again and can directly verify them, thereby improving reconciliation efficiency. Furthermore, the reconciliation fields can be parameterized, and adding new reconciliation fields can be achieved without modifying the code.

[0111] Example 6: The reconciliation system sends a two-way reconciliation MQ message. The MQ reconciliation message contains transaction details and business objects.

[0112] Step 1: The reconciliation system responds to the reconciliation MQ message containing transaction details and the business object corresponding to the transaction serial number in the transaction details by sending the reconciliation MQ message to the bank side. This allows the bank side to check whether the data in the business object and the transaction details are consistent based on the pre-configured reconciliation fields after listening to the reconciliation MQ message, and receive the reconciliation result returned by the bank side.

[0113] Step 2: The reconciliation system responds to the reconciliation MQ message containing the business object and the transaction details data corresponding to the transaction serial number in the business object. It then sends the reconciliation MQ message to the business side so that after listening to the reconciliation MQ message, the business side can check whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields and receive the reconciliation result returned by the business side.

[0114] For records with discrepancies, they should be postponed and can be included in the data comparison of the next cycle. For example, if a record in the file from September 23, 2021, shows a failed reconciliation because the bank has the data but the business side does not (e.g., due to network timeout, the data was not written to the business side database), and on September 24, 2021, the network was restored and the data was written to the business side, then this discrepancy can be included in the reconciliation for September 24, 2021.

[0115] The backend operation module displays the reconciliation results from the bank-side and business-side reconciliation modules. It shows the reconciliation result for each data entry: reconciliation successful, reconciliation failed, discrepancies, etc., and allows users to claim and confirm discrepancies in records. To ensure data integrity and consistency, subsequent refunds (if data is available on the business side but not on the bank side) or settlement writes (if data is available on the bank side but not on the business side) are processed. The backend operation module also allows users to download reconciliation files, query detailed reconciliation file results, query transaction records, and upload reconciliation files (to help the bank reissue reconciliation files).

[0116] The process involves several steps: **Acknowledgment:** Operations staff manually intervene to address records that failed to reconcile. Multiple operations staff can process discrepancies simultaneously. Once an operation staff member acknowledges a discrepancy, it cannot be acknowledged by another. **Difference Confirmation:** This involves processing refunds for records that failed to reconcile, such as when the business side has data but the bank side does not, to ensure data integrity and consistency.

[0117] In addition, during the entire process, if a reconciliation error occurs due to network anomalies, the reconciliation system can automatically retry until the maximum number of repetitions is reached, such as 10 times. This improves system efficiency and ensures more efficient and stable operation. For the bank or business side, if a network error occurs during the reconciliation process, the reconciliation operation will be repeated until a reconciliation result is obtained or the preset number of repetitions is reached, such as 8 or 10 times.

[0118] The message-driven method provided in the above embodiments improves the efficiency of concurrent data verification and avoids the problem of not being able to automatically re-verify due to network anomalies. It also performs data integrity verification on the reconciliation results to ensure that the entire reconciliation process is efficient and the results are reliable.

[0119] See Figure 2 The diagram illustrates a specific reconciliation data processing method according to an embodiment of the present invention, including the following steps:

[0120] S201: The bank uploads the reconciliation file to the SFTP server;

[0121] S202: The reconciliation system monitors whether there are reconciliation files uploaded by the bank in the preset directory of the SFTP server. If they exist, the reconciliation files are parsed and verified. If the verification is successful, the reconciliation files are stored in the reconciliation file details table of the reconciliation database.

[0122] S203: The business side uploads business data to the MQ server;

[0123] S204: The reconciliation system listens to the business data under the MQ server, performs object conversion, and stores it in the transaction record details table of the reconciliation database;

[0124] S205: The reconciliation system periodically scans the reconciliation file details table and transaction record details table, and sends reconciliation MQ messages;

[0125] S206: For the bank-side reconciliation module, after listening to the bank-side reconciliation MQ message, it performs object conversion; the reconciliation MQ message only contains transaction detail data;

[0126] S207: Based on the first transaction serial number in the transaction details data, obtain the business object corresponding to the first transaction serial number in the business reconciliation terminal;

[0127] S208: Verify whether the amount, fund type, and user information in the bank's reconciliation MQ message match the amount, fund type, and user information in the business object, obtain the reconciliation result, and return it to the reconciliation system;

[0128] S209: For the business-side verification module, after listening to the business-side reconciliation MQ message, it performs object conversion on it; the reconciliation MQ message only contains the business object;

[0129] S210: Based on the second transaction serial number in the business object, obtain the transaction details data corresponding to the second transaction serial number in the bank's reconciliation terminal;

[0130] S211: Verify whether the amount, fund type, and user information of the reconciliation MQ message on the business side match the bank transaction records, obtain the reconciliation results, and return them to the reconciliation system;

[0131] S212: The reconciliation system receives reconciliation results from at least one of the bank side and the business side, records them in the reconciliation result table, and changes the status of the transaction details and business objects to "reconciled".

[0132] See Figure 3 The diagram illustrates another specific reconciliation data processing method according to an embodiment of the present invention, including the following steps:

[0133] S301: The bank uploads the reconciliation file to the SFTP server;

[0134] S302: The reconciliation system monitors whether there are reconciliation files uploaded by the bank in the preset directory of the SFTP server. If they exist, the reconciliation files are parsed and verified. If the verification is successful, the reconciliation files are stored in the reconciliation file details table of the reconciliation database.

[0135] S303: The business side uploads business data to the MQ server;

[0136] S304: The reconciliation system listens to business data under the MQ server, performs object conversion, and stores it in the transaction record details table of the reconciliation database;

[0137] S305: The reconciliation system periodically scans the reconciliation file details table and transaction record details table, and sends reconciliation MQ messages;

[0138] S306: After listening to the reconciliation MQ message, the bank-side reconciliation module checks whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, obtains the reconciliation result, and returns it to the reconciliation system; wherein, the reconciliation MQ message contains transaction details data and the business object corresponding to the transaction serial number in the transaction details data;

[0139] S307: After listening to the reconciliation MQ message, the business-side verification module checks whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, obtains the reconciliation result, and returns it to the reconciliation system; wherein, the reconciliation MQ message contains the business object and the transaction details data corresponding to the transaction serial number in the business object;

[0140] S308: The reconciliation system receives reconciliation results from at least one of the bank side and the business side, records them in the reconciliation result table, and changes the status of the transaction details and business objects to "reconciled".

[0141] Compared to existing technologies, this solution offers at least the following advantages: 1. By periodically scanning for unverified transaction objects, a reconciliation MQ message is generated and sent to the corresponding target reconciliation end for processing. This supports bilateral reconciliation from the bank side to the business side and from the business side to the bank side, and can be processed in parallel. 2. In the event of reconciliation system anomalies, bank-side anomalies, or business-side anomalies, the reconciliation operation can be restarted, thereby improving the timeliness of reconciliation. 3. For reconciliation data with abnormal results, manual intervention is possible, such as posting, claiming, and confirming discrepancies, to ensure the integrity of the reconciled data.

[0142] See Figure 4 The diagram shows the main modules of a reconciliation data processing device 400 provided in an embodiment of the present invention, including:

[0143] The reconciliation file receiving module 401 is used to parse the reconciliation file after listening to the reconciliation file sent by the first reconciliation terminal to obtain transaction detail data;

[0144] The business data receiving module 402 is used to perform object conversion processing on the business data after listening to the business data sent by the second reconciliation terminal, so as to obtain the converted business object.

[0145] The scanning module 403 is used to scan transaction objects whose current status is unverified, generate a reconciliation message queue (MQ) message, and determine the target reconciliation end corresponding to the transaction object; wherein, the transaction object includes at least one of the transaction detail data and the business object;

[0146] The processing module 404 is used to send the reconciliation MQ message to the target reconciliation terminal for reconciliation processing, receive the reconciliation result returned by the target reconciliation terminal, and change the status of the transaction details data and business objects verified this time to "verified".

[0147] In the implementation device of the present invention, the reconciliation system further includes a reconciliation database for storing a reconciliation file detail table and a transaction record detail table. The reconciliation file detail table is used to store transaction detail data, and the transaction record detail table is used to store business objects.

[0148] The reconciliation file receiving module 401 is also used for:

[0149] Based on the filename of the reconciliation file, a duplicate check is performed in the cache. If the check result indicates that a duplicate exists, the reconciliation process is stopped; and

[0150] Based on the filename of the reconciliation file, a duplicate filename check is performed in the reconciliation filename table of the reconciliation database. If the check result shows that a duplicate file exists, the reconciliation process is stopped.

[0151] In the apparatus of this invention, the reconciliation document receiving module 401 is further configured to:

[0152] In response to the detection of a reconciliation file in a preset directory on the server, the system determines the local temporary directory corresponding to the first reconciliation end, downloads the reconciliation file to the local temporary directory, and uploads it to cloud storage; and

[0153] After detecting that the reconciliation file has been verified, the reconciliation file in the local temporary directory is deleted.

[0154] In the apparatus of this invention, the reconciliation document receiving module 401 is used for:

[0155] The reconciliation file is parsed to obtain the header information and other line information. The total number of transactions and the total transaction amount recorded in the header information are compared with the sum of the number of transactions and the transaction amount recorded in the other line information. If the comparison results are the same, the reconciliation file is determined to be usable; otherwise, it is unusable.

[0156] In the apparatus of the present invention, the processing module 404 is configured to perform at least one of the following steps:

[0157] In response to the reconciliation MQ message containing transaction details data, the reconciliation MQ message is sent to the first reconciliation end. After listening to the reconciliation MQ message, the first reconciliation end obtains the business object corresponding to the first transaction serial number in the second reconciliation end based on the first transaction serial number in the transaction details data, and verifies whether the data in the business object is consistent with the transaction details data according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end.

[0158] In response to the reconciliation MQ message containing a business object, the reconciliation MQ message is sent to the second reconciliation end. After listening to the reconciliation MQ message, the second reconciliation end retrieves the transaction details data corresponding to the second transaction serial number in the first reconciliation end based on the second transaction serial number in the business object. Then, based on the pre-configured reconciliation fields, it verifies whether the data in the business object and the transaction details data are consistent and receives the reconciliation result returned by the second reconciliation end.

[0159] In the apparatus of the present invention, the processing module 404 is configured to perform at least one of the following steps:

[0160] In response to the reconciliation MQ message containing transaction details data and the business object corresponding to the transaction serial number in the transaction details data, the reconciliation MQ message is sent to the first reconciliation end, so that after listening to the reconciliation MQ message, the first reconciliation end checks whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end.

[0161] In response to a reconciliation MQ message containing a business object and transaction details data corresponding to the transaction serial number in the business object, the reconciliation MQ message is sent to the second reconciliation end. This allows the second reconciliation end to verify the consistency between the data in the business object and the transaction details data based on the pre-configured reconciliation fields after listening to the reconciliation MQ message, and then receive the reconciliation result returned by the second reconciliation end.

[0162] See Figure 5 This diagram illustrates the relationship between modules provided in an embodiment of the present invention, including:

[0163] The reconciliation file receiving module is responsible for processing the reconciliation files on the bank side, such as monitoring whether there are reconciliation files uploaded by the bank on the SFTP server, internal verification of the reconciliation files, and processing and storing them in the reconciliation file details table.

[0164] The business data receiving module is responsible for processing business data on the business side, such as listening to business data in the MQ server and converting objects to store them in the transaction record details table.

[0165] The reconciliation database is used to store detailed reconciliation documents, transaction record details, etc.

[0166] The scanning module is used to scan the transaction details data in the reconciliation file details table to generate bank-side reconciliation MQ messages; and to scan the business objects in the transaction record details table to generate business-side reconciliation MQ messages.

[0167] The bank-side reconciliation module is used to find the corresponding business data based on the transaction serial number in the bank's reconciliation MQ message and obtain the reconciliation result.

[0168] The business-side verification module is used to verify the corresponding transaction details data based on the transaction serial number in the business-side reconciliation MQ message, and obtain the reconciliation result.

[0169] The backend operation module is used to display the reconciliation results, handle discrepancies in business data and transaction details by posting them on the books, claiming them, or confirming the discrepancies, and handle exception retries.

[0170] Therefore, the aforementioned processing module includes a bank-side verification module, a business-side verification module, and a back-end operation module. Furthermore, the specific implementation details of the device described in this embodiment have already been explained in detail in the above-described method, and therefore will not be repeated here.

[0171] Figure 6 An exemplary system architecture 600 to which embodiments of the present invention can be applied is shown, including terminal devices 601, 602, 603, network 604, and server 605 (only an example).

[0172] Terminal devices 601, 602, and 603 can be various electronic devices with displays and support for web browsing, and have various communication client applications installed. Users can use terminal devices 601, 602, and 603 to interact with server 605 through network 604 to receive or send messages, etc.

[0173] Network 604 is a medium used to provide a communication link between terminal devices 601, 602, 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0174] Server 605 can be a server providing various services, used to perform operations such as receiving and processing data for storage, generating MQ messages for bilateral reconciliation, receiving and saving reconciliation results, etc. It should be noted that the methods provided in this embodiment of the invention are generally executed by server 605, and correspondingly, the apparatus is generally located within server 605.

[0175] It should be understood that Figure 6The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0176] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing a terminal device of the present invention. Figure 7 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0177] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0178] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0179] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this invention.

[0180] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0181] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0182] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor may be described as including a reconciliation file receiving module, a business data receiving module, a scanning module, and a processing module. The names of these modules do not necessarily limit the module itself; for example, the processing module may also be described as a "reconciliation processing module."

[0183] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to implement any of the above-described reconciliation data processing methods.

[0184] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for processing reconciliation data, characterized in that, Applied to an accounting reconciliation system, wherein the accounting reconciliation system is communicatively connected to a first reconciliation terminal and a second reconciliation terminal, the method includes: After listening to the reconciliation file sent by the first reconciliation end, the reconciliation file is parsed to obtain transaction detail data; and after listening to the business data sent by the second reconciliation end, the business data is subjected to object conversion processing to obtain the converted business object; wherein, the object conversion processing of the business data includes: converting the JSON-formatted string in the business data into a JAVA object; Scan for transaction objects whose current status is unverified, generate a reconciliation message queue (MQ) message, and determine the target reconciliation end corresponding to the transaction object; wherein, the transaction object includes at least one of the transaction details data and the business object; the target reconciliation end includes at least one of the first reconciliation end and the second reconciliation end; Send a reconciliation MQ message to the target reconciliation terminal for reconciliation processing, receive the reconciliation result returned by the target reconciliation terminal, and change the status of the transaction details data and business objects verified this time to "verified".

2. The method according to claim 1, characterized in that, The reconciliation system also includes a reconciliation database, which stores reconciliation file detail tables and transaction record detail tables. The reconciliation file detail tables are used to store transaction detail data, and the transaction record detail tables are used to store business objects. After listening to the reconciliation file sent by the first reconciliation end, it also includes: Based on the filename of the reconciliation file, a duplicate check is performed in the cache. If the check result is that the file exists, the reconciliation process is stopped. as well as Based on the filename of the reconciliation file, a duplicate filename check is performed in the reconciliation filename table of the reconciliation database. If the check result shows that a duplicate file exists, the reconciliation process is stopped.

3. The method according to claim 1 or 2, characterized in that, Also includes: In response to the detection that a reconciliation file exists in a preset directory of the server, the local temporary directory corresponding to the first reconciliation end is determined, the reconciliation file is downloaded to the local temporary directory, and then uploaded to cloud storage; as well as After detecting that the reconciliation file has been verified, the reconciliation file in the local temporary directory is deleted.

4. The method according to claim 1, characterized in that, The parsing of the reconciliation file includes: The reconciliation file is parsed to obtain the header information and other line information. The total number of transactions and the total transaction amount recorded in the header information are compared with the sum of the number of transactions and the transaction amount recorded in the other line information. If the comparison results are the same, the reconciliation file is determined to be usable; otherwise, it is unusable.

5. The method according to claim 1, characterized in that, The step of sending a reconciliation MQ message to the target reconciliation client for reconciliation processing and receiving the reconciliation result returned by the target reconciliation client includes performing at least one of the following steps: In response to the reconciliation MQ message containing transaction details data, the reconciliation MQ message is sent to the first reconciliation end. After listening to the reconciliation MQ message, the first reconciliation end obtains the business object corresponding to the first transaction serial number in the second reconciliation end based on the first transaction serial number in the transaction details data, and verifies whether the data in the business object is consistent with the transaction details data according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end. In response to the reconciliation MQ message containing a business object, the reconciliation MQ message is sent to the second reconciliation end. After listening to the reconciliation MQ message, the second reconciliation end retrieves the transaction details data corresponding to the second transaction serial number in the first reconciliation end based on the second transaction serial number in the business object. Then, based on the pre-configured reconciliation fields, it verifies whether the data in the business object and the transaction details data are consistent and receives the reconciliation result returned by the second reconciliation end.

6. The method according to claim 1, characterized in that, The step of sending a reconciliation MQ message to the target reconciliation client for reconciliation processing and receiving the reconciliation result returned by the target reconciliation client includes performing at least one of the following steps: In response to the reconciliation MQ message containing transaction details data and the business object corresponding to the transaction serial number in the transaction details data, the reconciliation MQ message is sent to the first reconciliation end, so that after listening to the reconciliation MQ message, the first reconciliation end checks whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end. In response to a reconciliation MQ message containing a business object and transaction details data corresponding to the transaction serial number in the business object, the reconciliation MQ message is sent to the second reconciliation end. This allows the second reconciliation end to verify the consistency between the data in the business object and the transaction details data based on the pre-configured reconciliation fields after listening to the reconciliation MQ message, and then receive the reconciliation result returned by the second reconciliation end.

7. A reconciliation data processing device, characterized in that, The device is used in an accounting reconciliation system, which is communicatively connected to a first reconciliation terminal and a second reconciliation terminal. The device includes: The reconciliation file receiving module is used to parse the reconciliation file sent by the first reconciliation end after listening to it, and obtain transaction detail data. The business data receiving module is used to perform object conversion processing on the business data after listening to the business data sent by the second reconciliation terminal, so as to obtain the converted business object; wherein, the object conversion processing of the business data includes: converting the JSON-formatted string in the business data into a JAVA object; The scanning module is used to scan for transaction objects whose current status is unverified, generate a reconciliation message queue (MQ) message, and determine the target reconciliation terminal corresponding to the transaction object; wherein, the transaction object includes at least one of the transaction detail data and the business object; the target reconciliation terminal includes at least one of the first reconciliation terminal and the second reconciliation terminal; The processing module is used to send the reconciliation MQ message to the target reconciliation terminal for reconciliation processing, receive the reconciliation result returned by the target reconciliation terminal, and change the status of the transaction details data and business objects verified this time to "verified".

8. The apparatus according to claim 7, characterized in that, The processing module is configured to perform at least one of the following steps: In response to the reconciliation MQ message containing transaction details data, the reconciliation MQ message is sent to the first reconciliation end. After listening to the reconciliation MQ message, the first reconciliation end obtains the business object corresponding to the first transaction serial number in the second reconciliation end based on the first transaction serial number in the transaction details data, and verifies whether the data in the business object is consistent with the transaction details data according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end. In response to the reconciliation MQ message containing a business object, the reconciliation MQ message is sent to the second reconciliation end. After listening to the reconciliation MQ message, the second reconciliation end retrieves the transaction details data corresponding to the second transaction serial number in the first reconciliation end based on the second transaction serial number in the business object. Then, based on the pre-configured reconciliation fields, it verifies whether the data in the business object and the transaction details data are consistent and receives the reconciliation result returned by the second reconciliation end.

9. The apparatus according to claim 7, characterized in that, The processing module is configured to perform at least one of the following steps: In response to the reconciliation MQ message containing transaction details data and the business object corresponding to the transaction serial number in the transaction details data, the reconciliation MQ message is sent to the first reconciliation end, so that after listening to the reconciliation MQ message, the first reconciliation end checks whether the data in the business object and the transaction details data are consistent according to the pre-configured reconciliation fields, and receives the reconciliation result returned by the first reconciliation end. In response to a reconciliation MQ message containing a business object and transaction details data corresponding to the transaction serial number in the business object, the reconciliation MQ message is sent to the second reconciliation end. This allows the second reconciliation end to verify the consistency between the data in the business object and the transaction details data based on the pre-configured reconciliation fields after listening to the reconciliation MQ message, and then receive the reconciliation result returned by the second reconciliation end.

10. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-6.

11. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-6.

Images