A method and device for processing reconciliation data

Abstract

This invention, applicable to the financial and other fields, provides a method and apparatus for processing reconciliation data. The method includes: determining the transaction time and type corresponding to multiple pre-received reconciliation requests from users; determining the time range corresponding to the reconciliation request based on the transaction time; splitting the transaction data corresponding to the reconciliation request according to the transaction type to generate a splitting result; and reconciling the transaction data based on the time range and the splitting result. This invention enables banks to flexibly and accurately complete reconciliation work for each partner institution with data from multiple collaborating institutions across different time periods, effectively avoiding the need for manual intervention due to time period factors. Through flexible configuration, it can efficiently complete reconciliation work for institutions with different time periods, promoting more flexible and efficient cooperation between banks and other institutions.

Description

Technical Field

[0001] This invention is applicable to the financial field or other fields, and specifically relates to a method and apparatus for processing reconciliation data. Background Technology

[0002] As internet technology and the financial industry become increasingly intertwined, more and more banks are establishing open ecosystems, collaborating with various third-party institutions to launch more high-quality financial products and services. This allows more customers to directly purchase bank products and conduct banking transactions through these partner institutions. Banks not only expand their sales channels but also increase revenue while serving customers. However, since consumer transactions involve fund transfers and reconciliation, banks reconcile funds with these third-party partners to verify discrepancies in transaction records. Because some third-party partners use different statistical period ranges than the bank's system, the start and end dates of transaction data provided by third-party partners often differ from the traditional calendar day time range. Since banks record transaction details using the traditional calendar day time, reconciliation with third-party partners frequently results in discrepancies due to inconsistent date ranges. Furthermore, differences exist among the various partner institutions, leading to variations in the time ranges of transaction data provided by different partners. This places significant adjustment pressure on the bank's accounting system, which is detrimental to the development of the bank's open financial product ecosystem. Summary of the Invention

[0003] It should be noted that the reconciliation data processing method and apparatus disclosed herein can be used in the financial field, or in any field other than the financial field. The application field of the reconciliation data processing method and apparatus disclosed herein is not limited.

[0004] To address the problems in existing technologies, this invention enables banks to flexibly and accurately complete reconciliation work for each of their numerous partner institutions with data from different time periods. This effectively avoids situations requiring manual intervention to adjust accounts due to time period factors. Through flexible configuration, reconciliation work for institutions with different time periods can be completed efficiently, promoting more flexible and efficient cooperation between banks and other institutions.

[0005] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0006] In a first aspect, the present invention provides a method for processing reconciliation data (executed at the agent node end), comprising:

[0007] The transaction time and transaction type corresponding to the reconciliation request are determined based on the reconciliation requests received from multiple users.

[0008] The time range corresponding to the reconciliation request is determined based on the transaction time.

[0009] Based on the transaction type, the transaction data corresponding to the reconciliation request is split according to the transaction type to generate a splitting result;

[0010] The transaction data is reconciled based on the time range and the splitting results.

[0011] In one embodiment, the time range includes: the start time of the staggered time and the end time of the staggered time; determining the time range corresponding to the reconciliation request based on the transaction time includes:

[0012] When the staggered start time and staggered end time are the first time limits, the time range is T days;

[0013] When the staggered start time and staggered end time are the second time limits, the time range is T+1 days.

[0014] In one embodiment, the step of splitting the transaction data corresponding to the reconciliation request according to the transaction type to generate a splitting result includes:

[0015] The transaction data is split according to the transaction type dimension to generate time-sharing files;

[0016] The time-sharing files within the T-day and the T+1-day period are merged to generate a split result.

[0017] In one embodiment, reconciling the transaction data based on the time range and the splitting results includes:

[0018] Parse the splitting results to obtain the transaction serial number, amount, and channel event number of the transaction data;

[0019] Within day T, the transaction data is matched based on the serial number, amount, and channel event number.

[0020] In one embodiment, determining the transaction time and transaction type corresponding to the reconciliation request based on the pre-received reconciliation requests from multiple users includes:

[0021] The reconciliation request is received periodically;

[0022] The reconciliation request is parsed to determine the transaction time and transaction type.

[0023] In one embodiment, parsing the reconciliation request to determine the transaction time and transaction type includes:

[0024] Create the corresponding XML file based on the reconciliation request;

[0025] Determine the full path of the XML file based on its header file;

[0026] The reconciliation request is loaded according to the full path of the XML file.

[0027] Secondly, the present invention provides a reconciliation data processing device (executed at the agent node end), comprising:

[0028] The transaction time determination module is used to determine the transaction time and transaction type corresponding to the reconciliation requests based on the reconciliation requests received from multiple users.

[0029] The time range determination module is used to determine the time range corresponding to the reconciliation request based on the transaction time.

[0030] The splitting result generation module is used to split the transaction data corresponding to the reconciliation request according to the transaction type to generate a splitting result;

[0031] The transaction data reconciliation module is used to reconcile the transaction data according to the time range and the splitting results.

[0032] In one embodiment, the time range includes: the start time of the staggered time and the end time of the staggered time; determining the time range corresponding to the reconciliation request based on the transaction time includes:

[0033] When the staggered start time and staggered end time are the first time limits, the time range is T days;

[0034] When the staggered start time and staggered end time are the second time limits, the time range is T+1 days.

[0035] In one embodiment, the splitting result generation module includes:

[0036] The time-sharing file generation unit is used to split the transaction data according to the transaction type dimension to generate a time-sharing file;

[0037] The splitting result generation unit is used to merge the time-sharing files within the T-day and the T+1-day to generate a splitting result.

[0038] In one embodiment, the transaction data reconciliation module includes:

[0039] The splitting result parsing unit is used to parse the splitting result to obtain the transaction serial number, amount, and channel event number of the transaction data;

[0040] The transaction data matching unit is used to match the transaction data within day T based on the transaction number, amount, and channel event number.

[0041] In one embodiment, the transaction time determination module includes:

[0042] A request receiving unit is used to periodically receive the reconciliation request;

[0043] The request parsing unit is used to parse the reconciliation request to determine the transaction time and transaction type.

[0044] In one embodiment, the request parsing unit includes:

[0045] The file creation unit is used to create the corresponding XML file based on the reconciliation request.

[0046] The path determination unit is used to determine the full path of the XML file based on the header file of the XML file.

[0047] The reconciliation request loading unit is used to load the reconciliation request according to the full path of the XML file.

[0048] Thirdly, the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of a reconciliation data processing method.

[0049] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a reconciliation data processing method.

[0050] As described above, the reconciliation data processing method and apparatus provided in this embodiment of the invention first determines the transaction time and transaction type corresponding to the reconciliation requests based on the reconciliation requests received from multiple users; then, it determines the time range corresponding to the reconciliation request based on the transaction time; according to the transaction type, it splits the transaction data corresponding to the reconciliation request to generate a splitting result; finally, it reconciles the transaction data based on the time range and the splitting result. This invention enables banks to flexibly and accurately complete the reconciliation work for each partner institution facing data from numerous partner institutions with different time-periods, effectively avoiding situations requiring manual intervention due to time-period discrepancies. Through flexible configuration, it can efficiently complete the reconciliation work for institutions with different time-periods, promoting more flexible and efficient cooperation between banks and other institutions. Attached Figure Description

[0051] In order to more clearly illustrate the embodiments of the present invention 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, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

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

[0053] Figure 2 This is a flowchart illustrating step 300 in an embodiment of the present invention;

[0054] Figure 3 This is a flowchart illustrating step 400 in an embodiment of the present invention;

[0055] Figure 4 This is a structural diagram of a flexible reconciliation system for different time-lapse data in a specific application example of the present invention;

[0056] Figure 5 This is a structural block diagram of the receiving module in a specific application example of the present invention;

[0057] Figure 6 This is a block diagram of the processing module structure in a specific application example of the present invention;

[0058] Figure 7 This is a block diagram of the verification module structure in a specific application example of the present invention.

[0059] Figure 8 This is a block diagram of the parameter module structure in a specific application example of the present invention.

[0060] Figure 9 This is a structural block diagram of the information storage module in a specific application example of the present invention;

[0061] Figure 10 This is a schematic diagram of the reconciliation data processing method in a specific application example of the present invention;

[0062] Figure 11 This is a schematic diagram of the real-time transaction processing flow in a specific application example of the present invention;

[0063] Figure 12 This is the intent of the time-lapse data reconciliation processing flow in a specific application example of the present invention;

[0064] Figure 13 This is a structural block diagram of the reconciliation data processing device in an embodiment of the present invention;

[0065] Figure 14 This is a structural block diagram of the splitting result generation module in an embodiment of the present invention;

[0066] Figure 15 This is a structural block diagram of the transaction data reconciliation module in an embodiment of the present invention;

[0067] Figure 16 This is a schematic diagram of the structure of an electronic device in an embodiment of the present invention. Detailed Implementation

[0068] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0069] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0070] An embodiment of the present invention provides a specific implementation method for reconciliation data processing, see below. Figure 1 The method specifically includes the following:

[0071] Step 100: Determine the transaction time and transaction type corresponding to the reconciliation request based on the reconciliation requests received from multiple users.

[0072] Specifically, staff set different time-sharing periods for different partner institutions (CorPon), specifying the start and end times of the time-sharing period. Simultaneously, banking personnel maintain the transaction types (Type) that require reconciliation for each partner institution, including but not limited to 1-Consumption, 2-Return, etc., and maintain the real-time detailed backup file storage paths (Path) for different institutions.

[0073] Step 200: Determine the time range corresponding to the reconciliation request based on the transaction time.

[0074] Preferably, if the current transaction time falls within the time range of 00:00 on the actual calendar day and the end time of the cooperating institution's staggered time period (Tend), then the transaction details backup will be placed in a file under the institution's T-day path. If the current transaction time falls within the time range of 24:00 on the actual calendar day and the end time of the cooperating institution's staggered time period (Tend), then the transaction details backup will be placed in a file under the institution's T+1 date path.

[0075] In addition, considering the large transaction volume, in order to improve system efficiency, a new file can be generated sequentially within a preset period of time under the same sending path for data storage.

[0076] Step 300: Based on the transaction type, split the transaction data corresponding to the reconciliation request to generate a splitting result.

[0077] Step 400: Reconcile the transaction data according to the time range and the splitting results.

[0078] It is understood that in steps 300 and 400, the transaction data refers to the transaction data file at the time of the error and the real-time detail backup file.

[0079] Specifically, on T+1 day, after receiving the staggered transaction data file for day T from the institution, it is split and merged. Then, the real-time detailed backup file under the bank's day T path is split and merged according to the transaction type dimension (Type). Then, the two files resulting from the split and merged staggered transaction data file and the real-time detailed backup file are matched and verified to complete the transaction data reconciliation.

[0080] The system receives out-of-time transaction data files and real-time detailed backup files for each transaction type, and performs reconciliation according to transaction type (Type). During reconciliation, the data in the files is matched against the corresponding transaction serial number (TraId), amount (TrAmt), channel event number (ChanId), and other data information. After the matching is completed, the reconciliation result (ComRe) is stored. The reconciliation result includes, but is not limited to, 1-reconciliation successful, 2-reconciliation abnormal, 3-many counterparties, and 4-few counterparties.

[0081] As described above, the reconciliation data processing method provided in this embodiment of the invention first determines the transaction time and transaction type corresponding to the reconciliation requests based on the reconciliation requests from multiple pre-received users; then, it determines the time range corresponding to the reconciliation request based on the transaction time; according to the transaction type, it splits the transaction data corresponding to the reconciliation request to generate a splitting result; finally, it reconciles the transaction data based on the time range and the splitting result. This invention enables banks to flexibly and accurately complete the reconciliation work for each partner institution facing data from numerous partner institutions with different time-periods, effectively avoiding the need for manual intervention due to time-period discrepancies. Flexible configuration allows for efficient completion of reconciliation work for institutions with different time-periods, promoting more flexible and efficient cooperation between banks and other institutions. Furthermore, the reconciliation data processing method provided in this embodiment of the invention splits the reconciliation tasks of third-party institutions into multiple time periods for reconciliation, effectively saving the computing resources of banking institutions and reducing the risk of excessive system load caused by excessive reconciliation business within the same time period.

[0082] In one embodiment, the time range includes: the start time of the staggered time and the end time of the staggered time; determining the time range corresponding to the reconciliation request based on the transaction time includes:

[0083] When the staggered start time and staggered end time are the first time limits, the time range is T days;

[0084] When the staggered start time and staggered end time are the second time limits, the time range is T+1 days.

[0085] First, the transaction time (TrDate) of the current transaction is determined. If the current transaction time (TrDate) falls within the time range of midnight of the actual calendar day and the end time of the cooperating institution's staggered time period (Tend), the transaction details are backed up and stored in a file under the institution's T-day path. If the current transaction time (TrDate) falls within the time range of the cooperating institution's staggered time period (Tend) and the end time of the actual calendar day (24:00), the transaction details are backed up and stored in a file under the institution's T+1 date path.

[0086] In one embodiment, see Figure 2 Step 300 further includes:

[0087] Step 301: Segment the transaction data according to the transaction type dimension to generate time-sharing files;

[0088] Step 302: Merge the time-sharing files within day T and within day T+1 to generate a split result.

[0089] In steps 301 and 302, when the cooperating institution provides the staggered transaction data file for the T-day period at the agreed time on T+1 day, the transaction type (Type) of the institution is read, and the staggered transaction data file is split according to the transaction type dimension (Type). After splitting, the staggered transaction data file of each transaction type (Type) is checked, and the information to complete the splitting process is used to trigger the real-time detailed backup file splitting and merging process.

[0090] Upon receiving the transaction data file splitting information, the files under the institution's T-day real-time detail backup file path are split according to transaction type. After splitting, each transaction type contains multiple time-sharing files. Then, the time-sharing files are merged according to transaction type. After merging, the real-time detail backup files of each transaction type are checked.

[0091] In one embodiment, see Figure 3 Step 400 further includes:

[0092] Step 401: Parse the splitting result to obtain the transaction serial number, amount, and channel event number of the transaction data;

[0093] Step 402: Match the transaction data within day T based on the transaction number, amount, and channel event number.

[0094] In steps 401 and 402, firstly, time parameters are set. When a transaction request is received by the receiving institution on calendar day T, the transaction is matched and determined to fall under the path of day T or T+1 based on the institution, transaction type, and transaction time (data under the path of day T is called the real-time detailed backup file of day T). When the receiving institution sends the staggered transaction data file of day T on calendar day T+1, the staggered transaction data file is split and merged, and then the real-time detailed backup file under the path of day T is split and merged. Finally, the two files resulting from the splitting and merging of these two files are matched and verified.

[0095] In one embodiment, step 100 specifically includes:

[0096] Step 101: Periodically receive the reconciliation requests;

[0097] Step 102: Parse the reconciliation request to determine the transaction time and transaction type.

[0098] In one embodiment, step 102 further includes:

[0099] Step 1021: Create the corresponding XML file based on the reconciliation request;

[0100] Step 1022: Determine the full path of the XML file based on its header file;

[0101] Step 1023: Load the reconciliation request according to the full path of the XML file.

[0102] To further illustrate this solution, the present invention also provides specific application examples of the reconciliation data processing method, which specifically include the following:

[0103] This specific application example also provides a flexible reconciliation system for different types of misaligned data, such as... Figure 4 As shown, the system includes a receiving module 1, a processing module 2, a verification module 3, a parameter module 4, and an information storage module 5, wherein:

[0104] Receiving Module 1: This module receives and processes relevant data sent by partner institutions. This data includes, but is not limited to, real-time transaction request messages and staggered transaction data files sent by partner institutions at agreed-upon times. The processing includes, but is not limited to: for real-time transaction request messages sent by partner institutions, identifying the corresponding transaction institution number upon receipt, sending it to Processing Module 2 for transaction processing, and simultaneously sending it to Information Storage Module 5 for storage; for staggered transaction data files sent by partner institutions, identifying the corresponding transaction institution number upon receipt, sending it to Verification Module 3 for transaction processing, and simultaneously sending it to Information Storage Module 5 for storage. Furthermore, Receiving Module 1 also receives and processes the real-time transaction processing results from Processing Module 2 and delivers the processing results to the partner institutions.

[0105] Processing module 2 receives real-time transaction request messages from third-party partners sent by receiving module 1. It then matches the current data with the transaction institution number identified by receiving module 1, and matches it against the parameter rules maintained by the parameter maintenance module and stored in the information storage module. After processing the real-time transaction, it backs up the real-time detailed data to the corresponding path file. Simultaneously, it sends the processing results of the real-time transaction request to receiving module 1 and information storage module 5.

[0106] In the verification module 3, after the receiving module 1 sends the off-time transaction data file sent by the cooperating institution, the verification module 3 processes the off-time transaction data file and the real-time detailed backup file sent by the cooperating institution. Specifically: the off-time transaction data file is split according to transaction type. The transaction type is the transaction type supported by the cooperating institution, maintained by the parameter maintenance module 4 and stored in the information storage module 5. This is split into sub-off-time transaction data files based on the transaction type. The processing of the real-time detailed backup file includes: splitting the real-time detailed backup file according to the backup path corresponding to the cooperating institution, resulting in multiple time-sharing sub-backup files under each transaction type (to improve system efficiency under high transaction volume, a new file is generated sequentially every 10 minutes under the same sending path for data storage). Then, the verification module 3 merges the time-sharing sub-backup files under each transaction type into a single data file. After completing the splitting and integration of the off-time transaction data file and the real-time detailed backup file, the off-time transaction data and real-time detailed backup data for each transaction type of each cooperating institution are reconciled. The reconciliation results are sent to information storage module 5.

[0107] Parameter module 4 is used to maintain the transaction types supported by different partner institutions, the time-sharing period, and the path of the corresponding real-time detail file backup, etc. After maintenance is completed, the maintenance results are sent to information storage module 5.

[0108] The information storage module 5 is used to store information related to real-time and staggered transaction data files sent by the receiving module 1, and to store real-time transaction processing information sent by the processing module 2, as well as verification results pushed by the verification module 3 and parameter maintenance information sent by the parameter module 4.

[0109] Furthermore, if Figure 5 As shown, the display receiving module 1 consists of an information receiving unit 11, an identification unit 12, and an information pushing unit 13. Wherein:

[0110] Information receiving unit 11: Receives real-time transaction request messages and staggered transaction data files sent by partner institutions at agreed-upon times, and pushes the information to identification unit 12. Simultaneously, it pushes the real-time transaction request messages sent by partner institutions to the real-time transaction information storage unit 51 of the information storage module 5 for storage. It also pushes the staggered transaction data files sent by partner institutions at agreed-upon times to the staggered transaction file storage unit 52 of the information storage module 5 for storage.

[0111] Identification unit 12: Used to receive and identify the transaction institution number corresponding to the information pushed by information receiving unit 11. After identification, it sends the real-time transaction request message sent by the cooperating institution to the real-time transaction receiving unit 21 of processing module 2, and sends the staggered transaction data file to the staggered transaction data processing unit 31 of verification module 3.

[0112] Information push unit 13: Used to receive real-time transaction processing result information pushed by real-time transaction push unit 24 and send the information to third-party institutions.

[0113] like Figure 6 As shown, processing module 2 consists of four parts: a real-time transaction receiving unit 21, a real-time transaction processing unit 22, a real-time transaction backup unit 23, and a real-time transaction push unit 24.

[0114] Real-time transaction receiving unit 21: The real-time transaction receiving unit is a unit used to receive real-time transaction request messages from cooperative institutions sent by the identification unit 12.

[0115] Real-time transaction processing unit 22: Receives transaction information pushed by real-time transaction receiving unit 21, processes the current transaction through the core system, receives the response result from the core system, and sends the response result to real-time transaction push unit 24. The processing result includes, but is not limited to, processing success, processing failure, and processing exception. Simultaneously, after receiving the response, it pushes information to real-time transaction backup unit 23.

[0116] The real-time transaction backup unit 23 receives transaction information pushed by the real-time transaction processing unit 22. This transaction information includes, but is not limited to, transaction processing results, transaction time, transaction card number, and transaction type. It then reads the corresponding time-sharing cycle of the transaction institution stored in the cooperating institution parameter storage unit 53. Simultaneously, it determines the transaction time of the current transaction. If the current transaction time falls within the time range of midnight on the actual calendar day and the end time (Tend) of the cooperating institution's time-sharing cycle, the transaction details are backed up to a file under the institution's current day's path. If the current transaction time falls within the time range of the end time (Tend) of the cooperating institution's time-sharing cycle and the end time (24:00) on the actual calendar day, the transaction details are backed up to a file under the institution's next date's path. To improve system efficiency under high transaction volumes, a new file is generated sequentially every 10 minutes under the same time-sharing path for data storage.

[0117] Real-time transaction push unit 24: Used to receive real-time transaction processing results pushed by real-time transaction processing unit 22. The transaction information includes, but is not limited to, transaction processing result, transaction time, transaction card number, transaction type, etc. After receiving, the information is pushed to information push unit 13 and real-time transaction information storage unit 51 of information storage module 5 for storage.

[0118] like Figure 7 As shown, the verification module 3 consists of three parts: a staggered transaction data processing unit 31, a real-time detailed backup file processing unit 32, and a verification unit 33. Among them:

[0119] Off-peak transaction data processing unit 31: It is used to receive the off-peak transaction data file of the cooperating institution pushed by the identification unit 12, and then read the transaction type of the institution stored in the cooperating institution parameter storage unit 53 of the information storage module. It splits the off-peak transaction data file according to the transaction type dimension, and sends the off-peak transaction data file of each transaction type to the verification unit 33 after splitting. At the same time, the information of the completed splitting process is sent to the real-time detailed backup file processing unit 32 to trigger the real-time detailed backup file splitting and merging process.

[0120] Real-time detailed backup file processing unit 32: After receiving the information from the staggered transaction data processing unit 31 that the staggered transaction data file has been split, it splits each file under the real-time detailed backup file path of the institution according to the transaction type. After splitting, each transaction type contains multiple time-sharing files. Then, it performs time-sharing file merging processing according to the transaction type. After merging processing, it pushes the real-time detailed backup file of each transaction type to the verification unit 33.

[0121] The verification unit 33 receives the off-time transaction data file and real-time detail backup file for each transaction type pushed by the off-time transaction data processing unit 31 and the real-time detail backup file processing unit 32, and performs reconciliation processing according to the transaction type. During reconciliation, the data in the file is matched with data information such as the transaction serial number (TraId), amount (TrAmt), and channel event number (ChanId) corresponding to the transaction. The processing result is sent to the reconciliation result storage unit 54 of the information storage module 5 for storage. The reconciliation result includes, but is not limited to, reconciliation success, reconciliation anomaly, multiple counterparties, and few counterparties.

[0122] like Figure 8 As shown, the parameter display module 4 consists of four parts: a partner institution staggered cycle maintenance unit 41, a partner institution transaction type maintenance unit 42, a partner institution backup path maintenance unit 43, and a parameter information push unit 44. Among them:

[0123] Partner Institution Off-Time Cycle Maintenance Unit 41: Used by banking personnel to maintain the off-time cycles of different partner institutions, including the start and end times of the off-time cycle for each partner institution. After maintenance, the information is pushed to the parameter information push unit 44.

[0124] Partner Institution Transaction Type Maintenance Unit 42: Through this unit, banking personnel can maintain the transaction types for each partner institution that require reconciliation. These transaction types include, but are not limited to, consumption and returns. After maintenance is completed, the maintained information is pushed to the Parameter Information Push Unit 44.

[0125] The partner institution backup path maintenance unit 43 allows banking personnel to maintain the storage paths for real-time detailed backup files and off-peak transaction data files for different institutions. After maintenance is complete, the maintained information is pushed to the parameter information push unit 44.

[0126] Parameter information push unit 44: Used to receive maintenance content information pushed by the cooperative institution off-time cycle maintenance unit 41, cooperative institution transaction type maintenance unit 42, and cooperative institution backup path maintenance unit 43, and push the information to the cooperative institution parameter storage unit 53 of the information storage module for storage.

[0127] like Figure 9 As shown, the information storage module 5 consists of four parts: a real-time transaction information storage unit 51, a staggered transaction file storage unit 52, a cooperating institution parameter storage unit 53, and a reconciliation result storage unit 54. Among them:

[0128] Real-time transaction information storage unit 51: used to receive and store real-time transaction information pushed by information receiving unit 11 and real-time transaction push unit 24. The transaction information includes, but is not limited to, transaction type, transaction amount, transaction time, transaction institution, etc. See Table 1.

[0129] Table 1

[0130]

[0131] Off-peak transaction file storage unit 52: Used to receive and store off-peak transaction data files sent by cooperating institutions at agreed time points by identification unit 12.

[0132] Cooperative Institution Parameter Storage Unit 53: Used to receive and store parameter information pushed by parameter information push unit 44. The parameter information includes, but is not limited to, cooperative institution transaction type, cooperative institution time-off cycle, and cooperative institution backup path, see Table 2.

[0133] Table 2

[0134]

[0135] Reconciliation result storage unit 54: Used to receive and store the reconciliation results pushed by the verification unit 33. The reconciliation results include, but are not limited to, reconciliation success, reconciliation error, multiple counterparties, and few counterparties.

[0136] See Figure 10 Based on the aforementioned flexible reconciliation system for different time-related data, the reconciliation data processing method in this specific application example includes:

[0137] Step S101: Maintain the time-out period and time-out path for reconciliation between partner institutions.

[0138] See Figure 11 First, bank staff use the parameter module to set different time-sharing period ranges for different partner institutions (CorPon) with different time-sharing data periods, i.e., the start and end times of the time-sharing period. Simultaneously, bank staff maintain the transaction types (Type) that require reconciliation for each partner institution, including but not limited to 1-Consumption, 2-Return, etc., and maintain the storage paths (Path) for real-time detailed backup files of different institutions.

[0139] Step S102: Process real-time transactions of partner institutions and back up real-time files according to parameters.

[0140] When a customer makes a purchase at a partner institution, the partner institution will send the transaction information to the bank system in real time. The real-time transaction information includes, but is not limited to, the transaction type (Type), transaction amount (TrAmt), transaction time (TrDate), transaction institution (CorPon), and payment card number (AccNo). When the bank receives the transaction, the bank system will perform accounting processing such as deduction after receiving the transaction: the receiving module receives the transaction and identifies the partner institution corresponding to the current transaction. Then, the real-time transaction processing unit 22 sends the current transaction to the core system for processing, and at the same time receives the response result (SysRe) of the core system and responds to the partner institution. The processing result includes, but is not limited to, 1-processing successful, 2-processing failed, and 3-processing abnormal.

[0141] The real-time transaction backup unit 23 then determines the transaction time (TrDate) of the current transaction based on the staggered time period corresponding to the trading institution. If the current transaction time (TrDate) falls within the time range of midnight on the actual calendar day and the end time (Tend) of the cooperating institution's staggered time period, the transaction details are backed up and stored in a file under the institution's T-day path. If the current transaction time (TrDate) falls within the time range of the end time (Tend) of the cooperating institution's staggered time period and the end time (24:00) on the actual calendar day, the transaction details are backed up and stored in a file under the institution's T+1 date path. Considering the high transaction volume, to improve system efficiency, a new file is generated sequentially every 10 minutes under the same path for data storage.

[0142] Step S103: Receive the time-lapse data file and process the real-time detailed backup file.

[0143] See Figure 12 When the cooperating institution provides the staggered transaction data file for the T-day period at the agreed time on T+1 day, the staggered transaction data processing unit 31 reads the transaction type (Type) of the institution stored in the cooperating institution parameter storage unit 53 of the information storage module, splits the staggered transaction data file according to the transaction type dimension (Type), and sends the staggered transaction data file of each transaction type (Type) to the verification unit 33 after splitting. At the same time, the information of the completed splitting process is sent to the real-time detailed backup file processing unit 32 to trigger the real-time detailed backup file splitting and merging process.

[0144] After receiving the information from the staggered transaction data processing unit 31 that the staggered transaction data file splitting is completed, the real-time detailed backup file processing 32 splits each file under the real-time detailed backup file path within the T-day of the institution according to the transaction type. After splitting, each transaction type contains multiple time-sharing files. Then, the time-sharing files are merged according to the transaction type. After merging, the real-time detailed backup file of each transaction type is pushed to the verification unit 33.

[0145] Step S104: Complete the reconciliation of misaligned data files.

[0146] The verification unit 33 receives the off-time transaction data file and real-time detail backup file for each transaction type pushed by the off-time transaction data processing unit 31 and the real-time detail backup file processing unit 32, and performs reconciliation processing according to the transaction type dimension (Type). During reconciliation, the data in the file is matched with data information such as the transaction serial number (TraId), amount (TrAmt), and channel event order number (ChanId) corresponding to the transaction. After the matching is completed, the reconciliation result (ComRe) is sent to the reconciliation result storage unit 54 of the information storage module 5 for storage. The reconciliation result includes, but is not limited to, 1-reconciliation successful, 2-reconciliation abnormal, 3-many competitors, and 4-few competitors.

[0147] As can be seen from the above description, the reconciliation data processing method provided in the specific application example of the present invention, through the receiving module, processing module, verification module, parameter module, and information storage module, enables banks to flexibly and accurately complete the reconciliation work for each cooperative institution when facing data from numerous cooperative institutions corresponding to different time periods. This effectively avoids situations requiring manual intervention to adjust accounts due to time period factors. Through flexible configuration, the reconciliation work for institutions with different time periods can be completed efficiently, promoting banks to cooperate with other institutions more flexibly and efficiently.

[0148] Based on the same inventive concept, this application also provides a reconciliation data processing apparatus, which can be used to implement the method described in the above embodiments, as shown in the following embodiments. Since the principle by which the reconciliation data processing apparatus solves the problem is similar to that of the reconciliation data processing method, the implementation of the reconciliation data processing apparatus can refer to the implementation of the reconciliation data processing method, and repeated details will not be elaborated further. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0149] Embodiments of the present invention provide a specific implementation of a reconciliation data processing device capable of implementing a reconciliation data processing method, see below. Figure 13 The reconciliation data processing device specifically includes the following components:

[0150] The transaction time determination module 10 is used to determine the transaction time and transaction type corresponding to the reconciliation request based on the reconciliation requests from multiple pre-received users;

[0151] The time range determination module 20 is used to determine the time range corresponding to the reconciliation request based on the transaction time.

[0152] The splitting result generation module 30 is used to split the transaction data corresponding to the reconciliation request according to the transaction type to generate a splitting result;

[0153] The transaction data reconciliation module 40 is used to reconcile the transaction data according to the time range and the splitting results.

[0154] In one embodiment, the time range includes: the start time of the staggered time and the end time of the staggered time; determining the time range corresponding to the reconciliation request based on the transaction time includes:

[0155] When the staggered start time and staggered end time are the first time limits, the time range is T days;

[0156] When the staggered start time and staggered end time are the second time limits, the time range is T+1 days.

[0157] In one embodiment, see Figure 14 The splitting result generation module 30 includes:

[0158] The time-sharing file generation unit 301 is used to split the transaction data according to the transaction type dimension to generate a time-sharing file;

[0159] The splitting result generation unit 302 is used to merge the time-sharing files within the T day and within the T+1 day to generate a splitting result.

[0160] In one embodiment, see Figure 15 The transaction data reconciliation module 40 includes:

[0161] The splitting result parsing unit 401 is used to parse the splitting result to obtain the transaction number, amount and channel event number of the transaction data;

[0162] The transaction data matching unit 402 is used to match the transaction data according to the serial number, amount and channel event number within day T.

[0163] As described above, the reconciliation data processing device provided in this embodiment of the invention first determines the transaction time and transaction type corresponding to the reconciliation requests based on the reconciliation requests received from multiple users; then, it determines the time range corresponding to the reconciliation request based on the transaction time; according to the transaction type, it splits the transaction data corresponding to the reconciliation request to generate a splitting result; finally, it reconciles the transaction data based on the time range and the splitting result. This invention enables banks to flexibly and accurately complete the reconciliation work for each partner institution when facing data from numerous partner institutions with different time-periods, effectively avoiding situations requiring manual intervention due to time-period discrepancies. Through flexible configuration, it can efficiently complete the reconciliation work for institutions with different time-periods, promoting more flexible and efficient cooperation between banks and other institutions.

[0164] The following is for reference. Figure 16 It shows a schematic diagram of the structure of an electronic device 600 suitable for implementing the embodiments of this application.

[0165] like Figure 16 As shown, the electronic device 600 includes a central processing unit (CPU) 601, which can perform various appropriate tasks and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the system 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

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

[0167] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0168] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0169] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0170] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0171] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0172] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for processing reconciliation data, characterized in that, include: The transaction time and transaction type corresponding to the reconciliation request are determined based on the reconciliation requests received from multiple users. The time range corresponding to the reconciliation request is determined based on the transaction time. Based on the transaction type, the transaction data corresponding to the reconciliation request is split according to the transaction type to generate a splitting result; the transaction data includes staggered transaction data files and real-time detail backup files; The transaction data is reconciled based on the stated time range and the splitting results, specifically: On T+1 day, after receiving the staggered transaction data file for day T from the institution, it is split and merged. Then, the real-time detail backup file under the bank's day T path is split and merged according to the transaction type. Then, the two files resulting from the splitting and merging of the staggered transaction data file and the real-time detail backup file are matched and verified to complete the transaction data reconciliation. Receive the off-time transaction data file and real-time detail backup file for each transaction type, and perform reconciliation according to the transaction type. During reconciliation, the data in the file is matched with the corresponding transaction serial number, amount, and channel event number. After the matching is completed, the reconciliation results are stored. The time range includes: the start time of the staggered time and the end time of the staggered time; determining the time range corresponding to the reconciliation request based on the transaction time includes: When the staggered start time and staggered end time are the first time limits, the time range is T days; When the staggered start time and staggered end time are the second time limits, the time range is T+1 days; Based on the transaction type, the step of splitting the transaction data corresponding to the reconciliation request according to the transaction type to generate a splitting result includes: The transaction data is split according to the transaction type dimension to generate time-sharing files; The time-sharing files within the T-day and the T+1-day period are merged to generate a split result.

2. The reconciliation data processing method according to claim 1, characterized in that, The reconciliation of the transaction data based on the time range and the splitting results includes: Parse the splitting results to obtain the transaction serial number, amount, and channel event number of the transaction data; Within day T, the transaction data is matched based on the serial number, amount, and channel event number.

3. The reconciliation data processing method according to claim 1, characterized in that, The step of determining the transaction time and transaction type corresponding to the reconciliation request based on the reconciliation requests from multiple pre-received users includes: The reconciliation request is received periodically; The reconciliation request is parsed to determine the transaction time and transaction type.

4. The reconciliation data processing method according to claim 3, characterized in that, The process of parsing the reconciliation request to determine the transaction time and transaction type includes: Create the corresponding XML file based on the reconciliation request; Determine the full path of the XML file based on its header file; The reconciliation request is loaded according to the full path of the XML file.

5. A reconciliation data processing device, characterized in that, include: The transaction time determination module is used to determine the transaction time and transaction type corresponding to the reconciliation requests based on the reconciliation requests received from multiple users. The time range determination module is used to determine the time range corresponding to the reconciliation request based on the transaction time. The splitting result generation module is used to split the transaction data corresponding to the reconciliation request according to the transaction type to generate a splitting result; The transaction data consists of staggered transaction data files and real-time detail backup files. The transaction data reconciliation module is used to reconcile the transaction data according to the time range and the splitting results, specifically: On T+1 day, after receiving the staggered transaction data file for day T from the institution, it is split and merged. Then, the real-time detail backup file under the bank's day T path is split and merged according to the transaction type. Then, the two files resulting from the splitting and merging of the staggered transaction data file and the real-time detail backup file are matched and verified to complete the transaction data reconciliation. Receive the off-time transaction data file and real-time detail backup file for each transaction type, and perform reconciliation according to the transaction type. During reconciliation, the data in the file is matched with the corresponding transaction serial number, amount, and channel event number. After the matching is completed, the reconciliation results are stored. The time range includes: the start time of the staggered time and the end time of the staggered time; determining the time range corresponding to the reconciliation request based on the transaction time includes: When the staggered start time and staggered end time are the first time limits, the time range is T days; When the staggered start time and staggered end time are the second time limits, the time range is T+1 days; Based on the transaction type, the step of splitting the transaction data corresponding to the reconciliation request according to the transaction type to generate a splitting result includes: The transaction data is split according to the transaction type dimension to generate time-sharing files; The time-sharing files within the T-day and the T+1-day period are merged to generate a split result.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the reconciliation data processing method according to any one of claims 1 to 4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the reconciliation data processing method according to any one of claims 1 to 4.

Images