Account authorization task management method, device, equipment, medium and program product

Abstract

The application discloses a kind of account authorization task management method, device, equipment, medium and program product.The present application relates to the technical field of financial technology.The method comprises: obtaining the material audit result corresponding to target task;If the material audit result meets the account authorization task return condition, the account identifier of the target account to be returned is obtained, and according to the task number of target task, the audit belonging stage of target task and the parent task number corresponding to target task are obtained;According to the audit belonging stage, the account authorization task return node is determined, the account identifier of the target account is matched with the account identifier of the parent task corresponding to the parent task number, to obtain the target parent task, and the target parent task is processed by account authorization task return node.The technical scheme of the present application can reduce time delay and improve the coherence of account authorization management process.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of financial technology, and in particular to a management method, device, equipment, medium and program product of an account authorization task. BACKGROUND

[0002] Since a group company can have member units in different regions, the bank institutions in different regions have accounts of the member units of the group company. If the group company needs to perform account management, such as account query or transfer, on the accounts associated with the member units, the group company needs to initiate an account authorization request to the bank institutions.

[0003] The traditional account authorization management process includes transferring account authorization application materials among the opening bank, the co-bank and the main bank, and needs to go through opening bank audit, main bank audit and main bank audit. In the audit process of the above-mentioned multiple audit stages, if the data audit result of a certain audit stage is that the account authorization application materials are incomplete or the audit is not passed, the member unit needs to re-initiate the account authorization application, so as to re-perform the above-mentioned material flow and data audit and other account authorization management processes based on the new account authorization application materials, resulting in an unavoidable time delay, affecting the processing efficiency of the account authorization application business. In addition, since the re-execution of account management can make the coherence of the entire account authorization management process poor, resulting in information loss or omission, the accuracy and reliability of the audit process are reduced. SUMMARY

[0004] Embodiments of the present application provide a management method, device, equipment, medium and program product of an account authorization task, which can reduce time delay and improve the coherence of the account authorization management process.

[0005] In a first aspect, the embodiments of the present application provide a management method of an account authorization task, comprising:

[0006] obtaining a data audit result corresponding to a target task, the target task representing an account authorization task in a set of account authorization tasks associated with accounts of member units of a group company, wherein the account authorization task is used to transfer account authorization application materials among an opening bank node, a co-bank node and a main bank node;

[0007] If the data review result meets the account authorization task return condition, an account identifier of a target account to be returned is obtained, and a review stage of the target task and a parent task number corresponding to the target task are obtained according to a task number of the target task, wherein the review stage includes a bank of first business review stage, a co-bank review stage and a host bank review stage, and the parent task number represents a number of a parent task of the target task, and the parent task represents an account authorization task associated with the target task in a previous review stage of the target task.

[0008] An account authorization task return node is determined according to the review stage, the account identifier of the target account is matched with an account identifier of a parent task corresponding to the parent task number, a target parent task is obtained, and the target parent task is processed by the account authorization task return node.

[0009] In a second aspect, an embodiment of the present application further provides an account authorization task management device, which comprises:

[0010] A review result obtaining module is configured to obtain a data review result corresponding to a target task, the target task representing an account authorization task in a set of account authorization tasks associated with an account of a member unit of a group company, wherein the account authorization task is used to pass an account authorization application data among a bank of first business node, a co-bank node and a host bank node.

[0011] A number obtaining module is configured to, if the data review result meets an account authorization task return condition, obtain an account identifier of a target account to be returned, and obtain a review stage of the target task and a parent task number corresponding to the target task according to a task number of the target task, wherein the review stage includes a bank of first business review stage, a co-bank review stage and a host bank review stage, and the parent task number represents a number of a parent task of the target task, and the parent task represents an account authorization task associated with the target task in a previous review stage of the target task.

[0012] A task return module is configured to determine an account authorization task return node according to the review stage, match the account identifier of the target account with an account identifier of a parent task corresponding to the parent task number, obtain a target parent task, and process the target parent task by the account authorization task return node.

[0013] In a third aspect, an embodiment of the present application further provides an electronic device, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, and the processor implements the account authorization task management method according to any of the embodiments of the present application when executing the program.

[0014] In a fourth aspect, an embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the account authorization task management method according to any one of the embodiments of the present application.

[0015] In a fifth aspect, an embodiment of the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the account authorization task management method according to any one of the embodiments of the present application.

[0016] In the embodiment of the present application, by obtaining the material audit result corresponding to the target task, if the material audit result meets the account authorization task return condition, the account identifier of the target account to be returned is obtained, and according to the task number of the target task, the audit belonging stage of the target task and the parent task number of the target task are obtained, the account authorization task return node is determined according to the audit belonging stage, the account identifier matching is performed on the parent task number of the target task and the parent task number of the parent task, the target parent task is obtained, and the target parent task is processed through the account authorization task return node. Through the embodiment of the present application, when a problem occurs in the whole account authorization management process, the account authorization task return node of the related audit stage can be returned in time, without restarting the whole account authorization management process. Therefore, the problem of large time delay caused by restarting the whole process is solved, and the problem of incoherent process caused by discarding the previous material audit result due to restarting the whole process is solved. The embodiment of the present application improves the processing efficiency of the account authorization application business, and when a problem occurs in the whole account authorization management process, the account authorization task return node of the related audit stage can be returned in time, the material audit result of the audit stage before the return can be retained, information loss or omission is avoided, and the accuracy and reliability of the audit process are improved. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some embodiments of the present application, and should not be regarded as a limitation to the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.

[0018] Figure 1 A flowchart of an account authorization task management method provided by an embodiment of the present application is shown in the figure.

[0019] Figure 2 A subtask division result diagram in an account authorization task management method provided by an embodiment of the present application is shown in the figure.

[0020] Figure 3A flowchart illustrating another method for managing account authorization tasks provided in an embodiment of the present invention;

[0021] Figure 4 A flowchart illustrating yet another method for managing account authorization tasks provided in an embodiment of the present invention;

[0022] Figure 5 A flowchart illustrating another method for managing account authorization tasks provided in an embodiment of the present invention;

[0023] Figure 6 A schematic diagram of the structure of an account authorization task management device provided in an embodiment of the present invention;

[0024] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0025] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0026] It should be noted that similar reference numerals and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this invention, terms such as "first" and "second" are used only to distinguish descriptions and should not be construed as indicating or implying relative importance. The acquisition, storage, use, and processing of data in the technical solutions of this application all comply with relevant national laws and regulations. It should be noted that in the embodiments of this application, certain existing industry solutions such as software, components, and models may be mentioned. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solutions of this application, and do not imply that the applicant has already used or necessarily used the relevant content of "this solution."

[0027] Figure 1 This is a flowchart illustrating a method for managing account authorization tasks according to an embodiment of the present invention. This embodiment is applicable to corporate business scenarios, particularly a scenario where a group company manages the accounts of its member units. For example, the group company performs operations such as account inquiries or account transfers to its member units. This method can be executed by an account authorization task management device, which can be implemented in software and / or hardware, optionally through an electronic device such as a mobile terminal, PC, or server.

[0028] like Figure 1 As shown, the method includes:

[0029] S110, acquire a material review result corresponding to a target task, the target task representing an account authorization task in a set of account authorization tasks associated with accounts of member units of a group company.

[0030] The account authorization task is used to pass account authorization application materials between an opening bank node, a co-bank node, and a host bank node. The account authorization application materials include materials of a member unit authorizing a group customer to manage its account. Optionally, the account authorization application materials include application materials submitted by the member unit and review materials of a node corresponding to a review stage.

[0031] In the embodiments of the present disclosure, the generation manner of the set of account authorization tasks includes: generating n+m+1 account authorization tasks according to the number n of member units of the group company and the number m of accounts of each member unit, and constructing the set of account authorization tasks according to the n+m+1 account authorization tasks.

[0032] Further, the account authorization task includes an opening bank subtask, a co-bank subtask, and a host bank subtask. The n+m+1 account authorization tasks are generated according to the number n of member units of the group company and the number m of accounts of each member unit, including: generating n co-bank subtasks according to the number n of member units of the group company, generating m opening bank subtasks according to the number m of accounts of each member unit, and generating one host bank subtask.

[0033] Figure 2 A schematic diagram of a subtask division result in a management method of an account authorization task provided by the embodiments of the present disclosure is shown in FIG. 1. Figure 2 As shown in FIG. 1, for a group company including three member units, assuming that the member units include member unit A, member unit B, and member unit C, and each member unit includes three accounts, opening bank subtasks 01-03 are generated for the accounts 001-003 of the member unit A. If the member unit A opens new accounts in the future, the opening bank subtasks will be increased accordingly. Opening bank subtasks 04-06 are generated for the accounts 004-005 of the member unit B. Opening bank subtasks 07-09 are generated for the accounts 007-009 of the member unit C. A co-bank subtask 10 is generated according to the co-bank to which the member unit A belongs. A co-bank subtask 11 is generated according to the co-bank to which the member unit B belongs. A co-bank subtask 12 is generated according to the co-bank to which the member unit C belongs. A host bank subtask 13 is generated according to the host bank to which the group company belongs.

[0034] It should be noted that the opening bank subtask can be a subtask of different bank institutions, a subtask of the same bank institution, or a subtask of part of the same bank institution and part of different bank institutions. The co-bank subtask can be a subtask of different bank institutions, a subtask of the same bank institution, or a subtask of part of the same bank institution and part of different bank institutions.

[0035] By generating at least one subtask corresponding to different audit stages, for each subtask, flexible return can be achieved, and the multi-level and multi-institution account authorization task can be returned to the node corresponding to the relevant audit stage in time when the account authorization task meets the return condition, without the need to restart the entire account authorization management process. The embodiment of the application can be flexibly returned at different levels of the opening bank node, the co-bank node, and the sponsor bank node in the account authorization management process, and can timely adjust the process according to the level of the task and the state of the task.

[0036] Each of the above subtasks includes a subtask and / or a parent task, and a task number can be set for each subtask. The task number of each subtask and the subtask number and the parent task number corresponding to the task number can be stored through a task detail table. For example, the co-bank subtask has a parent-child relationship with the opening bank subtask. Alternatively, the sponsor bank subtask has a parent-child relationship with the co-bank subtask. The opening bank subtask is the parent task of the co-bank subtask, and the co-bank subtask is the parent task of the sponsor bank subtask. Specifically, the task detail table includes a task number, a subtask number, a parent task number, an audit belonging stage, and a task state field. These fields are used to determine the key of the account authorization task return node and the task state.

[0037] With the rapid development of the economy, many group companies establish subsidiaries in many banks in various places as member units of the group company. In order to timely and effectively manage the account situation of each member unit, the group company needs to manage the accounts associated with the member units. In order to realize the management of the member unit accounts, the member units need to provide the account authorization application data required for account authorization to the bank for bank institution audit.

[0038] In the embodiment of the application, the opening bank refers to the account opening institution of the member unit. The co-bank refers to the management institution of the member unit. The sponsor bank refers to the management institution of the group company. For example, the bank institution to which the account of the member unit belongs is the opening bank node. The bank institution to which the account of the group company belongs is the sponsor bank node. The bank institution that manages the account of the member unit is the co-bank node.

[0039] The target task refers to the account authorization task of the node corresponding to the current audit stage. If the current audit stage is handled by the opening bank node, the target task refers to the opening bank subtask. If the current audit stage is handled by the co-bank node, the target task refers to the co-bank subtask. If the current audit stage is handled by the main bank node, the target task refers to the main bank subtask.

[0040] The opening bank subtask is used to deliver the account authorization application data to the co-bank node. If the co-bank subtask receives the account authorization application data and the data audit result delivered by the opening bank subtask of all parent nodes of the co-bank subtask, and the data audit result of the co-bank subtask and the data audit result of each parent node are all passed, the account authorization application data corresponding to each account is delivered to the main bank node. In addition, the audit stage and the task state are modified by the co-bank subtask. If the main bank node receives the account authorization application data and the data audit result delivered by the co-bank subtask of all parent nodes of the main bank subtask, and the data audit result of the main bank subtask and the data audit result of each parent node are all passed, the audit stage and the task state of the account authorization application are modified by the main bank subtask, and a passing notification is sent to the member unit.

[0041] Exemplarily, a data submission operation corresponding to the target task is obtained, and account authorization application data corresponding to the target task is obtained according to the data submission operation, wherein the account authorization application data is used for auditing account authorization. A data audit result of the account authorization application data corresponding to the target task is obtained.

[0042] Since the operation of submitting the account authorization application data by the member user to the opening bank can be considered as a data submission operation, correspondingly, the opening bank node obtains the data submission operation corresponding to the target task, and obtains the account authorization application data corresponding to the target task according to the data submission operation. However, the operation personnel associated with the target task in the opening bank audits the account authorization operation and inputs the audit result to the electronic device of the opening bank, so as to realize that the electronic device obtains the data audit result of the account authorization application data corresponding to the target task.

[0043] Optionally, obtaining the data audit result corresponding to the target task can further include the following steps:

[0044] The account authorization application data sent by the parent task of the target task is obtained as the account authorization application data corresponding to the target task, wherein the account authorization application data is used for auditing account authorization. A data audit result of the account authorization application data corresponding to the target task is obtained.

[0045] If the target task is a co-bank sub-task or a host bank sub-task, the account authorization application data is transferred from the opening bank node to the co-bank node or from the co-bank node to the host bank node accordingly, and the account authorization application data sent by the parent task of the target task is obtained as the account authorization application data corresponding to the target task. However, the operation personnel associated with the target task in the co-bank or the host bank audits the account authorization operation and inputs the audit result into the electronic device of the co-bank or the host bank, so that the electronic device obtains the data audit result of the account authorization application data corresponding to the target task.

[0046] The member unit submits an account authorization application to the opening bank, and the account authorization application includes account authorization application data. The account authorization application is audited, stamped and delivered by the opening bank, the co-bank and the host bank. When the authorized relationship of the member unit changes or one of the audit agencies has objections to the audit result of the previous level, the account authorization application is triggered to be returned to the audit agency of the previous level. Alternatively, if the audit agency of the previous level is a task jointly executed by multiple subjects, it needs to be returned to multiple process execution subjects. For example, it may be returned to the audit subject of the co-bank by the host bank, and then returned to the audit subject of the opening bank by the co-bank. Through the multi-level return mode of the task, the accuracy and integrity of the entire account authorization management process are ensured, the smooth progress of the account authorization management is ensured, and the automation and centralized management of the entire account authorization management process are realized.

[0047] S120, if the data audit result meets the account authorization task return condition, obtaining the account identifier of the target account to be returned, and according to the task number of the target task, obtaining the audit belonging stage of the target task and the parent task number corresponding to the target task.

[0048] The audit belonging stage includes the opening bank audit stage, the co-bank audit stage and the host bank audit stage, the parent task number represents the number of the parent task of the target task, and the parent task represents the account authorization task associated with the target task in the previous audit stage.

[0049] In the embodiments of the present disclosure, the account authorization task return condition can refer to a condition for judging whether the account authorization task needs to be returned. The account authorization task return condition is used to determine whether to trigger the return of the account authorization task.

[0050] Exemplarily, the account authorization task return condition includes at least one of the following:

[0051] The account authorization application data has at least one of the following: error information, missing information or incomplete information; the node corresponding to the current audit stage has objections to the data audit result of the node corresponding to the previous audit stage; the account authorization task audit fails.

[0052] In some embodiments, for the co-sponsor bank subtask, if the data audit result shows that there is one or more of the following errors in the account authorization application data, such as errors, omissions, or incomplete information, the opening bank subtask associated with the co-sponsor bank subtask is returned. Or, for the main sponsor bank subtask, if the data audit result shows that there is one or more of the following errors in the account authorization application data, such as errors, omissions, or incomplete information, the co-sponsor bank subtask associated with the main sponsor bank subtask is returned. It should be noted that if the data audit result meets the account authorization task return condition, the account corresponding to the current data audit result can be taken as a target account, and the account identifier of the target account is obtained. And, according to the audit belonging stage of the target task and the parent task number corresponding to the target task. Then, the account authorization task return node is determined by the audit belonging stage, and the parent task to which the task is returned is determined by matching the account identifier of the target account with the account identifier of the parent task. The account identifier can be the account number of the member unit's returned account.

[0053] In other embodiments, for the co-sponsor bank subtask, if the co-sponsor bank node objects to the audit result of the account authorization application data of the target account of the opening bank node, the opening bank subtask associated with the co-sponsor bank subtask is returned. For the main sponsor bank subtask, if the main sponsor bank node objects to the audit result of the account authorization application data of the target account of the co-sponsor bank node, the co-sponsor bank subtask is returned.

[0054] In some embodiments, for the co-sponsor bank subtask, if the co-sponsor bank node fails to pass the audit of the account authorization application data, the opening bank needs to further supplement or modify the account authorization application data, the opening bank subtask associated with the co-sponsor bank subtask is returned. For the main sponsor bank subtask, if the main sponsor bank node fails to pass the audit of the account authorization application data, the co-sponsor bank needs to further supplement or modify the account authorization application data, the co-sponsor bank subtask associated with the main sponsor bank subtask is returned.

[0055] For example, if the data audit result meets the account authorization task return condition, the account identifier of the target account to be returned by the task is obtained, and according to the task number of the target task, the audit belonging stage of the target task and the parent task number corresponding to the target task are obtained, including:

[0056] If the data audit result meets the account authorization task return condition, the account corresponding to the current data audit result is taken as a target account to be returned by the task, and the account identifier of the target account is obtained. And, according to the task number of the target task, the task number field of the task detail table is queried to obtain the task detail information corresponding to the target task. The task detail information includes account identifier, audit belonging stage, and parent task number, etc.

[0057] Specifically, target column data corresponding to the task number of the target task is queried from column data corresponding to the task number field of the task details table. Row data of a row where the target column data is located is taken as task details information corresponding to the target task. Then, according to the intersection of the row data of the row where the target column data is located and the audit belonging stage field and the parent task number field, information such as the audit belonging stage and the parent task number is determined.

[0058] It should be noted that the node corresponding to each audit stage passes in S130 the account authorization task return node according to the node corresponding to the previous audit stage, determines the account authorization task return node according to the audit belonging stage, matches the account identifier of the target account with the account identifier of the parent task corresponding to the parent task number, obtains the target parent task, and processes the target parent task through the account authorization task return node.

[0059] Among them, the account authorization task return node refers to the node corresponding to the audit stage to which the task is returned. In the embodiment of the disclosure, the account authorization task return node includes a bank node and / or a co-bank node. Specifically, the subtask returned by the host bank is first returned to the co-bank for processing, and if the co-bank audit is not passed, the task will be further returned to the bank. The subtask returned by the co-bank is returned to the bank for processing.

[0060] Since the task details table can obtain task details information, and the task details information includes the audit belonging stage and the account identifier, etc., the node corresponding to the previous audit stage of the current audit belonging stage is taken as the account authorization task return node.

[0061] Specifically, if the current audit belonging stage is processed by the host bank node, since the node corresponding to the previous audit stage of the current audit belonging stage is the co-bank node, it is determined that the account authorization task return node is the co-bank node. If the current audit belonging stage is processed by the co-bank node, since the node corresponding to the previous audit stage of the current audit stage is the bank node, it is determined that the account authorization task return node is the bank node.

[0062] The task details table is queried according to the parent task number, and the account identifier of the parent task corresponding to the parent task number is obtained. Since the parent task of the target task can be more than one, the account identifier of the target account needs to be matched with the account identifier of each parent task, and the parent task with the same account identifier as the account identifier of the target account is taken as the target parent task. The target parent task is processed through the account authorization task return node.

[0063] The task of the related technology needs to restart the entire account authorization management process, including resubmitting the account authorization application, re-auditing, and re-transferring, etc. steps, resulting in an unavoidable time delay, affecting the timeliness and efficiency of business processing. The embodiment of the present application does not need to restart the entire account authorization process, can return the task to the relevant audit node, shorten the time delay, improve the timeliness and efficiency of business processing. In addition, it also saves the human resources of resubmitting the audit and re-auditing. Since restarting the entire account authorization management process is equivalent to completely discarding the previous audit results and starting a new audit process, the coherence of the entire process is poor, which may cause information loss or omission, reducing the accuracy and reliability of the audit process.

[0064] Exemplarily, the target parent task is processed by the account authorization task return node, including:

[0065] Obtaining a matter list of the account authorization task return node, wherein the matter list includes task information of an account authorization task to be processed by the account authorization task return node.

[0066] Inserting the task information of the target parent task into the matter list, and marking the target parent task in the matter list with set identification information, and triggering processing of the target parent task based on the matter list.

[0067] Specifically, if the account authorization task return node is a bank opening node, obtaining a matter list of the bank opening corresponding to the target account, the matter list including task information of an account authorization task to be processed in the bank opening. Wherein, the task information includes task number and task state, etc. If the account authorization task return node is a co-bank node, obtaining a matter list of the co-bank corresponding to the target account, the matter list including task information of an account authorization task to be processed in the co-bank.

[0068] Since the target parent task is a child task that has been processed by the account authorization task return node, but due to task return, the target parent task needs to be inserted into the matter list, and the target parent task is marked in the matter list with set identification information to remind the operator to process the returned child task.

[0069] Wherein, the set identification information can include one or more of highlighting, a specific color as a background color or a text color, and text flashing, etc.

[0070] Optionally, the task change log table can be queried according to the target parent task number to obtain the operator corresponding to the target parent task of the account authorization task return node. The operator of the account authorization task return node can be notified by short message or email, etc. to process the returned child task in time. Optionally, the notification content includes the target parent task number, the return reason, and the operation to be executed, etc.

[0071] Optionally, the task return information corresponding to the account authorization task is stored through a task change log, wherein the task return information includes operation time, operator, change type and return reason. The task return information is stored through the task change log, so as to facilitate auditing and problem tracing.

[0072] The embodiment of the present application can return the account authorization task to the account authorization task return node of the relevant audit stage in time when a problem occurs in the entire account authorization management process, without restarting the entire account authorization management process. Thus, the problem of time delay caused by restarting the entire process is solved, and the problem of incoherent process caused by discarding the previous material audit result due to restarting the entire process is solved. The embodiment of the present application improves the processing efficiency of the account authorization application business, and can keep the material audit result of the previous audit stage before returning, avoid information loss or omission, and improve the accuracy and reliability of the audit process.

[0073] Figure 3 Another flowchart of the account authorization task management method provided by the embodiment of the present application is provided. The embodiment of the present application specifically limits the audit belonging stage of the target task and the acquisition method of the parent task number corresponding to the target task on the basis of the above-mentioned embodiments.

[0074] As shown in Figure 3 , the method comprises:

[0075] S310, obtaining a material audit result corresponding to a target task, the target task representing an account authorization task in a set of account authorization tasks associated with an account of a member unit of a group company.

[0076] The embodiment of the present application can obtain the account authorization application material corresponding to the target task according to the material submission operation corresponding to the target task, and then obtain the material audit result of the account authorization application material corresponding to the target task. Alternatively, the account authorization application material transmitted by the parent task of the target task can also be obtained, and then the material audit result of the account authorization application material corresponding to the target task is obtained.

[0077] S320, if the material audit result meets the account authorization task return condition, obtaining an account identifier of a target account to be returned, and querying a task detail table according to a task number of the target task to obtain an audit belonging stage of the target task and the parent task number.

[0078] The task specification table includes a task number, a subtask number, a parent task number, an audit belonging stage, an account identifier, and a task state of the account authorization task.

[0079] Illustratively, if the data audit result meets the account authorization task return condition, the task specification table is queried according to the task number of the target task to obtain the audit belonging stage and at least one parent task number of the target task.

[0080] S330, the node corresponding to the previous audit stage of the audit belonging stage is taken as an account authorization task return node.

[0081] S340, if the account identifier of the parent task corresponding to the parent task number matches the account identifier of the target account, the parent task is taken as a target parent task.

[0082] For the case that the target task corresponds to at least two parent tasks, the task specification table is queried by using each parent task number to obtain the account identifier of each parent task. Then, the account identifier of the target account is used to traverse the account identifiers of the parent tasks, and the parent task whose account identifier matches the account identifier of the target account is taken as a target parent task.

[0083] For the case that the target task corresponds to one parent task, the parent task corresponding to the target task is taken as a target parent task.

[0084] S350, according to the task state of the target task, the task state of the target parent task is modified to be in return processing, and the audit belonging stage is modified to be the audit stage corresponding to the account authorization task return node.

[0085] Illustratively, the task state of the target task in the task specification table is modified to be in audit, and the task state of the target parent task is modified to be in return processing. In addition, the audit belonging stage is modified to be the audit stage corresponding to the account authorization task return node.

[0086] If the co-sponsor bank finds problems and needs to return to the opening bank, the parent task number of the co-sponsor bank sub-task is used to query the task detail table to obtain the corresponding opening bank sub-task, and the task state of the opening bank sub-task is updated to be under review. Similarly, if the main sponsor bank finds that the account authorization application of a certain account exists problems, the task number of the main sponsor bank sub-task is used to query the co-sponsor bank sub-task corresponding to the account, and the state of the co-sponsor bank sub-task is updated to be under review. Then, the task number of the co-sponsor bank sub-task is used to query the opening bank sub-task corresponding to the account, and the task state of the opening bank sub-task is updated to be under review. Specifically, when the task is returned to the opening bank, the task state of the co-sponsor bank sub-task is modified to be in return processing, and the audit state of the opening bank task is updated to be under review. When the task is returned to the co-sponsor bank, the task state of the main sponsor bank sub-task is modified to be in return processing, and the task state of the co-sponsor bank sub-task is modified to be under review.

[0087] Referring to Figure 2 Assuming that the audit result of the co-sponsor bank sub-task corresponding to the account 002 of the member unit A is not passed, the parent task numbers of the opening bank sub-task 01, the opening bank sub-task 02 and the opening bank sub-task 03 are obtained by querying the task detail table according to the co-sponsor bank sub-task 10. The account identifiers of the parent tasks, which are the account 001 of the member unit A, the account 002 of the member unit A and the account 003 of the member unit A, are obtained by querying the task detail table according to the parent task numbers. The target parent task is the opening bank sub-task 02 by matching the account identifiers of the parent tasks with the account identifier of the target account (i.e. the account 002 of the member unit A). It can also be obtained from the co-sponsor bank sub-task 10 that the audit belongs to the co-sponsor bank processing by querying the task detail table. Thus, the task state of the co-sponsor bank sub-task 10 is updated to be in return processing, the task state of the opening bank sub-task 02 is updated to be under review, and the audit belongs to the opening bank.

[0088] S360, obtaining a matter list of the account authorization task return node.

[0089] The matter list includes the task information of the account authorization task to be processed of the account authorization task return node.

[0090] For example, assuming that the audit result of the co-sponsor bank sub-task corresponding to the account 002 of the member unit A is not passed, the task state of the opening bank sub-task 02 is updated to be under review in the matter list to ensure that the opening bank sub-task 02 is displayed in the to-do task list of the corresponding operator of the opening bank.

[0091] S370, inserting the task information of the target parent task into the matter list, marking the target parent task with setting identification information in the matter list, and triggering processing of the target parent task based on the matter list.

[0092] Assuming that the sub-task of the co-sponsor bank corresponds to the audit result of the account 002 of the member unit A, and the audit result is not passed, the opening bank can also notify the corresponding operator to handle the return task of the account 002 through a short message or an email and the like.

[0093] Optionally, the detailed information of the return task of the account 002 is recorded in the task change log, including the return time, the return reason, the operator of the previous node and the like.

[0094] S380, if the audit result does not meet the account authorization task return condition, and the audit belongs to the stage that is not processed by the sponsor bank node, the account authorization application data is transmitted to the node corresponding to the next audit stage of the audit belongs to the stage through the target task.

[0095] S390, if the audit result does not meet the account authorization task return condition, and the audit belongs to the stage that is processed by the sponsor bank node, the notification of the audit passing of the account authorization task is sent to the relevant personnel of the member unit.

[0096] Figure 4 Another flowchart of the account authorization task management method provided by the embodiment of the application is provided. The member unit initiates a task application to the opening bank 410. The task is an account authorization task. The opening bank performs task acceptance and audit 420. If the audit is passed, the task is transferred to the co-sponsor bank. The co-sponsor bank performs task acceptance and audit 430. If the audit is passed, the task is transferred to the sponsor bank. If the audit is not passed, the execution opening bank performs task acceptance and audit 420. The sponsor bank performs task acceptance and audit 440. If the audit is passed, the notification of the audit passing of the account authorization task is sent to the member unit 450. If the audit is not passed, the execution co-sponsor bank performs task acceptance and audit 440.

[0097] The embodiment of the application maintains the task number, the sub-task number, the parent task number, the audit belonging stage, the account identifier and the task state of each sub-task through the task detail table, queries the task detail table based on the task number of the target task, obtains the audit belonging stage and at least one parent task number of the target task. According to the parent task number, the account identifier of the parent task is obtained by querying the task detail table, the account identifier of the parent task is matched with the account identifier of the target account, and the target parent task is obtained. Then, the task state of the target task in the task detail table is modified to be under audit, the task state of the target parent task is modified to be in return processing, the audit belonging stage is modified to be the audit stage corresponding to the account authorization task return node. The embodiment of the application realizes flexible return operation between different levels such as the opening bank node, the co-sponsor bank node and the sponsor bank node, and can adjust the audit process according to the task state and the audit belonging level.

[0098] Figure 5 A flowchart of another account authorization task management method provided by an embodiment of the present application is shown. The embodiment of the present application is based on the above-mentioned embodiments, and additionally limits the transmission mode of the account authorization application data.

[0099] As shown in Figure 5 , the method comprises:

[0100] S510, obtaining an audit result of data corresponding to a target task, the target task representing an account authorization task in a set of account authorization tasks associated with an account of a member unit of a group company.

[0101] The account authorization task is used to transmit account authorization application data between an opening bank node, a co-bank node and a main bank node.

[0102] S520, if the audit result of the data meets account authorization task return conditions, obtaining an account identifier of a target account to be returned, and according to a task number of the target task, obtaining an audit belonging stage of the target task and a parent task number corresponding to the target task.

[0103] The audit belonging stage includes an opening bank audit stage, a co-bank audit stage and a main bank audit stage, the parent task number represents a number of a parent task of the target task, and the parent task represents an account authorization task associated with the target task in a previous audit stage of the target task.

[0104] S530, determining an account authorization task return node according to the audit belonging stage, matching the account identifier of the target account with an account identifier of a parent task corresponding to the parent task number to obtain a target parent task, and processing the target parent task through the account authorization task return node.

[0105] S540, obtaining modified account authorization application data, and sending the modified account authorization application data to a node associated with the target task through the target parent task.

[0106] The modified account authorization application data can be account authorization application data resubmitted by the member unit, or the account authorization application data can be audit data after the account authorization task return node re-audits the account authorization application data.

[0107] Illustratively, an opening bank sub-node obtains a data submission operation, obtains modified account authorization application data according to the data submission operation, and if the opening bank sub-node audits the modified account authorization application data and passes, sends the modified account authorization application data to a node associated with the target task.

[0108] Optionally, the host bank sub-node obtains the audit data of the re-audit account authorization application data of the co-bank sub-node, and if the host bank sub-node passes the audit data, the member unit account authorization application is informed to pass the audit, otherwise, the target task is returned.

[0109] S550, judging whether the parent task corresponding to the target task is completed data transmission operation, if yes, executing S560, otherwise executing S570.

[0110] Exemplarily, if the target task represents a co-bank sub-task, the co-bank sub-task receives all the account authorization application data transmitted by the corresponding bank sub-task, then S560 is executed.

[0111] Optionally, if the target task represents a host bank sub-task, the host bank sub-task receives all the account authorization application data transmitted by the corresponding co-bank sub-task, then S560 is executed.

[0112] S560, modifying the task state of the target task to audit processing, and modifying the audit belonging stage to the audit stage corresponding to the node associated with the target task.

[0113] If the data needs to be retransmitted, for example, a certain bank sub-task corresponding to the co-bank sub-task needs to retransmit the account authorization application data, if the task state of the target task and the audit belonging stage have been modified at this time, process errors may occur.

[0114] S570, waiting for a set time and returning to execute S550.

[0115] The embodiment of the application obtains the modified account authorization application data, and sends the modified account authorization application data to the node associated with the target task through the target parent task, only when all the parent tasks corresponding to the target task are completed data transmission operation, the task state of the target task is modified to audit processing, and the audit belonging stage is modified to the audit stage corresponding to the node associated with the target task, avoiding process execution errors caused by state mis-modification.

[0116] Figure 6 A structural schematic diagram of an account authorization task management device provided by the embodiment of the application is provided. The device can be realized in the form of software and / or hardware, and can be realized by an electronic device, which can be a mobile terminal, a PC terminal or a server, etc.

[0117] As shown in the figure, the device comprises an audit result obtaining module 610, a number obtaining module 620 and a task returning module 630. Figure 6

[0118] ​The audit result obtaining module 610 is configured to obtain an account authorization application material corresponding to a target task, the target task representing an account authorization task in a set of account authorization tasks associated with an account of a member unit of a group company, wherein the account authorization task is used to transfer the account authorization application material between an opening bank node, a co-bank node and a main bank node.

[0119] The number obtaining module 620 is configured to, if the audit result meets account authorization task return conditions, obtain an account identifier of a target account to be returned, and obtain an audit stage of the target task and a parent task identifier corresponding to the target task according to a task number of the target task, wherein the audit stage includes an opening bank audit stage, a co-bank audit stage and a main bank audit stage, the parent task identifier represents a number of a parent task of the target task, and the parent task represents an account authorization task associated with the target task in a previous audit stage of the target task.

[0120] The task return module 630 is configured to determine an account authorization task return node according to the audit stage, match the account identifier of the target account with an account identifier of a parent task corresponding to the parent task identifier, obtain a target parent task, and process the target parent task through the account authorization task return node.

[0121] Optionally, the account authorization task set is generated in the following manner:

[0122] n+m+1 account authorization tasks are generated according to the number n of member units of the group company and the number m of accounts of each member unit, and the account authorization task set is formed according to the n+m+1 account authorization tasks.

[0123] Further, the account authorization task includes an opening bank subtask, a co-bank subtask and a main bank subtask.

[0124] The n+m+1 account authorization tasks are generated according to the number n of member units of the group company and the number m of accounts of each member unit, and the account authorization task set is formed according to the n+m+1 account authorization tasks.

[0125] n co-bank subtasks are generated according to the number n of member units of the group company, m opening bank subtasks are generated according to the number m of accounts of each member unit, and one main bank subtask is generated.

[0126] Optionally, the audit result obtaining module 610 is specifically configured to:

[0127] The account authorization application material corresponding to the target task is obtained according to the material submission operation, and the account authorization application material is used for auditing account authorization.

[0128] obtain an audit result of the account authorization application data corresponding to the target task.

[0129] Optionally, the audit result obtaining module 610 is specifically configured to:

[0130] obtain account authorization application data sent by a parent task of the target task as the account authorization application data corresponding to the target task, wherein the account authorization application data is used for auditing account authorization.

[0131] obtain an audit result of the account authorization application data corresponding to the target task.

[0132] Optionally, the account authorization task return condition includes at least one of the following:

[0133] the account authorization application data has at least one of error information, missing information, or incomplete information;

[0134] a node corresponding to a current audit stage has an objection to an audit result of a node corresponding to a previous audit stage;

[0135] the account authorization task fails the audit.

[0136] Optionally, the number obtaining module 620 is specifically configured to:

[0137] query a task details table according to a task number of the target task to obtain an audit belonging stage of the target task and the parent task number, wherein the task details table includes a task number, a sub-task number, a parent task number, an audit belonging stage, an account identifier, and a task state of the account authorization task.

[0138] Optionally, the task return module 630 is specifically configured to:

[0139] set a node corresponding to a previous audit stage of the audit belonging stage as an account authorization task return node;

[0140] if an account identifier of a parent task corresponding to the parent task number matches an account identifier of the target account, set the parent task as a target parent task;

[0141] modify a task state of the target task according to the target task state to be under audit, modify a task state of the target parent task to be in return processing, modify the audit belonging stage to be an audit stage corresponding to the account authorization task return node, and process the target parent task through the account authorization task return node.

[0142] Further, the processing of the target parent task through the account authorization task return node includes:

[0143] Obtaining a list of matters of the account authorization task return node, wherein the list of matters includes task information of the account authorization task to be processed of the account authorization task return node;

[0144] Inserting the task information of the target parent task into the list of matters, and marking the target parent task in the list of matters by using setting identification information, and triggering processing of the target parent task based on the list of matters.

[0145] Optionally, the method further comprises:

[0146] A return information saving module is configured to save task return information corresponding to the account authorization task through a task change pipeline table, wherein the task return information includes operation time, operation personnel, change type and return reason.

[0147] Optionally, the method further comprises:

[0148] A state updating module is configured to, after processing the target parent task through the account authorization task return node, obtain modified account authorization application materials, send the modified account authorization application materials to the target task associated node through the target parent task, judge whether the parent task corresponding to the target task has completed the material transmission operation, if yes, modify the task state of the target task to be in audit processing, and modify the audit belonging stage to the audit stage corresponding to the target task associated node.

[0149] The account authorization task management device provided by the embodiment of the application can execute the account authorization task management method provided by any embodiment of the application, and has the function modules and beneficial effects corresponding to the execution method.

[0150] Figure 7 A structural schematic diagram of an electronic device is provided for the embodiment of the application. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, and other suitable computers. The components shown here, their connections, and their functions, are merely examples and are not intended to limit the implementations described and / or claimed in this document.

[0151] As Figure 7As shown, the electronic device 10 includes at least one processor 11, and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., connected to the at least one processor 11 in communication. The memory stores a computer program executable by the at least one processor 11, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or loaded from the storage unit 18 into the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0152] A plurality of components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc., an output unit 17, such as various types of displays, a speaker, etc., a storage unit 18, such as a magnetic disk, an optical disk, etc., and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.

[0153] The processor 11 can be various general and / or special-purpose processing components having processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 performs various methods and processes described above, such as a management method of an account authorization task.

[0154] In some embodiments, a management method of an account authorization task can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform a management method of an account authorization task by any other appropriate means, such as by means of firmware.

[0155] The various embodiments of the systems and techniques described above can be implemented in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a load programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0156] Computer programs used to implement the processes of the application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program, when executed by the processor, implements the functions / acts specified in the flowcharts and / or block diagrams. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine as part of a standalone software package, or entirely on a remote machine or server.

[0157] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store computer programs for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0158] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0159] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), blockchain network, and the Internet.

[0160] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. A server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.

[0161] The embodiments of the present application further provide a computer program product, comprising a computer program which, when executed by a processor, implements the account authorization task management method provided by any of the embodiments of the present application.

[0162] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0163] It is to be understood that the above description is merely a preferred embodiment of the application and the applied technical principles. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, modifications and substitutions can be made without departing from the scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments, and can include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims

1. A method for managing account authorization tasks, characterized in that, include: Obtain the document review results corresponding to the target task. The target task represents the account authorization task in the account authorization task set associated with the account of the group company's member unit. The account authorization task is used to transmit account authorization application materials between the account opening bank node, the cooperating bank node, and the lead bank node. If the document review result meets the conditions for returning the account authorization task, then obtain the account identifier of the target account to be returned, and, based on the task number of the target task, obtain the review stage to which the target task belongs and the parent task number corresponding to the target task. The review stage to which the target task belongs includes the account opening bank review stage, the cooperating bank review stage and the lead bank review stage. The parent task number represents the number of the parent task of the target task. The parent task represents the account authorization task associated with the target task in the previous review stage of the target task. Based on the stage of the review, the account authorization task return node is determined. The account identifier of the target account is matched with the account identifier of the parent task corresponding to the parent task number to obtain the target parent task. The target parent task is then processed through the account authorization task return node.

2. The method according to claim 1, characterized in that, The methods for generating the account authorization task set include: Based on the number of member units n of the group company and the number of accounts m of each member unit, n+m+1 account authorization tasks are generated, and the account authorization task set is formed by the n+m+1 account authorization tasks.

3. The method according to claim 2, characterized in that, The account authorization task includes sub-tasks from the opening bank, sub-tasks from the cooperating bank, and sub-tasks from the lead bank; The process of generating n+m+1 account authorization tasks based on the number of member units n of the group company and the number of accounts m of each member unit includes: Based on the number of member units n of the group company, generate n cooperating bank sub-tasks, based on the number of accounts m of each member unit, generate m account opening bank sub-tasks, and generate one lead bank sub-task.

4. The method according to claim 1, characterized in that, The process of obtaining the document review results corresponding to the target task includes: Obtain the data submission operation corresponding to the target task, and obtain the account authorization application data corresponding to the target task based on the data submission operation, wherein the account authorization application data is used to review account authorization; Obtain the document review results of the account authorization application materials corresponding to the target task.

5. The method according to claim 1, characterized in that, The process of obtaining the document review results corresponding to the target task includes: Obtain the account authorization application information sent by the parent task of the target task, and use it as the account authorization application information corresponding to the target task, wherein the account authorization application information is used to review account authorization; Obtain the document review results of the account authorization application materials corresponding to the target task.

6. The method according to claim 1, characterized in that, The conditions for revoking the account authorization task include at least one of the following: The account authorization application materials contain at least one of the following: incorrect information, missing information, or incomplete information; The node corresponding to the current review stage has objections to the document review results of the node corresponding to the previous review stage; The account authorization task review failed.

7. The method according to claim 1, characterized in that, The step of obtaining the review stage of the target task and the parent task number corresponding to the target task based on the task number of the target task includes: The task details table is queried based on the task number of the target task to obtain the review stage of the target task and the parent task number. The task details table includes the task number, sub-task number, parent task number, review stage, account identifier, and task status of the account-authorized task.

8. The method according to claim 7, characterized in that, The step of determining the account authorization task return node based on the stage of the review, matching the account identifier of the target account with the account identifier of the parent task corresponding to the parent task number to obtain the target parent task, and processing the target parent task through the account authorization task return node includes: The node corresponding to the previous review stage to which the review belongs is used as the account authorization task return node; If the account identifier of the parent task corresponding to the parent task number matches the account identifier of the target account, then the parent task is taken as the target parent task. The task status of the target task is changed to pending review, the task status of the target parent task is changed to being processed for return, the review stage is changed to the review stage corresponding to the account authorization task return node, and the target parent task is processed through the account authorization task return node.

9. The method according to claim 1 or 8, characterized in that, The process of handling the target parent task through the account-authorized task rollback node includes: Obtain the item list of the account authorization task return node, wherein the item list includes task information of the pending account authorization tasks of the account authorization task return node; Insert the task information of the target parent task into the item list, and mark the target parent task in the item list with the set identification information, and trigger the processing of the target parent task based on the item list.

10. The method according to claim 1, characterized in that, Also includes: The task change log is used to save the task return information corresponding to the account-authorized task. The task return information includes the operation time, operator, change type and return reason.

11. The method according to claim 1, characterized in that, After processing the target parent task through the account authorization task rollback node, the process further includes: Obtain the modified account authorization application information, and send the modified account authorization application information to the node associated with the target task through the target parent task; Determine whether all parent tasks corresponding to the target task have completed the data transfer operation; If so, the task status of the target task will be changed to "under review processing", and the review stage will be changed to the review stage corresponding to the node associated with the target task.

12. A management device for account authorization tasks, characterized in that, include: The review result acquisition module is used to acquire the review results of the materials corresponding to the target task. The target task represents the account authorization task in the account authorization task set associated with the account of the group company's member unit. The account authorization task is used to transmit account authorization application materials between the account opening bank node, the cooperating bank node and the lead bank node. The number acquisition module is used to acquire the account identifier of the target account to be returned if the data review result meets the conditions for returning the account authorization task, and to acquire the review stage of the target task and the parent task number corresponding to the target task according to the task number of the target task. The review stage includes the account opening bank review stage, the cooperating bank review stage and the lead bank review stage. The parent task number represents the number of the parent task of the target task. The parent task represents the account authorization task associated with the target task in the previous review stage of the target task. The task return module is used to determine the account authorization task return node according to the stage of the review, match the account identifier of the target account with the account identifier of the parent task corresponding to the parent task number to obtain the target parent task, and process the target parent task through the account authorization task return node.

13. An electronic device, characterized in that, The system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, it implements a management method for account authorization tasks as described in any one of claims 1-11.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the management method for account authorization tasks as described in any one of claims 1-11.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the management method for account authorization tasks as described in any one of claims 1-11.

Images