CN115880085A - Transaction reconciliation method, device, electronic equipment and storage medium - Google Patents
Transaction reconciliation method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115880085A CN115880085A CN202111134286.9A CN202111134286A CN115880085A CN 115880085 A CN115880085 A CN 115880085A CN 202111134286 A CN202111134286 A CN 202111134286A CN 115880085 A CN115880085 A CN 115880085A
- Authority
- CN
- China
- Prior art keywords
- transaction
- reconciliation
- file
- flow data
- check
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a transaction reconciliation method, a transaction reconciliation device, electronic equipment and a storage medium. The method comprises the following steps: in the process of executing a first transaction reconciliation task by using first transaction running data in a transaction database, recording the first transaction running data written into a reconciliation file in a transaction reconciliation check file, wherein the transaction reconciliation check file is stored in a storage area independent of the transaction database; in the process of executing a second transaction reconciliation task by using second transaction running data in the transaction database, determining target transaction running data to be reconciled according to the second transaction running data and the transaction reconciliation check file; and executing a reconciliation task on the target transaction flow data, and recording the target transaction flow data written into the reconciliation compensation file into the transaction reconciliation check file. The technical scheme reduces the writing operation on the transaction database and reduces the reading and writing pressure of the transaction database, so that the transaction database can better provide technical support for real-time transaction service.
Description
Technical Field
The present application relates to the field of online payment technologies, and in particular, to a transaction reconciliation method, an apparatus, an electronic device, and a storage medium.
Background
The transaction reconciliation refers to checking accounts by relying on transaction flow data, under the condition that the intermediate party platform is connected with a plurality of transaction mechanisms, the transaction flow data of each transaction mechanism is stored on the intermediate party platform, and the intermediate party platform can rely on a transaction database for storing the transaction flow data to carry out transaction reconciliation, so that a transaction reconciliation bill is provided for each transaction mechanism.
In the transaction reconciliation process, the situation that the transaction flow data used for the transaction reconciliation is not complete due to faults is difficult to completely avoid, and in order to solve the problem, the missed transaction flow data can be found out to carry out the reconciliation and the reconciliation state can be updated according to the reconciliation state of the transaction flow data. However, since the transaction flow data is stored in the transaction database, the writing operation of the reconciliation process to the transaction database increases the processing pressure of the transaction database, thereby possibly affecting the capability of the transaction database to process real-time transaction services.
Disclosure of Invention
The embodiment of the application provides a transaction reconciliation method, a transaction reconciliation device, electronic equipment and a storage medium, so as to reduce the influence of the transaction reconciliation on a transaction database.
The embodiment of the application adopts the following technical scheme:
in a first aspect, an embodiment of the present application provides a transaction reconciliation method, which is performed by a transaction reconciliation server, and includes: in the process of executing a first transaction reconciliation task by using first transaction running data in a transaction database, recording the first transaction running data written into a reconciliation file in a transaction reconciliation check file, wherein the transaction reconciliation check file is stored in a storage area independent of the transaction database; in the process of executing a second transaction reconciliation task by using second transaction running data in the transaction database, determining target transaction running data to be reconciled according to the second transaction running data and the transaction reconciliation check file; and executing a reconciliation compensation task on the target transaction running data, and recording the target transaction running data written into the reconciliation compensation file into the transaction reconciliation check file.
In some embodiments, performing a first transaction reconciliation task using first transaction pipelining data in the transaction database and performing a reconciled reconciliation task on the target transaction pipelining data comprises: reading transaction information related to the corresponding first transaction reconciliation task or the corresponding reimbursement reconciliation task in the first transaction flow data or the target transaction flow data, wherein the transaction information comprises at least one of the following: transaction flow identification, transaction amount, transaction type, transaction state, transaction initiator and transaction counter-party; and correspondingly writing the read transaction information into the reconciliation file or the reconciled reconciliation file.
In some embodiments, recording the first transaction flow data written to the reconciliation file in the transaction reconciliation file, and recording the target transaction flow data written to the reconciled reconciliation file in the transaction reconciliation file, comprises: and in the transaction reconciliation check file, generating a corresponding transaction reconciliation check record for each piece of transaction flow data written in the reconciliation check file or the reconciliation compensation check file respectively.
In some embodiments, the transaction reconciliation check record comprises: and the global unique identifier of the transaction flow data written into the reconciliation file or the reconciled reconciliation file.
In some embodiments, the globally unique identification includes a transaction pipeline identification and a transaction initiator.
In some embodiments, determining the target transaction flow data to be reconciled based on the second transaction flow data and the transaction reconciliation check file comprises: for each piece of second transaction flow data, inquiring in the transaction reconciliation check file according to the global unique identifier of the piece of second transaction flow data; and if the query result is null, determining that the second transaction flow data is the target transaction flow data to be reconciled.
In some embodiments, the transaction reconciliation method further comprises: and not recording first transaction running data which is not written into the reconciliation file in the transaction reconciliation check file, and not recording target transaction running data which is not written into the reconciliation supplement file in the transaction reconciliation check file.
In some embodiments, the transaction reconciliation check file has a unique correspondence with the transaction database, with different transaction databases corresponding to different transaction reconciliation check files.
In a second aspect, an embodiment of the present application further provides a transaction reconciliation device, which is applied to a transaction reconciliation server, and is used for implementing the transaction reconciliation method as described in any one of the above.
In some embodiments, the transaction reconciliation arrangement comprises: the reconciliation unit is used for recording the first transaction flow data written into the reconciliation file in a transaction reconciliation check file in the process of executing the first transaction reconciliation task by using the first transaction flow data in the transaction database, wherein the transaction reconciliation check file is stored in a storage area independent from the transaction database; the determining unit is used for determining target transaction flow data to be reconciled and reconciled according to the second transaction flow data and the transaction reconciliation check file in the process of executing a second transaction reconciliation task by using the second transaction flow data in the transaction database; and the account compensation and reconciliation unit is used for executing an account compensation and reconciliation task on the target transaction running data and recording the target transaction running data written into the account compensation and reconciliation file into the transaction and reconciliation check file.
In some embodiments, the reconciliation unit is configured to read transaction information related to the corresponding first transaction reconciliation task or the corresponding reimbursement task in the first transaction flow data or the target transaction flow data, where the transaction information includes at least one of: transaction flow identification, transaction amount, transaction type, transaction state, transaction initiator and transaction counter-party; and correspondingly writing the read transaction information into the reconciliation file or the reconciled reconciliation file.
In some embodiments, the reconciliation unit is configured to generate, in the transaction reconciliation check file, a corresponding transaction reconciliation check record for each piece of the first transaction flow data written in the reconciliation check file; and the account compensation and reconciliation unit is used for respectively generating a corresponding transaction and reconciliation check record for each piece of target transaction flow data written in the account compensation and reconciliation check file.
In some embodiments, the transaction reconciliation check record comprises: and the global unique identification of the transaction flow data written into the reconciliation file or the reconciled reconciliation file.
In some embodiments, the globally unique identification includes a transaction pipeline identification and a transaction initiator.
In some embodiments, the determining unit is configured to query each piece of second transaction flow data in the transaction reconciliation check file according to the globally unique identifier of the piece of second transaction flow data; and if the query result is null, determining that the second transaction flow data is the target transaction flow data to be reconciled.
In some embodiments, the reconciliation unit is further configured to not record the first transaction running data, in which the reconciliation file is not written, in the transaction reconciliation check file; and the account checking and supplementing unit is also used for not recording target transaction running data which is not written in the account checking and supplementing file in the transaction account checking and supplementing file.
In some embodiments, the transaction reconciliation check file has a unique correspondence with the transaction database, with different transaction databases corresponding to different transaction reconciliation check files.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor; and a memory arranged to store computer executable instructions that, when executed, cause the processor to perform a transaction reconciliation method as described in any of the above.
In a fourth aspect, embodiments of the present application further provide a computer-readable storage medium storing one or more programs which, when executed by an electronic device including a plurality of application programs, cause the electronic device to perform a transaction reconciliation method as described above.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: the transaction reconciliation check file stored independently of the transaction database is utilized to record the transaction flow data written in the reconciliation check file or the reconciliation correction check file, so that the writing operation on the transaction database in the transaction reconciliation task executing process is reduced, the writing operation on the transaction database in the reconciliation correction task executing process is also reduced, the reading and writing pressure on the transaction database is reduced, and the transaction database can better provide technical support for real-time transaction service.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic flow chart illustrating a transaction reconciliation method in an embodiment of the present application;
fig. 2 is a schematic structural diagram of a transaction reconciliation apparatus in an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
The inventor finds that if the transaction database is marked to indicate which transaction flow data are used for account checking and account compensating, although the missing transaction flow data can be determined by querying the transaction database, the writing operation on the transaction database in the account checking link is required to be added, the transaction flow data already used for account checking are marked, and the writing operation on the transaction database in the account compensating link is required to be added, and the transaction flow data already used for account compensating are marked.
The technical idea of the application is that the transaction reconciliation check file is used for recording the transaction reconciliation use condition of the transaction flow data outside the transaction database, when the reconciliation is compensated, the missed transaction flow data can be determined by using the transaction reconciliation check file, the write operation on the transaction database is reduced, and the transaction database can provide service for real-time transaction more fully.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart of a transaction reconciliation method in an embodiment of the present application. The transaction reconciliation method can be executed by a transaction reconciliation server and specifically comprises the following steps:
step S110, in the process of executing the first transaction reconciliation task by using the first transaction flow data in the transaction database, recording the first transaction flow data written into the reconciliation file in the transaction reconciliation check file, where the transaction reconciliation check file is stored in a storage area independent of the transaction database.
In this step, the reconciliation logic of the first transaction reconciliation task may be implemented with reference to the prior art, for example, whether there is a matched deposit transaction in the withdrawal transaction according to the transaction serial number. After the reconciliation is finished by using the piece of first transaction flow data, the piece of first transaction flow data or part of the content of the piece of first transaction flow data can be written into a reconciliation file.
Compared with the prior art, the method and the device have the advantages that whether the transaction flow data are used for transaction reconciliation or not is not directly recorded in the transaction database, but a transaction reconciliation check file is used, can be in a format required by any service such as text or tables and is not stored in the transaction database, so that the writing operation on the transaction database is reduced.
And step S120, in the process of executing a second transaction reconciliation task by using second transaction running data in the transaction database, determining target transaction running data to be reconciled according to the second transaction running data and the transaction reconciliation check file.
Generally, the execution of the first transaction reconciliation task has atomicity, that is, a piece of first transaction running data is read from the transaction database, and the first transaction reconciliation task is executed until the writing of the reconciliation file is successful, and the piece of transaction running data is not considered to be used for transaction reconciliation, and in the process, the omission of the transaction running data can be caused by file writing failure or data reading failure. In order to find out the missed transaction flow data, second transaction flow data can be determined firstly, wherein the second transaction flow data comprises first transaction flow data which are used by one or more first transaction reconciliation tasks; and determining actually used transaction flow data according to the transaction reconciliation check file, and determining the missed transaction flow data through comparison.
And step S130, executing a reconciliation compensation task on the target transaction running data, and recording the target transaction running data written into the reconciliation compensation file into the transaction reconciliation check file. Wherein the reconciliation logic of the reconciliation task can be the same as the reconciliation logic of the first transaction reconciliation task.
It can be seen that, in the method shown in fig. 1, transaction reconciliation check files stored independently of a transaction database are used for recording transaction flow data written in the reconciliation check files or the reconciliation correction files, so that the write operation on the transaction database in the transaction reconciliation task execution process is reduced, the write operation on the transaction database in the reconciliation correction task execution process is also reduced, the read-write pressure on the transaction database is reduced, and the transaction database can better provide technical support for real-time transaction service.
In some embodiments, performing a first transaction reconciliation task using first transaction pipeline data in a transaction database and performing a reconciliation compensation task on target transaction pipeline data comprises: reading transaction information related to the corresponding first transaction reconciliation task or the corresponding reimbursement reconciliation task in the first transaction flow data or the target transaction flow data, wherein the transaction information comprises at least one of the following: transaction flow identification, transaction amount, transaction type, transaction state, transaction initiator and transaction counter-party; and correspondingly writing the read transaction information into the reconciliation file or the reconciled reconciliation file.
And correspondingly reading transaction information related to the first transaction reconciliation task in the first transaction flow data or reading transaction information related to the reconciliation task in the target transaction flow data according to different executed tasks. In addition to the transaction information listed above, transaction time, transaction batch identification, and the like may be recorded in the transaction flow data. It should be noted here that not all transaction information recorded in the transaction flow data needs to participate in the transaction reconciliation, and therefore, only the transaction information related to the transaction reconciliation task in the transaction flow data needs to be read.
The actual stored in the transaction statement file is the detail of the read transaction information, so that the subsequent formation of the transaction statement corresponding to each transaction mechanism is facilitated, and the transaction mechanism can perform the checking and peer subsequent operation according to the transaction statement.
In some embodiments, recording the first transaction flow data written to the reconciliation file in the transaction reconciliation check file, and recording the target transaction flow data written to the reconciliation check file in the transaction reconciliation check file comprises: and in the transaction reconciliation check file, generating a corresponding transaction reconciliation check record for each piece of transaction flow data written in the reconciliation check file or the reconciliation compensation check file respectively.
That is, each time one transaction flow data is actually used, a corresponding transaction reconciliation check record is generated in the transaction reconciliation check file.
In the prior art, a status field is usually added in transaction flow data to record whether the transaction flow data is used for transaction reconciliation. In the technical scheme of the application, such processing is no longer performed in the transaction database, and therefore, how to ensure the accuracy of the realization of the recording and simultaneously ensure that no redundancy exists in the recording when the using condition of the transaction flow data is recorded needs to be faced.
In this regard, the present application proposes some solutions to this problem.
In some embodiments, the transaction reconciliation method further comprises: and not recording first transaction flow data which are not written into the reconciliation file in the transaction reconciliation check file, and not recording target transaction flow data which are not written into the reissue reconciliation file in the transaction reconciliation check file.
In the prior art, even transaction running data without account checking is also provided with a status field, and whether the transaction running data is actually used when a transaction account checking task is executed is distinguished by the value of the status field. For example, transaction flow data used for reconciliation, the value of the status field is true; transaction pipelining data for unpaired use, the value of the status field is false. Therefore, the reconciliation use condition of the transaction flow data is marked in the transaction database, and a large amount of space of the transaction database is occupied.
In the embodiment of the application, the successful use is recorded in the transaction reconciliation check file, that is, transaction running data written in the reconciliation check file or the reconciliation supplement file is not recorded, and the failure in use is not recorded, that is, the transaction running data not written in the reconciliation check file or the reconciliation supplement file is not recorded, that is, only positive data is recorded, and negative data is not recorded, so that the data volume of the transaction reconciliation check file is relatively smaller.
In some embodiments, the transaction reconciliation check record comprises: and the global unique identification of the transaction flow data written into the reconciliation file or the reconciled reconciliation file. That is to say, the transaction reconciliation check record only needs to show the record uniqueness of the transaction flow data, and if the use success of one transaction flow data is recorded, other transaction flow data cannot be located.
The selection of the globally unique identifier may be determined according to actual business requirements, for example, in some embodiments, the globally unique identifier includes a transaction flow identifier and a transaction initiator. The transaction running identity may be a transaction running number, but for some business scenarios, such as an out transaction and an in transaction, the transaction running number of one out transaction data is the same as the transaction running number of the matched in transaction data, thereby enabling verification. Therefore, in order to realize global uniqueness, a transaction initiator needs to be added.
In some embodiments, the transaction reconciliation check file has a unique correspondence with the transaction database, and different transaction databases have different transaction reconciliation check files.
In particular, the transaction database in the present application may be one of a plurality of databases in a distributed database system, or may be referred to as a sub-database. The first transaction reconciliation task, as well as the second transaction reconciliation task, can both involve multiple transaction databases in the distributed database system. If the transaction reconciliation check file corresponding to the task is directly generated, due to the flexibility of task configuration, the transaction reconciliation check file is not easy to inquire and manage, when the reconciliation is carried out, data routing needs to be carried out again, and the convenience is low, so that the transaction reconciliation check file corresponding to the transaction database one by one is constructed, and the execution efficiency of the reconciliation task can be improved.
In some embodiments, determining the target transaction flow data to be reconciled based on the second transaction flow data and the transaction reconciliation check file comprises: for each piece of second transaction flow data, inquiring in the transaction reconciliation check file according to the global unique identifier of the piece of second transaction flow data; and if the query result is null, determining that the second transaction flow data is the target transaction flow data to be reconciled.
For example, 1000 pieces of first transaction flow data expected to be used by the first transaction reconciliation task, and 980 pieces of relevant information of the transaction flow data are recorded in the transaction reconciliation check file, so that it can be determined that 20 pieces of missing transaction flow data are present, and the detailed description is that the 20 pieces of relevant information of the transaction flow data cannot be inquired in the transaction reconciliation check file.
Specifically, in the execution process of the reconciliation task of the replenishment transaction, the second transaction running data can be read one by one, the global unique identifier is respectively extracted and inquired in the transaction reconciliation check file, if the global unique identifier can be inquired, the second transaction running data is written into the reconciliation check file or the replenishment reconciliation check file, and the replenishment reconciliation is not needed; instead, the reconciliation logic can be utilized for processing.
The embodiment of the application also provides a transaction reconciliation device which is applied to a transaction reconciliation server and used for realizing the transaction reconciliation method in any one of the above embodiments.
Specifically, fig. 2 is a schematic structural diagram of a transaction reconciliation device in an embodiment of the present application. As shown in fig. 2, the transaction reconciliation apparatus 200 comprises:
the reconciliation unit 210 is configured to record the first transaction flow data written in the reconciliation file in the transaction reconciliation check file during the process of executing the first transaction reconciliation task by using the first transaction flow data in the transaction database, wherein the transaction reconciliation check file is stored in a storage area independent from the transaction database.
The determining unit 220 is configured to determine, according to the second transaction flow data and the transaction reconciliation check file, target transaction flow data to be reconciled during the process of executing the second transaction reconciliation task by using the second transaction flow data in the transaction database.
And the reconciliation supplementing unit 230 is used for executing a reconciliation supplementing task on the target transaction running data and recording the target transaction running data written into the reconciliation supplementing file into the transaction reconciliation checking file.
In some embodiments, the reconciliation unit 210 is configured to read transaction information related to the corresponding first transaction reconciliation task or the corresponding reimbursement task in the first transaction flow data or the target transaction flow data, where the transaction information includes at least one of: transaction flow identification, transaction amount, transaction type, transaction state, transaction initiator and transaction counter-party; and correspondingly writing the read transaction information into the reconciliation file or the reconciled reconciliation file.
In some embodiments, the reconciliation unit 210 is configured to generate, in the transaction reconciliation check file, a corresponding transaction reconciliation check record for each piece of the first transaction running data written in the reconciliation check file; and the reconciliation unit 230 is configured to generate a corresponding transaction reconciliation check record for each piece of target transaction flow data written in the reconciliation check file in the transaction reconciliation check file.
In some embodiments, the transaction reconciliation check record comprises: and the global unique identification of the transaction flow data written into the reconciliation file or the reconciled reconciliation file.
In some embodiments, the globally unique identification includes a transaction flow identification and a transaction initiator.
In some embodiments, the determining unit 220 is configured to query each piece of second transaction flow data in the transaction reconciliation check file according to the globally unique identifier of the piece of second transaction flow data; and if the query result is null, determining that the second transaction flow data is the target transaction flow data to be reconciled and reconciled.
In some embodiments, the reconciliation unit 210 is further configured to not record the first transaction running data, in which the reconciliation file is not written, in the transaction reconciliation check file; the reconciled ledger unit 230 is further configured to not record target transaction running data, in which the reconciled ledger file is not written, in the transaction reconciled ledger file.
In some embodiments, the transaction reconciliation check file has a unique correspondence with the transaction database, with different transaction databases corresponding to different transaction reconciliation check files.
It can be understood that the transaction reconciliation device can implement the steps of the transaction reconciliation method executed by the transaction reconciliation server provided in the foregoing embodiment, and the explanations related to the transaction reconciliation method are applicable to the transaction reconciliation device, and are not described herein again.
Fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Referring to fig. 3, at a hardware level, the electronic device includes a processor, and optionally further includes an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory, such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, the network interface, and the memory may be connected to each other via an internal bus, which may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 3, but this does not indicate only one bus or one type of bus.
And the memory is used for storing programs. In particular, the program may include program code including computer operating instructions. The memory may include both memory and non-volatile storage and provides instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to form the transaction reconciliation device on the logic level. The processor is used for executing the program stored in the memory and is specifically used for executing the following operations:
in the process of executing a first transaction reconciliation task by using first transaction running data in a transaction database, recording the first transaction running data written into a reconciliation file in a transaction reconciliation check file, wherein the transaction reconciliation check file is stored in a storage area independent of the transaction database; in the process of executing a second transaction reconciliation task by using second transaction running data in the transaction database, determining target transaction running data to be reconciled according to the second transaction running data and the transaction reconciliation check file; and executing a reconciliation compensation task on the target transaction running data, and recording the target transaction running data written into the reconciliation compensation file into the transaction reconciliation check file.
The method executed by the transaction reconciliation device disclosed in the embodiment of fig. 1 of the present application can be applied to or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
The electronic device may further execute the method executed by the transaction reconciliation apparatus in fig. 1, and implement the functions of the transaction reconciliation apparatus in the embodiment shown in fig. 1, which are not described herein again in this embodiment of the present application.
An embodiment of the present application further provides a computer-readable storage medium storing one or more programs, where the one or more programs include instructions, which when executed by an electronic device including a plurality of application programs, enable the electronic device to perform the method performed by the transaction reconciliation apparatus in the embodiment shown in fig. 1, and are specifically configured to perform:
in the process of executing a first transaction reconciliation task by using first transaction flow data in a transaction database, recording first transaction flow data written into a reconciliation file in a transaction reconciliation check file, wherein the transaction reconciliation check file is stored in a storage area independent of the transaction database; in the process of executing a second transaction reconciliation task by using second transaction running data in the transaction database, determining target transaction running data to be reconciled according to the second transaction running data and the transaction reconciliation check file; and executing a reconciliation compensation task on the target transaction running data, and recording the target transaction running data written into the reconciliation compensation file into the transaction reconciliation check file.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may 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, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may 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, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may 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, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (11)
1. A transaction reconciliation method performed by a transaction reconciliation server, wherein the method comprises:
in the process of executing a first transaction reconciliation task by using first transaction flow data in a transaction database, recording first transaction flow data written into a reconciliation file in a transaction reconciliation check file, wherein the transaction reconciliation check file is stored in a storage area 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 reconciled and reconciled according to the second transaction flow data and the transaction reconciliation check file;
and executing a reconciliation compensation task on the target transaction running data, and recording the target transaction running data written into the reconciliation compensation file into the transaction reconciliation check file.
2. The method of claim 1, wherein the performing a first transactional reconciliation task using first transactional flow data in a transactional database and a reconciliation task using the targeted transactional flow data comprises:
reading transaction information related to a corresponding first transaction reconciliation task or a corresponding reimbursement reconciliation task in the first transaction flow data or the target transaction flow data, wherein the transaction information comprises at least one of the following: transaction flow identification, transaction amount, transaction type, transaction state, transaction initiator and transaction counter-party;
and correspondingly writing the read transaction information into the reconciliation file or the reconciled reconciliation file.
3. The method of claim 1, wherein recording the first transaction flow data written to the reconciliation file in a transaction reconciliation check file, and recording the target transaction flow data written to the reconciled reconciliation file in the transaction reconciliation check file comprises:
in the transaction reconciliation check file, a corresponding transaction reconciliation check record is respectively generated for each piece of first transaction flow data written with the reconciliation file, and a corresponding transaction reconciliation check record is respectively generated for each piece of target transaction flow data written with the reconciliation check file.
4. The method of claim 3, wherein the transaction reconciliation check record comprises: and the global unique identification of the transaction flow data written into the reconciliation file or the reconciled reconciliation file.
5. The method of claim 4, wherein the globally unique identification comprises a transaction pipeline identification and a transaction initiator.
6. The method of claim 4, wherein the determining target transaction flow data to be reconciled from the second transaction flow data and the transaction reconciliation check file comprises:
for each piece of second transaction flow data, inquiring in the transaction reconciliation check file according to the global unique identifier of the piece of second transaction flow data; and if the query result is null, determining that the second transaction flow data is the target transaction flow data to be reconciled.
7. The method of claim 1, wherein the method further comprises:
and not recording first transaction running data which is not written into the reconciliation file in the transaction reconciliation check file, and not recording target transaction running data which is not written into the reconciliation compensation file in the transaction reconciliation check file.
8. The method of any one of claims 1 to 7, wherein the transaction reconciliation check document has a unique correspondence with the transaction database, with different transaction databases corresponding to different transaction reconciliation check documents.
9. A transaction reconciliation device applied to a transaction reconciliation server, wherein the transaction reconciliation device is used for realizing the transaction reconciliation method of any one of claims 1 to 8.
10. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions which, when executed, cause the processor to perform the transaction reconciliation method of any one of claims 1 to 8.
11. A computer-readable storage medium storing one or more programs which, when executed by an electronic device including a plurality of application programs, cause the electronic device to perform the transaction reconciliation method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111134286.9A CN115880085A (en) | 2021-09-27 | 2021-09-27 | Transaction reconciliation method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111134286.9A CN115880085A (en) | 2021-09-27 | 2021-09-27 | Transaction reconciliation method, device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115880085A true CN115880085A (en) | 2023-03-31 |
Family
ID=85762851
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111134286.9A Pending CN115880085A (en) | 2021-09-27 | 2021-09-27 | Transaction reconciliation method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115880085A (en) |
-
2021
- 2021-09-27 CN CN202111134286.9A patent/CN115880085A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110020542B (en) | Data reading and writing method and device and electronic equipment | |
| CN107330776B (en) | Method and device for detecting bookkeeping and abnormal bookkeeping details | |
| CN110032598B (en) | Method and device for updating field and electronic equipment | |
| CN108599973B (en) | Log association method, device and equipment | |
| CN111782668A (en) | Data structure reading and updating method and device, and electronic equipment | |
| CN111897825A (en) | Distributed transaction processing method and device | |
| CN110060139B (en) | Accounting processing method and device | |
| CN108647950B (en) | Transfer request processing method, device and equipment | |
| CN110992188B (en) | Transaction processing method, device and equipment | |
| CN110992040A (en) | Transaction processing method, device and equipment | |
| CN114371918A (en) | Distributed transaction processing method and device, storage medium and electronic equipment | |
| CN108230130B (en) | Method and device for verifying daily cutting data and electronic equipment | |
| US20200294057A1 (en) | Business processing method, apparatus, and equipment | |
| CN108710658B (en) | Data record storage method and device | |
| CN115880085A (en) | Transaction reconciliation method, device, electronic equipment and storage medium | |
| CN111459474B (en) | Templated data processing method and device | |
| CN112783954B (en) | Data access method, device and server | |
| CN110245115B (en) | File processing method, engine and system | |
| CN113449023A (en) | Service processing method and device and electronic equipment | |
| CN113094414A (en) | Circulation map generation method and device | |
| CN111951009A (en) | Transaction data processing method and device, electronic equipment and computer-readable storage medium | |
| CN115965480A (en) | Distributed account checking method, device and system | |
| CN117455644A (en) | New and old system switching method and device, electronic equipment and storage medium | |
| CN116680338A (en) | Clear application release method and device and electronic equipment | |
| CN112559610A (en) | Method and device for generating account checking file |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |