Transaction account reconciliation method, apparatus, electronic device, and storage medium

Abstract

The application discloses a transaction reconciliation method and device, an electronic device and a storage medium. The method comprises the following steps: in the process of executing a first transaction reconciliation task by using first transaction flow data in a transaction database, recording the first transaction flow data which has been written into a reconciliation file in a transaction reconciliation check file, and the transaction reconciliation check file is stored in a storage area which is independent of the transaction database; in the process of executing a second transaction reconciliation task by using second transaction flow data in the transaction database, determining target transaction flow data to be supplemented according to the second transaction flow data and the transaction reconciliation check file; executing a supplement reconciliation task on the target transaction flow data, and recording the target transaction flow data which has been written into a supplement reconciliation file into the transaction reconciliation check file. The technical scheme reduces the write operation on the transaction database, reduces the read-write pressure of the transaction database, and thus enables the transaction database to better provide technical support for real-time transaction services.

Description

Technical Field

[0001] This application relates to the field of online payment technology, and in particular to transaction reconciliation methods, devices, electronic devices, and storage media. Background Technology

[0002] Transaction reconciliation refers to the verification of accounts based on transaction flow data. In scenarios where an intermediary platform connects with multiple trading institutions, the transaction flow data of each trading institution is stored on the intermediary platform. The intermediary platform can then rely on the transaction database storing the transaction flow data to perform transaction reconciliation, thereby issuing transaction reconciliation statements to each trading institution.

[0003] During transaction reconciliation, it's difficult to completely avoid situations where incomplete transaction log data is used for reconciliation due to malfunctions. To address this, missing transaction log data can be identified and supplemented based on the reconciliation status, and the reconciliation status can be updated. However, since transaction log data is stored in the transaction database, the write operations performed on the transaction database during the supplementary reconciliation process increase the processing load on the transaction database, potentially affecting its ability to handle real-time transactions. Summary of the Invention

[0004] This application provides a transaction reconciliation method, apparatus, electronic device, and storage medium to mitigate the impact of transaction reconciliation on the transaction database.

[0005] The embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, embodiments of this application provide a transaction reconciliation method, executed by a transaction reconciliation server, comprising: during the execution of a first transaction reconciliation task using first transaction flow data in a transaction database, recording the first transaction flow data already written into a transaction reconciliation verification file, the transaction reconciliation verification file being stored in a storage area independent of the transaction database; during the execution of a second transaction reconciliation task using second transaction flow data in the transaction database, determining the target transaction flow data to be reconciled based on the second transaction flow data and the transaction reconciliation verification file; performing a supplementary reconciliation task on the target transaction flow data, and recording the target transaction flow data already written into the supplementary reconciliation file into the transaction reconciliation verification file.

[0007] In some embodiments, performing a first transaction reconciliation task using first transaction flow data in a transaction database and performing a supplementary reconciliation task using target transaction flow data includes: reading transaction information related to the corresponding first transaction reconciliation task or the corresponding supplementary reconciliation task from the first transaction flow data or target transaction flow data, wherein the transaction information includes at least one of the following: transaction flow identifier, transaction amount, transaction type, transaction status, transaction initiator, and transaction counterparty; and writing the read transaction information into a reconciliation file or a supplementary reconciliation file accordingly.

[0008] In some embodiments, recording the first transaction flow data that has been written into the reconciliation file in the transaction reconciliation verification file, and recording the target transaction flow data that has been written into the supplementary reconciliation file into the transaction reconciliation verification file, includes: generating a corresponding transaction reconciliation verification record for each transaction flow data that has been written into the reconciliation file or the supplementary reconciliation file in the transaction reconciliation verification file.

[0009] In some embodiments, the transaction reconciliation record includes a globally unique identifier for the transaction log data that has been written into the reconciliation file or supplementary reconciliation file.

[0010] In some embodiments, the globally unique identifier includes the transaction log identifier and the transaction initiator.

[0011] In some embodiments, determining the target transaction data to be reconciled based on the second transaction data and the transaction reconciliation file includes: for each second transaction data, querying the transaction reconciliation file based on the globally unique identifier of the second transaction data; if the query result is empty, then the second transaction data is determined to be the target transaction data to be reconciled.

[0012] In some embodiments, the transaction reconciliation method further includes: not recording first transaction flow data that was not written to the reconciliation file in the transaction reconciliation verification file, and not recording target transaction flow data that was not written to the supplementary reconciliation file in the transaction reconciliation verification file.

[0013] In some embodiments, the transaction reconciliation file has a unique correspondence with the transaction database, and different transaction databases correspond to different transaction reconciliation files.

[0014] Secondly, embodiments of this application also provide a transaction reconciliation device, applied in a transaction reconciliation server, for implementing any of the transaction reconciliation methods described above.

[0015] In some embodiments, the transaction reconciliation apparatus includes: a reconciliation unit, configured to record the first transaction flow data already written into a transaction reconciliation file in a transaction reconciliation verification file during the execution of a first transaction reconciliation task using first transaction flow data in a transaction database, the transaction reconciliation verification file being stored in a storage area independent of the transaction database; a determination unit, configured to determine the target transaction flow data to be reconciled based on the second transaction flow data and the transaction reconciliation verification file during the execution of a second transaction reconciliation task using second transaction flow data in a transaction database; and a supplementary reconciliation unit, configured to perform a supplementary reconciliation task on the target transaction flow data and record the target transaction flow data already written into the supplementary reconciliation file into the transaction reconciliation verification file.

[0016] In some embodiments, the reconciliation unit is used to read transaction information related to the corresponding first transaction reconciliation task or the corresponding supplementary reconciliation task from the first transaction flow data or the target transaction flow data. The transaction information includes at least one of the following: transaction flow identifier, transaction amount, transaction type, transaction status, transaction initiator, and transaction counterparty; and writes the read transaction information into the reconciliation file or the supplementary reconciliation file accordingly.

[0017] In some embodiments, the reconciliation unit is used to generate a corresponding transaction reconciliation record for each first transaction data that has been written into the reconciliation file in the transaction reconciliation verification file; the supplementary reconciliation unit is used to generate a corresponding transaction reconciliation record for each target transaction data that has been written into the supplementary reconciliation file in the transaction reconciliation verification file.

[0018] In some embodiments, the transaction reconciliation record includes a globally unique identifier for the transaction log data that has been written into the reconciliation file or supplementary reconciliation file.

[0019] In some embodiments, the globally unique identifier includes the transaction log identifier and the transaction initiator.

[0020] In some embodiments, the determining unit is configured to query the transaction reconciliation file for each second transaction data based on the globally unique identifier of the second transaction data; if the query result is empty, the second transaction data is determined to be the target transaction data to be reconciled.

[0021] In some embodiments, the reconciliation unit is further configured to not record the first transaction flow data that was not written to the reconciliation file in the transaction reconciliation verification file; the supplementary reconciliation unit is further configured to not record the target transaction flow data that was not written to the supplementary reconciliation file in the transaction reconciliation verification file.

[0022] In some embodiments, the transaction reconciliation file has a unique correspondence with the transaction database, and different transaction databases correspond to different transaction reconciliation files.

[0023] Thirdly, embodiments of this application also provide an electronic device, including: a processor; and a memory arranged to store computer-executable instructions, which, when executed, cause the processor to perform the transaction reconciliation method as described above.

[0024] Fourthly, embodiments of this application also provide a computer-readable storage medium storing one or more programs that, when executed by an electronic device including multiple applications, cause the electronic device to perform the transaction reconciliation method as described above.

[0025] The above-mentioned at least one technical solution adopted in the embodiments of this application can achieve the following beneficial effects: by using a transaction reconciliation verification file stored independently of the transaction database, the transaction flow data that has been written to the reconciliation file or the supplementary reconciliation file is recorded, which reduces the write operations to the transaction database during the execution of the transaction reconciliation task and the write operations to the transaction database during the execution of the supplementary reconciliation task, thereby reducing the read and write pressure on the transaction database and enabling the transaction database to better provide technical support for real-time transaction services. Attached Figure Description

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

[0027] Figure 1 This is a flowchart illustrating a transaction reconciliation method in an embodiment of this application;

[0028] Figure 2 This is a schematic diagram of the structure of a transaction reconciliation device according to an embodiment of this application;

[0029] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0031] The inventors discovered that while marking which transaction data has been used for reconciliation and reconciliation in the transaction database can help identify missing transaction data by querying the database, it requires adding write operations to the transaction database during both the reconciliation and reconciliation stages to mark transaction data used for reconciliation.

[0032] The technical concept of this application is to use a transaction reconciliation file to record the usage of transaction reconciliation data outside the transaction database. When supplementing the reconciliation, the transaction reconciliation file can be used to identify the missing transaction data, reducing write operations to the transaction database and enabling the transaction database to provide more comprehensive services for real-time transactions.

[0033] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0034] Figure 1 This is a flowchart illustrating a transaction reconciliation method according to an embodiment of this application. The transaction reconciliation method can be executed by a transaction reconciliation server and specifically includes:

[0035] In step S110, during the execution of the first transaction reconciliation task using the first transaction flow data in the transaction database, the first transaction flow data that has been written into the reconciliation file is recorded in the transaction reconciliation verification file, which is stored in a storage area independent of the transaction database.

[0036] In this step, the reconciliation logic for the first transaction reconciliation task can be implemented using existing technology, such as verifying whether a withdrawal transaction has a matching deposit transaction based on the transaction serial number. After reconciling using a single first transaction serial number, that first transaction serial number, or a portion thereof, can be written to the reconciliation file.

[0037] Unlike existing technologies, this application no longer directly records whether transaction flow data has been used for transaction reconciliation in the transaction database. Instead, it uses a transaction reconciliation verification file, which can be in any format required by the business, such as text or tables, and is not stored in the transaction database, thereby reducing write operations to the transaction database.

[0038] Step S120: During the second transaction reconciliation task performed using the second transaction flow data in the transaction database, the target transaction flow data to be reconciled is determined based on the second transaction flow data and the transaction reconciliation verification document.

[0039] Generally, the execution of the first transaction reconciliation task is atomic; that is, only after reading a first transaction record from the transaction database, executing the first transaction reconciliation task, and successfully writing it to the reconciliation file is the transaction record considered used for transaction reconciliation. During this process, transaction record data may be missed due to file write failures or data read failures. To find these missed transaction record data, we can first determine the second transaction record data, including one or more first transaction record data that should be used by the first transaction reconciliation task; then, based on the transaction reconciliation verification file, we determine the actual transaction record data used, and by comparison, we can identify the missed transaction record data.

[0040] Step S130: Perform a reconciliation task on the target transaction data and record the target transaction data already written to the reconciliation file into the transaction reconciliation verification file. The reconciliation logic of the reconciliation task can be the same as the reconciliation logic of the first transaction reconciliation task.

[0041] visible, Figure 1 The method shown utilizes a transaction reconciliation file stored independently of the transaction database to record transaction flow data that has been written to the reconciliation file or supplementary reconciliation file. This reduces write operations to the transaction database during both the execution of transaction reconciliation tasks and the execution of supplementary reconciliation tasks, alleviating the read and write pressure on the transaction database. As a result, the transaction database can better provide technical support for real-time transaction services.

[0042] In some embodiments, performing a first transaction reconciliation task using first transaction flow data in a transaction database and performing a supplementary reconciliation task using target transaction flow data includes: reading transaction information related to the corresponding first transaction reconciliation task or the corresponding supplementary reconciliation task from the first transaction flow data or target transaction flow data, wherein the transaction information includes at least one of the following: transaction flow identifier, transaction amount, transaction type, transaction status, transaction initiator, and transaction counterparty; and writing the read transaction information into a reconciliation file or a supplementary reconciliation file accordingly.

[0043] Depending on the task being performed, the system reads either the transaction information related to the first transaction reconciliation task from the first transaction log data, or the transaction information related to the supplementary reconciliation task from the target transaction log data. In addition to the transaction information listed above, the transaction log data may also record transaction time, transaction batch identifiers, etc. It's important to note that not all transaction information recorded in the transaction log data needs to participate in transaction reconciliation; therefore, only the transaction information related to the transaction reconciliation task needs to be read.

[0044] The transaction reconciliation file actually stores the details of these read transactions, which facilitates the subsequent generation of transaction reconciliation statements corresponding to each transaction institution, allowing the transaction institutions to perform subsequent operations such as verification based on the transaction reconciliation statements.

[0045] In some embodiments, recording the first transaction flow data that has been written into the reconciliation file in the transaction reconciliation verification file, and recording the target transaction flow data that has been written into the supplementary reconciliation file into the transaction reconciliation verification file, includes: generating a corresponding transaction reconciliation verification record for each transaction flow data that has been written into the reconciliation file or the supplementary reconciliation file in the transaction reconciliation verification file.

[0046] In other words, for each transaction record actually used, a corresponding transaction reconciliation record is generated in the transaction reconciliation file.

[0047] In existing technologies, a status field is typically added to the transaction log data to record whether the transaction log data has been used for transaction reconciliation. Since the technical solution of this application does not perform such processing in the transaction database, the challenge is how to ensure the accuracy of the records while simultaneously preventing redundancy when recording the usage of transaction log data.

[0048] In response, this application proposes some solutions to this problem.

[0049] In some embodiments, the transaction reconciliation method further includes: not recording first transaction flow data that was not written to the reconciliation file in the transaction reconciliation verification file, and not recording target transaction flow data that was not written to the supplementary reconciliation file in the transaction reconciliation verification file.

[0050] In existing technologies, even transaction log data that hasn't been used for reconciliation still has a status field. Whether transaction log data was actually used during transaction reconciliation is distinguished by the value of the status field. For example, for transaction log data that has been used for reconciliation, the value of this status field is true; for transaction log data that hasn't been used for reconciliation, the value of this status field is false. It's clear that marking the reconciliation usage status of transaction log data in the transaction database requires a significant amount of space from the transaction database.

[0051] In the embodiments of this application, successful use, that is, transaction flow data written to the reconciliation file or supplementary reconciliation file, is recorded in the transaction reconciliation verification file, but unsuccessful use, that is, transaction flow data not written to the reconciliation file or supplementary reconciliation file, is not recorded. In other words, only positive data is recorded and negative data is not recorded, so the amount of data in the transaction reconciliation verification file is relatively smaller.

[0052] In some embodiments, the transaction reconciliation record includes a globally unique identifier for the transaction log data that has been written into the reconciliation file or supplementary reconciliation file. That is, the transaction reconciliation record only needs to demonstrate the uniqueness of the transaction log data; if a transaction log data is recorded as successfully used, other transaction log data will not be located.

[0053] The selection of a globally unique identifier can be determined based on actual business needs. For example, in some embodiments, the globally unique identifier includes a transaction serial number and the transaction initiator. The transaction serial number can be a transaction number, but for some business scenarios, such as withdrawal and deposit transactions, the transaction serial number of a withdrawal transaction is the same as the transaction serial number of its matching deposit transaction, thus enabling verification. Therefore, to achieve global uniqueness, the transaction initiator also needs to be included.

[0054] In some embodiments, the transaction reconciliation file has a unique correspondence with the transaction database, and different transaction databases correspond to different transaction reconciliation files.

[0055] Specifically, the transaction database in this application can be one of multiple databases in a distributed database system, or it can be referred to as a sub-database. Both the first and second transaction reconciliation tasks can involve multiple transaction databases in the distributed database system. If transaction reconciliation files corresponding to the tasks are directly generated, the flexibility of task configuration would make these files difficult to query and manage. Furthermore, when performing supplementary reconciliation, data routing would need to be re-executed, resulting in low convenience. Therefore, constructing transaction reconciliation files that correspond one-to-one with each transaction database can improve the execution efficiency of supplementary reconciliation tasks.

[0056] In some embodiments, determining the target transaction data to be reconciled based on the second transaction data and the transaction reconciliation file includes: for each second transaction data, querying the transaction reconciliation file based on the globally unique identifier of the second transaction data; if the query result is empty, then the second transaction data is determined to be the target transaction data to be reconciled.

[0057] For example, the first transaction reconciliation task is expected to use 1,000 transaction records, while the transaction reconciliation verification file records information related to 980 transaction records. Therefore, it can be determined that there are 20 missing transaction records, specifically, the information related to these 20 transaction records cannot be found in the transaction reconciliation verification file.

[0058] Specifically, during the execution of the transaction reconciliation task, the second transaction data can be read one by one, the globally unique identifier can be extracted and queried in the transaction reconciliation verification file. If it can be found, it means that the second transaction data has been written into the reconciliation file or the supplementary reconciliation file and does not need to be reconciled. Otherwise, the supplementary reconciliation logic can be used for processing.

[0059] Embodiments of this application also provide a transaction reconciliation apparatus, applied in a transaction reconciliation server, for implementing the transaction reconciliation method as described in any of the above embodiments.

[0060] Specifically, Figure 2 This is a schematic diagram of the structure of a transaction reconciliation device according to an embodiment of this application. Figure 2 As shown, the transaction reconciliation device 200 includes:

[0061] The reconciliation unit 210 is used to record the first transaction flow data that has been written into the reconciliation file in the transaction reconciliation verification file during the process of performing the first transaction reconciliation task using the first transaction flow data in the transaction database. The transaction reconciliation verification file is stored in a storage area independent of the transaction database.

[0062] The determining unit 220 is used to determine the target transaction flow data to be reconciled based on the second transaction flow data and the transaction reconciliation verification document during the process of performing the second transaction reconciliation task using the second transaction flow data in the transaction database.

[0063] The reconciliation unit 230 is used to perform reconciliation tasks on the target transaction flow data and record the target transaction flow data that has been written into the reconciliation file into the transaction reconciliation verification file.

[0064] In some embodiments, the reconciliation unit 210 is used to read transaction information related to the corresponding first transaction reconciliation task or the corresponding supplementary reconciliation task from the first transaction flow data or the target transaction flow data. The transaction information includes at least one of the following: transaction flow identifier, transaction amount, transaction type, transaction status, transaction initiator, and transaction counterparty; and writes the read transaction information into the reconciliation file or the supplementary reconciliation file accordingly.

[0065] In some embodiments, the reconciliation unit 210 is used to generate a corresponding transaction reconciliation record for each first transaction data that has been written into the reconciliation file in the transaction reconciliation verification file; the supplementary reconciliation unit 230 is used to generate a corresponding transaction reconciliation record for each target transaction data that has been written into the supplementary reconciliation file in the transaction reconciliation verification file.

[0066] In some embodiments, the transaction reconciliation record includes a globally unique identifier for the transaction log data that has been written into the reconciliation file or supplementary reconciliation file.

[0067] In some embodiments, the globally unique identifier includes the transaction log identifier and the transaction initiator.

[0068] In some embodiments, the determining unit 220 is used to query the transaction reconciliation file for each second transaction data based on the globally unique identifier of the second transaction data; if the query result is empty, the second transaction data is determined to be the target transaction data to be reconciled.

[0069] In some embodiments, the reconciliation unit 210 is further configured not to record the first transaction flow data that was not written to the reconciliation file in the transaction reconciliation verification file; the supplementary reconciliation unit 230 is further configured not to record the target transaction flow data that was not written to the supplementary reconciliation file in the transaction reconciliation verification file.

[0070] In some embodiments, the transaction reconciliation file has a unique correspondence with the transaction database, and different transaction databases correspond to different transaction reconciliation files.

[0071] It is understood that the above-mentioned transaction reconciliation device can implement each step of the transaction reconciliation method executed by the transaction reconciliation server provided in the foregoing embodiments. The relevant explanations of the transaction reconciliation method are applicable to the transaction reconciliation device and will not be repeated here.

[0072] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Please refer to it. Figure 3 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.

[0073] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0074] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0075] The processor reads the corresponding computer program from non-volatile memory into main memory and then executes it, forming a transaction reconciliation mechanism at the logical level. The processor executes the program stored in memory and specifically performs the following operations:

[0076] During the execution of the first transaction reconciliation task using the first transaction flow data in the transaction database, the first transaction flow data already written into the transaction reconciliation verification file is recorded in the transaction reconciliation verification file, which is stored in a storage area independent of the transaction database. During the execution of the second transaction reconciliation task using the second transaction flow data in the transaction database, the target transaction flow data to be reconciled is determined based on the second transaction flow data and the transaction reconciliation verification file. A supplementary reconciliation task is performed on the target transaction flow data, and the target transaction flow data already written into the supplementary reconciliation file is recorded into the transaction reconciliation verification file.

[0077] The above is as stated in this application. Figure 1The transaction reconciliation device disclosed in the illustrated embodiments can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0078] The electronic device can also perform Figure 1 The method for executing the transaction reconciliation device in China, and the implementation of the transaction reconciliation device in China. Figure 1 The functions of the embodiments shown are not described in detail here.

[0079] This application also proposes a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by an electronic device including multiple applications, enable the electronic device to perform... Figure 1 The method executed by the transaction reconciliation device in the illustrated embodiment is specifically used to perform:

[0080] During the execution of the first transaction reconciliation task using the first transaction flow data in the transaction database, the first transaction flow data already written into the transaction reconciliation verification file is recorded in the transaction reconciliation verification file, which is stored in a storage area independent of the transaction database. During the execution of the second transaction reconciliation task using the second transaction flow data in the transaction database, the target transaction flow data to be reconciled is determined based on the second transaction flow data and the transaction reconciliation verification file. A supplementary reconciliation task is performed on the target transaction flow data, and the target transaction flow data already written into the supplementary reconciliation file is recorded into the transaction reconciliation verification file.

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

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

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

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

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

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

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

[0088] 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 a process, method, article, or apparatus. Without further limitations, 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 said element.

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

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

Claims

1. A transaction reconciliation method, executed by a transaction reconciliation server, wherein, The method includes: During the execution of the first transaction reconciliation task using the first transaction flow data in the transaction database, the first transaction flow data that has been written into the reconciliation file is recorded in the transaction reconciliation verification file, which is stored in a storage area independent of the transaction database. During the execution of the second transaction reconciliation task using the second transaction flow data in the transaction database, the target transaction flow data to be reconciled is determined based on the second transaction flow data and the transaction reconciliation verification file. Perform a reconciliation task on the target transaction flow data, and record the target transaction flow data that has been written into the reconciliation file into the transaction reconciliation verification file; The transaction reconciliation verification file is used to record the usage of transaction reconciliation data in the transaction flow record. The transaction reconciliation file records the first transaction flow data already written to the reconciliation file, and records the target transaction flow data already written to the supplementary reconciliation file into the transaction reconciliation file, including: In the transaction reconciliation file, a corresponding transaction reconciliation record is generated for each first transaction data that has been written into the reconciliation file, and a corresponding transaction reconciliation record is generated for each target transaction data that has been written into the supplementary reconciliation file. In the process of performing the second transaction reconciliation task using the second transaction log data in the transaction database, the target transaction log data to be reconciled is determined based on the second transaction log data and the transaction reconciliation verification document, including: In the process of performing a second transaction reconciliation task using the second transaction flow data in the transaction database, the second transaction flow data is determined, and the second transaction flow data includes one or more first transaction flow data that should be used by the first transaction reconciliation task; Determine the actual transaction log data used based on the transaction reconciliation documents; By comparing the first transaction log data that should be used in the first transaction reconciliation task with the actual transaction log data used, the missing transaction log data is determined. The method further includes: The first transaction data that was not written to the reconciliation file is not recorded in the transaction reconciliation file, and the target transaction data that was not written to the supplementary reconciliation file is not recorded in the transaction reconciliation file. The transaction reconciliation file has a unique correspondence with the transaction database, and different transaction databases correspond to different transaction reconciliation files.

2. The method as described in claim 1, wherein, The step of performing a first transaction reconciliation task using the first transaction flow data in the transaction database, and performing a supplementary reconciliation task on the target transaction flow data, includes: Read transaction information related to the corresponding first transaction reconciliation task or the corresponding supplementary reconciliation task from the first transaction flow data or the target transaction flow data. The transaction information includes at least one of the following: transaction flow identifier, transaction amount, transaction type, transaction status, transaction initiator, and transaction counterparty. The read transaction information will be written into the reconciliation file or supplemented into the reconciliation file accordingly.

3. The method as described in claim 1, wherein, The transaction reconciliation record includes a globally unique identifier for the transaction flow data that has been written into the reconciliation file or supplementary reconciliation file.

4. The method of claim 3, wherein, The globally unique identifier includes the transaction log identifier and the transaction initiator.

5. The method of claim 3, wherein, The step of determining the target transaction data to be reconciled based on the second transaction log data and the transaction reconciliation document includes: For each second transaction record, a query is performed in the transaction reconciliation file based on the globally unique identifier of that second transaction record; if the query result is empty, then that second transaction record is determined to be the target transaction record to be reconciled.

6. A transaction reconciliation device, applied in a transaction reconciliation server, wherein, The transaction reconciliation device is used to implement the transaction reconciliation method according to any one of claims 1 to 5.

7. An electronic device, comprising: processor; as well as A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform any of the transaction reconciliation methods of claims 1 to 5.

8. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of applications, cause the electronic device to perform any of the transaction reconciliation methods of claims 1 to 5.

Images