WO2022142040A1 - Procédé et appareil de vérification de données de facturation, dispositif informatique et support de stockage - Google Patents

Procédé et appareil de vérification de données de facturation, dispositif informatique et support de stockage Download PDF

Info

Publication number
WO2022142040A1
WO2022142040A1 PCT/CN2021/091690 CN2021091690W WO2022142040A1 WO 2022142040 A1 WO2022142040 A1 WO 2022142040A1 CN 2021091690 W CN2021091690 W CN 2021091690W WO 2022142040 A1 WO2022142040 A1 WO 2022142040A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
verified
billing
bill
bill data
Prior art date
Application number
PCT/CN2021/091690
Other languages
English (en)
Chinese (zh)
Inventor
楚亚兵
黑晓群
Original Assignee
平安普惠企业管理有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安普惠企业管理有限公司 filed Critical 平安普惠企业管理有限公司
Publication of WO2022142040A1 publication Critical patent/WO2022142040A1/fr

Links

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

Definitions

  • 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.
  • 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.
  • manual reconciliation is prone to omission of bills, and the required labor costs are also very huge.
  • many companies have developed their own automated reconciliation systems.
  • the current reconciliation system has a low degree of automation and fails to realize the automation of reconciliation well.
  • 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.
  • 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.
  • a first aspect of the present application discloses a method for verifying billing data, the method comprising:
  • 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;
  • the bill file is a file in multiple file formats, and bill files in different file formats correspond to different file parsers.
  • a third aspect of the present application discloses a computer device, the computer device comprising:
  • the bill file is a file in multiple file formats, and bill files in different file formats correspond to different file parsers.
  • 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:
  • the bill file is a file in multiple file formats, and bill files in different file formats correspond to different file parsers.
  • 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.
  • FIG. 1 is a schematic flowchart of a method for verifying billing data disclosed in an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a device for verifying billing data disclosed in an embodiment of the present application
  • FIG. 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.
  • 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.
  • 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:
  • the bill file may be a file in multiple file formats, and the bill file in different file formats corresponds to different file parsers.
  • the file format of the obtained bill file may be word format, excel format, txt format, or the like.
  • 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).
  • the reconciliation system is the most important part of the payment system. It is at the end of the entire payment process.
  • the bill file can be uploaded by the terminal of the third-party payment channel or the terminal of the bank.
  • 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.
  • 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.
  • 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.
  • 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" .
  • the data included in the parsed original billing data is usually messy and redundant.
  • 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.
  • Bank A 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.
  • only the data in the fields that need to be compared can be extracted as the bill data to be verified.
  • 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.
  • the billing data the data in the transaction date field is extracted as the billing data to be verified.
  • 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.
  • 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.
  • the method further includes:
  • 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.
  • 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.
  • a transaction record without a corresponding transaction flow record is extracted from the to-be-verified bill data as the differential bill data.
  • 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.
  • the method further includes:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the method further includes:
  • the similar bill data is sent to the manual checking terminal.
  • the bill data to be manually inspected is likely to be incorrect data.
  • 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.
  • 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).
  • 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 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 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;
  • 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:
  • 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.
  • 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.
  • the acquiring a billing file containing billing data to be verified includes:
  • a third-party payment channel or the bank's 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.
  • 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.
  • 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.
  • the bill file upload can be completed within 30 minutes. If the bill file upload time exceeds 30 minutes, the server may freeze.
  • 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.
  • 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.
  • 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.
  • FIG. 2 is a schematic structural diagram of an apparatus for verifying billing data disclosed in an embodiment of the present application.
  • 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;
  • the bill file is a file in multiple file formats, and bill files in different file formats correspond to different file parsers.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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:
  • the specific manner in which the acquiring module 201 acquires the bill file containing the bill data to be verified is:
  • FIG. 3 is a schematic structural diagram of a computer device disclosed in an embodiment of the present application.
  • the computer equipment may include:
  • a memory 301 storing executable program code
  • 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.
  • 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.
  • 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.

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

L'invention concerne un procédé de vérification de données de facturation qui comprend les étapes suivantes : obtenir un fichier de facturation contenant des données de facturation à vérifier (101) ; appliquer le fichier de facturation à l'entrée d'un analyseur de fichiers correspondant à un format de fichier du fichier de facturation à des fins d'analyse pour obtenir des données de facturation d'origine correspondant au fichier de facturation (102) ; déterminer, selon un identifiant de canal de téléversement correspondant au fichier de facturation, un type de données standard correspondant au fichier de facturation (103) ; extraire des données relatives au type de données standard, des données de facturation d'origine en tant que données de facturation à vérifier contenues dans le fichier de facturation (104) ; obtenir des données de facturation de référence à utiliser pour vérifier les données de facturation à vérifier (105) ; et vérifier, selon les données de facturation de référence, les données de facturation à vérifier afin d'obtenir un résultat de vérification correspondant aux données de facturation à vérifier, le résultat de vérification étant utilisé pour indiquer que les données de facturation à vérifier ont passé ou échoué la vérification (106). L'invention permet d'améliorer le degré d'automatisation d'un système de rapprochement, et par conséquent de mieux mettre en oeuvre l'automatisation du rapprochement.
PCT/CN2021/091690 2020-12-29 2021-04-30 Procédé et appareil de vérification de données de facturation, dispositif informatique et support de stockage WO2022142040A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011590424.X 2020-12-29
CN202011590424.XA CN112669008A (zh) 2020-12-29 2020-12-29 账单数据的验证方法、装置、计算机设备以及存储介质

Publications (1)

Publication Number Publication Date
WO2022142040A1 true WO2022142040A1 (fr) 2022-07-07

Family

ID=75411770

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/091690 WO2022142040A1 (fr) 2020-12-29 2021-04-30 Procédé et appareil de vérification de données de facturation, dispositif informatique et support de stockage

Country Status (2)

Country Link
CN (1) CN112669008A (fr)
WO (1) WO2022142040A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115936886A (zh) * 2023-03-15 2023-04-07 深圳华锐分布式技术股份有限公司 异构证券交易系统的失效检测方法、装置、设备及介质
CN116702024A (zh) * 2023-05-16 2023-09-05 见知数据科技(上海)有限公司 流水数据类型识别方法、装置、计算机设备和存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112669008A (zh) * 2020-12-29 2021-04-16 平安普惠企业管理有限公司 账单数据的验证方法、装置、计算机设备以及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
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
CN110188136A (zh) * 2019-06-10 2019-08-30 四川长虹电器股份有限公司 一种基于银企直联的组件化对账系统及其对账方法
CN110659965A (zh) * 2019-09-24 2020-01-07 北京腾赋网络科技有限公司 一种自动反映外卖订单的账单差异的控制方法
CN112669008A (zh) * 2020-12-29 2021-04-16 平安普惠企业管理有限公司 账单数据的验证方法、装置、计算机设备以及存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107888672A (zh) * 2017-11-02 2018-04-06 深圳市牛鼎丰科技有限公司 账单数据处理方法、装置、存储介质和计算机设备
CN109325028A (zh) * 2018-08-22 2019-02-12 平安普惠企业管理有限公司 一种对账文件验证方法及终端设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
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
CN110188136A (zh) * 2019-06-10 2019-08-30 四川长虹电器股份有限公司 一种基于银企直联的组件化对账系统及其对账方法
CN110659965A (zh) * 2019-09-24 2020-01-07 北京腾赋网络科技有限公司 一种自动反映外卖订单的账单差异的控制方法
CN112669008A (zh) * 2020-12-29 2021-04-16 平安普惠企业管理有限公司 账单数据的验证方法、装置、计算机设备以及存储介质

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115936886A (zh) * 2023-03-15 2023-04-07 深圳华锐分布式技术股份有限公司 异构证券交易系统的失效检测方法、装置、设备及介质
CN115936886B (zh) * 2023-03-15 2023-06-27 深圳华锐分布式技术股份有限公司 异构证券交易系统的失效检测方法、装置、设备及介质
CN116702024A (zh) * 2023-05-16 2023-09-05 见知数据科技(上海)有限公司 流水数据类型识别方法、装置、计算机设备和存储介质
CN116702024B (zh) * 2023-05-16 2024-05-28 见知数据科技(上海)有限公司 流水数据类型识别方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
CN112669008A (zh) 2021-04-16

Similar Documents

Publication Publication Date Title
WO2022142040A1 (fr) Procédé et appareil de vérification de données de facturation, dispositif informatique et support de stockage
CN108536521B (zh) 基于仿真平台离线环境核对方法及装置
US20020138570A1 (en) System for and method of automatically migrating data among multiple legacy applications and accessible storage formats
CN107463538A (zh) 一种银联文件数据比对方法和系统
CN110598007B (zh) 账单文件处理方法、装置、介质及电子设备
CN117036073B (zh) 基于互联网的发票审核与自动报销系统
CN117036115A (zh) 合同数据的核验方法、装置和服务器
CN113158988A (zh) 财务报表处理方法、装置以及计算机可读存储介质
CN109324963B (zh) 自动测试收益结果的方法及终端设备
CN109582334B (zh) 可编程逻辑器件的升级方法及装置
CN111539725A (zh) 一种差错数据处理方法、装置及系统
WO2023116031A1 (fr) Procédé et appareil de vérification de message, dispositif terminal et support de stockage lisible par ordinateur
CN113704123B (zh) 接口测试方法、装置、设备以及存储介质
CN113050925B (zh) 区块链智能合约修复方法及装置
CN112308523A (zh) 凭证信息的管理方法、装置、设备及存储介质
US20190355053A1 (en) Method, a device and a system of a distributed financial flows auditing
CN113836145B (zh) 请求数据的方法、装置、电子设备及计算机可读存储介质
CN112241328B (zh) 数据处理方法、装置及系统
CN113220594B (zh) 自动化测试方法、装置、设备及存储介质
CN112070470B (zh) 一种年报申报方法、装置、电子设备及存储介质
CN115223292A (zh) 发药机的处理方法、装置、存储介质及电子设备
CN111275550A (zh) 信息处理方法、装置、可读存储介质和电子设备
CN116579866B (zh) 一种基于Spark和Hadoop的数据对账方法及系统
TWI831114B (zh) 跨平台交易與會計分離之完整性驗證方法、系統、電腦裝置及電腦可讀取的記錄媒體
US11405408B2 (en) Method, apparatus and computer program for verifying the integrity of electronic messages

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21912802

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 30/10/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21912802

Country of ref document: EP

Kind code of ref document: A1