WO2022142040A1

WO2022142040A1 - Billing data verification method and apparatus, computer device and storage medium

Info

Publication number: WO2022142040A1
Application number: PCT/CN2021/091690
Authority: WO
Inventors: 楚亚兵; 黑晓群
Original assignee: 平安普惠企业管理有限公司
Priority date: 2020-12-29
Filing date: 2021-04-30
Publication date: 2022-07-07
Also published as: CN112669008A

Abstract

A billing data verification method, comprising: obtaining a billing file containing billing data to be verified (101); inputting the billing file into a file parser corresponding to a file format of the billing file for parsing to obtain original billing data corresponding to the billing file (102); determining, according to an uploading channel identifier corresponding to the billing file, a standard data type corresponding to the billing file (103); extracting data of the standard data type from the original billing data to serve as the billing data to be verified contained in the billing file (104); obtaining reference billing data to be used for verifying the billing data to be verified (105); and verifying, according to the reference billing data, the billing data to be verified to obtain a verification result corresponding to the billing data to be verified, the verification result being used for indicating that the billing data to be verified passes the verification or fails to pass the verification (106). The automation degree of a reconciliation system can be improved, and thus, the automation of the reconciliation can be better implemented.

Description

Verification method, device, computer equipment and storage medium for billing data

This application claims the priority of the Chinese patent application filed on December 29, 2020 with the application number 202011590424.X and the invention titled "Method, Device, Computer Equipment and Storage Medium for Verification of Billing Data", all of which The contents are incorporated herein by reference.

technical field

The present application relates to the technical field of digital assets, and in particular, to a method, device, computer equipment and storage medium for verifying billing data.

Background technique

Account reconciliation refers to checking and checking the bills in the account books in order to ensure the correctness and reliability of the records in the account books. Traditional reconciliation work is usually performed by manual reconciliation. However, manual reconciliation is prone to omission of bills, and the required labor costs are also very huge. In order to improve reconciliation efficiency and save labor costs, many companies have developed their own automated reconciliation systems. However, the inventor found that the current reconciliation system has a low degree of automation and fails to realize the automation of reconciliation well. For example, the current reconciliation system usually cannot automatically obtain the bill files that need to be reconciled, and the bill files that need to be reconciled need to be uploaded manually. , some billing files are in excel format), the reconciliation data in the billing file is scattered and other reasons, and the automatic analysis of the billing file has not been realized.

technical problem

The technical problem to be solved by this application is that the current account reconciliation system has a low degree of automation and fails to realize the automation of account reconciliation well.

technical solutions

In order to solve the above technical problems, a first aspect of the present application discloses a method for verifying billing data, the method comprising:

Obtain a billing file containing billing data to be verified;

inputting the billing file into a file parser corresponding to the file format of the billing file for parsing to obtain original billing data corresponding to the billing file;

Determine the standard data type corresponding to the billing file according to the upload channel identifier corresponding to the billing file;

Extracting the data of the standard data type from the original billing data as the billing data to be verified contained in the billing file;

obtaining reference billing data to be used for the verification of the billing data to be verified;

Verifying the bill data to be verified according to the reference bill data to obtain a verification result corresponding to the bill data to be verified, where the verification result is used to indicate that the verification of the bill data to be verified has passed or the verification has failed;

Wherein, the bill file is a file in multiple file formats, and bill files in different file formats correspond to different file parsers.

A second aspect of the present application discloses an apparatus for verifying billing data, the apparatus comprising:

The acquisition module is used to acquire the bill file containing the bill data to be verified;

a parsing module, configured to input the billing file into a file parser corresponding to the file format of the billing file for parsing to obtain original billing data corresponding to the billing file;

a determining module, configured to determine the standard data type corresponding to the billing file according to the upload channel identifier corresponding to the billing file;

an extraction module, configured to extract the data of the standard data type from the original bill data, as the bill data to be verified contained in the bill file;

The obtaining module is further configured to obtain reference bill data to be used for the verification of the bill data to be verified;

A verification module, configured to verify the bill data to be verified according to the reference bill data, and obtain a verification result corresponding to the bill data to be verified, and the verification result is used to indicate that the verification of the bill data to be verified is passed or verified Fail;

A third aspect of the present application discloses a computer device, the computer device comprising:

a memory in which executable program code is stored;

a processor connected to the memory;

When the processor calls the executable program code stored in the memory, the following method is performed:

Obtain a billing file containing billing data to be verified;

A fourth aspect of the present application discloses a computer storage medium. The computer storage medium stores computer instructions. When the computer instructions are called, the following method is performed:

Obtain a billing file containing billing data to be verified;

beneficial effect

In the embodiment of the present application, the form of manually uploading reconciliation data can be replaced, and different file parsers can be used to complete the parsing of the reconciliation file according to the different file formats of the billing file, and then different types of reconciliation files can be extracted according to the different uploading channels of the billing file. The data is used as the bill data to be verified, so that the bill data to be verified can be accurately extracted from the bill file, which is conducive to improving the efficiency and accuracy of bill data verification, thereby improving the automation of the reconciliation system and better realizing the reconciliation. automation.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

1 is a schematic flowchart of a method for verifying billing data disclosed in an embodiment of the present application;

2 is a schematic structural diagram of a device for verifying billing data disclosed in an embodiment of the present application;

3 is a schematic structural diagram of a computer device disclosed in an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a computer storage medium disclosed in an embodiment of the present application.

Embodiments of the present invention

The present application discloses a verification method, device, computer equipment and storage medium for billing data, which can replace the form of manually uploading reconciliation data, and use different file parsers to complete the parsing of the billing file according to the file format of the billing file. , and then extract different types of data as the bill data to be verified according to the different upload channels of the bill file, so that the bill data to be verified can be accurately extracted from the bill file, which is beneficial to improve the efficiency and accuracy of bill data verification, thereby improving the The degree of automation of the reconciliation system can better realize the automation of reconciliation. Each of them will be described in detail below.

Example 1

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a method for verifying billing data disclosed in an embodiment of the present application. As shown in Figure 1, the verification method of the billing data may include the following operations:

101. Obtain a bill file containing bill data to be verified.

102. Input the billing file into a file parser corresponding to the file format of the billing file for analysis, and obtain original billing data corresponding to the billing file.

103. Determine the standard data type corresponding to the billing file according to the upload channel identifier corresponding to the billing file.

104. Extract the data of the standard data type from the original bill data, as the bill data to be verified contained in the bill file.

105. Acquire reference bill data to be used for verifying the bill data to be verified.

106. Verify the bill data to be verified according to the reference bill data, and obtain a verification result corresponding to the bill data to be verified, where the verification result is used to indicate that the verification of the bill data to be verified passes or fails.

In this embodiment of the present application, the bill file may be a file in multiple file formats, and the bill file in different file formats corresponds to different file parsers. By automatically obtaining the billing file containing the billing data to be verified for subsequent billing data verification, there is no need to manually upload the billing file, thereby improving the automation of the reconciliation process. The file format of the obtained bill file may be word format, excel format, txt format, or the like. In the account reconciliation system, file parsers corresponding to different file formats can be preset to perform different parsing operations on bill files of different file formats to obtain the bill data to be verified contained in the bill file (described later). In addition, the reconciliation system is the most important part of the payment system. It is at the end of the entire payment process. It is mainly used to ensure the consistency of the transaction flow data of the platform and the data of third-party payment channels or bank bills. It is the guarantee of the payment system. The last line of defense for financial security. Assuming that the reconciliation system is applied in the payment system, the bill file can be uploaded by the terminal of the third-party payment channel or the terminal of the bank. In this case, the reference bill data can be the transaction flow data of the platform where the reconciliation system is located. Compare the bill data to be verified provided by the third-party payment channel or bank with the transaction flow data of the platform. If the two are consistent, the bill is correct, and the verification of the bill data to be verified is passed. If the two are inconsistent, the bill has errors and needs to be verified. Billing data verification failed.

In the account reconciliation system, file parsers corresponding to different file formats can be preset to perform different parsing operations on bill files of different file formats to obtain the bill data to be verified contained in the bill file. For example, if the file format of the bill file is excel, the corresponding file parser may be the ExcelUtil tool. After the bill file is entered into the ExcelUtil tool, you can first check whether the name of the bill file is correct, and then check whether the header of the bill file is filled in according to the standard file, then parse the bill file into a list set, and convert the content of the bill file into For the preset object type, obtain the attribute value corresponding to the table header according to the attribute name, and finally verify the correctness of the content of the billing file. If the verification is passed, the original billing data corresponding to the billing file is obtained. The parsed original bill data may include an upload channel identifier field to distinguish the upload channel of the original bill data. For example, if the upload channel identifier field is recorded as "Bank A", it means that the channel for uploading the original bill data is "Bank A" . In addition, the data included in the parsed original billing data is usually messy and redundant. For example, a transaction record in the original billing data may include the serial number, principal, interest, fee, penalty interest, transaction date and other data of the transaction record. , different types of data are stored in different fields (for example, a field for principal, a field for interest, etc.). However, when reconciliation is performed on different channels, the data to be reconciled is usually different. For example, when Bank A reconciles accounts, it needs to compare the fields of the principal, while when Bank B reconciles accounts, it does not need to compare the fields of the principal, but only the fields of the transaction date. To simplify the comparison operation, only the data in the fields that need to be compared can be extracted as the bill data to be verified. Assuming that the bill file is uploaded by Bank A, extract the data of the principal field from the original bill data corresponding to the bill file as the bill data to be verified. In the billing data, the data in the transaction date field is extracted as the billing data to be verified. Specifically, a table can be preset, in which fields to be compared by different upload channels (ie, standard data types) can be recorded. By querying the table, the standard data types of the billing file can be determined.

It can be seen that the implementation of the verification method for billing data described in FIG. 1 can replace the form of manually uploading the reconciliation data, and use different file parsers to complete the parsing of the billing file according to the different file formats of the billing file. Different upload channels can extract different types of data as the bill data to be verified, so that the bill data to be verified can be accurately extracted from the bill file, which is beneficial to improve the efficiency and accuracy of bill data verification, thereby improving the automation of the reconciliation system. , to better automate reconciliation.

In an optional embodiment, after verifying the bill data to be verified according to the reference bill data, and obtaining a verification result corresponding to the bill data to be verified, the method further includes:

When the verification result is used to indicate that the verification of the to-be-verified bill data fails, extracting the unverified differential bill data from the to-be-verified bill data;

obtaining target billing data for verification of the differential billing data;

Difference verification is performed on the differential bill data according to the target bill data to obtain a differential verification result corresponding to the differential bill data, where the differential verification result is used to indicate whether the differential bill data passes or fails the differential verification.

In this optional embodiment, when reconciliation is performed using the reconciliation system, sometimes data errors or data omissions may occur. When there is a data error or missing data transmission, the transaction records in the bill data to be verified may not be in a one-to-one correspondence with the transaction records (that is, the transaction flow records of the platform) with reference to the bill data, and there is no transaction for which there is a corresponding transaction flow record. The record will cause the verification of the bill data to be verified to fail. When the verification of the to-be-verified bill data fails, a transaction record without a corresponding transaction flow record is extracted from the to-be-verified bill data as the differential bill data. If there is a phenomenon of missing data transmission, the transaction flow record corresponding to the difference bill data may be in the reference bill data for the last reconciliation process or the reference bill data for the next reconciliation process, so the last time The reference bill data for reconciliation processing or the reference bill data for next reconciliation processing is used as the target bill data, and is compared with the difference bill data (ie difference verification). If the comparison is passed, the difference verification of the difference bill data is passed. , which means that the data of the differential billing data is correct, but it fails to pass the verification due to data omission. The billing data to be verified in the billing file is still equal, and manual verification does not need to be performed again. If the difference verification of the difference billing data fails, it means that the data of the difference billing data may be wrong and need to be checked and corrected manually.

It can be seen that by implementing this optional embodiment, when the verification of the to-be-verified bill data fails, further verification can be performed on the to-be-verified bill data that has not passed the verification, thereby making the verification result more accurate.

In an optional embodiment, after the difference verification is performed on the differential bill data according to the target bill data, and a differential verification result corresponding to the differential bill data is obtained, the method further includes:

When the difference verification result is used to indicate that the verification of the difference bill data fails, the bill data to be manually checked is sent to a predetermined manual check terminal, and the bill data to be checked manually refers to the difference that fails the difference verification. billing data;

Receive a manual check result input by the user at the manual check terminal based on the bill data to be manually checked, where the manual check result is used to indicate that the bill data to be checked manually is valid or invalid;

When the received manual inspection result is used to indicate that the bill data to be manually inspected is valid, a reconciliation operation corresponding to the bill data to be manually inspected is performed for the bill data to be manually inspected.

In this optional embodiment, if the difference bill data fails to pass the difference verification, the difference bill data that fails the difference verification needs to be sent to a manual inspection terminal (for example, the terminal corresponding to the financial staff), and then the financial staff manually Manually check the difference bill data that has not passed the difference verification. If the financial staff manually checks that the difference bill data is correct and valid data, the corresponding account reconciliation operation will be performed on the difference bill data that has not passed the difference verification. Here, the reconciliation operation may be to automatically generate the reference bill data corresponding to the difference bill data that has not passed the difference verification, and then perform a verification on the difference bill data that has not passed the difference verification, so as to make the difference bill that has not passed the difference verification. Data can pass validation. In the account reconciliation system, bill reconciliation is a common requirement. If the bill data is true and valid after manual inspection, the bill data in the reconciliation system can be reconciled by performing an account reconciliation operation.

It can be seen that the implementation of this optional embodiment can manually check the differential bill data that has not passed the differential verification when the verification of the differential bill data fails, so that the verification result can be made more accurate by means of manual verification, and the results can be checked manually. When the difference bill data that has not passed the difference verification is real and valid, the corresponding account reconciliation operation is performed to realize the automatic execution of the reconciliation operation, which further improves the automation of the reconciliation system.

In an optional embodiment, after receiving the manual check result input by the user at the manual check terminal based on the bill data to be checked manually, the method further includes:

When the received manual check result is used to indicate that the bill data to be checked manually is invalid, determine whether there is similar bill data similar to the bill data to be checked manually in the reference bill data and the target bill data ;

When it is determined that the similar bill data exists in the reference bill data and the target bill data, the similar bill data is sent to the manual checking terminal.

In this optional embodiment, if it is confirmed by manual inspection that the bill data to be manually inspected is not real and valid data, the bill data to be manually inspected is likely to be incorrect data. In the reconciliation system, there are many factors that cause incorrect billing data, such as incorrect entry data caused by user's misoperation, data loss during the transmission of billing data, etc. If some insignificant factor caused the incorrect billing data, the error is usually minor, such as a missing or changed number. At this time, the similar bill data in the reference bill data and the target bill data that is similar to the bill data to be manually checked is first inquired, and then the similar bill data is sent to the manual check terminal, which can assist the user to correct the wrong bill data (the user is in the comparison After similar billing data and manual checking of billing data, it is easier to find errors in manual checking of billing data, which is more beneficial for users to correct data).

It can be seen that the implementation of this optional embodiment can send similar billing data to the manual checking terminal after manual checking and confirm that the billing data to be checked manually is wrong data, so as to assist the user in correcting the wrongly checking billing data manually, and improve the accuracy of the checking. The intelligence of the accounting system.

In an optional embodiment, the bill data to be verified includes at least one transaction record to be verified, and each transaction record to be verified includes at least a record identifier and transaction information corresponding to the bill record to be verified. The billing data includes at least one reference transaction record, and each of the reference transaction records includes at least a record identifier and transaction information corresponding to the reference transaction record;

And, performing the verification on the bill data to be verified according to the reference bill data to obtain a verification result corresponding to the bill data to be verified, including:

Store all the transaction records to be verified and all the reference transaction records in the Map object of redis;

Store the record identifiers corresponding to all the transaction records to be verified and the record identifiers corresponding to all the reference transaction records to the set object of redis;

Based on the redisdiff algorithm, determine whether there is a difference between all the transaction records to be verified and all the reference transaction records;

When it is judged that there is a difference between all the transaction records to be verified and all the reference transaction records, it is determined that the verification result corresponding to the bill data to be verified is a verification failure;

When it is determined that there is no difference between all the transaction records to be verified and all the reference transaction records, it is determined that the verification result corresponding to the bill data to be verified is verified as passed.

In this optional embodiment, the bill data to be verified and the reference bill data are stored in redis according to the syntax of redis cache, and then the redisdiff algorithm is used to compare the bill data to be verified and the reference bill data, so that the redisdiff algorithm can be used. high performance and improve the speed of data validation. The comparison between the bill data to be verified and the reference bill data may include the following methods: comparing whether the number of records of successful transactions in the bill data to be verified and the reference bill data are consistent, comparing all the records in the bill data to be verified and the reference bill data Whether the number of records is consistent, compare whether the record identification and transaction information (which may include information such as principal, interest, fees, penalty interest, etc.) of each record in the bill data to be verified and the reference bill data are consistent. If the comparison result of one of the above comparison methods is inconsistent, it can be determined that the verification result corresponding to the bill data to be verified is that the verification fails.

It can be seen that by implementing this optional embodiment, the reissdiff algorithm can be used to compare the bill data to be verified with the reference bill data, so that the high performance of the reissdiff algorithm can be utilized to improve the verification efficiency of the bill data.

In an optional embodiment, the acquiring a billing file containing billing data to be verified includes:

Acquire the bill file containing the bill data to be verified from the preset target ftp server, where the target ftp server is used to store the bill file regularly uploaded by the third-party system, or,

Call the billing data download interface provided by the third-party system to obtain the billing file containing the billing data to be verified.

In this optional embodiment, in the payment system, a third-party payment channel or the bank's system (third-party system) can be pre-agreed to push the bill file to the specified target ftp server regularly, and then the account reconciliation system is The billing file can be obtained from the target ftp server for verification. In this way, the efficiency of obtaining the billing file can be improved by utilizing the efficiency of the ftp server for transferring files. Since the ftp server downloads or operates multiple files for a long time, the connection will be disconnected due to timeout. Therefore, when the third-party system pushes the billing file to the target ftp server, it is necessary to set the link timeout time. If the file push time exceeds the link timeout time, determine If the target ftp server is stuck, you need to re-link the target ftp server and push the billing file again. The interval between re-linking and pushing can be every 5-10 minutes (that is, the target ftp server is re-linked every 5-10 minutes). The link timeout time can be set to 30 minutes. In theory, the bill file upload can be completed within 30 minutes. If the bill file upload time exceeds 30 minutes, the server may freeze. In addition, some third-party payment channels or bank systems (third-party systems) provide a download interface for downloading bill files, and the download interface can be called periodically to obtain bill files.

It can be seen that implementing this optional embodiment can provide different ways to obtain billing files, and can improve the efficiency of obtaining billing files by utilizing the efficiency of file transmission by the ftp server, thereby improving the verification efficiency of billing data.

Optionally, it is also possible to upload the verification information of the verification method of the billing data to the blockchain.

Specifically, the verification information is obtained by running the verification method of the billing data, and is used to record the verification status of the billing data, for example, the file name of the acquired billing file, the parsed original billing data, the The extracted bill data to be verified, the obtained reference bill data, the verification result of the bill data to be verified, and so on. Uploading verification information to the blockchain ensures its security and fairness and transparency to users. The user can download the verification information from the blockchain, so as to check whether the verification information of the verification method of the billing data has been tampered with. The blockchain referred to in this example is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain, essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

Embodiment 2

Please refer to FIG. 2 , which is a schematic structural diagram of an apparatus for verifying billing data disclosed in an embodiment of the present application. As shown in Figure 2, the verification device for billing data may include:

an obtaining module 201, configured to obtain a bill file containing bill data to be verified;

A parsing module 202, configured to input the billing file into a file parser corresponding to the file format of the billing file for parsing to obtain original billing data corresponding to the billing file;

A determination module 203, configured to determine the standard data type corresponding to the billing file according to the upload channel identifier corresponding to the billing file;

an extraction module 204, configured to extract the data of the standard data type from the original bill data, as the bill data to be verified contained in the bill file;

The obtaining module 201 is further configured to obtain reference bill data to be used for the verification of the bill data to be verified;

The verification module 205 is configured to verify the bill data to be verified according to the reference bill data, and obtain a verification result corresponding to the bill data to be verified, and the verification result is used to indicate that the verification of the bill data to be verified has passed or verification failed;

In an optional embodiment, the extraction module 204 is further configured to verify the bill data to be verified according to the reference bill data in the verification module 205 to obtain the verification corresponding to the bill data to be verified After the result, when the verification result is used to indicate that the verification of the to-be-verified bill data fails, extract the unverified differential bill data from the to-be-verified bill data;

The obtaining module 201 is further configured to obtain target billing data for verifying the differential billing data;

And, the device also includes:

A difference verification module, configured to perform difference verification on the difference bill data according to the target bill data, and obtain a difference verification result corresponding to the difference bill data, where the difference verification result is used to represent the difference verification of the difference bill data Pass or fail.

In an optional embodiment, the apparatus further includes:

The sending module is configured to, after the difference verification module performs the difference verification on the difference bill data according to the target bill data, and obtains the difference verification result corresponding to the difference bill data, when the difference verification result is used to indicate the difference verification result. When the verification of the differential bill data fails, the bill data to be manually checked is sent to a predetermined manual check terminal, and the bill data to be checked manually refers to the differential bill data that has not passed the differential verification;

a receiving module, configured to receive a manual check result input by a user at the manual check terminal based on the bill data to be checked manually, where the manual check result is used to indicate that the bill data to be checked manually is valid or invalid;

The account reconciliation module is configured to, when the manual inspection result received by the receiving module is used to indicate that the bill data to be manually inspected is valid, execute the corresponding process of the bill data to be manually inspected for the bill data to be manually inspected. Balance operation.

In an optional embodiment, the apparatus further includes:

The judgment module is configured to judge whether the reference bill data and the target bill data exist in the reference bill data and the target bill data when the manual check result received by the receiving module is used to indicate that the bill data to be checked manually is invalid. Manually check similar billing data with similar billing data;

The sending module is further configured to send the similar bill data to the manual checking terminal when the judgment module judges that the similar bill data exists in the reference bill data and the target bill data.

And, the verification module 205 verifies the bill data to be verified according to the reference bill data, and the specific manner of obtaining the verification result corresponding to the bill data to be verified is as follows:

In an optional embodiment, the specific manner in which the acquiring module 201 acquires the bill file containing the bill data to be verified is:

For the specific description of the apparatus for verifying the billing data, reference may be made to the specific description of the method for verifying the billing data, which will not be repeated here.

Embodiment 3

Please refer to FIG. 3 , which is a schematic structural diagram of a computer device disclosed in an embodiment of the present application. As shown in Figure 3, the computer equipment may include:

a memory 301 storing executable program code;

a processor 302 connected to the memory 301;

The processor 302 invokes the executable program code stored in the memory 301 to execute the steps in the method for verifying billing data disclosed in Embodiment 1 of the present application.

Embodiment 4

The embodiment of the present application discloses a computer storage medium 401, where the computer storage medium 401 stores computer instructions, and when the computer instructions are invoked, is used to execute the steps in the method for verifying billing data disclosed in the first embodiment of the present application. The computer storage medium 401 may be non-volatile or volatile.

The device embodiments described above are only illustrative, wherein the modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in One place, or it can be distributed over multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. Those of ordinary skill in the art can understand and implement it without creative effort.

Claims

1. A method for verifying billing data, wherein the method comprises:

Obtain a billing file containing billing data to be verified;

2. The method for verifying billing data according to claim 1, wherein after verifying the billing data to be verified according to the reference billing data, and obtaining a verification result corresponding to the billing data to be verified, the Methods also include:

3. The method for verifying billing data according to claim 2, wherein after performing differential verification on the differential billing data according to the target billing data, and obtaining a differential verification result corresponding to the differential billing data, the Methods also include:

4. The method for verifying billing data according to claim 3, wherein after receiving the manual checking result input by the user at the manual checking terminal based on the billing data to be checked manually, the method further comprises:

5. The method for verifying billing data according to any one of claims 1-4, wherein the billing data to be verified includes at least one transaction record to be verified, and each transaction record to be verified includes at least the transaction record to be verified. The record identifier and transaction information corresponding to the billing record, the reference billing data includes at least one reference transaction record, and each of the reference transaction records includes at least the record identifier and transaction information corresponding to the reference transaction record;

6. The method for verifying billing data according to any one of claims 1-4, wherein the acquiring the billing file containing the billing data to be verified comprises:

7. A device for verifying billing data, wherein the device comprises:

8. The device for verifying billing data according to claim 7, wherein the extracting module is further configured to verify the billing data to be verified according to the reference billing data in the verification module to obtain the billing data to be verified. After verifying the verification result corresponding to the bill data, when the verification result is used to indicate that the verification of the to-be-verified bill data fails, extract the differential bill data that fails the verification from the to-be-verified bill data;

The obtaining module is further configured to obtain target billing data for verifying the differential billing data;

And, the device also includes:

9. A computer device, wherein the computer device comprises:

a memory in which executable program code is stored;

a processor connected to the memory;

Obtain a billing file containing billing data to be verified;

10. The computer device according to claim 9, wherein after the verification of the to-be-verified bill data according to the reference bill data to obtain a verification result corresponding to the to-be-verified bill data, the method further comprises: :

11. The computer device according to claim 10, wherein after performing the difference verification on the difference bill data according to the target bill data, and obtaining a difference verification result corresponding to the difference bill data, the method further comprises: :

12. The computer device according to claim 11, wherein after receiving the manual check result input by the user at the manual check terminal based on the bill data to be checked manually, the method further comprises:

13. The computer device according to any one of claims 9-12, wherein the bill data to be verified includes at least one transaction record to be verified, and each transaction record to be verified at least includes the corresponding bill record to be verified. The record identifier and transaction information of the reference bill data include at least one reference transaction record, and each of the reference transaction records includes at least the record identifier and transaction information corresponding to the reference transaction record;

14. The computer device according to any one of claims 9-12, wherein said obtaining a billing file containing billing data to be verified comprises:

15. A computer storage medium storing a computer program, wherein, when the computer program is executed by a processor, the following method is implemented:

Obtain a billing file containing billing data to be verified;

16. The computer storage medium according to claim 15, wherein after the verification of the bill data to be verified according to the reference bill data and obtaining the verification result corresponding to the bill data to be verified, the method further include:

17. The computer storage medium according to claim 16, wherein after the difference verification is performed on the differential billing data according to the target billing data, and a differential verification result corresponding to the differential billing data is obtained, the method further comprises: include:

18. The computer storage medium according to claim 17, wherein after receiving the manual checking result input by the user at the manual checking terminal based on the bill data to be checked manually, the method further comprises:

19. The computer storage medium according to any one of claims 15-18, wherein the bill data to be verified comprises at least one transaction record to be verified, and each transaction record to be verified includes at least the bill record to be verified Corresponding record identifiers and transaction information, the reference bill data includes at least one reference transaction record, and each of the reference transaction records includes at least the record identifier and transaction information corresponding to the reference transaction record;

20. The computer storage medium according to any one of claims 15-18, wherein the obtaining a billing file containing billing data to be verified comprises: