Contract risk dynamic scoring method and multistage examination and approval device

Abstract

The invention discloses a contract risk dynamic scoring method and a multi-level approval device, and belongs to the technical field of contract management, the method comprises the steps that risk fields in a contract form are extracted to form a to-be-verified list, and the risk fields are fields needing risk management and control in the contract form; extracting risk fields meeting trigger conditions in the to-be-verified list to form a target list, wherein the trigger conditions have corresponding weights; calculating the sum value of the weights corresponding to the risk fields in the target list to obtain a risk score; and matching a corresponding risk level according to the risk score. According to the invention, the risk assessment of the contract is realized through the preset triggering condition, and the efficiency and accuracy of contract management are improved.

Description

Technical Field

[0001] The present application belongs to the technical field of contract management, and specifically, relates to a contract risk dynamic scoring method and a multi-level approval device. Background Art

[0002] Contract management plays a vital role in the operation of modern enterprises, especially in enterprises with strict requirements for contract management. The review, approval and signing process of contracts is usually cumbersome and complicated. In the contract approval process, if the clauses related to contract risks are not effectively controlled, it may cause the enterprise to face legal, financial or reputation risks. Therefore, how to efficiently and accurately conduct contract risk assessment and reasonably formulate the approval process is a major challenge in the current contract management system.

[0003] Currently, most contract management systems still use traditional manual review and approval methods. This approval method relies on manual experience to judge the risk level of the contract and lacks support based on data and intelligent evaluation.

[0004] This approval method has the following problems:

[0005] 1. Inefficiency and subjectivity of manual review

[0006] Because the terms of contracts are complex and lengthy, manual review can easily miss important legal risks or potential business risks. Especially when the number of contracts is huge and involves multiple departments, the efficiency and accuracy of manual review face great challenges.

[0007] 2. Rigid and lengthy approval process

[0008] Many companies have pre-set, fixed approval processes that do not take into account the actual risk level of the contract. For example, a low-risk contract may still need to go through multiple levels of approval, resulting in low approval efficiency; while a high-risk contract may lack sufficient approval levels, increasing potential risks.

[0009] 3. Lack of intelligent risk assessment and dynamic process adjustment

[0010] Existing contract management systems usually do not have an intelligent risk assessment mechanism, and the approval process cannot be flexibly adjusted according to the specific risk situation of the contract, and cannot adapt to the personalized needs of contracts with different risk levels.

[0011] In view of this, this application is hereby filed. Summary of the invention

[0012] The technical problem to be solved by this application is to overcome the deficiencies of the prior art and provide a contract risk dynamic scoring method and a multi-level approval device.

[0013] In order to solve the above technical problems, the basic concept of the technical solution adopted in this application is:

[0014] In a first aspect of the present application, a contract risk dynamic scoring method is provided, the method comprising:

[0015] Extract risk fields in the contract form to form a to-be-verified list, wherein the risk fields are fields in the contract form that require risk control;

[0016] Extract risk fields that meet trigger conditions from the to-be-verified list to form a target list, wherein the trigger conditions have corresponding weights;

[0017] Calculating the sum of the weights corresponding to the risk fields in the target list to obtain a risk score;

[0018] The corresponding risk level is matched according to the risk score.

[0019] In a possible implementation, extracting the risk fields that meet the trigger condition in the to-be-verified list to form a target list includes:

[0020] A rule engine model is used to determine whether the risk field in the to-be-verified list meets the triggering condition;

[0021] If so, the risk fields that meet the triggering conditions are output to form a target list;

[0022] If not, delete the risk fields that do not meet the trigger conditions.

[0023] In a possible implementation: the method further includes: establishing a rule engine model;

[0024] The method for establishing a rule engine model comprises:

[0025] Filling configuration information into the initial rule template to obtain a final rule template, wherein the configuration information at least includes a trigger condition and a weight corresponding to the trigger condition;

[0026] Converting the final rule template into a final rule template of a Drools statement;

[0027] A rule engine model consists of a final rule template of at least one Drools statement.

[0028] In a possible implementation, the step of extracting the risk fields in the contract form to form a to-be-verified list includes:

[0029] Extracting key fields from the contract form;

[0030] Determining a field in the key field that is used for comparison with the trigger condition as a risk field;

[0031] The to-be-verified list is composed of at least one of the risk fields.

[0032] In a possible implementation: the key fields include at least the contract number, the total contract amount and the specified period;

[0033] The determining that a field in the key field that is used for comparison with the trigger condition is a risk field includes:

[0034] When the trigger condition is a preset contract amount, determining the total contract amount in the key field as a risk field, and the total contract amount is used for comparison with the preset contract amount; or

[0035] When the trigger condition is a preset deadline, determining the specified deadline in the key field as a risk field, and the specified deadline is used for comparison with the preset deadline; or

[0036] When the trigger conditions are a preset contract amount and a preset term, the total contract amount and the specified term in the key fields are determined to be risk fields, the total contract amount is used to compare with the preset contract amount, and the specified term is used to compare with the preset term.

[0037] In a possible implementation manner: the risk level includes at least a low risk level, a medium risk level and a high risk level, and different risk levels correspond to different risk scores.

[0038] In a second aspect of the present application, a multi-level approval device is provided, which is used to execute the above-mentioned contract risk dynamic scoring method, and the device includes:

[0039] The risk assessment module is used to match the corresponding risk level according to the risk score of the contract form;

[0040] An approval process module, used to select a corresponding approval process template from an approval process template library according to the risk level;

[0041] The approval execution module is used to send the contract form to the terminal of the approver involved in the approval process template.

[0042] In a possible implementation: the approval process template library includes a first approval process template, a second approval process template and a third approval process template, the first approval process template corresponds to a low risk level, the second approval process template corresponds to a medium risk level, and the third approval process template corresponds to a high risk level.

[0043] In a possible implementation manner: the number of approving personnel involved in the first approval process template < the number of approving personnel involved in the second approval process template < the number of approving personnel involved in the third approval process template.

[0044] In a possible implementation, a data display module is also included, and the data display module is used to display a risk assessment report, and the risk assessment report includes a risk score and an approval process of a contract form.

[0045] After adopting the above technical solution, the present application has the following beneficial effects compared with the prior art:

[0046] 1. This application supports user-defined configuration of the rule engine model. At the same time, users can also customize the risk level and the approval process template corresponding to the risk level. When the risk field meets the trigger condition, the risk score is calculated and different approval process templates are obtained according to the risk score matching. Different approval process templates correspond to different approval processes and approvers, so that this application can automatically manage the contract approval process without manual intervention, which improves the automation and flexibility of the contract approval process;

[0047] 2. This application is filled in by the user with configuration information, which continuously enriches and improves the rule engine model, allowing users to flexibly match different approval processes through low-code or no-code methods, greatly simplifying the management and adjustment of approval processes. Compared with the hard-coded and fixed approval process in traditional systems, this application provides higher customization and adaptability, and can respond to changes in contract risks in real time. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The accompanying drawings are part of this application and are used to provide a further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application, but do not constitute an improper limitation on this application. Obviously, the drawings described below are only some embodiments. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0049] Figure 1 It is a flow chart of a contract risk dynamic scoring method in an embodiment of the present application.

[0050] Figure 2 It is a system block diagram of a multi-level approval device in an embodiment of the present application.

[0051] Explanation of the accompanying drawings: 1. Risk assessment module; 2. Approval process module; 3. Approval execution module; 4. Data display module.

[0052] It should be noted that these drawings and textual descriptions are not intended to limit the conceptual scope of the present application in any way, but rather to illustrate the concepts of the present application for those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the following will be combined with the appended Figure 1-2 , the technical solutions in the embodiments are described clearly and completely. The following embodiments are used to illustrate the present application but are not used to limit the scope of the present application.

[0054] In the description of the present application, it should be noted that the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or apparatuses.

[0055] In the description of this application, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0056] like Figure 1 As shown, the present application provides a contract risk dynamic scoring method, which mainly performs risk assessment on contract forms based on a dynamic rule engine, so as to facilitate the subsequent execution of the corresponding contract approval process based on the risk assessment, while ensuring the security of the contract form, it can also improve the efficiency, flexibility and accuracy of contract form management. The following are the specific steps of the contract risk dynamic scoring method of the present application.

[0057] Step S1: extract risk fields in the contract form to form a to-be-verified list, where the risk fields are fields in the contract form that require risk management and control.

[0058] The contract form includes at least one contract, which contains the cooperation agreement between the enterprise or institution and the partner. The agreed content includes but is not limited to the cooperation content, the total contract amount and the specified period. The enterprise or institution then generates the contract type and contract number according to the specific content of the cooperation to obtain a complete contract.

[0059] Based on the obtained contract form, a deep learning model is used to extract the key fields in the contract form, such as any one of CNN, RNN, LSTM and Transformer. Specifically, the key fields are defined in advance by the user. The key fields are fields in the contract that contain important information. Depending on the type of contract, the key fields may be different. For example, if the contract type is a sales contract, the key fields at least include the contract number, the total contract amount and the specified period. Among them, the contract number is used to distinguish different contracts, the total contract amount is the cooperation remuneration agreed in the contract, and the specified period is the delivery time agreed in the contract.

[0060] Furthermore, the fields in the key fields that require risk control are called risk fields. For example, the key fields include the contract number, the total contract amount and the specified period. Since the total contract amount and the specified period are the contents agreed upon by both parties and are factors that affect the security of the contract, they are the key control objects, namely the total contract amount and the specified period, which are risk fields.

[0061] After obtaining the risk field, the risk field is output as a to-be-verified list. Specifically, the to-be-verified list is a structured data format, such as JSON format or Java format, so after obtaining the risk field, the risk field is converted into a structured data format, thereby outputting the to-be-verified list. The to-be-verified list can be formed by concatenating multiple risk fields after conversion, or by converting a single risk field. To facilitate the explanation of the structured data format of the to-be-verified list, the following is a specific example:

[0062] {

[0063] "contractId":"C12345",

[0064] "amount":150000,

[0065] "paymentTerms":60,

[0066] "clauses":[

[0067] {

[0068] "type":"payment",

[0069] "description":"The payment term is 60days."

[0070] },

[0071] {

[0072] "type":"penalty",

[0073] "description":"A penalty of 5% will be applied for late payments."

[0074] } ]

[0076] }

[0077] Among them, contractId represents the contract number, C12345 represents the contract number value, amount represents the total contract amount, 150000 represents the total contract amount value, paymentTerms represents the specified period, and 60 represents the specific number of days of the specified period, so C12345, 150000, and 60 are the key fields of the contract in this example. In this example, since there is a penalty for the specified period, namely "payment", the specified period is a field that needs to be risk controlled, and the specified period (60 days) is used as a risk field. Correspondingly, when the specified period is exceeded, a 5% penalty will be imposed.

[0078] Therefore, through step S1, the risk field can be extracted from the contract form to obtain a list to be verified, and then step S2 is entered.

[0079] Step S2: extract risk fields that meet the trigger conditions in the to-be-verified list to form a target list, and the trigger conditions have corresponding weights.

[0080] First, call up the rule engine model. The rule engine model is established in advance, and the establishment process is: the user first fills in the configuration information. The configuration information includes at least the trigger condition and the weight corresponding to the trigger condition. The trigger condition is used to evaluate whether the risk field really needs to be controlled. When the risk field reaches the trigger condition, it means that the risk field really needs to be controlled, and the specific method of control is related to the weight corresponding to the trigger condition. Then, fill the configuration information into the initial rule template to obtain the final rule template. The initial rule template is defined in advance. The initial rule template includes the rule name, condition, weight and approver. The larger the weight, the more corresponding approvers there are, so as to achieve the purpose of different weights corresponding to different controls. In a specific example, the initial rule template is as follows:

[0081] Rule Name:

[0082] condition:

[0083] Weight:

[0084] Approver:

[0085] The user needs to fill in the blanks in the above initial rule template with corresponding content. The content filled in is the configuration information, so as to obtain the final rule template, for example:

[0086] Rule name: High-value contracts

[0087] Condition: Contract amount > 100,000

[0088] Weight: 50

[0089] Approver: A

[0090] Among them, High Amount Contract, Contract Amount>100000, 50, A are configuration information filled in by the user, Contract Amount>100000 is the trigger condition, and 50 is the weight. In actual applications, the rule name can be set in advance, and the approver can be automatically generated according to the weight, so the configuration information filled in by the user may only include the trigger condition and the weight corresponding to the trigger condition.

[0091] Therefore, according to the above initial rule template, the user can customize and fill in multiple configuration information, thereby obtaining multiple final rule templates to enrich and improve the rule engine model.

[0092] After converting the final rule template into the final rule template of the Drools statement, a rule engine model is obtained. The rule engine model adopts the Drools engine. Converting the final rule template into the Drools statement is to facilitate calling and executing the rule engine model.

[0093] Based on the retrieved rule engine model, the rule engine model is used to determine whether the risk field in the to-be-verified list meets the trigger conditions. If the risk field meets the trigger conditions, the risk field that meets the trigger conditions is output to form a target list; otherwise, when the risk field does not meet the trigger conditions, the risk field that does not meet the trigger conditions is deleted.

[0094] From the judgment process of the rule engine model, we can know that the risk field is used to compare with the trigger condition. Therefore, in actual application, the risk field can be determined from the key fields according to the trigger condition defined by the user in advance. Specifically:

[0095] When the trigger condition is the preset contract amount, the total contract amount in the key field is determined as the risk field, and then the total contract amount is compared with the preset contract amount; or

[0096] When the trigger condition is a preset deadline, determine the specified deadline in the key field as a risk field, and then compare the specified deadline with the preset deadline; or

[0097] When the trigger conditions are the preset contract amount and the preset term, the total contract amount and the specified term in the key fields are determined to be risk fields, and then the total contract amount is compared with the preset contract amount, and the specified term is compared with the preset term.

[0098] Of course, a deep learning-based network model can also be used to extract risk fields from key fields.

[0099] It should be noted that after traversing the risk fields in the to-be-verified list using the above rule engine model, a target list is generated and the process proceeds to step S3.

[0100] Step S3: Calculate the sum of the weights corresponding to the risk fields in the target list to obtain a risk score.

[0101] Since the trigger condition has a corresponding weight, when the risk field meets the trigger condition, the weight corresponding to the trigger condition indirectly corresponds to the risk field. Therefore, after obtaining the target list, the sum of the weights corresponding to the risk fields in the target list is calculated, and the sum is used as the risk score of the contract form.

[0102] Step S4: Match the corresponding risk level according to the risk score.

[0103] The risk level includes at least a low risk level, a medium risk level and a high risk level, and different risk levels correspond to different risk scores. Specifically, the low risk level, the medium risk level and the high risk level each correspond to a score range, and the score ranges corresponding to different risk levels do not overlap. At the same time, the maximum value of the score range corresponding to the low risk level is less than the minimum value of the score range corresponding to the medium risk level, and the maximum value of the score range corresponding to the medium risk level is less than the minimum value of the score range corresponding to the high risk level. Specifically, according to the score range into which the risk score falls, the risk level corresponding to the score range is the risk level of the contract form.

[0104] Step S5: Select a corresponding approval process template from the approval process template library according to the risk level, and send the contract form to the terminal of the approver involved in the approval process template.

[0105] First, establish an approval process template library. The approval process template library stores multiple approval process templates. In a specific example, the approval process template library stores a first approval process template, a second approval process template, and a third approval process template. The first approval process template corresponds to a low risk level, the second approval process template corresponds to a medium risk level, and the third approval process template corresponds to a high risk level.

[0106] The first approval process template is:

[0107] {

[0108] "templateId":"LowRiskFlow",

[0109] "nodes":[

[0110] {"id":"1","role":"Submitter","label":"Contract Submitter"},

[0111] {"id":"2","role":"TeamLeader","label":"Approval by Team Leader"}

[0112] ],

[0113] "edges":[

[0114] {"from":"1","to":"2"} ]

[0116] }

[0117] Among them, LowRiskFlow indicates that the type of the approval process template is the first approval process template, which is also called the low-risk contract approval process template. The terminal ID of the submitter of the first approval process template is 1. After the submitter submits the contract form, the contract is transmitted to the terminal device of the team leader with terminal ID 2 for approval by the team leader.

[0118] The second approval process template is:

[0119] {

[0120] "templateId":"MediumRiskFlow",

[0121] "nodes":[

[0122] {"id":"1","role":"Submitter","label":"Contract Submitter"},

[0123] {"id":"2","role":"TeamLeader","label":"Team Leader Approval"},

[0124] {"id":"3","role":"LegalManager","label":"Legal Manager Approval"}

[0125] ],

[0126] "edges":[

[0127] {"from":"1","to":"2"},

[0128] {"from":"2","to":"3"} ]

[0130] }

[0131] Among them, MediumRiskFlow indicates that the type of the approval process template is the second approval process template, which is also called the medium-risk contract approval process template. The terminal ID of the submitter of the second approval process template is 1. After the submitter submits the contract form, the contract is transmitted to the terminal device of the team leader with terminal ID 2 for approval. After the team leader's approval, the contract is transmitted to the terminal device of the legal manager with terminal ID 3 for approval.

[0132] The third approval process template is:

[0133] {

[0134] "templateId":"HighRiskFlow",

[0135] "nodes":[

[0136] {"id":"1","role":"Submitter","label":"Contract Submitter"},

[0137] {"id":"2","role":"TeamLeader","label":"Team Leader Approval"},

[0138] {"id":"3","role":"LegalManager","label":"Legal Manager Approval"},

[0139] {"id":"4","role":"FinanceDirector","label":"Financial Director Approval"},

[0140] {"id":"5","role":"CEO","label":"President Approval"}

[0141] ],

[0142] "edges":[

[0143] {"from":"1","to":"2"},

[0144] {"from":"2","to":"3"},

[0145] {"from":"3","to":"4"},

[0146] {"from":"4","to":"5"} ]

[0148] }

[0149] Among them, HighRiskFlow indicates that the type of the approval process template is the third approval process template, which is also called the high-risk contract approval process template. The terminal ID of the submitter of the third approval process template is 1. After the submitter submits the contract form, the contract is transmitted to the terminal device of the team leader with terminal ID 2 for approval by the team leader. After the team leader completes the approval, the contract is transmitted to the terminal device of the legal manager with terminal ID 3 for approval by the legal manager. After the legal manager completes the approval, the contract is transmitted to the terminal device of the financial director with terminal ID 4 for approval by the financial director. After the financial director completes the approval, the contract is transmitted to the terminal device of the president with terminal ID 5 for approval by the president.

[0150] Therefore, after obtaining the risk level of the contract form, the corresponding approval process template is selected from the approval process template library according to the risk level, and the contract form is sent to the terminals of the approvers involved in the approval process template in sequence to execute the approval process of the contract form.

[0151] In addition, after the approval process is completed, a detailed risk assessment report is generated based on the risk level and approval process of the contract form, including risk scores, trigger conditions, approvers involved in the approval process, and approval time. Furthermore, the risk assessment report is visually displayed on a display, and dashboard charts, bar charts, etc. are used to display the risk score of the contract form and the risk level corresponding to the risk score. The risk fields that meet the trigger conditions and the sum of the weights corresponding to the risk fields are displayed in a list form, and a flowchart is used to display the approval process of the contract form to ensure that users can intuitively and quickly understand the entire process of contract management. Furthermore, this application supports exporting risk assessment reports to PDF or Excel format for easy archiving and sharing.

[0152] Specifically, examples of risk assessment reports are:

[0153] {

[0154] "contractId":"C12345",

[0155] "totalRiskScore":80,

[0156] "riskLevel":"Medium",

[0157] "triggeredRules":[

[0158] {

[0159] "ruleName":"HighAmountRule",

[0160] "description":"The contract amount exceeds 100000",

[0161] "weight":50

[0162] },

[0163] {

[0164] "ruleName":"LatePaymentRule",

[0165] "description":"The payment period exceeds 30 days",

[0166] "weight":30

[0167] }

[0168] ],

[0169] "approvalFlow":[

[0170] {"role":"Submitter","action":"Contract Submission"},

[0171] {"role":"TeamLeader","action":"Team leader approval"},

[0172] {"role":"LegalManager","action":"Legal Manager Approval"}

[0173] ],

[0174] "recommendations":[

[0175] "Reduce the total contract amount to less than 100,000.",

[0176] "Shorten the prescribed period to within 30 days." ]

[0178] }

[0179] Among them, "contractId":"C12345" refers to the risk assessment report generated for the contract with contract number C12345. The risk score in the risk assessment report is 80 points, and the corresponding risk level is medium risk level. Moreover, the total contract amount and the specified period in the contract meet their respective trigger conditions. The corresponding approval process is: after the submitter submits the contract form, the contract is transmitted to the terminal device of the team leader, who will review and approve it. After the team leader's review and approval, the contract is transmitted to the terminal device of the legal manager, who will review and approve it. Two suggestions were also generated for the risk assessment report, including reducing the total contract amount to less than 100,000 and shortening the specified period to within 30 days.

[0180] It should be noted that by managing the contract form through the method of steps S1 to S5 above, the automation of the approval process and the engine rule model are combined. Through the systematic and automated approval process design, the errors and workload of manual operations are significantly reduced, while the efficiency and accuracy of contract approval are improved.

[0181] In summary, the implementation principle of a contract risk dynamic scoring method of the present application is as follows: first, extract the key fields in the contract form, extract the risk fields from the key fields, and use the rule engine model to determine whether the risk fields meet the trigger conditions. The risk fields that meet the trigger conditions are output as a target list and the sum of the weights corresponding to the risk fields in the target list is calculated to obtain the risk score. Then, the corresponding risk level is matched according to the risk score, and then the corresponding approval process template is matched according to the risk level. The contract form is sent to the terminal of the approver involved in the approval process template to execute the approval process. Finally, a risk assessment report is generated based on the risk score and the approval process of the contract form, so that the user can intuitively view the entire contract management process. It can be seen that the present application supports user-defined configuration of the rule engine model, and the user can also customize the risk level and the approval process template corresponding to the risk level. When the risk field meets the trigger condition, the risk score is calculated and different approval process templates are obtained according to the risk score matching. Different approval process templates correspond to different approval processes and approvers, so that the present application does not require manual intervention, and improves the automation and flexibility of the contract approval process.

[0182] like Figure 2 As shown, the present application also provides a multi-level approval device, which includes a risk assessment module 1, an approval process module 2 and an approval execution module 3.

[0183] The risk assessment module 1 is used to match the corresponding risk level according to the risk score of the contract form.

[0184] Approval process module 2 is used to select a corresponding approval process template from the approval process template library according to the risk level.

[0185] The approval execution module 3 is used to send the contract form to the terminal of the approver involved in the approval process template.

[0186] According to the differences in the functions implemented by the above modules, different modules may be further subdivided into different sub-modules. For example, the risk assessment module 1 can also be divided into a configuration sub-module, a first extraction sub-module, a second extraction sub-module, a data calculation sub-module and a data matching sub-module, wherein: the configuration sub-module is used for users to fill in configuration information and dynamically generate a rule engine model based on the configuration information, the first extraction sub-module is used to extract the risk fields in the contract form to form a to-be-verified list, the second extraction sub-module is used to extract the risk fields in the to-be-verified list that meet the trigger conditions to form a target list, the data calculation sub-module is used to calculate the sum of the weights corresponding to the risk fields in the target list to obtain a risk score, and the data matching sub-module is used to match the corresponding risk level according to the risk score.

[0187] At the same time, in order to facilitate users to fill in configuration information, the configuration submodule has a configuration interface, which allows users to configure trigger conditions and weights corresponding to the trigger conditions through a graphical interface to achieve the purpose of dynamically generating a rule engine model.

[0188] In addition, the multi-level approval device also includes a data display module 4, and the data display module 4, such as a display, can display the risk assessment report.

[0189] The modules involved in the embodiments described in the present application may be implemented by software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes a risk assessment module 1, an approval process module 2, an approval execution module 3 and a data display module 4. The names of these modules do not constitute a limitation on the modules themselves in some cases. For example, the risk assessment module 1 may also be described as a "module for matching the corresponding risk level according to the risk score of the contract form".

[0190] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the described module can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0191] In order to better execute the program of the above method, the present application also provides a contract risk dynamic scoring device, which includes a memory and a processor.

[0192] The memory may be used to store instructions, programs, codes, code sets or instruction sets. The memory may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function, and instructions for implementing the above-mentioned contract risk dynamic scoring method, etc.; the data storage area may store data involved in the above-mentioned contract risk dynamic scoring method, etc.

[0193] The processor may include one or more processing cores. The processor calls the data stored in the memory by running or executing the instructions, programs, code sets or instruction sets stored in the memory, performs various functions of the present application and processes data. The processor may be at least one of a special purpose integrated circuit, a digital signal processor, a digital signal processing device, a programmable logic device, a field programmable gate array, a central processing unit, a controller, a microcontroller and a microprocessor. It is understandable that for different devices, the electronic device used to implement the above-mentioned processor function can also be other, and the embodiments of the present application are not specifically limited.

[0194] The present application also provides a computer-readable storage medium, for example, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes. The computer-readable storage medium stores a computer program that can be loaded by a processor and execute the above-mentioned contract risk dynamic scoring method.

[0195] The above is only a preferred embodiment of the present application and does not constitute any form of limitation to the present application. Although the present application has been disclosed as above with a preferred embodiment, it is not used to limit the present application. Any technician familiar with this patent can make some changes or modifications to equivalent embodiments of equivalent changes using the technical content suggested above without departing from the scope of the technical solution of the present application. The implementation scheme in the above embodiment can also be further combined or replaced. However, any simple modification, equivalent change and modification made to the above embodiment based on the technical essence of the present application without departing from the content of the technical solution of the present application are still within the scope of the solution of the present application.

Claims

1. A contract risk dynamic scoring method, characterized in that: include: Extract risk fields in the contract form to form a to-be-verified list, wherein the risk fields are fields in the contract form that require risk control; Extracting the risk fields that meet the trigger conditions in the to-be-verified list to form a target list, including: using a rule engine model to determine whether the risk fields in the to-be-verified list meet the trigger conditions; if so, outputting the risk fields that meet the trigger conditions to form a target list; if not, deleting the risk fields that do not meet the trigger conditions, wherein the trigger conditions have corresponding weights; the method for establishing a rule engine model includes: filling configuration information into an initial rule template to obtain a final rule template, wherein the configuration information at least includes a trigger condition and a weight corresponding to the trigger condition; converting the final rule template into a final rule template of a Drools statement; and forming a rule engine model from at least one final rule template of a Drools statement; Calculating the sum of the weights corresponding to the risk fields in the target list to obtain a risk score; The corresponding risk level is matched according to the risk score.

2. The contract risk dynamic scoring method according to claim 1 is characterized in that: The risk fields in the contract form are extracted to form a to-be-verified list, including: Extracting key fields from the contract form; Determining a field in the key field that is used for comparison with the trigger condition as a risk field; The to-be-verified list is composed of at least one of the risk fields.

3. The contract risk dynamic scoring method according to claim 2 is characterized in that: The key fields include at least the contract number, the total contract amount and the specified period; The determining that a field in the key field that is used for comparison with the trigger condition is a risk field includes: When the trigger condition is a preset contract amount, the total contract amount in the key field is determined as a risk field, and the total contract amount is used for comparison with the preset contract amount; or When the trigger condition is a preset deadline, determining the specified deadline in the key field as a risk field, and the specified deadline is used for comparison with the preset deadline; or When the trigger conditions are a preset contract amount and a preset term, the total contract amount and the specified term in the key fields are determined to be risk fields, the total contract amount is used to compare with the preset contract amount, and the specified term is used to compare with the preset term.

4. The contract risk dynamic scoring method according to claim 1 is characterized in that: The risk levels include at least a low risk level, a medium risk level and a high risk level, and different risk levels correspond to different risk scores.

5. A multi-level approval device, used to execute the contract risk dynamic scoring method as described in any one of claims 1 to 4, characterized in that: include: A risk assessment module (1), used to match the corresponding risk level according to the risk score of the contract form; An approval process module (2), used to select a corresponding approval process template from an approval process template library according to the risk level; The approval execution module (3) is used to send the contract form to the terminal of the approver involved in the approval process template.

6. The multi-level approval device according to claim 5, characterized in that: The approval process template library includes a first approval process template, a second approval process template and a third approval process template. The first approval process template corresponds to a low risk level, the second approval process template corresponds to a medium risk level, and the third approval process template corresponds to a high risk level.

7. The multi-level approval device according to claim 6, characterized in that: The number of approval personnel involved in the first approval process template < the number of approval personnel involved in the second approval process template < the number of approval personnel involved in the third approval process template.

8. The multi-level approval device according to claim 5, characterized in that: It also includes a data display module (4), which is used to display a risk assessment report, and the risk assessment report includes the risk score and approval process of the contract form.

Images