CN112669008A - Bill data verification method and device, computer equipment and storage medium - Google Patents
Bill data verification method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112669008A CN112669008A CN202011590424.XA CN202011590424A CN112669008A CN 112669008 A CN112669008 A CN 112669008A CN 202011590424 A CN202011590424 A CN 202011590424A CN 112669008 A CN112669008 A CN 112669008A
- Authority
- CN
- China
- Prior art keywords
- bill
- data
- verified
- bill data
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000013524 data verification Methods 0.000 title abstract description 16
- 238000012795 verification Methods 0.000 claims abstract description 123
- 230000015654 memory Effects 0.000 claims description 17
- 238000007689 inspection Methods 0.000 claims description 6
- 238000000605 extraction Methods 0.000 claims description 2
- 238000004590 computer program Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000012937 correction Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 230000007123 defense Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Data Mining & Analysis (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Finance (AREA)
- Technology Law (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses a bill data verification method, which comprises the following steps: acquiring a bill file containing bill data to be verified; inputting the bill file into a file parser corresponding to the file format of the bill file for parsing to obtain original bill data corresponding to the bill file; determining a standard data type corresponding to the bill file according to the uploading channel identifier corresponding to the bill file; extracting data of a standard data type from the original bill data to serve as bill data to be verified contained in a bill file; acquiring reference bill data to be used for verifying the bill data to be verified; and 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, wherein the verification result is used for indicating that the bill data to be verified passes verification or fails verification. Therefore, the invention can improve the automation degree of the account checking system and better realize the automation of the account checking. The invention also relates to the technical field of block chains.
Description
Technical Field
The invention relates to the technical field of digital assets, in particular to a method and a device for verifying bill data, computer equipment and a storage medium.
Background
The account checking refers to checking and checking the bills in the account book in the accounting for ensuring the correct and reliable records of the account book. The traditional reconciliation work is usually carried out by using a manual reconciliation mode, however, the manual reconciliation is easy to cause the condition of bill omission, and the required labor cost is very huge. In order to improve the reconciliation efficiency and save the labor cost, various companies develop respective automatic reconciliation systems. However, the automation degree of the current reconciliation system is low, and the reconciliation automation cannot be well realized. For example, the current reconciliation system usually cannot automatically acquire a bill file to be reconciled, needs to manually upload the bill file to be reconciled, and cannot automatically analyze the bill file due to various file formats of the bill file (for example, some bill files are word formats and some bill files are excel formats), the reconciliation data in the bill file is scattered, and the like.
Disclosure of Invention
The invention aims to solve the technical problem that the existing reconciliation system has low automation degree and cannot well realize the automation of the reconciliation.
In order to solve the above technical problem, a first aspect of the present invention discloses a method for verifying billing data, where the method includes:
acquiring a bill file containing bill data to be verified;
inputting the bill file into a file parser corresponding to the file format of the bill file for parsing to obtain original bill data corresponding to the bill file;
determining a standard data type corresponding to the bill file according to the uploading channel identifier corresponding to the bill file;
extracting data of the standard data type from the original bill data to serve as bill data to be verified contained in the bill file;
acquiring reference bill data to be used for verifying the bill 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, wherein the verification result is used for indicating that the bill data to be verified passes verification or fails verification;
the bill files are files in various file formats, and the bill files in different file formats correspond to different file parsers.
The second aspect of the present invention discloses a device for verifying bill data, the device comprising:
the acquisition module is used for acquiring a bill file containing bill data to be verified;
the analysis module is used for inputting the bill file into a file analyzer corresponding to the file format of the bill file for analysis to obtain original bill data corresponding to the bill file;
the determining module is used for determining the standard data type corresponding to the bill file according to the uploading channel identifier corresponding to the bill file;
the extraction module is used for extracting the data of the standard data type from the original bill data to be used 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 verifying the bill data to be verified;
the verification module is used for 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, and the verification result is used for indicating that the bill data to be verified passes verification or fails verification;
the bill files are files in various file formats, and the bill files in different file formats correspond to different file parsers.
A third aspect of the present invention discloses a computer apparatus, comprising:
a memory storing executable program code;
a processor coupled to the memory;
the processor calls the executable program code stored in the memory to execute part or all of the steps of the method for verifying the bill data disclosed by the first aspect of the present invention.
In a fourth aspect of the present invention, a computer storage medium is disclosed, wherein the computer storage medium stores computer instructions, and when the computer instructions are called, the computer instructions are used for executing part or all of the steps in the method for verifying the bill data disclosed in the first aspect of the present invention.
In the embodiment of the invention, a bill file containing bill data to be verified and reference bill data used for verifying the bill data to be verified are automatically acquired, after the bill file containing the bill data to be verified is acquired, the bill file is firstly input into a file parser corresponding to the file format of the bill file to perform corresponding parsing operation, original bill data are acquired, the standard data type of the bill file is determined according to an uploading channel of the bill file, data of the standard data type is extracted from the original bill data to be used as the bill data to be verified, and finally the bill data to be verified is verified according to the reference bill data, so that a verification result of the bill data to be verified is acquired. Therefore, the embodiment of the invention can replace the manual form of uploading the account checking data, different file analyzers are used for analyzing the bill file according to different file formats of the bill file, and different types of data are extracted according to different uploading channels of the bill file to serve as the bill data to be verified, so that the bill data to be verified can be accurately extracted from the bill file, the efficiency and the accuracy of bill data verification can be improved, the automation degree of an account checking system can be further improved, and the automation of account checking can be better realized.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for verifying billing data according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a bill data verification apparatus according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer storage medium according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," and the like in the description and claims of the present invention and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, article, or article that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or article.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The invention discloses a bill data verification method, a bill data verification device, computer equipment and a storage medium, which can replace a manual form of uploading account checking data, complete the analysis of a bill file by using different file analyzers according to different file formats of the bill file, and extract different types of data according to different uploading channels of the bill file to serve as the bill data to be verified, so that the bill data to be verified can be accurately extracted from the bill file, the bill data verification efficiency and accuracy can be improved, the automation degree of an account checking system can be improved, and the account checking automation can be better realized. The following are detailed below.
Example one
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a method for verifying billing data according to an embodiment of the present invention. As shown in fig. 1, the verification method of the account data may include the following operations:
101. and acquiring a bill file containing the bill data to be verified.
102. And inputting the bill file into a file analyzer corresponding to the file format of the bill file for analysis to obtain original bill data corresponding to the bill file.
103. And determining the standard data type corresponding to the bill file according to the uploading channel identifier corresponding to the bill file.
104. And extracting the data of the standard data type from the original bill data to serve as the bill data to be verified contained in the bill file.
105. Obtaining reference bill data to be used for performing verification of the bill data to be verified.
106. And 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, wherein the verification result is used for indicating that the bill data to be verified passes verification or fails verification.
In the embodiment of the invention, the bill file can be a file with a plurality of file formats, and the bill files with different file formats correspond to different file parsers. The bill file containing the bill data to be verified is automatically acquired for subsequent bill data verification, so that the bill file does not need to be uploaded manually, and the automation degree of the reconciliation process can be improved. The file format of the obtained bill file may be word format, excel format, txt format, and the like. In the reconciliation system, file parsers corresponding to different file formats may be preset, and are used to perform different parsing operations on the bill files in different file formats to obtain bill data to be verified (described later) included in the bill files. In addition, the account checking system is the most important ring in the payment system, is positioned at the tail end of the whole payment link, is mainly used for ensuring the consistency of transaction flow data of the platform and third-party payment channel or bank bill data, and is the last line of defense for ensuring the fund safety of the payment system. If the reconciliation system is applied to the payment system, the bill file can be uploaded by a terminal of a third-party payment channel or a terminal of a bank, and at this time, the reference bill data can be transaction flow data of a platform where the reconciliation system is located. And comparing the bill data to be verified provided by the third-party payment channel or the bank with transaction running data of the platform, wherein if the bill data to be verified and the transaction running data of the platform are consistent, the bill is correct, the bill data to be verified is verified to pass, and if the bill data to be verified and the transaction running data of the platform are inconsistent, the bill has errors, and the bill data to be verified is not verified to pass.
In the reconciliation system, file analyzers corresponding to different file formats can be preset and used for performing different analysis operations on the bill files in different file formats to obtain the bill data to be verified contained in the bill files. For example, if the file format of the bill file is excel, the corresponding file parser may be an ExcelUtil tool. After the bill file is input into the ExcelUtil tool, whether the name of the bill file is correct or not can be checked, whether the header of the bill file is filled according to a standard file or not can be checked, then the bill file is analyzed into a list set, the content of the bill file is converted into a preset object type, an attribute value corresponding to the header of the form is obtained according to the attribute name, finally, the correctness of the content of the bill file is checked, and if the bill file passes the checking, the original bill data corresponding to the bill file is obtained. The parsed original bill data may include an upload channel identification field for distinguishing an upload channel of the original bill data, and if the upload channel identification field is recorded as "bank a", it indicates that the channel for uploading the original bill data is "bank a". In addition, the parsed raw bill data typically includes cluttered and redundant data, for example, a transaction record in the raw bill data may include serial number, principal, interest, cost, penalty, transaction date, etc. of the transaction record, and different types of data are stored in different fields (e.g., principal for one field, interest for one field, etc.). However, when reconciliation is performed in different channels, the data required for reconciliation is usually different. For example, bank A requires a field for comparing principal when checking account, while bank B does not require a field for comparing principal when checking account, and only requires a field for comparing transaction date. In order to simplify the comparison operation, only the data in the field to be compared can be extracted to be used as the bill data to be verified. And if the bill file is uploaded by the bank A, extracting the data of the principal field from the original bill data corresponding to the bill file to be used as the bill data to be verified, and if the bill file is uploaded by the bank B, extracting the data of the transaction date field from the original bill data corresponding to the bill file to be used as the bill data to be verified. Specifically, a table may be preset, fields (i.e., standard data types) to be compared by different uploading channels may be recorded in the table, and the standard data types of the bill files may be determined by querying the table.
Therefore, the bill data verification method described in fig. 1 can replace a manual form of uploading account checking data, different file analyzers are used for completing analysis of the bill files according to different file formats of the bill files, and different types of data are extracted according to different uploading channels of the bill files to serve as the bill data to be verified, so that the bill data to be verified can be accurately extracted from the bill files, the bill data verification efficiency and accuracy can be improved, the automation degree of an account checking system can be improved, and the account checking automation can be better realized.
In an optional embodiment, after the verifying the to-be-verified bill data according to the reference bill data and obtaining a verification result corresponding to the to-be-verified bill data, the method further includes:
when the verification result is used for indicating that the bill data to be verified is not verified, extracting differential bill data which are not verified from the bill data to be verified;
obtaining target billing data for verification of the differential billing data;
and performing difference verification on the difference bill data according to the target bill data to obtain a difference verification result corresponding to the difference bill data, wherein the difference verification result is used for indicating whether the difference verification of the difference bill data passes or fails.
In this alternative embodiment, when the reconciliation system is used for reconciliation, a data error or a data missing phenomenon sometimes occurs. When data errors or data missing occurs, the transaction records in the bill data to be verified may not correspond to the transaction records of the reference bill data (i.e., the transaction flow records of the platform) one by one, and the absence of the corresponding transaction records of the transaction flow records may cause the bill data to be verified to fail in verification. And when the bill data to be verified is not verified, extracting the transaction records without the corresponding transaction flow records from the bill data to be verified as difference bill data. If the phenomenon of data missing exists, the transaction flow record corresponding to the differential bill data may be the reference bill data subjected to reconciliation processing last time or the reference bill data subjected to reconciliation processing next time, so that the reference bill data subjected to reconciliation processing last time or the reference bill data subjected to reconciliation processing next time can be used as the target bill data to be compared with the differential bill data (i.e. differential verification), if the comparison is passed, the differential verification of the differential bill data is passed, i.e. the data of the differential bill data is correct, only the verification fails due to the data missing, the bill data to be verified in the bill file is still flat, manual verification is not required again, if the comparison is not passed, the differential verification of the differential bill data is not passed, and the data representing the differential bill data is possibly wrong, manual checking and correction are required.
Therefore, by implementing the optional embodiment, when the bill data to be verified is not verified, the bill data to be verified which is not verified can be further verified, so that the verification result is more accurate.
In an optional embodiment, after the differential verification is performed on the differential billing data according to the target billing data to obtain a differential verification result corresponding to the differential billing data, the method further includes:
when the difference verification result is used for indicating that the difference bill data is not verified, sending the bill data to be artificially checked to a predetermined artificial checking terminal, wherein the bill data to be artificially checked is the difference bill data which is not verified;
receiving a manual checking result input by a user at the manual checking terminal based on the bill data to be manually checked, wherein the manual checking result is used for indicating whether the bill data to be manually checked is valid or invalid;
and when the received manual checking result is used for indicating that the bill data to be manually checked is valid, performing account balancing operation corresponding to the bill data to be manually checked according to the bill data to be manually checked.
In this optional embodiment, if the differential billing data fails to pass the differential verification, the differential billing data that fails to pass the differential verification needs to be sent to a manual checking terminal (e.g., a terminal corresponding to a financial staff), and then the financial staff manually checks the differential billing data that fails to pass the differential verification, and if the financial staff manually checks that the differential billing data is correct and valid data, the corresponding tie-down operation is performed on the differential billing data that fails to pass the differential verification. Here, the tie-out operation may be to automatically generate reference bill data corresponding to the differential bill data that is not differentially verified, and then perform a verification once again for the differential bill data that is not differentially verified, thereby enabling the differential bill data that is not differentially verified to be verified. In the reconciliation system, the billing account is a common requirement, and if the billing data is real and effective after manual inspection, the billing data in the reconciliation system can be leveled by executing the reconciliation operation.
Therefore, the optional embodiment can be implemented to manually check the differential bill data which is not verified in the differential bill data verification process, so that the verification result can be more accurate by using a manual checking mode, and when the differential bill data which is not verified in the differential bill data verification process is true and effective, the corresponding tie-out operation is executed, the automatic tie-out operation is realized, and the automation degree of the tie-out system is further improved.
In an optional embodiment, the receiving user follows the manual checking result input by the manual checking terminal based on the to-be-manually-checked bill data, and the method further includes:
when the received manual inspection result is used for indicating that the bill data to be manually inspected is invalid, judging whether similar bill data similar to the bill data to be manually inspected exists in the reference bill data and the target bill data or not;
and when the similar bill data exists in the reference bill data and the target bill data, sending the similar bill data to the manual checking terminal.
In this alternative embodiment, if it is confirmed through the manual inspection that the billing data to be manually inspected is not the real and valid data, the billing data to be manually inspected has larger data which may be wrong. In the reconciliation system, there are many factors causing the wrong bill data, for example, the wrong account data is caused by the misoperation of the user, the data is lost in the transmission process of the bill data, and the like. If the incorrect billing data is caused by some of the less influential factors, the error is usually minor, such as one of the digits missing or changed. At this time, similar bill data similar to the bill data to be manually checked in the reference bill data and the target bill data is inquired first, and then the similar bill data is sent to the manual checking terminal, so that the correction of wrong bill data can be assisted for the user (the user can find the wrong place of the bill data to be manually checked more easily after comparing the similar bill data with the manual checking bill data, and the data correction by the user is facilitated).
Therefore, by implementing the optional embodiment, after the manual checking to be confirmed that the manual checking bill data are wrong data, the similar bill data are sent to the manual checking terminal, so that the user is assisted to correct the wrong manual checking bill data, and the intelligent degree of the checking system is improved.
In an optional embodiment, the to-be-verified bill data includes at least one to-be-verified transaction record, each to-be-verified transaction record includes at least a record identifier and transaction information corresponding to the to-be-verified bill record, the reference bill data includes at least one reference transaction record, and each reference transaction record includes at least a record identifier and transaction information corresponding to the reference transaction record;
and 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, including:
storing all the transaction records to be verified and all the reference transaction records to a Map object of redis;
storing all record identifications corresponding to the transaction records to be verified and all record identifications corresponding to the reference transaction records to a set object of redis;
judging whether all the transaction records to be verified and all the reference transaction records have differences or not based on a redisdiff algorithm;
when all the transaction records to be verified and all the reference transaction records are judged to be different, determining that the verification result corresponding to the bill data to be verified is verification failure;
and when judging that all the transaction records to be verified are not different from all the reference transaction records, determining that the verification result corresponding to the bill data to be verified is verification passing.
In the optional embodiment, the bill data to be verified and the reference bill data are stored in the redis according to the syntax of the redis cache, and then the comparison between the bill data to be verified and the reference bill data is performed by using the redisdiff algorithm, so that the high performance of the redisdiff algorithm can be used, and the data verification speed is improved. The comparison between the bill data to be verified and the reference bill data may include the following modes: comparing whether the number of records in the bill data to be verified and the reference bill data, which are successful in transaction, is consistent, comparing whether the number of all records in the bill data to be verified and the reference bill data is consistent, and comparing whether the record identification and the transaction information (which can include information such as principal, interest, cost, penalty and the like) 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 comparison modes is inconsistent, the verification result corresponding to the bill data to be verified is determined to be verification failure.
Therefore, the optional embodiment can be implemented to compare the bill data to be verified with the reference bill data by using the redisdiff algorithm, so that the high performance of the redisdiff algorithm can be utilized, and the verification efficiency of the bill data is improved.
In an optional embodiment, the obtaining a bill file containing bill data to be verified includes:
obtaining a bill file containing bill data to be verified from a preset target ftp server, wherein the target ftp server is used for storing the bill file uploaded by a third-party system regularly, or,
and calling a bill data downloading interface provided by the third-party system to obtain a bill file containing the bill data to be verified.
In this alternative embodiment, in the payment system, it may be agreed in advance that the bill file is pushed to the designated target ftp server by a third party payment channel or a system of a bank (third party system) at regular time, and then the reconciliation system can obtain the bill file from the target ftp server for verification. Therefore, the efficiency of transmitting the file by using the ftp server can be improved, and the efficiency of obtaining the bill file can be improved. Since the link is disconnected due to the fact that the ftp server downloads or operates a plurality of files for a long time, when the third-party system pushes the bill file to the target ftp server, the link timeout time needs to be set, if the file pushing time exceeds the link timeout time, the target ftp server is determined to be stuck, the target ftp server needs to be re-linked, and the bill file needs to be pushed again, wherein the time interval between re-linking and pushing can be 5-10 minutes (namely, the target ftp server is re-linked every 5-10 minutes). The link timeout time may be set to 30 minutes, and the uploading of the bill file can be completed in 30 minutes theoretically, and if the uploading time of the bill file exceeds 30 minutes, there may be a case that the server is jammed. In addition, some third party payment channels or systems of banks (third party systems) provide a download interface for downloading the bill file, which can be invoked periodically to obtain the bill file.
Therefore, different modes can be provided for acquiring the bill file by implementing the alternative embodiment, and the efficiency of acquiring the bill file can be improved by utilizing the efficiency of file transfer of the ftp server, so that the verification efficiency of the bill data is improved.
Optionally, it is also possible: and uploading verification information of the verification method of the bill data to a block chain.
Specifically, the verification information is obtained by running the verification method of the bill data, and is used for recording the verification condition of the bill data, such as the file name of the acquired bill file, the parsed original bill data, the extracted bill data to be verified, the acquired reference bill data, the verification result of the bill data to be verified, and the like. Uploading the verification information to the blockchain can ensure the safety and the fair transparency to the user. The user may download the verification information from the blockchain to verify whether the verification information of the verification method of the bill data is tampered. The blockchain referred to in this example is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
Example two
Referring to fig. 2, fig. 2 is a schematic structural diagram of a bill data verification apparatus according to an embodiment of the present invention. As shown in fig. 2, the verification device of the account data may include:
an obtaining module 201, configured to obtain a bill file including bill data to be verified;
the analysis module 202 is configured to input the bill file into a file analyzer corresponding to the file format of the bill file to perform analysis, so as to obtain original bill data corresponding to the bill file;
the determining module 203 is configured to determine a standard data type corresponding to the bill file according to the uploading channel identifier corresponding to the bill file;
an extracting module 204, configured to extract data of the standard data type from the original billing data to serve as to-be-verified billing data included in the billing file;
the obtaining module 201 is further configured to obtain reference billing data to be used for verifying the billing data to be verified;
the verification module 205 is configured to verify the billing data to be verified according to the reference billing data to obtain a verification result corresponding to the billing data to be verified, where the verification result is used to indicate that the billing data to be verified passes verification or fails verification;
the bill files are files in various file formats, and the bill files in different file formats correspond to different file parsers.
In an optional embodiment, the extracting module 204 is further configured to, after the verifying module 205 verifies 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, extract differential bill data that is not verified from the to-be-verified bill data when the verification result is used to indicate that the to-be-verified bill data is not verified;
the obtaining module 201 is further configured to obtain target billing data for performing verification of the differential billing data;
and, the apparatus further comprises:
and the difference verification module is used for performing difference verification on the difference bill data according to the target bill data to obtain a difference verification result corresponding to the difference bill data, and the difference verification result is used for indicating whether the difference verification of the difference bill data passes or fails.
In an optional embodiment, the apparatus further comprises:
the sending module is used for sending the bill data to be manually checked to a predetermined manual checking terminal when the difference verification result is used for indicating that the verification of the difference bill data is not passed after the difference verification module performs difference verification on the difference bill data according to the target bill data to obtain a difference verification result corresponding to the difference bill data, wherein the bill data to be manually checked is the difference bill data which is not subjected to the difference verification;
the receiving module is used for receiving a manual checking result input by the user at the manual checking terminal based on the bill data to be manually checked, wherein the manual checking result is used for indicating that the bill data to be manually checked is valid or invalid;
and the account leveling module is used for executing account leveling operation corresponding to the bill data to be artificially checked aiming at the bill data to be artificially checked when the manual checking result received by the receiving module is used for indicating that the bill data to be artificially checked is valid.
In an optional embodiment, the apparatus further comprises:
the judging module is used for judging whether similar bill data similar to the bill data to be artificially checked exists in the reference bill data and the target bill data or not when the manual checking result received by the receiving module is used for indicating that the bill data to be artificially checked is invalid;
the sending module is further configured to send the similar bill data to the manual checking terminal when the judging module judges that the similar bill data exists in the reference bill data and the target bill data.
In an optional embodiment, the to-be-verified bill data includes at least one to-be-verified transaction record, each to-be-verified transaction record includes at least a record identifier and transaction information corresponding to the to-be-verified bill record, the reference bill data includes at least one reference transaction record, and each reference transaction record includes at least a record identifier and transaction information corresponding to the reference transaction record;
the verification module 205 verifies the bill data to be verified according to the reference bill data, and a specific manner of obtaining a verification result corresponding to the bill data to be verified is as follows:
storing all the transaction records to be verified and all the reference transaction records to a Map object of redis;
storing all record identifications corresponding to the transaction records to be verified and all record identifications corresponding to the reference transaction records to a set object of redis;
judging whether all the transaction records to be verified and all the reference transaction records have differences or not based on a redisdiff algorithm;
when all the transaction records to be verified and all the reference transaction records are judged to be different, determining that the verification result corresponding to the bill data to be verified is verification failure;
and when judging that all the transaction records to be verified are not different from all the reference transaction records, determining that the verification result corresponding to the bill data to be verified is verification passing.
In an optional embodiment, the specific way for the obtaining module 201 to obtain the bill file containing the bill data to be verified is as follows:
obtaining a bill file containing bill data to be verified from a preset target ftp server, wherein the target ftp server is used for storing the bill file uploaded by a third-party system regularly, or,
and calling a bill data downloading interface provided by the third-party system to obtain a bill file containing the bill data to be verified.
For the specific description of the verification apparatus of the bill data, reference may be made to the specific description of the verification method of the bill data, which is not described in detail herein.
EXAMPLE III
Referring to fig. 3, fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention. As shown in fig. 3, the computer apparatus may include:
a memory 301 storing executable program code;
a processor 302 connected to the memory 301;
the processor 302 calls the executable program code stored in the memory 301 to execute the steps of the method for verifying the bill data disclosed in the embodiment of the present invention.
Example four
The embodiment of the invention discloses a computer storage medium 401, wherein a computer instruction is stored in the computer storage medium 401, and when the computer instruction is called, the computer instruction is used for executing the steps in the bill data verification method disclosed by the embodiment of the invention.
The above-described embodiments of the apparatus are merely illustrative, and the modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above detailed description of the embodiments, those skilled in the art will clearly understand that the embodiments may be implemented by software plus a necessary general hardware platform, and may also be implemented by hardware. Based on such understanding, the above technical solutions may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, where the storage medium includes a Read-Only Memory (ROM), a Random Access Memory (RAM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), a One-time Programmable Read-Only Memory (OTPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc-Read-Only Memory (CD-ROM), or other magnetic disk memories, magnetic tape memories, magnetic disk drives, magnetic tape drives, and magnetic tape drives, Or any other medium which can be used to carry or store data and which can be read by a computer.
Finally, it should be noted that: the method, apparatus, computer device and storage medium for verifying billing data disclosed in the embodiments of the present invention are only preferred embodiments of the present invention, and are only used for illustrating the technical solutions of the present invention, not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art; the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A method of validating billing data, the method comprising:
acquiring a bill file containing bill data to be verified;
inputting the bill file into a file parser corresponding to the file format of the bill file for parsing to obtain original bill data corresponding to the bill file;
determining a standard data type corresponding to the bill file according to the uploading channel identifier corresponding to the bill file;
extracting data of the standard data type from the original bill data to serve as bill data to be verified contained in the bill file;
acquiring reference bill data to be used for verifying the bill 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, wherein the verification result is used for indicating that the bill data to be verified passes verification or fails verification;
the bill files are files in various file formats, and the bill files in different file formats correspond to different file parsers.
2. The method for verifying the bill data as claimed in claim 1, wherein after the verifying 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 comprises:
when the verification result is used for indicating that the bill data to be verified is not verified, extracting differential bill data which are not verified from the bill data to be verified;
obtaining target billing data for verification of the differential billing data;
and performing difference verification on the difference bill data according to the target bill data to obtain a difference verification result corresponding to the difference bill data, wherein the difference verification result is used for indicating whether the difference verification of the difference bill data passes or fails.
3. The method for verifying the billing data of claim 2, wherein after the differential verification of the differential billing data according to the target billing data and the differential verification result corresponding to the differential billing data is obtained, the method further comprises:
when the difference verification result is used for indicating that the difference bill data is not verified, sending the bill data to be artificially checked to a predetermined artificial checking terminal, wherein the bill data to be artificially checked is the difference bill data which is not verified;
receiving a manual checking result input by a user at the manual checking terminal based on the bill data to be manually checked, wherein the manual checking result is used for indicating whether the bill data to be manually checked is valid or invalid;
and when the received manual checking result is used for indicating that the bill data to be manually checked is valid, performing account balancing operation corresponding to the bill data to be manually checked according to the bill data to be manually checked.
4. The method of verifying bill data as claimed in claim 3, wherein said receiving user follows a result of manual inspection inputted at said manual inspection terminal based on said bill data to be manually inspected, said method further comprising:
when the received manual inspection result is used for indicating that the bill data to be manually inspected is invalid, judging whether similar bill data similar to the bill data to be manually inspected exists in the reference bill data and the target bill data or not;
and when the similar bill data exists in the reference bill data and the target bill data, sending the similar bill data to the manual checking terminal.
5. The method for validating bill data as claimed in any one of claims 1 to 4, wherein the bill data to be validated includes at least one transaction record to be validated, each transaction record to be validated includes at least a record identifier and transaction information corresponding to the bill record to be validated, the reference bill data includes at least one reference transaction record, and each reference transaction record includes at least a record identifier and transaction information corresponding to the reference transaction record;
and 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, including:
storing all the transaction records to be verified and all the reference transaction records to a Map object of redis;
storing all record identifications corresponding to the transaction records to be verified and all record identifications corresponding to the reference transaction records to a set object of redis;
judging whether all the transaction records to be verified and all the reference transaction records have differences or not based on a redisdiff algorithm;
when all the transaction records to be verified and all the reference transaction records are judged to be different, determining that the verification result corresponding to the bill data to be verified is verification failure;
and when judging that all the transaction records to be verified are not different from all the reference transaction records, determining that the verification result corresponding to the bill data to be verified is verification passing.
6. The method for verifying the billing data according to any one of claims 1 to 4, wherein the obtaining of the billing file containing the billing data to be verified comprises:
obtaining a bill file containing bill data to be verified from a preset target ftp server, wherein the target ftp server is used for storing the bill file uploaded by a third-party system regularly, or,
and calling a bill data downloading interface provided by the third-party system to obtain a bill file containing the bill data to be verified.
7. An apparatus for verifying billing data, the apparatus comprising:
the acquisition module is used for acquiring a bill file containing bill data to be verified;
the analysis module is used for inputting the bill file into a file analyzer corresponding to the file format of the bill file for analysis to obtain original bill data corresponding to the bill file;
the determining module is used for determining the standard data type corresponding to the bill file according to the uploading channel identifier corresponding to the bill file;
the extraction module is used for extracting the data of the standard data type from the original bill data to be used 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 verifying the bill data to be verified;
the verification module is used for 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, and the verification result is used for indicating that the bill data to be verified passes verification or fails verification;
the bill files are files in various file formats, and the bill files in different file formats correspond to different file parsers.
8. The device for verifying the billing data according to claim 7, wherein the extracting module is further configured to, after the verifying module verifies the billing data to be verified according to the reference billing data to obtain a verification result corresponding to the billing data to be verified, extract differential billing data that is not verified from the billing data to be verified when the verification result indicates that the billing data to be verified is not verified;
the obtaining module is further configured to obtain target bill data for performing verification of the differential bill data;
and, the apparatus further comprises:
and the difference verification module is used for performing difference verification on the difference bill data according to the target bill data to obtain a difference verification result corresponding to the difference bill data, and the difference verification result is used for indicating whether the difference verification of the difference bill data passes or fails.
9. A computer device, characterized in that the computer device comprises:
a memory storing executable program code;
a processor coupled to the memory;
the processor calls the executable program code stored in the memory to execute the method of verifying billing data according to any of claims 1-6.
10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, implements the method of verifying bill data according to any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011590424.XA CN112669008A (en) | 2020-12-29 | 2020-12-29 | Bill data verification method and device, computer equipment and storage medium |
| PCT/CN2021/091690 WO2022142040A1 (en) | 2020-12-29 | 2021-04-30 | Billing data verification method and apparatus, computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011590424.XA CN112669008A (en) | 2020-12-29 | 2020-12-29 | Bill data verification method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112669008A true CN112669008A (en) | 2021-04-16 |
Family
ID=75411770
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011590424.XA Pending CN112669008A (en) | 2020-12-29 | 2020-12-29 | Bill data verification method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112669008A (en) |
| WO (1) | WO2022142040A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022142040A1 (en) * | 2020-12-29 | 2022-07-07 | 平安普惠企业管理有限公司 | Billing data verification method and apparatus, computer device and storage medium |
| CN116702024A (en) * | 2023-05-16 | 2023-09-05 | 见知数据科技(上海)有限公司 | Method, device, computer equipment and storage medium for identifying type of stream data |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115936886B (en) * | 2023-03-15 | 2023-06-27 | 深圳华锐分布式技术股份有限公司 | Failure detection method, device, equipment and medium for heterogeneous securities trading system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107888672A (en) * | 2017-11-02 | 2018-04-06 | 深圳市牛鼎丰科技有限公司 | Billing data processing method, device, storage medium and computer equipment |
| CN109325028A (en) * | 2018-08-22 | 2019-02-12 | 平安普惠企业管理有限公司 | A kind of reconciliation file verification method and terminal device |
| CN110188136A (en) * | 2019-06-10 | 2019-08-30 | 四川长虹电器股份有限公司 | A kind of modularization reconciliation system and its account checking method based on bank-corporate express |
| CN110659965A (en) * | 2019-09-24 | 2020-01-07 | 北京腾赋网络科技有限公司 | Control method for automatically reflecting bill difference of takeout order |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5822716A (en) * | 1996-07-22 | 1998-10-13 | Atlantic Richfield Company | System and method for generating bills of lading for liquid commodity shipments |
| CN112669008A (en) * | 2020-12-29 | 2021-04-16 | 平安普惠企业管理有限公司 | Bill data verification method and device, computer equipment and storage medium |
-
2020
- 2020-12-29 CN CN202011590424.XA patent/CN112669008A/en active Pending
-
2021
- 2021-04-30 WO PCT/CN2021/091690 patent/WO2022142040A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107888672A (en) * | 2017-11-02 | 2018-04-06 | 深圳市牛鼎丰科技有限公司 | Billing data processing method, device, storage medium and computer equipment |
| CN109325028A (en) * | 2018-08-22 | 2019-02-12 | 平安普惠企业管理有限公司 | A kind of reconciliation file verification method and terminal device |
| CN110188136A (en) * | 2019-06-10 | 2019-08-30 | 四川长虹电器股份有限公司 | A kind of modularization reconciliation system and its account checking method based on bank-corporate express |
| CN110659965A (en) * | 2019-09-24 | 2020-01-07 | 北京腾赋网络科技有限公司 | Control method for automatically reflecting bill difference of takeout order |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022142040A1 (en) * | 2020-12-29 | 2022-07-07 | 平安普惠企业管理有限公司 | Billing data verification method and apparatus, computer device and storage medium |
| CN116702024A (en) * | 2023-05-16 | 2023-09-05 | 见知数据科技(上海)有限公司 | Method, device, computer equipment and storage medium for identifying type of stream data |
| CN116702024B (en) * | 2023-05-16 | 2024-05-28 | 见知数据科技(上海)有限公司 | Method, device, computer equipment and storage medium for identifying type of stream data |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022142040A1 (en) | 2022-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112669008A (en) | Bill data verification method and device, computer equipment and storage medium | |
| CN112668303A (en) | Data processing method, device, equipment and storage medium | |
| CN113468491A (en) | API service engine method, system, electronic equipment and computer readable storage medium | |
| CN107463538A (en) | A kind of Unionpay's file data comparison method and system | |
| CN110020550B (en) | Assessment method, device and equipment for verification platform | |
| CN110853216B (en) | Information storage method, information storage device, information storage medium and computer equipment | |
| CN115373868A (en) | Intelligent data processing system and method | |
| CN114338850B (en) | Message checking method, device, terminal equipment and computer readable storage medium | |
| CN109324963B (en) | Method for automatically testing profit result and terminal equipment | |
| CN112232962A (en) | Transaction index processing method, device and equipment | |
| CN117314662A (en) | Intelligent account checking method, system, equipment and storage medium | |
| CN112241328B (en) | Data processing method, device and system | |
| CN113704123B (en) | Interface testing method, device, equipment and storage medium | |
| CN114418775A (en) | Method, device, equipment and medium for checking annual fund investment data | |
| CN116957785A (en) | Channel account checking method, device, electronic equipment and computer program product | |
| CN113988793A (en) | Method and system for checking value-added tax electronic invoice | |
| CN113506006A (en) | Transaction confirmation method, device, medium and equipment of peer business system | |
| CN112990922A (en) | Batch payment method, device, equipment and storage medium | |
| CN112308523A (en) | Management method, device, equipment and storage medium of certificate information | |
| CN113779065B (en) | Verification method, device, terminal equipment and medium for data comparison | |
| CN113220594B (en) | Automatic test method, device, equipment and storage medium | |
| KR101088054B1 (en) | Test system and test method for the message based communication system | |
| CN113360491B (en) | Data quality inspection method, device, electronic equipment and storage medium | |
| CN118586869A (en) | Invoice processing method, invoice processing device, invoice processing equipment and invoice processing storage medium | |
| CN110673888B (en) | Verification method and device for configuration file |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |