Interbank transaction account checking connection method and device based on new and old system switching

Abstract

The invention provides an inter-bank transaction account checking connection method and device based on new and old system switching. The method comprises the steps of determining a starting time point of T-day data migration of a new system and an old system, performing account checking processing by adopting the old system according to old account checking elements at a first preset time point before the starting time point, migrating to-be-migrated data of the old system to the new system under the condition that the starting time is reached, and monitoring the data migration progress, wherein in the data migration process of the old system and the new system, the old system is adopted to process services; and when it is detected that data migration is completed, taking the current time point as a migration completion time point, switching the old system into a new system to process the service, and at a second preset time point, adopting the new system to perform account checking processing on the migration time period and the service data generated in the (T-1) day according to the new account checking element. The problem that the accuracy of data reconciliation is low during the existing new and old system switching period is solved.

Description

Technical Field

[0001] This application relates to the technical field of interbank transaction reconciliation during the transition between old and new systems. Specifically, it relates to a method, apparatus, computer-readable storage medium, and electronic device for interbank transaction reconciliation during the transition between old and new systems. Background Technology

[0002] In the process of digital transformation in the financial industry, upgrading and replacing core banking systems has become an inevitable process. This process involves data migration and business processing integration between the old and new systems, especially when handling interbank transaction reconciliation, which presents numerous challenges. During traditional banking system switching, reconciliation processing is typically limited to internal transactions. However, for interbank transactions, especially those involving third-party clearing channels (such as UnionPay and China Unicom), existing technologies have the following shortcomings:

[0003] 1. Inconsistent Reconciliation Elements: The old and new systems differ in key elements of transaction reconciliation. For example, the old system may rely on specific fields (such as the receiving organization identifier, sending organization identifier, system tracking number, etc.) for reconciliation, while the new system may introduce entirely new reconciliation elements, such as the global business tracking number. This difference is particularly pronounced during system transitions, making reconciliation between the old and new systems incompatible and increasing the complexity of the reconciliation process.

[0004] 2. Interbank Transaction Continuity Risk: During system switchover, interbank transactions may be processed across the old and new systems. Since the daily switchover times (i.e., the time when business dates change) of different systems and third-party clearing channels are usually inconsistent, interbank transactions within the switchover window are difficult to accurately track and reconcile, thus increasing the risk of transaction omissions and errors.

[0005] 3. Significant challenges in cross-institutional coordination: During bank system upgrades, third-party clearing channels often cannot cooperate with banks to make specific system changes or adjustments. This means that during system switching, banks must independently handle the complexities of reconciliation with third-party channels, and cannot rely on the coordination and support of external institutions.

[0006] 4. Data Migration and Business Processing Conflicts: During the system switchover transition period—from the start of data migration to the point where the new system fully takes over business operations—balancing the needs of data migration with the continued business processing requirements of the old system is a challenge. Improper handling may lead to gaps in business data before and after the migration, affecting the consistency and completeness of reconciliation.

[0007] In summary, existing interbank transaction reconciliation solutions lack effective methods to ensure the compatibility of reconciliation elements, transaction continuity, and cross-institutional collaborative capabilities during the upgrading and replacement of core banking systems. This not only limits the efficiency of banking system upgrades but also brings potential financial risks and a loss of customer trust. Summary of the Invention

[0008] The main objective of this application is to provide a method, apparatus, computer-readable storage medium, and electronic device for connecting interbank transaction reconciliation based on the switching between old and new systems, so as to at least solve the problem of low data reconciliation accuracy during the current system switching period.

[0009] To achieve the above objectives, according to one aspect of this application, a method for connecting interbank transaction reconciliation based on the switching between old and new systems is provided, comprising: determining the start time point of data migration between the new system and the old system on day T; at a first preset time point before the start time point, using the old system to perform reconciliation processing according to old reconciliation elements; upon reaching the start time point, migrating the data to be migrated from the old system to the new system, and monitoring the data migration progress, wherein, during the data migration process between the old system and the new system, the old system is used to process business; upon detecting that the data migration is complete, taking the current time point as the migration completion time point, switching the old system to the new system to process business, and at a second preset time point, using the new system to perform reconciliation processing on the business data generated within the migration period and day T-1 according to new reconciliation elements, wherein the migration period is the time period during which the old system processes business during the data migration process, the new reconciliation elements are determined based on the old reconciliation elements, and the second preset time point is a time point after the migration completion time point.

[0010] Optionally, after using the old system to perform reconciliation processing based on the old reconciliation elements, the method further includes: determining the new reconciliation elements corresponding to the business that occurred in the old system within T-1 days and during the migration period, based on preset data migration rules and the old reconciliation elements, wherein the new reconciliation elements include a global business tracking number and an original global business tracking number field, and the old reconciliation elements include an accepting organization identifier code, a sending organization identifier code, a system tracking number, a transaction transmission time, a message type, and a card number.

[0011] Optionally, the new system is used to reconcile business data during the migration period based on new reconciliation elements, including: obtaining the business data during the migration period, wherein the business data includes first transaction data from the daytime online transactions of the new system and second transaction data from the UnionPay channel side; and using the global business tracking number as the new reconciliation element to match and reconcile the first transaction data and the second transaction data.

[0012] Optionally, after performing matching and reconciliation processing on the first transaction data and the second transaction data, the method further includes: if the global business tracking number of the first transaction data matches the global business tracking number of the second transaction data, determining that the reconciliation of the first transaction data and the second transaction data is successful, and updating the reconciliation status of the first transaction data and the second transaction data to the reconciled status respectively; if the global business tracking number of the first transaction data does not match the global business tracking number of the second transaction data, determining that the reconciliation of the first transaction data and the second transaction data fails, and storing the first transaction data and the second transaction data in the error register.

[0013] Optionally, after obtaining the business data for the migration period, the method further includes: storing the first transaction data into a core-side detail table and a core-side temporary detail table, and storing the second transaction data into a UnionPay channel detail table and a UnionPay channel temporary table; and storing the transaction data in the core-side detail table, the core-side temporary detail table, the UnionPay channel detail table, and the UnionPay channel temporary table in segments.

[0014] Optionally, after storing the first transaction data and the second transaction data in the error register, the method further includes: performing failure analysis processing on the first transaction data and the second transaction data in the error register that represent reconciliation failure, and obtaining failure analysis results; and performing adjustment processing on the first transaction data and the second transaction data according to the failure analysis results.

[0015] Optionally, determining the starting time point for data migration between the new system and the old system includes: obtaining the daily switching time points of the old system, the new system, and the UnionPay card system respectively, and determining the starting time point for data migration between the new system and the old system based on the daily switching time points of the old system, the new system, and the UnionPay card system, wherein the daily switching time point represents the time point of the operation of switching business dates at a fixed time every day.

[0016] According to another aspect of this application, a connection device for interbank transaction reconciliation based on the switching between old and new systems is provided, comprising: a first processing unit, configured to determine the start time point of data migration between the new system and the old system on day T; at a first preset time point before the start time point, using the old system to perform reconciliation processing according to the old reconciliation elements; and, upon reaching the start time point, migrating the data to be migrated from the old system to the new system, and monitoring the data migration progress, wherein, during the data migration process between the old system and the new system, the old system is used to process business; and a second processing unit, configured to, upon detecting that the data migration is complete, use the current time point as the migration completion time point, switch the old system to the new system to process business, and at a second preset time point, use the new system to perform reconciliation processing on the business data generated within the migration period and day T-1 according to the new reconciliation elements, wherein the migration period is the time period during which the old system processes business during the data migration process, the new reconciliation elements are determined based on the old reconciliation elements, and the second preset time point is a time point after the migration completion time point.

[0017] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to execute any of the aforementioned methods for connecting interbank transaction reconciliation based on the switching between old and new systems.

[0018] According to another aspect of this application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including methods for performing any of the described methods for reconciling interbank transactions based on a switchover between old and new systems.

[0019] By applying the technical solution of this application, the starting time point for data migration between the new system and the old system on day T is determined. At a first preset time point before the starting time point, the old system performs reconciliation processing based on the old reconciliation elements. Upon reaching the starting time, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process, the old system handles business operations. Upon detection of data migration completion, the current time point is taken as the migration completion time point, and the old system is switched to the new system for business operations. At a second preset time point, the new system performs reconciliation processing based on the new reconciliation elements for the migration period and the business data generated within day T-1. The migration period is the time period during which the old system handles business operations during the data migration process, the new reconciliation elements are determined based on the old reconciliation elements, and the second preset time point is the time point after the migration completion time point. By setting and monitoring the starting time point for data migration on day T during the switchover process, it is ensured that the old system can complete reconciliation processing based on its original reconciliation elements before the first preset time point, thereby avoiding data processing interruptions due to incompatibility of reconciliation elements during the system switchover. Once the data migration is complete, the current time is used as the completion time. The new system is immediately activated to process business transactions. Simultaneously, at a second pre-set time, the new system is used to reconcile business data generated during the migration period with data generated within T-1 days. The new reconciliation elements cover the old reconciliation elements and add key fields required for reconciliation, such as the global business tracking number, achieving a seamless transition between the old and new reconciliation elements. This method avoids the risk of interruption in cross-bank transaction reconciliation continuity, ensures the integrity and automation of the reconciliation process during system switchover, and significantly improves reconciliation efficiency and accuracy. It also solves the problem of low data reconciliation accuracy during existing system switchovers. Attached Figure Description

[0020] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0021] Figure 1 A hardware structure block diagram of a mobile terminal for performing a connection method for interbank transaction reconciliation based on the switching between old and new systems, according to an embodiment of this application, is shown.

[0022] Figure 2 A flowchart illustrating a method for reconciling interbank transactions based on a switch between old and new systems, according to an embodiment of this application, is shown.

[0023] Figure 3 A flowchart illustrating a specific method for connecting interbank transaction reconciliation based on the switching between old and new systems, according to an embodiment of this application, is shown.

[0024] Figure 4 A flowchart illustrating a novel interbank transaction reconciliation scheme provided according to an embodiment of this application is shown.

[0025] Figure 5 A structural block diagram of a connection device for interbank transaction reconciliation based on the switching between old and new systems, according to an embodiment of this application, is shown. Detailed Implementation

[0026] 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.

[0027] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0029] For ease of description, the following explains some of the nouns or terms used in the embodiments of this application:

[0030] Global Business Tracking Number: A unique identifier defined within the banking system that tracks the entire lifecycle of interbank transactions.

[0031] Date switching: The operation of switching business dates at a fixed time each day in banking systems, card organizations, etc.

[0032] As described in the background section, the data continuity and reconciliation accuracy are low during the transition between old and new systems. To address the problem of low data reconciliation accuracy during the transition between old and new systems, embodiments of this application provide a method, apparatus, computer-readable storage medium, and electronic device for connecting interbank transaction reconciliation based on the transition between old and new systems.

[0033] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0034] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of a mobile terminal for a method of connecting interbank transaction reconciliation based on the switching between old and new systems, according to an embodiment of the present invention. Figure 1 As shown, a mobile 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. The mobile 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 mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0035] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the method for connecting interbank transaction reconciliation based on the switching between old and new systems 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 the mobile terminal via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the aforementioned networks may include wireless networks provided by the mobile terminal's communication provider. In one instance, the transmission device 106 includes a Network Interface Controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0036] This embodiment provides a method for connecting interbank transaction reconciliation based on the switching between old and new systems, which runs on a mobile terminal, computer terminal or similar computing device. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Also, although the logical order is shown in the flowchart, in some cases the steps shown or described can be executed in a different order than that shown here.

[0037] Figure 2 This is a flowchart illustrating the method for reconciling interbank transactions based on the switching between old and new systems, according to an embodiment of this application. For example... Figure 2 As shown, the method includes the following steps:

[0038] Step S201: Determine the start time of the data migration between the new system and the old system on day T. At a first preset time point before the start time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the start time is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business.

[0039] Specifically, at the first preset time point before the aforementioned start time, the old system is used to reconcile the transactions of day T-2 based on the old reconciliation elements. For example, taking the UnionPay channel as an example, the old system's daily cutoff time is 21:30, the new system's daily cutoff time is 22:30, and the UnionPay channel's daily cutoff time is always 23:00. The start time for data migration between the new and old systems is determined to be 0:00 on day T. At 6:00 on day T-1, the old system uses the old reconciliation elements to reconcile the transactions of day T-2. The reconciliation scope is: within the bank, from 21:30 on day T-3 to 21:30 on day T-2; and within the UnionPay side, from 23:00 on day T-3 to 23:00 on day T-2.

[0040] Step S202: Upon detecting that the data migration is complete, the current time point is taken as the migration completion time point. The old system is switched to the new system to process business. At the second preset time point, the new system is used to reconcile the business data generated within the migration period and T-1 day according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process. The new reconciliation elements are determined based on the old reconciliation elements. The second preset time point is the time point after the migration completion time point.

[0041] The old reconciliation elements of the old system include: the receiving organization identification code, the sending organization identification code, the system tracking number, the transaction transmission time, the message type, and the card number. The new reconciliation elements include the global business tracking number and the original global business tracking number field. According to the preset data migration rules, the old reconciliation elements are mapped to the global business tracking number and the original global business tracking number field in the new reconciliation elements.

[0042] Specifically, data migration is completed at 8:00 AM on day T. The new system is then activated at 8:00 AM on day T. Before the new system is activated, at 6:00 AM on day T, the old system uses the old reconciliation elements to reconcile the accounts of day T-1. The reconciliation scope is from 9:30 PM on day T-2 to 6:00 PM on day T-1 on the intra-bank side, and from 11:00 PM on day T-2 to 11:00 PM on the UnionPay side. At this point, the old core system can completely reconcile errors before 11:00 PM on day T-2. At 8:00 AM on day T, the new system uses the global business tracking number as the reconciliation element to reconcile the accounts of day T-1. The reconciliation scope is from 9:30 PM on day T-2 to 6:00 PM on day T-1 on the intra-bank side, and from 11:00 PM on day T-2 to 11:00 PM on the UnionPay side.

[0043] In addition, after 23:00 on T-1 day, UnionPay card organizations send the T-1 day reconciliation file to the UnionPay front-end system. The UnionPay front-end system sends the reconciliation file to the old system according to the old system file format, and at the same time sends it to the new system according to the new system file format. For the global business tracking number in the new system file, the original global business tracking number is spliced ​​together using the transaction elements of the old system according to the data migration rules.

[0044] In this embodiment, by applying steps S201 and S202 above, and by setting and monitoring the start time of data migration during the switchover process, it is ensured that the old system can complete reconciliation processing based on its original reconciliation elements before the first preset time point, thereby avoiding data processing interruptions caused by incompatibility of reconciliation elements during the system switchover. When the data migration is complete, the current time point is used as the migration completion time point, and the new system is immediately activated to process business. Simultaneously, at the second preset time point, the new system is used to reconcile business data within the migration period and within T-1 days. The new reconciliation elements cover the old reconciliation elements and add key fields required for reconciliation, such as the global business tracking number, achieving seamless integration of the old and new reconciliation elements. This method avoids the risk of interruption in cross-bank transaction reconciliation continuity, ensures the integrity and automation of the reconciliation process during the system switchover, and significantly improves reconciliation efficiency and accuracy. It solves the problem of low data reconciliation accuracy during the existing switchover process between old and new systems.

[0045] In the specific implementation process, after the old system is used to perform reconciliation processing based on the old reconciliation elements, the above method also includes: determining the above new reconciliation elements corresponding to the business that occurred in the above old system within the migration period within T-1 days according to the preset data migration rules and the above old reconciliation elements. The above new reconciliation elements include the global business tracking number and the original global business tracking number fields. The old reconciliation elements include the accepting organization identification code, the sending organization identification code, the system tracking number, the transaction transmission time, the message type, and the card number.

[0046] Among them, the preset data migration rule is a pre-set rule that uses old reconciliation elements to splice together new reconciliation elements.

[0047] This method, once the new system starts running and takes over the reconciliation tasks, introduces a mechanism for generating and applying new reconciliation elements to ensure that transactions occurring in the old system between T-1 and the completion of the system migration can be accurately identified and reconciled by the new system. Specifically, based on preset data migration rules and old reconciliation elements, the global business tracking number and the original global business tracking number fields corresponding to transactions occurring in the old system within the aforementioned migration period on T-1 day are determined. This process achieves seamless integration of reconciliation elements between the old and new systems, ensuring that even during the sensitive period of system switching, cross-bank transactions can be correctly identified by the new system and included in the reconciliation process. This approach not only solves the problem of incompatibility of reconciliation elements but also effectively guarantees the continuity of reconciliation and data integrity, avoiding data omissions or errors caused by the switch, and improving the transaction processing capacity and reconciliation efficiency during the bank's system switchover.

[0048] Specifically, the new system is used to reconcile business data during the migration period based on the new reconciliation elements. This includes: obtaining the business data during the migration period, wherein the business data includes the first transaction data from the daytime online transactions of the new system and the second transaction data from the UnionPay channel; and using the global business tracking number as the new reconciliation element to match and reconcile the first transaction data and the second transaction data.

[0049] This new system reconciles business data for the migration period based on new reconciliation elements. Specifically, it acquires business data within the migration period, encompassing both the first transaction data from the new system's daytime online transactions and the second transaction data from the UnionPay channel. The new system uses a global business tracking number as the core reconciliation element to match and reconcile the first and second transaction data. The core of this technical solution lies in dynamically generating and mapping global business tracking numbers, thus resolving the inconsistency in reconciliation elements between the old and new systems and ensuring the continuity and accuracy of transaction data reconciliation during the switchover period.

[0050] More specifically, after matching and reconciling the first transaction data and the second transaction data, the method further includes: if the global business tracking number of the first transaction data matches the global business tracking number of the second transaction data, determining that the reconciliation of the first transaction data and the second transaction data is successful, and updating the reconciliation status of the first transaction data and the second transaction data to the reconciled status respectively; if the global business tracking number of the first transaction data does not match the global business tracking number of the second transaction data, determining that the reconciliation of the first transaction data and the second transaction data fails, and storing the first transaction data and the second transaction data in the error register.

[0051] Specifically, the process of determining that the reconciliation of the first transaction data and the second transaction data has failed, and storing the first transaction data and the second transaction data in the error register when the global business tracking number of the first transaction data does not match, includes:

[0052] In the event of a failed match and the core (new system daytime online transactions) has transaction data but the channel (UnionPay channel side) has no transaction data: if the core transaction details reconciliation status is 'one-time reconciliation', update the reconciliation status to 'reconciliation failed'; if the core transaction details reconciliation status is 'not reconciled', update the core transaction details reconciliation status to 'one-time reconciliation', and simultaneously record it in the error register, recording the error flag as 'core has but channel does not', and the processing status as 'not processed'.

[0053] In the event of a failed match and the channel has transaction data but the core does not: if the channel details reconciliation status is 'one-time reconciliation', update the reconciliation status to 'reconciliation failed'; if the channel details reconciliation status is 'not reconciled', update the channel details reconciliation status to 'one-time reconciliation', and simultaneously record it in the error logbook, recording the error flag as 'channel has but core does not', and the processing status as 'unprocessed'.

[0054] This method automatically determines successful reconciliation when the global business tracking number of the first transaction data matches that of the second transaction data, and updates the reconciliation status of both transaction data to "reconciled," thereby ensuring the consistency and integrity of transaction records. Conversely, if the global business tracking numbers do not match, the reconciliation of the first and second transaction data is deemed unsuccessful. In this case, both transaction data will be stored in the error register to provide a basis for subsequent manual review and anomaly handling.

[0055] Furthermore, after obtaining the aforementioned business data for the aforementioned migration period, the method further includes: storing the aforementioned first transaction data into the core side detail table and the core side temporary detail table respectively, and storing the aforementioned second transaction data into the UnionPay channel detail table and the UnionPay channel temporary table respectively; and storing the transaction data in the aforementioned core side detail table, the aforementioned core side temporary detail table, the aforementioned UnionPay channel detail table, and the aforementioned UnionPay channel temporary table in segments.

[0056] This method first stores the initial transaction data involving both the old and new systems into the core-side detailed table and the core-side temporary detailed table, respectively. Simultaneously, it stores the second transaction data involving cross-bank transactions into the UnionPay channel detailed table and the UnionPay channel temporary table. This step ensures the integrity and security of all critical business data. Next, to improve subsequent reconciliation efficiency, the transaction data in the core-side detailed table, the core-side temporary detailed table, the UnionPay channel detailed table, and the UnionPay channel temporary table are stored in shards. This strategy not only fully utilizes storage resources but also significantly accelerates data retrieval and comparison speed. In practice, sharded storage allows for parallel processing of multiple datasets, thereby significantly shortening the reconciliation cycle and improving the accuracy and timeliness of reconciliation.

[0057] Furthermore, after storing the first transaction data and the second transaction data in the error register, the method further includes: performing failure analysis processing on the first transaction data and the second transaction data in the error register that indicate reconciliation failure, and obtaining failure analysis results; and performing adjustment processing on the first transaction data and the second transaction data based on the failure analysis results.

[0058] This method involves storing the first and second failed transaction data in an error logbook, followed by failure analysis to obtain detailed results. This process aims to deeply analyze the specific reasons for the reconciliation failure, providing precise guidance for subsequent adjustments. Based on the analysis results, the system executes targeted adjustments to correct discrepancies and ensure the accuracy and consistency of cross-bank transaction data. This method not only enhances the robustness of the reconciliation process but also improves error handling efficiency through automated failure analysis, reduces labor costs, and ensures smooth transaction reconciliation during the transition between old and new systems.

[0059] Specifically, determining the starting time point for data migration between the new system and the old system includes: obtaining the daily cut-off time points of the old system, the new system, and the UnionPay card system respectively; determining the starting time point for data migration between the new system and the old system based on the daily cut-off time points of the old system, the new system, and the UnionPay card system; wherein the daily cut-off time point represents the time point of the operation of switching business dates at a fixed time each day.

[0060] This method determines the start time of the data migration between the new and old systems on day T. This includes obtaining the daily cut-off times for the old, new, and UnionPay card systems, and then determining the start time of the data migration based on these daily cut-off times. This process fully considers the differences in processing time among the systems, ensuring that interbank transaction information can be accurately transferred between the old and new systems and the UnionPay card system during the data migration process. This avoids potential transaction omissions or duplications due to inconsistent daily cut-off times. By accurately matching the daily cut-off times, this embodiment achieves seamless connection and data integrity for interbank transaction reconciliation during system switching, guaranteeing the continuity and security of financial services during the bank system upgrade.

[0061] To enable those skilled in the art to better understand the technical solution of this application, the implementation process of the method for connecting interbank transaction reconciliation based on the switching between old and new systems will be described in detail below with reference to specific embodiments.

[0062] The existing banking system faces the following problems during the transition from the old to the new system:

[0063] (1) Incompatibility of reconciliation elements between the old and new systems: For example, the old system relies on fixed fields for reconciliation, while the new system uses internally unified serial numbers for reconciliation, making it difficult to process transactions in a compatible manner during the switchover period.

[0064] (2) Risk of interbank transaction continuity: When switching systems, interbank transactions may be scattered in the old and new systems, making it difficult to ensure the continuity of reconciliation and easily causing errors and omissions.

[0065] (3) Difficulty in cross-institutional collaboration: Cross-bank clearing channels are usually various card organizations, which cannot cooperate with the bank system to switch to special processing.

[0066] This embodiment relates to a specific method for connecting interbank transaction reconciliation during the switchover between old and new systems. It is compatible with the inconsistencies in reconciliation elements between the old and new systems, ensures reconciliation continuity, and adheres to the principle of minimal modification. Specifically, it includes the following:

[0067] 1. Background of the Solution (taking UnionPay channel as an example):

[0068] (1) The reconciliation elements of the old system are the receiving institution identification code, the sending institution identification code, the system tracking number, the transaction transmission time, the message type, and the card number; the reconciliation elements of the new system are the transaction serial number (global business tracking number) that is universally used within the bank.

[0069] (2) The new system requires UnionPay-side reconciliation files with the addition of the Global Business Tracking Number and the original Global Business Tracking Number fields compared to the old system.

[0070] (3) The daily switching time for the old system is 21:30, the daily switching time for the new system is 22:30, and the daily switching time for the UnionPay channel is always 23:00.

[0071] (4) Switching between old and new systems: The old system will switch to the new system at 18:00 on T-1 day. At 0:00 on T day, the old system data will be migrated to the new system. The new system will be put into use at 8:00 on T day. The old system will provide services to the public from 0:00 to 8:00 on T day.

[0072] 2. Switching scheme as follows Figure 3 As shown, it specifically includes the following:

[0073] (1) At 6:00 on T-1, the old system uses the old reconciliation elements to reconcile the accounts on T-2. The reconciliation range is from 21:30 on T-3 to 21:30 on T-2 on the intra-bank side, and from 23:00 on T-3 to 23:00 on T-2 on the UnionPay side.

[0074] (2) After 23:00 on T-1 day, UnionPay card organization sends the reconciliation file of T-1 day to UnionPay front-end system. UnionPay front-end system sends the reconciliation file to the old system according to the old system file format, and sends it to the new system according to the new system file format. The global business tracking number and the original global business tracking number in the new system file are spliced ​​together using the transaction elements of the old system according to the data migration rules.

[0075] (3) At 6:00 on day T, the old system uses the old reconciliation elements to reconcile the accounts of day T-1. The reconciliation range is from 21:30 on day T-2 to 18:00 on day T-1 on the internal side, and from 23:00 on day T-2 to 23:00 on day T-1 on the UnionPay side. At this point, the old core system can completely reconcile the errors before 23:00 on day T-2.

[0076] (4) From 0:00 to 8:00 on day T, data from the old system is migrated to the new system;

[0077] (5) At 8:00 on day T, the new system uses the global business tracking number as the reconciliation element to reconcile the accounts of day T-1. The reconciliation scope is from 21:30 on day T-2 to 18:00 on day T-1 on the bank side, and from 23:00 on day T-2 to 23:00 on day T-1 on the UnionPay side.

[0078] (6) After 23:00 on day T, UnionPay Card Organization sends the reconciliation file of day T to UnionPay Front-end System. UnionPay Front-end System will send it to the new system according to the new system file format. For transactions that occurred in the old system, the global business tracking number and the original global business tracking number are spliced ​​together using the transaction elements of the old system according to the data migration rules. For transactions that occurred in the new system, the global business tracking number is matched with the global business tracking number field in the online transactions sent to the new system during the day.

[0079] (7) At 8:00 on T+1 day, the new system uses the global business tracking number as the reconciliation element to reconcile the accounts on T day. The reconciliation range is from 18:00 on T-1 day to 22:30 on T day on the bank side, and from 23:00 on T-1 day to 23:00 on T day on the UnionPay side. Thus, the new system can completely reconcile the errors after 23:00 on T-2 day.

[0080] 3. The new system's interbank transaction reconciliation solution is as follows: Figure 4 As shown, it specifically includes the following:

[0081] 1) The data sources for reconciliation are as follows: the daily online transaction records of the new system are stored in the core side detailed table and the core side temporary detailed table; the reconciliation files of the UnionPay channel side are stored in the UnionPay channel detailed table and the temporary table; both the core side and the channel side data are stored in segments. On each segment, the data from both sides are used for reconciliation. After the reconciliation is completed, the reconciliation difference results of each segment are stored in the error register, and all segments are summarized and processed.

[0082] 2) The reconciliation rules for each transaction between the UnionPay channel side and the core side are as follows:

[0083] (1) Use the global business tracking number as the reconciliation element, and match and reconcile the temporary transaction details of UnionPay channel and the temporary core transaction details respectively.

[0084] (2) If there are matching transaction details on both sides, the reconciliation is considered successful. Update the reconciliation status of the matched core transaction details and UnionPay channel transaction details to 'Reconciled'. If the reconciliation status of the core transaction details is updated from 'One-time Reconciliation' to 'Reconciled' or the reconciliation status of the channel transaction details is updated from 'One-time Reconciliation' to 'Reconciled', then retrieve the detailed record information according to the reconciliation elements and check the error register record. If the record processing status is 'Unprocessed', update it to 'Automatically Processed'.

[0085] (3) Records that cannot be matched and are available in the core but not in the channel: If the core details reconciliation status is 'one-time reconciliation', update the reconciliation status to 'reconciliation failed'; if the core reconciliation status is 'not reconciled', update the core transaction details reconciliation status to 'one-time reconciliation', and at the same time record it in the error register, record the error mark as 'available in the core but not in the channel', and the processing status as 'not processed'.

[0086] (4) Records that cannot be matched and have a core but no matching channel: If the channel details reconciliation status is 'one reconciliation', update the reconciliation status to 'reconciliation failed'; if the channel details reconciliation status is 'not reconciled', update the channel details reconciliation status to 'one reconciliation', and at the same time record it in the error register, record the error mark as 'channel has core but no matching channel', and the processing status as 'not processed'.

[0087] (5) For the generated error register, the error handling operator selects the transactions that need adjustment based on the reconciliation results and initiates the adjustment.

[0088] This embodiment achieves the following technical effects:

[0089] 1. Dynamic generation and mapping technology for global business tracking numbers: By parsing the key fields of interbank clearing documents and matching historical tracking numbers with the online transaction database or generating new numbers according to migration rules, seamless compatibility of reconciliation elements between the old and new systems can be achieved.

[0090] 2. Phased Switching Strategy: Based on the difference between the daily switching time of the channel and the daily switching time of the bank's core system, the new system will be connected to the T-1 day reconciliation in advance, and the reconciliation file distribution strategy will be dynamically adjusted to ensure the continuity of reconciliation between the old and new systems.

[0091] 3. Segmented reconciliation and error handling process: Transaction data from the core side and the channel side are stored in segments, and reconciliation is performed on a transaction-by-transaction basis according to the segment. Differences are recorded through an error register, supporting automatic marking and manual intervention in collaborative processing.

[0092] This application also provides a connection device for interbank transaction reconciliation based on the switch between old and new systems. It should be noted that this connection device can be used to execute the connection method for interbank transaction reconciliation based on the switch between old and new systems provided in this application. This device is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0093] The following describes the connection device for cross-bank transaction reconciliation based on the switching between old and new systems provided in the embodiments of this application.

[0094] Figure 5 This is a schematic diagram of a connection device for interbank transaction reconciliation based on the switching between old and new systems, according to an embodiment of this application. Figure 5 As shown, the device includes:

[0095] The first processing unit 51 is used to determine the start time point of the data migration between the new system and the old system on day T. At a first preset time point before the start time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the start time point is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business.

[0096] The second processing unit 52 is used to switch the old system to the new system to process business when the data migration is detected to be completed, taking the current time as the migration completion time. At a second preset time, the new system is used to reconcile the business data generated within the migration period and T-1 day according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process. The new reconciliation elements are determined based on the old reconciliation elements. The second preset time is a time point after the migration completion time.

[0097] In this embodiment, the first processing unit is used to determine the start time of the data migration between the new system and the old system on day T. Before the start time, the old system performs reconciliation processing based on the old reconciliation elements at a first preset time point. When the start time is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business. The second processing unit is used to switch the old system to the new system to process business when the data migration is detected to be complete, taking the current time point as the migration completion time point. At the second preset time point, the new system performs reconciliation processing on the business data generated within the migration period and day T-1 based on the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process, the new reconciliation elements are determined based on the old reconciliation elements, and the second preset time point is the time point after the migration completion time point. During the system switchover, by setting and monitoring the start time of data migration, it was ensured that the old system could complete reconciliation processing based on its original reconciliation elements before the first preset time point, thus avoiding data processing interruptions caused by incompatibility of reconciliation elements during the system switchover. Once the data migration was complete, the current time point was used as the migration completion time point, and the new system was immediately activated to process business. Simultaneously, at the second preset time point, the new system was used to reconcile business data generated within the migration period and T-1 day. The new reconciliation elements covered the old reconciliation elements and added key fields required for reconciliation, such as the global business tracking number, achieving seamless integration of the old and new reconciliation elements. This solution avoided the risk of interruption in cross-bank transaction reconciliation continuity, ensured the integrity and automation of the reconciliation process during the system switchover, and significantly improved reconciliation efficiency and accuracy. It solved the problem of low data reconciliation accuracy during the existing system switchover.

[0098] As an optional solution, the device also includes a determining unit, used to determine, after reconciliation processing is performed using the old system based on the old reconciliation elements, the new reconciliation elements corresponding to the business that occurred in the old system within the migration period of T-1 day according to preset data migration rules and the old reconciliation elements. The new reconciliation elements include a global business tracking number and an original global business tracking number field. The old reconciliation elements include an accepting organization identifier code, a sending organization identifier code, a system tracking number, a transaction transmission time, a message type, and a card number.

[0099] In one optional embodiment, the second processing unit includes an acquisition module and a reconciliation processing module. The acquisition module is used to acquire the business data for the migration period, wherein the business data includes the first transaction data of the new system's daytime online transactions and the second transaction data from the UnionPay channel. The reconciliation processing module is used to use the global business tracking number as the new reconciliation element to match and reconcile the first transaction data and the second transaction data.

[0100] In one optional embodiment, the second processing unit further includes a first determining module and a second determining module. The first determining module is used to determine that the reconciliation of the first transaction data and the second transaction data is successful if the global business tracking number of the first transaction data matches the global business tracking number of the second transaction data, and to update the reconciliation status of the first transaction data and the second transaction data to a reconciled status. The second determining module is used to determine that the reconciliation of the first transaction data and the second transaction data fails if the global business tracking number of the first transaction data does not match the global business tracking number of the second transaction data, and to store the first transaction data and the second transaction data in an error register.

[0101] In one optional embodiment, the second processing unit further includes an input module and a storage module; the input module is used to, after obtaining the business data for the migration period, store the first transaction data into the core-side detail table and the core-side temporary detail table, and store the second transaction data into the UnionPay channel detail table and the UnionPay channel temporary table, respectively; the storage module is used to perform segmented storage of the transaction data in the core-side detail table, the core-side temporary detail table, the UnionPay channel detail table, and the UnionPay channel temporary table.

[0102] In one optional embodiment, the second processing unit further includes an analysis processing module and an adjustment processing module; the analysis processing module is used to perform failure analysis processing on the first transaction data and the second transaction data in the error register that indicate reconciliation failure after storing the first transaction data and the second transaction data in the error register, and obtain failure analysis results; the adjustment processing module is used to perform adjustment processing on the first transaction data and the second transaction data according to the failure analysis results.

[0103] In one optional scheme, the first processing unit includes a third determining module, which is used to obtain the daily switching time points of the old system, the new system, and the UnionPay card system respectively, and determine the starting time point of the data migration between the new system and the old system based on the daily switching time points of the old system, the new system, and the UnionPay card system, wherein the daily switching time point represents the time point of the operation of switching the business date at a fixed time every day.

[0104] The aforementioned interbank transaction reconciliation connection device based on the switch between old and new systems includes a processor and a memory. All the aforementioned units are stored as program units in the memory, and the processor executes these program units to achieve the corresponding functions. All the aforementioned modules reside in the same processor; alternatively, the modules may be located in different processors in any combination.

[0105] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and adjusting kernel parameters can address the issue of low data reconciliation accuracy during system transitions.

[0106] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0107] This invention provides a computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the aforementioned method for connecting interbank transaction reconciliation based on the switching between old and new systems.

[0108] Specifically, the methods for reconciling interbank transactions during the switch between the old and new systems include:

[0109] Step S201: Determine the starting time point for data migration between the new system and the old system. At a first preset time point before the starting time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the starting time point is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business.

[0110] Step S202: Upon detecting that the data migration is complete, the current time point is taken as the migration completion time point. The old system is switched to the new system to process business. At the second preset time point, the new system is used to reconcile the business data of the migration period according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process. The new reconciliation elements include newly added reconciliation elements and the old reconciliation elements. The second preset time point is the time point after the migration completion time point.

[0111] This invention provides a processor for running a program, wherein the program executes the aforementioned method for connecting interbank transaction reconciliation based on the switching between old and new systems.

[0112] Specifically, the methods for reconciling interbank transactions during the switch between the old and new systems include:

[0113] Step S201: Determine the start time of the data migration between the new system and the old system on day T. At a first preset time point before the start time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the start time is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business.

[0114] Step S202: Upon detecting that the data migration is complete, the current time point is taken as the migration completion time point. The old system is switched to the new system to process business. At the second preset time point, the new system is used to reconcile the business data generated within the migration period and T-1 day according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process. The new reconciliation elements are determined based on the old reconciliation elements. The second preset time point is the time point after the migration completion time point.

[0115] This invention provides an electronic device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs at least the following steps:

[0116] Step S201: Determine the start time of the data migration between the new system and the old system on day T. At a first preset time point before the start time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the start time is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business.

[0117] Step S202: Upon detecting that the data migration is complete, the current time point is taken as the migration completion time point. The old system is switched to the new system to process business. At the second preset time point, the new system is used to reconcile the business data generated within the migration period and T-1 day according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process. The new reconciliation elements are determined based on the old reconciliation elements. The second preset time point is the time point after the migration completion time point.

[0118] The devices mentioned in this article can be servers, PCs, tablets, mobile phones, etc.

[0119] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having at least the following method steps:

[0120] Step S201: Determine the start time of the data migration between the new system and the old system on day T. At a first preset time point before the start time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the start time is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business.

[0121] Step S202: Upon detecting that the data migration is complete, the current time point is taken as the migration completion time point. The old system is switched to the new system to process business. At the second preset time point, the new system is used to reconcile the business data generated within the migration period and T-1 day according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process. The new reconciliation elements are determined based on the old reconciliation elements. The second preset time point is the time point after the migration completion time point.

[0122] 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. They can be implemented using computer-executable program code, and thus can be stored 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 described 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.

[0123] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0124] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. 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... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0125] 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 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0126] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0127] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0128] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0129] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0130] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0131] 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.

[0132] The above description is merely a preferred embodiment of this application and is not intended to limit 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 protection scope of this application.

Claims

1. A method for connecting interbank transaction reconciliation during the switchover between old and new systems, characterized in that, include: The starting time point for the data migration between the new system and the old system on day T is determined. At a first preset time point before the starting time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the starting time point is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business. Upon detection that data migration is complete, the current time point is taken as the migration completion time point. The old system is switched to the new system to process business. At a second preset time point, the new system is used to reconcile the business data generated within the migration period and within T-1 days according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process. The new reconciliation elements are determined based on the old reconciliation elements. The second preset time point is a time point after the migration completion time point.

2. The method according to claim 1, characterized in that, After reconciling accounts using the old system based on the old reconciliation elements, the method further includes: Based on the preset data migration rules and the old reconciliation elements, the new reconciliation elements corresponding to the business that occurred in the old system within the migration period on day T-1 are determined. The new reconciliation elements include the global business tracking number and the original global business tracking number fields. The old reconciliation elements include the accepting organization identification code, the sending organization identification code, the system tracking number, the transaction transmission time, the message type, and the card number.

3. The method according to claim 1, characterized in that, The new system is used to reconcile business data for the migration period based on the new reconciliation elements, including: Obtain the business data for the migration period, wherein the business data includes the first transaction data of the daytime online transactions of the new system and the second transaction data of the UnionPay channel side; Using the global business tracking number as the new reconciliation element, the first transaction data and the second transaction data are matched and reconciled.

4. The method according to claim 3, characterized in that, After matching and reconciling the first transaction data with the second transaction data, the method further includes: If the global business tracking number of the first transaction data matches the global business tracking number of the second transaction data, it is determined that the reconciliation of the first transaction data and the second transaction data is successful, and the reconciliation status of the first transaction data and the second transaction data is updated to the reconciled status respectively. If the global business tracking number of the first transaction data does not match the global business tracking number of the second transaction data, it is determined that the reconciliation between the first transaction data and the second transaction data has failed, and the first transaction data and the second transaction data are stored in the error register.

5. The method according to claim 3, characterized in that, After obtaining the business data for the migration time period, the method further includes: The first transaction data is stored in the core side detail table and the core side temporary detail table, respectively, and the second transaction data is stored in the UnionPay channel detail table and the UnionPay channel temporary table, respectively. The transaction data in the core side detail table, the core side temporary detail table, the UnionPay channel detail table, and the UnionPay channel temporary table are stored in segments.

6. The method according to claim 4, characterized in that, After storing the first transaction data and the second transaction data in the error register, the method further includes: The first and second transaction data in the error register that represent reconciliation failures are subjected to failure analysis processing to obtain failure analysis results. Based on the failure analysis results, the first transaction data and the second transaction data are adjusted.

7. The method according to claim 1, characterized in that, Determine the start time point of the data migration between the new system and the old system on day T, including: The daily switching time points of the old system, the new system, and the UnionPay card system are obtained respectively. Based on the daily switching time points of the old system, the new system, and the UnionPay card system, the starting time point of the T-day data migration between the new system and the old system is determined. The daily switching time point represents the time point of the operation of switching the business date at a fixed time every day.

8. A connection device for interbank transaction reconciliation based on the switching between old and new systems, characterized in that, include: The first processing unit is used to determine the start time point of the data migration between the new system and the old system on day T. Before the start time point, the old system is used to perform reconciliation processing based on the old reconciliation elements. When the start time is reached, the data to be migrated from the old system is migrated to the new system, and the data migration progress is monitored. During the data migration process between the old system and the new system, the old system is used to process business. The second processing unit is used to switch the old system to the new system to process business when the data migration is detected to be complete, taking the current time as the migration completion time. At a second preset time, the new system is used to reconcile the business data generated within the migration period and T-1 days according to the new reconciliation elements. The migration period is the time period during which the old system processes business during the data migration process, the new reconciliation elements are determined based on the old reconciliation elements, and the second preset time is a time point after the migration completion time.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the connection method for interbank transaction reconciliation based on the switching between old and new systems as described in any one of claims 1 to 7.

10. An electronic device, characterized in that, include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including a method for performing the reconciliation of interbank transactions based on a switchover between old and new systems as described in any one of claims 1 to 7.

Images