A data processing method, apparatus, device, and medium

Abstract

The application relates to the technical field of data verification, in particular to a data processing method and device, equipment and medium, which are used to solve the problem that the error processing flow in the prior art cannot guarantee the accuracy of the result. The method comprises the following steps: acquiring transaction record data of a multi-party transaction error, wherein the transaction record data comprises record data generated by at least one processing component in M processing components of a processing system of a multi-party transaction for performing processing on the multi-party transaction; sending indication information to M1 processing components in the M processing components; acquiring reconciliation data generated when the M1 processing components perform reconciliation; when it is determined that the account information of the reconciliation data and the transaction record data are matched successfully, displaying the reconciliation data and the transaction record data on a user interface; and in response to an operation performed by a user on the user interface, ending the reconciliation process of the error sheet.

Description

Technical Field

[0001] This application relates to the field of data verification technology, and in particular to a data processing method, apparatus, device and medium. Background Technology

[0002] During a transaction, different transactions within the same transaction may be recorded by multiple accounting components. In some scenarios, due to technical failures such as system crashes or human error, some accounting components may fail to record the transaction successfully, while others may record it successfully. This results in the transaction not being completely offset, creating a one-sided accounting situation. When a one-sided accounting situation occurs, an error handling process can be generated, which can then be used for automatic or manual adjustments. After the adjustments are completed, the error handling process ends. However, in existing technologies, the error handling process lacks a robust verification mechanism, making it impossible to guarantee whether the error handling has been completed and whether the adjusted result is accurate. Summary of the Invention

[0003] This application provides a data processing method, apparatus, device, and medium to solve the problem that error processing procedures in the prior art cannot guarantee the accuracy of results.

[0004] In a first aspect, embodiments of this application provide a data processing method, including:

[0005] The system retrieves transaction record data indicating errors in multi-party transactions. This transaction record data includes data generated by at least one of the M processing components in the multi-party transaction processing system. Instruction information is sent to M1 of the M processing components, where M1 is the component that did not generate record data during the processing of the multi-party transaction. The instruction information instructs the M1 processing components to adjust accounts based on the transaction record data. Adjustment data generated by the M1 processing components during the adjustment process is retrieved. When the account information of the adjustment data and the transaction record data is successfully matched, the adjustment data and the transaction record data are displayed on the user interface. In response to an operation performed by the user on the user interface, instructing the user to complete the verification of the adjustment data and the transaction record data, the error reconciliation process ends.

[0006] Based on the above solution, by acquiring adjustment data and transaction record data, and matching the adjustment data and transaction record data with account information, a verification scheme is provided for the error handling process, which can ensure the correctness and completeness of the adjustment and increase the accuracy of error order processing.

[0007] In one possible implementation, the transaction record data includes the identifier of at least one of the M processing components, and the account information recorded by the at least one processing component for processing multi-party transactions. The account information includes transaction amount and transaction account information. Sending instruction information to M1 processing components among the M processing components includes: determining M1 processing components among the M processing components that need to adjust the transaction record data based on the account information recorded by the at least one processing component for processing multi-party transactions; wherein the identifier information of any of the M1 processing components is not included in the transaction record data or the account information corresponding to any of the processing components is incomplete; and sending instruction information to the M1 processing components.

[0008] In one possible implementation, obtaining the adjustment data generated when the M1 processing components perform adjustment includes: obtaining the adjustment data periodically sent by the M1 processing components and storing it in a set storage space, wherein the set storage space stores at least one adjustment data generated when the M1 processing components perform adjustment for the multi-party transaction in N adjustment cycles; N is a positive integer.

[0009] Determining that the account information of the adjustment data and the transaction record data matches includes: obtaining at least one adjustment data generated by the M1 processing components during N adjustment cycles for the multi-party transaction from the designated storage space, and determining that the account information in the at least one adjustment data matches the account information in the transaction record data.

[0010] In one possible implementation, the method further includes: before sending instruction information to M1 of the M processing components, adding an error order for the multi-party transaction to an error registration table, wherein the error order includes transaction record data of the multi-party transaction; wherein the instruction information includes identification information of the error order;

[0011] The adjustment data of a processing component includes the adjustment time when the processing component performs the adjustment operation, the global event tracking number of the operation, and the adjustment record generated by the operation. The global event tracking number is the operation identifier generated by the processing component when it performs the adjustment operation.

[0012] Retrieve at least one adjustment data point generated by the M1 processing component during N adjustment cycles for the multi-party transactions from the designated storage space, including:

[0013] Obtain at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the error report; wherein, at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the error report are generated and added to the error report indicated by the identification information of the error report in the error registration table when at least one processing component in the M1 processing component triggers the execution of the adjustment operation;

[0014] Based on the at least one global event tracking number and the adjustment time corresponding to each global event tracking number, at least one adjustment data generated by the M1 processing component during the adjustment of the multi-party transaction in N adjustment cycles is obtained from the set storage space.

[0015] In one possible implementation, the error slip further includes a matching status, which can be a successful match, a failed match, or a no-match; when the account information in the at least one adjustment data matches the account information in the transaction record data, the matching status of the error slip is a successful match; or; when the account information in the at least one adjustment data does not match the account information in the transaction record data, the matching status of the error slip is a failed match; or, before performing a matching operation on the account information in the at least one adjustment data and the account information in the transaction record data, the matching status of the error slip is a no-match.

[0016] Based on the above scheme, the matching status of the error order can be used to determine whether the adjustment data and transaction record data are balanced, which can provide users with a strong basis for verification.

[0017] In one possible implementation, the error slip further includes a matching timestamp and a matching count, and the method further includes: when it is determined that the transaction record data does not match the account information of the adjustment data, updating the matching timestamp and the matching count corresponding to the error slip.

[0018] In one possible implementation, the error order further includes the order creation time. When it is determined that the account information matching between the adjustment data and the transaction record data fails, the method further includes: when the error order meets a first condition at a set time, obtaining at least one adjustment data generated by the M1 processing components during the adjustment of the multi-party transaction sent in K adjustment cycles from the set storage space, wherein the K adjustment cycles are the adjustment cycles between the N adjustment cycles and the set time; matching the transaction record data with the at least one adjustment data generated during the adjustment of the multi-party transaction sent in the N adjustment cycles and the at least one adjustment data generated during the adjustment of the multi-party transaction sent in the K adjustment cycles to obtain a matching result, and updating the matching status of the error order according to the matching result; wherein the first condition includes the time interval between the error order creation time and the set time being greater than a first set duration, the time interval between the matching timestamp and the set time being greater than the matching cycle, and the number of matching times being less than a first threshold.

[0019] Based on the above scheme, a matching period can be set. If the adjustment data and transaction record data of the previous matching period fail to match, the adjustment data between the last matching time and the current matching time can be obtained in the current matching period, and then re-matched, which improves the accuracy of business processing.

[0020] In one possible implementation, the method further includes: when it is determined that the error registration table does not include a second error order at a second set time and the creation time of the second error order is greater than a third set time, saving the second error order to the error registration table, wherein the second error order includes the second transaction record data of the second multi-party transaction; obtaining at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the second error order; wherein the at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the second error order are generated and added to the error registration table when at least one adjustment operation is triggered corresponding to the second error order. The error is identified by the identification information of the second error order; based on at least one global event tracking number in the second error order and the adjustment time corresponding to each global event tracking number, at least one adjustment data corresponding to the second error order is obtained from the set storage space when the processing component corresponding to the second error order sends an adjustment for the second multi-party transaction in N1 adjustment cycles; the account information of the second transaction record data is matched with the account information of at least one adjustment data corresponding to the second error order to obtain the matching result of the second error order; the matching status of the second error order is updated according to the matching result of the second error order, and the matching timestamp and matching number of the second error order are updated.

[0021] Secondly, embodiments of this application provide a data processing apparatus, including:

[0022] The acquisition module is used to acquire transaction record data for errors in multi-party transactions. The transaction record data includes record data generated by at least one of the M processing components that perform processing on the multi-party transactions in the multi-party transaction processing system.

[0023] The sending module is used to send instruction information to M1 of the M processing components, wherein the M1 processing component is the processing component among the M processing components that did not generate record data during the processing of the multi-party transaction, and the instruction information is used to instruct the M1 processing component to adjust the accounts according to the transaction record data of the multi-party transaction;

[0024] The acquisition module is also used to acquire the adjustment data generated when the M1 processing components perform the adjustment;

[0025] The display module is used to display the adjustment data and the transaction record data on the user interface when it is determined that the account information of the adjustment data and the transaction record data are successfully matched.

[0026] The processing module is used to respond to an operation performed by the user on the user interface, wherein the operation instructs the user to complete the verification of the adjustment data and the transaction record data, and then ends the verification process of the error order.

[0027] In one possible implementation, the transaction record data includes the identifier of at least one of the M processing components, and the account information recorded by the at least one processing component for processing multi-party transactions. The account information includes transaction amount and transaction account information. When the sending module sends the instruction information to M1 of the M processing components, it is specifically used to: determine the M1 processing components among the M processing components that need to adjust the transaction record data based on the account information recorded by the at least one processing component for processing multi-party transactions; if the identifier information of any of the M1 processing components is not included in the transaction record data or the account information corresponding to any of the processing components is incomplete; and send the instruction information to the M1 processing components.

[0028] In one possible implementation, the acquisition module, when acquiring the adjustment data generated by the M1 processing components during the adjustment process, is specifically used to: acquire the adjustment data periodically sent by the M1 processing components and store it in a designated storage space, wherein the designated storage space stores at least one adjustment data generated by the M1 processing components during N adjustment cycles for the multi-party transaction; N is a positive integer;

[0029] The processing module, when determining that the account information of the adjustment data and the transaction record data matches, is specifically used to: obtain at least one adjustment data generated by the M1 processing components during the N adjustment cycles for the multi-party transaction from the set storage space, and determine that the account information in the at least one adjustment data matches the account information in the transaction record data.

[0030] In one possible implementation, the processing module is further configured to: add an error order for the multi-party transaction to the error registration table before sending the instruction information to M1 of the M processing components; the error order includes transaction record data of the multi-party transaction; wherein the instruction information includes the identification information of the error order.

[0031] The adjustment data of a processing component includes the adjustment time when the processing component performs the adjustment operation, the global event tracking number of the operation, and the adjustment record generated by the operation. The global event tracking number is the operation identifier generated by the processing component when it performs the adjustment operation.

[0032] The acquisition module, when acquiring at least one adjustment data generated by the M1 processing component during N adjustment cycles for adjusting the multi-party transactions from the designated storage space, specifically performs the following: acquiring at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the error order; wherein, the at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the error order are generated when at least one processing component of the M1 processing component triggers the execution of the adjustment operation and added to the error order in the error registration table as indicated by the error order identification information; and acquiring at least one adjustment data generated by the M1 processing component during N adjustment cycles for adjusting the multi-party transactions from the designated storage space based on the at least one global event tracking number and the adjustment time corresponding to each global event tracking number.

[0033] In one possible implementation, the error slip further includes a matching status, which can be a successful match, a failed match, or a no-match; when the account information in the at least one adjustment data matches the account information in the transaction record data, the matching status of the error slip is a successful match; or; when the account information in the at least one adjustment data does not match the account information in the transaction record data, the matching status of the error slip is a failed match; or, before performing a matching operation on the account information in the at least one adjustment data and the account information in the transaction record data, the matching status of the error slip is a no-match.

[0034] In one possible implementation, the error slip further includes a matching timestamp and a matching count, and the processing module is further configured to: when it is determined that the transaction record data does not match the account information of the adjustment data, update the matching timestamp and the matching count corresponding to the error slip.

[0035] In one possible implementation, the error order further includes the order creation time of the error order. When the processing module determines that the account information matching between the adjustment data and the transaction record data fails, it is further configured to: when the error order meets a first condition at a set time, retrieve at least one adjustment data generated by the M1 processing components during K adjustment cycles for adjusting the accounts of the multi-party transaction from the set storage space, where the K adjustment cycles are the adjustment cycles between the N adjustment cycles and the set time; match the transaction record data with the at least one adjustment data generated during the N adjustment cycles and the at least one adjustment data generated during the K adjustment cycles for adjusting the accounts of the multi-party transaction to obtain a matching result, and update the matching status of the error order according to the matching result; wherein, the first condition includes the time interval between the error order creation time and the set time being greater than a first set duration, the time interval between the matching timestamp and the set time being greater than the matching cycle, and the number of matching times being less than a first threshold.

[0036] In one possible implementation, the processing module is further configured to: when it is determined that the error registration table does not include a second error order at a second set time and the creation time of the second error order is greater than a third set time, save the second error order to the error registration table, wherein the second error order includes the second transaction record data of the second multi-party transaction; the acquisition module is further configured to acquire at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the second error order; wherein the at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the second error order are generated and added to the error registration table when at least one adjustment operation is triggered for the second error order. The error message is identified by the second error message; based on at least one global event tracking number in the second error message and the adjustment time corresponding to each global event tracking number, at least one adjustment data corresponding to the second error message is obtained from the designated storage space when the processing component corresponding to the second error message sends an adjustment for the second multi-party transaction in N1 adjustment cycles; the processing module is further configured to match the account information of the second transaction record data with the at least one adjustment data corresponding to the second error message to obtain the matching result of the second error message; update the matching status of the second error message according to the matching result of the second error message, and update the matching timestamp and matching number of the second error message.

[0037] Thirdly, this application provides an electronic device, comprising:

[0038] Memory, used to store program instructions;

[0039] A processor is configured to invoke program instructions stored in the memory and execute the steps of the method described in any one of the first aspects according to the obtained program instructions.

[0040] Fourthly, this application provides a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the method described in any one of the first aspects.

[0041] Fifthly, this application provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the method described in any one of the first aspects.

[0042] Furthermore, the technical effects of any of the implementation methods in the second to fifth aspects can be found in the first aspect and the technical effects of different implementation methods of the first aspect, which will not be repeated here. Attached Figure Description

[0043] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1A A schematic diagram of a business system architecture provided in this application embodiment;

[0045] Figure 1B A schematic diagram of a server structure provided in an embodiment of this application;

[0046] Figure 2 A flowchart illustrating a data processing method provided in an embodiment of this application;

[0047] Figure 3 A schematic diagram of a data processing apparatus provided in an embodiment of this application;

[0048] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0050] The terms "first" and "second" in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. The term "multiple" in this application can mean at least two, for example, two, three, or more, and the embodiments of this application do not impose limitations.

[0051] The data collection, dissemination, and use in this application all comply with relevant national laws and regulations.

[0052] Before introducing the data processing method provided in the embodiments of this application, for ease of understanding, the technical background of the embodiments of this application will be described in detail below.

[0053] During transactions, different transactions within the same transaction may require multiple accounting components to perform the accounting. In some scenarios, due to technical failures such as system crashes or human error, some accounting components may fail to record the transaction successfully, while others may record it successfully. This results in the transaction not being completely offset, creating a one-sided accounting situation. When a one-sided accounting situation occurs, an error handling process can be generated, which can then be used for automatic or manual adjustments. After the adjustments are completed, the error handling process can be terminated. However, in existing technologies, error handling processes lack robust verification mechanisms, making it impossible to guarantee whether the error handling has been completed and whether the adjusted result is accurate.

[0054] To address the aforementioned issues, this application provides a data processing method, apparatus, device, and medium. When an erroneous account is identified, an error slip is created based on the erroneous account, and the processing component that failed to post the transaction is notified to adjust the account based on the error slip. After the processing component adjusts the account, the time information and global event tracking number of the adjustment transaction are stored in the error slip. At the end of the day, a file sent by the processing component is received; this file includes the adjustment details of the adjustment transaction. Further, the adjustment data in the file is determined using the global event tracking number and time information, and the adjustment data is matched with the transaction record data in the error slip. When a match is successful, the matching status of the error slip is configured as "match successful," and the adjustment data and transaction record data are displayed on the user interface. When the user completes the verification of the error slip on the user interface, the verification process for the error slip ends.

[0055] Figure 1A An exemplary business system architecture applicable to embodiments of this application is illustrated. This system architecture may include one or more execution devices. The execution device may be implemented by one or more servers (or devices). The execution device can be used to implement the data processing method provided in embodiments of this application.

[0056] In some embodiments, the execution device may include one or more servers 100. Figure 1AThis example uses three servers. Server 100 can be implemented using a physical server or a virtual server. A server can be implemented as a single server or as a server cluster. A single server or a server cluster can be used to implement the data processing method provided in this application. Optionally, server 100 can be connected to other servers or terminal devices to receive transaction record data and adjustment data sent by other servers or terminal devices, or to send transaction record data and adjustment data to other servers or terminal devices. For example, terminal devices can be mobile phones, tablets, and personal computers. In some scenarios, server 100 can also receive data processing tasks sent by other servers or terminal devices, or send data processing results to other servers or terminal devices.

[0057] For example, server 100 can also be connected to a display device. After processing the data, server 100 can display the data processing results, transaction record data, and adjustment data through the display device. For example, the display device can be a liquid crystal display, an organic light-emitting diode (OLED) display, a projection display device, etc., and this application does not specifically limit it.

[0058] As an example, see Figure 1B As shown, the server 100 may include a processor 110, a communication interface 120, and a memory 130. Of course, the server 100 may also include other components. Figure 1B Not shown in the image.

[0059] The communication interface 120 is used to communicate with other servers or terminal devices, receiving transaction record data and adjustment data sent by other servers or terminal devices, or sending transaction record data and adjustment data to other servers or terminal devices. The communication interface 120 can also receive data processing requests from other servers or terminal devices, or send data processing results to other servers or terminal devices.

[0060] Processor 110 is the control center of server 100. It connects various parts of server 100 through various interfaces and routes. By running or executing software programs and / or modules stored in memory 130, and by calling data stored in memory 130, it performs various functions of server 100 and processes data. Processor 110 may be a processor, microprocessor, controller, or other control component. For example, it may be a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.

[0061] The memory 130 can be used to store software programs and modules. The processor 110 executes various functional applications and data processing by running the software programs and modules stored in the memory 130. The memory 130 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function, etc.; the data storage area may store data created according to business processing, etc. As a non-volatile computer-readable storage medium, the memory 130 can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The memory 130 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic memory, magnetic disk, optical disk, etc. The memory 130 is any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory 130 in this embodiment can also be a circuit or any other means capable of implementing storage functions for storing program instructions and / or data.

[0062] It should be noted that the above Figure 1A and Figure 1B The structure shown is merely an example, and the embodiments of the present invention are not limited thereto.

[0063] This application provides a data processing method. Figure 2 An exemplary data processing method flow is illustrated, which can be executed by an execution device. For example, it can be implemented by one or more servers, or by a processor within a server, or by one or more modules of a processor. The specific flow is as follows:

[0064] 201. Retrieve transaction record data for errors in multi-party transactions.

[0065] In some embodiments, during multi-party transactions, the transactions may be jointly recorded by M processing components, thereby generating transaction data records for the multi-party transactions. In some scenarios, when some processing components record the multi-party transactions while others fail to record them or do not generate any transactions, the transaction record data includes record data generated by at least one of the M processing components that perform processing for the multi-party transactions in the multi-party transaction processing system.

[0066] As an example, when party A transfers 10,000 yuan to party B, party A's account receives a deduction of 10,000 yuan, while party B's account receives a deposit of 10,000 yuan. In some scenarios, when party A and party B's accounts are on the same bank, their processing systems are identical. The processing system deducts the money from party A's account, transfers the deducted amount to party B's account, and then records the transaction in both party A and party B's accounts using processing components. In other scenarios, when party A and party B's accounts are not on the same bank, their processing systems differ. Party A's processing system deducts the money from party A's account, transfers the deducted amount to party B's processing system, and then records the transaction in party A's account using processing component A1 to obtain transaction record data (deposit record). After receiving the deduction amount from the processing system corresponding to transaction party A, the processing system corresponding to transaction party B transfers the deduction amount to transaction party B's account and records the transaction in transaction party B's account through processing component B1, obtaining transaction record data (logging record). In some scenarios, if the processing component corresponding to transaction party B fails to record the transaction in transaction party B's account, an accounting reconciliation error will occur when performing general ledger operations.

[0067] 202, Send indication information to M1 of the M processing components.

[0068] In some embodiments, the transaction record data includes the identifier of at least one of the M processing components and the account information recorded by the at least one processing component for processing multi-party transactions. The account information includes transaction amount and transaction account information. Processing component M1 is the processing component among the M processing components that did not generate record data during the processing of multi-party transactions. Specifically, M1 processing components among the M processing components that need to adjust the transaction record data can be determined based on the account information recorded by the at least one processing component for processing multi-party transactions; the identifier information of any processing component in M1 processing components is not included in the transaction record data or the account information corresponding to any processing component is incomplete; and instruction information is sent to the M1 processing components. As an example, when determining that the transaction record data corresponds to two processing components, A1 and B1, based on the identifier information of the processing components in the transaction record of a multi-party transaction, it can be determined that the identifier information is not included in the transaction record data or the account information corresponding to the processing component is incomplete, based on the account information in the transaction record data, which includes transaction amount and transaction account information. For example, if it is determined that the transaction only includes transaction record data corresponding to the A1 processing component and does not include transaction record data generated by the B1 processing component during the multi-party transaction processing, or if the transaction record data does not contain the identification information of the B1 processing component, an instruction message can be sent to the B1 processing component.

[0069] 203. Obtain the adjustment data generated when M1 processing components perform adjustment.

[0070] In some embodiments, reconciliation data periodically sent by M1 processing components is received and stored in a designated storage space. This designated storage space stores at least one reconciliation data point generated by the M1 processing components during N reconciliation cycles for multi-party transactions, where N is a positive integer. As an example, the M1 processing components may send reconciliation data on a daily or two-day basis; this application does not specifically limit this.

[0071] In some embodiments, before sending instruction information to M1 of the M processing components, error orders for multi-party transactions can be added to the error registry. These error orders include transaction record data for the transactions. When sending instruction information to the M1 of the M processing components, the instruction information includes identification information for the error orders. As an example, the identification information can be represented by a fixed-length string, or it can be represented in other forms. This application does not impose specific limitations on the form or length of the string.

[0072] In some embodiments, the reconciliation data of a processing component includes the time when the processing component performs a reconciliation operation, the global event tracking number of the operation, and the reconciliation record data generated by the operation. The global event tracking number is an operation identifier generated by the processing component performing the reconciliation operation. Obtaining at least one reconciliation data generated by the M1 processing component during N reconciliation cycles for multi-party transactions from a designated storage space can be achieved as follows: obtaining at least one global event tracking number and the reconciliation time corresponding to each global event tracking number from an error report. Specifically, the at least one global event tracking number and the reconciliation time corresponding to each global event tracking number in the error report are those generated when at least one processing component in the M1 processing component triggers the execution of a reconciliation operation and added to the error report identification information in the error registration table. Further, at least one reconciliation data generated by the M1 processing component during N reconciliation cycles for multi-party transactions can be obtained from the designated storage space based on the at least one global event tracking number and the reconciliation time corresponding to each global event tracking number.

[0073] As an example, the identifier of an error order in the instruction information received by the B1 processing component can be represented as "42357958ae". After receiving the instruction information, the B1 processing component can determine the error order with identifier 42357958ae in the error registration table based on the instruction information, and then obtain the transaction record data in that error order. Further, the B1 processing component can perform an adjustment operation based on the transaction record data to generate adjustment data. This adjustment data can include the time of the adjustment operation, the global event tracking number of the operation, and the adjustment record data generated by the operation. As an example, the time of the adjustment operation can be represented as 14:32:53 on March 21, 2022, and the global event tracking number of the operation can be represented as "JX2022346974628". Further, the adjustment time and the global event tracking number of the operation can be added to the error order with identifier 42357958ae in the error registration table. Furthermore, the adjustment data corresponding to the global event tracking number and adjustment time can be obtained from the designated storage space based on the global event tracking number "JX2022346974628" and the adjustment time. Similarly, when the B1 processing component needs to perform multiple adjustments, at least one adjustment data generated by the B1 processing component during the adjustment of multi-party transactions in N adjustment cycles can be obtained using the above method.

[0074] In some embodiments, when the M1 processing components and the consistency platform are in the same system, the error identification department of the consistency platform can formulate an adjustment plan based on transaction record data. On the error adjustment execution department's page, clicking the "Execute" button automatically calls the accounting transaction interface of the internal processing components, obtains the adjustment data of the adjustment transaction, and saves it in the error form.

[0075] In some embodiments, when the M1 processing components are not in the same system as the consistency platform, after the M1 processing components complete the reconciliation, the reconciliation time and global event tracking number of one or more reconciliation data entries need to be entered on the error adjustment execution page. Further, the consistency platform establishes a matching mapping relationship between transaction record data and reconciliation data, and performs account matching based on this mapping relationship.

[0076] 204. When it is determined that the account information of the adjustment data and the transaction record data match, the adjustment data and transaction record data will be displayed on the user interface.

[0077] In some embodiments, at least one adjustment data point generated during the adjustment of multi-party transactions by M1 processing components over N adjustment cycles is retrieved from a designated storage space. The accounting information in the at least one adjustment data point matches the accounting information in the transaction record data, thereby determining whether the transaction corresponding to the error order has been balanced. Specifically, the debit and credit amounts can be determined based on the transaction amounts in the adjustment data and the transaction record data. When the debit amount matches the credit amount, it is determined that the accounting information in the adjustment data and the transaction record data has successfully matched, thus determining that the transaction corresponding to the error order has been balanced.

[0078] In some embodiments, the "Schedule Matching" function can be manually triggered on the error adjustment and inspection page to activate the external system account adjustment matching function and display the matching results on the user interface.

[0079] In some embodiments, the error report also includes a matching status, which can be either a successful match, a failed match, or a no-match. Before performing a matching operation on the account information in at least one adjustment data point and the account information in the transaction record data, the error report's matching status is "no-match." When the account information in at least one adjustment data point matches the account information in the transaction record data, the error report's matching status is "successful match." Furthermore, at least one adjustment data point and the transaction record data can be displayed on the user interface. In some scenarios, the matching status can also be displayed on the user interface.

[0080] 205. In response to the user's action on the user interface, the error check process ends.

[0081] In some embodiments, the operation instructs the user to complete the reconciliation of the adjustment data and the transaction record data. In some scenarios, the user can view the transaction record data and adjustment data of the error order through the display interface. When the user clicks to complete the reconciliation of the adjustment data and the transaction record data, the reconciliation process of the error order ends.

[0082] Based on the above scheme, by matching the accounting information obtained from the adjustment scheme with the transaction record data in the error report, and then determining the matching result, the correctness and completeness of the adjustment can be guaranteed, and the accuracy of error report processing can be increased.

[0083] In some embodiments, when the accounting information in at least one adjustment data point does not match the accounting information in the transaction record data, the matching status of the error report is "match failed". The error report also includes a matching timestamp and a matching count. When it is determined that the transaction record data does not match the accounting information of at least one adjustment data point, the matching timestamp and matching count corresponding to the error report are updated. For example, when the matching timestamp corresponding to the error report is determined to be February 10, 2022, 13:20:04, and the matching count is 1, when it is determined that the accounting information of at least one adjustment data point does not match the transaction record data, the matching timestamp can be updated to February 13, 2022, 10:46:50, and the matching count can be updated to 2 based on the current time.

[0084] In some embodiments, when a processing component involves multiple processing systems, if the system where the consistency platform resides (this system) and an external system simultaneously perform adjustments, the adjustment data from the external system may not be immediately sent to the error report of the consistency platform, or all adjustment data may not be sent at once. Therefore, adjustments may fail to be completed, leading to a mismatch between the adjustment data and the transaction record data. Taking the first processing component as an example, when the first processing component needs to perform multiple adjustments for multi-party transactions, the adjustments may not be completed immediately, or they may be processed in batches at different times. For example, if the first processing component needs to perform three adjustments for multi-party transactions, it may execute three adjustment transactions after receiving the instruction information. Alternatively, after receiving the instruction information, it may execute one adjustment transaction on the same day it receives the instruction information and send the adjustment data corresponding to that transaction. On the second day, the adjustment transaction corresponding to that multi-party transaction may not be executed. On the third day, the remaining two adjustment transactions are executed, and the adjustment data corresponding to those two transactions is sent.

[0085] In some scenarios, the error order also includes the error order creation time. When it is determined that the account information of the adjustment data and the transaction record data fails to match, the error order's matching status is "match failed". When the error order's matching status is "match failed", and the error order meets the first condition at a set time, at least one adjustment data generated by M1 processing components during the adjustment of multi-party transactions sent in K adjustment cycles is retrieved from the set storage space. Here, K adjustment cycles refer to the adjustment cycles between N adjustment cycles and the set time. The first condition includes the time interval between the error order creation time and the set time exceeding a first set duration, the time interval between the matching timestamp and the set time being greater than the matching cycle, and the number of matches being less than a first threshold. As an example, the first condition can be expressed as the time interval between the error order creation time and the set time being greater than 6 days, the time interval between the matching timestamp and the set time being greater than 1 day, and the number of matches being less than 3. The first set duration, matching cycle, and first threshold can also be set to other durations or values, which are not specifically limited in this application. Furthermore, at least one adjustment data point generated by the M1 processing components during the adjustment of multi-party transactions can be retrieved from the designated storage space. In some embodiments, the M1 processing components periodically send adjustment data corresponding to multi-party transactions until all error order adjustment transactions corresponding to the identification information in the indication information are executed.

[0086] Furthermore, the transaction record data can be matched with at least one adjustment data point generated during N adjustment cycles and K adjustment cycles for multi-party transactions to obtain a matching result. The matching status of the error order is then updated based on the matching result. In some scenarios, after updating the matching status, the matching timestamp and matching count of the error order can also be updated.

[0087] In some embodiments, when it is determined that the second error order is not included in the error registration table at the second set time and the creation time of the second error order is greater than the third set duration, the second error order is saved to the error registration table. The second error order includes the second transaction record data of the second multi-party transaction. Further, at least one global event tracking number and the adjustment time corresponding to each global event tracking number can be obtained from the second error order; wherein, at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the second error order are those generated and added to the error registration table by the identification information of the second error order when the adjustment operation is triggered. In some scenarios, at least one adjustment data corresponding to the second error order can be obtained from the set storage space based on at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the second error order, generated when the processing component corresponding to the second error order performs adjustments for the second multi-party transaction during N1 adjustment cycles. The matching result of the second error order is obtained by matching the account information of the second transaction record data with the at least one adjustment data corresponding to the second error order. The matching status of the second error order is updated based on its matching result, along with its matching timestamp and matching count. For example, if the second error order's matching result is a mismatch, its matching status can be set to "Match Failed," its matching timestamp updated to reflect the current time, and its matching count set to 1.

[0088] This application provides a data processing apparatus; please refer to... Figure 3 The device 300 can perform each step of the above data processing method, which will not be described in detail here to avoid repetition. The device 300 includes an acquisition module 301, a transmission module 302, a display module 303, and a processing module 304.

[0089] The acquisition module 301 is used to acquire transaction record data for errors in multi-party transactions. The transaction record data includes record data generated by at least one of the M processing components that perform processing for the multi-party transactions in the multi-party transaction processing system.

[0090] The sending module 302 is used to send instruction information to M1 of the M processing components, wherein the M1 processing component is the processing component among the M processing components that did not generate record data during the processing of the multi-party transaction, and the instruction information is used to instruct the M1 processing component to adjust the accounts according to the transaction record data of the multi-party transaction;

[0091] The acquisition module 301 is also used to acquire the adjustment data generated when the M1 processing components perform the adjustment;

[0092] The display module 303 is used to display the adjustment data and the transaction record data on the user interface when it is determined that the account information of the adjustment data and the transaction record data are successfully matched.

[0093] The processing module 304 is used to respond to an operation performed by the user on the user interface, wherein the operation instructs the user to complete the verification of the adjustment data and the transaction record data, and then ends the verification process of the error order.

[0094] In some embodiments, the transaction record data includes the identifier of at least one of the M processing components and the account information recorded by the at least one processing component for processing multi-party transactions. The account information includes transaction amount and transaction account information. When sending instruction information to M1 of the M processing components, the sending module 302 is specifically used to: determine the M1 processing components among the M processing components that need to adjust the transaction record data based on the account information recorded by the at least one processing component for processing multi-party transactions; if the identifier information of any of the M1 processing components is not included in the transaction record data or the account information corresponding to any of the processing components is incomplete; and send instruction information to the M1 processing components.

[0095] In some embodiments, the acquisition module 301, when acquiring the adjustment data generated when the M1 processing components perform adjustment, is specifically used to: acquire the adjustment data periodically sent by the M1 processing components and store it in a set storage space, wherein the set storage space stores at least one adjustment data generated by the M1 processing components when performing adjustment for the multi-party transaction in N adjustment cycles; N is a positive integer;

[0096] The processing module 304, when determining that the account information of the adjustment data and the transaction record data matches, is specifically used to: obtain at least one adjustment data generated by the M1 processing components during the N adjustment cycles for the multi-party transaction from the set storage space, and determine that the account information in the at least one adjustment data matches the account information in the transaction record data.

[0097] In one possible implementation, the processing module 304 is further configured to: add an error order for the multi-party transaction to the error registration table before sending the instruction information to M1 of the M processing components; the error order includes transaction record data of the multi-party transaction; wherein the instruction information includes the identification information of the error order.

[0098] The adjustment data of a processing component includes the adjustment time when the processing component performs the adjustment operation, the global event tracking number of the operation, and the adjustment record generated by the operation. The global event tracking number is the operation identifier generated by the processing component when it performs the adjustment operation.

[0099] The acquisition module 301, when acquiring at least one adjustment data generated by the M1 processing component during N adjustment cycles for adjusting the multi-party transactions from the designated storage space, specifically performs the following: acquiring at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the error order; wherein, the at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the error order are generated when at least one processing component in the M1 processing component triggers the execution of the adjustment operation and added to the error order in the error registration table as indicated by the error order identification information; and acquiring at least one adjustment data generated by the M1 processing component during N adjustment cycles for adjusting the multi-party transactions from the designated storage space based on the at least one global event tracking number and the adjustment time corresponding to each global event tracking number.

[0100] In some embodiments, the error slip also includes a matching status, which can be a successful match, a failed match, or a no-match; when the account information in the at least one adjustment data matches the account information in the transaction record data, the matching status of the error slip is a successful match; or; when the account information in the at least one adjustment data does not match the account information in the transaction record data, the matching status of the error slip is a failed match; or, before performing a matching operation on the account information in the at least one adjustment data and the account information in the transaction record data, the matching status of the error slip is a no-match.

[0101] In some embodiments, the error slip also includes a matching timestamp and a matching count, and the processing module 304 is further configured to: update the matching timestamp and matching count corresponding to the error slip when it is determined that the transaction record data does not match the account information of the adjustment data.

[0102] In some embodiments, the error order also includes the creation time of the error order. The processing module 304, when determining that the account information matching between the adjustment data and the transaction record data fails, is further configured to: when the error order meets a first condition at a set time, retrieve at least one adjustment data generated by the M1 processing components during K adjustment cycles for adjusting the accounts of the multi-party transaction from the set storage space, where the K adjustment cycles are the adjustment cycles between the N adjustment cycles and the set time; match the transaction record data with the at least one adjustment data generated during the N adjustment cycles and the at least one adjustment data generated during the K adjustment cycles for adjusting the accounts of the multi-party transaction to obtain a matching result, and update the matching status of the error order according to the matching result; wherein, the first condition includes the time interval between the creation time of the error order and the set time being greater than a first set duration, the time interval between the matching timestamp and the set time being greater than the matching cycle, and the number of matching times being less than a first threshold.

[0103] In some embodiments, the processing module 304 is further configured to: when it is determined that the error registration table does not include a second error order at a second set time and the creation time of the second error order is greater than a third set time, save the second error order to the error registration table, wherein the second error order includes the second transaction record data of the second multi-party transaction; the acquisition module 301 is further configured to acquire at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the second error order; wherein, at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the second error order are generated and added to the error registration table when at least one adjustment operation is triggered for the second error order. The error message indicates the error message in the second error message; based on at least one global event tracking number in the second error message and the adjustment time corresponding to each global event tracking number, at least one adjustment data corresponding to the second error message is obtained from the set storage space when the processing component corresponding to the second error message sends an adjustment for the second multi-party transaction in N1 adjustment cycles; the processing module 304 is further configured to match the account information of the second transaction record data with the at least one adjustment data corresponding to the second error message to obtain the matching result of the second error message; update the matching status of the second error message according to the matching result of the second error message, and update the matching timestamp and matching number of the second error message.

[0104] Based on the same inventive concept, this application provides an electronic device that can realize the functions of the data processing device described above. Please refer to... Figure 4The device includes a memory 401 and a processor 402.

[0105] The memory 401 is used to store program instructions;

[0106] The processor 402 is used to call the program instructions stored in the memory and execute the above data processing method according to the obtained program.

[0107] In the embodiments of this application, the processor 402 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, capable of implementing or executing the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0108] Memory 401, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory 401 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic storage, magnetic disk, optical disk, etc. Memory 401 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. In the embodiments of this application, memory 401 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0109] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium, which includes computer program code. When the computer program code is executed on a computer, it causes the computer to perform any of the data processing methods described above. Since the principle by which the computer-readable storage medium solves the problem is similar to that of the data processing method, the implementation of the computer-readable storage medium can be referred to the implementation of the method, and repeated details will not be repeated.

[0110] Based on the same inventive concept, this application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to execute any of the data processing methods described above. Since the principle by which the above computer program product solves the problem is similar to that of the data processing method, the implementation of the above computer program product can be referred to the implementation of the method, and repeated details will not be described again.

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

[0112] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0113] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0114] 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 one or more flowcharts and / or one or more block diagrams.

[0115] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A data processing method, characterized in that, include: Obtain transaction record data for errors in multi-party transactions, wherein the transaction record data includes record data generated by at least one of the M processing components that perform processing on the multi-party transactions in the multi-party transaction processing system; Add the error report for the multi-party transaction to the error registration form. The error report includes the transaction record data and the identification information of the error report. Instruction information is sent to M1 of the M processing components, where M1 is the processing component that did not generate record data during the processing of the multi-party transaction due to the lack of accounting. The instruction information includes the identification information of the error order, which instructs the M1 processing components to obtain transaction record data from the error order indicated by the identification information for reconciliation. After performing the reconciliation operation, the M1 processing components add the global event tracking number of at least one reconciliation data and the reconciliation time corresponding to each global event tracking number to the error order indicated by the identification information in the error registration table. The global event tracking number is an operation identifier generated by the processing component when performing the reconciliation operation. Based on at least one global event tracking number in the error report and the adjustment time corresponding to each global event tracking number, obtain the adjustment data generated when the M1 processing components perform the adjustment. When it is determined that the account information of the adjustment data and the transaction record data are successfully matched, the matching status of the error order is set to the matching success status, and the adjustment data and the transaction record data are displayed on the user interface; In response to an action performed by the user on the user interface, which instructs the user to complete the reconciliation of the adjustment data and the transaction record data, the reconciliation process of the error slip ends.

2. The method as described in claim 1, characterized in that, The transaction record data includes the identifier of at least one of the M processing components, and the account information recorded by the at least one processing component for processing multiple transactions. The account information includes the transaction amount and transaction account information. Sending instruction information to M1 of the M processing components includes: Based on the account information recorded by the at least one processing component for processing multiple transactions, determine M1 processing components among the M processing components that need to adjust the transaction record data; the identification information of any processing component in the M1 processing components is not included in the transaction record data or the account information corresponding to any processing component is incomplete; Send instruction information to the M1 processing components.

3. The method as described in claim 2, characterized in that, The process of obtaining the adjustment data generated when the M1 processing components perform adjustment includes: The adjustment data periodically sent by the M1 processing components is obtained and stored in a set storage space. The set storage space stores at least one adjustment data generated by the M1 processing components when adjusting the accounts for the multi-party transactions during N adjustment cycles; N is a positive integer. Determining that the account information of the adjustment data and the transaction record data matches includes: Obtain at least one adjustment data point generated by the M1 processing components during N adjustment cycles for the multi-party transactions from the designated storage space, and determine that the account information in the at least one adjustment data point matches the account information in the transaction record data.

4. The method as described in claim 3, characterized in that, The reconciliation data of a processing component includes the reconciliation time when the processing component performs the reconciliation operation, the global event trace number of the operation, and the reconciliation record generated by the operation. At least one reconciliation data point generated by the M1 processing component during N reconciliation cycles for the multi-party transactions is retrieved from the designated storage space, including: Obtain at least one global event tracking number and the corresponding adjustment time for each global event tracking number from the error report; Based on the at least one global event tracking number and the adjustment time corresponding to each global event tracking number, at least one adjustment data generated by the M1 processing component during the adjustment of the multi-party transaction in N adjustment cycles is obtained from the set storage space.

5. The method as described in claim 4, characterized in that, The matching status of the error order also includes matching failure and no match; When the account information in at least one of the adjustment data does not match the account information in the transaction record data, the matching status of the error order is "matching failed"; or, Before performing a matching operation between the account information in at least one adjustment data point and the account information in the transaction record data, the matching status of the error order is unmatched.

6. The method as described in claim 5, characterized in that, The error report also includes a matching timestamp and the number of matches, and the method further includes: When it is determined that the transaction record data does not match the account information of the adjustment data, the matching timestamp and the number of matching times corresponding to the error order are updated.

7. The method according to any one of claims 1-6, characterized in that, The error report also includes the time the error report was created. When it is determined that the account information of the adjustment data and the transaction record data fails to match, the method further includes: When the error order at the set time meets the first condition, at least one adjustment data generated by the M1 processing components during the adjustment of the multi-party transaction sent in the K adjustment cycles is obtained from the set storage space. The K adjustment cycles are the adjustment cycles between the N adjustment cycles and the set time. The transaction record data is matched with at least one adjustment data generated during the N adjustment cycles and the K adjustment cycles for the multi-party transactions to obtain a matching result, and the matching status of the error order is updated according to the matching result. The first condition includes the time interval between the creation time of the error order and the set time being greater than a first set duration, the time interval between the matching timestamp and the set time being greater than the matching period, and the number of matching times being less than a first threshold.

8. The method as described in claim 1, characterized in that, The method further includes: When it is determined that the error registration table at the second set time does not include the second error order and the creation time of the second error order is greater than the third set time, the second error order is saved to the error registration table. The second error order includes the second transaction record data of the second multi-party transaction. Obtain at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the second error order; wherein, at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the second error order are generated when the second error order triggers the execution of the adjustment operation and added to the error order in the error registration table as indicated by the identification information of the second error order; Based on at least one global event tracking number in the second error order and the adjustment time corresponding to each global event tracking number, at least one adjustment data corresponding to the second error order is obtained from the set storage space when the processing component corresponding to the second error order sends the adjustment data for the second multi-party transaction in N1 adjustment cycles. The matching result of the second error order is obtained by matching the second transaction record data with the account information of at least one adjustment data corresponding to the second error order. Update the matching status of the second error order based on the matching result of the second error order, and update the matching timestamp and matching count of the second error order.

9. A data processing apparatus, characterized in that, include: The acquisition module is used to acquire transaction record data for errors in multi-party transactions. The transaction record data includes record data generated by at least one of the M processing components that perform processing on the multi-party transactions in the multi-party transaction processing system. The processing module is used to add the error order of the multi-party transaction to the error registration table. The error order includes the transaction record data and the identification information of the error order. A sending module is used to send instruction information to M1 of the M processing components. The M1 processing component is the processing component among the M processing components that has not generated record data during the processing of the multi-party transaction without accounting. The instruction information includes the identification information of the error order, which is used to instruct the M1 processing components to obtain transaction record data from the error order indicated by the identification information and to perform reconciliation. After performing the reconciliation operation, the M1 processing components add the global event tracking number of at least one reconciliation data and the reconciliation time corresponding to each global event tracking number to the error order indicated by the identification information in the error registration table. The global event tracking number is an operation identifier generated by the processing component when performing the reconciliation operation. The acquisition module is also used to acquire the adjustment data generated when the M1 processing components perform the adjustment based on at least one global event tracking number in the error order and the adjustment time corresponding to each global event tracking number; The display module is used to set the matching status of the error order to a successful match status and display the adjustment data and the transaction record data on the user interface when it is determined that the account information of the adjustment data and the transaction record data are successfully matched. The processing module is used to respond to an operation performed by the user on the user interface, wherein the operation instructs the user to complete the verification of the adjustment data and the transaction record data, and then ends the verification process of the error order.

10. The apparatus as claimed in claim 9, characterized in that, The transaction record data includes the identifier of at least one of the M processing components, and the account information recorded by the at least one processing component for processing multi-party transactions. The account information includes the transaction amount and transaction account information. When the sending module sends instruction information to M1 of the M processing components, it is specifically used for: Based on the account information recorded by the at least one processing component for processing multiple transactions, determine M1 processing components among the M processing components that need to adjust the transaction record data; the identification information of any processing component in the M1 processing components is not included in the transaction record data or the account information corresponding to any processing component is incomplete; Send instruction information to the M1 processing components.

11. The apparatus as claimed in claim 10, characterized in that, The acquisition module, when acquiring the adjustment data generated by the M1 processing components during the adjustment process, is specifically used for: The adjustment data periodically sent by the M1 processing components is obtained and stored in a set storage space. The set storage space stores at least one adjustment data generated by the M1 processing components when adjusting the accounts for the multi-party transactions during N adjustment cycles; N is a positive integer. The processing module, when determining that the account information of the adjustment data and the transaction record data matches, is specifically used for: Obtain at least one adjustment data point generated by the M1 processing components during N adjustment cycles for the multi-party transactions from the designated storage space, and determine that the account information in the at least one adjustment data point matches the account information in the transaction record data.

12. The apparatus as claimed in claim 11, characterized in that, The reconciliation data of a processing component includes the reconciliation time when the processing component performs the reconciliation operation, the global event tracking number of the operation, and the reconciliation record generated by the operation. The acquisition module, when acquiring at least one reconciliation data point generated by the M1 processing component during N reconciliation cycles for the multi-party transaction from the designated storage space, is specifically used for: Obtain at least one global event tracking number and the corresponding adjustment time for each global event tracking number from the error report; Based on the at least one global event tracking number and the adjustment time corresponding to each global event tracking number, at least one adjustment data generated by the M1 processing component during the adjustment of the multi-party transaction in N adjustment cycles is obtained from the set storage space.

13. The apparatus as claimed in claim 12, characterized in that, The matching status of the error order is either match failure or no match; When the account information in at least one of the adjustment data does not match the account information in the transaction record data, the matching status of the error order is "matching failed"; or, Before performing a matching operation between the account information in at least one adjustment data point and the account information in the transaction record data, the matching status of the error order is unmatched.

14. The apparatus as claimed in claim 13, characterized in that, The error report also includes a matching timestamp and the number of matches; the processing module is further used for: When it is determined that the transaction record data does not match the account information of the adjustment data, the matching timestamp and the number of matching times corresponding to the error order are updated.

15. The apparatus according to any one of claims 9-14, characterized in that, The error report also includes the creation time of the error report. When the processing module determines that the account information of the adjustment data and the transaction record data fails to match, it is further configured to: When the error order at the set time meets the first condition, at least one adjustment data generated by the M1 processing components during the adjustment of the multi-party transaction sent in the K adjustment cycles is obtained from the set storage space. The K adjustment cycles are the adjustment cycles between the N adjustment cycles and the set time. The transaction record data is matched with at least one adjustment data generated during the N adjustment cycles and the K adjustment cycles for the multi-party transactions to obtain a matching result, and the matching status of the error order is updated according to the matching result. The first condition includes the time interval between the creation time of the error order and the set time being greater than a first set duration, the time interval between the matching timestamp and the set time being greater than the matching period, and the number of matching times being less than a first threshold.

16. The apparatus as claimed in claim 9, characterized in that, The processing module is also used for: When it is determined that the error registration table at the second set time does not include the second error order and the creation time of the second error order is greater than the third set time, the second error order is saved to the error registration table. The second error order includes the second transaction record data of the second multi-party transaction. The acquisition module is further configured to acquire at least one global event tracking number and the adjustment time corresponding to each global event tracking number from the second error order; wherein, at least one global event tracking number and the adjustment time corresponding to each global event tracking number in the second error order are generated and added to the error order indicated by the identification information of the second error order in the error registration table when the second error order triggers the execution of the adjustment operation; Based on at least one global event tracking number in the second error order and the adjustment time corresponding to each global event tracking number, at least one adjustment data corresponding to the second error order is obtained from the set storage space when the processing component corresponding to the second error order sends the adjustment data for the second multi-party transaction in N1 adjustment cycles. The processing module is further configured to match the second transaction record data with the account information of at least one adjustment data corresponding to the second error order to obtain the matching result of the second error order; Update the matching status of the second error order based on the matching result of the second error order, and update the matching timestamp and matching count of the second error order.

17. An electronic device, characterized in that, include: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the steps of the method according to any one of claims 1-8.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a computer, cause the computer to perform the method as described in any one of claims 1-8.

19. A computer program product, characterized in that, The computer program product includes: computer program code, which, when run on a computer, causes the computer to perform the method described in any one of claims 1-8.

Images