Tree-shaped cross-audit method, device, electronic device and storage medium

Abstract

The present invention provides a tree-shaped cross-audit method, device, electronic device and storage medium, which can generate an audit tree corresponding to a service configuration file. The audit tree contains at least one audit point, and each audit point has a corresponding tree structure. The nodes in the tree structure are audit branches with audit criteria, and the audit branches belonging to the leaf nodes have corresponding audit results. Based on this, after obtaining a contract file to be audited, the target audit point in the contract file can be determined according to the audit points in the audit tree, and then the contract file can be cross-compared according to the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit point, so as to obtain the target audit result corresponding to the contract file.

Description

Technical Field

[0001] The present invention relates to the field of software technology, and more particularly, to a tree-shaped cross-audit method, device, electronic device, and storage medium. Background Art

[0002] Currently, intelligent auditing is only based on OCR (Optical Character Recognition) of single words. Usually, the entire OCR text is recognized, and the audit terms are configured as rules. When the OCR text hits the audit terms, a prompt is given, and the information of the audit terms and the audit criteria are compared manually. For example, whether the information of audit terms such as "contract date", "business license validity period", "invoice number" in the material meets their respective audit criteria.

[0003] This requires a large amount of manual business comparison to determine whether the entire material meets the requirements of the audit criteria in the supply chain finance business. Summary of the Invention

[0004] In view of this, to solve the above problems, the present invention provides a tree-shaped cross-audit method, device, electronic device, and storage medium, and the technical solutions are as follows:

[0005] A tree-shaped cross-audit method, the method includes:

[0006] Generating an audit tree corresponding to the service configuration file, where the audit tree includes at least one audit point, each audit point has a corresponding tree structure, the nodes in the tree structure are audit branches with corresponding audit criteria, and the audit branches belonging to the leaf nodes have corresponding audit results;

[0007] Obtaining a contract file to be audited, and determining the target audit point in the contract file according to the audit points in the audit tree;

[0008] Cross-comparing the contract file according to the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit point to obtain the target audit result corresponding to the contract file.

[0009] Preferably, the generating an audit tree corresponding to the service configuration file includes:

[0010] Splitting at least one audit point and the description information of each audit point from the service configuration file;

[0011] For each review point, split the subject and object from the description information of the review point, and determine the predicate as the comparison logic; combine the subject, predicate, and object to obtain the review criteria corresponding to the review point, and configure it as the review branch corresponding to the review point; combine the review branches corresponding to the review point as nodes, and configure the corresponding review results for the review branches belonging to the leaf nodes to obtain the tree structure corresponding to the review point;

[0012] Combine the tree structures corresponding to each of the at least one review point to obtain the review tree corresponding to the service configuration file.

[0013] Preferably, there are multiple service configuration files; generating the review tree corresponding to the service configuration file further includes:

[0014] Perform cross-configuration of review points and review branches for the review trees corresponding to each service configuration file to obtain a honeycomb-shaped review tree with multi-file intersection.

[0015] Preferably, generating the review tree corresponding to the service configuration file further includes:

[0016] Obtain the review scales with mutually replaceable logics, and configure the obtained review scales into the tree structure corresponding to the specified review point in the review tree.

[0017] Preferably, cross-comparing the contract file according to the review criteria corresponding to the review branches in the tree structure corresponding to the target review point includes:

[0018] Cross-compare the contract file according to the review criteria and review scales corresponding to the review branches in the tree structure corresponding to the target review point.

[0019] A tree-shaped cross-review device, the device includes:

[0020] A review tree generation module, configured to generate a review tree corresponding to a service configuration file, the review tree includes at least one review point, each review point has a corresponding tree structure, the nodes in the tree structure are review branches with corresponding review criteria, and the review branches belonging to the leaf nodes have corresponding review results;

[0021] A cross-comparison module, configured to obtain a contract file to be reviewed, determine the target review point in the contract file according to the review points in the review tree; cross-compare the contract file according to the review criteria corresponding to the review branches in the tree structure corresponding to the target review point to obtain the target review result corresponding to the contract file.

[0022] Preferably, the review tree generation module is specifically configured to:

[0023] Split at least one review point and the description information of each review point from the service configuration file; for each review point, split the subject and object from the description information of this review point, and determine the predicate as the comparison logic; combine the subject, predicate, and object to obtain the review criteria corresponding to this review point, and configure it as the review branch corresponding to this review point; combine the review branches corresponding to this review point as nodes, and configure the corresponding review results for the review branches belonging to the leaf nodes to obtain the tree structure corresponding to this review point; combine the tree structures corresponding to the at least one review point to obtain the review tree corresponding to the service configuration file.

[0024] Preferably, the review tree generation module is further configured to:

[0025] In the case where there are multiple service configuration files, perform cross-configuration of review points and review branches for the review trees corresponding to each service configuration file to obtain a honeycomb-shaped review tree with multi-file cross.

[0026] An electronic device, the electronic device includes: at least one memory and at least one processor; the memory stores an application program, the processor calls the application program stored in the memory, and the application program is used to implement the tree-shaped cross-review method.

[0027] A storage medium stores computer program code, and when the computer program code is executed, it implements the tree-shaped cross-review method.

[0028] Compared with the prior art, the beneficial effects achieved by the present invention are:

[0029] The present invention provides a tree-shaped cross-review method, device, electronic device and storage medium, which can generate a review tree corresponding to a service configuration file. The review tree contains at least one review point, and each review point has a corresponding tree structure. The nodes in the tree structure are review branches with review criteria, and the review branches belonging to the leaf nodes have corresponding review results. Based on this, after obtaining the contract file to be reviewed, the target review point in the contract file can be determined according to the review points in the review tree, and then the contract file can be cross-compared according to the review criteria corresponding to the review branches in the tree structure corresponding to the target review point, so as to obtain the target review result corresponding to the contract file. Based on the present invention, the data information in the business process can be organically combined into a review tree. Using this review tree as a standard library, cross-review point comparison of multiple files or comparison between elements within a single file can be completed. After splitting the review criteria in supply chain finance trade, the standard library is configured, and then the review result is output. Description of the Drawings

[0030] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can also be obtained based on the provided drawings.

[0031] Figure 1 It is the method flow chart of the tree-shaped cross-audit method provided by the embodiment of the present invention;

[0032] Figure 2 It is an example of the audit tree provided by the embodiment of the present invention;

[0033] Figure 3 It is a partial method flow chart of the tree-shaped cross-audit method provided by the embodiment of the present invention;

[0034] Figure 4 It is the structural schematic diagram of the tree-shaped cross-audit device provided by the embodiment of the present invention. Detailed implementation manners

[0035] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.

[0036] To make the above objects, features, and advantages of the present invention more obvious and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific implementation manners.

[0037] Comparing with the audit competitors in the market, usually the entire OCR text is identified, the audit terms are configured as rules, and when the audit terms are hit in the text, a prompt will be given. Still, a large amount of manual business comparison is required to determine whether the document meets the requirements. To solve this problem, the present invention provides a tree-shaped cross-audit method. The tree-shaped cross-audit in the present invention is mainly different from the single OCR word recognition and hit audit. The audit criteria are transformed into a tree structure, and at the same time, multiple files can be cross-configured to form a honeycomb-shaped audit tree for multi-file cross. As a standard library, based on this standard library, users can upload one or more files. The underlying audit logic will identify the audit results of each detailed audit criterion through intelligent algorithms, cross-compare multiple results, and obtain an intelligent audit result list of the overall material items. The results of all audit points can be visually presented in a tree shape, which is clear at a glance for the auditors.

[0038] See Figure 1 , Figure 1It is the method flow chart of the tree - shaped cross - review method provided by the embodiments of the present invention. The tree - shaped cross - review method includes the following steps:

[0039] S10, generate a review tree corresponding to the service configuration file. The review tree contains at least one review point, and each review point has a corresponding tree - shaped structure. The nodes in the tree - shaped structure are review branches with review criteria, and the review branches belonging to the leaf nodes have corresponding review results.

[0040] In the embodiments of the present invention, using the existing single OCR recognition technology, multiple review results are combined with the data information in the business process and organically combined into a review tree, and the review tree is regarded as the standard library.

[0041] The service configuration file contains business rules. The business rules are split into business requirements. For example, in the actual scenario, basic information standard splitting, China Securities Depository and Clearing Corporation Limited (CSDC) model addition, CSDC standard splitting, contract standard splitting, invoice standard splitting, credit reference letter standard splitting, and IOU standard splitting, etc. can be carried out. The business requirements (i.e., review terms) obtained by splitting are the review points. Then, the review word library of the review points is split, the review criteria are combined, the review results are configured, and the review criteria and review results are combined and configured. In the form of cross - configuration, the rule tree configuration required for the material file can be completed.

[0042] See Figure 2 , Figure 2 It is an example of the review tree provided by the embodiments of the present invention. See Figure 2 , Figure 2 It is the review tree obtained by splitting the business contract standard. In this review tree, there are three review points: review point 1 - the main body of Party A, review point 2 - the main body of Party B, and review point 3 - whether the alteration and PS of the document meet the requirements. Continue to see Figure 2 , review point 1 - the main body of Party A, review point 2 - the main body of Party B, and review point 3 - whether the alteration and PS of the document meet the requirements each have corresponding tree - shaped structures. Taking review point 1 - the main body of Party A as an example, the tree - shaped structure corresponding to this review point 1 - the main body of Party A contains four review branches, and each review branch has a corresponding review criterion, that is, "the name of Party A's enterprise is not equal to null" (subsequently referred to as review criterion 1), "the name of Party A's enterprise is equal to null" (i.e., Figure 2 at the same level as review criterion 1 in the figure, represented by "otherwise" in the figure, subsequently referred to as review criterion 2), "the name of the seal is equal to the name of Party A's enterprise; the name of the seal is equal to the purchaser; the name of the seal is equal to the name of the issuer" (subsequently referred to as review criterion 3), "the name of the seal is not equal to the name of Party A's enterprise; the name of the seal is not equal to the purchaser; the name of the seal is not equal to the name of the issuer" (i.e., Figure 2 at the same level as review criterion 3 in the figure, represented by "otherwise" in the figure, subsequently referred to as review criterion 4).

[0043] It should be noted that among the three conditions in Review Criterion 3, namely "the chapter name is equal to the name of Party A's enterprise", "the chapter name is equal to the name of the purchaser", and "the chapter name is equal to the name of the issuer", they are in an "or" relationship. That is to say, as long as any one of the conditions "the chapter name is equal to the name of Party A's enterprise", "the chapter name is equal to the name of the purchaser", and "the chapter name is equal to the name of the issuer" is met, it can be considered that "the review is passed". Similarly, among the three conditions in Review Criterion 4, namely "the chapter name is not equal to the name of Party A's enterprise", "the chapter name is not equal to the name of the purchaser", and "the chapter name is not equal to the name of the issuer", they are in an "and" relationship. That is to say, when all three conditions "the chapter name is not equal to the name of Party A's enterprise", "the chapter name is not equal to the name of the purchaser", and "the chapter name is not equal to the name of the issuer" are met simultaneously, it can be considered that "the review fails and the seal of Party A cannot be identified".

[0044] Continuing with the example of Review Point 1 - Party A's entity for illustration, the tree structure corresponding to this Review Point 1 - Party A's entity has four nodes (i.e., four review branches), which respectively correspond to Review Criterion 1, Review Criterion 2, Review Criterion 3, and Review Criterion 4. The review branch corresponding to Review Criterion 3 is a child node of the review branch corresponding to Review Criterion 1. The review branches corresponding to Review Criterion 2, Review Criterion 3, and Review Criterion 4 are leaf nodes. Specifically, the review result corresponding to the review branch of Review Criterion 2 is "the review fails, and there is no Party A's entity in the contract", the review result corresponding to the review branch of Review Criterion 3 is "the review is passed", and the review result corresponding to the review branch of Review Criterion 4 is "the review fails and the seal of Party A cannot be identified".

[0045] When the review path node is configured with multiple branches, the review branches can be selected according to the priority. When one of the review branches is triggered, the other review branches do not perform the review. Continue to refer to Figure 2For the same level of audit standards 1 and 2, the audit branch 1 corresponding to audit standard 1 has a priority of 1, while the audit branch 2 corresponding to audit standard 2 has a priority of 2, that is, audit standard 1 is executed first, and if audit standard 1 is met, audit standard 3 is continued to be executed; if audit standard 1 is not met, audit standard 2 is continued to be executed, and the audit result "audit failed, the contract does not have Party A" is output; similarly, for the same level of audit standards 3 and 4, the audit branch 1 corresponding to audit standard 3 has a priority of 1, while the audit branch 2 corresponding to audit standard 4 has a priority of 2, that is, audit standard 3 is executed first, and if audit standard 3 is met, the audit result "audit passed" is output; if audit standard 3 is not met, audit standard 4 is continued to be executed, and the audit result "audit failed, Party A's seal cannot be identified" is output. Based on this, for the Party A subject in the business contract, the three-party rules of the seal name in the contract and the elements (purchaser) and business point (issuer name) of the invoice can be configured. After the configuration is completed, after the system performs cross-comparison, it can be known whether the audit point of the business contract - Party A subject meets the requirements. The same applies to other audit points.

[0046] In the specific implementation process, step S10 "generating an audit tree corresponding to the business configuration file" can adopt the following steps, and the method flow chart is as follows: Figure 3 As shown:

[0047] S101, extracting at least one audit point and description information of each audit point from a service configuration file.

[0048] In the embodiment of the present invention, different business requirements can be configured as different audit points, and then at least one audit point can be separated from the business configuration file. Accordingly, the text description of the audit point is the description information of the audit point.

[0049] S102, for each audit point, separate the subject and object from the description information of the audit point, and determine the predicate as the comparison logic; obtain the audit standard corresponding to the audit point by combining the subject, predicate and object, and configure it as the audit branch corresponding to the audit point; combine the audit branches corresponding to the audit point as nodes, and configure the corresponding audit results for the audit branches belonging to the leaf nodes, so as to obtain the tree structure corresponding to the audit point.

[0050] In the embodiments of the present invention, for each review point, the subject and object can be split from the description information of the review point to construct a review vocabulary. Moreover, by matching the preset comparison logic, the predicate serving as the comparison logic in the description information of the review point can be determined. For example, "checked number", "seal color", "seal name", "seal type", "authorization period", "authorization business horizontal line content", "company name" can be used as the words in the review vocabulary, and words such as "less than", "not equal to", "greater than or equal to" all belong to the predicates serving as the comparison logic.

[0051] Furthermore, the existing DCR technology can be used to organically combine the subject and object located in the review vocabulary in each sentence of the description information, as well as the predicate closest to the subject and object in this sentence, and combine them into a phrase in the form of subject-predicate-object as the review criterion. For example, "seal name is not equal to empty", "invoice type is equal to ordinary VAT invoice".

[0052] Moreover, the review criterion obtained by organic combination is configured as review branch 1 (with a priority of 1) and combined as a node. Correspondingly, the node of review branch 2 (with a priority of 2) at the same level can be obtained. For example, "seal name is not equal to empty" is used as the node of review branch 1 (with a priority of 1), and the node of the review branch 2 (with a priority of 2) at the same level is "seal name is equal to empty". Of course, the execution order of the review criteria can also be preconfigured. For example, first execute the review criterion "seal name is not equal to empty", and if this review criterion is met, then execute the review criterion "invoice type is equal to ordinary VAT invoice", so as to configure all the review criteria under this review point as nodes for combination. And for the review branches that belong to the leaf nodes, corresponding review results can be configured for them, so as to obtain the tree structure corresponding to this review point.

[0053] It should be noted that the review results are divided into two categories: "review passed" and "review failed". For the category of "review failed", the reason for failure can also be configured according to the actual scenario and returned as the result. Continue to refer to Figure 2 Taking review point 1 - Party A's entity as an example for continued illustration, the review result of the review branch corresponding to review criterion 3 is "review passed", and the review results of the review branches corresponding to review criteria 2 and 4 are both "review failed". For this, the reasons for failure can be configured respectively, that is, the review result of the review branch corresponding to review criterion 2 is "review failed, the contract has no Party A's entity", and the review result of the review branch corresponding to review criterion 4 is "review failed, the seal of Party A cannot be identified".

[0054] S103. Combine the tree structures corresponding to at least one review point to obtain the review tree corresponding to the service configuration file.

[0055] In the embodiments of the present invention, after obtaining the tree structures corresponding to each review point, they can be combined to obtain the review tree corresponding to the service configuration file. Since multiple review points can be configured in the review tree, the review result is a multi-dimensional and multi-path result.

[0056] In some embodiments, the present invention can also support cross-configuration of multiple files simultaneously to construct a honeycomb-shaped review tree with multi-file cross. Specifically, when there are multiple service configuration files, step S10 "generating the review tree corresponding to the service configuration file" can also adopt the following steps:

[0057] Perform cross-configuration of review points and review branches on the review trees corresponding to each service configuration file to obtain a honeycomb-shaped review tree with multi-file cross.

[0058] In the embodiments of the present invention, each service configuration file can generate its corresponding review tree according to the above description. Therefore, among the service configuration files, there can be the same review points and the same review branches in the review tree. Taking service configuration file 1 and service configuration file 2 as an example, where:

[0059] The review tree corresponding to service configuration file 1 includes review points a and b. The nodes in the tree structure corresponding to review point a include the review branches corresponding to review criteria 5, 6, 7, and 8, and the nodes in the tree structure corresponding to review point b include the review branches corresponding to review criteria 9 and 10. The review tree corresponding to service configuration file 2 includes review points a and c. The nodes in the tree structure corresponding to review point a include the review branches corresponding to review criteria 5, 6, 11, and 12, and the nodes in the tree structure corresponding to review point c include the review branches corresponding to review criteria 13 and 14. After performing cross-configuration of review points and review branches on the review trees corresponding to service configuration file 1 and service configuration file 2 respectively, the obtained honeycomb-shaped review tree with multi-file cross includes review points a, b, and c. Among them, the nodes in the tree structure corresponding to review point a include the review branches corresponding to review criteria 5, 6, 7, 8, 11, and 12, the nodes in the tree structure corresponding to review point b include the review branches corresponding to review criteria 9 and 10, and the nodes in the tree structure corresponding to review point c include the review branches corresponding to review criteria 13 and 14.

[0060] In addition, when manual review is carried out and the description document needs to be stamped with the company seal, in some scenarios, both the company's human resources seal and the company's official seal are recognized as correct for this document. Therefore, for such situations where both the human resources seal and the company's official seal are acceptable, it is described as scale review in manual review. In this regard, in the intelligent review of the present invention, this is implemented as a logic where the human resources seal and the company seal are mutually replaceable. In this regard, step S10 "generating an audit tree corresponding to the service configuration file" can also adopt the following steps:

[0061] Obtain the audit scale of the mutually replaceable logic, and configure the obtained audit scale into the tree structure corresponding to the specified audit point in the audit tree.

[0062] In the embodiment of the present invention, for a specified audit point in the audit tree, an audit scale can be configured for a certain audit branch thereof, so that the tree structure corresponding to this audit point is configured by combining an audit branch with a corresponding audit standard, an audit scale, and an audit result. After adding the audit scale, the current node and all subsequent stages use this audit scale.

[0063] For easy understanding, examples of audit scales are given. "The name of Party A's enterprise is mutually equivalent to the invoice code", "The core enterprise company is mutually equivalent to the nature of the enterprise", "The legal person name is mutually equivalent to the signature of the legal person of Party A", etc. can all be used as audit scales.

[0064] For easy understanding, continue to refer to Figure 2 , taking audit point 1 - Party A's main body as an example for illustration. Assume that the audit scale "The name of Party A's enterprise is mutually equivalent to the invoice code" is configured for the audit branch corresponding to audit standard 1 in the tree structure corresponding to audit point 1 - Party A's main body. In this regard, since the priority of audit branch 1 corresponding to audit standard 1 is 1, audit standard 1 is executed first. If audit standard 1 is not met, then continue to execute the audit scale of audit standard 1, "The name of Party A's enterprise is mutually equivalent to the invoice code", that is, if the invoice code is not equal to null, then continue to execute audit standard 3. Conversely, if the invoice code is null, then continue to execute audit standard 2.

[0065] S20. Obtain the contract file to be audited, and determine the target audit point in the contract file according to the audit points in the audit tree.

[0066] In the embodiment of the present invention, for the contract file to be audited, the contract file can be split to determine the audit points in it that are the same as those in the audit tree, and the determined audit points are used as the target audit points. Continuing with the Figure 2 illustrated audit tree as an example for illustration. Assume that the contract file is split to determine that the contract file contains audit point 1 - Party A's main body, then this audit point 1 - Party A's main body is used as the target audit point.

[0067] S30. Cross-compare the contract documents against the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit point to obtain the target audit result corresponding to the contract documents.

[0068] In the embodiments of the present invention, for ease of understanding, continue to use Figure 2 the shown audit tree as an example to illustrate. Assume that the target audit point is audit point 1 - Party A's entity. Then, the contract documents can be cross-compared according to the tree structure corresponding to this audit point 1 - Party A's entity. First, execute audit criterion 1. If audit criterion 1 is satisfied, continue to execute audit criterion 3. If audit criterion 1 is not satisfied, then continue to execute audit criterion 2, and output the audit result "Audit failed, the contract has no Party A's entity" (that is, the target audit result is "Audit failed, the contract has no Party A's entity"); after executing audit criterion 3, if audit criterion 3 is satisfied, output the audit result "Audit passed" (that is, the target audit result is "Audit passed"). If audit criterion 3 is not satisfied, then continue to execute audit criterion 4, and output the audit result "Audit failed, the seal of Party A cannot be identified" (that is, the target audit result is "Audit failed, the seal of Party A cannot be identified").

[0069] Of course, in some scenarios, if the audit scale has been configured in the tree structure corresponding to the target audit point, then step S30 "Cross-compare the contract documents against the audit criteria in the tree structure corresponding to the target audit point" can adopt the following steps:

[0070] Cross-compare the contract documents against the audit criteria and audit scales corresponding to the audit branches in the tree structure corresponding to the target audit point.

[0071] For ease of understanding, continue to use Figure 2 the shown audit tree as an example to illustrate. Assume that the target audit point is audit point 1 - Party A's entity. Continue to assume that the audit branch corresponding to audit criterion 1 is configured with the audit scale "The name of Party A's enterprise is equivalent to the invoice code". Then, if audit criterion 1 is not satisfied, continue to execute the audit scale "The name of Party A's enterprise is equivalent to the invoice code" of audit criterion 1. If the audit scale "The name of Party A's enterprise is equivalent to the invoice code" is satisfied, continue to execute audit criterion 3. On the contrary, if the audit scale "The name of Party A's enterprise is equivalent to the invoice code" is not satisfied, then continue to execute audit criterion 2.

[0072] The tree-shaped cross-audit method provided by the embodiments of the present invention configures audit terms (points to be audited in documents and business processes) as audit criteria in the tree-shaped audit tree, configures the audit flow according to the tree rules, and can directly return the corresponding audit passed or failed results after comparison, without the need for manual comparison again.

[0073] Based on the tree-shaped cross-audit method provided in the above embodiments, an embodiment of the present invention correspondingly provides a device for executing the tree-shaped cross-audit method. The structural schematic diagram of the device is as shown in Figure 4 and includes:

[0074] An audit tree generation module 10, configured to generate an audit tree corresponding to a service configuration file. The audit tree contains at least one audit point, and each audit point has a corresponding tree structure. The nodes in the tree structure are audit branches with corresponding audit criteria, and the audit branches belonging to the leaf nodes have corresponding audit results;

[0075] A cross-comparison module 20, configured to obtain a contract file to be audited, and determine the target audit points in the contract file according to the audit points in the audit tree; perform cross-comparison on the contract file according to the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit points, and obtain the target audit result corresponding to the contract file.

[0076] Optionally, the audit tree generation module 10 is specifically configured to:

[0077] Split at least one audit point and the description information of each audit point from the service configuration file; for each audit point, split the subject and object from the description information of the audit point, and determine the predicate as the comparison logic; combine the subject, predicate, and object to obtain the audit criteria corresponding to the audit point, and configure it as the audit branch corresponding to the audit point; combine the audit branches corresponding to the audit point as nodes, and configure the corresponding audit results for the audit branches belonging to the leaf nodes to obtain the tree structure corresponding to the audit point; combine the tree structures corresponding to at least one audit point respectively to obtain the audit tree corresponding to the service configuration file.

[0078] Optionally, the audit tree generation module 10 is further configured to:

[0079] In the case where there are multiple service configuration files, perform cross-configuration of audit points and audit branches for the audit trees corresponding to each service configuration file to obtain a honeycomb-shaped audit tree with multi-file cross.

[0080] Optionally, the audit tree generation module 10 is further configured to:

[0081] Obtain the audit scales with mutually replaceable logics, and configure the obtained audit scales into the tree structure corresponding to the specified audit points in the audit tree.

[0082] Optionally, the cross-comparison module 20 for performing cross-comparison on the contract file according to the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit points is specifically configured to:

[0083] Cross - compare the contract documents according to the audit criteria and audit scales corresponding to the audit branches in the tree - shaped structure corresponding to the target audit points.

[0084] It should be noted that for the refined functions of each module in the embodiments of the present invention, reference can be made to the corresponding publicly disclosed parts of the above - mentioned tree - shaped cross - audit method embodiments, which will not be elaborated here.

[0085] Based on the tree - shaped cross - audit method provided in the above - mentioned embodiments, an embodiment of the present invention provides an electronic device, which includes: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, and the application program is used to implement the tree - shaped cross - audit method.

[0086] Based on the tree - shaped cross - audit method provided in the above - mentioned embodiments, an embodiment of the present invention provides a storage medium, which stores computer program code, and when the computer program code is executed, it implements the tree - shaped cross - audit method.

[0087] The above has introduced in detail a tree - shaped cross - audit method, device, electronic device and storage medium provided by the present invention. Specific examples are used in this article to elaborate on the principle and implementation manner of the present invention. The description of the above embodiments is only used to help understand the method and its core idea of the present invention; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present invention.

[0088] It should be noted that each embodiment in this specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. The same or similar parts among the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method part.

[0089] It should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non - exclusive inclusion, so that a process, method, article or device including a series of elements inherently includes the elements, or further includes the elements inherent in these process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, article or device including the said element.

[0090] The foregoing description of the disclosed embodiments enables those skilled in the art to practice or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A tree-shaped cross-audit method, characterized in that, The method includes: generating an audit tree corresponding to the service configuration file, where the audit tree includes at least one audit point, each audit point has a corresponding tree structure, the nodes in the tree structure are audit branches with corresponding audit criteria, and the audit branches belonging to the leaf nodes have corresponding audit results; obtaining a contract file to be audited, and determining the target audit point in the contract file according to the audit points in the audit tree; performing cross-comparison on the contract file according to the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit point, to obtain the target audit result corresponding to the contract file; wherein, generating the audit tree corresponding to the service configuration file includes: splitting at least one audit point and the description information of each audit point from the service configuration file; for each audit point, splitting the subject and object from the description information of the audit point, and determining the predicate as the comparison logic; combining the subject, predicate, and object to obtain the audit criteria corresponding to the audit point, and configuring it as the audit branch corresponding to the audit point; combining the audit branches corresponding to the audit point as nodes, and configuring the corresponding audit results for the audit branches belonging to the leaf nodes, to obtain the tree structure corresponding to the audit point; combining the tree structures corresponding to the at least one audit point respectively to obtain the audit tree corresponding to the service configuration file; wherein, there are multiple service configuration files; generating the audit tree corresponding to the service configuration file further includes: performing cross-configuration of audit points and audit branches on the audit trees corresponding to each service configuration file to obtain a honeycomb-shaped audit tree with multi-file cross; 2. The method according to claim 1, characterized in that, generating the audit tree corresponding to the service configuration file further includes: obtaining the audit scales of mutually substitutable logics, and configuring the obtained audit scales into the tree structure corresponding to the specified audit point in the audit tree; 3. The method according to claim 2, characterized in that, wherein, performing cross-comparison on the contract file according to the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit point includes: performing cross-comparison on the contract file according to the audit criteria and audit scales corresponding to the audit branches in the tree structure corresponding to the target audit point; 4. A tree-shaped cross-audit device, characterized in that, The device includes: an audit tree generation module, configured to generate an audit tree corresponding to the service configuration file, where the audit tree includes at least one audit point, each audit point has a corresponding tree structure, the nodes in the tree structure are audit branches with corresponding audit criteria, and the audit branches belonging to the leaf nodes have corresponding audit results; a cross-comparison module, configured to obtain a contract file to be audited, and determine the target audit point in the contract file according to the audit points in the audit tree; perform cross-comparison on the contract file according to the audit criteria corresponding to the audit branches in the tree structure corresponding to the target audit point, to obtain the target audit result corresponding to the contract file; wherein, the audit tree generation module is specifically configured to: Split out at least one review point and the description information of each review point from the service configuration file; for each review point, split out the subject and object from the description information of this review point, and determine the predicate as the comparison logic; obtain the review criteria corresponding to this review point by combining the subject, predicate and object, and configure it as the review branch corresponding to this review point; combine the review branches corresponding to this review point as nodes, and configure the corresponding review results for the review branches belonging to the leaf nodes to obtain the tree structure corresponding to this review point; combine the tree structures corresponding to the at least one review point respectively to obtain the review tree corresponding to the service configuration file. The review tree generation module is further configured to: In the case where there are multiple service configuration files, perform cross-configuration of review points and review branches on the review trees corresponding to each service configuration file to obtain a honeycomb-shaped review tree with multi-file intersection.

5. An electronic device, characterized in that, The electronic device includes: at least one memory and at least one processor; the memory stores an application program, and the processor calls the application program stored in the memory, and the application program is used to implement the tree-shaped cross-review method according to any one of claims 1-3.

6. A storage medium, characterized in that, The storage medium stores computer program code, and when the computer program code is executed, it implements the tree-shaped cross-review method according to any one of claims 1-3.

Images