A reconciliation method and apparatus

By adjusting the cut-off point of the error report and setting up a difference table, the problem of poor timeliness of error reports caused by the asynchronous daily cut-off points between financial institutions and clearing centers was solved, thereby improving the efficiency of error report generation and error processing.

CN117036071BActive Publication Date: 2026-11-10CHINA EVERBRIGHT BANK
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311064619.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-08-22
Publication Date
2026-11-10
Estimated Expiration
2043-08-22

AI Technical Summary

Technical Problem

The asynchronous daily cut-off times between financial institutions and clearing centers result in poor overall timeliness of error reports, a problem that current technology cannot effectively solve.

Method used

By adjusting the cut-off point of the error report and setting up a difference table, the first settlement document is used as a benchmark to check against the second settlement document, generating a first error report and a second error report. The cut-off point of the second error report is preset with an offset time, and the error is checked in conjunction with the difference table to eliminate invalid errors.

Benefits of technology

While ensuring the accuracy of error reports, the efficiency of error report generation has been improved from T+2 to T+1, which significantly improves the timeliness of error handling for financial institutions and reduces the workload of manual processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117036071B_ABST
    Figure CN117036071B_ABST
Patent Text Reader

Abstract

This invention provides a reconciliation method and apparatus. The method includes: obtaining a first clearing document of a first institution based on a first day's cutoff point; obtaining a second clearing document of a second institution based on a second day's cutoff point; comparing the first clearing document with the second clearing document to obtain a first error report; and comparing the second clearing document with the first clearing document to obtain a second error report and a difference table. The cutoff point of the second error report is preset to be earlier than the first day's cutoff point by a predetermined offset time. The difference table contains difference information within the offset time. Error reconciliation is performed based on the first error report, the second error report, and the difference table. This invention solves the problem of poor overall timeliness of error reports caused by the asynchronous daily cutoff points between financial institutions and clearing centers in related technologies. By setting up a difference table, it improves the timeliness of error processing for financial institutions.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of automatic programming, and more specifically, to a reconciliation method and apparatus. Background Technology

[0002] Financial institutions provide cardholders with cross-institutional payment and settlement services, which requires cross-institutional online financial transactions. Figure 3 This is a typical diagram illustrating a financial institution's connection to the UnionPay clearing center, such as... Figure 3 As shown, such transactions typically use a centralized clearing institution as the clearing service center for all parties (e.g., UnionPay is the clearing center for UnionPay card transactions). At the end of the day, the clearing center performs a day-end clearing operation to terminate the online transactions of the day and include all (agreed-to-be-cleared) online transactions between the day-end clearing points into the day's clearing. It also issues a clearing document to the financial institution for the full amount of transactions included in the clearing that day, so that the institution can conduct account reconciliation on the same day.

[0003] Since the clearing center currently uses 11 PM as its daily cutoff time, while financial institutions use midnight (this is just an example; the clearing center's cutoff time may be later than the financial institution's, but the principle of accurate reconciliation is similar), institutions adopt the clearing center's reconciliation principle and issue the following two types of erroneous accounts: If the clearing center has an account that the financial institution does not, the institution should use the clearing center's clearing documents to find the financial institution's reconciliation documents and verify to obtain a report stating that the clearing center has the account but the institution does not; if the financial institution has an account that the clearing center does not, the institution should use the financial institution's reconciliation documents to find the clearing center's clearing documents and verify to obtain a report stating that the institution has the account but the institution does not.

[0004] Because the daily cut-off times between institutions and clearing centers are not synchronized, the traditional method of reconciliation, in which neither financial institutions nor clearing centers have their transaction records cut off, can only generate a "Clearance with No Errors" report on T+1 (based on the clearing center's daily cut-off point being earlier than the financial institution's, the same below). However, the "Clearance with No Errors" report cannot be generated for this period due to the lack of clearing center transaction records between 11 PM and 12 AM, and can only be generated on T+2. The overall clearing cycle is relatively long and the timeliness is also relatively poor.

[0005] No solution has yet been proposed to address the aforementioned problems in the relevant technologies. Summary of the Invention

[0006] This invention provides a reconciliation method and apparatus to at least solve the problem in related technologies where the daily reconciliation time of financial institutions and clearing centers is not synchronized, resulting in poor overall timeliness of error reports.

[0007] According to one embodiment of the present invention, a reconciliation method is provided, comprising:

[0008] The first liquidation document of the first institution is obtained according to the first day's cutoff point, and the second liquidation document of the second institution is obtained according to the second day's cutoff point, wherein the first day's cutoff point is earlier than the second day's cutoff point;

[0009] The first liquidation document is compared with the second liquidation document to obtain a first error report, wherein the cut-off point of the first error report is the cut-off point of the first day;

[0010] The second liquidation document is compared with the first liquidation document to obtain a second error report and a difference table. The cut-off point of the second error report is a preset offset time earlier than the cut-off point of the first day. The difference table contains the difference information within the offset time.

[0011] Errors are checked against the first error report, the second error report, and the difference table.

[0012] Optionally, obtaining the first liquidation document of the first institution based on the first day's cutoff point, and obtaining the second liquidation document of the second institution based on the second day's cutoff point, includes:

[0013] Obtain the first settlement document for day T from the first cutoff point of day T-1 to the first cutoff point of day T;

[0014] Obtain the second clearing documents of the second institution from the second day cutoff point of day T-1 to the second day cutoff point of day T, as well as the second clearing documents of day T-1 in the previous clearing cycle.

[0015] Optionally, the first liquidation document is compared with the second liquidation document to obtain a first error report, including:

[0016] The corresponding transaction information is found in the first settlement document of day T, the second settlement document of day T, and the second settlement document of day T-1.

[0017] The transaction information that exists in the first clearing file on day T but does not exist in the second clearing file on day T or the second clearing file on day T-1 is identified as the first error information, and the first error report is obtained.

[0018] Optionally, a second error report is obtained by comparing the second liquidation document with the first liquidation document, including:

[0019] The third day's cutoff point is obtained by advancing the first day's cutoff point by the aforementioned offset time;

[0020] Based on the third day cutoff point, the offset second clearing file for day T is extracted from the second clearing file for day T and the second clearing file for day T-1, wherein the offset second clearing file for day T is the clearing file of the second institution from the third day cutoff point for day T-1 to the third day cutoff point for day T;

[0021] The corresponding transaction information is found in the first settlement file of day T based on the offset second settlement file of day T;

[0022] The transaction information that exists in the offset second clearing file on day T but does not exist in the first clearing file on day T is identified as the second error information, and the second error report is obtained.

[0023] Optionally, a discrepancy table is obtained by comparing the second liquidation document with the first liquidation document, including:

[0024] Extract the second clearing file within the offset time period from the second clearing file of day T, wherein the second clearing file within the offset time period is the clearing file of the second institution from the cutoff point of day T to the cutoff point of day T;

[0025] Based on the second clearing file within the specified offset time, the corresponding transaction information is retrieved from the first clearing file on day T.

[0026] The transaction information that exists in the second clearing file within the offset time period but does not exist in the first clearing file on day T is determined as the difference table.

[0027] Optionally, error matching is performed based on the first error report, the second error report, and the difference table, including at least one of the following:

[0028] Eliminate paired reversal and cancellation transactions in the first error report;

[0029] Eliminate paired reversal transactions in the second error report and the difference table;

[0030] Eliminate paired confirmation transactions in the first error report and the second error report;

[0031] Eliminate paired confirmation transactions in the first error report and the difference table.

[0032] Optionally, the method further includes:

[0033] When generating the first error report or the second error report, mark the error generation time corresponding to the error information;

[0034] The error information in the error report is assigned to the error list corresponding to the transaction type based on the error generation time, wherein the error generation time is different for different transaction types.

[0035] According to another embodiment of the present invention, an account reconciliation device is also provided, comprising:

[0036] The acquisition module is used to acquire the first liquidation document of the first institution based on the first day cutoff point, and to acquire the second liquidation document of the second institution based on the second day cutoff point, wherein the first day cutoff point is earlier than the second day cutoff point;

[0037] The first verification module is used to verify the first liquidation document against the second liquidation document to obtain a first error report, wherein the cut-off point of the first error report is the cut-off point of the first day;

[0038] The second verification module is used to verify the second settlement document against the first settlement document to obtain a second error report and a difference table. The cut-off point of the second error report is a preset offset time earlier than the cut-off point of the first day, and the difference table contains the difference information within the offset time.

[0039] The error matching module is used to perform error matching based on the first error report, the second error report, and the difference table.

[0040] Optionally, the acquisition module includes:

[0041] The first acquisition unit is used to acquire the first settlement document of the first institution from the first day cutoff point of day T-1 to the first day cutoff point of day T;

[0042] The second acquisition unit is used to acquire the second settlement document of day T from the second day cutoff point of day T-1 to the second day cutoff point of day T, and the second settlement document of day T-1 in the previous settlement cycle.

[0043] Optionally, the first verification module includes:

[0044] The first search unit is used to search for corresponding transaction information in the second settlement document on day T and the second settlement document on day T-1 based on the first settlement document on day T.

[0045] The first determining unit is used to determine the transaction information that exists in the first clearing file on day T but does not exist in the second clearing file on day T or the second clearing file on day T-1 as the first error information, and to obtain the first error report.

[0046] Optionally, the second verification module includes:

[0047] An advance unit is used to advance the first day's cut-off point by the offset time to obtain the third day's cut-off point;

[0048] The first extraction unit is used to extract the offset second settlement file of day T from the second settlement file of day T and the second settlement file of day T-1 according to the third day cutoff point, wherein the offset second settlement file of day T is the settlement file of the second institution from the third day cutoff point of day T-1 to the third day cutoff point of day T;

[0049] The second search unit is used to search for the corresponding transaction information in the first clearing file of day T based on the offset second clearing file of day T.

[0050] The second determining unit is used to determine the transaction information that exists in the offset second clearing file of day T but does not exist in the first clearing file of day T as the second error information, and to obtain the second error report.

[0051] Optionally, the second verification module further includes:

[0052] The second extraction unit is used to extract the second clearing file within the offset time from the second clearing file of day T, wherein the second clearing file within the offset time is the clearing file of the second institution from the cut-off point of day T to the cut-off point of day T;

[0053] The third search unit is used to search for the corresponding transaction information in the first clearing file on day T based on the second clearing file within the offset time period;

[0054] The third determining unit is used to determine the transaction information that exists in the second clearing file within the offset time but does not exist in the first clearing file on day T as the difference table.

[0055] Optionally, the error matching module includes:

[0056] The elimination unit is configured to perform error matching based on the first error report, the second error report, and the difference table, including at least one of the following: eliminating paired reversal transactions and cancellation transactions in the first error report; eliminating paired reversal transactions in the second error report and the difference table; eliminating paired confirmation transactions in the first error report and the second error report; and eliminating paired confirmation transactions in the first error report and the difference table.

[0057] Optionally, the device further includes:

[0058] The marking module is used to mark the error generation time corresponding to the error information when generating the first error report or the second error report;

[0059] The classification module is used to classify the error information in the error report into the error list of the corresponding transaction type according to the error generation time, wherein the error generation time is different for different transaction types.

[0060] According to yet another embodiment of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is executed by a processor to perform the steps in any of the above method embodiments.

[0061] According to yet another embodiment of the present invention, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0062] This invention solves the problem of poor timeliness of error reports caused by the asynchronous daily cut-off points between financial institutions and clearing centers in related technologies. By adjusting the cut-off points of error reports and setting up a difference table, the generation efficiency of error reports is improved from T+2 to T+1 while ensuring the accuracy of error reports, which greatly improves the timeliness of error handling for financial institutions. At the same time, invalid errors in error reports are automatically eliminated through error matching, reducing the workload of subsequent manual processing and improving error handling efficiency. Attached Figure Description

[0063] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0064] Figure 1 This is a hardware structure block diagram of the computer terminal for the reconciliation method according to an embodiment of the present invention;

[0065] Figure 2 This is a flowchart of the reconciliation method according to an embodiment of the present invention;

[0066] Figure 3 This is a typical diagram illustrating a financial institution's connection to a clearing center;

[0067] Figure 4 This is a diagram illustrating the daily cutoff point and error generation time in traditional reconciliation methods;

[0068] Figure 5 This is a schematic diagram of the daily cutoff point and error generation time according to an embodiment of the present invention;

[0069] Figure 6 This is a schematic diagram of the error report coverage according to an embodiment of the present invention;

[0070] Figure 7This is a schematic diagram of the processing flow of the reconciliation system according to an embodiment of the present invention;

[0071] Figure 8 This is a block diagram of an account reconciliation device according to an embodiment of the present invention. Detailed Implementation

[0072] The present invention will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the present application can be combined with each other.

[0073] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0074] Example 1

[0075] The method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking its operation on a computer terminal as an example, Figure 1 This is a hardware structure block diagram of the computer terminal for the reconciliation method according to an embodiment of the present invention, such as... Figure 1 As shown, a computer terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. Optionally, the computer terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the computer terminal described above. For example, the computer terminal may also include components that are more complex than those described above. Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0076] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the reconciliation method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0077] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0078] This embodiment provides a reconciliation method that runs on the aforementioned computer terminal or network architecture. Figure 2 This is a flowchart of the reconciliation method according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps:

[0079] Step S202: Obtain the first liquidation document of the first institution based on the first day's cutoff point, and obtain the second liquidation document of the second institution based on the second day's cutoff point;

[0080] Step S204: Compare the first liquidation document with the second liquidation document to obtain a first error report;

[0081] Step S206: Compare the second liquidation document with the first liquidation document to obtain a second error report and a difference table;

[0082] Step S208: Perform error matching based on the first error report, the second error report, and the difference table.

[0083] In this embodiment, the cutoff point of the first day is earlier than the cutoff point of the second day. The cutoff point of the first error report is the cutoff point of the first day. The cutoff point of the second error report is earlier than the cutoff point of the first day by a preset offset time, and the difference table contains the difference information within the offset time.

[0084] In this embodiment, the offset time can be set to a shorter time period, including but not limited to 10 minutes or less. Setting the offset time can avoid the impact of cut-off point glitch data on error reports when the clocks of financial institutions and clearing centers are out of sync.

[0085] Steps S202 to S208 can solve the problem of poor overall timeliness of error reports caused by the asynchronous daily cut-off points of financial institutions and clearing centers in related technologies. By moving the cut-off point of the second error report forward, the generation efficiency of error reports can be improved. By setting a difference table, the accuracy of error generation can be guaranteed, and the impact of spurious data on error reports can be prevented.

[0086] In an optional embodiment, step S202 may include the following steps:

[0087] Step S2022: Obtain the first settlement document of day T from the first day cutoff point of day T-1 to the first day cutoff point of day T;

[0088] Step S2024: Obtain the second settlement document of day T from the second cutoff point of day T-1 to the second cutoff point of day T, and the second settlement document of day T-1 in the previous settlement cycle.

[0089] In an optional embodiment, step S204 may include the following steps:

[0090] Step S2042: Based on the first clearing document of day T, search for the corresponding transaction information in the second clearing document of day T and the second clearing document of day T-1;

[0091] Step S2044: Transaction information that exists in the first clearing file on day T but does not exist in the second clearing file on day T or the second clearing file on day T-1 is identified as first error information, and the first error report is obtained.

[0092] In an optional embodiment, step S206 may include the following steps:

[0093] Step S2061: Advance the first day's cut point by the offset time to obtain the third day's cut point;

[0094] Step S2062: Extract the offset second clearing file of day T from the second clearing file of day T and the second clearing file of day T-1 according to the third day cutoff point, wherein the offset second clearing file of day T is the clearing file of the second institution from the third day cutoff point of day T-1 to the third day cutoff point of day T;

[0095] Step S2063: Search for the corresponding transaction information in the first clearing file of day T based on the offset second clearing file of day T;

[0096] Step S2064: The transaction information that exists in the offset second clearing file of day T but does not exist in the first clearing file of day T is determined as the second error information, and the second error report is obtained.

[0097] In an optional embodiment, step S206, when generating the second error report, also needs to consider the difference table of day T-1 or the settlement documents of the first institution from the third day cutoff point of day T-1 to the first day cutoff point of day T-1.

[0098] In an optional embodiment, step S206 may further include the following steps:

[0099] Step S2065: Extract the second clearing file within the offset time from the second clearing file of day T, wherein the second clearing file within the offset time is the clearing file of the second institution from the cutoff point of day T to the cutoff point of day T;

[0100] Step S2066: Search for the corresponding transaction information in the first clearing file on day T based on the second clearing file within the offset time period;

[0101] Step S2067: The transaction information that exists in the second clearing file within the offset time period but does not exist in the first clearing file on day T is determined as the difference table.

[0102] In an optional embodiment, the error matching based on the first error report, the second error report, and the difference table in step S208 may include at least one of the following:

[0103] Eliminate paired reversal and cancellation transactions in the first error report;

[0104] Eliminate paired reversal transactions in the second error report and the difference table;

[0105] Eliminate paired confirmation transactions in the first error report and the second error report;

[0106] Eliminate paired confirmation transactions in the first error report and the difference table.

[0107] In an optional embodiment, the method further includes: marking the error generation time corresponding to the error information when generating the first error report or the second error report; and classifying the error information in the error report into the error list of the corresponding transaction type according to the error generation time, wherein the error generation time corresponding to different transaction types is different.

[0108] In an exemplary embodiment, the first institution may be a clearing center or UnionPay, and the second institution may be a financial institution or a bank. Correspondingly, the first error report may be a "clearing center has no error report" or a "UnionPay has no error report," and the second error report may be a "clearing center has no error report" or a "UnionPay has no error report" (here, "I" can refer to the bank). This embodiment of the invention is based on the clearing center's daily cutoff point being earlier than the financial institution's daily cutoff point, but the reverse is also possible.

[0109] In an optional embodiment, after step S208, the method further includes sending the checked error report to the error handling personnel for manual processing, or entering the corresponding automated error handling process according to the transaction type of the error.

[0110] Figure 3 This is a typical diagram illustrating a financial institution's connection to a clearing center, such as... Figure 3 As shown, inter-institutional reconciliation is handled by the front-end systems within each financial institution. The reconciliation method in this invention is primarily applied to the front-end systems of each financial institution.

[0111] In an exemplary embodiment, the first institution is a clearing center, which sets its daily cutoff time at 11 PM. The second institution is a financial institution, which sets its daily cutoff time at midnight (this is just an example; the clearing center's cutoff time may also be later than the financial institution's). In reconciliation with the clearing center, the clearing center's reconciliation principle is adopted, and the following two aspects of erroneous accounts are issued:

[0112] 1. Clearing Center has financial institutions but no financial institutions: Search the financial institution's reconciliation documents using the clearing center's clearing documents, and verify the "clearing center has financial institutions but no financial institutions" error report from 23:00 on day T-1 to 23:00 on day T (equivalent to the first error report);

[0113] 2. Financial institutions have clearing center but no clearing center: Locate the clearing center's clearing documents using the financial institution's reconciliation documents, and verify the "I have clearing and no error report" from 22:50 on T-1 day to 22:50 on T day (equivalent to the second error report).

[0114] Furthermore, the clearing center and financial institution differ in different transaction scenarios. For example, in UnionPay card transactions, the clearing center is UnionPay, and this invention does not impose any restrictions on this.

[0115] Using the method in this embodiment of the invention, when the clearing center's daily cut-off point is earlier than the financial institution's daily cut-off point, the clearing center's transaction volume is still reconciled using the traditional method of not splitting, and the first error report of day T is verified on day T+1; while the financial institution also achieves the verification of the second error report of day T on day T+1 by moving the cut-off point of the second error report forward, thereby shortening the overall error processing time.

[0116] Figure 4 This is a diagram illustrating the daily cutoff point and error generation time in traditional reconciliation methods, such as... Figure 4 As shown, a typical debit card reconciliation example is used:

[0117] Daily cut-off points: approximately 24 points for the core system, approximately 24 points for the front-end system, and approximately 23 points for the UnionPay Clearing Center.

[0118] Error time limit: Debit card errors must be corrected on day T+2.

[0119] Reconciliation mode: The front-end system receives UnionPay clearing documents and internal reconciliation documents on T+1, and reconciles them with the front-end system's transaction records in pairs according to UnionPay reconciliation and internal reconciliation. The final error is then calculated after summarizing the reconciliation results.

[0120] UnionPay reconciliation: Use UnionPay's T-day clearing documents to find the internal documents for T-day and T-1 day, and output the information from 23:00 on T-1 day to 23:00 on T day, showing that UnionPay has the information and there are no errors (T+1 time limit) [according to UnionPay's T-day clearing date].

[0121] Intra-bank reconciliation: Locate the UnionPay clearing document on day T using the intra-bank T-1 and T-day reconciliation documents, and find the UnionPay error record from 00:00 on day T-1 to 24:00 on day T-1 (T+2 time limit) [according to the intra-bank T-1 accounting date].

[0122] When using traditional reconciliation methods, it is impossible to verify all errors by T+1 (if UnionPay has an error but I don't, T+1; if UnionPay doesn't have an error but I do, T+2), requiring T+2 to complete the process, resulting in poor timeliness. In addition, the error reports contain a large number of paired errors, requiring a significant amount of manual review and screening, leading to low error processing efficiency.

[0123] This application uses debit card reconciliation as an example, but it may also include, but is not limited to, credit card reconciliation. In credit card reconciliation, the bank's daily cutoff point may be earlier than UnionPay's daily cutoff point. In this case, UnionPay's daily cutoff point is used as the benchmark for UnionPay reconciliation and intra-bank reconciliation.

[0124] Figure 5 This is a schematic diagram of the daily cutoff point and error generation time according to an embodiment of the present invention. Figure 5 As shown, a daily cutoff point (usually 23:00) is introduced from the clearing institution (UnionPay) to divide the intra-bank reconciliation data on day T.

[0125] This invention allows the "UnionPay No-Own-Factory" error interval to be moved from day T-1 to day T, meaning that UnionPay No-Own-Factory errors for day T can be generated on day T+1. Accurate errors occurring before 11 PM on day T (UnionPay's daily cut-off time) (covering 98.5% of the day's transaction volume) can be completed on day T+1 (improving timeliness by one day), thereby enhancing overall error generation efficiency.

[0126] In this embodiment, to avoid the influence of glitch data at the cut-off point, the cut-off point is moved forward by 10 minutes and a difference table (suspected error) is generated for this time period. This difference table is used to eliminate paired errors across reports (22:50-23:00).

[0127] In this embodiment, UnionPay reconciliation uses the UnionPay clearing file on day T to search for the reconciliation files on day T and day T-1 within the bank, and outputs "UnionPay has no errors (T+1 time limit)," generating "UnionPay has no errors from 23:00 on day T-1 to 23:00 on day T" [same as the traditional method].

[0128] In this embodiment, intra-bank reconciliation uses the intra-bank reconciliation files of day T-1 and day T to search the UnionPay clearing files. Intra-bank data before the shift date cutoff (22:50) on day T is reconciled, resulting in a daily error. Intra-bank data after the shift date cutoff (22:50) on day T participates in the reconciliation but does not generate errors; only a difference table is generated to eliminate cross-report errors (22:50-23:00). Differences within this 10-minute period are matched against UnionPay's "I have no errors" list to check for paired errors and eliminate them. The final output is the UnionPay "I have no errors" list from 22:50 on day T-1 to 22:50 on day T [different from traditional methods].

[0129] In an optional embodiment, during the reconciliation on day T-1, a difference table for day T-1 (22:50-23:00) is also generated that only participates in the reconciliation and does not generate errors. During the reconciliation on day T, the difference table for day T-1 is reconfirmed and written to the second error table for day T to make up for this part of the time error, and finally the second error table for day T (from 22:50 on day T-1 to 22:50 on day T) is formed.

[0130] In one exemplary embodiment, the discrepancy table may contain errors where some transactions accepted at 23:00 were recorded within the bank but not cleared by UnionPay. The discrepancy table is used to fill in UnionPay's missing errors during the offset time period and is a shadow table of the second error table.

[0131] In an optional embodiment, three types of error elimination are also set to perform positive and negative transaction matching (including matching within a single report and matching across reports) to eliminate invalid errors and improve error quality.

[0132] In one alternative embodiment, the three types of error elimination are as follows:

[0133] 1. Paired erroneous transactions in the clearing report (can be eliminated in this report: such as consumption and consumption reversal transactions appearing in pairs in the clearing file, but not recorded in the bank's books, generally reflected in the card issuer's transactions);

[0134] 2. I have paired erroneous transactions in the cleared and error-free report (which can be eliminated in the report: for example, consumption and consumption reversal transactions appear in pairs in the bank's reconciliation file, but are not reflected in the clearing file, and are generally reflected in the receiving party's transactions);

[0135] 3. Paired errors across reports: These errors are reflected in two separate reports, "Clearance with no errors" and "I have cleared with no errors," and they appear in pairs (cross-report elimination is possible: for example, credit entries "I have cleared but no errors" and credit confirmation entries "Cleared but no errors" appear in pairs).

[0136] In this embodiment, the difference table can also be used to eliminate pairwise errors across reports of type 3 (22:50-23:00).

[0137] In an exemplary embodiment, the paired error transactions in the Clearing and Error-Free Report may include any of the following: withdrawal / withdrawal reversal; deposit / deposit cancellation; pre-authorization completion / pre-authorization completion cancellation; pre-authorization completion / pre-authorization completion; consumption / consumption cancellation; consumption / consumption reversal; collection / collection reversal; collection / collection cancellation; transfer out / transfer out reversal; transfer out / transfer out cancellation.

[0138] In an exemplary embodiment, the paired error transactions in the clear and error-free report may include any of the following: withdrawal on behalf of another party / reversal of withdrawal on behalf of another party; consumption on behalf of another party / reversal of consumption on behalf of another party; completion of pre-authorization on behalf of another party / reversal of pre-authorization completion on behalf of another party.

[0139] In an exemplary embodiment, cross-report pairwise errors may include any of the following: credit (bank accounting) and credit confirmation (UnionPay accounting) transactions, which are actually acceptances of the same transaction, but due to system processing abnormalities, the bank and UnionPay accounting transactions are not the same.

[0140] In an optional embodiment, the error generation date can be used instead of the clearing date concept, breaking the original limitation of errors occurring based on transaction dates, and forming an error generation report after segmenting data according to the reconciliation date.

[0141] In this embodiment, UnionPay reconciliation involves searching the UnionPay T-day clearing documents for the T-day and T-1-day internal documents, and outputting the period from 23:00 on T-1-day to 23:00 on T-day (T+1 timeframe). Previously, errors were tagged according to the UnionPay T-day clearing date; this has been adjusted to tag errors based on the T+1-day error generation date. That is, errors verified on T+1-day are tagged with the error generation date T+1.

[0142] In this embodiment, for intra-bank reconciliation, the T-1 and T-day reconciliation files are used to find the UnionPay clearing file on day T, and the UnionPay error is found between 00:00 on T-1 day and 24:00 on T-1 day (T+2 time limit). Originally, the error was labeled according to the intra-bank accounting date of T-1 day. This time, it is adjusted to label the error as occurring on T+1 day. That is, the error verified on T+1 day is labeled with the error generation date T+1.

[0143] In an exemplary embodiment, UnionPay's transfer transactions can be cancelled by customers within 24 hours. UnionPay's actual clearing can only be completed on T+2. During the reconciliation process of commercial banks, the earliest time to confirm accounting errors is the early morning of T+3. By tagging the errors based on their generation date, transactions with longer processing times can be separated without affecting the processing time of other transactions.

[0144] In this embodiment, the transaction times covered by the first and second error tables are not exactly the same. In addition, due to the special nature of transfer transactions, it is impossible to achieve a unified understanding of errors in different dimensions. By introducing the error generation date, the business's understanding of errors can be aligned through the error generation time.

[0145] In this embodiment, errors are not generated based on the actual time of the transaction in the transaction log. Instead, the error date dimension is adjusted to the date of error generation to accommodate errors from different dates within the same row and display them under the same error generation date. This error method also provides support for grouping errors such as delayed transfers that exceed 3 days into a single error generation date.

[0146] Figure 6 This is a schematic diagram illustrating the coverage of error reports according to an embodiment of the present invention. Figure 6 As shown, the following error report can be generated on T+1 day:

[0147] UnionPay error report from 23:00 on day T-1 to 23:00 on day T (first error report);

[0148] UnionPay error report from 22:50 on day T-1 to 22:50 on day T (Second Error Report).

[0149] In this embodiment, the second error report is generated 10 minutes earlier than the first error report (this time is only for example) to avoid abnormal situations at the daily cutoff point. UnionPay data between 22:50 and 23:00 on day T is not included in the generation of the error report, but the difference data within this 10-minute period can be used for subsequent error reconciliation and provided to error processing personnel for reference.

[0150] In this embodiment, the report interval is set to a half-open, half-closed form to prevent data at the cut-off point from being calculated repeatedly.

[0151] Figure 7 This is a schematic diagram of the processing flow of the reconciliation system according to an embodiment of the present invention. Figure 7 As shown, the reconciliation system includes the following structure:

[0152] Document processing module 72, reconciliation module 74, error generation module 76, and error matching module 78.

[0153] In this embodiment, the file processing module is used to obtain transaction records from various locations and preprocess them. For example, it obtains core files from the core system, obtains front-end transaction records from the front-end system, records the UnionPay daily cut-off time through the front-end system, obtains UnionPay clearing files from UnionPay, and generates corresponding core transaction records, front-end transaction records, UnionPay daily cut-off records, and UnionPay clearing transaction records, respectively.

[0154] In this embodiment, the file processing module introduces a daily cut-off time point recording function, which is registered by the online transaction system and referenced during the reconciliation process.

[0155] In this embodiment, the reconciliation module is used to reconcile accounts based on the core transaction log and the preceding transaction log. The core reconciliation identifier in the preceding transaction log is updated according to the transaction number and date, specifically the core transaction log and the preceding transaction log from 0:00 to 24:00 on day T.

[0156] In this embodiment, the reconciliation module is also used to reconcile accounts based on the pre-processing transaction record and the UnionPay clearing transaction record, and update the UnionPay reconciliation identifier according to the UnionPay key field, specifically the UnionPay clearing transaction record from 23:00 on day T-1 to 23:00 on day T and the pre-processing transaction record from 0:00 to 24:00 on day T.

[0157] In this embodiment, the error generation module is used to aggregate the reconciliation results in the reconciliation module, and determine whether the daily reconciliation is abnormal according to the UnionPay daily reconciliation table, and generate UnionPay No Error and UnionPay No Error for T+1 (Daily reconciliation normal) or T+2 (Daily reconciliation abnormal).

[0158] Specifically, under normal circumstances, if the transaction is processed normally on day T+1, there will be no error on my part from day T-1 to day T, and there will be no error on my part from day T+1 to day T.

[0159] In this embodiment, the error generation module is also used to use the "daily cut-off point" introduced in the file processing module and to divide the intra-line flow data of the day according to the daily cut-off point.

[0160] Specifically, in order to accurately segment clearing records, the front-end system records the UnionPay daily segmentation time and segments debit card transaction records according to that time minus 10 minutes.

[0161] In this embodiment, the UnionPay daily cut-off time point is introduced as a key element for splitting T-day data. Considering abnormal situations before and after the daily cut-off point (such as the UnionPay daily cut-off notification arriving later than the next day's transaction), financial institutions proactively advance the cut-off point by 10 minutes and generate a discrepancy table (suspected error) within 10 minutes.

[0162] Specifically, a semi-open, semi-closed interval can be used for time-point segmentation, that is, the daily UnionPay "No Me" error data is processed according to the following formula:

[0163] Previous day's daily cut-10 minutes <= transaction date and time < next day's daily cut-10 minutes;

[0164] This ensures that the daily transaction data is not overlapping.

[0165] In this embodiment, the suspected reconciliation errors within the 10-minute period are generated into a discrepancy table, which is used to eliminate paired errors across reports.

[0166] In this embodiment, if a delayed transfer occurs in the reconciliation results, the error generation module is also used to generate a delayed transfer error for T-2 on T+1 (T+3 time limit).

[0167] In this embodiment, the error matching module uses the UnionPay "I have but no" and "UnionPay "I have but no" reports to be matched based on the error generation date generated in the error generation module to eliminate the eliminateable transaction types.

[0168] In this embodiment, the transaction type may include the following:

[0169] A. Unilateral transactions in the "Clearance Report with No Errors" and paired erroneous transactions in the "Clearance Report with No Errors" (which can be eliminated in this report: for example, consumption and consumption reversal transactions appear in pairs in the clearing documents, but are not recorded in the bank's books, and are generally reflected in the card issuer's transactions). Based on the key information retrieved from this type of transaction record, UnionPay is used as an example here:

[0170] Field 7: Date and time of transaction sending; Field 11: System tracking number; Field 32: Accepting agency number; Field 33: Sending agency number, which uniquely defines a pair of transactions in the original transaction and the reversal transaction and cancels out such pairs of transactions to avoid errors.

[0171] B. I have one-sided accounts in the clear and error-free statement, as well as paired erroneous transactions in the clear and error-free statement (which can be eliminated in this statement: for example, consumption and consumption reversal transactions appear in pairs in the intra-bank reconciliation file, but are not reflected in the settlement file, and are generally reflected in the receiving party's transactions). Based on the key information retrieved in this type of transaction record, here we take intra-bank transaction records as an example:

[0172] The accounting date - internal transaction number uniquely defines a pair of transactions in the original transaction and the reversal transaction, and cancels out such pairs of transactions to prevent errors.

[0173] C. This is reflected in two separate reports: "Clearance with No Errors" and "I Have Clearance with No Errors," and they appear in pairs (cross-report elimination is possible, such as credit entries "I Have Clearance with No Errors" and credit confirmation entries "Clearance with No Errors" appearing as pairs). Based on the key information retrieved from this type of transaction record, here we take an intra-bank transaction record as an example:

[0174] Starting from the "Clearance and No Errors" report, the unique identifier of the credit confirmation from the clearing center (taking UnionPay as an example) is used to link the credit transactions with the same key elements (field 7: transaction sending date and time; field 11: system tracking number; field 32: accepting institution number; field 33: sending institution number) in the "Clearance and No Errors" report, thereby canceling out paired errors in the two reports and preventing errors from forming.

[0175] In this embodiment, by marking the error generation date on the error during the error generation process, intra-industry transactions with different error cycles can be grouped together to the same error generation date, so that intra-industry errors can be quickly entered into the error list according to different transaction types (with different error cycles).

[0176] In this embodiment, the error matching module is also used to send the matched UnionPay "I have but not me" and "UnionPay "I have but not me" reports to the error handling personnel for manual error processing.

[0177] This embodiment can improve error processing efficiency from T+2 to T+1, significantly enhancing the timeliness of error processing for financial institutions to adapt to the increased timeliness brought about by the current digitalization of transactions. It can also improve error accuracy and increase the work efficiency of error processing personnel. Backtesting with actual production data has reduced the proportion of invalid errors by an average of 81.8%.

[0178] According to another embodiment of the present invention, an account reconciliation device is also provided. Figure 8 This is a block diagram of an account reconciliation device according to an embodiment of the present invention, such as... Figure 8 As shown, the reconciliation device includes:

[0179] The acquisition module 82 is used to acquire the first liquidation document of the first institution based on the first day cutoff point, and to acquire the second liquidation document of the second institution based on the second day cutoff point, wherein the first day cutoff point is earlier than the second day cutoff point;

[0180] The first verification module 84 is used to verify the first liquidation document against the second liquidation document to obtain a first error report, wherein the cut-off point of the first error report is the cut-off point of the first day;

[0181] The second verification module 86 is used to verify the second settlement document against the first settlement document to obtain a second error report and a difference table. The cut-off point of the second error report is a preset offset time earlier than the cut-off point of the first day, and the difference table contains the difference information within the offset time.

[0182] The error matching module 88 is used to perform error matching based on the first error report, the second error report, and the difference table.

[0183] In one optional embodiment, the acquisition module includes:

[0184] The first acquisition unit is used to acquire the first settlement document of the first institution from the first day cutoff point of day T-1 to the first day cutoff point of day T;

[0185] The second acquisition unit is used to acquire the second settlement document of day T from the second day cutoff point of day T-1 to the second day cutoff point of day T, and the second settlement document of day T-1 in the previous settlement cycle.

[0186] In an optional embodiment, the first verification module includes:

[0187] The first search unit is used to search for corresponding transaction information in the second settlement document on day T and the second settlement document on day T-1 based on the first settlement document on day T.

[0188] The first determining unit is used to determine the transaction information that exists in the first clearing file on day T but does not exist in the second clearing file on day T or the second clearing file on day T-1 as the first error information, and to obtain the first error report.

[0189] In an optional embodiment, the second verification module includes:

[0190] An advance unit is used to advance the first day's cut-off point by the offset time to obtain the third day's cut-off point;

[0191] The first extraction unit is used to extract the offset second settlement file of day T from the second settlement file of day T and the second settlement file of day T-1 according to the third day cutoff point, wherein the offset second settlement file of day T is the settlement file of the second institution from the third day cutoff point of day T-1 to the third day cutoff point of day T;

[0192] The second search unit is used to search for the corresponding transaction information in the first clearing file of day T based on the offset second clearing file of day T.

[0193] The second determining unit is used to determine the transaction information that exists in the offset second clearing file of day T but does not exist in the first clearing file of day T as the second error information, and to obtain the second error report.

[0194] In an optional embodiment, the second verification module further includes:

[0195] The second extraction unit is used to extract the second clearing file within the offset time from the second clearing file of day T, wherein the second clearing file within the offset time is the clearing file of the second institution from the cut-off point of day T to the cut-off point of day T;

[0196] The third search unit is used to search for the corresponding transaction information in the first clearing file on day T based on the second clearing file within the offset time period;

[0197] The third determining unit is used to determine the transaction information that exists in the second clearing file within the offset time but does not exist in the first clearing file on day T as the difference table.

[0198] In an optional embodiment, the error matching module includes:

[0199] The elimination unit is configured to perform error matching based on the first error report, the second error report, and the difference table, including at least one of the following: eliminating paired reversal transactions and cancellation transactions in the first error report; eliminating paired reversal transactions in the second error report and the difference table; eliminating paired confirmation transactions in the first error report and the second error report; and eliminating paired confirmation transactions in the first error report and the difference table.

[0200] In an optional embodiment, the apparatus further includes:

[0201] The marking module is used to mark the error generation time corresponding to the error information when generating the first error report or the second error report;

[0202] The classification module is used to classify the error information in the error report into the error list of the corresponding transaction type according to the error generation time, wherein the error generation time is different for different transaction types.

[0203] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0204] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program is executed by a processor to perform the steps in any of the above method embodiments.

[0205] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0206] S1, obtain the first liquidation document of the first institution based on the cutoff point of the first day, and obtain the second liquidation document of the second institution based on the cutoff point of the second day;

[0207] S2, compare the first liquidation document with the second liquidation document to obtain the first error report;

[0208] S3, compare the second liquidation document with the first liquidation document to obtain a second error report and a difference table;

[0209] S4, perform error matching based on the first error report, the second error report, and the difference table. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0210] Embodiments of the present invention also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0211] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0212] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0213] S1, obtain the first liquidation document of the first institution based on the cutoff point of the first day, and obtain the second liquidation document of the second institution based on the cutoff point of the second day;

[0214] S2, compare the first liquidation document with the second liquidation document to obtain the first error report;

[0215] S3, compare the second liquidation document with the first liquidation document to obtain a second error report and a difference table;

[0216] S4, perform error matching based on the first error report, the second error report, and the difference table.

[0217] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0218] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0219] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A reconciliation method, characterized in that, include: Obtain the first clearing document of day T from the first day cutoff point of day T-1 to the first day cutoff point of day T of the first institution, and obtain the second clearing document of day T from the second day cutoff point of day T-1 to the second day cutoff point of day T of the second institution, as well as the second clearing document of day T-1 of the previous clearing cycle, wherein the first day cutoff point is earlier than the second day cutoff point; The first liquidation document is compared with the second liquidation document to obtain a first error report, wherein the cut-off point of the first error report is the cut-off point of the first day; The second liquidation document is compared with the first liquidation document to obtain a second error report and a difference table. The cut-off point of the second error report is a preset offset time earlier than the cut-off point of the first day. The difference table contains the difference information within the offset time. Perform error matching based on the first error report, the second error report, and the difference table; The process of comparing the second clearing document with the first clearing document to obtain a second error report includes: advancing the first day's cutoff point by the offset time to obtain a third day's cutoff point; extracting the offset second clearing document of day T from the second clearing document of day T and the second clearing document of day T-1 based on the third day's cutoff point, wherein the offset second clearing document of day T is the clearing document of the second institution from the third day's cutoff point of day T-1 to the third day's cutoff point of day T; searching for corresponding transaction information in the first clearing document of day T based on the offset second clearing document of day T; identifying transaction information that exists in the second clearing document of day T but does not exist in the first clearing document of day T as second error information, and obtaining the second error report; The difference table is obtained by comparing the second clearing document with the first clearing document, which includes: extracting the second clearing document within the offset time from the second clearing document of day T, wherein the second clearing document within the offset time is the clearing document of the second institution from the cutoff point of day T to the cutoff point of day T; searching for the corresponding transaction information in the first clearing document of day T based on the second clearing document within the offset time; and determining the transaction information that exists in the second clearing document within the offset time but does not exist in the first clearing document of day T as the difference table.

2. The method according to claim 1, characterized in that, A first error report is obtained by comparing the first liquidation document with the second liquidation document, based on the first liquidation document, including: The corresponding transaction information is found in the first settlement document of day T, the second settlement document of day T, and the second settlement document of day T-1. The transaction information that exists in the first clearing file on day T but does not exist in the second clearing file on day T or the second clearing file on day T-1 is identified as the first error information, and the first error report is obtained.

3. The method according to claim 1, characterized in that, Error matching is performed based on the first error report, the second error report, and the difference table, including at least one of the following: Eliminate paired reversal and cancellation transactions in the first error report; Eliminate paired reversal transactions in the second error report and the difference table; Eliminate paired confirmation transactions in the first error report and the second error report; Eliminate paired confirmation transactions in the first error report and the difference table.

4. The method according to claim 1, characterized in that, The method further includes: When generating the first error report or the second error report, mark the error generation time corresponding to the error information; The error information in the error report is assigned to the error list corresponding to the transaction type based on the error generation time, wherein the error generation time is different for different transaction types.

5. A reconciliation device, characterized in that, include: The acquisition module is used to acquire the first clearing document of day T from the first day cutoff point of day T-1 to the first day cutoff point of day T of the first institution, and to acquire the second clearing document of day T from the second day cutoff point of day T-1 to the second day cutoff point of day T of the second institution, as well as the second clearing document of day T-1 in the previous clearing cycle, wherein the first day cutoff point is earlier than the second day cutoff point; The first verification module is used to verify the first liquidation document against the second liquidation document to obtain a first error report, wherein the cut-off point of the first error report is the cut-off point of the first day; The second verification module is used to verify the second settlement document against the first settlement document to obtain a second error report and a difference table. The cut-off point of the second error report is a preset offset time earlier than the cut-off point of the first day, and the difference table contains the difference information within the offset time. The error matching module is used to perform error matching based on the first error report, the second error report, and the difference table. The apparatus further includes: advancing the first day cutoff point by the offset time to obtain a third day cutoff point; extracting the offset second day clearing file from the second clearing file of day T and the second clearing file of day T-1 based on the third day cutoff point, wherein the offset second day clearing file of day T is the clearing file of the second institution from the third day cutoff point of day T-1 to the third day cutoff point of day T; searching for corresponding transaction information in the first clearing file of day T based on the offset second day clearing file of day T; determining the transaction information present in the offset second day clearing file of day T but not present in the first clearing file of day T as second error information, and obtaining a second error report; extracting the second clearing file within the offset time from the second day clearing file of day T, wherein the second clearing file within the offset time is the clearing file of the second institution from the third day cutoff point of day T to the second day cutoff point of day T; searching for corresponding transaction information in the first clearing file of day T based on the second clearing file within the offset time; determining the transaction information present in the second clearing file within the offset time but not present in the first clearing file of day T as the difference table.

6. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, wherein the computer program is executed by a processor to perform the method described in any one of claims 1 to 4.

7. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the method of any one of claims 1 to 4.

Citation Information

Patent Citations

  • Daily switching judgment method and device

    CN109598604A

  • Resource clearing method and device, computer equipment and storage medium

    CN110232565A