A transaction data processing method and apparatus

Abstract

The present disclosure provides a transaction data processing method and device, through a two-stage matching process, solves the matching failure problem caused by the local database response delay of the platform with explicit matching fields, reduces the demand for manual supplement; by supporting user customization of matching elements, performing the second matching based on the customized elements, solving the matching problem of the platform without explicit matching fields, breaking through the limitation of fixed fields, expanding the application range; based on the matching of multiple field combinations, avoid single field error, realize accurate matching, solve the problem of poor accuracy of manual matching; using the unique identification of transaction data and the last node data for bidirectional binding and automatic state updating, replacing manual recording of association relationship, avoiding human error, improving efficiency; through multi-scene matching mechanism such as automatic triggering, timing task, user manual triggering, achieving continuous matching coverage of full transaction data, solving the limitation of single matching mode, further reducing manual intervention.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of association reconciliation, and in particular to a transaction data processing method and device. BACKGROUND

[0002] Payment vouchers, transaction details and receipts are three common types of data or vouchers in financial management. In the entire transaction business process, payment records are generated at the payment stage, transaction details are generated at the transaction stage, and receipts are generated at the completion of the transaction. In the process of fund management, the enterprise finance needs to associate and match payment vouchers, transaction details and receipts. How to improve the accuracy of association and matching and reduce the pressure of manual matching is a technical problem that needs to be solved urgently.

[0003] The current matching system relies on the direct interface of the bank business system and realizes automatic matching through fixed matching fields. However, this method is only suitable for transaction data generated by bank business systems with clear matching fields. For transaction data generated by bank business systems without clear matching fields, accurate matching cannot be achieved, and only manual matching can be relied on, which is not only inefficient but also may lead to inaccurate matching due to human error. SUMMARY

[0004] The present disclosure provides a transaction data processing method and device to at least solve the above technical problems in the prior art.

[0005] According to a first aspect of the present disclosure, a transaction data processing method is provided. A transaction system generates transaction data of nodes in a transaction process in sequence, including payment vouchers, transaction details and receipts. The method is applied to a transaction association matching system and includes:

[0006] Receiving transaction data generated by the transaction system and storing it in the local database of the transaction association matching system. The transaction data is transaction details or receipts. In response to the source platform of the transaction data supporting transaction association matching function, a matching element is generated, a first matching process is performed based on the matching element, and a first matching result is obtained;

[0007] In response to the first matching result being the transaction data of the previous node matched with the transaction data stored in the local database, the state of the transaction data and the transaction data of the previous node matched with it in the local database is set to matched. In response to the first matching result being that the local database does not store the transaction data of the previous node matched with the transaction data, a second matching process is performed through a data API service for the transaction data at a fixed time, and a second matching result is obtained;

[0008] in response to the second matching result being that the specified database has transaction data of the previous node matching the transaction data, setting states of the transaction data and the transaction data of the previous node matching the transaction data in the local database as matched; and in response to the second matching result being that the specified database does not store the transaction data of the previous node matching the transaction data, returning an operation of performing the second matching process on the transaction data through the data API service.

[0009] The method further comprises:

[0010] in response to the source platform of the transaction data not supporting the transaction correlation matching function, obtaining a matching element customized by a user;

[0011] performing the second matching process through the data API service based on the customized matching element.

[0012] The method further comprises:

[0013] obtaining transaction data specified by a user as not matched;

[0014] in response to the source platform of the transaction data supporting the transaction correlation matching function, generating a matching element, performing the second matching process based on the matching element, and obtaining a second matching result;

[0015] in response to the source platform of the transaction data not supporting the transaction correlation matching function, obtaining a matching element customized by a user, and performing the second matching process through the data API service based on the customized matching element.

[0016] The first matching process comprises: based on a multi-field combined matching element, searching for transaction data of a previous node in the local database, which is completely consistent with all field values of the matching element;

[0017] The second matching process comprises: based on a multi-field combined matching element, calling a data API service to search for transaction data of a previous node in the specified database, which is completely consistent with all field values of the matching element.

[0018] When the states of the transaction data and the transaction data of the previous node matching the transaction data in the local database are set as matched, the method further comprises:

[0019] binding, in the local database, a unique identifier of the transaction data with the transaction data of the matched previous node, and binding a unique identifier of the transaction data of the matched previous node with the transaction data.

[0020] The method further comprises:

[0021] synchronizing the transaction data, the state and the bound identifier stored in the local database to the designated database.

[0022] The application further provides a transaction data processing device, a transaction system sequentially generates transaction data of nodes in a transaction flow, including a payment voucher, a transaction detail and a receipt, the device is applied to a transaction association matching system, and the device comprises the following:

[0023] a data receiving and storing module, which is configured to receive transaction data generated by the transaction system, store the transaction data in a local database of the transaction association matching system, and trigger a platform function judging module, the transaction data is a transaction detail or a receipt;

[0024] the platform function judging module is configured to judge whether a source platform of the transaction data supports a transaction association matching function in response to the trigger;

[0025] a matching element generating module, which is configured to generate a matching element in response to the source platform supporting the transaction association matching function;

[0026] a first matching flow executing module, which is configured to execute a first matching flow based on the matching element, and obtain a first matching result;

[0027] a second matching flow executing module, which is configured to execute a second matching flow through a data API service in response to the first matching result being that the local database does not store previous node transaction data matched with the transaction data, and obtain a second matching result, and the second matching flow is executed through the data API service at a specified time when the second matching result is that the designated database does not store matched previous node transaction data;

[0028] a state updating module, which is configured to set a state of the transaction data and the matched previous node transaction data in the local database as matched when the first matching result is that the local database stores the matched previous node transaction data, and set the state of the transaction data and the matched previous node transaction data in the local database as matched when the second matching result is that the designated database stores the matched previous node transaction data.

[0029] The device further comprises:

[0030] an interaction module, which is configured to acquire a matching element customized by a user and send the customized matching element to the second matching flow executing module in response to the source platform of the transaction data not supporting the transaction association matching function;

[0031] Correspondingly, the second matching flow executing module is further configured to execute the second matching flow through the data API service based on the customized matching element.

[0032] The interaction module is further configured to trigger the platform function judgment module to judge whether the source platform of the transaction data supports the transaction association matching function when the user-specified unmatched transaction data is acquired.

[0033] The first matching process execution module is specifically configured to: based on a matching element of a multi-field combination, search the transaction data of the previous node in the local database that is completely consistent with all field values of the matching element;

[0034] The second matching process execution module is specifically configured to: based on a matching element of a multi-field combination, call a data query service to search the transaction data of the previous node in the specified database that is completely consistent with all field values of the matching element.

[0035] In the above scheme, through two-level matching processes (the first matching is based on a preset multi-field combination to perform real-time matching in the local database, and the second matching is performed through a data API service to access the specified database for compensation at a fixed time after the first matching fails), the matching failure problem of platforms with explicit matching fields caused by the response delay of the local database is solved, and the demand for manual compensation is reduced; by supporting user customization of matching elements and performing the second matching based on the customized elements, the matching problem of platforms without explicit matching fields is solved, the fixed field limitation is broken, and the application range is expanded; the matching is performed based on a multi-field combination to avoid single field errors, achieve accurate matching, and solve the problem of poor accuracy of manual matching; the unique identification of transaction data and the data of the previous node is bidirectionally bound and the state is automatically updated, which replaces manual recording of the association relationship, avoids human errors, and improves efficiency; through multiple scene matching mechanisms such as automatic triggering, a fixed time task, and user manual triggering, the continuous matching coverage of all transaction data is achieved, the limitation of a single matching method is solved, and manual intervention is further reduced.

[0036] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0037] The above and other objects, features and advantages of the exemplary embodiments of the present disclosure will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0038] In the drawings, identical or corresponding reference numerals indicate identical or corresponding parts.

[0039] Figure 1 A transaction data processing flow diagram of an embodiment of the present application;

[0040] Figure 2A transaction data processing flow diagram of another embodiment of the present application;

[0041] Figure 3 A transaction data processing device structure diagram of an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to make the purposes, features and advantages of the present disclosure more obvious and easy to understand, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present disclosure.

[0043] As Figure 1 shown, the present application provides a transaction data processing method applied to a transaction association matching system, which matches transaction data generated by a transaction system, including the following operations:

[0044] Operation 101, receiving transaction data generated by a transaction system and storing it in the local database of the transaction association matching system, the transaction data being transaction details or a return single, in response to the source platform of the transaction data supporting transaction association matching function, generating matching elements, executing a first matching process based on the matching elements, and obtaining a first matching result.

[0045] The transaction system refers to a business system that generates node transaction data in sequence in the transaction process, specifically covering related systems of payment link, transaction occurrence link and transaction completion link (such as bank payment system). Its core function is to generate and output transaction data in the order of transaction process, including payment documents, transaction details and return single, providing original data source for the matching of subsequent transaction association matching system. It can be understood that more node transaction data can be generated according to the transaction process of different transaction systems, and these transaction data are matched.

[0046] In the example of the present application, the payment document is the first node data of the transaction process, which is generated in the payment link and is a voucher recording payment information, containing fields such as document number (VoucherNo), bank account number (BankAcc), amount (amt), payment date, transaction counterparty information, etc. In particular, as the first node, the payment document does not trigger the matching process when stored in the local database of the transaction association matching system, but only serves as a matching object for subsequent nodes (transaction details).

[0047] The transaction details are the second node data of the transaction process, generated when the transaction occurs, and are the transaction-by-transaction record of the fund flow, containing fields such as transaction date, amount (amt), bank account (BankAcc), transaction serial number, and counterparty account number. After being stored in the local database, it triggers the first matching process to match the transaction data of the previous node (payment document).

[0048] The receipt is the third node data of the transaction process, generated after the transaction is completed, and is the transaction confirmation voucher issued by the transaction system (bank or payment institution), containing fields such as voucher number (VoucherNo), bank account (BankAcc), amount (amt), transaction time, and bank seal identification. After being stored in the local database, it triggers the first matching process to match the transaction data of the previous node (transaction details).

[0049] The transaction association matching system receives payment documents, transaction details, or receipts generated by the transaction system in the transaction process in real time through a pre-set interface (such as a bank direct interface). Among them:

[0050] When the transaction association matching system receives data, it first checks the data format (such as field integrity and data type compliance), and after passing the check, writes the full field information of the payment document, transaction details, or receipt to the corresponding data table (payment document table / detail data table / receipt data table) in the local database, and generates a unique identifier for each transaction data (such as SerialId (transaction detail unique identifier), BillNo (payment document unique identifier), ReceiptId (receipt unique identifier)), and initializes its status as "unmatched" by default.

[0051] This process needs to ensure the real-time nature of data storage, ensuring that the subsequent matching process (such as the first matching process when storing) can be based on the latest data, and the local database needs to support fast query and field retrieval of transaction data, providing a data basis for multi-field combination matching in the first matching process.

[0052] When storing transaction details or receipts, first determine whether the source platform supports transaction association matching function. The source platform here refers to the source of transaction data (transaction details or receipts) (such as bank systems, financial institutions, and other transaction systems). Supporting transaction association matching function means that the platform's transaction data contains explicit fields that can be used for cross-node matching. The source information supporting transaction association matching function can be pre-configured, and if the source platform of the stored transaction data matches the pre-configured source information, it is determined that the transaction association matching function is supported.

[0053] According to the matching rules supported by the source platform, i.e. the pre-set multi-field combination, extract the values of the corresponding fields from the transaction data to generate matching elements.

[0054] For example, the transaction data is a transaction detail (to be matched with a payment voucher), the source platform is 1, and according to the preset multi-field combination, the matching element can be "VoucherNo (payment voucher number) + BankAcc (local account number) + amt (amount)". The source platform is 2, and the matching element can be Reverse4 (payment identifier) + BankAcc (local account number) + amt (amount). If the return sheet corresponds to the source platform 1, the matching element thereof includes the "VoucherNo (payment voucher number) + BankAcc (local account number) + amt (amount)" field.

[0055] Then, based on the generated matching element, a first matching process is performed, and the core is to retrieve the transaction data of the previous node in the local database based on the generated matching element. The specific steps are as follows:

[0056] Based on the matching element (for example, VoucherNo + BankAcc + amt), the transaction data of the previous node is retrieved in the local database:

[0057] If it is a transaction detail, it can be checked whether there is a payment voucher in the payment voucher table with the same values of VoucherNo, BankAcc and amt.

[0058] If it is a return sheet, it can be checked whether there is a transaction detail in the transaction detail table with the same values of VoucherNo, BankAcc and amt.

[0059] The retrieval process depends on the index mechanism of the local database to ensure real-time performance.

[0060] If the transaction data (such as the transaction detail finds the corresponding payment voucher, and the return sheet finds the corresponding transaction detail) of the previous node with all field values completely consistent with the matching element is retrieved in the local database, the first matching result is successful. If the transaction data of the previous node with all field values completely consistent with the matching element is not retrieved in the local database (possibly because the previous node data is not stored, the field values do not match, etc.), the first matching result is failed.

[0061] Operation 102, in response to the first matching result that the local database stores the transaction data of the previous node matched with the transaction data, the state of the transaction data and the transaction data of the previous node matched therewith in the local database is set to be matched; in response to the first matching result that the local database does not store the transaction data of the previous node matched with the transaction data, a second matching process is performed for the transaction data through a data API service to obtain a second matching result.

[0062] When the first matching process successfully retrieves the last node transaction data matching the current transaction data (transaction details or receipt) in the local database, the system performs the following operations:

[0063] The status field (such as match_status) of the transaction data in the local database is updated from not matched to matched, and in one example, it can also be assigned a matching time (such as match_time). The status of the last node transaction data is also updated to matched and the matching time is recorded.

[0064] In one example, the matched transaction data in the local database can also be uniquely identified and bidirectionally bound:

[0065] If the current transaction data is a transaction detail (matching payment document), add a BillNo field to the transaction detail, bind the unique identifier of the corresponding payment document, and add a SerialId field to the payment document, bind the unique identifier of the transaction detail.

[0066] If the current transaction data is a receipt (matching transaction detail), add a SerialId field to the receipt, bind the unique identifier of the corresponding transaction detail, and add a ReceiptId field to the transaction detail table, bind the unique identifier of the receipt.

[0067] In one example, the matching relationship can also be recorded in the local database, which contains information such as unique identifiers, matching time, and matching elements, which can facilitate subsequent queries.

[0068] When the first matching process does not find matching last node transaction data in the local database, the system triggers the second matching process, with the following specific steps:

[0069] For transaction data that is not successfully matched by the first matching process, it can be stored in a cache queue, and the second matching process can be performed on the transaction data in the queue at a regular time (i.e., the second matching process is triggered by a regular task). In one example, to facilitate queries in the queue, the matching elements and unique identifiers of the transaction data (generated in operation 101) can be recorded.

[0070] The system can regularly call a pre-configured data API service (such as a bank data API or an internal API of a transaction association matching system) to access an external data source (a specified database), and based on the matching elements of the current transaction data, initiate a query request: pass the matching elements (such as VoucherNo+BankAcc+amt) of the transaction data to the data API service as query conditions to find matching last node transaction data in the specified database.

[0071] If the transaction data of the previous node that is completely consistent with all field values of the matching element is found in the specified database (such as the transaction details find the corresponding payment voucher, the return sheet finds the corresponding transaction details), the second matching result is successful; if the transaction data of the previous node that is completely consistent with all field values of the matching element is not found in the specified database (may be due to the previous node data not being stored, field values not matching, etc.), the first matching result is failed.

[0072] The data API service queries the specified database to implement the second matching process, which can improve the query efficiency of the data: the traditional query method directly accesses the transaction system (the core business system such as the payment system), and the core system needs to prioritize transaction execution, fund transfer and other key businesses. High-frequency queries will occupy its computing resources, resulting in query request queuing and response delay. As an independent query intermediate layer, the data API service can handle matching query requirements, so that query requests do not need to wait, thereby shortening the response time. In addition, the data API service can be optimized around the query characteristics of the matching (such as multi-field combination retrieval, high-frequency repeated query), for example, index and cache design, joint index of matching element fields (such as VoucherNo, BankAcc, amt) is established, and hot query results (such as matching data of recent high-frequency transactions) are stored through cache (such as Redis), avoiding accessing the underlying database every time, and directly returning the result from the cache.

[0073] Operation 103, in response to the second matching result being that the specified database has transaction data of the previous node that matches the transaction data, setting the state of the transaction data and the transaction data of the previous node that matches it in the local database to matched; in response to the second matching result being that the specified database does not store transaction data of the previous node that matches the transaction data, returning to the operation of executing the second matching process through the data API service for the transaction data.

[0074] When the second matching process (querying the specified database through the data API service) successfully retrieves the previous node transaction data that matches the current transaction data (transaction details or return sheet), the system performs the following operations:

[0075] According to the unique identifier of the current transaction data and the unique identifier of the matched previous node transaction data (the unique identifier of the matched previous node transaction data can be returned by the data API service in response to the query request data in the second matching process, and the unique identifier of the current transaction data can be obtained from the cache queue), the corresponding transaction data is retrieved in the local database, and the state field (such as match_status) of the transaction data in the local database is updated from unmatched to matched, and in an example, a matching time (such as match_time) can also be assigned to it, and the state of the previous node transaction data is also updated to matched, and the matching time is recorded.

[0076] In an example, the matched transaction data can also be bidirectionally bound in the local database by unique identifier:

[0077] If the current transaction data is a transaction detail (matching a payment document), a BillNo field is added to the transaction detail to bind the unique identifier of the corresponding payment document, and a SerialId field is added to the payment document to bind the unique identifier of the transaction detail.

[0078] If the current transaction data is a receipt (matching a transaction detail), a SerialId field is added to the receipt to bind the unique identifier of the corresponding transaction detail, and a ReceiptId field is added to the transaction detail table to bind the unique identifier of the receipt.

[0079] In an example, the matching relationship can also be recorded in the local database, which includes the unique identifiers of both parties, the matching time, and the matching elements, which can facilitate subsequent queries.

[0080] When the second matching process (querying the specified database through the data API service) does not retrieve the previous node transaction data matched with the current transaction data (transaction detail or receipt), the transaction data is stored in the cache queue again, and the second matching process is performed on the transaction data in the queue at a regular time.

[0081] The second matching process performed by each timing task is the same as described in operation 102, which will not be repeated here.

[0082] In another example of the present disclosure, as shown in Figure 2 The transaction data processing method further includes:

[0083] Operation 201, in response to the source platform of the transaction data not supporting the transaction association matching function, obtaining the matching elements customized by the user, and performing the second matching process based on the customized matching elements through the data API service.

[0084] When the source platform of the transaction data (transaction details or receipt) does not support transaction association matching function (i.e. the platform does not provide the fixed fields required by the first matching process, or cannot obtain standardized matching elements through direct interface), the system actively obtains the user's customized matching elements, and executes the second matching process through the data API service.

[0085] The system shows the user the configurable fields of the current transaction data through the interactive interface, including mandatory fields and optional fields. For example, the mandatory fields can include: amount (amt), bank account (BankAcc), currency (Currency), transaction time (TransTime), etc.; the optional fields can include: counterparty account (CounterpartyAcc), purpose, transaction trace number (TraceNo), etc., and the user can check according to the actual business rules.

[0086] The user checks the field combination through the interface (such as amt+BankAcc+Currency+Purpose), forms the customized matching elements, and saves it as the exclusive matching rule of the source platform (the matching elements can be reused when the transaction data of the source platform is matched in the future, until the user re-customizes).

[0087] The system extracts the user's customized matching element field values from the current transaction data (transaction details or receipt), takes the customized matching elements as the query condition, accesses the specified database (such as the self-built database of the source platform, third-party data service, etc.) through the data API service, and retrieves the last node transaction data consistent with the element field values.

[0088] The data API service supports the retrieval of non-standardized fields (such as adapting custom multi-field combinations), ensuring that the user's customized rules can be implemented.

[0089] If the second matching process is not successful at this time, the transaction data will be stored in the cache queue (record its customized matching elements and the unique identifier generated when the transaction data is stored in the database), and the second matching process can be triggered again through the timing task through the data API service. If the second matching process is successful at this time, the current transaction data and its corresponding.

[0090] In another example of the present application, the second matching process can also be triggered according to the user's needs. For example, in some scenarios, after the transaction data is stored, the transaction data is displayed according to the user's needs, and according to the state of the transaction data recorded in the local database, the displayed transaction data includes matched and unmatched, or only the unmatched transaction data is displayed according to the user's needs. The user can issue a matching request for the unmatched transaction data through interactive operation. At this time, the transaction association matching system obtains the user-specified unmatched transaction data, and judges whether the source platform of the transaction data supports the transaction association matching function.

[0091] If the transaction association matching function is supported, the matching elements are generated (according to the matching rules supported by the source platform, that is, the pre-set multi-field combination, the values of the corresponding fields in the transaction data are extracted to generate the matching elements), and the second matching process is executed based on the matching elements through the data API service to obtain the second matching result; if the matching is successful, the state is updated in the local database, and if the matching fails, the transaction data is stored in the cache queue and waits for the timing task to trigger the second matching process through the data API.

[0092] If the transaction association matching function is not supported, the user-customized matching elements can be obtained through the interactive interface, and the second matching process is executed based on the customized matching elements through the data API service (same as operation 201, which will not be described here).

[0093] It should be noted that the specified database accessed by the second matching process needs to synchronize the transaction data in real time from the local database, including the state and the bound identifier. Real-time synchronization can ensure that the specified database contains the latest transaction data of the local database, so as to ensure the accuracy of the second matching process.

[0094] In the above scheme of the present application, a hierarchical matching mechanism is adopted, the first matching process is used to match in real time based on the pre-set multi-field combination in the local database, and the second matching process is used to compensate the matching through the data API service to access the specified database, thereby solving the problem of limited application scope caused by relying on fixed fields; by supporting user-defined matching elements, the system automatically executes the matching, thereby avoiding the problem of low efficiency and poor accuracy of pure manual matching when there is no explicit field; by using the unique identifier bidirectional binding and real-time synchronization of transaction data, state and identifier between the local database and the specified database, the traceability and consistency of the matching relationship are realized; through the multi-scene triggering mechanism such as automatic triggering after storage, timing task compensation triggering, and user manual click triggering, the system availability is improved in abnormal conditions.

[0095] In order to realize the above-mentioned transaction data processing method, the present application also provides a transaction data processing device, and a transaction system generates transaction data of nodes in a transaction process in sequence, including payment vouchers, transaction details and receipts. The device is applied to a transaction association matching system, such asFigure 3 The device comprises:

[0096] A data receiving and storing module 10 is configured to receive transaction data generated by a transaction system, store the transaction data in a local database of the transaction association matching system, and trigger a platform function judging module 20, wherein the transaction data is transaction details or a receipt;

[0097] The platform function judging module 20 is configured to determine whether a source platform of the transaction data supports a transaction association matching function in response to the trigger;

[0098] A matching element generating module 30 is configured to generate a matching element in response to the source platform supporting the transaction association matching function;

[0099] A first matching flow executing module 40 is configured to execute a first matching flow based on the matching element to obtain a first matching result;

[0100] A second matching flow executing module 50 is configured to execute a second matching flow through a data API service to obtain a second matching result in response to the first matching result being that the local database does not store previous node transaction data matched with the transaction data, and the second matching flow is executed through the data API service at a specified time when the second matching result is that the specified database does not store the previous node transaction data matched with the transaction data;

[0101] A state updating module 60 is configured to set a state of the transaction data and the previous node transaction data matched with the transaction data in the local database as matched when the first matching result is that the local database stores the previous node transaction data matched with the transaction data, and set the state of the transaction data and the previous node transaction data matched with the transaction data in the local database as matched when the second matching result is that the specified database stores the previous node transaction data matched with the transaction data.

[0102] The device further comprises an interaction module (not shown in the figure), which is configured to obtain matching elements customized by a user and send the customized matching elements to the second matching flow executing module 50 in response to the source platform of the transaction data not supporting the transaction association matching function, and the second matching flow executing module 50 is further configured to execute the second matching flow through the data API service based on the customized matching elements.

[0103] The interaction module is further configured to, when the user-specified unmatched transaction data is obtained, trigger the platform function judgment module 20 to determine whether the source platform of the transaction data supports a transaction correlation matching function. If so, the matching element generation module 30 is triggered to generate a matching element, so that the second matching process execution module 50 executes a second matching process based on the generated matching element through a data API service; if not, the interaction module is triggered to obtain a user-customized matching element, and the customized matching element is sent to the second matching process execution module 50, so that the second matching process is executed based on the customized matching element through the data API service.

[0104] The first matching process execution module 40 is specifically configured to, based on the multi-field combined matching element, retrieve transaction data of the previous node in the local database that is completely consistent with all field values of the matching element.

[0105] The second matching process execution module 50 is specifically configured to, based on the multi-field combined matching element, call a data query service to retrieve transaction data of the previous node in the specified database that is completely consistent with all field values of the matching element.

[0106] Exemplarily, the present disclosure also provides an electronic device, comprising:

[0107] a processor;

[0108] a memory for storing executable instructions of the processor;

[0109] The processor is configured to read the executable instructions from the memory and execute the instructions to implement the above transaction data processing method.

[0110] Exemplarily, the present disclosure also provides a computer readable storage medium, which stores a computer program for executing the above transaction data processing method.

[0111] In addition to the above method and device, the embodiments of the present application can also be a computer program product, which includes computer program instructions that, when executed by a processor, cause the processor to perform the steps of the methods according to various embodiments of the present application described in the above “Exemplary Method” section.

[0112] The computer program product can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. The embodiments of the present application are not limited by the programming languages used to implement the methods described herein.

[0113] In addition, an embodiment of the present application can also be a computer readable storage medium, which stores computer program instructions, and when the computer program instructions are run on a processor, the processor executes the steps of the methods according to various embodiments of the present application described in the above "Exemplary Methods" section of the specification.

[0114] The computer readable storage medium can be any combination of one or more computer readable media. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the above. More specific examples (a non-exhaustive list) of the computer readable storage medium include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0115] The above describes the basic principles of the present application in combination with specific embodiments, but it should be noted that the advantages, advantages, effects and the like mentioned in the present application are only examples and are not limiting, and these advantages, advantages, effects and the like cannot be considered as the must-have of each embodiment of the present application. In addition, the above specific details are only for the purpose of example and understanding, and are not limiting, and the above details do not limit the present application to the must-have of the above specific details.

[0116] The block diagrams of the devices, apparatuses, equipment, systems referred to in this application are only illustrative examples and are not intended to require or imply that the connection, arrangement, configuration must be as shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, equipment, systems can be connected, arranged, configured in any manner. Words such as "include," "contain," "have," and the like are open-ended words that are intended to mean "including but not limited to," and are to be used interchangeably. The words "or" and "and" as used herein are intended to mean "and / or," and are to be used interchangeably. The word "such as" as used herein is intended to mean "such as but not limited to," and is to be used interchangeably.

[0117] It is also important to note that each of the devices, apparatuses, and methods described in this application can be embodied in a variety of forms, including but not limited to a device, a system, a method, a computer program product, a process, a business method, a data structure, and the like.

[0118] The above description of disclosed aspects is provided to enable any person skilled in the art to make or use the application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects without departing from the scope of the application. Thus, the present application is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0119] The above description has been presented for the purpose of illustration and description. Furthermore, this description is not intended to limit the embodiments of the application to the forms disclosed herein. Although various example aspects and embodiments have been discussed above, those of skill in the art will recognize certain variations, modifications, changes, additions, and sub-combinations thereof.

Claims

1. A method for processing transaction data, characterized in that, The transaction system sequentially generates transaction data for each node in the transaction process, including payment slips, transaction details, and receipts. This method is applied to a transaction association matching system, including: The system receives transaction data generated by the transaction system in real time and stores it in the local database of the transaction association matching system. The transaction data is either transaction details or receipts. In response to the fact that the source platform of the transaction data supports the transaction association matching function, the system generates matching elements and executes the first matching process based on the matching elements to obtain the first matching result. In response to the first matching result that the local database stores transaction data of the previous node that matches the transaction data, the status of the transaction data and the transaction data of the previous node that matches it in the local database is set to matched; in response to the first matching result that the local database does not store transaction data of the previous node that matches the transaction data, the second matching process is executed periodically for the transaction data through the data API service to obtain the second matching result. In response to the second matching result that the specified database has transaction data of the previous node that matches the transaction data, the status of the transaction data and the transaction data of the previous node that matches it in the local database is set to matched; in response to the second matching result that the specified database does not store transaction data of the previous node that matches the transaction data, the operation of performing the second matching process through the data API service for the transaction data is returned periodically. When setting the status of the transaction data in the local database and the transaction data of the previous node that matches it to "matched", the method further includes: In the local database, the unique identifier of the transaction data is bound to the transaction data of the matching previous node; The transaction data, the status, and the bound identifier stored in the local database are synchronized to the designated database.

2. The method according to claim 1, characterized in that, The method also includes: In response to the fact that the source platform of the transaction data does not support the transaction association matching function, the user-customized matching elements are obtained; Based on customized matching elements, a second matching process is executed through the data API service.

3. The method according to claim 1, characterized in that, The method also includes: Retrieve user-specified unmatched transaction data; In response to the fact that the source platform of the transaction data supports the transaction association matching function, a matching element is generated, and a second matching process is executed based on the matching element to obtain a second matching result; Since the source platform of the transaction data does not support the transaction association matching function, the system obtains user-customized matching elements and executes a second matching process based on the customized matching elements through the data API service.

4. The method according to any one of claims 1-3, characterized in that, The first matching process includes: retrieving transaction data from the previous node in the local database based on the matching element with a combination of multiple fields, which is completely consistent with all field values ​​of the matching element; The second matching process includes: based on the matching elements with multiple field combinations, calling the data API service to retrieve the transaction data of the previous node in the specified database that is completely consistent with all field values ​​of the matching element.

5. A transaction data processing device, characterized in that, The transaction system sequentially generates transaction data for each node in the transaction process, including payment slips, transaction details, and receipts. The device is used in a transaction association and matching system and includes: The data receiving and storage module is used to receive transaction data generated by the transaction system in real time, store it in the local database of the transaction association matching system, and trigger the platform function judgment module. The transaction data is either transaction details or receipts. The platform function judgment module is used to respond to the trigger and determine whether the source platform of the transaction data supports the transaction association matching function; The matching element generation module generates matching elements in response to the source platform supporting transaction association matching function; The first matching process execution module is used to execute the first matching process based on the matching elements to obtain the first matching result; The second matching process execution module, in response to the first matching result being that the local database does not store the previous node transaction data that matches the transaction data, executes the second matching process through the data API service to obtain the second matching result, and periodically executes the second matching process through the data API service when the second matching result is that the specified database does not store the matching previous node transaction data. The status update module is used to set the status of the transaction data and its matching previous node transaction data in the local database to "matched" when the first matching result is that the local database stores matching previous node transaction data; it is also used to set the status of the transaction data and its matching previous node transaction data in the local database to "matched" when the second matching result is that the specified database stores matching previous node transaction data. When setting the status of the transaction data in the local database and the transaction data of the previous node that matches it to "matched", the method further includes: In the local database, the unique identifier of the transaction data is bound to the transaction data of the matching previous node; The transaction data, the status, and the bound identifier stored in the local database are synchronized to the designated database.

6. The apparatus according to claim 5, characterized in that, The device also includes: The interaction module is used to respond to the fact that the source platform of the transaction data does not support the transaction association matching function, obtain the user-customized matching elements, and send the customized matching elements to the second matching process execution module; Accordingly, the second matching process execution module is also used to execute the second matching process through a data API service based on customized matching elements.

7. The apparatus according to claim 6, characterized in that, The interaction module is also used to trigger the platform function judgment module to determine whether the source platform of the transaction data supports the transaction association matching function when unmatched transaction data specified by the user is obtained.

8. The apparatus according to claim 5, characterized in that: The first matching process execution module is specifically used to: based on the matching element with a combination of multiple fields, retrieve the transaction data of the previous node in the local database that is completely consistent with all field values ​​of the matching element; The second matching process execution module is specifically used to: based on the matching elements with multiple field combinations, call the data query service in the specified database to retrieve the transaction data of the previous node that is completely consistent with all field values ​​of the matching element.

Images