Data processing method and device, equipment and storage medium

Abstract

The application provides a data processing method, device and equipment and a storage medium. The method comprises the following steps: obtaining to-be-audited revenue data, wherein the revenue data comprises receivable detailed data, collected detailed data, receivable data for verification and collected data for verification; performing auditing processing on the to-be-audited revenue data to obtain audited successful revenue data and un-audited successful revenue data; sending the audited successful revenue data and the un-audited successful revenue data to a user terminal to feed back corrected revenue data; and obtaining corresponding long-short amount values according to the corrected revenue data. According to the method, the audited successful revenue data and the un-audited successful revenue data can be directly obtained by automatically performing auditing processing on the data, and the corresponding long-short amount values can be automatically obtained according to the corrected revenue data, without manual reconciliation, thereby reducing labor cost and improving reconciliation efficiency.

Description

Technical Field

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

[0002] With the increasing development of internet businesses, the business covered by enterprise revenue and fund management is becoming more and more complex, with more and more data source interfaces, reports, and functional modules.

[0003] The existing revenue and cash reconciliation method is based on the aggregation of information by staff at the provincial, municipal, district, county, and branch levels, thereby realizing daily and monthly cash flow settlement and automatic management of overages and shortages.

[0004] However, the existing method of manually reconciling revenue and funds by staff is labor-intensive, time-consuming, and inefficient. Summary of the Invention

[0005] This application provides a data processing method, apparatus, device, and storage medium to solve the problem that the existing method of manually reconciling revenue funds by staff is time-consuming and inefficient.

[0006] Firstly, this application provides a data processing method, including:

[0007] Obtain the revenue data to be audited, including: accounts receivable details, actual revenue details, accounts receivable as the basis, and actual revenue as the basis;

[0008] The revenue data to be audited is audited to obtain the revenue data that was successfully audited and the revenue data that was not successfully audited.

[0009] The revenue data that was successfully audited and the revenue data that was not successfully audited are sent to the user terminal so that the user terminal can provide feedback on the corrected revenue data.

[0010] The corresponding long and short item values ​​are obtained based on the revised revenue data.

[0011] Secondly, this application provides a data processing apparatus, comprising:

[0012] The acquisition unit is used to acquire revenue data to be audited, the revenue data including: accounts receivable details, actual revenue details, accounts receivable as the basis, and actual revenue as the basis;

[0013] The processing unit is used to perform auditing processing on the revenue data to be audited, and to obtain the revenue data that was successfully audited and the revenue data that was not successfully audited.

[0014] The processing unit is also used to send the audited revenue data and the unaudited revenue data to the user terminal, so that the user terminal can provide feedback on corrected revenue data based on the unaudited revenue data.

[0015] The processing unit is also used to obtain the corresponding long / short item values ​​based on the corrected revenue data.

[0016] Thirdly, this application provides an electronic device, including: a processor, a memory, and a transceiver;

[0017] Interconnection of processor, memory, and transceiver circuits;

[0018] The memory stores the instructions that the computer executes;

[0019] A transceiver is used to send and receive data.

[0020] The processor executes computer execution instructions stored in memory, causing the processor to perform the method described in the first aspect.

[0021] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first aspect.

[0022] The data processing method, apparatus, equipment, and storage medium provided in this application acquire revenue data to be audited, including: accounts receivable details, actual receipt details, accounts receivable as the basis, and actual receipt as the basis; perform audit processing on the revenue data to be audited to obtain audited revenue data and unaudited revenue data; send the audited revenue data and the unaudited revenue data to a user terminal for the user terminal to provide feedback on corrected revenue data; obtain the corresponding overage / underage values ​​based on the corrected revenue data. By automatically auditing the data, the system can directly obtain audited revenue data and unaudited revenue data, and can automatically obtain the corresponding overage / underage values ​​based on the corrected revenue data, eliminating the need for manual reconciliation by staff, reducing labor costs, and improving reconciliation efficiency. Attached Figure Description

[0023] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0024] Figure 1 A schematic diagram of the network architecture for the data processing method provided in this application;

[0025] Figure 2 A flowchart illustrating a data processing method provided in this application;

[0026] Figure 3 A flowchart illustrating another data processing method provided in this application;

[0027] Figure 4 A schematic diagram of the structure of a data processing device provided in this application;

[0028] Figure 5 This is a first block diagram of an electronic device used to implement the data processing method of the embodiments of this application;

[0029] Figure 6 This is a second block diagram of an electronic device used to implement the data processing method of the embodiments of this application.

[0030] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0031] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0032] To clearly understand the technical solution of this application, the solutions of the prior art will be described in detail first.

[0033] With the rapid development of internet businesses, the business scope of enterprise revenue and cash management is becoming increasingly complex, with more and more data source interfaces, reports, and functional modules. The existing revenue and cash reconciliation method is based on the aggregation of data by staff at the provincial, municipal, district, county, and branch levels, thereby realizing daily and monthly cash flow settlement and automatic management of overages and shortages.

[0034] However, the existing method of manually reconciling revenue and funds by staff is labor-intensive, time-consuming, and inefficient.

[0035] Therefore, given the low efficiency of existing methods that rely on manual sampling of incoming data, the inventors discovered in their research that a new method can be used to automatically process and verify revenue data. This method involves acquiring revenue data to be audited, including accounts receivable details, actual receipt details, accounts receivable as the basis, and actual receipt as the basis. The audited revenue data is then processed to obtain both successfully audited and unaudited revenue data. This data is then sent to the user terminal for feedback and correction. Based on the corrected revenue data, the corresponding overage / underage figures are obtained. This automatic data auditing process directly yields both successfully audited and unaudited revenue data, and automatically calculates overage / underage figures based on the corrected revenue data. This eliminates the need for manual reconciliation by staff, reducing labor costs and improving reconciliation efficiency.

[0036] Therefore, based on the above-mentioned inventive discoveries, the inventors proposed the technical solutions of the embodiments of this application. The network architecture and application scenarios of the data processing method provided in the embodiments of this application are described below.

[0037] like Figure 1 As shown in the embodiment of this application, the network architecture corresponding to the data processing method includes: server 1 and user terminal 2. Server 1 obtains revenue data to be audited, including: accounts receivable details, actual receipt details, accounts receivable as the basis, and actual receipt as the basis. Server 1 performs audit processing on the revenue data to be audited, obtaining successfully audited revenue data and unaudited revenue data. Server 1 sends the successfully audited revenue data and unaudited revenue data to user terminal 2 for feedback and correction. Server 1 obtains the corresponding overage / underage figures based on the corrected revenue data. By automatically auditing the data, successfully audited revenue data and unaudited revenue data can be directly obtained, and the corresponding overage / underage figures can be automatically obtained based on the corrected revenue data, eliminating the need for manual reconciliation by staff, reducing labor costs, and improving reconciliation efficiency.

[0038] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0039] Figure 2 This is a flowchart illustrating a data processing method provided in this application, applied to an electronic device. The electronic device can be a digital computer of various forms, such as a cellular phone, smartphone, laptop computer, desktop computer, workstation, personal digital assistant, server, blade server, mainframe computer, and other suitable computers. Figure 2 As shown, the method includes:

[0040] Step 201: Obtain the revenue data to be audited. The revenue data includes: accounts receivable details, actual revenue details, accounts receivable as the standard data, and actual revenue as the standard data.

[0041] In this embodiment, revenue data to be audited is obtained, including accounts receivable details, actual revenue details, accounts receivable as the standard data, and actual revenue as the standard data.

[0042] Step 202: Perform auditing on the revenue data to be audited to obtain the revenue data that was successfully audited and the revenue data that was not successfully audited.

[0043] In this embodiment, the revenue data to be audited is audited to obtain revenue data that has been successfully audited and revenue data that has not been successfully audited. Specifically, the auditing is performed on the detailed receivable data, the detailed receivable data, the data based on receivable, and the data based on actual receivable.

[0044] Step 203: Send the successfully audited revenue data and the unaudited revenue data to the user terminal so that the user terminal can provide feedback on the corrected revenue data.

[0045] In this embodiment, successfully audited revenue data and unaudited revenue data are sent to the user terminal. The user terminal receives and displays the successfully audited revenue data, allowing the user to understand the data more intuitively. The user can correct the unaudited revenue data, such as checking for errors in order information, and the corrected revenue data is displayed through the user terminal.

[0046] Step 204: Obtain the corresponding long and short item values ​​based on the revised revenue data.

[0047] In this embodiment, corrected revenue data is received, corresponding surplus / shortage values ​​are obtained based on the corrected revenue data, and the surplus / shortage values ​​are compared with preset thresholds. Based on the comparison results, the corresponding database is determined and stored.

[0048] In this embodiment, revenue data to be audited is obtained, including accounts receivable details, actual receipt details, accounts receivable as the basis, and actual receipt as the basis. Auditing processing is performed on the revenue data to be audited to obtain successfully audited revenue data and unaudited revenue data. The obtained successfully audited and unaudited revenue data are sent to the user terminal for feedback and correction. Further, the corresponding overage / underage figures are obtained based on the corrected revenue data. By automatically auditing the data, successfully audited and unaudited revenue data can be directly obtained, and the corresponding overage / underage figures can be automatically obtained based on the corrected revenue data. This eliminates the need for manual reconciliation by staff, reducing labor costs and improving reconciliation efficiency.

[0049] Figure 3 A flowchart illustrating another data processing method provided in this application, which is applied to electronic devices, such as... Figure 3 As shown, the method includes:

[0050] Step 301: Obtain the revenue data to be audited. The revenue data includes: accounts receivable details, actual revenue details, accounts receivable as the standard data, and actual revenue as the standard data.

[0051] In this embodiment, step 301 and step 201 have the same technical features. For a detailed description, please refer to step 201, which will not be repeated here.

[0052] Step 302: Perform auditing on the revenue data to be audited to obtain the revenue data that was successfully audited and the revenue data that was not successfully audited.

[0053] In one possible implementation, if the revenue data is accounts receivable details, the revenue data to be audited is audited to obtain successfully audited revenue data and unaudited revenue data, including:

[0054] Step 3021: Obtain the headquarters' actual receipt details data and match the transaction identifier in the accounts receivable details data to be audited with the order identifier in the headquarters' actual receipt details data.

[0055] In this embodiment, the actual receipt details of the headquarters are obtained, and the transaction identifier in the accounts receivable details data to be audited is matched with the order identifier in the actual receipt details data of the headquarters. The transaction identifier and the order identifier are the same identifier, but it is called the transaction identifier in the accounts receivable details data and the order identifier in the actual receipt details data.

[0056] Before obtaining accounts receivable details, the process also includes:

[0057] Based on the branch code, find the detailed data within a preset time period in the provincial production charge details table that matches the branch code; summarize the payable date, branch code, business transaction identifier, and business number information in the detailed data within the preset time period to form the charge details table payable details; based on the business transaction identifier in the charge details table payable details, associate the data with the physical channel charge details table and the internet channel charge details table to obtain the payable details data.

[0058] In this embodiment, the branch code is obtained, and the detailed data within a preset time period in the provincial production charge details table that matches the branch code is found. The receivable date, branch code, business flow identifier, and business number information in the detailed data within the preset time period are summarized to obtain the charge details table receivable details. Furthermore, the data in the charge details table receivable details are associated with the physical channel charge details table and the Internet channel charge details table based on the business flow identifier in the charge details table receivable details table to obtain the receivable details data.

[0059] Step 3022: If the transaction identifier matches the order identifier, determine whether the order information corresponding to the order identifier that matches the transaction identifier is consistent with the order information corresponding to the transaction identifier. The order information includes: order amount and payment method.

[0060] In this embodiment, if the transaction identifier in the accounts receivable details to be audited matches the order identifier in the headquarters' actual receipt details, it is determined whether the order information corresponding to the order identifier that matches the transaction identifier is the same as the order information corresponding to the transaction identifier. The order information includes the order amount and payment method. The order amount and payment method in the order information corresponding to the order identifier that matches the transaction identifier are compared with the order amount and payment method in the order information corresponding to the transaction identifier.

[0061] Step 3023: If yes, then delete the accounts receivable details corresponding to the transaction identifier from the accounts receivable details to be audited, and obtain the updated first accounts receivable details. The accounts receivable details corresponding to the transaction identifier are the accounts receivable details that have been successfully audited.

[0062] In this embodiment, if the order information corresponding to the order identifier matched by the transaction identifier is the same as the order information corresponding to the transaction identifier, it indicates that it is the same order. The accounts receivable details corresponding to the transaction identifier are deleted from the accounts receivable details data to be audited, and updated first accounts receivable details data is obtained. The accounts receivable details data corresponding to the transaction identifier are the accounts receivable details data that have been successfully audited. All successfully audited accounts receivable details data corresponding to the accounts receivable details data to be audited are summarized, and the summarized successfully audited accounts receivable details data is sent to the user terminal.

[0063] Step 3024: Match the business identifier in the updated first accounts receivable details with the business identifier in the headquarters actual receipt details, and determine the accounts receivable details that have not been successfully audited based on the business identifier matching results.

[0064] In this embodiment, the business identifier in the updated first accounts receivable details is matched with the business identifier in the headquarters actual receipt details, thereby determining the accounts receivable details that have not been successfully audited based on the business identifier matching result.

[0065] Optionally, the unaudited accounts receivable details can be determined based on the business identifier matching results, including:

[0066] If the business identifier in the updated first accounts receivable details data matches the business identifier in the headquarters' actual receipt details data, then the accounts receivable details data within a preset time period corresponding to the matching business identifier will be deleted from the updated first accounts receivable details data, resulting in updated second accounts receivable details data. The accounts receivable details data within a preset time period corresponding to the matching business identifier are the audited accounts receivable details data. Next, the branch's actual receipt details data will be retrieved, and it will be determined whether the business number in the updated second accounts receivable details data matches the business number corresponding to the non-refund status in the branch's actual receipt details data. If so, the matching business identifier will be deleted from the updated first accounts receivable details data. The corresponding accounts receivable details are deleted from the updated second accounts receivable details data to obtain the updated third accounts receivable details data. The accounts receivable details data corresponding to the matching business identifier are the successfully audited accounts receivable details data. It is determined whether the business number of the updated third accounts receivable details data matches the business number corresponding to the order cancellation status in the branch actual receipt details data. If so, the accounts receivable details data corresponding to the matching business identifier are deleted from the updated third accounts receivable details data to obtain the unaudited accounts receivable details data. The accounts receivable details data corresponding to the matching business identifier are the successfully audited accounts receivable details data.

[0067] In this embodiment, if the business identifier of the updated first accounts receivable details data matches the business identifier in the headquarters actual receipt details data, then the accounts receivable details data within a preset time period corresponding to the matching business identifier are deleted from the updated first accounts receivable details data to obtain the updated second accounts receivable details data. The deleted part, namely the accounts receivable details data within the preset time period corresponding to the matching business identifier, is the accounts receivable details data that has been successfully audited.

[0068] Further, obtain the detailed data of actual revenue received by the division. The detailed data of actual revenue received by the division is the detailed data of actual revenue received by the province. Determine whether the business number of the updated second detailed data of accounts receivable matches the business number corresponding to the non-refund status in the detailed data of accounts receivable received by the division. If the business number of the updated second detailed data of accounts receivable matches the business number corresponding to the non-refund status in the detailed data of accounts receivable received by the division, then delete the detailed data of accounts receivable corresponding to the matching business identifier from the updated second detailed data of accounts receivable, and obtain the updated third detailed data of accounts receivable. The deleted part, that is, the detailed data of accounts receivable corresponding to the matching business identifier, is the detailed data of accounts receivable that has been successfully audited.

[0069] Further, it is determined whether the business number of the updated third accounts receivable details matches the business number corresponding to the order cancellation status in the branch's actual receipt details. If the business number of the updated third accounts receivable details matches the business number corresponding to the order cancellation status in the branch's actual receipt details, the accounts receivable details corresponding to the matching business identifier are deleted from the updated third accounts receivable details, resulting in unaudited accounts receivable details. The accounts receivable details corresponding to the matching business identifier are the successfully audited accounts receivable details. All unaudited accounts receivable details corresponding to the accounts receivable details to be audited are summarized, and the summarized unaudited accounts receivable details are sent to the user terminal for the user to correct the unaudited accounts receivable details and provide feedback on the corrected accounts receivable details.

[0070] In one possible implementation, if the revenue data is detailed actual receipt data, the revenue data to be audited is audited to obtain successfully audited revenue data and unaudited revenue data, including:

[0071] Step 3025: Obtain the detailed accounts receivable data of the headquarters and the detailed accounts receivable data of the branches, and determine whether the order identifier of the actual receipts data to be audited matches the order identifier in the detailed accounts receivable data of the headquarters.

[0072] In this embodiment, the head office accounts receivable details and branch accounts receivable details are obtained. It is determined whether the order identifier of the actual receipt details to be audited matches the order identifier in the head office accounts receivable details. Furthermore, based on the matching result, the actual receipt details that have been successfully audited and the actual receipt details that have not been successfully audited are determined.

[0073] Step 3026: If yes, determine whether the order information corresponding to the matched order identifier is consistent with the order information corresponding to the order identifier of the actual receipt details data to be audited. The order information includes: order amount and payment method.

[0074] In this embodiment, if the order identifier of the actual receipts data to be audited matches the order identifier in the accounts receivable data of the headquarters, it is determined whether the order information corresponding to the matching order identifier is consistent with the order information corresponding to the order identifier of the actual receipts data to be audited. The order information includes the order amount and payment method.

[0075] Step 3027: If yes, then delete the actual receipt details data corresponding to the order identifier from the actual receipt details to be audited, and obtain the updated first actual receipt details data. The actual receipt details data corresponding to the order identifier is the actual receipt details data that has been successfully audited.

[0076] In this embodiment, if the order information corresponding to the matched order identifier is consistent with the order information corresponding to the order identifier of the actual receipt details data to be audited, it indicates that it is the same order. The actual receipt details data corresponding to the order identifier is deleted from the actual receipt details to be audited, and the updated first actual receipt details data is obtained. The actual receipt details data corresponding to the order identifier is the actual receipt details data that has been successfully audited.

[0077] Step 3028: Determine the unaudited actual receipt data based on the updated first actual receipt details data, headquarters accounts receivable details data, and branch accounts receivable details data.

[0078] In this embodiment, the unaudited actual receipt data is determined based on the updated first actual receipt details data, the headquarters accounts receivable details data, and the branch accounts receivable details data.

[0079] Optionally, the unaudited receivables data can be determined based on the updated first receivables details, headquarters receivables details, and branch receivables details, including:

[0080] Determine whether the order identifier corresponding to the payment status in the updated first actual receipt details data matches the order identifier corresponding to the payment status in the branch accounts receivable details data; if so, delete the actual receipt details data corresponding to the matching order identifier from the updated first actual receipt details data to obtain the updated second actual receipt details data. The actual receipt details data corresponding to the matching order identifier is the audited actual receipt data. Determine whether the order identifier corresponding to the refund status in the updated second actual receipt details data matches the order identifier corresponding to the refund status in the branch accounts receivable details data; if so, delete the actual receipt details data corresponding to the matching order identifier from the updated second actual receipt details data to obtain the updated third actual receipt details data. The actual receipt details data corresponding to the matching order identifier is the audited actual receipt data. Determine the unaudited actual receipt data based on the updated third actual receipt details data and the headquarters accounts receivable details data.

[0081] In this embodiment, it is determined whether the order identifier corresponding to the payment status in the updated first actual receipt details data matches the order identifier corresponding to the payment status in the branch accounts receivable details data. If the order identifier corresponding to the payment status in the updated first actual receipt details data matches the order identifier corresponding to the payment status in the branch accounts receivable details data, the actual receipt details data corresponding to the matching order identifier is further deleted from the updated first actual receipt details data to obtain the updated second actual receipt details data. The actual receipt details data corresponding to the matching order identifier is the actual receipt data that has been successfully audited.

[0082] Further, it is determined whether the order identifier corresponding to the refund status in the updated second actual receipt details data matches the order identifier corresponding to the refund status in the branch accounts receivable details data. If the order identifier corresponding to the refund status in the updated second actual receipt details data matches the order identifier corresponding to the refund status in the branch accounts receivable details data, the actual receipt details data corresponding to the matching order identifier is deleted from the updated second actual receipt details data, and the updated third actual receipt details data is obtained. Among them, the actual receipt details data corresponding to the matching order identifier is the actual receipt data that has been successfully audited. Further, based on the updated third actual receipt details data and the headquarters accounts receivable details data, the actual receipt data that has not been successfully audited is determined.

[0083] Optionally, the unaudited actual receipts data can be determined based on the updated third-party actual receipts details and the headquarters accounts receivable details, including:

[0084] Determine whether the order identifier corresponding to the payment status in the updated third actual receipt details data matches the order identifier corresponding to the payment status in the headquarters accounts receivable details data; if so, delete the actual receipt details data corresponding to the matching order identifier from the updated third actual receipt details data to obtain the updated fourth actual receipt details data. The actual receipt details data corresponding to the matching order identifier are the audited actual receipt data. Determine whether the order identifier corresponding to the refund status in the updated fourth actual receipt details data matches the order identifier corresponding to the refund status in the headquarters accounts receivable details data; if so, delete the actual receipt details data corresponding to the matching order identifier from the updated fourth actual receipt details data to obtain the unaudited actual receipt data. The actual receipt details data corresponding to the matching order identifier are the audited actual receipt data.

[0085] In this embodiment, it is determined whether the order identifier corresponding to the payment status in the updated third actual receipt details data matches the order identifier corresponding to the payment status in the headquarters accounts receivable details data. If the order identifier corresponding to the payment status in the updated third actual receipt details data matches the order identifier corresponding to the payment status in the headquarters accounts receivable details data, the actual receipt details data corresponding to the matching order identifier is deleted from the updated third actual receipt details data to obtain the updated fourth actual receipt details data. The actual receipt details data corresponding to the matching order identifier is the actual receipt data that has been successfully audited.

[0086] Furthermore, it is determined whether the order identifier corresponding to the refund status in the updated fourth actual receipt details data matches the order identifier corresponding to the refund status in the headquarters accounts receivable details data. If the order identifier corresponding to the refund status in the updated fourth actual receipt details data matches the order identifier corresponding to the refund status in the headquarters accounts receivable details data, the actual receipt details data corresponding to the matching order identifier is deleted from the updated fourth actual receipt details data, obtaining the actual receipt data that has not been successfully audited. Among them, the actual receipt details data corresponding to the matching order identifier is the audited actual receipt data. All audited actual receipt details data corresponding to the actual receipt details data to be audited are summarized, and the summarized audited actual receipt details data is sent to the user terminal so that the user can intuitively understand the actual receipt details data.

[0087] In one possible implementation, if the revenue data is based on accounts receivable, the revenue data to be audited is audited to obtain successfully audited revenue data and unaudited revenue data, including:

[0088] Step 3021a: Obtain the audited actual receipt details data and the audited accounts receivable details data, and determine whether the order identifier in the accounts receivable data to be audited matches the order identifier in the audited actual receipt details data.

[0089] In this embodiment, the successfully audited actual receipt details data and successfully audited accounts receivable details data are obtained. It is further determined whether the order identifier in the accounts receivable data to be audited matches the order identifier in the successfully audited actual receipt details data. Based on the identifier matching result, the unaudited accounts receivable data and the successfully audited accounts receivable data are determined.

[0090] Step 3021b: If yes, then delete the accounts receivable data corresponding to the matching order identifier from the accounts receivable data to be audited, and obtain the accounts receivable data that has not been successfully audited. The accounts receivable data corresponding to the matching order identifier is the accounts receivable data that has been successfully audited.

[0091] In this embodiment, if the order identifier in the accounts receivable data to be audited matches the order identifier in the successfully audited actual receipt details data, the accounts receivable data corresponding to the matching order identifier is deleted from the accounts receivable data to be audited, resulting in accounts receivable data that has not been successfully audited. The accounts receivable data corresponding to the matching order identifier is the accounts receivable data that has been successfully audited.

[0092] Step 3021c: Determine whether the order identifier in the successfully audited accounts receivable details matches the order identifier in the successfully audited actual receipt details.

[0093] In this embodiment, it is determined whether the order identifier in the successfully audited accounts receivable details matches the order identifier in the successfully audited actual receipt details. Based on the matching result, the unaudited accounts receivable data and the successfully audited accounts receivable data are determined.

[0094] Step 3021d: If yes, delete the accounts receivable data corresponding to the matched order identifier from the successfully audited accounts receivable details data to obtain the unaudited accounts receivable data. The accounts receivable data corresponding to the matched order identifier is the successfully audited accounts receivable data.

[0095] In this embodiment, if the order identifier in the successfully audited accounts receivable details matches the order identifier in the successfully audited actual receipt details, the accounts receivable data corresponding to the matching order identifier is deleted from the successfully audited accounts receivable details to obtain unaudited accounts receivable data. The deleted data is the successfully audited accounts receivable data.

[0096] In one possible implementation, the revenue data is based on actual receipts.

[0097] The revenue data to be audited is audited to obtain both successfully audited and unsuccessfully audited revenue data, including:

[0098] Step 3021e: Obtain the audited accounts receivable details and audited actual receipt details, and determine whether the order identifier in the actual receipt data to be audited matches the order identifier in the audited accounts receivable details.

[0099] In this embodiment, the audited accounts receivable details and audited actual receipt details are obtained, and it is determined whether the order identifier in the actual receipt data to be audited matches the order identifier in the audited accounts receivable details.

[0100] Step 3021f: If yes, then delete the actual receipt data corresponding to the matching order identifier from the actual receipt data to be audited, and obtain the actual receipt data that has not been successfully audited. The actual receipt data corresponding to the matching order identifier is the actual receipt data that has been successfully audited.

[0101] In this embodiment, if the order identifier in the actual receipt data to be audited matches the order identifier in the successfully audited accounts receivable details data, the actual receipt data corresponding to the matching order identifier is deleted from the actual receipt data to be audited, and the unaudited actual receipt data is obtained. The accounts receivable data corresponding to the matching order identifier is the successfully audited actual receipt data.

[0102] Step 3021g: Determine whether the order identifier in the successfully audited actual receipt details data matches the order identifier in the successfully audited accounts receivable details data.

[0103] In this embodiment, it is determined whether the order identifier in the successfully audited actual receipt details data matches the order identifier in the successfully audited accounts receivable details data. Based on the matching result, the unaudited actual receipt data and the successfully audited actual receipt data are determined.

[0104] Step 3021f: If yes, then delete the actual receipt data corresponding to the matched order identifier from the audited actual receipt details data to obtain the unaudited actual receipt data. The actual receipt data corresponding to the matched order identifier is the audited actual receipt data.

[0105] In this embodiment, if the order identifier in the successfully audited actual receipt details data matches the order identifier in the successfully audited accounts receivable details data, the matching part is deleted, and the actual receipt data corresponding to the matching order identifier is deleted from the successfully audited actual receipt details data to obtain the unaudited actual receipt data. The actual receipt data corresponding to the matching order identifier is the successfully audited actual receipt data.

[0106] Step 303: Send the successfully audited revenue data and the unaudited revenue data to the user terminal so that the user terminal can provide feedback on the corrected revenue data.

[0107] In this embodiment, step 303 has the same technical features as step 203. For a detailed description, please refer to step 203, which will not be repeated here.

[0108] Step 304: Obtain the accounts receivable and actual receipts corresponding to the order identifiers in the corrected revenue data. Perform a check for overages and shortages based on the accounts receivable and actual receipts corresponding to the order identifiers to obtain the overage and shortage values ​​corresponding to the order identifiers. The overage and shortage values ​​include: overage value and shortage value.

[0109] In this embodiment, the accounts receivable and actual revenue corresponding to the order identifier in the corrected revenue data are obtained. Further, a balance check is performed based on the accounts receivable and actual revenue corresponding to the order identifier to obtain the balance values ​​for each order identifier. These balance values ​​include both excess and shortage values. Specifically, the difference between actual revenue and accounts receivable is calculated. If the difference is positive, it indicates that the actual revenue exceeds the accounts receivable; this difference is the excess value. If the difference is negative, it indicates that the actual revenue does not exceed the accounts receivable; this difference is the shortage value. The excess and shortage values ​​are compared with a preset threshold, and the corresponding database is determined based on the comparison result for storage.

[0110] Optionally, after verifying the overage / underage amount based on the amount due and the amount actually received corresponding to the order identifier, the process further includes:

[0111] If the shortage value is less than a preset threshold, the order identifier and order information corresponding to the shortage value being less than the preset threshold are stored in a preset first database; if the excess value is greater than the preset threshold, the order identifier and order information corresponding to the excess value being greater than the preset threshold are stored in a preset second database; if the excess value is equal to the shortage value, the order identifier and order information corresponding to the excess value being equal to the shortage value are stored in a preset third database.

[0112] In this embodiment, if the shortage value is less than a preset threshold (where the preset threshold is 0), the order identifier and order information corresponding to the shortage value being less than the preset threshold are stored in a preset first database, which stores data related to the shortage value. If the excess value is greater than the preset threshold, the order identifier and order information corresponding to the excess value being greater than the preset threshold are stored in a preset second database, which stores data related to the excess value. If the excess value is equal to the shortage value, the order identifier and order information corresponding to the excess value being equal to the shortage value are stored in a preset third database, which stores data related to the consistency between the excess and shortage values.

[0113] By automatically auditing data, it can directly obtain both successfully audited and unaudited revenue data. Furthermore, it can automatically calculate corresponding overages and underages based on the corrected revenue data, eliminating the need for manual reconciliation by staff, reducing labor costs, and improving reconciliation efficiency. It can also store different types of data by category, making it easy for users to find information.

[0114] Figure 4 A schematic diagram of the structure of a data processing device provided in this application is shown below. Figure 4 As shown, the data processing device 400 provided in this embodiment includes an acquisition unit 401 and a processing unit 402.

[0115] The system includes an acquisition unit 401 for acquiring revenue data to be audited, which includes accounts receivable details, actual revenue details, accounts receivable as-receivable data, and actual revenue as-receivable data. A processing unit 402 is used to process the revenue data to be audited, obtaining successfully audited revenue data and unaudited revenue data. The processing unit 402 also sends the successfully audited and unaudited revenue data to the user terminal, allowing the user terminal to provide corrected revenue data based on the unaudited revenue data. The processing unit 402 further obtains the corresponding overage / underage figures based on the corrected revenue data.

[0116] Optionally, the acquisition unit is further configured to acquire the headquarters' actual receipt details data. The processing unit is further configured to match the transaction identifier in the accounts receivable details data to be audited with the order identifier in the headquarters' actual receipt details data; if the transaction identifier matches the order identifier, then determine whether the order information corresponding to the order identifier matched by the transaction identifier is consistent with the order information corresponding to the transaction identifier, the order information including: order amount and payment method; if so, then delete the accounts receivable details data corresponding to the transaction identifier from the accounts receivable details data to be audited, and obtain updated first accounts receivable details data, the accounts receivable details data corresponding to the transaction identifier being the successfully audited accounts receivable details data; match the business identifier in the updated first accounts receivable details data with the business identifier in the headquarters' actual receipt details data, and determine the accounts receivable details data that have not been successfully audited based on the business identifier matching result.

[0117] Optionally, the processing unit is further configured to, if the business identifier of the updated first accounts receivable details data matches the business identifier in the headquarters' actual receipt details data, delete the accounts receivable details data within a preset time period corresponding to the matching business identifier from the updated first accounts receivable details data, and obtain the updated second accounts receivable details data. The accounts receivable details data within the preset time period corresponding to the matching business identifier are the successfully audited accounts receivable details data. The acquisition unit is further configured to acquire the branch's actual receipt details data. The processing unit is further configured to determine whether the business number of the updated second accounts receivable details matches the business number corresponding to the non-refund status in the branch actual receipt details data; if so, delete the accounts receivable details corresponding to the matching business identifier from the updated second accounts receivable details data to obtain updated third accounts receivable details data, wherein the accounts receivable details corresponding to the matching business identifier are the audited accounts receivable details data; and determine whether the business number of the updated third accounts receivable details matches the business number corresponding to the refund status in the branch actual receipt details data; if so, delete the accounts receivable details corresponding to the matching business identifier from the updated third accounts receivable details data to obtain unaudited accounts receivable details data, wherein the accounts receivable details corresponding to the matching business identifier are the audited accounts receivable details data.

[0118] Optionally, the acquisition unit is further configured to acquire headquarters accounts receivable details and branch accounts receivable details. The processing unit is further configured to determine whether the order identifier of the actual receipt details data to be audited matches the order identifier in the headquarters accounts receivable details data; if so, determine whether the order information corresponding to the matching order identifier is consistent with the order information corresponding to the order identifier in the actual receipt details data to be audited, the order information including: order amount and payment method; if so, delete the actual receipt details data corresponding to the order identifier from the actual receipt details to be audited, and obtain updated first actual receipt details data, the actual receipt details data corresponding to the order identifier being the audited successful actual receipt details data; determine the unaudited actual receipt data based on the updated first actual receipt details data, headquarters accounts receivable details data, and branch accounts receivable details data.

[0119] Optionally, the processing unit is further configured to determine whether the order identifier corresponding to the payment status in the updated first actual receipt details data matches the order identifier corresponding to the payment status in the branch accounts receivable details data; if so, delete the actual receipt details data corresponding to the matching order identifier from the updated first actual receipt details data to obtain updated second actual receipt details data, wherein the actual receipt details data corresponding to the matching order identifier is the audited actual receipt data; determine whether the order identifier corresponding to the refund status in the updated second actual receipt details data matches the order identifier corresponding to the refund status in the branch accounts receivable details data; if so, delete the actual receipt details data corresponding to the matching order identifier from the updated second actual receipt details data to obtain updated third actual receipt details data, wherein the actual receipt details data corresponding to the matching order identifier is the audited actual receipt data; and determine the unaudited actual receipt data based on the updated third actual receipt details data and the headquarters accounts receivable details data.

[0120] Optionally, the processing unit is further configured to determine whether the order identifier corresponding to the payment status in the updated third actual receipt details data matches the order identifier corresponding to the payment status in the headquarters accounts receivable details data; if so, the actual receipt details data corresponding to the matching order identifier is deleted from the updated third actual receipt details data to obtain updated fourth actual receipt details data, and the actual receipt details data corresponding to the matching order identifier is the audited actual receipt data; and to determine whether the order identifier corresponding to the refund status in the updated fourth actual receipt details data matches the order identifier corresponding to the refund status in the headquarters accounts receivable details data; if so, the actual receipt details data corresponding to the matching order identifier is deleted from the updated fourth actual receipt details data to obtain unaudited actual receipt data, and the actual receipt details data corresponding to the matching order identifier is the audited actual receipt data.

[0121] Optionally, the acquisition unit is further configured to acquire successfully audited actual receipt details data and successfully audited accounts receivable details data. The processing unit is further configured to determine whether the order identifier in the accounts receivable data to be audited matches the order identifier in the successfully audited actual receipt details data; if so, the accounts receivable data corresponding to the matching order identifier is deleted from the accounts receivable data to be audited, obtaining unaudited accounts receivable data, and the accounts receivable data corresponding to the matching order identifier is the successfully audited accounts receivable data; and to determine whether the order identifier in the successfully audited accounts receivable details data matches the order identifier in the successfully audited actual receipt details data; if so, the accounts receivable data corresponding to the matching order identifier is deleted from the successfully audited accounts receivable details data, obtaining unaudited accounts receivable data, and the accounts receivable data corresponding to the matching order identifier is the successfully audited accounts receivable data.

[0122] Optionally, the acquisition unit is further configured to acquire successfully audited accounts receivable details and successfully audited actual receipt details. The processing unit is further configured to determine whether the order identifier in the actual receipt data to be audited matches the order identifier in the successfully audited accounts receivable details; if so, delete the actual receipt data corresponding to the matching order identifier from the actual receipt data to be audited, obtaining unaudited actual receipt data, and the actual receipt data corresponding to the matching order identifier is the successfully audited actual receipt data; determine whether the order identifier in the successfully audited actual receipt details matches the order identifier in the successfully audited accounts receivable details; if so, delete the actual receipt data corresponding to the matching order identifier from the successfully audited actual receipt details, obtaining unaudited actual receipt data, and the actual receipt data corresponding to the matching order identifier is the successfully audited actual receipt data.

[0123] Optionally, the acquisition unit is further configured to acquire the accounts receivable and actual receipts corresponding to the order identifiers in the corrected revenue data. The processing unit is further configured to perform a balance check based on the accounts receivable and actual receipts corresponding to the order identifiers, and obtain the balance values ​​corresponding to the order identifiers, including: the balance value and the balance value.

[0124] Optionally, the processing unit is further configured to: if the shortage value is less than a preset threshold, store the order identifier and order information corresponding to the shortage value being less than the preset threshold in a preset first database; if the excess value is greater than the preset threshold, store the order identifier and order information corresponding to the excess value being greater than the preset threshold in a preset second database; and if the excess value is equal to the shortage value, store the order identifier and order information corresponding to the excess value being equal to the shortage value in a preset third database.

[0125] Figure 5 This is a first block diagram of an electronic device used to implement the data processing method of the embodiments of this application, such as... Figure 5 As shown, the electronic device 500 includes: a memory 501, a processor 502, and a transceiver 503.

[0126] The processor 502, memory 501, and transceiver 503 are interconnected;

[0127] Transceiver 503 is used for sending and receiving data;

[0128] Memory 501 stores computer-executed instructions;

[0129] The processor 502 executes computer execution instructions stored in the memory 501, causing the processor 502 to perform the method provided in any of the above embodiments.

[0130] Figure 6 This is a second block diagram of an electronic device used to implement the data processing method of the embodiments of this application, such as... Figure 6 As shown, the electronic device can be a computer, digital broadcasting terminal, messaging device, tablet device, personal digital assistant, server, server cluster, etc.

[0131] Electronic device 800 may include one or more of the following components: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input / output (I / O) interface 812, sensor component 814, and communication component 816.

[0132] Processing component 802 typically controls the overall operation of electronic device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0133] Memory 804 is configured to store various types of data to support the operation of electronic device 800. Examples of this data include instructions for any application or method operating on electronic device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0134] Power supply component 806 provides power to various components of electronic device 800. Power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 800.

[0135] Multimedia component 808 includes a screen that provides an output interface between electronic device 800 and user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When electronic device 800 is in an operating mode, such as a shooting mode or video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0136] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when electronic device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0137] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0138] Sensor assembly 814 includes one or more sensors for providing state assessments of various aspects of electronic device 800. For example, sensor assembly 814 can detect the on / off state of electronic device 800, the relative positioning of components such as the display and keypad of electronic device 800, changes in position of electronic device 800 or a component of electronic device 800, the presence or absence of user contact with electronic device 800, orientation or acceleration / deceleration of electronic device 800, and temperature changes of electronic device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0139] Communication component 816 is configured to facilitate wired or wireless communication between electronic device 800 and other devices. Electronic device 800 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0140] In an exemplary embodiment, the electronic device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0141] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of an electronic device 800 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0142] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores computer-executable instructions that are executed by a processor using the methods in any of the above embodiments.

[0143] In an exemplary embodiment, a computer program product is also provided, including a computer program that is executed by a processor using the methods of any of the above embodiments.

[0144] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0145] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A data processing method, characterized in that, The method includes: Obtain the revenue data to be audited, including: accounts receivable details, actual revenue details, accounts receivable as the basis, and actual revenue as the basis; The revenue data to be audited is audited to obtain the revenue data that was successfully audited and the revenue data that was not successfully audited. The revenue data that was successfully audited and the revenue data that was not successfully audited are sent to the user terminal so that the user terminal can provide feedback on the corrected revenue data. The corresponding long and short item values ​​are obtained based on the revised revenue data; Before obtaining the accounts receivable details, the process also includes: Based on the branch code, find the detailed data within a preset time period in the provincial production fee details table that matches the branch code; summarize the payable date, branch code, business flow identifier, and business number information in the detailed data within the preset time period to form the payable details table; based on the business flow identifier in the payable details table, associate the physical channel fee details table and the internet channel fee details table to obtain the payable details data; If the revenue data is accounts receivable details; the auditing process for the revenue data to be audited, to obtain successfully audited revenue data and unsuccessfully audited revenue data, includes: Obtain the headquarters' actual receipt details data, and match the transaction identifier in the accounts receivable details data to be audited with the order identifier in the headquarters' actual receipt details data; if the transaction identifier matches the order identifier, determine whether the order information corresponding to the order identifier that matches the transaction identifier is consistent with the order information corresponding to the transaction identifier, the order information including: order amount and payment method; if so, delete the accounts receivable details data corresponding to the transaction identifier from the accounts receivable details data to be audited, and obtain updated first accounts receivable details data, the accounts receivable details data corresponding to the transaction identifier is the successfully audited accounts receivable details data; match the business identifier in the updated first accounts receivable details data with the business identifier in the headquarters' actual receipt details data, and determine the accounts receivable details data that were not successfully audited based on the business identifier matching result.

2. The method according to claim 1, characterized in that, The process of determining the unaudited accounts receivable details based on the business identifier matching results includes: If the business identifier of the updated first accounts receivable details data matches the business identifier in the headquarters actual receipt details data, then the accounts receivable details data within a preset time period corresponding to the matching business identifier will be deleted from the updated first accounts receivable details data to obtain the updated second accounts receivable details data. The accounts receivable details data within a preset time period corresponding to the matching business identifier are the accounts receivable details data that have been successfully audited. Obtain the detailed data of the actual receipts of the branch and determine whether the business number of the updated second detailed data of accounts receivable matches the business number corresponding to the non-refund status in the detailed data of the actual receipts of the branch. If so, the accounts receivable details corresponding to the matching business identifier will be deleted from the updated second accounts receivable details data to obtain the updated third accounts receivable details data. The accounts receivable details corresponding to the matching business identifier are the accounts receivable details data that have been successfully audited. Determine whether the business number in the updated third accounts receivable details data matches the business number corresponding to the order cancellation status in the branch actual receipt details data; If so, the accounts receivable details corresponding to the matching business identifier are deleted from the updated third accounts receivable details data to obtain accounts receivable details that have not been successfully audited. The accounts receivable details corresponding to the matching business identifier are the accounts receivable details that have been successfully audited.

3. The method according to claim 1, characterized in that, If the revenue data mentioned is a detailed list of actual receipts; The auditing process for the revenue data to be audited, to obtain successfully audited revenue data and unsuccessfully audited revenue data, includes: Obtain detailed accounts receivable data from headquarters and branches, and determine whether the order identifiers in the actual receipts data to be audited match the order identifiers in the detailed accounts receivable data from headquarters. If so, determine whether the order information corresponding to the matched order identifier is consistent with the order information corresponding to the order identifier of the actual receipt details data to be audited. The order information includes: order amount and payment method. If so, the actual receipt details corresponding to the order identifier are deleted from the actual receipt details to be audited, and the updated first actual receipt details are obtained. The actual receipt details corresponding to the order identifier are the actual receipt details that have been successfully audited. The unaudited actual receipts were determined based on the updated first actual receipts details, headquarters accounts receivable details, and branch accounts receivable details.

4. The method according to claim 3, characterized in that, The determination of unaudited actual receipt data based on the updated first actual receipt details, headquarters accounts receivable details, and branch accounts receivable details includes: Determine whether the order identifier corresponding to the payment status in the updated first actual receipt details data matches the order identifier corresponding to the payment status in the segment accounts receivable details data; If so, the actual receipt details data corresponding to the matched order identifier will be deleted from the updated first actual receipt details data to obtain the updated second actual receipt details data. The actual receipt details data corresponding to the matched order identifier is the actual receipt data that has been successfully audited. Determine whether the order identifier corresponding to the refund status in the updated second actual receipt details data matches the order identifier corresponding to the refund status in the segment accounts receivable details data; If so, the actual receipt details data corresponding to the matching order identifier will be deleted from the updated second actual receipt details data to obtain the updated third actual receipt details data. The actual receipt details data corresponding to the matching order identifier is the actual receipt data that has been successfully audited. The unaudited actual receipts were determined based on the updated third-party actual receipts details and the headquarters accounts receivable details.

5. The method according to claim 4, characterized in that, The determination of unaudited actual receipts based on the updated third-party actual receipts details and the headquarters accounts receivable details includes: Determine whether the order identifier corresponding to the payment status in the updated third-party receivables details data matches the order identifier corresponding to the payment status in the headquarters accounts receivable details data; If so, the actual receipt details data corresponding to the matched order identifier will be deleted from the updated third actual receipt details data to obtain the updated fourth actual receipt details data. The actual receipt details data corresponding to the matched order identifier is the actual receipt data that has been successfully audited. Determine whether the order identifier corresponding to the refund status in the updated fourth receivables details data matches the order identifier corresponding to the refund status in the headquarters accounts receivable details data; If so, the actual receipt details corresponding to the matched order identifier will be deleted from the updated fourth actual receipt details data to obtain the actual receipt data that was not successfully audited. The actual receipt details corresponding to the matched order identifier are the actual receipt data that was successfully audited.

6. The method according to claim 1, characterized in that, If the revenue data mentioned is based on accounts receivable; The auditing process for the revenue data to be audited, to obtain successfully audited revenue data and unsuccessfully audited revenue data, includes: Obtain the audited detailed data of actual receipts and the audited detailed data of accounts receivable, and determine whether the order identifier in the accounts receivable data to be audited matches the order identifier in the audited detailed data of actual receipts. If so, the accounts receivable data corresponding to the matched order identifier is deleted from the accounts receivable data to be audited, and unaudited accounts receivable data is obtained. The accounts receivable data corresponding to the matched order identifier is the successfully audited accounts receivable data. Determine whether the order identifier in the successfully audited accounts receivable details data matches the order identifier in the successfully audited actual receipts details data; If so, the accounts receivable data corresponding to the matching order identifier will be deleted from the successfully audited accounts receivable details data to obtain the unaudited accounts receivable data. The accounts receivable data corresponding to the matching order identifier is the successfully audited accounts receivable data.

7. The method according to claim 1, characterized in that, If the revenue data mentioned is based on actual receipts; The auditing process for the revenue data to be audited, to obtain successfully audited revenue data and unsuccessfully audited revenue data, includes: Obtain the audited accounts receivable details and audited actual receipt details, and determine whether the order identifier in the actual receipt data to be audited matches the order identifier in the audited accounts receivable details; If so, the actual receipt data corresponding to the matching order identifier is deleted from the actual receipt data to be audited, and the actual receipt data that was not successfully audited is obtained. The actual receipt data corresponding to the matching order identifier is the actual receipt data that was successfully audited. Determine whether the order identifier in the successfully audited actual receipt details data matches the order identifier in the successfully audited accounts receivable details data; If so, the actual receipt data corresponding to the matching order identifier is deleted from the successfully audited actual receipt details data to obtain the unaudited actual receipt data. The actual receipt data corresponding to the matching order identifier is the successfully audited actual receipt data.

8. The method according to any one of claims 1 to 7, characterized in that, The step of obtaining the corresponding long / short item values ​​based on the revised revenue data includes: Obtain the accounts receivable and actual revenue corresponding to the order identifiers in the corrected revenue data; The overage and underage amounts are verified based on the amount due and the amount actually received corresponding to the order identifier to obtain the overage and underage values ​​corresponding to the order identifier. The overage and underage values ​​include the overage value and the underage value.

9. The method according to claim 8, characterized in that, The step of verifying the overage / underage amount based on the payable and actual amount received according to the order identifier, and obtaining the overage / underage amount corresponding to the order identifier, includes: If the shortage value is less than a preset threshold, the order identifier and order information corresponding to the shortage value being less than the preset threshold will be stored in the preset first database; If the length value is greater than the preset threshold, the order identifier and order information corresponding to the length value being greater than the preset threshold will be stored in the preset second database; If the length value equals the length value, the order identifier and order information corresponding to the length value equaling the length value are stored in the preset third database.

10. A data processing apparatus, characterized in that, The device includes: The acquisition unit is used to acquire revenue data to be audited, the revenue data including: accounts receivable details, actual revenue details, accounts receivable as the basis, and actual revenue as the basis; The processing unit is used to perform auditing processing on the revenue data to be audited, and to obtain the revenue data that was successfully audited and the revenue data that was not successfully audited. The processing unit is also used to send the audited revenue data and the unaudited revenue data to the user terminal, so that the user terminal can provide feedback on corrected revenue data based on the unaudited revenue data. The processing unit is also used to obtain the corresponding long and short item values ​​based on the corrected revenue data; Before obtaining the accounts receivable details, the obtaining unit is further configured to: Based on the branch code, find the detailed data within a preset time period in the provincial production fee details table that matches the branch code; summarize the payable date, branch code, business flow identifier, and business number information in the detailed data within the preset time period to form the payable details table; based on the business flow identifier in the payable details table, associate the physical channel fee details table and the internet channel fee details table to obtain the payable details data; If the revenue data is accounts receivable details, the processing unit is specifically used for: Obtain the headquarters' actual receipt details data, and match the transaction identifier in the accounts receivable details data to be audited with the order identifier in the headquarters' actual receipt details data; if the transaction identifier matches the order identifier, determine whether the order information corresponding to the order identifier that matches the transaction identifier is consistent with the order information corresponding to the transaction identifier, the order information including: order amount and payment method; if so, delete the accounts receivable details data corresponding to the transaction identifier from the accounts receivable details data to be audited, and obtain updated first accounts receivable details data, the accounts receivable details data corresponding to the transaction identifier is the successfully audited accounts receivable details data; match the business identifier in the updated first accounts receivable details data with the business identifier in the headquarters' actual receipt details data, and determine the accounts receivable details data that were not successfully audited based on the business identifier matching result.

11. An electronic device, comprising: Processor, memory, and transceiver; Interconnection of processor, memory, and transceiver circuits; A transceiver is used to send and receive data. The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 9.

Images