Financial examination and approval method, device, equipment and medium

Abstract

The invention provides a financial examination and approval method, device and equipment and a medium, relates to the field of information security, and can be used in the financial field. The method comprises the following steps: in response to a received current financial examination and approval application, extracting information of a current financial submitter and a to-be-examined and approved task from the current financial examination and approval application; obtaining values of a plurality of indexes used for evaluating the business level of the current financial submitter, wherein the values of at least part of the indexes in the plurality of indexes are updated along with time or along with behaviors of the current financial submitter; processing the values of the plurality of indexes of the current financial submitter to obtain a target business level vector corresponding to the current financial submitter; calculating the similarity between the target service level vector and the reference service level vector; and determining an approval mode of the current financial approval application based on the similarity, when the similarity exceeds a similarity threshold, approving the to-be-approved task in an automatic approval mode, otherwise, approving the to-be-approved task in a manual approval mode.

Description

Technical Field

[0001] The present disclosure relates to the field of information security and can be used in the financial field, and more specifically to a financial approval method, device, equipment, medium and program product. Background Art

[0002] Financial approval is a frequently occurring business in enterprises, and a large part of the payments are daily, small and unimportant payment items. For such payment items, if the financial submitters are delegated power and the approval is fast and automatic, the payment efficiency of the daily business of the enterprise can be greatly improved. However, in the automatic approval, it is necessary to guard against the security of the use of funds and avoid the abuse of the automatic approval mechanism. For this reason, in the prior art, some screening conditions are usually set for the financial submitters in the automatic approval, for example, the identity, qualifications, total amount within a period of time (such as daily or monthly), and the maximum amount of a single time of the financial submitter are limited. The financial approval application that matches the conditions is automatically approved, and those that do not match are manually approved.

[0003] In the process of implementing this solution, the inventor found that there are at least the following problems in the prior art: in the prior art, once the automatic approval authority is authorized to a certain financial submitter, the scope of the automatic approval authority of the financial submitter (such as the amount range, business scope, etc.) is fixed, and unless it is reset next time, it will not change with the behavior of the financial submitter, the actual performance in the business, etc. In this way, if the financial submitter performs poorly (such as making mistakes, or there is suspicion of fictitious small transactions, etc.), the authorization scope of automatic approval will not be limited, and it will not have a suppressive effect on the poor performance of the financial submitter; similarly, when the financial submitter performs well (such as reducing or zero errors, taking on more tasks), the authorization scope of automatic approval will not be increased accordingly, and it will not be able to generate incentives for the good performance of the financial submitter, thereby improving the automatic approval efficiency of the enterprise. It can be seen that the existing financial automatic approval mechanism is relatively rigid, and cannot be automatically adjusted adaptively with the business performance of the financial submitter, and is not smart enough. Summary of the invention

[0004] In view of the above problems, the present disclosure provides a financial approval method, apparatus, device, medium and program product that can perform adaptive authorization according to the current business level of the financial submitter in automatic financial approval authorization.

[0005] The first aspect of the disclosed embodiment provides a financial approval method. The method includes: in response to receiving a current financial approval application, extracting information of the current financial submitter and the task to be approved from the current financial approval application; obtaining values ​​of multiple indicators used to evaluate the business level of the current financial submitter, and the values ​​of at least some of the multiple indicators are updated over time or with the behavior of the financial submitter; processing the values ​​of the multiple indicators of the current financial submitter to obtain a target business level vector corresponding to the current financial submitter; obtaining a reference business level vector corresponding to the task to be approved; calculating the similarity between the target business level vector and the reference business level vector; and determining the approval method of the current financial approval application based on the similarity, including: when the similarity exceeds a similarity threshold, approving the task to be approved in an automatic approval manner; otherwise, approving the task to be approved in a manual approval manner.

[0006] According to an embodiment of the present disclosure, the multiple indicators include at least one of the following categories: behavioral indicators or business background indicators. The behavioral indicators are statistical indicators of the financial submitter's behavior in submitting financial approvals. The business background indicators are the financial submitter's educational background indicators and / or years of experience indicators.

[0007] According to an embodiment of the present disclosure, after determining the approval mode of the current financial approval application based on the similarity, the method further includes: updating the value of the behavior indicator of the current financial submitter.

[0008] According to an embodiment of the present disclosure, the behavioral indicators include at least one of the following: the number of authorized automatic approvals in history, the number of rejected automatic approvals in history, the number of times or the ratio of approved approval results in automatic approvals in history, the number of times or the ratio of rejected approval results in automatic approvals in history, the number of times or the ratio of approved approval results in manual approvals in history, the number of times or the ratio of rejected approval results in manual approvals in history, the number of times financial approvals are submitted on the day, and the total number of financial approval applications submitted in history.

[0009] According to an embodiment of the present disclosure, obtaining the benchmark business level vector corresponding to the pending approval task includes: determining the business scenario and target approval amount to which the pending approval business belongs based on the information of the pending approval task; wherein different pre-approval condition vectors are set for different levels of pre-approval amount ranges in the business scenario; determining the level of the pre-approval amount range to which the target approval amount belongs to obtain the target level; and selecting the pre-approval condition vector corresponding to the target level to obtain the benchmark business level vector.

[0010] According to an embodiment of the present disclosure, the method further includes pre-setting different pre-approval condition vectors for pre-approval amount ranges of different levels in the business scenario, specifically including: setting an initial pre-approval condition vector for the pre-approval amount range of each level in the business scenario; dynamically updating the pre-approval condition vector according to the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario. Wherein, dynamically updating the pre-approval condition vector according to the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario specifically includes: accumulating the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario to obtain a first measurement data set; when the data volume of the first measurement data set exceeds the first data volume threshold, counting the distribution ratio between the manual approval method and the automatic approval method for all historical approval tasks falling within the pre-approval amount range of each level in the business scenario; and when the distribution ratio meets the first approval item adjustment condition, updating the pre-approval condition vector.

[0011] According to an embodiment of the present disclosure, the dynamic updating of the pre-approval condition vector based on the approval results of the historical approval tasks falling within the pre-approval amount range of each level in the business scenario also includes: for a second historical approval task approved by manual approval, obtaining feedback suggestions from the approver on whether the second historical approval task is more suitable for the automatic approval method; accumulating the obtained feedback suggestions to obtain a second measurement data set; when the data volume of the second measurement data set exceeds a second data volume threshold, determining the proportion of automatic approval tendencies that are more suitable for the automatic approval method among all second historical approval tasks approved by the manual approval method based on the feedback suggestions in the second measurement data set; and updating the pre-approval condition vector when the automatic approval tendency proportion meets the second approval adjustment condition.

[0012] According to an embodiment of the present disclosure, the automatic approval of the pending task includes: identifying the current financial submitter; and approving the pending task if the identity is identified; otherwise, determining that the pending task is not approved.

[0013] According to an embodiment of the present disclosure, the automatic approval method for approving the pending approval task includes: collecting information about the current submission environment of the current financial approval application; comparing the information about the current submission environment with the environmental requirements set for the pending approval task to obtain a comparison result; and if the comparison result indicates that the current submission environment meets the environmental requirements set for the pending approval task, approving the pending approval task; otherwise, determining that the pending approval task has failed.

[0014] According to a second aspect of the disclosed embodiment, a financial approval device is provided. The financial approval device includes: an information extraction module, a first acquisition module, a second acquisition module, a similarity calculation module and an approval module. The information extraction module is used to extract information about the current financial submitter and the task to be approved from the current financial approval application in response to receiving the current financial approval application. The first acquisition module is used to obtain the values ​​of multiple indicators used to evaluate the business level of the current financial submitter, the values ​​of at least some of the multiple indicators are updated over time or with the behavior of the financial submitter, and the values ​​of the multiple indicators of the current financial submitter are processed to obtain the target business level vector corresponding to the current financial submitter. The second acquisition module is used to obtain the benchmark business level vector corresponding to the task to be approved. The similarity calculation module is used to calculate the similarity between the target business level vector and the benchmark business level vector. The approval module is used to determine the approval method of the current financial approval application based on the similarity, including: when the similarity exceeds the similarity threshold, the task to be approved is approved in an automatic approval manner; otherwise, the task to be approved is approved in a manual approval manner.

[0015] According to an embodiment of the present disclosure, the second acquisition module is specifically used to: determine the business scenario and target approval amount to which the pending approval business belongs based on the information of the pending approval task; wherein different pre-approval condition vectors are set for different levels of pre-approval amount ranges in the business scenario; determine the level of the pre-approval amount range to which the target approval amount belongs to obtain the target level; and select the pre-approval condition vector corresponding to the target level to obtain the benchmark business level vector.

[0016] According to an embodiment of the present disclosure, the financial approval device further includes a pre-approval condition deployment module. The pre-approval condition deployment module is further used to: pre-set different pre-approval condition vectors for pre-approval amount ranges of different levels in the business scenario, wherein an initial pre-approval condition vector is set for the pre-approval amount range of each level in the business scenario, and the pre-approval condition vector is dynamically updated according to the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario. Wherein, the dynamic updating of the pre-approval condition vector according to the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario specifically includes: accumulating the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario to obtain a first measurement data set; when the data volume of the first measurement data set exceeds the first data volume threshold, counting the distribution ratio between the manual approval mode and the automatic approval mode for all historical approval tasks falling within the pre-approval amount range of each level in the business scenario; and when the distribution ratio meets the first approval item adjustment condition, updating the pre-approval condition vector.

[0017] In a third aspect of the embodiments of the present disclosure, an electronic device is provided. The electronic device includes one or more processors and a memory. The memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned financial approval method.

[0018] According to a fourth aspect of the embodiments of the present disclosure, there is also provided a computer-readable storage medium on which executable instructions are stored. When the instructions are executed by a processor, the processor executes the above-mentioned financial approval method.

[0019] According to a fifth aspect of the disclosed embodiments, a computer program product is provided, including a computer program, which implements the above-mentioned financial approval method when executed by a processor. One or more of the above-mentioned embodiments have the following advantages or beneficial effects: at each financial approval, the corresponding business level vector can be obtained according to the latest values ​​of multiple indicators used to evaluate the current business level of the financial submitter, and then the similarity between the business level vector of the financial submitter and the benchmark business level vector can be used to judge whether the current business level of the financial submitter reaches the benchmark business level required for automatic authorization in the current financial approval. If it reaches the benchmark business level, the automatic approval authority is granted, otherwise the manual approval process is followed. In this way, the automatic authorization situation of each financial approval can be adapted to the current business level of the financial submitter, making the automatic approval authorization mechanism in financial approval more intelligent. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0021] Figure 1 The application scenario diagram of the financial approval method, apparatus, device, medium and program product according to the embodiment of the present disclosure is schematically shown;

[0022] Figure 2 A flowchart of a financial approval method according to an embodiment of the present disclosure is schematically shown;

[0023] Figure 3 A flowchart for obtaining a benchmark business level vector corresponding to a task to be approved in one embodiment of the present disclosure is schematically shown;

[0024] Figure 4 A flowchart schematically shows a flow chart of dynamically updating a preset pre-approval condition vector for a pre-approval amount range of each level in each business scenario in another embodiment of the present disclosure;

[0025] Figure 5 A flowchart schematically shows a method of dynamically updating a preset pre-approval condition vector for a pre-approval amount range at each level in each business scenario in yet another embodiment of the present disclosure;

[0026] Figure 6 A flowchart schematically shows an embodiment of the present disclosure in which an enterprise negotiates with a bank to implement a financial approval method of the present disclosure embodiment on the bank side;

[0027] Figure 7 A flowchart schematically shows another embodiment of the present disclosure, in which automatic approval is performed on the bank side according to the major categories of business scenarios;

[0028] Figure 8 A flowchart schematically shows an automatic approval process based on the business level of the financial submitter on the bank side in another embodiment of the present disclosure;

[0029] Fig. 9 A schematic diagram of a structure of a financial approval device according to an embodiment of the present disclosure is shown; and

[0030] Fig.10 A block diagram of an electronic device suitable for implementing the financial approval method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0032] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0033] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0034] When using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). The terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more features.

[0035] The disclosed embodiments provide a financial approval method, apparatus, device, medium and program product. According to the disclosed embodiments, at each financial approval, a corresponding business level vector can be obtained according to the values ​​of multiple indicators used to evaluate the current business level of the financial submitter, and then the similarity between the business level vector and the benchmark business level vector corresponding to the business applied for approval is used to measure whether the current business level of the financial submitter meets the business level requirements for automatic approval of the applied task, and accordingly decide whether to give the financial submitter the authority for automatic approval at each financial approval.

[0036] In this way, the automatic authorization of each financial approval can be adapted to the current business level of the financial submitter. For example, when the business level of the financial submitter drops significantly, the business that could be automatically approved before may be rejected for automatic approval because the similarity between the business level vector of the financial submitter and the benchmark business vector corresponding to the applied task is lower than the similarity threshold. Correspondingly, when the business level of the financial submitter increases significantly, the business that was not allowed to be automatically approved before may be allowed for automatic approval because the similarity between the business level vector of the financial submitter and the benchmark business vector corresponding to the applied task exceeds the similarity threshold. This avoids the situation in the prior art that once a certain automatic approval authority is granted to a certain financial submitter, the scope of the authority is fixed unless otherwise modified, regardless of the actual performance of the financial submitter.

[0037] In the embodiment of the present disclosure, the business level vector is obtained by processing the values ​​of multiple indicators used to evaluate the business level of the current financial submitter. Among the multiple indicators, the values ​​of at least some indicators can be continuously updated, for example, continuously updated with the financial submitter's years of employment, current business, or financial submission behavior. In this way, the business level vector of each financial submitter can be continuously updated.

[0038] For example, as the business level of financial submitters continues to improve, their business level vectors can also change synchronously, so that the financial submitters can be continuously granted automatic approval permissions at higher business levels. For example, after a financial submitter changes, the new financial submitter can be automatically granted permissions that are appropriate to his or her initial business level. As he or she becomes more proficient in financial business and his or her business level continues to improve, he or she can be automatically granted higher automatic approval permissions.

[0039] For example, when a financial submitter makes mistakes or behaves abnormally in financial submission, reflecting a decline in his or her professional level or suspicion of cheating, this information can also be recorded in the corresponding indicators and then reflected in the professional level vector. This can reduce or limit the automatic approval authority of the financial submitter, impose corresponding penalties on the financial submitter, and promptly suppress the abnormal behavior of the financial submitter, thus forming a supervision mechanism for the automatic approval process.

[0040] It can be seen that by reflecting the business level of the financial submitter through the business level vector and granting the financial submitter the automatic approval authority corresponding to his or her business level, on the one hand, the authority granted to the financial submitter can be automatically and gradually adjusted according to the changes in the business level of the financial submitter, and on the other hand, the abnormal behavior of the financial submitter can be supervised and punished and restricted in time, avoiding the rigid approach of either granting authority or directly revoking authority in related technologies, so that the process of automatic financial approval can be synchronized with the business level of the financial submitter and is more flexible.

[0041] Figure 1 The application scenario diagram of the financial approval method, apparatus, device, medium and program product according to the embodiments of the present disclosure is schematically shown.

[0042] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a financial submitter client 101, a financial supervisor client 102, a financial approval system 103, and a network 104. The network 104 is used to provide a communication link between the financial submitter client 101, the financial supervisor client 102, and the financial approval system 103. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0043] The financial submitter may submit a financial approval request through the financial submitter client 101 .

[0044] The financial supervisor can maintain corresponding pre-approval conditions that can be automatically approved for pre-approval amount ranges of different levels in various business scenarios through the financial supervisor client 102. For example, multiple indicators for evaluating the business level of the financial submitter are selected and set, a processing method for processing the multiple indicators into a business level vector is specified or selected, and a benchmark value of each indicator is set for each level of pre-approval amount range, and then uploaded to the financial approval system 103, so that a pre-approval condition vector (or a benchmark business level vector) corresponding to each level of pre-approval amount range can be formed in the financial approval system 103.

[0045] The financial approval system 103 can execute the financial approval method of the embodiment of the present disclosure, process the financial approval application sent by the financial submitter client 101, and determine whether to go through the automatic approval process or the manual approval process. In the manual approval process, the financial approval system 103 can send the financial approval application to the financial supervisor client 102 for manual review. Accordingly, the financial approval device, equipment, medium and program product of the embodiment of the present disclosure can also be set in the financial approval system 103.

[0046] In some embodiments, the financial approval system 103 may be a financial management system set up on the enterprise side. Therefore, the information of the approved tasks (such as the amount and account information) needs to be sent to the bank in the form of a payment request, and the bank will perform the final payment processing. In other embodiments, the financial approval system 103 may also be set up on the bank side, and the bank will supervise after the enterprise and the bank reach an agreement, so that the approved tasks can be directly paid by the bank backend.

[0047] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0048] The following will be based on Figure 1 The application scenario described by Figure 2 to Figure 8 The financial approval method of the embodiment of the present disclosure is described in detail.

[0049] Figure 2 The flowchart of the financial approval method according to the embodiment of the present disclosure is schematically shown.

[0050] like Figure 2 As shown, the financial approval method according to this embodiment may include operations S210 to S270.

[0051] In operation S210 , in response to receiving the current financial approval application, information of the current financial submitter and the tasks to be approved is extracted from the current financial approval application.

[0052] In operation S220, the values ​​of multiple indicators for evaluating the business level of the current financial submitter are obtained, and the values ​​of the multiple indicators of the current financial submitter are processed to obtain a target business level vector corresponding to the current financial submitter. The values ​​of at least some of the multiple indicators are updated over time or with the behavior of the financial submitter. In this article, the "target business level vector" is only used for naming distinction and refers to the business level vector of the "current financial submitter".

[0053] The values ​​of at least some of the multiple indicators can be continuously updated, for example, continuously updated over time or with the financial submission behavior of the financial submitter, so that the business level vector of the same financial submitter in the financial approval application of the same financial submitter can be different at different times or stages.

[0054] In one embodiment, the plurality of indicators may include but are not limited to the following categories of indicators: behavioral indicators and business context indicators.

[0055] The behavior indicator is a statistical indicator of the behavior of the financial submitter submitting financial approval, and can be continuously updated with the financial submission behavior of the financial submitter. Among them, the behavior indicator may include but is not limited to: the number of authorized automatic approvals in history, the number of rejected automatic approvals in history, the number of approval results or ratios of approvals in automatic approvals in history, the number of approval results or ratios of approvals in manual approvals in history, the number of approval results or ratios of approvals in manual approvals in history, the number of financial approvals submitted on the day, and the total number of financial approval applications submitted in history.

[0056] Business background indicators are indicators of the financial submitter's experience or educational background in the business related to the business to be approved. Among them, business background indicators may include but are not limited to: years of work experience, business proficiency, job level, importance of the business in charge, educational background, qualifications, etc. By comparison, it can be seen that the values ​​of business background indicators are either not updated, such as educational background and other information may not change after the financial submitter starts working, or the update frequency is significantly lower than that of behavioral indicators. For example, business background indicators can be updated regularly (such as half a year) or in response to a predetermined trigger event (such as a change in position information).

[0057] In the disclosed embodiments, the business level vector is obtained by processing the values ​​of multiple indicators. Specifically, in some embodiments, the corresponding conversion relationship between the value and the numerical value can be defined for each indicator in the multiple indicators (for example, different academic qualifications in the educational background are mapped to different numerical values, and different behavioral indicator statistics can be mapped to different numerical values), and then the numerical values ​​converted from the values ​​of the multiple indicators are arranged in a preset dimensional order to form a vector; in other embodiments, the numerical values ​​converted from the values ​​of the multiple indicators can also be processed according to a specific processing method, and then arranged according to a preset dimension to form a vector. Among them, the specific method may include but is not limited to: compression and dimensionality reduction, standardization processing, etc. For example, when multiple indicators can be divided into two categories: behavioral indicators and business background indicators, the values ​​of each category of indicators can be weighted and then uniformly output as a value, so as to achieve dimensional compression.

[0058] In operation S230, a reference business level vector corresponding to the task to be approved is obtained. The reference business level vector is used to measure the business level required for automatic approval of the task to be approved.

[0059] In operation S240, the similarity between the target service level vector and the reference service level vector is calculated. The similarity can be represented by cosine similarity between vectors, or can be represented by parameters such as distance between vectors, which is not limited in the present disclosure.

[0060] Then, in operation S250, it is determined whether the similarity exceeds a similarity threshold, and an approval method for the current financial approval application is selected according to the determination result.

[0061] When the similarity exceeds the similarity threshold, in operation S260, the pending task is approved by automatic approval; otherwise, in operation S270, the pending task is approved by manual approval, that is, the financial approval application is submitted to the manual approval process.

[0062] The business level of the financial submitter can often be analyzed by combining multiple factors that reflect the business proficiency. People with similar or equivalent business levels may have different values ​​on the same indicator, but the values ​​of different indicators may fluctuate up and down, and the gaps offset each other, thereby reflecting that the business level is basically equivalent. For this reason, the embodiment of the present disclosure uses a benchmark business level vector to screen financial submitters who have reached the benchmark business level by similarity. The basic idea is that the financial submitters whose business level vectors are within the similarity threshold range of the benchmark business level vector all reach the benchmark business level. This way of evaluating and screening the business level is more practical. After all, two people with equivalent business levels are often unlikely to be consistent in all indicators or exceed a certain benchmark. Compared with the scheme in the related art that sets multi-dimensional conditions and then grants automatic approval authority only when the conditions of each dimension are met, the embodiment of the present disclosure can be more flexible in automatic approval authorization, avoiding the situation where the one-size-fits-all hard indicator condition matching is too rigid.

[0063] According to some embodiments of the present disclosure, when the pending task is approved in the automatic approval mode in the above operation S260, the identity of the financial submitter can be identified to prevent others from impersonating the identity. For example, the identity of the current financial submitter is identified by means of biometric information recognition, and if the identity recognition is passed, the automatic approval of the pending task is continued (such as bill verification, fund payment, notification sending, information recording, etc.); otherwise, it is determined that the pending task is not approved, and the approval of the pending task is directly terminated.

[0064] According to other embodiments of the present disclosure, when the task to be approved is approved in the automatic approval mode in the above operation S260, if there are requirements for the environment in which the financial approval application is submitted, it is also possible to judge whether the environment in which the current financial approval application is submitted meets the requirements, and only the financial approval application submitted in the environment that meets the requirements is allowed to enter the automatic approval process. For example, some sensitive business requirements must be submitted using specific equipment in the office, or some business requirements must be submitted in the office environment, or some business requirements cannot be submitted in a noisy environment at least. Specifically, when automatically approving the task to be approved, the information of the current submission environment of the current financial approval application (such as equipment information, IP address, audio information, image or video information in the surrounding environment, etc.) can be collected, and then the information of the current submission environment is compared with the environmental requirements set for the task to be approved to obtain a comparison result; and if the comparison result shows that the current submission environment meets the environmental requirements set for the task to be approved, the task to be approved continues to be automatically approved, otherwise, it is determined that the approval of the task to be approved is not passed, and the current financial approval application is directly rejected.

[0065] Of course, the identity recognition or submission environment detection operations in the above-mentioned embodiments can also be performed before calculating the similarity, that is, only when there is no financial submitter impersonating the identity and / or the submission environment meets the requirements, it is judged whether the business level of the financial submitter meets the requirements of automatic approval.

[0066] According to an embodiment of the present disclosure, when the above-mentioned multiple indicators include behavioral indicators, after operation S260 or S270, the value of the behavioral indicator of the current financial submitter can also be updated according to the behavior and / or approval result of submitting the financial approval application this time. Since financial approval is a common occurrence in an enterprise, the value of the behavioral indicator of the financial submitter can be updated in time according to the financial submission behavior of the financial submitter. Thus, the business level vector of the financial submitter obtained each time a financial approval application is made can timely reflect the gradual change of the business level of the financial submitter. Moreover, for each financial approval application, the business level vector of the financial submitter based on can reflect the current business level of the financial submitter. In this way, for the same financial submitter, in different financial approval applications, as its business level is different (reflected in the business level vector) and the pending approval tasks requested for approval are different, the result of whether to perform automatic approval authorization will also be different. In this way, fine-grained review and authorization of each financial approval application is realized, and the financial security of the financial approval application is improved.

[0067] Figure 3 The flowchart of operation S230 of obtaining the reference business level vector corresponding to the task to be approved in one embodiment of the present disclosure is schematically shown.

[0068] like Figure 3 As shown, according to this embodiment, operation S230 may include operations S231 to S233.

[0069] In operation S231, the business scenario and target approval amount to which the pending approval business belongs are determined according to the information of the pending approval task. Different pre-approval condition vectors are set for pre-approval amount ranges of different levels in the business scenario.

[0070] In operation S232, the level of the pre-approval amount range to which the target approval amount belongs is determined to obtain the target level.

[0071] In operation S233, a pre-approval condition vector corresponding to the target level is selected to obtain a reference service level vector.

[0072] According to the embodiments of the present disclosure, an initial pre-approval condition vector can be set for the pre-approval amount range of each level in the business scenario. For example, the financial director fills in the benchmark values ​​of multiple indicators corresponding to the pre-approval amount range of the level he is responsible for through the financial director client 102, and uploads it to the financial approval system 103. The financial approval system 103 can process the benchmark values ​​of multiple indicators and combine the initial pre-approval condition vector. Then, the embodiments of the present disclosure can also dynamically update the pre-approval condition vector based on the approval results of historical approval tasks that fall within the pre-approval amount range of each level in the business scenario. The logic of the dynamic update can refer to Figure 4 or Figure 5 Introduction.

[0073] Figure 4 A flowchart schematically illustrates a method of dynamically updating a preset pre-approval condition vector for a pre-approval amount range at each level in each business scenario in another embodiment of the present disclosure.

[0074] like Figure 4 As shown, according to this embodiment, the process of dynamically updating the pre-approval condition vector may include operations S401 to S403.

[0075] In operation S401, approval results of historical approval tasks that fall within the pre-approval amount range of each level in the business scenario are accumulated to obtain a first measurement data set.

[0076] In operation S402, when the data volume of the first calculated data set exceeds the first data volume threshold, all historical approval tasks falling within the pre-approval amount range of each level in the business scenario are counted, and the distribution ratio between the manual approval method and the automatic approval method is calculated.

[0077] In operation S403, when the allocation ratio satisfies the first approval-document adjustment condition, the pre-approval condition vector is updated.

[0078] For example, when the allocation ratio is higher than the preset first allocation ratio threshold, it can be considered that the proportion of manual approval is too high, and the conditional restrictions of automatic approval need to be relaxed. At this time, some or all values ​​in the pre-approval condition vector can be adjusted manually or automatically according to a certain adjustment range to relax the benchmark business level required for the automatic approval process. For another example, when the allocation ratio is lower than the preset second allocation ratio threshold (where the second allocation ratio threshold is lower than the first allocation ratio threshold), it can be considered that the proportion of manual approval is too low, and the conditional restrictions of automatic approval need to be strengthened. At this time, some or all values ​​in the pre-approval condition vector can be adjusted manually or automatically according to the preset adjustment range to improve the benchmark business level required for the automatic approval process. In this way, the allocation ratio of manual approval and automatic approval methods is controlled within a reasonable range, and a relative balance is maintained between the capital payment efficiency and capital security of the enterprise.

[0079] Figure 5 A flowchart schematically illustrates a method of dynamically updating a preset pre-approval condition vector for a pre-approval amount range at each level in each business scenario in yet another embodiment of the present disclosure.

[0080] like Figure 5 As shown, according to this embodiment, the process of dynamically updating the pre-approval condition vector may include operations S501 to S504.

[0081] In operation S501, for the second historical approval task approved by manual approval, feedback suggestions from the approver on whether the second historical approval task is more suitable for automatic approval are obtained. In order to reduce the randomness of feedback suggestions, the approver can be required to provide appropriate reasons when giving feedback that the second historical approval task is more suitable for automatic approval.

[0082] In operation S502, the acquired feedback suggestions are accumulated to obtain a second measurement data set.

[0083] In operation S503, when the data volume of the second measured data set exceeds the second data volume threshold, based on the feedback suggestions in the second measured data set, the proportion of automatic approval tendencies that are more suitable for the automatic approval method among all second historical approval tasks approved in the manual approval method is determined.

[0084] In operation S504, when the automatic approval tendency ratio meets the second approval adjustment condition, the pre-approval condition vector is updated. For example, when the automatic approval tendency ratio is higher than the ratio threshold in the second approval adjustment condition, the pre-approval condition vector can be adjusted manually or automatically to relax the benchmark business level required by the automatic approval process. Thus, the financial approval process can be optimized based on the manual approval feedback of the financial supervisor or approver.

[0085] The following Figure 6 to Figure 8 The application example of the financial approval method of the embodiment of the present disclosure implemented on the bank side is introduced as an example. Figure 1 As introduced in , the financial approval system 103 can be set up on the bank side, and the enterprise grants the bank certain authority to supervise the enterprise's financial approval application.

[0086] Figure 6 The flowchart schematically shows the negotiation between an enterprise and a bank to implement the financial approval method of the embodiment of the present disclosure on the bank side in one embodiment of the present disclosure.

[0087] like Figure 6 As shown, when the enterprise negotiates with the bank to implement the financial approval method of the embodiment of the present disclosure on the bank side, the overall process may include steps S601 to S604. The implementation of the financial approval method of the embodiment of the present disclosure can be designed from the perspective of the bank to provide online financial approval for the corporate customers of the bank, specifically involving five participants, including: a corporate customer marketing system, a financial submitter client 101, a financial supervisor client 102, a bank-supervised financial approval system 103, and a bank account terminal or a third-party account terminal.

[0088] First, in step S601, the enterprise and the bank sign a regulatory approval agreement in advance. Specifically, the corporate customer marketing system opens and maintains the regulatory approval agreement according to the needs of the corporate customer. After the maintenance is completed, the corporate customer marketing system will send a corresponding message to the financial approval system supervised by the bank to register the corporate regulatory approval opening status. The corporate customer marketing system is an internal management system of the bank, which is used to maintain the agreement signed between the corporate customer and the bank.

[0089] Next, in step S602, the enterprise financial manager maintains the pre-approval conditions according to the requirements. Figure 1 , the enterprise financial director can maintain the pre-approval conditions and supervise the funds of online payments through operations in the financial director client 102. The financial director client 102 refers to the terminal where the financial director initiates the request, which can be a local program installed in a PC or mobile APP. Generally, the request is initiated in the form of a URL that meets the http protocol. The specific function is that when the enterprise opens the financial approval function supervised by the bank, the financial approval system 103 supervised by the bank will send instructions to the financial director client 102 to display the supervision approval function. The financial director can maintain the pre-approval conditions through this function, and send the information to the financial approval system 103 supervised by the bank after the maintenance is completed.

[0090] Next, in step S603, the financial submitter submits a financial approval application through the financial submitter client 101, requesting online payment operations. The financial submitter client 101 refers to the terminal from which the financial submitter initiates the request, which can be a local program installed in a PC or mobile APP. Generally, the request is initiated in the form of a URL that meets the http protocol, and various business operations such as transfer, salary payment, financial management, and online financing can be performed.

[0091] Next, in step S604, the financial approval system 103 supervised by the bank determines whether the financial approval application submitted by the financial submitter can be automatically approved or requires manual approval, and performs subsequent processing according to the judgment result. Specifically, the financial approval system 103 can execute the financial approval method of the embodiment of the present disclosure to process the financial approval application. For financial approval applications that can be automatically approved, information verification and other processing can be automatically performed, and after approval, funds payment can be made using the bank account end or the third-party account end. For manual approval, the financial approval application is sent to the financial supervisor client 102 to wait for the approval result of the financial supervisor. The financial approval system 103 may include a registration book and a regulatory approval verification module, and specific functions include: a. After the corporate client marketing system maintains the regulatory approval function, it receives instructions and registers the regulatory approval activation status into the corporate client basic information table, and sends instructions to the financial submitter client 101 and the financial supervisor's client 102; b. After the financial supervisor client 101 maintains the pre-approval conditions, it receives the pre-approval conditions information and registers the pre-approval conditions details into the regulatory approval details table; c. After the financial submitter client 101 initiates the financial approval application instruction, it judges the financial approval application according to the pre-approval conditions to determine whether to perform automatic approval or manual approval.

[0092] The pre-approval conditions can be set from multiple dimensions. The following are three simple setting methods.

[0093] Method 1: Set pre-approval conditions according to business scenarios. Core logic: Divide by business scenario. The same business scenarios use the same pre-approval conditions. You can set several different parameters according to the specific business. Business scenarios can be divided into two categories: limited and unlimited.

[0094] The common parameters in limit scenarios include: regulated account number, regulated financial submitter, pre-approval amount range, pre-approval purpose, and validity period of pre-approval conditions; other parameters can be customized. You can maintain the applicable functions first and then set the field information. For example, you can set the contract number for transfer and remittance, and the name of the financial product for investment and financial management.

[0095] The common parameters for unlimited scenarios include: the regulated financial submitter S, the validity period of the pre-approval conditions; other parameters can be customized by maintaining the applicable functions first and then setting the field information. For example, for account inquiries, you can set the query account number, and for credit report inquiries, you can set the number of queries.

[0096] Method 2: Set pre-approval conditions according to the business level of the financial submitter. Core logic: The business level and other attributes of the financial submitter are taken into consideration in the pre-approval conditions, where the same business level is subject to the same automatic approval authorization mode.

[0097] Indicators for evaluating the business level of financial submitters include business background indicators and behavioral indicators. Business background indicators include, but are not limited to: years of work experience, business proficiency, job level, and importance of the business in charge. Behavioral indicators: the number of authorized automatic approvals in history, the number of rejected automatic approvals in history, the number of approval results or ratios of approvals in automatic approvals in history, the number of approval results or ratios of approvals in manual approvals in history, the number of approval results or ratios of approvals in manual approvals in history, the number of financial approvals submitted on the day, and the total number of financial approval applications submitted in history.

[0098] The weights of each indicator can be clearly defined in the pre-approval conditions, for example:

[0099] (1) 0-3 years of working experience is worth 1, 3-10 years of working experience is worth 2, and more than 10 years of working experience is worth 3;

[0100] (2) The score of business proficiency is 0 for unskilled, 1 for average, and 2 for skilled;

[0101] (3) The importance of the business in charge is scored as 1 for unimportant, 2 for moderate, and 3 for important;

[0102] (4) The score of the number of authorization rejections in the same history is 1 if the number of rejections is more than 5 times, 2 if the number of rejections is 1-4 times, and 3 if the number of rejections is never 3.

[0103] Corresponding to different financial submitters, corresponding values ​​can be set for the parameters in this scenario based on dimensions such as the financial submitter's business proficiency and years of experience.

[0104] In one embodiment, as described above, the above indicators can be combined to form a business level vector. The financial director can set the benchmark value of each indicator when submitting the pre-approval conditions. Then submit this information to the financial approval system 103. The financial approval system 103 combines and processes the benchmark values ​​of each indicator uploaded by the financial director client 102 to form a pre-approval condition vector (i.e., a benchmark business level vector) corresponding to the pre-approval amount range of different levels in each business scenario. Then, this is used as a measurement or evaluation benchmark for the business level of the financial submitter in the financial approval process, and the cosine similarity is used to determine whether the business level of the financial submitter meets the qualifications for automatic approval.

[0105] For example, the pre-approval amount of preset approval condition 1 is 10 million, and this condition requires the benchmark business level vector to be [3, 2, 2, 2]; the pre-approval amount of preset approval condition 2 is 5 million, and this condition requires the benchmark business level vector to be [2, 2, 1, 1]. After the financial submitter initiates the financial approval application, the similarity between the financial submitter's business level vector and the vector in the preset approval condition is calculated by the cosine function. That is, the benchmark business level vector set in the preset approval condition is RY (Y1, Y2, Y3, Y4, ..., Yn), and the financial submitter's business level vector is RA (A1, A2, A3, A4, ..., An). The cosine similarity between the current financial submitter's business level vector RA and the vector RY in the preset approval condition can be calculated as follows:

[0106]

[0107] If they are very similar (for example, the cosine value is between 0.8 and 1.0), they will be automatically approved; otherwise, they will enter the manual approval process.

[0108] Of course, in other embodiments, the various indicators in (1) to (4) above can also be accumulated to evaluate the business level score of the financial submitter, and then the pre-approval conditions can be set accordingly. For example, the financial director can set that when automatically approving a business within a certain amount range, the business level score of the financial submitter should be in the interval [6, 14]. Assume that two pre-approval conditions are preset: the pre-approval amount of the preset approval condition 1 is 10 million, and this condition requires the business level score of the financial submitter to be [10, 14]; the pre-approval amount of the preset approval condition 2 is 5 million, and this condition requires the business level score of the submitter to be [8, 10]. After the financial submitter initiates the transaction, the business level score of the financial submitter is calculated and matched with the approval conditions. If the match is successful, it is automatically approved, otherwise it enters the manual approval process.

[0109] Method three: Dynamically assemble according to business scenarios and various attributes of the actual submitter, and set pre-approval conditions. Core logic: In theory, a financial submitter should use a fixed U-shield in his name to initiate a transaction, but subject to the company's management system, there may be situations where the same U-shield is used by different financial submitters or the same financial submitter uses different U-shiels for transactions. In this case, it will be inaccurate to automatically judge the approval conditions according to a single scenario or a single financial submitter. At this time, it is necessary to increase the recognition of the financial submitter's biometric information (such as face recognition, U-shield button strength, etc.) to dynamically assemble the automatic approval conditions.

[0110] For example, you can get the following variables:

[0111] Business scenario variable x1: the business scenario category for initiating the transaction, such as remittance 1, or investment and financial management 2;

[0112] Business level variable x2 of the financial submitter: The value of x2 is obtained according to method 2, which can be either the business level vector of the financial submitter or the business level score of the financial submitter.

[0113] Biometric information x3 of the financial submitter: evaluated based on the identification information, if it is the person himself, the value is 1; otherwise, the value is 0.

[0114] Environmental information for current financial applications submitted x4: Based on the situation assessment obtained through identification, 2 for office, 1 for non-office, 0 for outdoor.

[0115] In one embodiment, the above four variables can be spliced ​​into a vector, such as [x1, x2, x3, x4]. According to the values ​​of the above four variables in the pre-approval conditions corresponding to the pre-approval amount range of each level in each business scenario, the corresponding pre-approval condition vector is obtained, and each time the financial submitter submits a financial approval application, the values ​​of the above four variables in this financial approval application are obtained to obtain the application vector corresponding to this financial approval application, and then the similarity between the application vector and the pre-approval condition vector is calculated, and it is determined whether to go through the automatic approval process or the manual approval process according to the similarity result.

[0116] In another embodiment, the above four variables can also be divided into two categories: access class and evaluation class. For example, biological information x3 can be classified into the access class, so that only when the value of x3 represents the person himself, other conditions can be judged, otherwise the financial application approval is directly rejected. Correspondingly, the business level variable x2 can be classified into the evaluation class, and can be judged by similarity. Of course, in addition to the business level variable x2, in some embodiments, environmental information x4 can also be used as an evaluation class. For example, when environmental information x4 is used to evaluate the noisiness of the environment and the degree of compliance with the preset environmental conditions, environmental information x4 can be processed as an evaluation class variable. After the variables are divided into two categories: access class and evaluation class, the access class variables are processed with the logic of compliance or not. As for the evaluation class variables, they can be spliced ​​into vectors and then analyzed by vector similarity.

[0117] Figure 7 A flowchart schematically illustrates automatic approval based on major business scenario categories on the bank side in another embodiment of the present disclosure.

[0118] like Figure 7 As shown, combined Figure 1 ,After the bank and the enterprise negotiate, after the financial approval system supervised by the bank is opened on the bank side, the financial approval process in the scenario of automatic approval based on the major business scenarios may include the following S71~S712.

[0119] S71, the bank opens and maintains the corporate supervision and approval agreement in the corporate customer marketing system according to the needs of corporate customers. After the maintenance is completed, the corporate customer marketing system sends the agreement information to the financial approval system 103 supervised by the bank.

[0120] S72, the bank-supervised financial approval system registers the enterprise supervision approval agreement activation status into the enterprise customer basic information table, associates the enterprise group number, group certificate information, etc., and sends the corresponding information to the enterprise's financial submitter client 101 and financial supervisor client 102 respectively.

[0121] S73, the financial submitter client 101 receives the information and adds a regulatory approval judgment when submitting the financial purchase transaction; the financial supervisor client 102 receives the information and displays the regulatory approval function, including manual approval and maintenance of pre-approval conditions in automatic approval.

[0122] S74, the financial supervisor maintains the pre-approval conditions for the limit-type financial purchase transactions through the supervision and approval function in the financial supervisor client 102. The fields that can be set include but are not limited to: the supervised account number, the supervised financial submitter information, the pre-approval amount range, the pre-approval purpose, the financial products that can be purchased, the validity period of the approval conditions, etc. The financial supervisor client 102 sends the corresponding information to the financial approval processing system 103 supervised by the bank.

[0123] S75, the bank-supervised financial approval processing system 103 receives the pre-approval conditions and registers the pre-approval condition details into the supervision approval details table.

[0124] S76, the financial submitter logs in to the financial submitter client 101 to apply for the purchase of financial products.

[0125] S77, the financial submitter client 101 determines whether the financial submitter is a supervised financial submitter, if yes, proceed to S78, if not, proceed to S712.

[0126] S78, the financial submitter client 101 sends the financial purchase application instruction information to the financial approval system 103 supervised by the bank to determine whether the instruction type belongs to the supervised instructions. If so, enter S79, and then enter S712.

[0127] S79, the financial approval processing system 103 supervised by the bank compares the submission time, payment account number, name of financial product, purchase amount, purpose summary information and other elements when the instruction is submitted with the pre-approval conditions: whether the payment account number is consistent with the corporate account number, whether the purpose summary information is consistent with the pre-approved purpose, whether the purchase amount is less than the balance of the pre-approved amount, whether the instruction submission time is within the validity period of the approval document. If any of the checks fails, enter S710; if all the above checks pass, enter S711.

[0128] S710, the instruction information submitted by the financial submitting client 101 does not meet the pre-approval conditions, and the transaction status is fed back to the financial submitting client 101 as failure.

[0129] S711, the financial approval processing system 103 supervised by the bank releases the transaction instruction, and the bank account end makes payment from the payment account.

[0130] S712, the bank account registers the purchase of the financial product, and the financial submitter client 101 updates the transaction status to success, and the transaction is completed.

[0131] Figure 8 A flowchart schematically illustrates automatic approval based on the business level of a financial submitter on the bank side in yet another embodiment of the present disclosure.

[0132] like Figure 8 As shown, combined Figure 1 After the bank negotiates with the enterprise, after the financial approval system 103 supervised by the bank is opened on the bank side, the process of automatic approval based on the business level of the financial submitter may include the following S81~S811.

[0133] S81, the bank opens and maintains the enterprise supervision and approval agreement in the legal person customer marketing system according to the needs of the enterprise customers, and after the maintenance is completed, the agreement information is sent to the financial approval processing system 103 supervised by the bank.

[0134] S82, the bank-supervised financial approval processing system 103 registers the enterprise supervision approval agreement activation status into the enterprise customer basic information table, associates the enterprise group number, group certificate information, etc., and sends the corresponding information to the enterprise's financial submitter client 101 and financial supervisor client 102 respectively.

[0135] S83, the financial submitter client 101 receives information and adds a regulatory approval judgment when the financial submitter applies for a payment transaction; the financial supervisor client 102 receives information and displays the regulatory approval function, including manual approval and maintenance of pre-approval conditions in automatic approval.

[0136] S84, the financial director maintains the pre-approval conditions through the regulatory approval function in the financial director client 102, including the values ​​of multiple indicators of the authorized financial submitters and the business level of the financial submitters corresponding to the pre-approval amount range under each business scenario. The financial director client 102 sends the corresponding information to the financial approval processing system 103 supervised by the bank.

[0137] S85, the bank-supervised financial approval processing system 103 receives the pre-approval conditions and registers the pre-approval condition details into the supervision approval details table, and can process multiple indicators in the pre-approval conditions into a pre-approval condition vector.

[0138] S86 , the financial submitter applies for a payment transaction through the financial submitter client 101 .

[0139] S87, the financial submitter client 101 determines whether the financial submitter is a supervised financial submitter, if yes, proceed to S88, if not, proceed to S810.

[0140] S88, the financial submitter client 101 sends the transfer and remittance instruction information to the financial approval system 103 supervised by the bank, obtains the business level vector of the financial submitter, and then performs a similarity judgment with the pre-approval condition vector (i.e., the benchmark business level vector). If the similarity is greater than the similarity threshold, the instruction is released to enter S810, otherwise it enters the manual approval process in S89.

[0141] S89, the financial manager logs in to the financial manager client 102 and manually approves the payment transaction application.

[0142] S8 1 0, the financial approval system 103 supervised by the bank automatically approves the transaction payment request, verifies the account information, etc. When the verification is successful, the personal account end successfully receives the remittance.

[0143] S811, the transaction status is updated to success in the financial submitter client 101, and the transaction is completed.

[0144] It can be seen that according to the embodiments of the present disclosure, corporate customers can maintain pre-approval conditions in different dimensions according to actual needs, thereby delegating financial approval authority to qualified financial submitters. On the one hand, this can avoid the need for financial supervisors to perform frequent subsequent manual approval operations. On the other hand, it also effectively improves the processing efficiency of financial approval and payment, and reduces problems caused by untimely manual approval.

[0145] By monitoring the financial approval application of each financial submitter through pre-approval conditions, the prior supervision can be strengthened for enterprise management, avoiding the possibility of the financial submitter abusing the operation authority to transfer the company's property. It can be seen that the approval model according to the embodiment of the present disclosure can meet the needs of corporate customers, has flexibility, pertinence, and dynamism, can further enhance the customer experience, and can achieve a good balance between the efficiency of corporate financial approval and the security of automatic approval.

[0146] Based on the financial approval methods of the above embodiments, the present disclosure also provides a financial approval device. Fig. 9 The financial approval device is described in detail.

[0147] Fig. 9 The structural block diagram of the financial approval device 900 according to the embodiment of the present disclosure is schematically shown.

[0148] like Fig. 9 As shown, according to some embodiments of the present disclosure, the financial approval device 900 may include an information extraction module 910, a first acquisition module 920, a second acquisition module 930, a similarity calculation module 940 and an approval module 950. According to other embodiments of the present disclosure, the financial approval device 900 may further include a pre-approval condition deployment module 960. The financial approval device 900 may perform a reference Figure 2 to Figure 8 The financial approval method described.

[0149] Specifically, the information extraction module 910 is used to extract information about the current financial submitter and the task to be approved from the current financial approval application in response to receiving the current financial approval application. In one embodiment, the information extraction module 910 may perform the operation S210 described above.

[0150] The first acquisition module 920 is used to obtain the values ​​of multiple indicators for evaluating the business level of the current financial submitter, the values ​​of at least some of the multiple indicators are updated over time or with the behavior of the financial submitter, and the values ​​of the multiple indicators of the current financial submitter are processed to obtain the target business level vector corresponding to the current financial submitter. In one embodiment, the first acquisition module 920 can perform the operation S220 described above.

[0151] The second acquisition module 930 is used to acquire the reference business level vector corresponding to the task to be approved. In one embodiment, the second acquisition module 930 may perform the operation S230 described above.

[0152] The similarity calculation module 940 is used to calculate the similarity between the target service level vector and the reference service level vector. In one embodiment, the similarity calculation module 940 may perform the operation S240 described above.

[0153] The approval module 950 is used to determine the approval method of the current financial approval application based on the similarity, including: when the similarity exceeds the similarity threshold, the task to be approved is approved in an automatic approval manner; otherwise, the task to be approved is approved in a manual approval manner. In one embodiment, the approval module 950 can perform the operations S250 to S270 described above.

[0154] The pre-approval condition deployment module 960 is also used to: pre-set different pre-approval condition vectors for pre-approval amount ranges of different levels in the business scenario, wherein an initial pre-approval condition vector is set for each level of pre-approval amount range in the business scenario, and the pre-approval condition vector is dynamically updated according to the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario. The specific process of dynamically updating the pre-approval condition vector according to the approval results of historical approval tasks falling within the pre-approval amount range of each level in the business scenario can be referred to in the previous text. Figure 4 or Figure 5 Introduction.

[0155] The second acquisition module 930 is specifically used to: determine the business scenario and target approval amount to which the business to be approved belongs according to the information of the task to be approved; determine the level of the pre-approval amount range to which the target approval amount belongs to obtain the target level; and select the pre-approval condition vector corresponding to the target level to obtain the benchmark business level vector. In one embodiment, the second acquisition module 930 can perform the operations S231-233 described above.

[0156] According to an embodiment of the present disclosure, any multiple modules among the information extraction module 910, the first acquisition module 920, the second acquisition module 930, the similarity calculation module 940, the approval module 950 and the pre-approval condition deployment module 960 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the information extraction module 910, the first acquisition module 920, the second acquisition module 930, the similarity calculation module 940, the approval module 950 and the pre-approval condition deployment module 960 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation modes of software, hardware and firmware or in a proper combination of any of them. Alternatively, at least one of the information extraction module 910, the first acquisition module 920, the second acquisition module 930, the similarity calculation module 940, the approval module 950 and the pre-approval condition deployment module 960 can be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function can be performed.

[0157] Fig.10 A block diagram of an electronic device suitable for implementing the financial approval method according to an embodiment of the present disclosure is schematically shown.

[0158] like Fig.10As shown, the electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include an onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0159] In RAM 1003, various programs and data required for the operation of electronic device 1000 are stored. Processor 1001, ROM 1002 and RAM 1003 are connected to each other via bus 1004. Processor 1001 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1002 and / or RAM 1003. It should be noted that the program can also be stored in one or more memories other than ROM 1002 and RAM 1003. Processor 1001 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0160] According to an embodiment of the present disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to the bus 1004. The electronic device 1000 may further include one or more of the following components connected to the I / O interface 1005: an input portion 1006 including a keyboard, a mouse, etc.; an output portion 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1008 including a hard disk, etc.; and a communication portion 1009 including a network interface card such as a LAN card, a modem, etc. The communication portion 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage portion 1008 as needed.

[0161] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0162] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above and / or one or more memories other than ROM 1002 and RAM 1003.

[0163] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiment of the present disclosure.

[0164] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 1001. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0165] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1009, and / or installed from the removable medium 1011. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0166] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and / or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0167] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0168] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a 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 box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0169] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0170] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A financial approval method, comprising: In response to receiving the current financial approval application, extracting information of the current financial submitter and the task to be approved from the current financial approval application; Obtaining values ​​of a plurality of indicators for evaluating the business level of the current financial submitter, wherein the values ​​of at least some of the plurality of indicators are updated over time or with the behavior of the financial submitter; Processing the values ​​of multiple indicators of the current financial submitter to obtain a target business level vector corresponding to the current financial submitter; Obtaining a benchmark business level vector corresponding to the task to be approved; Calculating the similarity between the target service level vector and the reference service level vector; as well as Determining the approval method of the current financial approval application based on the similarity includes: when the similarity exceeds a similarity threshold, approving the pending approval task in an automatic approval manner; Otherwise, the pending approval task is approved manually.

2. The method according to claim 1, wherein: The multiple indicators include at least one of the following categories: Behavioral indicators, wherein the behavioral indicators are statistical indicators of the financial submitter's behavior in submitting financial approvals; or Business background indicators, wherein the business background indicators are the education background indicators and / or years of experience indicators of the financial submitter.

3. The method according to claim 2, wherein: After determining the approval method of the current financial approval application based on the similarity, the method further includes: The value of the behavior indicator of the current financial submitter is updated.

4. The method according to claim 2 or 3, wherein: The behavioral indicators include at least one of the following: The number of authorized automatic approvals in history, the number of rejected automatic approvals in history, the number of approved approvals or the ratio in automatic approvals in history, the number of rejected approvals or the ratio in automatic approvals in history, the number of approved approvals or the ratio in manual approvals in history, the number of rejected approvals or the ratio in manual approvals in history, the number of financial approvals submitted on the day, and the total number of financial approval applications submitted in history.

5. The method according to claim 1, wherein: The step of obtaining the benchmark business level vector corresponding to the task to be approved comprises: Determine the business scenario and target approval amount to which the pending approval task belongs according to the information of the pending approval task; wherein different pre-approval condition vectors are set for different levels of pre-approval amount ranges in the business scenario; Determine the level of the pre-approval amount range to which the target approval amount belongs, and obtain the target level; and The pre-approval condition vector corresponding to the target level is selected to obtain the reference service level vector.

6. The method according to claim 5, wherein: The method further includes pre-setting different pre-approval condition vectors for different levels of pre-approval amount ranges in the business scenario, specifically including: For each level of pre-approval amount range in the business scenario, an initial pre-approval condition vector is set; Dynamically updating the pre-approval condition vector according to the approval results of the historical approval tasks that fall within the pre-approval amount range of each level in the business scenario, specifically includes: Accumulating the approval results of the historical approval tasks that fall within the pre-approval amount range of each level in the business scenario to obtain a first measurement data set; When the data volume of the first calculated data set exceeds a first data volume threshold, counting the distribution ratio between the manual approval method and the automatic approval method for all historical approval tasks within the pre-approval amount range of each level in the business scenario; and When the allocation ratio satisfies the first approval item adjustment condition, the pre-approval condition vector is updated.

7. The method according to claim 6, wherein: The dynamically updating the pre-approval condition vector according to the approval results of the historical approval tasks falling within the pre-approval amount range of each level in the business scenario further comprises: For the second historical approval task that has been approved by manual approval, obtaining feedback from the approver on whether the second historical approval task is more suitable for automatic approval; Accumulating the acquired feedback suggestions to obtain a second measurement data set; When the data volume of the second calculated data set exceeds a second data volume threshold, determining, based on the feedback suggestions in the second calculated data set, a proportion of automatic approval tendencies that are more suitable for the automatic approval method among all second historical approval tasks that have been approved in the manual approval method; and When the automatic approval tendency ratio satisfies the second approval document adjustment condition, the pre-approval condition vector is updated.

8. The method according to claim 1, wherein: The automatic approval method for approving the pending approval task includes: identifying said current financial submitter; If the identity recognition is successful, the task to be approved is approved; otherwise, it is determined that the task to be approved is not approved.

9. The method according to claim 1, wherein: The automatic approval method for approving the pending approval task includes: Collect information about the current submission environment of the current financial approval application; Comparing the information of the currently submitted environment with the environment requirement conditions set for the task to be approved to obtain a comparison result; and If the comparison result indicates that the current submission environment meets the environment requirement conditions set for the task to be approved, the task to be approved is approved; otherwise, it is determined that the task to be approved is not approved.

10. A financial approval device, comprising: An information extraction module, configured to extract information of a current financial submitter and tasks to be approved from the current financial approval application in response to receiving the current financial approval application; The first acquisition module is used to: Obtaining values ​​of a plurality of indicators for evaluating the business level of the current financial submitter, wherein the values ​​of at least some of the plurality of indicators are updated over time or with the behavior of the financial submitter; as well as Processing the values ​​of multiple indicators of the current financial submitter to obtain a target business level vector corresponding to the current financial submitter; A second acquisition module is used to acquire a benchmark business level vector corresponding to the task to be approved; A similarity calculation module, used to calculate the similarity between the target service level vector and the reference service level vector; as well as An approval module, used for determining an approval method of the current financial approval application based on the similarity, including: when the similarity exceeds a similarity threshold, approving the pending approval task in an automatic approval manner; Otherwise, the pending approval task is approved manually.

11. An electronic device, comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors execute the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having computer program instructions stored thereon, wherein the computer program instructions, when executed by a processor, implement the method according to any one of claims 1 to 9.

Images