Examination and approval process supervision method and equipment for regional financial enterprise, and medium

Abstract

The embodiment of the invention discloses an approval process supervision method and device for a regional financial enterprise and a medium, and relates to the technical field of approval supervision, and the method comprises the steps: receiving the approval declaration information of the financial enterprise, determining a plurality of approval process nodes corresponding to the financial enterprise through the approval declaration information, the method comprises the following steps: acquiring a plurality of approval process nodes to determine process information of each approval process node, matching a plurality of corresponding approval user nodes in a regional management platform according to the process information of each approval process node to set a node permission for each approval user node, and sending to-be-approved material information to a first approval user node with the approval permission, determining approval result data of each first approval user node in the corresponding approval process node according to the process information of the approval process node; and verifying the examination and approval result data through the second examination and approval user node with the supervision authority, and determining supervision result data of the examination and approval process node so as to supervise the examination and approval process.

Description

Technical Field

[0001] This specification relates to the technical field of approval supervision, and particularly to a method, device, and medium for supervising the approval process of regional financial enterprises. Background Art

[0002] The financial industry is a highly regulated industry, and special financial regulatory agencies are established to supervise and manage it. Local financial enterprises such as microloan companies, financing guarantee companies, pawnshops, financial leasing companies, commercial factoring companies, and regional equity markets, as a type of financial institution, their business activities involve the raising, investment, and management of funds. Therefore, they need to be approved and supervised by financial regulatory agencies to ensure the compliance and stability of their business activities.

[0003] The approval process of local financial enterprises is often cumbersome and involves many links. Taking microloan companies as an example, starting from submitting an application for establishment, it needs to go through multiple rounds of reviews by multiple departments, including the review of various aspects such as shareholder qualifications, sources of funds, and articles of association. The approval involves multiple regional nodes. Although financial approval agencies have formulated detailed approval standards, due to factors such as professional background, work experience, and thinking patterns, different approval personnel may have deviations in understanding and implementing the standards, resulting in different approval results for enterprises with the same conditions. At the same time, there are also regulatory gaps in the approval connection between regional nodes, and problems such as poor information transmission are likely to occur.

[0004] Therefore, in the approval scenario of regional financial enterprises, the approval process lacks supervision, and it is impossible to guarantee the approval results and efficiency. Summary of the Invention

[0005] One or more embodiments of this specification provide a method, device, and medium for supervising the approval process of regional financial enterprises to solve the following technical problems: In the approval scenario of regional financial enterprises, the approval process lacks supervision, and it is impossible to guarantee the approval results and efficiency.

[0006] One or more embodiments of this specification adopt the following technical solutions:

[0007] One or more embodiments of this specification provide a method for supervising the approval process of regional financial enterprises. The method includes: receiving the approval application information of a financial enterprise, and determining multiple approval process nodes corresponding to the financial enterprise through the approval application information, so as to determine the process information of each approval process node, where the process information includes approval reference criteria; according to the process information of each approval process node, matching multiple approval user nodes corresponding to each approval process node in the regional management platform, and setting node permissions for each approval user node, where the node permissions include approval permissions and supervision permissions; sending the information of materials to be approved to the first approval user node with approval permissions, and approving the financial enterprise according to the process information of the approval process node, and determining the approval result data of each first approval user node in the corresponding approval process node; verifying the approval result data of the first approval user node through the second approval user node with supervision permissions, and determining the supervision result data of the approval process node, so as to supervise the approval process.

[0008] One or more embodiments of this specification provide an approval process supervision device for regional financial enterprises, including:

[0009] At least one processor; and,

[0010] A memory communicatively connected to the at least one processor; wherein,

[0011] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above method.

[0012] A non-volatile computer storage medium provided by one or more embodiments of this specification stores computer-executable instructions, and the computer-executable instructions are set to: execute the above method.

[0013] The above at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects: Through the technical solution of the embodiments of this specification, by receiving approval application information, multiple approval process nodes and their process information are determined, including approval reference standards, which sets clear and unified standards for the entire approval process, ensuring the consistency and standardization of the approval work, and avoiding randomness and differences caused by human factors; According to the process information of the approval process nodes, multiple corresponding approval user nodes are matched in the regional management platform, and the approval tasks can be assigned to the most suitable personnel, taking into account factors such as the professional skills and experience of different approval users, realizing the optimal allocation of human resources; The reasonable personnel allocation enables the approval work to be quickly started and efficiently promoted. Each approval user node focuses on its own proficient field, reducing the repeated communication and handover costs caused by mismatched personnel, thus accelerating the entire approval process and meeting the requirements of financial enterprises for approval timeliness; The first approval user node with approval authority and the second approval user node with supervision authority are set up to form a two-level approval supervision mechanism. The first approval user node conducts preliminary approval, and the second approval user node verifies the approval result data, double-guaranteeing the accuracy and reliability of the approval result. This multi-level review helps to discover and correct possible approval mistakes and reduce approval risks; Through the verification of the second approval user node, problems that may occur in the approval process of the first approval user node can be timely discovered, standardizing the approval behavior and improving the quality of the approval work. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings. In the drawings:

[0015] Figure 1 It is a schematic flowchart of a method for supervising the approval process of a regional financial enterprise provided by the embodiments of this specification;

[0016] Figure 2 It is a schematic structural diagram of a device for supervising the approval process of a regional financial enterprise provided by the embodiments of this specification. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0017] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all the embodiments. Based on the embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this specification.

[0018] The embodiments of this specification provide a method for supervising the approval process of regional financial enterprises. It should be noted that the execution subject in the embodiments of this specification can be a server or any device with data processing capabilities. Figure 1 It is a schematic flowchart of a method for supervising the approval process of a regional financial enterprise provided by the embodiments of this specification, as Figure 1 shown, mainly including the following steps:

[0019] Step S101, receive the approval application information of the financial enterprise, and through the approval application information, determine multiple approval process nodes corresponding to the financial enterprise to determine the process information of each approval process node.

[0020] Among them, the process information includes approval reference standards.

[0021] In an embodiment of this specification, an approval supervision system is set up in advance. When a financial enterprise needs to apply for approval, it registers an enterprise account in the approval supervision system and sends the approval application information that needs to be approved to the supervision system. After receiving the approval application information of the financial enterprise, the approval supervision system automatically identifies the approval application information to determine multiple approval process nodes corresponding to the financial enterprise to determine the process information of each approval process node, and the process information includes approval reference standards.

[0022] Through the approval application information, determine multiple approval process nodes corresponding to the financial enterprise, and determine the process information of each such approval process node, specifically including: parsing the approval application information to extract the financial enterprise type and enterprise application element information of the financial enterprise, and the enterprise application element information includes any one or more of the business scope element, registered capital element, shareholder information element, business model element, and risk management element; conducting a formal review of the enterprise application element information, and when the formal review passes, mapping according to the financial enterprise type and the enterprise application element information into a pre-set approval process template to determine corresponding multiple approval process nodes, where the approval process nodes include any one or more of the qualification review node, business review node, risk management review node, compliance review node, and financial review node; through the multiple approval process nodes, determine the process information of each such approval process node.

[0023] In one embodiment of this specification, the network interface part of the system is continuously in a listening state. Triggered by the approval declaration information of a financial enterprise, the approval declaration information is sent to the data parsing module. The data parsing module first performs format verification on the declaration information to ensure that it conforms to the system's preset data format specifications. For example, using a specific XML or JSON format for data encapsulation, the system will check the structural integrity of the data, the correct use of tags, etc. If the format is correct, it starts preliminary parsing to identify the key identifiers in the data, such as the identifier of the financial enterprise type. Through techniques such as regular expressions and semantic analysis, the financial enterprise type and enterprise declaration element information are extracted from the declaration information. The financial enterprise type is stored in a dedicated enterprise type identifier field. For the enterprise declaration element information, according to different element types, such as business scope elements, registered capital elements, etc., they are respectively stored in the corresponding database tables or data structures for subsequent calling and processing.

[0024] The formal review module is used to load the pre-set review rules from the rule library. These rules are stored in a structured form, for example, in the form of conditional statements and matching patterns. For business scope elements, the rules may stipulate that specific industry keywords must be included and the expression cannot be ambiguous. The extracted enterprise declaration element information is matched with these rules one by one. Check whether each element information is complete. For example, the registered capital element must have a clear amount value and be accompanied by the path of a legal fund certification document or relevant reference. At the same time, the standardization of the information is checked. If all element information passes the rule matching, the formal review is passed, and a passing signal will be sent to the subsequent process, along with the classified and stored enterprise declaration element information. If any element information does not conform to the rules, a detailed error report will be generated, indicating the specific element that does not conform to the rules and the reason, and feedback it to the financial enterprise declaration terminal, requesting it to modify and resubmit.

[0025] According to the determined type of financial enterprise, call the corresponding template from the approval process template library. The template library is stored in an easily retrievable manner, such as using a tree structure or a hash table structure, with the type of financial enterprise as the index. For example, a microloan company corresponds to a specific approval process template, and a financial leasing company corresponds to another set of templates. The approval process templates corresponding to each type of financial enterprise can be set through big data statistical analysis of historical approval processes. Match the enterprise declaration element information with the requirements in the template. For example, if the declared business model element shows that the financial enterprise is involved in an online-offline integrated microloan business, there will be specific approval process nodes in the template for such a business model, such as an online business risk assessment node, an offline business compliance review node, etc. Through this matching, determine multiple corresponding approval process nodes. Integrate the determined multiple approval process nodes in a preset logical order to form an ordered approval process chain, and output it to the subsequent process information determination module, along with the preliminary identification of each node and the associated enterprise declaration element information.

[0026] For each approval process node, parse its detailed process information from the node attribute library. The node attribute library stores the relevant attributes of each approval process node, including approval types (such as qualification review, business review, etc.), approval reference standards, requirements for the roles of approval personnel, etc. For example, for the risk management review node, its approval reference standard will be clearly defined as a specific risk assessment index system and risk control measure requirements. Integrate the parsed process information with the previously associated enterprise declaration element information. For example, at the financial review node, combine the enterprise-declared registered capital element and financial statement information to determine specific financial review key points and standards. Store the integrated process information in the approval process information table for approval personnel to consult and perform approval operations at any time.

[0027] Through the above technical solution, the data reception and parsing module performs format verification, preliminary parsing, and classification extraction on the approval application information, enabling the accurate extraction of financial enterprise types and various enterprise application element information from complex application data, ensuring the accuracy of the information obtained by the system, and providing a reliable data foundation for subsequent review and approval processes; in accordance with the preset review rules, the integrity and standardization of the enterprise application element information are checked to ensure that the application information meets the requirements in form and avoid approval delays caused by missing information or non-standard formats; according to the financial enterprise type, the corresponding approval process template is called, and the enterprise application element information is matched with it to determine the approval process nodes. The templatized operation method makes the approval process highly standardized and regularized. Different financial enterprise types have relatively fixed approval process frameworks, and regardless of when and where the approval is carried out, the same standard process is followed, reducing approval differences caused by human factors and improving the fairness and consistency of approval; in the entire processing process from data reception to process information determination, most links are automated, reducing manual intervention and improving approval efficiency. Compared with the traditional manual processing method, a large number of approval application information can be processed in a short time, and the approval process and related information can be quickly determined, meeting the requirements of financial enterprises for approval timeliness.

[0028] Step S102: According to the process information of each approval process node, in the regional management platform, match multiple approval user nodes corresponding to each approval process node to set node permissions for each approval user node.

[0029] Among them, the node permissions include approval permissions and supervision permissions;

[0030] According to the process information of each such approval process node, in the regional management platform, matching multiple approval user nodes corresponding to each such approval process node specifically includes: obtaining the organizational node information of multiple approval organizations pre-stored in the regional management platform, where the organizational node information includes the approval users and organizational approval content associated with each organizational node; according to the process information of each such approval process node and the organizational node information, searching for an approval organizational node that matches the process information in the regional management platform; obtaining the user information of multiple approval users in the approval organizational node to analyze the multiple approval users and determine multiple approval user nodes corresponding to each such approval process node.

[0031] Analyze the multiple approval users to determine the multiple approval user nodes corresponding to each approval process node, specifically including: dividing the multiple approval users according to the rank information in the user information to determine the first approval user set and the second approval user set, where the ranks of the users in the second approval user set are higher than those in the first approval user set; obtaining the historical approval data and real-time idle status in the user information, where the historical approval data includes the historical approval passing rate corresponding to each type of financial enterprise, the average approval duration corresponding to each type of financial enterprise, and the historical approved enterprise type; screening in the first approval user set and the second approval user set respectively through the historical approval data and the real-time idle status to determine the multiple approval user nodes corresponding to each approval process node.

[0032] Screen in the first approval user set and the second approval user set respectively through the historical approval data and the real-time idle status to determine the multiple approval user nodes corresponding to each approval process node, specifically including: screening the multiple first approval users in the first approval user set through the historical approval data to determine the first approval users meeting the preset requirements; screening multiple second approval users in the idle state in the second approval user set according to the real-time idle status, and sorting the second approval users according to their ranks to generate the user numerical identifier for each second approval user; generating a random number in a specified format according to the preset rule through the user numerical identifier, and determining the second approval users through the random number and the user numerical identifier; determining the multiple approval user nodes corresponding to the approval process node through the first approval users and the second approval users.

[0033] In an embodiment of the present specification, the database storage module of the access area management platform stores the organization node information corresponding to multiple approval organizations. For example, it may adopt the table structure of a relational database. One table records the organization nodes, and another table records the approval users and the organization approval content. The system retrieves all the organization node information from the database through a specific query statement, such as an SQL query, based on a preset index (which may be the organization ID, etc.), and loads it into the memory cache of the system for subsequent quick access to reduce the I / O pressure on the database. Parse the organization node information into an object model, and each object contains the unique identifier of the organization node, the associated list of approval users (each user is also stored in the form of an object, including basic information such as user ID and name), and the description information of the organization approval content.

[0034] Analyze the process information of each approval process node. The process information here may include approval types (such as qualification review, risk assessment, etc.), approval reference criteria (specific quantitative indicators or compliance requirements), etc. The system extracts this information to form a feature set for matching. By traversing the organizational node information loaded in memory, compare the organizational approval content of each organizational node with the process information of the approval process node. Information comparison can be carried out through technologies such as keyword matching and semantic analysis. For example, if the process information of the approval process node is about the risk assessment of small loan companies, the system will search for organizational nodes in the organizational approval content that contain relevant keywords such as "small loan" and "risk assessment". Once a matching organizational node is found, it is used as a candidate approval organizational node.

[0035] For the selected approval organizational nodes, obtain the user information of multiple approval users under the organizational node. This information may be stored in the user information table and queried through the association relationship between the organizational node and the user (such as the organization-user association table). The obtained user information includes responsibility levels, historical approval data, professional skills, etc., which are also loaded into memory for processing. According to the preset division rules, all approval users are divided into two sets, namely the first approval user set and the second approval user set. For example, those above a certain job level are set as the second approval user set, and those not higher than this job level are set as the first approval user set. The job levels of users in the second approval user set are higher than those in the first approval user set. This division method helps the system to screen subsequent candidates targeted according to the characteristics and capabilities of users at different job levels, realizing the reasonable allocation of approval resources.

[0036] Obtain the historical approval data from the approval user information. This data contains detailed information such as the historical approval passing rate corresponding to each type of financial enterprise, the average approval duration corresponding to each type of financial enterprise, and the historical approval enterprise types. The system extracts relevant information from the historical approval data for analysis according to the type of financial enterprise corresponding to the current approval process node. Evaluate each user in the first approval user set according to the preset requirements. For example, the preset requirements may be that for a specific type of financial enterprise, the historical approval passing rate needs to reach a certain percentage, and the average approval duration cannot exceed a certain threshold, etc. By comparing the historical approval data of each user with the preset requirements, screen out the first approval users who meet the requirements. If there are multiple first approval users who meet the requirements, then screen according to the ratio of the historical approval passing rate to the average approval duration, and determine the approval user with the largest ratio as the first approval user.

[0037] Obtain the working status information of the approved users in real time, extract the real-time idle status from it, which can be obtained by integrating with the user office system, task management system, etc. For example, by monitoring the operation activity of the user in the approval system, if there is no operation within a period of time, it is determined as the idle status. According to the real-time idle status, screen out multiple second approval users in the idle state from the second approval user set. Then, sort these idle second approval users according to their job ranks. The sorting method may be based on the numerical value or level identifier corresponding to the previously parsed job rank information, and arranged from high to low or from low to high. The sorting method is not limited here. After the sorting is completed, generate a unique user numerical identifier for each second approval user in the idle state according to the sorting result. This identifier may be generated based on the sorting order. For example, the user numerical identifier of the first user is 1, the second is 2, and so on. This identifier will be used for subsequent random selection operations to ensure the traceability and accuracy of the selection process.

[0038] Generate a random number in a specified format according to the preset rules. For example, set the value range of the random number to be from 1 to the total number of idle second approval users, and it is in integer format. Then, determine the final second approval user through the generated random number and the user numerical identifier of each idle second approval user. For example, if the generated random number is 3, and among the user numerical identifiers generated by sorting according to the job rank, the user corresponding to the numerical value 3 is the second approval user selected to execute this approval task. This method that combines random factors and job rank information not only ensures randomness but also takes into account the job rank differences of users to a certain extent, which helps to fairly and reasonably select approval personnel among idle users.

[0039] Combine the first approval user and the second approval user determined through the above screening process to form multiple approval user nodes corresponding to each approval process node. Set node permissions for each such approval user node, specifically including: obtaining the set of attributed users of the approval user node; setting the node permissions of each such approval user node according to the job rank information corresponding to the set of attributed users. When the set of attributed users of the approval user node is the first approval user set, determine the node permission of the approval user node as the approval permission. When the set of attributed users of the approval user node is the second approval user set, determine the node permission of the approval user node as the supervision permission. After determining the approval user node, send an approval reminder in the form of a message reminder to the corresponding approval user node and send the permission type.

[0040] Through the above technical solutions, by matching detailed process information with organizational node information and conducting multi-dimensional analysis of approval users, it is possible to accurately determine the appropriate approval users corresponding to each approval process node, ensuring that each approval task can be assigned to personnel with relevant experience and capabilities. For example, for the approval process node involving a specific type of financial enterprise, users with good historical approval passing rates and reasonable approval durations in the approval of this type of enterprise will be preferentially selected. Precise matching helps improve the approval quality and reduce errors caused by unprofessional or inexperienced personnel. Considering the real-time idle status of approval users can avoid assigning tasks to busy users, thus achieving efficient utilization of human resources. The approval users are divided into the first approval user set and the second approval user set, and different node permissions (approval permissions and supervision permissions) are set according to the belonging of the sets, establishing a hierarchical approval structure. This structure makes the approval process more hierarchical. Junior users (the first approval user set) can first conduct approval work, while senior users (the second approval user set) use their higher positions and rich experience for supervision, which helps control the approval quality and promptly discover and correct possible problems. In the second approval user set, the final user is determined by rank sorting and random number generation, ensuring the fairness of task assignment. Through the matching method based on process information and organizational node information and the dynamic screening mechanism for approval users, it can flexibly adapt to the changes in financial business. When a new type of financial enterprise or approval process requirement appears, the system can quickly adjust the matching strategy and re-screen the appropriate approval users to ensure that the approval work can keep up with the pace of business development in a timely manner.

[0041] Step S103: Send the information of the materials to be approved to the first approval user nodes with approval permissions, and approve the financial enterprise according to the process information of the approval process nodes to determine the approval result data of each first approval user node in the corresponding approval process node.

[0042] In one embodiment of this specification, all materials related to a specific financial enterprise are extracted from a database or document management system storing information on materials awaiting approval, including business licenses, financial statements, business plans, risk assessment reports, etc. submitted by the financial enterprise, as well as relevant data collected in previous processes, such as enterprise declaration element information, etc. The information is integrated to form a complete data packet of materials awaiting approval. Based on the previously determined approval user nodes and permission settings, the first approval user node with approval authority is identified, and through information such as node identifiers or user IDs, the first approval user node that needs to receive the materials awaiting approval is accurately located. Using an internal messaging mechanism, such as message queues, Web service calls, etc., the integrated data packet of materials awaiting approval is sent to the corresponding first approval user node. During the sending process, the system records information such as the sending time and the sending object for subsequent tracking and auditing. At the same time, in order to ensure the security and integrity of the data, technical means such as encryption and digital signatures may be used.

[0043] When the first approval user node receives the information on materials awaiting approval, it extracts the process information of the corresponding approval process node from the approval process information repository. This information includes approval types (such as qualification review, business review, etc.), approval reference criteria (such as registered capital requirements, business compliance indicators, etc.), and approval operation guides (such as specific contents to be checked, the order of approvals, etc.). The first approval user reviews the materials awaiting approval of the financial enterprise one by one based on the received process information. For example, in the qualification review link, the approval user checks whether the shareholder qualifications of the financial enterprise meet the requirements, including the financial status and credit records of the shareholders; in the business review link, it evaluates whether the business model of the enterprise is feasible and complies with market demands and regulatory requirements. During the review process, the approval user may make relevant markings, record problems, or raise questions in the system. According to the review situation, the first approval user enters the approval result data into the system, including conclusions such as approval, disapproval, or the need to supplement materials, as well as detailed approval opinions and reasons. For example, if it is considered that a certain business of the financial enterprise has compliance risks, the approval user will elaborate on the risk points and relevant bases in the approval opinion. The system conducts preliminary format verification and logical verification on the approval result data to ensure the accuracy and integrity of the data. The approval result data generated by the first approval user node is stored in a dedicated approval result database. When storing, it is associated with the identifier of the financial enterprise, approval process node information, and approval user information, etc., for subsequent query and traceability.

[0044] Through the above technical solution, the approval is carried out according to the process information of the approval process nodes, so that each first approval user node follows the same standards and steps, which can avoid inconsistent approval results caused by subjective factors or operation differences of different approvers; directly send the information of the materials to be approved to the first approval user node with approval authority, avoiding the chaos and delay in the process of material transmission. The accurate information transmission mechanism ensures that the approvers can obtain the required materials in time, thus quickly starting the approval process and improving the overall approval efficiency; assign the approval tasks to the first approval user nodes, realizing the reasonable division of labor in the approval work. Each node focuses on the approval work within its own scope of responsibilities, avoiding duplication or omission of tasks, which helps to speed up the approval speed. Multiple first approval user nodes approve different process nodes in parallel, which can greatly shorten the entire approval cycle.

[0045] Step S104, through the second approval user node with supervision authority, verify the approval result data of the first approval user node to determine the supervision result data of the approval process node, so as to supervise the approval process.

[0046] Through the second approval user node with supervision authority, verify the approval result data of the first approval user node to determine the supervision result data of the approval process node, specifically including: under the trigger of the first approval user node uploading the approval result data, encrypt the node identifier of the first approval user node to determine the first encrypted node identifier; send the first encrypted node identifier and the approval result data to the second approval user node to determine the supervision result data of the approval process node.

[0047] In an embodiment of the present specification, monitor the upload operation of the approval result data of the first approval user node. When the first approval user node completes the approval and submits the result data to the system, the upload behavior is captured by the system as an event. The event listener recognizes the occurrence of the event through a preset interface and protocol, and sends an encryption instruction to the encryption module. After receiving the instruction, the encryption module extracts the encryption key from the key management library. The key may be a symmetric key updated regularly or the private key in the public-private key pair based on the asymmetric encryption system. The encryption module uses a specific encryption algorithm, such as the AES (Advanced Encryption Standard) or RSA (Rivest-Shamir-Adleman) algorithm, to encrypt the node identifier of the first approval user node. During the encryption process, the binary data of the node identifier is converted and scrambled according to the algorithm rules to generate the first encrypted node identifier.

[0048] Pack the first encrypted node identifier and the supervision result data (i.e., the approval result data of the first approval user node). The packing method may adopt a specific data format, such as JSON or XML, to encapsulate the two in a data structure. Then, through the network communication module, using protocols such as HTTP and HTTPS, send the packed data to the second approval user node. During the transmission process, a data verification mechanism, such as CRC (Cyclic Redundancy Check), may be adopted to ensure that the data is not tampered with during transmission. After the network receiving module of the second approval user node receives the data, it first performs an integrity check on the data by calculating the CRC check value again and comparing it with the check value attached by the sender. If the check passes, according to the data format specification, parse the data, extract the first encrypted node identifier and the supervision result data, and store them in different positions in the system temporary buffer for subsequent processing. Send the first encrypted node identifier and the supervision result data to the second approval user node to determine the supervision result data of this approval process node.

[0049] Determine the supervision result data of this approval process node, specifically including: through this second approval user node, match the first encrypted node identifier with the set of encrypted node identifiers with approval permissions preset, and verify the approval permission of the first encrypted node; after the verification passes, verify the supervision result data to generate the supervision result data of this approval process node.

[0050] In an embodiment of this specification, first send the first encrypted node identifier to the second approval user node. The second approval user node reads the set of encrypted node identifiers with approval permissions preset from the system's permission management database. This set stores the encrypted identifiers of all legal approval nodes, and may be stored in data structures such as hash tables or arrays for quick search. Through this second approval user node, compare the received first encrypted node identifier with each element in the set of encrypted node identifiers. If there is an identical item between the first encrypted node identifier and the encrypted identifier in the set of encrypted node identifiers, that is, a matching item is found, it is determined that the first approval user node has legal approval permissions and the permission verification passes; if no matching identifier can be found in the set, the permission verification fails. In the case where the permission verification passes, send the approval result data to the second approval user node.

[0051] Load the verification rules for the regulatory result data in the rule library and display them to the second approval user node. These rules may include data format specifications, approval standard thresholds, logical relationship judgments, etc. For example, for the financial approval results of financial enterprises, the rules may stipulate the reasonable range of the asset-liability ratio, the accuracy requirements for profit calculation, etc. The second approval user verifies the regulatory result data one by one according to the loaded verification rules and submits the verification results item by item. For the data format, check whether it conforms to the preset format template; for the approval standard, compare each indicator in the approval result with the standard threshold; for the logical relationship, verify whether there is a contradiction between the approval conclusion and the approval basis. If the verification results of all items pass, it means that the approval result of the first approval user has passed the verification. When the approval results corresponding to each approval process node pass the verification, the regulatory result data generated according to each approval process node is stored in the approval result database of the system and associated with the corresponding approval process node and financial enterprise information for subsequent query and traceability.

[0052] Through the above technical solution, by encrypting the node identifier of the first approval user node and comparing it with the pre-stored set of legitimate encrypted node identifiers, it is ensured that only the result data uploaded by legitimate approval nodes can enter the subsequent verification process, preventing illegal nodes from impersonating legitimate approval nodes to upload false data, guaranteeing the security and legality of the source of approval data, and reducing the approval risk from the source; requiring the second approval user to verify the regulatory result data one by one and submit the results item by item ensures the comprehensiveness and accuracy of the verification process, avoiding approval mistakes caused by some problems being ignored; loading the verification rules and displaying them to the second approval user node ensures that all approval supervision operations are carried out according to unified standards, avoiding inconsistent verification results caused by personal understanding differences or non-standard operations, and realizing the standardization and standardization of the approval supervision process.

[0053] Through the technical solution of the embodiments of this specification, by receiving approval application information, multiple approval process nodes and their process information are determined, including approval reference criteria, which sets clear and unified standards for the entire approval process, ensuring the consistency and standardization of the approval work and avoiding the randomness and differences caused by human factors; according to the process information of the approval process nodes, multiple corresponding approval user nodes are matched in the regional management platform, which can assign approval tasks to the most suitable personnel, taking into account factors such as the professional skills and experience of different approval users, and realizing the optimal allocation of human resources; reasonable personnel allocation enables the approval work to be started quickly and promoted efficiently. Each approval user node focuses on its own good field, reducing the repeated communication and handover costs caused by personnel mismatch, thus accelerating the entire approval process and meeting the requirements of financial enterprises for the timeliness of approval; a first approval user node with approval authority and a second approval user node with supervision authority are set up to form a two-level approval supervision mechanism. The first approval user node conducts preliminary approval, and the second approval user node verifies the approval result data, double-guaranteeing the accuracy and reliability of the approval result. This multi-level review helps to discover and correct possible approval mistakes and reduce approval risks; through the verification of the second approval user node, problems that may occur in the approval process of the first approval user node can be discovered in time, standardizing the approval behavior and improving the quality of the approval work.

[0054] The embodiments of this specification also provide an approval process supervision device for regional financial enterprises, as Figure 2 shown. The device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above method.

[0055] The embodiments of this specification also provide a non-volatile computer storage medium storing computer-executable instructions, and the computer-executable instructions are set to: execute the above method.

[0056] The embodiments in this specification are all described in a progressive manner. The same or similar parts among the embodiments can be referred to each other, and the key points of each embodiment are the differences from other embodiments. In particular, for the embodiments of the device, equipment, and non-volatile computer storage medium, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments.

[0057] The above description is of specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the acts or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0058] The devices and media provided by the embodiments of this specification correspond one-to-one with the methods. Therefore, the devices and media also have beneficial technical effects similar to those of their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be elaborated here.

[0059] Those skilled in the art should understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0060] This specification is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0061] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction means that implements the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0062] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 steps of the functions specified in one block or multiple blocks.

[0063] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

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

[0065] Computer-readable media includes permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0066] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the presence of another identical element in the process, method, commodity or device comprising the element.

[0067] The above description is only for one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, various changes and modifications can be made to one or more embodiments of this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included within the scope of the claims of this specification.

Claims

1. A method for supervising the approval process of a regional financial enterprise, characterized in that: The method comprises: Receiving approval declaration information of a financial enterprise, and determining a plurality of approval process nodes corresponding to the financial enterprise through the approval declaration information, so as to determine process information of each approval process node, wherein the process information includes an approval reference standard; According to the process information of each approval process node, in the regional management platform, multiple approval user nodes corresponding to each approval process node are matched to set node permissions for each approval user node, wherein the node permissions include approval permissions and supervision permissions; Sending the information of materials to be approved to the first approval user node with approval authority, approving the financial enterprise according to the process information of the approval process node, and determining the approval result data of each of the first approval user nodes in the corresponding approval process node; The approval result data of the first approval user node is verified by the second approval user node with supervision authority, and the supervision result data of the approval process node is determined to supervise the approval process.

2. A method for supervising the approval process of a regional financial enterprise according to claim 1, characterized in that: Determining multiple approval process nodes corresponding to the financial enterprise through the approval declaration information, and determining process information of each approval process node, specifically including: Parsing the approval application information to extract the financial enterprise type and enterprise application element information of the financial enterprise, wherein the enterprise application element information includes any one or more of the business scope element, registered capital element, shareholder information element, business model element and risk management element; Perform a formal review on the enterprise application element information. When the formal review is passed, the information is mapped to a preset approval process template according to the type of financial enterprise and the enterprise application element information to determine a plurality of corresponding approval process nodes, wherein the approval process nodes include any one or more of a qualification review node, a business review node, a risk management review node, a compliance review node, and a financial review node; The process information of each approval process node is determined through the multiple approval process nodes.

3. A method for supervising the approval process of a regional financial enterprise according to claim 1, characterized in that: According to the process information of each approval process node, in the regional management platform, multiple approval user nodes corresponding to each approval process node are matched, specifically including: Acquire organization node information corresponding to a plurality of approval organizations pre-stored in the regional management platform, wherein the organization node information includes approval users and organization approval content associated with each organization node; According to the process information of each approval process node and the organization node information, searching the regional management platform for an approval organization node that matches the process information; The user information of multiple approval users in the approval organization node is obtained to analyze the multiple approval users and determine multiple approval user nodes corresponding to each approval process node.

4. A method for supervising the approval process of a regional financial enterprise according to claim 3, characterized in that: Analyzing the multiple approval users to determine the multiple approval user nodes corresponding to each approval process node specifically includes: According to the rank information in the user information, the plurality of approval users are divided into a first approval user set and a second approval user set, wherein the rank of users in the second approval user set is higher than that in the first approval user set; Obtaining historical approval data and real-time idle status in the user information, wherein the historical approval data includes the historical approval pass rate corresponding to each financial enterprise type, the average approval time corresponding to each financial enterprise type, and the historical approval enterprise type; The first approval user set and the second approval user set are screened respectively by using the historical approval data and the real-time idle status to determine a plurality of approval user nodes corresponding to each approval process node.

5. A method for supervising the approval process of a regional financial enterprise according to claim 4, characterized in that: The first approval user set and the second approval user set are screened by the historical approval data and the real-time idle state to determine a plurality of approval user nodes corresponding to each approval process node, specifically including: Screening multiple first approval users in the first approval user set through the historical approval data to determine a first approval user that meets preset requirements; According to the real-time idle status, a plurality of second approval users in the second approval user set are screened and sorted according to their job levels to generate a user numerical identifier for each of the second approval users; According to the user numerical identifier, a random number in a specified format is generated according to a preset rule, and a second approval user is determined by the random number and the user numerical identifier; A plurality of approval user nodes corresponding to the approval process node are determined through the first approval user and the second approval user.

6. A method for supervising the approval process of a regional financial enterprise according to claim 1, characterized in that: Setting node permissions for each of the approval user nodes specifically includes: Obtaining a user set to which the approval user node belongs; The node authority of each of the approval user nodes is set according to the job grade information corresponding to the belonging user set.

7. A method for supervising the approval process of a regional financial enterprise according to claim 1, characterized in that: The second approval user node with supervision authority verifies the approval result data of the first approval user node to determine the supervision result data of the approval process node, specifically including: When the first approving user node uploads the approval result data, the node identifier of the first approving user node is encrypted to determine a first encrypted node identifier; The first encrypted node identifier and the approval result data are sent to a second approval user node to determine the supervision result data of the approval process node.

8. A method for supervising the approval process of a regional financial enterprise according to claim 7, characterized in that: Determine the supervision result data of the approval process node, specifically including: By using the second approval user node, the first encryption node identifier is matched with a preset set of encryption node identifiers with approval authority, and the approval authority of the first encryption node is verified; After the verification is passed, the supervision result data is verified to generate the supervision result data of the approval process node.

9. A device for monitoring the approval process of a regional financial enterprise, characterized in that: The device comprises: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can perform the method according to any one of claims 1 to 8.

10. A non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer executable instructions are configured to execute the method according to any one of claims 1 to 8.

Images