An error single processing method, device, equipment and medium

Abstract

The application relates to the technical field of data processing, in particular to an error single processing method and device, equipment and medium, which are used for solving the problems of low processing efficiency and low accuracy caused by manual processing of error singles. The method comprises the following steps: obtaining a plurality of target details generated on a set date from an accounting engine component, and obtaining error singles generated before the set date from each accounting component; wherein the target details are details with the same to-be-settlement detail identifier and successful consistency check; the to-be-settlement detail identifier is an identifier of details with failed transaction consistency check before the set date; the error singles comprise a plurality of error details; comparing the identifiers of the plurality of target details with the identifiers of the error details in the error singles, and determining at least one target error single from the error singles according to the comparison result; and processing each target error single based on the obtained plurality of target details.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to an error order processing method, apparatus, device, and medium. Background Technology

[0002] The same transaction may be recorded in multiple accounting components, and then the accounting information is aggregated for end-of-day reconciliation. Due to inconsistencies in daily cutoff and data supply times between different components, accounting data may be split into different end-of-day batches for reconciliation (e.g., the same transaction data may be distributed across day T and day T+1 batches). For a single end-of-day batch, the accounting for this transaction is incomplete, resulting in accounting discrepancies, i.e., false discrepancies, and consequently, error reports. Cross-system transaction discrepancies contain a large amount of false discrepancy details, which require manual verification and processing, leading to low efficiency and difficulty in ensuring accuracy. Summary of the Invention

[0003] This application provides a method, apparatus, device, and medium for processing error orders, which addresses the problems of low processing efficiency and low accuracy caused by manual processing of error orders.

[0004] In a first aspect, embodiments of this application provide an error order processing method, the method comprising:

[0005] The system retrieves multiple target details generated on a set date from the accounting engine component, and retrieves error reports generated before the set date from each accounting component; wherein, the target details are details with the same identifier as the details to be settled and whose consistency verification is successful, the details to be settled are identifiers of details whose transaction consistency verification failed before the set date, and the error reports include multiple error details;

[0006] The identifiers of the multiple target details are compared with the identifiers of the error details in the error order, and at least one target error order is determined from the error orders based on the comparison results;

[0007] For each target error order, each target error order is processed based on the obtained target details.

[0008] Based on the above scheme, this application obtains the target details for a set date and identifies at least one target error order among the error orders generated before the set date by the identifier of the target details. Then, it processes each target error order based on multiple target details, which can automatically identify error orders and realize automatic processing of error orders, improve the processing efficiency of multiple error orders, and achieve high accuracy.

[0009] In one possible implementation, processing each target error order based on obtaining the plurality of target details includes:

[0010] Determine the total number of error details in each target error order, and the number of target error details corresponding to each target error order, wherein the number of target error details is the number of error details in the target error order that have the same identifier as the target detail;

[0011] Match the total number of error details with the target number of error details;

[0012] The target error order is processed based on the matching results.

[0013] Based on the above scheme, this application calculates the total number of error details in the target error order and the target error detail number, matches the total number and the target error detail number, and then processes the target error order in different ways based on the matching results.

[0014] In one possible implementation, processing the target error order based on the matching result includes:

[0015] If the matching result is that the total number of error details is equal to the target number of error details, then the status of each error detail in the target error order is changed to the processed status, and the target error order is closed.

[0016] If the matching result shows that the total number of error details is greater than the target number of error details, then the target error order is modified based on the multiple target details.

[0017] Using the above scheme, when the total number of error details is equal to the target number of minor error details, the order can be directly closed. When the total number of error details is not equal to the target number of error details, the target error details can be modified.

[0018] In one possible implementation, modifying the target error form based on the plurality of target details includes:

[0019] Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer;

[0020] A new error order is created based on the error details in the target error order other than the N target error details, and the target error order is closed.

[0021] Set the status of each error detail in the new error report to pending processing.

[0022] Based on the above scheme, this application can create a new error record by using error details other than the target error details, that is, create a new error record for the details of the consistency check failure, and thus realize the processing of error records.

[0023] In one possible implementation, processing the target error order based on the plurality of target details includes:

[0024] Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer;

[0025] The status of N target error details in the target error order is modified to the processed status, and a new number of target error details is determined based on at least one error detail in the pending status of the error order.

[0026] Based on the above scheme, this application can modify the status of the target error details, thereby realizing the processing of the target error details in the error report.

[0027] In one possible implementation, comparing the identifiers of the plurality of target details with the identifiers of the error details in the error report includes:

[0028] Identify M error details in the error log that are in a pending state, where M is a positive integer;

[0029] For any one of the M error details, the identifier of the error detail is compared with the identifiers of the plurality of target details.

[0030] Based on the above scheme, before comparison, this application needs to determine the status of the error details in the error report, and then compare the identifier of the error details that need to be processed with the identifier of the target details, which can save comparison time and improve processing efficiency.

[0031] In one possible implementation, determining at least one target error document from the error documents based on the comparison result includes:

[0032] For each error order, if the comparison result shows that the identifier of at least one error detail in the error order is the same as the identifier of the target detail, then the error order is taken as the target error order.

[0033] Secondly, this application provides an error order processing apparatus, the apparatus comprising:

[0034] The acquisition module is used to acquire multiple target details generated on a set date from the accounting engine component, and to acquire error reports generated before the set date from each accounting component; wherein, the target details are details with the same identifier as the details to be reconciled and whose consistency verification is successful, the details to be reconciled identifier is the identifier of the details whose transaction consistency verification failed before the set date, and the error report includes multiple error details;

[0035] The processing module is used to compare the identifiers of the plurality of target details with the identifiers of the error details in the error order, and determine at least one target error order from the error orders based on the comparison results; for each target error order, the module processes each target error order based on the obtained plurality of target details.

[0036] In one possible implementation, the processing module, when processing each target error order based on the acquired target details, is specifically used for:

[0037] Determine the total number of error details in each target error order, and the number of target error details corresponding to each target error order, wherein the number of target error details is the number of error details in the target error order that have the same identifier as the target detail;

[0038] Match the total number of error details with the target number of error details;

[0039] The target error order is processed based on the matching results.

[0040] In one possible implementation, the processing module, when processing the target error record based on the matching result, is specifically used for:

[0041] If the matching result is that the total number of error details is equal to the target number of error details, then the status of each error detail in the target error order is changed to the processed status, and the target error order is closed.

[0042] If the matching result shows that the total number of error details is greater than the target number of error details, then the target error order is modified based on the multiple target details.

[0043] In one possible implementation, when the processing module modifies the target error form based on the plurality of target details, it is specifically used for:

[0044] Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer;

[0045] A new error order is created based on the error details in the target error order other than the N target error details, and the target error order is closed.

[0046] Set the status of each error detail in the new error report to pending processing.

[0047] In one possible implementation, when the processing module modifies the target error form based on the plurality of target details, it is specifically used for:

[0048] Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer;

[0049] The status of N target error details in the target error order is modified to the processed status, and a new number of target error details is determined based on at least one error detail in the pending status of the error order.

[0050] In one possible implementation, the processing module, when comparing the identifiers of the plurality of target details with the identifiers of the error details in the error report, specifically performs the following:

[0051] Identify M error details in the error log that are in a pending state, where M is a positive integer;

[0052] For any one of the M error details, the identifier of the error detail is compared with the identifiers of the plurality of target details.

[0053] In one possible implementation, when the processing module determines at least one target error document from the error documents based on the comparison results, it is specifically configured to:

[0054] For each error order, if the comparison result shows that the identifier of at least one error detail in the error order is the same as the identifier of the target detail, then the error order is taken as the target error order.

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

[0056] Memory, used to store program instructions;

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

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

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

[0060] 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

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

[0062] Figure 1 A flowchart illustrating an error order processing method provided in this application embodiment;

[0063] Figure 2 A schematic diagram illustrating an error order modification method provided in an embodiment of this application;

[0064] Figure 3 A schematic diagram illustrating another error order modification method provided in this application embodiment;

[0065] Figure 4 A flowchart for error order processing is provided in an embodiment of this application;

[0066] Figure 5 A schematic diagram of an error order processing device provided in an embodiment of this application;

[0067] Figure 6 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

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

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

[0070] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. It should be noted that in the embodiments of this application, certain existing industry solutions such as software, components, and models may be mentioned. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solutions of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0071] The acquisition, transmission, storage, and use of data in this application all comply with the requirements of relevant national laws and regulations.

[0072] To better understand the error report processing method proposed in this application, the technical terms involved in this application are explained below.

[0073] Consistency verification: When a process or a group of processes with business consistency requirements are implemented in multiple applications or application components, a certain method is used to check whether the process group was actually successfully executed together after the process group ends.

[0074] Error details: Data errors that occur during the transaction process due to non-compliance with transaction inconsistencies, such as discrepancies between debits and credits or between totals and totals.

[0075] Error Request: An error request is a processing order created for accounting data that does not meet the consistency requirements of transactions and results in errors. It is a collection of erroneous accounting data that is categorized and processed.

[0076] Order creation: Receive and process error details, and assign error processing orders to the primary responsible component through automatic order creation via system batch processing or manual order creation by the processing order service staff.

[0077] Cross-system transaction discrepancies: Due to system design flaws, system crashes, or human error, some components fail to record transactions successfully, while other components record transactions successfully. This results in the transaction's accounting entries not being fully offset, creating a one-sided accounting situation.

[0078] False Imbalance Across Systems: The same transaction is recorded in multiple accounting components and then aggregated in the accounting engine system for end-of-day reconciliation. Due to inconsistencies in daily cutoff and data supply times between components, accounting data may be split across different batches of the accounting engine's end-of-day batch for reconciliation (data distributed across the T-day batch and the T+1-day batch). For a single end-of-day batch, the accounting for this transaction is incomplete, resulting in an imbalance. However, when the data from multiple end-of-day batches are viewed together, the accounting for this transaction appears complete and balanced; therefore, this type of imbalance is called a false imbalance.

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

[0080] The same transaction may be recorded in multiple accounting components, and then the accounting information is aggregated for end-of-day reconciliation. Due to inconsistencies in daily cutoff and data supply times between different components, accounting data may be split into different end-of-day batches for reconciliation (e.g., the same transaction data may be distributed across day T and day T+1 batches). For a single end-of-day batch, the accounting for this transaction is incomplete, resulting in accounting discrepancies, i.e., false discrepancies, and consequently, error reports. Cross-system transaction discrepancies contain a large amount of false discrepancy details, which require manual verification and processing, leading to low efficiency and difficulty in ensuring accuracy.

[0081] To address the aforementioned problems, this application provides a method, apparatus, and device for processing error orders. The method involves obtaining multiple target details generated on a set date from an accounting engine component, and obtaining error orders generated before the set date from various accounting components. The method compares the identifiers of the multiple target details with the identifiers of the error details in the error orders, and determines at least one target error order from the error orders based on the comparison result. Each target error order is then processed. The processing methods include closing or splitting orders, with the specific method determined based on a comparison between the number of target error details in the target error order and the total number of error details in the target error order. This method enables automated identification of error orders, thereby achieving automated processing of error orders, improving the processing efficiency of multiple error orders, and achieving high accuracy.

[0082] This application provides an error order processing method, see [link to relevant documentation]. Figure 1 As shown, the specific process of this method is as follows:

[0083] Step S101: Obtain multiple target details generated on a set date from the accounting engine component, and obtain error reports generated before the set date from each accounting component.

[0084] Among them, the target details are the details with the same identifier as the details to be settled and whose consistency has been successfully verified. The identifier of the details to be settled is the identifier of the details whose transaction consistency verification failed before the set date. The error report includes multiple error details.

[0085] In some embodiments, since a transaction corresponding to the same identifier may be recorded by multiple accounting components, and the daily cut-off times of different accounting components are different, it is possible that some accounting components will successfully record the transaction on the day the transaction is initiated, while others will only successfully record it on the second day after the transaction is initiated. Therefore, on the day of the transaction, because the other accounting components failed to record the transaction, the transaction consistency check fails, and an error order is created based on the transaction details of the primary responsible component where the consistency check failed. In some scenarios, after another accounting component successfully records the transaction on the second day after the transaction is initiated, the consistency check between the details generated by the other accounting component and the details generated by the components at the time of the transaction initiation fails. In this application, the details generated on the day the transaction is initiated are called pending balance details, and the target details are the details generated on the second day after the transaction is initiated. In some embodiments, when the details of multiple accounting components correspond to the same identifier, the multiple details can be filtered and deduplicated, with each identifier corresponding to only one detail. Specifically, you can select the details generated by the accounting component with the earliest accounting time based on the accounting time, or select the details of the accounting component with the earliest transaction based on the transaction rules.

[0086] In some embodiments, the detail identifier can be a set number or a serial number.

[0087] Step S102: Compare the identifiers of multiple target details with the identifiers of error details in the error report, and determine at least one target error report from the error reports based on the comparison results.

[0088] In some embodiments, M error details in an error order can be identified as being in a pending state. For any one of these M error details, its identifier is compared with the identifiers of multiple target details. Here, M is a positive integer. As an example, an error order may contain S error details, where M are in a pending state and S are in a processed state. Then, the identifier of each of the M error details is compared with the identifiers of multiple target details.

[0089] Furthermore, for each error order, if the comparison result shows that the identifier of at least one error detail in the error order is the same as the identifier of the target detail, the error order is designated as the target error order. Here, the error detail refers to the error detail in the pending processing state. For example, if the identifier of at least one error detail in an error order is the same as the identifier of the target detail, then that error order is designated as the target error order. For instance, if the identifier of error detail A1 in an error order is L1, the identifier of error detail A2 is L2, the identifier of target detail C1 is L1, and the identifier of target detail C2 is L2, then the identifiers of error details A1 and A2 in the error order are the same as the identifiers of target details C1 and C2, respectively, and therefore that error order is designated as the target error order.

[0090] Step S103: For each target error order, process each target error order based on obtaining multiple target details.

[0091] In some embodiments, processing each target error order based on obtaining multiple target details can be achieved in the following ways:

[0092] Determine the total number of error details in each target error order, and the target error detail number corresponding to each target error order. The target error detail number is the number of error details in the target error order that have the same identifier as the target detail. Further, match the total number of error details with the target error detail number; then process the target error order based on the matching result.

[0093] In some embodiments, processing the target error order based on the matching results can be achieved in the following ways:

[0094] In some scenarios, if the total number of error details matches the target number of error details, the status of each error detail in the target error order is changed to "processed," and the target error order is closed. For example, if the total number of error details in the target error order is 10, and the target error order itself is also 10, then it's confirmed that each error detail in the target error order has been successfully verified. Therefore, the status of each error detail can be changed to "processed," and the target error order can be closed.

[0095] In other scenarios, if the total number of error details in the matching result is greater than the target number of error details, then the target error order is modified based on multiple target details. For example, if the total number of error details in the target error order is 10 and the target number of error details is 6, then in step S403 it can be determined that 6 error details in the target error order have successfully matched for consistency, and 4 error details have failed to match for consistency. Therefore, the target error order needs to be modified based on multiple target details.

[0096] In some embodiments, modifying the target error form based on multiple target details can be achieved in the following two ways:

[0097] In the first implementation, N target error details with the same identifier as the target details can be identified in the target error order based on the identifiers corresponding to the multiple target details. Here, N is a positive integer. Further, a new error order can be created based on the error details other than the N target error details in the target error order, and the target error order can be closed. Further, the status of each error detail in the new error order is set to "pending processing".

[0098] As an example, such as Figure 2 As shown, target error form 1 includes 10 error details, namely error details 1-10, and their corresponding identifiers are K1-K10. There are 6 target details with identifiers K1, K2, K4, K5, K7, and K8. Then, a new error form 2 can be created based on error details 3, 6, 9, and 10, and target error form 1 can be closed.

[0099] In the second implementation, N target error details with the same identifier as the target detail can be determined from the target error order based on the identifiers corresponding to the multiple target details. Here, N is a positive integer. Furthermore, the status of the N target error details in the target error order can be modified to a processed state, and a new number of target error details can be determined based on at least one error detail in the pending state of the error order.

[0100] As an example, such as Figure 3As shown, Target Error Item 1 includes 10 error details, labeled 1-10, with corresponding identifiers K1-K10, and their statuses are pending. Six target details are labeled K1, K2, K4, K5, K7, and K8. Therefore, the statuses of error details 1, 2, 4, 5, 7, and 8 in Target Error Item 1 can be changed to processed, while the statuses of error details 3, 6, 9, and 10 remain pending. Furthermore, the new number of target error details in Target Error Item 1 is 4.

[0101] The following example illustrates the error reporting method of this application. Taking a set date of T+1, the target details (hereinafter referred to as false imbalance details) as details generated on T+1, and error reports generated before the set date as error reports generated on T+1 and error reports generated on T, the error reporting method will be explained in detail below. See [link to relevant documentation]. Figure 4 :

[0102] S401, retrieve the target details for T+1 day, the error report for T day, and the error report for T+1 day.

[0103] Among them, the T-day error form is an error processing form created through the system's automatic form creation process for data that failed to reconcile cross-system transactions on day T. The T+1-day error form is an error processing form created through the accounting system's automatic form creation process for data that failed to reconcile cross-system transactions on day T+1.

[0104] The error record creation process involves two scenarios: one is creating a record based on the accounting set number, and the other is creating a record based on the global event tracking number (serial number). The specific process is as follows: First, detailed data is extracted from the source table to intermediate table 1. This table can be sorted by fields such as multi-entity identifier and accounting set number to determine candidate master records. The source table records the detailed data generated by each accounting component, and the multi-entity identifier indicates the transaction attributes of the detailed data, such as domestic or overseas. Next, the primary key of the candidate master record for each set number or serial number is determined. This can be done by using the record corresponding to the smallest transaction service code of the smallest transaction sequence number. For example, multiple accounting components may correspond to the same set number, and each accounting component has a transaction sequence number based on the transaction order. Each accounting component may have multiple transaction service codes for the same set number. Therefore, the record of the earliest transaction (i.e., the earliest transaction record generated by the component with the smallest transaction sequence number) is selected as the candidate master record. In some scenarios, since intermediate table 1 has already been sorted, the smallest primary key of each set number or serial number can be used. The transaction service code of the candidate master record is used as the master transaction service code to obtain intermediate table 2. Then, intermediate table 2 is written to the master table EH_FORM_INFO. Finally, groups with the same master transaction service number are merged to create a new error processing order.

[0105] The T+1 day false unbalanced details are the target details provided by the T+1 day accounting engine system. The target details are the details with the same identifier as the details to be balanced and whose consistency has been successfully verified. The identifier of the details to be balanced is the identifier of the details whose transaction consistency verification failed before T+1 day.

[0106] S402, based on the false unevenness details, determine the target error sheet and obtain the false unevenness error handling information table.

[0107] Specifically, all relevant target error orders can be retrieved based on the set number (i.e., the set number) or serial number in the false imbalance details (CMPT_FALSE_UNEQUAL), and written into the false imbalance error processing form information table (AC_FUE_ERR_FORM). When retrieving relevant target error orders, it is necessary to ensure that the set number or serial number is in a pending status and that the error order is an unclosed order (i.e., unprocessed).

[0108] After identifying the target error order, the false imbalance error handling order information table includes the primary key, type (old order, new order), and status of the error order involved. The status indicates whether the error order has been processed.

[0109] Based on the reconciliation set number or serial number in the false imbalance details, compare it with the reconciliation set number or serial number in the error details of the error report, and then determine the following variables:

[0110] C1: The number of details with the serial number in "FALSE_UNEQUAL".

[0111] C2: The serial number is not in the number of details in "Fake Uneven Details (CMPT_FALSE_UNEQUAL)".

[0112] C3: The number of sets in the "Fake Unequal Details (CMPT_FALSE_UNEQUAL)" list.

[0113] C4: The number of items is not in the "Fake Uneven Details (CMPT_FALSE_UNEQUAL)" list.

[0114] C0: Quantity of error reports.

[0115] False Imbalance Error Handling Form Information AC_FUE_ERR_FORM

[0116]

[0117]

[0118] S403, process the target error order based on the false imbalance error processing information table.

[0119] In some embodiments, the target error handling unit can be determined to have been successfully checked if and only if the following equations hold true: (C1-C2) == C0 or (C3-C4) == C0

[0120] Furthermore, after confirming that the target error order has been successfully matched, the status of the target error order in the false imbalance error handling form information table can be changed to "matching successful" or "processed", and the target error order can be closed.

[0121] In some embodiments, when the above equation is not satisfied, the target error order cannot be automatically closed. Instead, error details that are not present in the target details (such as mismatched account set numbers / serial numbers, etc.) can be added to the remarks field, and the status of the target error order can be set to "suspended".

[0122] In some embodiments, error orders in the "pending" state in the false imbalance error handling order information table can be traversed. Based on the information of the error orders, including key information such as error type, primary responsible component, and transaction service number in the basic information of the error orders, a split order processing can be generated for the error orders, and the new error orders can be written to the error order master table EH_FORM_INFO. Furthermore, the information and status in the false imbalance error handling order information table can be modified.

[0123] In some embodiments, there are two methods for splitting error orders. One method is to separate the details of non-false discrepancies from the old error order, that is, to create a new error order based on the details of non-false discrepancies. This method recalculates the timeout period from the creation date of the new error order, which is more reasonable. However, for the accounting component, the error order needs to be reclaimed, and if adjustments or attachments were previously added to the old error order, these operations will all belong to the old error order, and the new error order needs to be redone. The other method is to separate the details of false discrepancies from the old error order, that is, to retain the non-false discrepancies details in the old error order. Specifically, the status of false discrepancies can be set to "processed," so that false discrepancies can be distinguished from non-false discrepancies based on the status of the details. This method does not require the accounting component to reclaim the error order, and if adjustments or attachments were added to the old error order, these operations can still be used. However, the timeout period for processing work orders will be calculated from the original error order creation date, which is unreasonable, and the information in the old error order has been changed, resulting in a high risk of reconciliation.

[0124] In some embodiments, when processing error orders, all related error order information can be retrieved based on the balance set number or serial number in the false imbalance details and the status is "pending processing". If the status of all the error orders involved is "processed", the status of the false imbalance details can be changed to "processed successfully" to prevent the false imbalance details from being processed repeatedly, thus avoiding resource waste.

[0125] Based on the same technical concept, this application provides an error order processing device, please refer to... Figure 5 The device 500 can perform any step in the error order processing method described above, and will not be repeated here to avoid repetition. The device 500 includes an acquisition module 501 and a processing module 502.

[0126] The acquisition module 501 is used to acquire multiple target details generated on a set date from the accounting engine component, and to acquire error reports generated before the set date from each accounting component; wherein, the target details are details with the same identifier as the details to be reconciled and whose consistency verification is successful, the details to be reconciled identifier is the identifier of the details whose transaction consistency verification failed before the set date, and the error report includes multiple error details;

[0127] The processing module 502 is used to compare the identifiers of the plurality of target details with the identifiers of the error details in the error order, and determine at least one target error order from the error orders based on the comparison result; for each target error order, the processing is performed on each target error order based on the obtained plurality of target details.

[0128] In one possible implementation, the processing module 502, when processing each target error order based on the acquired target details, is specifically used for:

[0129] Determine the total number of error details in each target error order, and the number of target error details corresponding to each target error order, wherein the number of target error details is the number of error details in the target error order that have the same identifier as the target detail;

[0130] Match the total number of error details with the target number of error details;

[0131] The target error order is processed based on the matching results.

[0132] In one possible implementation, the processing module 502, when processing the target error record based on the matching result, is specifically used for:

[0133] If the matching result is that the total number of error details is equal to the target number of error details, then the status of each error detail in the target error order is changed to the processed status, and the target error order is closed.

[0134] If the matching result shows that the total number of error details is greater than the target number of error details, then the target error order is modified based on the multiple target details.

[0135] In one possible implementation, when the processing module 502 modifies the target error form based on the plurality of target details, it is specifically used for:

[0136] Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer;

[0137] A new error order is created based on the error details in the target error order other than the N target error details, and the target error order is closed.

[0138] Set the status of each error detail in the new error report to pending processing.

[0139] In one possible implementation, when the processing module 502 modifies the target error form based on the plurality of target details, it is specifically used for:

[0140] Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer;

[0141] The status of N target error details in the target error order is modified to the processed status, and a new number of target error details is determined based on at least one error detail in the pending status of the error order.

[0142] In one possible implementation, the processing module 502, when comparing the identifiers of the plurality of target details with the identifiers of the error details in the error report, is specifically used for:

[0143] Identify M error details in the error log that are in a pending state, where M is a positive integer;

[0144] For any one of the M error details, the identifier of the error detail is compared with the identifiers of the plurality of target details.

[0145] In one possible implementation, when the processing module 502 determines at least one target error record from the error records based on the comparison results, it is specifically used for:

[0146] For each error order, if the comparison result shows that the identifier of at least one error detail in the error order is the same as the identifier of the target detail, then the error order is taken as the target error order.

[0147] Based on the same technical concept, embodiments of this application provide an electronic device that can realize the function of the error order processing device described above. Please refer to... Figure 6 The device includes a memory 601 and a processor 602.

[0148] Memory 601 is used to store program instructions;

[0149] The processor 602 is used to call program instructions stored in the memory and execute any step in the error handling method according to the obtained program instructions.

[0150] In this embodiment, the processor 602 is the control center of the electronic device, connecting various parts of the electronic device through various interfaces and routes. It executes various functions and processes data by running or executing software programs and / or modules stored in the memory 601, and by calling data stored in the memory 601. Optionally, the processor 602 may include one or more processing units. The processor 602 may be, for example, 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.

[0151] The memory 601 can be used to store software programs and modules. The processor 602 executes various functional applications and data processing by running the software programs and modules stored in the memory 601. The memory 601 mainly includes a program storage area and a data storage area. The program storage area can store the operating system, application programs required for at least one function, etc.; the data storage area can store data created according to business processing, etc. As a non-volatile computer-readable storage medium, the memory 601 can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The memory 601 can 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 601 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 601 in this embodiment can also be a circuit or any other means capable of implementing storage functions for storing program instructions and / or data.

[0152] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium, comprising: a computer program, which, when executed on a computer, causes the computer to perform any of the error order processing methods described above. Since the principle by which the computer-readable storage medium solves the problem is similar to that of the error order 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 elaborated further.

[0153] 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 error order processing methods described above. Since the principle by which the above computer program product solves the problem is similar to that of the error order processing method, the implementation of the above computer program product can refer to the implementation of the method, and repeated details will not be repeated.

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

[0155] 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, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0156] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

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

[0158] 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. An error order processing method, characterized in that, include: The system retrieves multiple target details generated on a set date from the accounting engine component, and retrieves error reports generated before the set date from each accounting component; wherein, the target details are details with the same identifier as the details to be reconciled and whose consistency verification is successful, the details to be reconciled identifier are the identifiers of details whose transaction consistency verification failed before the set date, and the error reports include multiple error details, each error detail corresponding to a status, the status being used to indicate whether the error detail has been processed; Based on the status of multiple target details, the identifiers of the multiple target details are compared with the identifiers of error details in the error order that are in the pending processing state. Based on the comparison result, at least one target error order is determined from the error orders and written into the false imbalance error processing order information table. The status of the multiple target details indicates whether the target detail has been processed. The identifier is a set number or a serial number. The false imbalance error processing order information table includes the error order status corresponding to each of the at least one target error order. The error order status indicates whether the target error order has been processed, and the error order status of the target error order is "unclosed." For each target error order in the false imbalance error handling form information table, each target error order is processed based on the obtained multiple target details, specifically including: Based on the error details in the pending state, determine the total number of error details in each target error order, and determine the number of target error details corresponding to each target error order. The number of target error details is the number of error details in the target error order that have the same identifier as the target detail. Match the total number of error details with the target number of error details; The target error order is processed based on the matching results, and the status of the multiple target details is modified. The processing of the target error order includes at least one of the following: modifying the status of each error detail in the target error order, closing the target error order, and creating a new error order.

2. The method as described in claim 1, characterized in that, The processing of the target error order based on the matching result includes: If the matching result is that the total number of error details is equal to the target number of error details, then the status of each error detail in the target error order is changed to the processed status, and the target error order is closed. If the matching result shows that the total number of error details is greater than the target number of error details, then the target error order is modified based on the multiple target details.

3. The method as described in claim 2, characterized in that, The modification of the target error form based on the multiple target details includes: Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer; A new error order is created based on the error details in the target error order other than the N target error details, and the target error order is closed. Set the status of each error detail in the new error report to pending processing.

4. The method as described in claim 2, characterized in that, The modification of the target error form based on the multiple target details includes: Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer; The status of N target error details in the target error order is modified to the processed status, and a new number of target error details is determined based on at least one error detail in the pending status of the error order.

5. The method as described in claim 1, characterized in that, The step of comparing the identifiers of the multiple target details with the identifiers of the error details in the error report that are in a pending state includes: Identify M error details in the error log that are in a pending state, where M is a positive integer; For any one of the M error details, the identifier of the error detail is compared with the identifiers of the plurality of target details.

6. The method according to any one of claims 1-5, characterized in that, The step of determining at least one target error document from the error documents based on the comparison results includes: For each error order, if the comparison result shows that the identifier of at least one error detail in the error order is the same as the identifier of the target detail, then the error order is taken as the target error order.

7. An error order processing device, characterized in that, include: The acquisition module is used to acquire multiple target details generated on a set date from the accounting engine component, and to acquire error orders generated before the set date from each accounting component; wherein, the target details are details with the same identifier as the details to be reconciled and whose consistency verification is successful, the details to be reconciled identifier is the identifier of the details whose transaction consistency verification failed before the set date, and the error order includes multiple error details, each error detail corresponding to a status, the status being used to indicate whether the error detail has been processed; The processing module is used to compare the identifiers of multiple target details with the identifiers of error details in the error orders that are in a pending state, based on the status of multiple target details, and to determine at least one target error order from the error orders according to the comparison result, and write it into the false imbalance error processing order information table; wherein, the status of multiple target details is used to indicate whether the target detail has been processed, the identifier is a set number or a serial number, the false imbalance error processing order information table includes the error order status corresponding to each of the at least one target error order, the error order status is used to indicate whether the target error order has been processed, and the error order status of the target error order is "unclosed"; for each target error order in the false imbalance error processing order information table, each target error order is processed based on the obtained multiple target details, specifically including: Based on the error details in the pending state, determine the total number of error details in each target error order, and determine the number of target error details corresponding to each target error order. The number of target error details is the number of error details in the target error order that have the same identifier as the target detail. Match the total number of error details with the target number of error details; The target error order is processed based on the matching results, and the status of the multiple target details is modified. The processing of the target error order includes at least one of the following: modifying the status of each error detail in the target error order, closing the target error order, and creating a new error order.

8. The apparatus as claimed in claim 7, characterized in that, The processing module, when processing the target error order based on the matching result, is specifically used for: If the matching result is that the total number of error details is equal to the target number of error details, then the status of each error detail in the target error order is changed to the processed status, and the target error order is closed. If the matching result shows that the total number of error details is greater than the target number of error details, then the target error order is modified based on the multiple target details.

9. The apparatus as claimed in claim 8, characterized in that, The processing module, when modifying the target error form based on the multiple target details, is specifically used for: Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer; A new error order is created based on the error details in the target error order other than the N target error details, and the target error order is closed. Set the status of each error detail in the new error report to pending processing.

10. The apparatus as claimed in claim 8, characterized in that, The processing module, when modifying the target error form based on the multiple target details, is specifically used for: Based on the identifiers corresponding to the multiple target details, determine N target error details in the target error order that have the same identifier as the target details, where N is a positive integer; The status of N target error details in the target error order is modified to the processed status, and a new number of target error details is determined based on at least one error detail in the pending status of the error order.

11. The apparatus as claimed in claim 7, characterized in that, The processing module, when comparing the identifiers of the plurality of target details with the identifiers of the error details in the error report that are in a pending state, specifically performs the following: Identify M error details in the error log that are in a pending state, where M is a positive integer; For any one of the M error details, the identifier of the error detail is compared with the identifiers of the plurality of target details.

12. The apparatus according to any one of claims 7-11, characterized in that, When the processing module determines at least one target error record from the error records based on the comparison results, it is specifically used for: For each error order, if the comparison result shows that the identifier of at least one error detail in the error order is the same as the identifier of the target detail, then the error order is taken as the target error order.

13. 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 method of any one of claims 1-6 according to the obtained program instructions.

14. 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-6.

15. 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-6.

Images