Paperless auditing method and equipment for reimbursement scene, storage medium and product

Abstract

The invention discloses a paperless auditing method and device for a reimbursement scene, a storage medium and a product, and relates to the technical field of information processing. The paperless auditing method comprises the following steps: monitoring a reimbursement request initiated by a client, and obtaining reimbursement source data corresponding to the reimbursement request; integrating the reimbursement source data according to the reimbursement request, and generating a paperless reimbursement receipt corresponding to the reimbursement request; performing paperless auditing on the reimbursement document according to the cost dimension of the reimbursement document by using a verification chain connected with a plurality of business verification rules in series; and when the paperless reimbursement document passes the paperless auditing, pushing the paperless reimbursement document and the corresponding reimbursement source data to a corresponding reimbursement system for approval and reimbursement. According to the technical scheme, the problem that reimbursement auditing efficiency is affected due to the fact that reimbursement receipts in an existing scheme are not necessarily suitable for paperless processing and possibly cannot be uploaded to a reimbursement system can be solved.

Description

Technical Field

[0001] The present application relates to the field of information processing technology, and in particular to a paperless audit method, device, storage medium and product for reimbursement scenarios. Background Art

[0002] In information processing technology, financial information involving business, finance and management is an important part of information processing. Financial information inevitably involves financial reimbursement. Traditional financial reimbursement is handled manually, which is inefficient. With the development of information technology, financial reimbursement has gradually turned to a paperless application environment.

[0003] The traditional paperless reimbursement system of corporate finance usually includes: employee terminal, reimbursement data processing module, leader approval terminal and reimbursement amount management module; first, the reimbursement data processing module will identify the invoice information, work permit number and reimbursement personnel uploaded by the employee terminal; after successful identification, it will match with the keywords and verify the matching results. The specific verification items include invoice authenticity query, reimbursement personnel information verification, reimbursement personnel face verification and reimbursement item verification; then, the matching results that pass the verification are sent to the leader approval terminal, and the matching results that fail the verification are sent to the employee terminal, notifying the reimbursement personnel that reimbursement cannot be made or prompting the reimbursement personnel to make modifications; the leader approval terminal will approve layer by layer according to the company's authority settings, and the leader approval terminal will send the approval signal to the reimbursement amount management module; finally, the reimbursement amount management module will remit the reimbursement amount to the employee account to complete the entire invoice reimbursement operation.

[0004] However, the paperless reimbursement system for corporate finance provided by the existing technology can only verify the authenticity of invoices, information of reimbursement personnel and reimbursement items, which are peripheral information related to finance. It cannot automatically verify specific reimbursement documents and can only be done manually. This is because reimbursement documents involving invoices, orders and expense data are not necessarily suitable for paperless processing and require manual verification, resulting in the reimbursement documents being unable to be uploaded to the reimbursement system, thereby affecting the efficiency of reimbursement review.

[0005] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0006] The main purpose of this application is to provide a paperless audit method, equipment, storage medium and product for reimbursement scenarios, aiming to solve the technical problem in existing solutions that reimbursement documents involving invoices, orders and expense data may not be suitable for paperless processing, resulting in the inability to upload reimbursement documents to the reimbursement system, thereby affecting the efficiency of reimbursement audit.

[0007] To achieve the above objectives, this application provides a paperless review method for reimbursement scenarios, including:

[0008] Monitor the reimbursement request initiated by the client and obtain the reimbursement source data corresponding to the reimbursement request;

[0009] Integrate reimbursement source data according to reimbursement requests and generate paperless reimbursement documents corresponding to the reimbursement requests;

[0010] Use a verification chain that connects multiple business verification rules to conduct paperless review of reimbursement documents according to the expense dimension of the reimbursement documents;

[0011] When the paperless review of the reimbursement document is passed, the paperless reimbursement document and the corresponding reimbursement source data will be pushed to the corresponding reimbursement system for approval and reimbursement.

[0012] Preferably, in the above-mentioned paperless audit method, the step of monitoring the reimbursement request initiated by the client and obtaining the reimbursement source data corresponding to the reimbursement request includes:

[0013] Get the reimbursement source data uploaded by the client;

[0014] Connect to the data issuance system corresponding to the reimbursement source data and extract reimbursement identification information from the data issuance system;

[0015] Use reimbursement identification information to identify and verify reimbursement source data;

[0016] When the identification and verification of the reimbursement source data is passed, the source type and sequence ID of the reimbursement source data are generated, and the sequence ID is used to store the reimbursement source data in the database of the corresponding source type.

[0017] Preferably, in the above-mentioned paperless audit method, the step of integrating the reimbursement source data according to the reimbursement request and generating a paperless reimbursement document corresponding to the reimbursement request includes:

[0018] Get the sequence ID included in the reimbursement request;

[0019] Searching for multiple reimbursement source data from databases corresponding to different source types according to sequence IDs, wherein the reimbursement source data is stored in databases corresponding to the source types;

[0020] Create an expense reimbursement instance, integrate multiple reimbursement source data into the expense reimbursement instance according to source type, and obtain paperless reimbursement documents.

[0021] Preferably, in the above-mentioned paperless audit method, before the step of using a verification chain having a plurality of business verification rules connected in series to conduct paperless audit on the reimbursement document according to the expense dimension of the reimbursement document, the method further comprises:

[0022] Extract multiple reimbursement object information from the reimbursement document;

[0023] Determine whether multiple reimbursement object information all meet the corresponding reimbursement object requirements;

[0024] If it is determined that any of the multiple reimbursement object information does not meet the corresponding reimbursement object requirements, a non-applicable result is output; wherein the non-applicable result is used to indicate that the reimbursement document is not within the reimbursement applicable scope;

[0025] If it is determined that multiple reimbursement object information meets the corresponding reimbursement object requirements, a verification chain that connects multiple business verification rules is executed to perform paperless review of the reimbursement document according to the expense dimension of the reimbursement document.

[0026] Preferably, in the above-mentioned paperless audit method, before the step of using a verification chain having a plurality of business verification rules connected in series to conduct paperless audit on the reimbursement document according to the expense dimension of the reimbursement document, the method further comprises:

[0027] Multiple rule validators are set, wherein each rule validator encapsulates a business validation rule, and the business validation rule is used to perform paperless review of reimbursement documents according to the source type of the reimbursement source data;

[0028] According to the source type verified by the business verification rules, set the priority of multiple rule verifiers;

[0029] According to the arrangement priority, multiple rule checkers are connected in series in the form of responsibility chain to obtain a check chain.

[0030] Preferably, in the above-mentioned paperless audit method, the step of using a verification chain having multiple business verification rules in series to conduct paperless audit on the reimbursement document according to the expense dimension of the reimbursement document includes:

[0031] According to the order of the verification chain, multiple rule verifiers are used to conduct paperless review of reimbursement documents based on the expense dimension;

[0032] Determine whether the expenses of the reimbursement document meet the expense requirements corresponding to the source type specified in the business verification rules;

[0033] If the expense of the reimbursement document meets the expense requirements, the reimbursement document and the corresponding reimbursement source data are determined to meet the paperless review conditions;

[0034] When all rule checkers in the check chain determine that the reimbursement document and the corresponding reimbursement source data meet the paperless review conditions, the reimbursement document is determined to have passed the paperless review, and the step of pushing the paperless reimbursement document and the corresponding reimbursement source data to the corresponding reimbursement system for approval and reimbursement is executed.

[0035] Preferably, in the above-mentioned paperless audit method, after the step of using a verification chain having multiple business verification rules in series to conduct paperless audit on the reimbursement document according to the expense dimension of the reimbursement document, the method further comprises:

[0036] When the paperless review of the reimbursement document fails, the reimbursement source data that meets the paperless review conditions will be pushed to the reimbursement system for approval and reimbursement, and an approval failure notification will be sent to the client, where the approval failure notification includes a notification message of the reimbursement source data that does not meet the paperless review conditions;

[0037] When the reimbursement document is not within the reimbursement scope, a paperless notification of non-applicability is sent to the client.

[0038] To achieve the above-mentioned objectives, the present application also provides a paperless audit device for reimbursement scenarios, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of a paperless audit method for reimbursement scenarios as provided in any of the above-mentioned technical solutions.

[0039] To achieve the above-mentioned purpose, the present application also provides a storage medium, which is a computer-readable storage medium. A computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the paperless audit method for reimbursement scenarios provided by any of the above-mentioned technical solutions are implemented.

[0040] To achieve the above objectives, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the paperless audit method for reimbursement scenarios provided by any of the above technical solutions.

[0041] One or more technical solutions proposed in this application have at least the following technical effects:

[0042] Listen to the reimbursement request initiated by the client, obtain the reimbursement source data corresponding to the reimbursement request, and integrate the reimbursement source data into the paperless reimbursement document according to the reimbursement request; then use the verification chain with multiple business verification rules in series to conduct a paperless review of the reimbursement document according to the expense dimension of the reimbursement document to determine whether the paperless reimbursement document meets the paperless requirements stipulated for approval and reimbursement. Only when the paperless review of the reimbursement document is passed can the paperless reimbursement document and the corresponding reimbursement source data be pushed to the corresponding reimbursement system for approval and reimbursement; if the approval is not passed, it cannot be pushed to the reimbursement system for approval and reimbursement. The above method can automatically review the compliance of reimbursement documents with paperless requirements without manual intervention, and the processing efficiency is high. In addition, reimbursement documents can support paperless review of multiple source data, such as expenses, invoices, and orders, and configure multiple business verification rules in the form of a verification chain, which can cover most paperless review scenarios. In summary, the above method can solve the problem in the prior art that reimbursement documents may not be suitable for paperless processing, resulting in the reimbursement documents may not be uploaded to the reimbursement system, affecting the efficiency of reimbursement review. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0045] Figure 1 A flowchart of a first paperless review method for a reimbursement scenario provided in an embodiment of the present application;

[0046] Figure 2 For this application Figure 1 A flowchart of a method for obtaining reimbursement source data provided by the illustrated embodiment;

[0047] Figure 3 For this application Figure 1 A schematic diagram of a process for generating a reimbursement document provided in the illustrated embodiment;

[0048] Figure 4 A flowchart of a method for determining the applicable scope of reimbursement object information provided in an embodiment of the present application;

[0049] Figure 5 A flowchart of a method for verifying a reimbursement document using a verification chain provided in an embodiment of the present application;

[0050] Figure 6 This application Figure 1 The illustrated embodiment provides a flow chart of a paperless review method for reimbursement documents;

[0051] Figure 7 It is a flowchart of a second paperless review method for reimbursement scenarios provided in an embodiment of the present application;

[0052] Figure 8 It is a relationship diagram between an expense instance and reimbursement source data provided in an embodiment of the present application;

[0053] Fig. 9 It is a schematic diagram of the structure of a reimbursement document provided in an embodiment of the present application;

[0054] Fig.10 It is a flowchart of a paperless review and reimbursement method provided in an embodiment of the present application;

[0055] Fig.11 It is a structural diagram of a paperless audit engine provided in an embodiment of the present application;

[0056] Fig.12 It is a flowchart of a judgment method of using a range judgment module provided in an embodiment of the present application;

[0057] Fig.13 It is a flowchart of a verification method of a rule verifier module provided in an embodiment of the present application;

[0058] Fig.14 This application Fig.13 A schematic diagram of a process flow of core rules for paperless auditing provided by the illustrated embodiment;

[0059] Fig.15 It is a structural schematic diagram of a paperless review device for reimbursement scenarios provided in an embodiment of the present application.

[0060] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0061] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0062] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0063] The existing technology has the following technical problems: the paperless reimbursement system for corporate finance provided by the existing technology can only verify the authenticity of invoices, information of reimbursement personnel and reimbursement matters, which are peripheral information related to finance, but cannot verify specific reimbursement documents. This is because reimbursement documents involving invoices, orders and expense data may not be suitable for paperless processing, resulting in the reimbursement documents may not be uploaded to the reimbursement system, thereby affecting the efficiency of reimbursement review.

[0064] To solve the above technical problems, the present application provides a solution, which integrates the reimbursement source data according to the reimbursement request to generate a paperless reimbursement document corresponding to the reimbursement request; uses a verification chain that connects multiple business verification rules to perform paperless review of the reimbursement document according to the expense dimension of the reimbursement document; when the paperless review of the reimbursement document is passed, the paperless reimbursement document and the corresponding reimbursement source data are pushed to the corresponding reimbursement system for approval and reimbursement.

[0065] In summary, the paperless review solution for reimbursement scenarios provided in this application can solve the problem that existing reimbursement documents may not be able to be uploaded to the reimbursement system, affecting the efficiency of reimbursement review.

[0066] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device that can realize the above functions, a computer-readable storage medium, etc.

[0067] In order to better understand the above technical solution, the exemplary embodiments of the present application will be described in more detail with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments shown here. On the contrary, these embodiments are provided to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0068] To achieve the above technical objectives, see Figure 1 , Figure 1 The present application provides a flowchart of a first paperless audit method for reimbursement scenarios. Figure 1 As shown, the paperless audit method includes:

[0069] S110: Listen to the reimbursement request initiated by the client, and obtain the reimbursement source data corresponding to the reimbursement request.

[0070] The paperless audit method provided in the embodiment of the present application corresponds to a paperless audit engine, or a paperless audit device, which can audit paperless reimbursement documents as part of the reimbursement system to determine whether they meet the paperless requirements. Fig.11 As shown, the paperless audit engine needs to monitor the reimbursement requests initiated by the client in real time; when the client initiates reimbursement, the reimbursement system passes the reimbursement source data corresponding to the reimbursement request to the paperless audit engine; then the paperless audit engine obtains the reimbursement source data corresponding to the reimbursement request, where the reimbursement source data includes expenses, orders, invoices and other data. The paperless audit engine can integrate the above data by obtaining the reimbursement source data, and then generate a paperless reimbursement document, and finally perform a paperless audit judgment on the reimbursement document, and output the audit results including not applicable, non-paperless and paperless results to the reimbursement system.

[0071] Specifically, as a preferred embodiment, Figure 2 As shown, in the above paperless audit method, step S110: monitoring the reimbursement request initiated by the client and obtaining the reimbursement source data corresponding to the reimbursement request includes:

[0072] S111: Obtaining the reimbursement source data uploaded by the client First, the reimbursement source data is uploaded by the client along with the reimbursement request or between reimbursement requests, and the reimbursement source data here includes orders, expenses, invoices and other forms.

[0073] S112: Connect to the data issuance system corresponding to the reimbursement source data and extract the reimbursement identification information from the data issuance system. Figure 8 As shown in the relationship diagram between the expense instance and the reimbursement source data, the reimbursement source data in the embodiment of the present application includes forms such as corporate payment orders, invoices, and personal payment orders. The embodiment of the present application connects to external data issuance systems, such as hotel, company, airline, and railway systems, and re-extracts reimbursement identification information from the external data issuance system to verify the authenticity of the reimbursement source data.

[0074] S113: Use the reimbursement identification information to identify and verify the reimbursement source data. Figure 8In the relationship diagram provided by the illustrated embodiment, personal payment orders include hotel orders, train orders, airplane orders, dining orders, and car orders, etc. In this way, the authenticity of the order can be queried from the data issuance systems of hotels, trains, airplanes, and restaurants, thereby extracting reimbursement identification information. The reimbursement identification information here includes the authenticity of the reimbursement source data and the authenticity of the information provided by the reimbursement source data. For example, in a hotel order, the reimbursement identification information can include the merchant name, check-in date, consumption city, and check-out date, etc. In summary, by using the reimbursement identification information, the reimbursement source data can be identified and verified, thereby verifying the authenticity of the reimbursement source data.

[0075] S114: When the identification and verification of the reimbursement source data is passed, the source type and sequence ID of the reimbursement source data are generated, and the reimbursement source data is stored in the database of the corresponding source type using the sequence ID. Both the source type and the sequence ID can be extracted from the reimbursement source, for example, the sequence ID can be extracted from the date when the data is generated, and the source type such as invoice type, order type and expense type can associate the corresponding reimbursement source data with the corresponding database.

[0076] The technical solution provided in the embodiment of the present application can extract reimbursement identification information from the data issuance system by connecting to the data issuance system corresponding to the reimbursement source data, and then use the reimbursement identification information to identify and verify the reimbursement source data. When the verification is passed, the source type and sequence ID of the reimbursement source data are generated, so that the reimbursement source data can be stored in a database corresponding to the source type, so as to be available for subsequent paperless review and reimbursement use.

[0077] Figure 1 The technical solution provided by the illustrated embodiment, after obtaining the reimbursement source data corresponding to the reimbursement request, further includes the following steps:

[0078] S120: Integrate the reimbursement source data according to the reimbursement request and generate a paperless reimbursement document corresponding to the reimbursement request.

[0079] In an embodiment of the present application, a reimbursement request corresponds to a situation where an expense, an invoice, and an order are associated. For example, the same business trip generates an invoice, an order, and an expense. In this way, the reimbursement source data can be integrated according to the reimbursement request. To facilitate the integration of the reimbursement source data, information such as the reimbursement date, location, and reimbursement type can be included in the reimbursement request. After integrating the reimbursement source data, a paperless reimbursement document corresponding to the reimbursement request can be generated.

[0080] Specific reimbursement documents such as Fig. 9As shown, it includes the total cost amount and cost items of the document; there are multiple cost items, including personal payment orders, public payment orders and invoices, and the invoices include information such as invoice type, invoice file type and invoice amount.

[0081] Among them, as a preferred embodiment, Figure 3 As shown, in the above paperless audit method, step S120: integrating the reimbursement source data according to the reimbursement request and generating a paperless reimbursement document corresponding to the reimbursement request includes:

[0082] S121: Get the sequence ID included in the reimbursement request. The sequence ID here corresponds to a reimbursement request, or the same batch of reimbursement source data that needs to be reimbursed. When a user applies for reimbursement, the sequence ID can be used to query the same batch of reimbursement source data from the database of the corresponding source type. For example, the expenses, invoices and orders that need to be reimbursed in the same time period can be queried.

[0083] S122: Searching for multiple reimbursement source data from databases corresponding to different source types according to the sequence ID, wherein the reimbursement source data is stored in the database corresponding to the source type. Figure 8 It can be seen from the technical solution provided by the embodiment shown that the public payment order is stored in the biz database through the public payment order sequence ID; the public payment + personal order is stored in the biz / tsdb database through the order sequence ID and the voucher unique ID respectively, and the personal payment order + invoice + business card is stored in the biz database through the voucher unique ID and voucher type respectively. Therefore, according to the sequence ID, it is possible to search for multiple reimbursement source data from the database corresponding to different source types, and integrate the multiple reimbursement source data.

[0084] S123: Create an expense reimbursement instance, integrate multiple reimbursement source data into the expense reimbursement instance according to source type, and obtain a paperless reimbursement document. Figure 8 It can be seen from the illustrated embodiment that the embodiment of the present application creates an expense instance, which includes a public payment order set and an expense instance voucher, wherein the expense instance voucher includes an invoice set and a personal payment order set, and the invoice set includes invoice information and invoice files, and the invoice file includes information such as the invoice file type and the source file identifier; the invoice file type here can be in a format such as PDF. Personal payment orders include hotel orders, train orders, airplane orders, dining orders, and car orders. Personal payment orders, public payment orders, and invoices can be integrated through serial IDs to obtain paperless reimbursement documents. For the specific form of the reimbursement documents, please refer to Fig. 9 The input reimbursement source data is processed, and the association between data from multiple sources, such as expenses, orders and invoices and each reimbursement form is processed to obtain the processing result.

[0085] The processing result here can be the relationship between various source data and the reimbursement form, such as [expense=>reimbursement form] [order=>reimbursement form] [invoice=>reimbursement form]; it can also be the relationship after the reimbursement form is integrated with various source data, such as [reimbursement form=>expense+order+invoice].

[0086] The technical solution provided in the embodiment of the present application obtains the serial ID contained in the reimbursement request, and then searches for the reimbursement source data from the database corresponding to different source types according to the serial ID. It is possible to integrate the reimbursement source data into the expense reimbursement instance according to the above source type, thereby obtaining a paperless reimbursement document. In this way, the paperless reimbursement document can be used to integrate multiple reimbursement source data in the above manner, and electronic review can be performed, thereby improving the efficiency of reviewing and approving reimbursement.

[0087] Figure 1 The technical solution provided by the illustrated embodiment, after the step of generating a paperless reimbursement document corresponding to the reimbursement request, further includes:

[0088] S130: Use a verification chain that connects multiple business verification rules to conduct paperless review of the reimbursement documents according to the expense dimension of the reimbursement documents.

[0089] In the technical solution provided in the embodiment of the present application, verification is performed according to multiple business verification rules. In the present application, multiple rule verifiers are set, each rule verifier sets a business verification rule, and then the above-mentioned multiple rule verifiers are arranged in the form of a responsibility chain to form a verification chain. In this way, the use of a verification chain with multiple business verification rules in series can perform paperless review of the reimbursement documents according to the expense dimension of the reimbursement documents. The paperless review here specifically determines whether the above-mentioned generated paperless reimbursement documents meet the paperless requirements of the approval regulations. Only when they meet the paperless requirements can the electronic version of the reimbursement document be passed to the reimbursement system for approval.

[0090] In addition, before using the verification chain to conduct paperless review of the reimbursement document, it is also necessary to determine whether the paperless reimbursement document is within the applicable scope of reimbursement. Only when it is within the applicable scope of reimbursement can paperless review be performed.

[0091] Specifically, as a preferred embodiment, Figure 4 As shown, in the above paperless audit method, before step S130: using a verification chain having multiple business verification rules in series to conduct paperless audit on the reimbursement document according to the expense dimension of the reimbursement document, the method further includes:

[0092] S201: extracting multiple reimbursement object information from the reimbursement document. The reimbursement object information here includes the input enterprise object, document type object and department object, so that after obtaining the reimbursement object information, it can be determined whether the reimbursement object information meets the corresponding reimbursement requirements.

[0093] S202: Determine whether multiple reimbursement object information all meet the corresponding reimbursement object requirements. Because not all invoices, orders and expenses can be reimbursed, it is necessary to determine whether the input reimbursement object information such as the enterprise document type and department meets the corresponding reimbursement object requirements, such as whether the business trip is to the specified enterprise, whether the invoice of the specified enterprise is obtained, etc. In this way, by determining whether the reimbursement object information all meets the corresponding reimbursement object requirements, that is, the above reimbursement object information meets the applicable scope of reimbursement, it can be applied to paperless review, and then submitted to the corresponding reimbursement approval department for approval.

[0094] S203: If it is determined that any of the multiple reimbursement object information does not meet the corresponding reimbursement object requirements, an inapplicable result is output; wherein the inapplicable result is used to indicate that the reimbursement document is not within the reimbursement applicable scope. When the inapplicable result is output, the reimbursement document is not within the reimbursement applicable scope, and a paperless inapplicable notification will be returned to the client. The user can then upload the reimbursement source data that meets the reimbursement object requirements, or manually upload the data to the relevant approval department, and can also stop reimbursement.

[0095] S204: If it is determined that the multiple reimbursement object information all meet the corresponding reimbursement object requirements, a step of using a verification chain that connects multiple business verification rules in series to perform paperless review of the reimbursement document according to the expense dimension of the reimbursement document is executed.

[0096] The technical solution provided in the embodiment of the present application determines whether multiple reimbursement object information meets the corresponding reimbursement object requirements. Only when they meet the reimbursement object requirements can the verification chain with multiple business regulations be used to perform paperless review of the reimbursement documents according to the expense dimension of the reimbursement documents. This can further improve the accuracy and efficiency of paperless review.

[0097] In addition, the paperless audit in the present application embodiment requires the setting of a paperless audit engine, such as Fig.11 As shown, the paperless audit is performed using the rule checker mode of the paperless audit engine. The rule checker module includes a check chain formed by connecting multiple rule checkers in series in the form of responsibility chain. Each rule checker includes a business check rule.

[0098] Specifically, as a preferred embodiment, Figure 5As shown, in the above paperless audit method, before step S130: using a verification chain having multiple business verification rules in series to perform paperless audit on the reimbursement document according to the expense dimension of the reimbursement document, the method further includes:

[0099] S301: multiple rule checkers are set, wherein each rule checker encapsulates a business check rule, and the business check rule is used to perform paperless review on the reimbursement document according to the source type of the reimbursement source data;

[0100] S302: according to the source type verified by the business verification rule, set the priority of multiple rule verifiers; for example Fig.14 As shown, first determine the expense type. If there is no expense category or the total expense amount is 0, it is directly determined to be paperless. At this time, there is no need to perform the next rule checker, and the paperless result is directly output. The subsequent rule checkers include business check rules for no orders but invoices, business check rules for orders and public payment orders, business check rules for orders and personal payment orders, and check rules for orders and personal payment orders. Set the arrangement priority of multiple rule checkers by source type to obtain a complete check chain.

[0101] S303: Connect multiple rule validators in series in the form of a responsibility chain according to the arrangement priority to obtain a verification chain. The responsibility chain pattern connects multiple validators in a chain structure so that the request is passed along the chain until a validator processes the request. The responsibility chain pattern allows multiple objects to have the opportunity to process a request, thereby avoiding the coupling relationship between the sender and receiver of the request. The present application connects these rule validators into a verification chain and passes the above-mentioned reimbursement documents along this chain until it is determined that all expenses meet the paperless reimbursement conditions.

[0102] The technical solution provided in the embodiment of the present application requires setting up a verification chain in advance before applying the verification chain to perform paperless review of reimbursement documents. Specifically, multiple rule verifiers are set, each rule verifier encapsulates a business verification rule, and an arrangement priority is set according to the source type verified by the business verification rule. The rule verifiers are connected in series in the form of a responsibility chain according to the arrangement priority, so that a complete verification chain can be obtained. In this way, the paperless approval efficiency of reimbursement documents can be improved.

[0103] After the step of connecting multiple rule checkers in series to obtain a check chain, it is necessary to execute the above step S130 to use the check chain to perform paperless review on the reimbursement document according to the expense dimension of the reimbursement document.

[0104] Specifically, as a preferred embodiment, Figure 6As shown, in the above paperless audit method, step S130: using a verification chain having multiple business verification rules in series, the step of conducting a paperless audit on the reimbursement document according to the expense dimension of the reimbursement document includes:

[0105] S131: According to the order of the verification chain, use multiple rule verifiers to perform paperless audit on the expense dimension of the reimbursement document. In the embodiment of the present application, the verification chain will perform paperless audit on the expense dimension of the reimbursement document. If a certain expense meets any one of the rules in the verification chain, then the expense meets the paperless condition, otherwise it does not meet.

[0106] S132: Determine whether the expense of the reimbursement document meets the expense requirements corresponding to the source type specified in the business verification rules. Specifically, each rule verifier in the verification chain in the embodiment of the present application determines whether the expense of the reimbursement document meets the expense requirements corresponding to the source type specified in the business verification rules, for example Fig.14 From the process shown, we can see that: Rule Verifier 0 has the highest priority, and its verification rule can determine whether there is no expense category and the expense amount is 0; Rule Verifier 1 has a priority of 3, which can determine whether there is no order but there is an invoice, and all invoices meet the requirements. At this time, the audit is for paperless situation.

[0107] S133: If the expense of the reimbursement document meets the expense requirements, it is determined that the reimbursement document and the corresponding reimbursement source data meet the paperless review conditions.

[0108] S134: When all rule checkers in the check chain determine that the reimbursement document and the corresponding reimbursement source data meet the paperless review conditions, the reimbursement document is determined to have passed the paperless review, and the step of pushing the paperless reimbursement document and the corresponding reimbursement source data to the corresponding reimbursement system for approval and reimbursement is executed.

[0109] Combination Fig.14 It can be seen from the shown rules that in the technical solution provided by the embodiment of the present application, the verification chain will perform paperless audit based on the expense dimension of the document. If an expense meets any one of the rules on the verification chain, the expense meets the paperless condition, otherwise it does not meet the condition. When all expenses meet the paperless condition, the audit result of the document is paperless, otherwise it is not paperless. Through the above method, the priorities of various rule verifiers can be configured in the form of a chain of responsibility, and paperless audit can be performed on reimbursement source data of various source types, thereby covering the vast majority of reimbursement scenarios for paperless audit.

[0110] Combined with this application Fig.11It can be seen from the embodiments shown and the above embodiments that the application mainly includes the application scope judgment module and the rule verification module to judge whether the reimbursement document is applicable to paperless and whether the reimbursement document meets the paperless review conditions through the application scope and business verification rules respectively. Here, it is necessary to collect the review results of the reimbursement list. Specifically, Figure 1 The technical solution provided by the illustrated embodiment, after the step of conducting paperless review of the reimbursement document according to the expense dimension of the reimbursement document, further includes:

[0111] S140: When the paperless review of the reimbursement document is passed, the paperless reimbursement document and the corresponding reimbursement source data are pushed to the corresponding reimbursement system for approval and reimbursement. When the paperless review of the reimbursement document is passed, the reimbursement document and the corresponding reimbursement source data are pushed to the reimbursement system for approval and reimbursement, which can improve the approval efficiency of the paperless reimbursement document and the reimbursement source data, thereby providing an online reimbursement channel.

[0112] In addition, as a preferred embodiment, Figure 7 As shown, in the above paperless audit method, after the step of using a verification chain that connects multiple business verification rules to conduct paperless audit on the reimbursement document according to the expense dimension of the reimbursement document, the method further includes:

[0113] S150: When the paperless review of the reimbursement document fails, the reimbursement source data that meets the paperless review conditions is pushed to the reimbursement system for approval and reimbursement, and an approval failure notification is sent to the client, where the approval failure notification includes a notification message of the reimbursement source data that does not meet the paperless review conditions.

[0114] The approval failure notification will send a notification message to the customer segment indicating that the paperless review conditions are not met. This will enable the user to re-upload the reimbursement source data that meets the review conditions, or manually upload the reimbursement source data.

[0115] S160: When the reimbursement document is not within the reimbursement applicable scope, a paperless non-applicability notification is sent to the client.

[0116] Combination Fig.11It can be seen from the structure of the paperless audit engine shown that in the embodiment of the present application, there are two results for judging the scope of application of the reimbursement document: not applicable and continue to judge. When the result is not applicable, the paperless audit will no longer be performed, and the inapplicable results will be directly collected and returned. When the result is "continue to judge", the step of using a verification chain with multiple business verification rules in series is entered. There are two results output by all rule verifiers on the verification chain: paperless and non-paperless. Both results will be collected and returned. In summary, three results will be returned in the end: not applicable, paperless and non-paperless. Among them, paperless means that the paperless review of the reimbursement document has passed, non-paperless means that the paperless review of the reimbursement document has failed, and not applicable means that the reimbursement document is not within the scope of reimbursement.

[0117] The technical solution provided by the embodiment of the present application obtains the reimbursement source data corresponding to the reimbursement request by monitoring the reimbursement request initiated by the client, and integrates the reimbursement source data into the paperless reimbursement document according to the reimbursement request; then, a verification chain with multiple business verification rules is used to conduct a paperless review of the reimbursement document according to the expense dimension of the reimbursement document to determine whether the paperless reimbursement document meets the paperless requirements stipulated for the approval of reimbursement. Only when the paperless review of the reimbursement document is passed can the paperless reimbursement document and the corresponding reimbursement source data be pushed to the corresponding reimbursement system for approval and reimbursement; if the approval is not passed, it cannot be pushed to the reimbursement system for approval and reimbursement. The above method can automatically review the compliance of the reimbursement document with the paperless requirements without manual intervention, and the processing efficiency is high. In addition, the reimbursement document can support paperless review of multiple source data, such as expenses, invoices, and orders, and configure multiple business verification rules in the form of a verification chain, which can cover most paperless review scenarios. In summary, the above method can solve the problem in the prior art that reimbursement documents may not be suitable for paperless processing, resulting in the reimbursement documents may not be uploaded to the reimbursement system, affecting the efficiency of reimbursement review.

[0118] In addition, if Fig.10 As shown, the present application also provides a flow chart of a paperless audit and reimbursement method, which is applied to a paperless audit and reimbursement system, which includes a client, a paperless audit engine and a reimbursement system. Fig.10 As shown, the workflow of the paperless review and reimbursement method is as follows:

[0119] S401: The client initiates a reimbursement request.

[0120] S402: After receiving the reimbursement request, the reimbursement system integrates the reimbursement order number, expenses, order, invoice and other data into the reimbursement document.

[0121] S403: The paperless review engine performs paperless review on the reimbursement documents.

[0122] S404: The reimbursement system receives the audit results of the paperless audit engine: not applicable, paperless, and non-paperless, and then approves the reimbursement based on the audit results.

[0123] Of course, orders, expenses, invoices and other source data can also be sent to the paperless review engine for review separately.

[0124] Specifically, the structure of the paperless audit engine is as follows: Fig.11 As shown, the paperless audit engine includes:

[0125] Data preprocessing module, application scope judgment module, rule verifier module and result collection module; among them, the rule verifier mode is the core of the paperless audit engine.

[0126] The workflow of the paperless audit engine is as follows:

[0127] First, the reimbursement source data is input externally. These reimbursement source data can include data such as expenses, orders, and invoices. The data preprocessing module combines various types of reimbursement source data according to the dimensions of the reimbursement documents, and then uses the scope judgment module to determine whether paperless is applicable; the judgment rules include subsidiary-level judgment and department-level judgment, among which the subsidiary-level judgment includes: whether the enterprise is applicable, whether the network is applicable, and whether the project is applicable; the department-level judgment mainly determines whether the reimbursement document is applicable to each sub-department. The rule verifier module is used to use the core business verification rules to perform paperless verification on the reimbursement documents, such as whether all orders are public payments, whether all invoices are originals, etc. The result collection module is used to collect data from the first two modules: the scope judgment module and the rule verifier module, and return the results. Finally, the result collection module outputs the audit results.

[0128] In addition, it should be noted that the scope of application judgment module is used to make corresponding judgments on the input reimbursement object information such as the enterprise, document type and corresponding department, and determine whether these reimbursement object information all meet the reimbursement object requirements. In this way, it can be determined whether the reimbursement document is within the reimbursement scope. If the step is within the reimbursement scope, the inapplicable result is output to explain to the client that the reimbursement document is not within the reimbursement scope.

[0129] Specific as Fig.12 As shown, the workflow of the application scope judgment module is as follows:

[0130] S501: After obtaining the external input reimbursement order, determine whether the corresponding company can apply paperless; if yes, execute step S502; if no, directly execute step S504.

[0131] S502: Determine whether the corresponding document type can be applied to paperless; if so, execute step S503; if not, execute step S504.

[0132] S503: Determine whether the corresponding department is within the applicable scope; then execute step S504.

[0133] S504: Collect applicable results and finally output the applicable results.

[0134] In addition, if Fig.13 As shown, the rule checker module has two modes, preset rule mode and custom rule mode. The difference between the two rule modes is that the rules preset in the preset rule mode are the existing paperless audit business rules and can be used directly; the custom rule mode requires the configuration of rules according to needs. The specific process is as follows:

[0135] S601: For the reimbursement document input externally, select a mode, that is, select a configuration item; and execute step S602 or step S603 respectively.

[0136] S602: Preset rule mode, including preset rule A, preset rule B, and even preset rule N, and finally outputting applicable results according to the preset rules.

[0137] S603: Custom rule mode, including custom rule A, custom rule B, and even custom rule N (expandable), and finally outputs applicable results.

[0138] In addition, combined Fig.13 The rule checker module shown in the figure, for the specific core rules of paperless audit, see Fig.14 , Fig.14 The core rules for paperless auditing of the rule checker module shown include:

[0139] S701: First, determine whether the reimbursement document meets Rule A. Rule A has the highest priority, which is priority 1. Its specific rule is that there is no expense category or the expense amount is 0. If it meets the requirement, it is directly output as paperless. If it does not meet the requirement, execute step S702. The structure of the reimbursement document is as follows: Fig. 9 shown.

[0140] S702: intermediate processing matters, cyclically verifying each expense; taking one expense from the expense list each time, and then entering S703; this step is first entered by the above step S701, and subsequently entered by step S707.

[0141] S703: Determine whether Rule B is met. The priority of Rule B is 2, and its specific rules are as follows: there is no order but there is an invoice, and all invoices meet the requirements, which means there is no paper; if not, execute step S704.

[0142] S704: Determine whether Rule C is met. The priority of Rule C is 3, and its specific rules are as follows: if there is an order and it is a public payment order, it is paperless; if not, execute step S705.

[0143] S705: Determine whether Rule D is met. The priority of Rule D is 4, and its specific rules are as follows: there is an order and it is an individual payment order, and all invoices meet the requirements, which is paperless; if not, execute step S706: Determine whether Rule E is met. The priority of Rule E is 5, and its specific rules are as follows: there is an order and it is an individual payment order, and the fee amount is 0, which is paperless; if not, execute step S707.

[0144] S707: Determine whether the rule N is met. The rule N is extensible. If so, execute step S708; if not, directly determine that it is not paperless.

[0145] S708: Determine whether there is the next expense. If so, return to step S702; if not, directly determine that there is no paper.

[0146] In summary, the technical solution of the present application can solve the problems in the existing reimbursement process that the offline paper reimbursement process is long, the steps are cumbersome and the efficiency is low. Compared with the existing technical solutions mentioned in the background technology, the paperless audit solution provided by the present application can automatically audit in real time without manual intervention, and has high processing efficiency; supports the configuration of paperless application scope (subsidiary level, department level); supports paperless audit of data from multiple sources (expenses, invoices, orders); supports the audit of original invoices; supports the configuration of the priority of the rule verifier in the form of a chain of responsibility; supports the use of preset rule modes and custom rule modes; preset rules can be paperless audit business rules used by specific enterprises and departments; the rule verifier is highly extensible and can cover most scenarios.

[0147] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the paperless audit method used in the reimbursement scenario of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0148] In addition, the paperless audit device for reimbursement scenarios provided in the present application includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the paperless audit method for reimbursement scenarios of any of the above-mentioned embodiments.

[0149] Reference below Fig.15, which shows a schematic diagram of the structure of a paperless audit device for reimbursement scenarios suitable for implementing the embodiments of the present application. The paperless audit device for reimbursement scenarios in the embodiments of the present application can include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.15 The paperless audit device shown for reimbursement scenarios is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present application.

[0150] like Fig.15 As shown, the paperless audit device for reimbursement scenarios can include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the paperless audit device for reimbursement scenarios are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can enable the paperless audit device for reimbursement scenarios to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a model building device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0151] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0152] The paperless audit device for reimbursement scenarios provided by the present application adopts the paperless audit method for reimbursement scenarios in the above-mentioned embodiment. Compared with the prior art, the beneficial effects of the paperless audit device for reimbursement scenarios provided by the present application are the same as the beneficial effects of the paperless audit method for reimbursement scenarios provided by the above-mentioned embodiment, and other technical features in the paperless audit device for reimbursement scenarios are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0153] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0154] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

[0155] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the paperless audit method for reimbursement scenarios in the above-mentioned embodiments.

[0156] The computer-readable storage medium provided in the present application can be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium can be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0157] The computer-readable storage medium carries one or more programs, and when the one or more programs are executed by the model building device, the computer program code for performing the operation of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, through the Internet using an Internet service provider).

[0158] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes also be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs a specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0159] The modules involved in the embodiments of the present application can be implemented by software or hardware, wherein the name of the module does not limit the unit itself in some cases.

[0160] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned paperless audit method for reimbursement scenarios. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the paperless audit method for reimbursement scenarios provided in the above-mentioned embodiments, and will not be described in detail here.

[0161] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the paperless audit method for reimbursement scenarios as described above.

[0162] The computer program product provided by this application can solve the technical problems solved by the existing methods. Compared with the existing technology, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the paperless audit method for reimbursement scenarios provided by the above embodiment, which will not be repeated here.

[0163] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A paperless audit method for reimbursement scenarios, characterized in that: include: Listen to the reimbursement request initiated by the client, and obtain the reimbursement source data corresponding to the reimbursement request; Integrate the reimbursement source data according to the reimbursement request to generate a paperless reimbursement document corresponding to the reimbursement request; Using a verification chain that connects multiple business verification rules, the reimbursement document is paperlessly reviewed according to the expense dimension of the reimbursement document; When the paperless review of the reimbursement document is passed, the paperless reimbursement document and the corresponding reimbursement source data are pushed to the corresponding reimbursement system for approval and reimbursement.

2. The paperless audit method according to claim 1, characterized in that: The step of monitoring the reimbursement request initiated by the client and obtaining the reimbursement source data corresponding to the reimbursement request includes: Get the reimbursement source data uploaded by the client; Connecting to the data issuance system corresponding to the reimbursement source data, and extracting reimbursement identification information from the data issuance system; Using the reimbursement identification information to identify and verify the reimbursement source data; When the identification and verification of the reimbursement source data is passed, a source type and a sequence ID of the reimbursement source data are generated, and the sequence ID is used to store the reimbursement source data in a database of the corresponding source type.

3. The paperless audit method according to claim 1 or 2, characterized in that: The step of integrating the reimbursement source data according to the reimbursement request to generate a paperless reimbursement document corresponding to the reimbursement request includes: Obtaining the sequence ID included in the reimbursement request; Searching for multiple reimbursement source data from databases corresponding to different source types according to the sequence ID, wherein the reimbursement source data is stored in the database corresponding to the source type; An expense reimbursement instance is established, and the multiple reimbursement source data are integrated into the expense reimbursement instance according to the source type to obtain the paperless reimbursement document.

4. The paperless audit method according to claim 1, characterized in that: Before the step of using a verification chain having a plurality of business verification rules connected in series to perform paperless review on the reimbursement document according to the expense dimension of the reimbursement document, the method further includes: Extracting multiple reimbursement object information from the reimbursement document; Determining whether the multiple pieces of reimbursement object information all meet the corresponding reimbursement object requirements; If it is determined that any of the multiple reimbursement object information does not meet the corresponding reimbursement object requirements, an inapplicable result is output; wherein the inapplicable result is used to indicate that the reimbursement document is not within the reimbursement applicable scope; If it is determined that the multiple reimbursement object information all meet the corresponding reimbursement object requirements, the step of using the verification chain that connects multiple business verification rules in series to perform paperless review of the reimbursement document according to the expense dimension of the reimbursement document is executed.

5. The paperless audit method according to claim 1, characterized in that: Before the step of using a verification chain having a plurality of business verification rules connected in series to perform paperless review on the reimbursement document according to the expense dimension of the reimbursement document, the method further includes: Setting a plurality of rule checkers, wherein each rule checker encapsulates a business check rule, and the business check rule is used to perform paperless review on the reimbursement document according to the source type of the reimbursement source data; According to the source type verified by the business verification rule, setting the arrangement priority of the multiple rule verifiers; According to the arrangement priority, the multiple rule checkers are connected in series in the form of responsibility chain to obtain the check chain.

6. The paperless audit method according to claim 5, characterized in that: The step of using a verification chain having a plurality of business verification rules connected in series to perform paperless review on the reimbursement document according to the expense dimension of the reimbursement document comprises: According to the sequence of the verification chain, the multiple rule verifiers are used to perform paperless review on the reimbursement document based on the expense dimension; Determine whether the expense of the reimbursement document meets the expense requirements corresponding to the source type specified in the business verification rule; If the expense of the reimbursement document meets the expense requirement, determining that the reimbursement document and the corresponding reimbursement source data meet the paperless review conditions; When all rule checkers in the verification chain determine that the reimbursement document and the corresponding reimbursement source data meet the paperless review conditions, it is determined that the paperless review of the reimbursement document has passed, and the step of pushing the paperless reimbursement document and the corresponding reimbursement source data to the corresponding reimbursement system for approval and reimbursement is executed.

7. The paperless audit method according to claim 6, characterized in that: After the step of using a verification chain having a plurality of business verification rules connected in series to perform paperless review on the reimbursement document according to the expense dimension of the reimbursement document, the method further includes: When the paperless review of the reimbursement document fails, the reimbursement source data that meets the paperless review conditions is pushed to the reimbursement system for approval and reimbursement, and an approval failure notification is sent to the client, wherein the approval failure notification includes a notification message of the reimbursement source data that does not meet the paperless review conditions; When the reimbursement document is not within the reimbursement applicable scope, a paperless non-applicability notification is sent to the client.

8. A paperless audit device for reimbursement scenarios, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the paperless audit method for reimbursement scenarios as described in any one of claims 1 to 7.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the paperless audit method for reimbursement scenarios as described in any one of claims 1 to 7 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the paperless audit method for reimbursement scenarios as claimed in any one of claims 1 to 7 are implemented.

Images