WO2024055779A1

WO2024055779A1 - Bill processing method and apparatus

Info

Publication number: WO2024055779A1
Application number: PCT/CN2023/111714
Authority: WO
Inventors: 刘晓彩; 洪飞宇
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2022-09-15
Filing date: 2023-08-08
Publication date: 2024-03-21
Also published as: CN115423461A

Abstract

Provided in the embodiments of the present specification are a bill processing method and apparatus, the bill processing method comprising: carrying out data cleaning on bill data of a check period in an account period to obtain a reference bill set; adding abnormal bills of a previous check period to the reference bill set to obtain an incremental bill set of the check period; and checking the incremental bill set and a corresponding bill set to be checked, obtaining abnormal bills of the check period and adding same to an abnormal bill set so as to be used for bill auditing, the bill auditing being carried out, after the account period ends, on the basis of the abnormal bill set and a bill summarizing result of the account period, and, after the auditing passes, a note application being made.

Description

Bill processing method and device

Technical field

This document relates to the field of data processing technology, and in particular to a bill processing method and device.

Background technique

With the development of Internet technology and the popularization of mobile terminals, more and more services have begun to extend to online scenarios, such as transactions, invoice issuance, etc. Online scenarios have become more and more frequent and convenient, and subsequently online-based services have emerged. The above-mentioned integrated transaction and invoice issuance processing process, but as the transaction methods in the online scenario become more and more complex and diverse, higher requirements are put forward for the transaction and invoice issuance processing process.

Contents of the invention

One or more embodiments of this specification provide a bill processing method, which includes: performing data cleaning on the bill data of the reconciliation period within the accounting period to obtain a benchmark bill set. Add the abnormal bills of the previous reconciliation cycle to the base bill set to obtain the incremental bill set of the reconciliation cycle. The incremental bill set is reconciled with the corresponding bill set to be verified, and the abnormal bills of the verification period are obtained and added to the abnormal bill set for bill review. The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed.

One or more embodiments of this specification provide a bill processing device, which includes: performing data cleaning on the bill data of the reconciliation period within the accounting period to obtain a benchmark bill set. Add the abnormal bills of the previous reconciliation cycle to the base bill set to obtain the incremental bill set of the reconciliation cycle. The incremental bill set is reconciled with the corresponding bill set to be verified, and the abnormal bills of the verification period are obtained and added to the abnormal bill set for bill review. The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed.

One or more embodiments of the present specification provide a bill processing device, including: a processor; and, a memory configured to store computer-executable instructions that, when executed, cause the processor to: Perform data cleaning on the bill data of the reconciliation period within the accounting period to obtain a baseline bill set. Add the abnormal bills of the previous reconciliation cycle to the base bill set to obtain the incremental bill set of the reconciliation cycle. The incremental bill set is reconciled with the corresponding bill set to be verified, and the abnormal bills of the verification period are obtained and added to the abnormal bill set for bill review. Wherein, the bill review is based on the abnormal bill set and The bill summary results within the accounting period are carried out, and the bill application is made after the review is passed.

One or more embodiments of this specification provide a storage medium for storing computer-executable instructions. When executed by a processor, the computer-executable instructions implement the following process: perform reconciliation of bill data of the reconciliation cycle within the accounting period. Data cleaning to obtain a baseline bill set. Add the abnormal bills of the previous reconciliation cycle to the base bill set to obtain the incremental bill set of the reconciliation cycle. The incremental bill set is reconciled with the corresponding bill set to be verified, and the abnormal bills of the verification period are obtained and added to the abnormal bill set for bill review. The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed.

Description of drawings

In order to more clearly illustrate the technical solutions in one or more embodiments of this specification, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only used in this specification. For some of the embodiments recorded, those of ordinary skill in the art can also obtain other drawings based on these drawings without exerting creative efforts.

Figure 1 is a processing flow chart of a bill processing method provided by one or more embodiments of this specification.

Figure 2 is a schematic diagram of an organization code bill processing scenario provided by one or more embodiments of this specification.

Figure 3 is a processing flow chart of a bill processing method applied to an organization code scenario provided by one or more embodiments of this specification.

Figure 4 is a schematic diagram of a bill processing device provided by one or more embodiments of this specification.

Figure 5 is a schematic structural diagram of a bill processing device provided by one or more embodiments of this specification.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the following will describe the technical solutions in one or more embodiments of this specification in conjunction with the drawings in one or more embodiments of this specification. The technical solution is described clearly and completely. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the protection scope of this document.

An embodiment of a bill processing method provided in this specification: The bill processing method provided by this application performs data cleaning on the bill data of the current verification period within the accounting period to obtain the benchmark bill set of the current verification period, and combine the previous The abnormal bills of a verification cycle are added to the base bill set to obtain the incremental bill set of the current verification cycle, and the incremental bill set of the current verification cycle is reconciled with the corresponding bill set to be verified, so as to achieve treatment with the help of the incremental bill set The verification processing of the bill set and obtaining the abnormal bills of the current verification cycle improves the efficiency and accuracy of bill verification; further, by adding the abnormal bills obtained by the verification processing to the abnormal bill set, it provides information for the bill review of the current accounting period. Data preparation, so that after the end of the current accounting period, the bill can be reviewed based on the incremental bill set and the bill summary results in the current accounting period, and the corresponding bill application can be made after the review is passed, so as to build on more accurate billing data. On the other hand, bill application is implemented based on bills, making the bill application process more convenient and effective.

Step S102: Perform data cleaning on the bill data of the reconciliation period within the accounting period to obtain a benchmark bill set.

The verification cycle within the accounting period described in this embodiment refers to the time period for bill verification within an accounting period. For example, every day in the accounting period is regarded as a verification accounting period. This embodiment uses any period within the accounting period. One reconciliation cycle (current reconciliation cycle) is taken as an example for description. The implementation of other reconciliation cycles within the accounting period is similar to the current reconciliation cycle, and will not be described in detail in this embodiment. The bill data refers to the bill data of all transactions conducted within the verification period; the base bill set refers to the bill set consisting of the remaining bills after cleaning specific bills in the bill data of all transactions. Specifically, Specific bills refer to bills that are not related to the unapproved bills in the following set of unapproved bills. The remaining bills after cleaning are related to or related to the unapproved bills in the set of unapproved bills.

In this embodiment, since the bill data contains the bill data of all transactions performed within the verification period, the purpose of data cleaning is to clean out the bills in the bill data that are not related to the bills to be verified in the following set of bills to be verified. , retain the bills related to the pending bills for subsequent verification processing of the centralized pending bills.

In an optional implementation provided by this embodiment, performing data cleaning on the bill data of the reconciliation period within the accounting period to obtain a benchmark bill set includes: reading the type tag of each bill in the bill data; the type The tags include a first tag corresponding to the payment with the institution code and a second tag corresponding to the payment with the non-institution code; clean the bills of the second tag in the bill data to obtain the benchmark composed of the bills of the first tag. Bill set.

Among them, the organization code payment refers to the payment processing using the organization code. The organization code refers to the payment code or identification code set by the organization for the payment, invoicing amount/or reimbursement of the organization members. The organization code can uniquely identify Organization, organization code can exist in the form of QR code, bar code, voice code and other identification codes. The non-organization code payment refers to payment processing that does not use the organization code for payment processing and uses other payment methods, such as payment processing using the user's own payment code, or payment processing using the merchant's collection code. .

It should be noted that, in addition to the above-mentioned implementation of data cleaning of the bill data of the verification period, during the process of data cleaning of the bill data of the verification period, the bill data can also be cleaned. machine Bills other than the institutional code bills are cleaned to obtain the benchmark bill set consisting of organization code bills.

Step S104: Add the abnormal bills of the previous verification period to the base bill set to obtain an incremental bill set of the verification period.

During specific implementation, the abnormal bills of the previous reconciliation cycle are added to the benchmark bill set of the current reconciliation cycle to ensure that the benchmark data relied on for reconciliation processing of the following bill sets to be reconciled is comprehensive and effective, and so on. , the abnormal bills of the current verification cycle will be added to the baseline bill set of the next verification cycle to form the incremental bill set of the next verification cycle, thereby ensuring the accuracy and comprehensiveness of bill verification.

In an optional implementation provided by this embodiment, the abnormal bills of the previous verification cycle are obtained in the following manner: the incremental bill set of the previous verification cycle is verified against the corresponding bill set to be verified. , obtain the abnormal bill of the previous reconciliation period.

Here, the process of verifying the incremental bill set of the previous verification cycle with the corresponding bill set to be verified is the same as the process of verifying the incremental bill set of the current verification cycle with the corresponding bill set to be verified as described below. The process of the verification process is similar. Please refer to the implementation method of the verification process provided below, which will not be described again in this embodiment.

The above-mentioned data cleaning provided by this embodiment and adding the abnormal bills of the previous verification cycle to the base bill set of the current verification cycle to obtain an incremental bill set are intended to verify the bill set to be verified corresponding to the incremental bill set. That is, the incremental bill set of the current verification cycle is used as the reference data for checking the following bill sets to be verified during the verification process. Optionally, the bills to be verified in the bill set to be verified include agency code bills. Correspondingly, The set of bills to be verified consists of organization code bills; wherein the organization code bills are generated after payment processing based on the organization code of the organization.

On the basis that the bill set to be verified is composed of agency code bills, the bill set to be verified corresponding to the incremental bill set refers to the bill set to be verified consisting of agency code bills corresponding to the current verification cycle (the current verification cycle corresponds to The set of bills to be verified), optionally, the set of bills to be verified corresponding to the current verification period is included in the bill summary results in the accounting period, and the current verification can be read from the bill summary results in the accounting period The set of bills to be approved corresponding to the cycle.

In an optional implementation provided by this embodiment, the bill summary result is determined in the following manner: aggregating the agency code bills associated with the account period to obtain the bill summary result; the agency code bill It is associated to the accounting period after being calculated and determined to belong to the accounting period.

Optionally, the aggregation process is implemented in at least one of the following ways: aggregating the agency code bills associated with the account period according to the reconciliation period to obtain a set of bills to be verified consisting of agency code bills for each reconciliation period. Calculate the total bill amount of each reconciliation cycle based on the bill amount of the agency code bill in each reconciliation period during the accounting period. Calculate the total billing amount of each reconciliation cycle based on the agency code bill of each reconciliation cycle. Calculate the bill items of the agency code bill in each reconciliation cycle. number.

Optionally, the bill summary result includes at least one of the following: a set of bills to be verified consisting of agency code bills in each reconciliation period within the accounting period, and a total bill calculated based on the bill amount of the agency code bills in each reconciliation period. The bill amount, the total amount of invoices in each verification cycle, and the number of bills issued by the organization code in each verification cycle.

In practical applications, the bill review and bill application processes provided by this embodiment need to be carried out after all verification processes in each verification cycle within the accounting period are completed. In view of this, in order to improve the bill review and bill application process, For processing efficiency and processing timeliness, this embodiment provides the above-mentioned data cleaning and adding the abnormal bills of the previous verification cycle to the base bill set of the current verification cycle to obtain an incremental bill set, and the following increment of the current verification cycle The process of checking the bill set with the corresponding bill set to be verified can be carried out based on the offline system, so that bill review and bill application can be carried out based on the abnormal bill set calculated in advance based on the offline system.

Step S106: Check the incremental bill set with the corresponding bill set to be verified, obtain the abnormal bills in the verification period, and add them to the abnormal bill set for bill review.

During specific implementation, in the process of verifying the set of bills to be verified corresponding to the verification period using the incremental bill set of the verification period, in order to improve the accuracy and effectiveness of the verification processing of the bill set to be verified, from At least one verification dimension is used to perform verification processing on the bill set to be verified. In an optional implementation manner provided in this embodiment, the incremental bill set is verified against the corresponding bill set to be verified to obtain the verification period. Abnormal bills are added to the abnormal bill set, including: reconciling the bills in the incremental bill set with the bills to be verified in the bill set to be verified in at least one verification dimension; and verifying the exceptions in each verification dimension obtained by the verification process The bill is added to the set of exception bills.

The verification dimensions include: a bill verification dimension that checks whether the entire bill is consistent or a corresponding bill at the bill level, and/or an amount verification dimension that checks whether the bill amount is consistent at the bill amount level.

Specifically, in an optional implementation provided by this embodiment, the reconciliation process of the bills in the incremental bill set and the bills to be verified in the bill set to be verified in at least one verification dimension includes: verification Whether the bills in the incremental bill set have corresponding bills to be verified in the bill set to be verified, and according to the verification results, the bills that do not have corresponding bills to be verified in the incremental bill set are used as abnormal bills in the bill verification dimension; And/or, check whether the bill amount of the bill in the incremental bill set is consistent with the bill amount of the corresponding unverified bill in the unverified bill set, and use the bill with inconsistent bill amount as an abnormal bill in the amount verification dimension based on the verification result. .

Here, by checking the bill set to be verified corresponding to the current verification cycle and the incremental bill set of the current verification cycle, the Single-level consistency, inconsistent bills that do not exist in the set of bills to be verified but exist in the set of incremental bills are treated as abnormal bills to avoid bills that fail to pass the bill review due to data delay or bill loss during the bill application process. The application cannot be processed to ensure smooth execution of bill application. In addition, by checking the consistency of the bill set to be verified corresponding to the current verification cycle and the incremental bill set of the current verification cycle at the bill amount level, bills with inconsistent bill amounts are treated as abnormal bills to avoid errors in bill application.

In addition, in order to further improve the accuracy and comprehensiveness of bill verification, you can also check the bills to be verified corresponding to the current verification cycle based on the total bill amount of the centralized bills to be verified corresponding to the current verification cycle. To reduce the probability of errors in the bill review or bill application process for bills to be verified, this embodiment provides an optional implementation method to calculate the total bill amount of the bills to be verified in the set of bills to be verified; combine the total amount of the bill with Check the total bill amount of the verification period included in the bill summary result; after obtaining the verification result, if the verification result is that the total bill amount of the two is inconsistent, you can perform the above to compare the incremental bill set with The corresponding set of bills to be verified is subjected to the verification process; if the verification result is that the total amount of the two bills is consistent, no processing is required, or the incremental bill set and the corresponding set of bills to be verified are verified by performing the above process to further improve the accuracy and comprehensiveness of bill verification.

In practical applications, after checking the incremental bill set with the corresponding bill set to be verified and obtaining the abnormal bill, the abnormal bill can be processed for the sake of accounting consistency and the data requirements for subsequent bill review and bill application. Carry out corresponding processing, such as account adjustment processing, to ensure the consistency of accounts and the smooth progress of bill review and bill application. In an optional implementation provided by this embodiment, the incremental bill set and The corresponding bill set to be verified is verified and processed, and the abnormal bills of the verification period are obtained and added to the abnormal bill set for bill review. After that, an adjustment task for the abnormal bill is generated and the adjustment task is performed. Distribute; update the abnormal bills in the abnormal bill set according to the reconciliation data generated after the execution of the reconciliation task.

In this embodiment, the incremental bill set is compared with the corresponding bill set to be verified, and the abnormal bills of the verification period are obtained and added to the abnormal bill set. The purpose is to be able to obtain the abnormal bill set based on the obtained abnormal bill set. Conduct bill review on the system, and apply for a bill if the bill review passes. Optionally, the bill review is conducted after the end of the bill period based on the abnormal bill set and the bill summary results within the bill period. , and apply for a ticket after passing the review.

In an optional implementation provided by this embodiment, the bill review is implemented in the following manner: verifying whether the verification processing of the incremental bill set and the corresponding bill set to be verified in each verification period within the accounting period is completed, That is: verify whether the set of bills to be verified corresponding to each verification cycle in the accounting period has been verified; if so, verify whether the abnormal bills in each verification cycle are empty (or, verify whether the abnormal bill set after verification processing is empty), and if is empty, execute the ticket According to the application; if it is not empty, check whether the bill status of the abnormal bill in the abnormal bill set is the adjusted state. If it is the adjusted state, execute the bill application. If it is the unadjusted state, generate an unadjusted state. If the bill has an unfinished reconciliation cycle between the incremental bill set and the corresponding to-be-checked bill set, no processing will be done, or if the bill is detected When the verification processing of the incremental bill set of each verification cycle and the corresponding bill set to be verified in the bill has been completed, the process of verifying whether the abnormal bills of each verification cycle is empty is performed.

In addition to the implementation methods of bill review provided above, the bill review can also be implemented by any of the three implementation methods provided below: Verify whether the set of bills to be verified corresponding to each verification cycle in the accounting period is verified Completed; if yes, verify whether the billing status of the abnormal bill in the abnormal bill set is the adjusted status. If it is the adjusted status, execute the bill application; if it is the unadjusted status, generate an exception of the unadjusted status. The bill adjustment reminder may not be processed; alternatively, verify whether the set of bills to be verified corresponding to each verification period in the accounting period has been verified; if so, verify whether the abnormal bill set after verification is empty, and if it is empty, execute The bill application; or, verify whether the billing status of the abnormal bill set in the abnormal bill set corresponding to each verification period in the accounting period is the adjusted status. If it is the adjusted status, perform the required Apply for the above bill; if it is in the unadjusted state, an adjustment reminder for the abnormal bill in the unadjusted state will be generated or will not be processed.

During the specific implementation process, in the bill application scenario, there is often a need to combine different bills to apply for bills. On the one hand, it can reduce the workload of the bill application party in bill application, and on the other hand, it can also reduce the bill issuance party in bill issuance. The processing volume of Apply for bills based on the results of the merger process.

Specifically, in an optional implementation provided by this embodiment, the sets of bills to be verified in each verification period within the accounting period are merged, and a bill application is made based on the merged processing results, including: according to the payment corresponding to the bill The institution merges the unverified bills of each payment institution in the account period, obtains the first total bill of each payment institution in the account period, and calls the bill application interface to perform the first total bill. Issuance of bills; wherein, the payment institution refers to an institution that provides funds for payment processing of the bills to be verified in the collection of bills to be verified; when the bills to be verified in the collection of bills to be verified are agency code bills, the payment institution is The institution to which the institution code belongs; or, according to the merchant corresponding to the bill, merge the unverified bills of each merchant in the bill set to be verified in the account period to obtain the second total bill of each merchant in the account period, and Call the bill application interface of each merchant to issue bills for the general bill; or, according to the bill application cycle of the bill, merge the bills to be verified in each bill application cycle to obtain the third total bill for each bill application cycle, and Call the bill application interface to issue bills for the total bill.

It should be noted that the three specific implementation methods for bill application processing provided above can be combined according to actual needs in specific applications. For example, the bill application is implemented in the following ways: according to the reconciliation between the payment institution and the merchant. All bills to be verified during the period are collected and merged with those of each payment institution to obtain the total bill of each payment institution for each merchant during the accounting period, and the bill application interface of each merchant is called to calculate the total bill. Invoice issuance.

When the bills to be verified in the collection of bills to be verified are organization code bills, employees of different organizations of the organization use the organization code to pay and obtain the organization code bill. For the organization, during the bill application process, consumption at the same merchant can be The organization code bills paid by employees of different organizations can be merged and one invoice can be issued for the same merchant. This can greatly save the number of bill applications for the organization and improve the efficiency of bill application.

In addition to the method provided above for merging the bill sets to be verified in each verification cycle within the accounting period and processing the bill application based on the results of the merger, the following methods can also be used to implement the bill application: According to the bill application dimension Consolidate the bill sets to be verified in each verification cycle within the accounting period, and apply for bills based on the results of the consolidation process. The bill application dimension refers to the data dimension based on which data is used as the core for bill application during the bill application process. Optionally, the bill application dimension includes the payment institution dimension, the merchant dimension, and the bill application cycle dimension. For example, in the bill application process, if the payment institution is used as the data core to apply for bills, the bills of the same payment institution will be merged, and then the merged bills will be used to apply for bills. Then the bill application dimension of the current bill application will be the payment institution. dimensions.

It should be noted that, as provided above, the incremental bill set is reconciled with the corresponding bill set to be verified, and the abnormal bills of the verification cycle are obtained and added to the abnormal bill set for bill review. It is replaced by checking the incremental bill set with the corresponding bill set to be verified, obtaining the abnormal bills of the verification period and adding them to the abnormal bill set. Correspondingly, the bill review is completed at the end of the account period. It is then carried out based on the abnormal bill set and the bill summary results in the accounting period, and the bill application is made after the review is passed. It can also be replaced by: If the bill set to be verified corresponding to each verification period in the accounting period is verified Completed, and the checked abnormal bill set is empty, apply for a bill; or be replaced by: If the check of the unchecked bill set corresponding to each verification cycle in the accounting period is completed, and the checked abnormal bill set contains If the bill status is adjusted, apply for a bill.

The following takes the application of a bill processing method provided by this embodiment in the organization code scenario as an example. The bill processing method provided by this embodiment is further described with reference to Figures 2 and 3. See Figure 3 for application in the organization code scenario. The bill processing method specifically includes the following steps.

Referring to Figure 2, the offline system cleans the bills other than agency code bills (non-agency code bills) in the bill data of the current verification period, obtains a benchmark bill set consisting of agency code bills, and checks the previous one in the offline system The abnormal bills of the period are added to the base bill set to obtain the incremental bill set of the current reconciliation period. Then the bills in the incremental bill set are reconciled with the institution code bills in the institution code bill set to obtain the abnormal bills and add them to the abnormal bill set. Among them; and, generate reconciliation tasks for abnormal bills in the abnormal bill collection, perform task allocation, and update the corresponding abnormal bills based on the reconciliation data; after the end of the accounting period, conduct bill review based on the pre-obtained bill summary results and abnormal bill sets , after passing the review, bill application will be made for the checked bill set. Specifically, during the bill application process, the checked bill set will be merged and bill application will be made based on the merged processing result.

Step S302: Clean bills other than agency code bills in the bill data of the current reconciliation period within the accounting period to obtain a benchmark bill set consisting of agency code bills.

Step S304: Add the abnormal bills of the previous verification cycle to the base bill set to obtain the incremental bill set of the current verification cycle.

Step S306: Check the bills in the incremental bill set and the institution code bills in the institution code bill set in at least one verification dimension.

Step S308: Add the abnormal bills of each verification dimension obtained in the verification process to the abnormal bill set for bill review.

The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed. Specifically, the bill review is implemented in the following way: verify whether the billing status of the abnormal bill set in the abnormal bill set after the verification of the bill set to be verified corresponding to each verification cycle in the accounting period is adjusted. If it is adjusted, status, the set of bills to be verified corresponding to each verification cycle in the accounting period will be regarded as the set of verified bills and bill application will be made. Wherein, the bill application includes merging the checked bill sets and applying for a bill based on the merged processing result.

The embodiment of a bill processing device provided in this specification is as follows: In the above embodiment, a bill processing method is provided, and correspondingly, a bill processing device is also provided, which will be described below with reference to the accompanying drawings.

Referring to FIG. 4 , a schematic diagram of a bill processing device provided in this embodiment is shown.

Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiments described below are merely illustrative.

This embodiment provides a bill processing device, including: a data cleaning module 402, configured to perform data cleaning on the bill data of the reconciliation period within the accounting period, to obtain a benchmark bill set; an abnormal bill adding module 404, configured to add the previous Abnormal bills of a verification period are added to the base bill set to obtain an incremental bill set of the verification period; the verification processing module 406 is configured to reconcile the incremental bill set with the corresponding bill set to be verified. , obtain the abnormal bills of the verification period and add them to the abnormal bill set for bill review; wherein the bill review is based on the abnormal bill set and the bill within the account period after the end of the account period. The billing summary results are performed and Apply for a ticket after passing the review.

An example of a bill processing device provided in this specification is as follows: Corresponding to a bill processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a bill processing device. The bill processing device uses To implement the bill processing method provided above, FIG. 4 is a schematic structural diagram of a bill processing device provided by one or more embodiments of this specification.

This embodiment provides a bill processing device, including: As shown in Figure 5, the bill processing device may vary greatly due to different configurations or performance, and may include one or more processors 501 and memories 502. The memory One or more storage applications or data may be stored in 502. Among them, the memory 502 may be short-term storage or persistent storage. The application program stored in memory 502 may include one or more modules (not shown), each module may include a series of computer-executable instructions in the bill processing device. Furthermore, the processor 501 may be configured to communicate with the memory 502 and execute a series of computer-executable instructions in the memory 502 on the bill processing device. The bill processing device may also include one or more power supplies 503, one or more wired or wireless network interfaces 504, one or more input/output interfaces 505, one or more keyboards 506, etc.

In a specific embodiment, the bill processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each Each module may include a series of computer-executable instructions in a statement processing device, and the one or more programs configured to be executed by one or more processors may include computer-executable instructions for performing the following: Check the billing data of the cycle for data cleaning and obtain the baseline bill set;

Add the abnormal bills of the previous verification cycle to the base bill set to obtain the incremental bill set of the verification cycle; perform verification processing on the incremental bill set and the corresponding bill set to be verified to obtain the verification cycle abnormal bills and added to the abnormal bill set for bill review; wherein the bill review is conducted after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and Apply for a ticket after passing the review.

An example of a storage medium provided in this specification is as follows: Corresponding to a bill processing method described above and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

The storage medium provided by this embodiment is used to store computer executable instructions. When executed by the processor, the computer executable instructions implement the following process: perform data cleaning on the bill data of the reconciliation period within the accounting period, and obtain a benchmark bill set. ; Add the abnormal bills of the previous verification cycle to the base bill set to obtain the incremental bill set of the verification cycle; verify the incremental bill set with the corresponding bill set to be verified to obtain the verification Periodic abnormal bills are added to the abnormal bill set for bill review; where the bill review is performed on the account After the end of the period, it will be carried out based on the abnormal bill set and the bill summary results within the accounting period, and the bill application will be made after the review is passed.

It should be noted that the embodiment about the storage medium in this specification and the embodiment about the bill processing method in this specification are based on the same inventive concept. Therefore, for the specific implementation of this embodiment, please refer to the implementation of the corresponding method mentioned above, and the duplication will not be repeated. Repeat.

The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desired results. Additionally, the processes depicted in the figures do not necessarily require the specific order shown, or sequential order, to achieve desirable results. Multitasking and parallel processing are also possible or may be advantageous in certain implementations.

In the 1930s, improvements in a technology could be clearly distinguished as hardware improvements (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method processes). However, with the development of technology, many improvements in today's method processes can be regarded as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement of a method flow cannot be implemented using hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic functions are determined by the user programming the device. Designers can program themselves to "integrate" a digital system on a PLD, instead of asking chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing, and before compilation The original code must also be written in a specific programming language, which is called Hardware Description Language (HDL), and HDL is not just one kind, but there are many, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., are currently the most commonly used The two are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that by simply logically programming the method flow using the above-mentioned hardware description languages and programming it into the integrated circuit, the hardware circuit that implements the logical method flow can be easily obtained.

The controller may be implemented in any suitable manner, for example the controller may take the form of a microprocessor or processor and a computer storing computer readable program code (eg software or firmware) executable by the (micro)processor. In the form of readable media, logic gates, switches, Application Specific Integrated Circuits (ASICs), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.

For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and/or hardware.

It will be appreciated by those skilled in the art that one or more embodiments of this specification may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The specification is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements a process or multiple processes in the flow chart and/or a block or block in the block diagram Features specified in multiple boxes.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer-readable media, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory. (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, disk storage or other magnetic storage devices, or any other non-transmission medium, can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

One or more embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts among the various embodiments It is sufficient to refer to each other, and each embodiment focuses on its differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.

The above are only examples of this document and are not intended to limit this document. Various modifications and variations of this document may occur to those skilled in the art. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this document shall be included in the scope of the claims of this document.

Claims

A method of billing that includes:

Perform data cleaning on the bill data of the reconciliation period within the accounting period to obtain a baseline bill set;

Add the abnormal bills of the previous reconciliation cycle to the base bill set to obtain the incremental bill set of the reconciliation cycle;

Check the incremental bill set with the corresponding bill set to be verified, obtain the abnormal bills of the verification period and add them to the abnormal bill set for bill review;

The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed.
The bill processing method according to claim 1, wherein the bill data of the verification period within the accounting period is cleaned to obtain a benchmark bill set, including:

Read the type tag of each bill in the bill data; the type tag includes a first tag corresponding to institution code payment and a second tag corresponding to non-institution code payment;

Clean the bills of the second label in the bill data to obtain the reference bill set consisting of the bills of the first label.
According to the bill processing method of claim 1, the abnormal bill of the previous verification cycle is obtained in the following manner:

The incremental bill set of the previous verification cycle is verified against the corresponding bill set to be verified, and the abnormal bills of the previous verification cycle are obtained.
The bill processing method according to claim 1, the step of checking the incremental bill set with the corresponding bill set to be checked, obtaining the abnormal bills of the check period and adding them to the abnormal bill set, including:

Perform reconciliation processing on at least one reconciliation dimension between the bills in the incremental bill set and the pending bills in the pending bill set;

Add the abnormal bills of each reconciliation dimension obtained by the reconciliation process to the abnormal bill set.
The bill processing method according to claim 4, wherein the reconciliation process of the bills in the incremental bill set and the bills to be verified in the bill set to be verified in at least one verification dimension includes:

Check whether the bills in the incremental bill set have corresponding bills to be verified in the bill set to be verified, and according to the verification results, use the bills that do not have corresponding bills to be verified in the incremental bill set as abnormal bills in the bill verification dimension. ;and / or,

Check whether the bill amount of the bill in the incremental bill set is consistent with the bill amount of the corresponding unverified bill in the unverified bill set, and use the bill with inconsistent bill amount as an abnormal account in the amount verification dimension based on the verification result. one.
The bill processing method according to claim 1, wherein the incremental bill set is compared with the corresponding bill set to be verified, and the abnormal bills of the verification period are obtained and added to the abnormal bill set for processing. After the bill review step is performed, it also includes:

Generate an adjustment task for the abnormal bill and allocate the adjustment task;

The abnormal bills in the abnormal bill set are updated according to the accounting data generated after the execution of the accounting task.
The bill processing method according to claim 1, further comprising:

Calculate the total bill amount of the bills to be verified in the collection of bills to be verified;

The total bill amount is compared with the total bill amount of the verification period included in the bill summary result.
The bill processing method according to claim 1, wherein the bills to be verified in the set of bills to be verified include institution code bills;

Wherein, the institution code bill is generated after payment processing based on the institution's institution code.
According to the bill processing method of claim 8, the bill summary result is determined in the following manner:

The bills with the institution code associated with the account period are aggregated to obtain the bill aggregation result; the bills with the institution code are associated with the account period after being determined to belong to the account period through calculation;

Wherein, the aggregation processing is implemented in at least one of the following ways:

Aggregate the agency code bills associated with the accounting period according to the reconciliation period to obtain a set of bills to be verified consisting of agency code bills for each reconciliation period, and calculate each reconciliation period based on the bill amount of the agency code bills for each reconciliation period in the accounting period The total bill amount is calculated based on the organization code bill in each verification cycle, and the total billing amount in each verification cycle is calculated, and the number of bills in each verification cycle is calculated.
According to the bill processing method of claim 8, the bill summary result includes at least one of the following:

A set of bills to be verified consisting of agency code bills for each verification cycle in the accounting period,

The total bill amount is calculated based on the bill amount of the institution code bill in each verification period.

Total billing amount for each reconciliation cycle, or

The number of agency code bills in each verification cycle.
According to the bill processing method of claim 1, the bill review is implemented in the following manner:

Verify whether the reconciliation processing of the incremental bill set and the corresponding bill set to be verified in each reconciliation period within the accounting period is completed;

If so, verify whether the abnormal bills in each verification cycle are empty. If it is empty, execute the bill application; if not, verify whether the bill status of the abnormal bill in the abnormal bill set is adjusted. If it is adjusted, Account status, Execute said ticket request.
According to the bill processing method of claim 1, the bill application is implemented in the following manner:

Consolidate the bill sets to be verified in each verification period within the accounting period, and apply for bills based on the results of the consolidation process.
The bill processing method according to claim 12, said merging the bill sets to be verified in each verification cycle within the accounting period, and applying for a bill based on the merging processing results, including:

According to the payment institution corresponding to the bill, the unverified bills of each payment institution in the bill collection period are merged to obtain the first total bill of each payment institution in the account period, and the bill application interface is called. Issuance of a bill for the first general bill; or,

According to the merchant corresponding to the bill, the unverified bills of each merchant in the bill collection to be verified in the account period are merged, the second total bill of each merchant in the account period is obtained, and the bill application interface of each merchant is called. Issuance of a bill for said total bill; or,

According to the bill application cycle of the bill, the bills to be verified in each bill application cycle are merged to obtain the third total bill of each bill application cycle, and the bill application interface is called to issue bills for the total bill.
A bill processing device including:

The data cleaning module is configured to perform data cleaning on the bill data of the reconciliation period within the accounting period to obtain a benchmark bill set;

An abnormal bill adding module configured to add the abnormal bills of the previous verification cycle to the base bill set to obtain an incremental bill set of the verification cycle;

A check processing module configured to check the incremental bill set with the corresponding bill set to be checked, obtain the abnormal bills of the check period and add them to the abnormal bill set for bill review;

The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed.
A bill processing device consisting of:

a processor; and, a memory configured to store computer-executable instructions that, when executed, cause the processor to:

Perform data cleaning on the bill data of the reconciliation period within the accounting period to obtain a baseline bill set;

Add the abnormal bills of the previous reconciliation cycle to the base bill set to obtain the incremental bill set of the reconciliation cycle;

Check the incremental bill set with the corresponding bill set to be verified, obtain the abnormal bills of the verification period and add them to the abnormal bill set for bill review;

The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed.
A storage medium used to store computer-executable instructions that implement the following process when executed by a processor:

Perform data cleaning on the bill data of the reconciliation period within the accounting period to obtain a baseline bill set;

Add the abnormal bills of the previous reconciliation cycle to the base bill set to obtain the incremental bill set of the reconciliation cycle;

Check the incremental bill set with the corresponding bill set to be verified, obtain the abnormal bills of the verification period and add them to the abnormal bill set for bill review;

The bill review is performed after the end of the account period based on the abnormal bill set and the bill summary results within the account period, and a bill application is made after the review is passed.