WO2018205716A1

WO2018205716A1 - Method and apparatus for managing user account

Info

Publication number: WO2018205716A1
Application number: PCT/CN2018/077667
Authority: WO
Inventors: 曾芳
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-05-08
Filing date: 2018-02-28
Publication date: 2018-11-15
Also published as: CN107784480A

Abstract

Provided are a method and apparatus for managing a user account. The method comprises: acquiring a created user account, with a level attribute and a limit amount attribute being added to the user account; acquiring a user level set in the level attribute; acquiring a limit amount set in the limit amount attribute, the limit amount corresponding to the user level; receiving a fund amount input via the user account; querying the user level corresponding to the user account, and reading the limit amount corresponding to the user level; and determining whether the fund amount is less than or equal to the limit amount, and if the fund amount is less than or equal to the limit amount, determining a generated check result to be valid. In the present application, a level attribute and a limit amount attribute are set in combination with practical conditions, and whether the bonus and deduction of a user account exceed a limit amount of a corresponding level is detected, and thus, where flexibility is ensured to the greatest possible degree, the risk caused by reasons such as a fund amount input error is reduced.

Description

Method and device for managing user account

This application claims the priority of the Chinese Patent Application entitled "A Method and Apparatus for Managing User Accounts", filed on May 8, 2017, with the application number of 201710318225.5, the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of the Internet, and in particular, to a method and apparatus for managing a user account.

Background technique

The management mode of the traditional insurance company, especially the management method of the salesman is relatively backward. The information of each salesperson is often recorded by means of an Excel spreadsheet, for example, the information of each salesperson is in a row in the table, and one column is recorded in each column. The amount of the payment, according to the information recorded in the form, can be managed by the salesperson.

Due to the large number of salesmen, this manual management method is prone to errors. For example, the salesperson's absence deductions and bonuses, etc. are added to the form manually. In the case of a large amount of business, manual operation errors will inevitably occur.

In view of the high error rate of the amount of money in the prior art, there is currently no ideal solution in the industry.

technical problem

In view of this, the embodiment of the present application provides a method and an apparatus for managing a user account, so as to solve the problem that the error rate of the amount of money entered in the prior art is high.

Technical solution

The method for managing a user account provided by the application includes:

Obtain the created user account, and add hierarchical attributes and limit metality to the user account;

Get the user level set in the hierarchy attribute;

Obtain a limit amount set in the limit metality, the limit amount corresponds to the user level; receive the amount of money input through the user account;

Query the user level corresponding to the user account, and read the limit amount corresponding to the user level;

Determine whether the amount of the payment is less than or equal to the limit amount. If the amount of the payment is less than or equal to the limit amount, it is determined that the generated audit result is effective.

Beneficial effect

In the embodiment of the present application, the level attribute and the limit amount attribute are set in combination with the actual situation, and the bonus and the deduction of the user account are detected to exceed the limit level of the corresponding level, and the amount of money input is controlled incorrectly when the flexibility is ensured as much as possible. Risks caused by such reasons.

DRAWINGS

1 is a flowchart of a method for managing a user account provided by an embodiment of the present application;

2 is a flowchart of a method for managing a user account provided by a preferred embodiment of the present application;

FIG. 3 is a structural block diagram of an apparatus for managing a user account according to an embodiment of the present application.

Embodiments of the invention

In order to make the technical problems, technical solutions and beneficial effects to be solved by the present application more clear, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

1 is a flowchart of a method for managing a user account provided by an embodiment of the present application. As shown in FIG. 1, the method includes steps S110 to S160.

In step S110, the created user account is obtained, and the hierarchical attribute and the restricted metality are added to the user account.

The user account may be created by the system administrator, or may be automatically created by the system after receiving the instruction to create a user account, and the information of each user is recorded in one row of the table compared to the prior art. The embodiment of the present application has a special user management system, and each user has a special user account, and the function is more powerful.

Since each salesperson has a separate account, each salesperson can submit data on his own initiative. In the prior art, the superior management personnel of each salesperson need to fill in the information of each salesperson in the form, or each salesperson sends the form to the superior management personnel, and then is summarized by the superior management personnel. If the number of salespersons is large, the superior is superior. When the manager fills in or summarizes the multi-person information, it is easy to generate an error. In the embodiment of the present application, each salesperson reports the information in the user account, and the user management system automatically compares the information of each salesperson according to various statistics. Ways to summarize, such as by time, by type of payment, or by amount of money, and so on.

Each user account corresponds to a salesperson. Each salesperson has a corresponding user level and limit amount when processing the business. When adding a user account, you can add the hierarchical attribute of the user account to set the user level, and you can add limited metality. Set the limit amount.

Setting the user level can classify and manage the salespersons at different stages. Because different levels of salesmen have gaps in salary, etc., in order to encourage and bind the salesmen at all levels, they can be set to different levels of salesmen. Different reward and punishment measures, such as different limit amounts, that is, the maximum amount of bonuses and the maximum amount of deductions.

When creating a user account, you can enter information such as job number, name, contact information, and password. The above information can be used to determine a unique user account. The information such as the job number and name of the user account cannot be modified. Therefore, the user account cannot be transferred to other users. If the salesperson leaves the job, the user account is directly deleted through the resignation operation procedure, and the business in the user account is transferred to another user account. in. The contact information and password information in the user account can be modified as needed.

In step S120, the user level set in the hierarchical attribute is obtained.

As above, since the salesperson can report the information by himself, in order to control the risk, it is necessary to determine the level of the salesperson corresponding to each user account, so that the superior user account has the authority to review the lower-level user account. For example, the embodiment of the present application may divide the user account into L0, L1, L8 levels according to preset regulations, such as the management structure of the company, and increase the level from L0 to L8 user level.

Different user accounts have different permissions or different limit amounts, and the subsequent steps will be described in detail.

In step S130, a limit amount set in the limit metality is obtained, and the limit amount corresponds to the user level.

The limit amount can be set automatically based on the user level. For each level of user level increase, the limit amount is increased by a certain amount. For example, the limit amount of the L0 level is 100,000 yuan, and for each level, the limit amount is increased by 100,000 yuan. Setting a limit amount can avoid a large loss of a lower-level user account.

Generally speaking, after setting the user level, the limit amount can be set by default, but the salesperson of the same level may have different limit amounts. For example, the salesperson with the L0 level receives the bonus exceeding the limit of the level for several consecutive months. If the promotion level requires a certain period of time, and often cannot be upgraded step by step, then because the limit amount is set in advance, the limit amount can be directly modified for the salesperson at the level, and the flexibility is improved.

Step S140, receiving the amount of money input through the user account.

The amount of the payment may be the amount of bonus or deduction when the salesperson performs reward and punishment according to the performance of the work, and the amount of the payment may be input into the user management system through the user account of the salesperson himself, the salesperson superiority and other management personnel.

For example, the salesman's year-end award is 200,000 yuan, then the salesperson can input the amount of 200,000 yuan through the user account.

Step S150: Query the user level corresponding to the user account, and read the limit amount corresponding to the user level.

In the user management system, the corresponding relationship table is pre-stored, and by reading the hierarchical attribute of the user account and limiting the metality, the unique user level and the limit amount of the user account can be obtained, and the correspondence table records the user corresponding to each user account. Levels and limit amounts, etc. Through the correspondence table, various permissions of each user account in the service can be clarified.

In step S160, it is determined whether the amount of the payment is less than or equal to the limit amount. If the amount of the payment is less than or equal to the limit amount, it is determined that the generated audit result is effective.

Generally speaking, different levels of salesmen have different reward and punishment limits. For example, the L0 level salesperson may have a year-end bonus of up to 100,000 yuan, that is, the limit amount is 100,000 yuan. 100,000 yuan. Then the limit of the L3 user account is 400,000 RMB. When the amount of the L3 user account is 200,000 RMB, the amount of the payment can be effective because the amount of the payment is less than the limit amount.

Different privilege settings are set for different salespersons. For example, the L0-level salesperson has an annual salary of 50,000 RMB, and the L8-level salesperson has an annual salary of 1 million RMB. If the upper limit of the reward and punishment amount is 1/10 of the annual salary of the L0-level salesperson, that is, 5,000 yuan. RMB, there is not much incentive or binding for the L8 level salesman; on the contrary, if the upper limit of the reward and punishment amount is 1/10 of the annual salary of the L8 level salesperson, that is, 100,000 yuan, the L0 level salesman cannot bear By setting different limit amounts for different levels, it is better to manage the salesmen at all levels.

The embodiment of the present application sets the hierarchical attribute and the limit amount attribute in combination with the actual situation, and detects whether the bonus and deduction of the user account exceed the limit level of the corresponding level, and controls the input of the amount due to the amount of money as much as possible to ensure flexibility. The risk caused by the cause.

The embodiment of the present application describes a case where the amount of money is less than or equal to the limit amount, and when the amount of money is greater than the limit amount, there is also a corresponding processing method. Preferably, after step S150, the following two steps S210 and S220 may be included.

Step S210: If the amount of the payment is greater than the limit amount, the amount of the payment is sent to the upper-level user account of the user account.

There are a number of reasons why the amount of money may be greater than the limit amount, such as incorrect input or abnormal completion of performance. In this case, the superior needs to be notified and approved by the superior.

Step S220: Receive and parse the audit information sent by the upper-level user account. If the audit information is passed, the generated audit result is valid. If the audit information is not passed, the generated audit result is invalid.

The upper level personnel are evaluated and submitted with the audit information through the upper level user account used. The audit information may correspond to a field of review opinions, in which 1 indicates consent and 0 indicates disagreement. Corresponding to this field, there is also a result field, in which 1 means valid.

The upper-level personnel are generally the upper-level business personnel. The business personnel also have their own limit amount. However, if the business personnel's limit is still less than the amount of the payment, then the upper-level audit that exceeds the amount of the amount is required to pass the amount.

For example, the L3 level user account inputs a sum of 800,000 RMB, while the L3 level user account limit is 400,000 RMB. Only the L7 level user account has a limit of 800,000 RMB or more, then the L3 level user. The amount of the account can be reviewed through a step-by-step review until the L7 level user account is approved. In another implementation manner, the user account of the intermediate level can be directly reviewed by the upper level of the L7 level of the L3 level user account. After the user account of the superior is approved, the amount of the payment is valid, that is, the amount can be issued; if the review fails, the amount of the payment is invalid, that is, the amount cannot be issued.

In order to further control the risk, the effective amount can also be reviewed. In addition to different levels of user accounts, an auditor account can also be set. For example, the limit of the L0 level salesperson is 100,000 yuan, if the L0 level If the salesperson repeatedly applies for the amount of less than 100,000 yuan, it can take effect. In order to prevent the salesman from encroaching on the company's property in this way, the auditor account can be set to further monitor the effective amount to avoid the above situation. Preferably, the measure for further controlling the risk by the auditor account includes steps S310 to S330.

In step S310, the amount of the payment that is valid in the preset time interval is sent to the auditor account.

The preset time interval can be set according to business requirements or financial requirements. For example, the preset time interval can be half a day or four hours. The auditor account will receive all the amount of the payment within 4 hours every 4 hours. The user of the auditor account will monitor the amount of each payment in turn according to the corresponding system.

Step S320, receiving and parsing the monitoring information sent by the auditor account.

After the auditor monitors, he or she obtains monitoring opinions and submits monitoring information to the system. The monitoring information may correspond to a field of monitoring opinions, in which 1 indicates consent and 0 indicates disagreement. The field of the monitoring opinion also corresponds to the above result field, and the field of the monitoring opinion has a higher weight than the field of the audit opinion, that is, when the character in the field of the audit opinion is 1, and the character in the field of the monitoring opinion is 0, The character in the result field is 0, which means the amount of the payment is invalid.

Step S330, if the monitoring information includes an invalid instruction, the audit result corresponding to the invalid instruction is changed to be invalid.

The invalid instruction is the character 0 in the field of the monitoring opinion in step S320. In order to better control the risk, a plurality of auditor accounts may be set. In one implementation manner, the monitoring information sent by any one of the auditor accounts is included. When the instruction is invalid, the result of the audit is changed to invalid. In another implementation manner, when the monitoring information sent by more than half of the auditor accounts includes an invalid instruction, the audit result is invalid.

When the various information of the salesman is recorded through the form, in addition to the amount of the money, the problem of the deposit is often involved, which is also a place where the form is prone to error. The preferred embodiment of the present application further provides a method for managing a user account. FIG. 2 is a flowchart of a method for managing a user account according to a preferred embodiment of the present application. As shown in FIG. 2, after the step S110, the method further Steps S410 to S450 may be included.

That is, after creating a user account and adding the hierarchical attributes of the user account and limiting the metality, it also includes:

In step S410, the guaranteed metality added for the user account is obtained.

Margin is one of the ways in which an insurance company binds a salesperson, avoiding the low quality of the salesman's service or causing economic losses to the customer. By collecting the deposit, on the one hand, it plays a supervisory role, on the other hand, when the salesman causes actual losses or arrears, it will make certain compensation and compensation through the deposit.

In step S420, the guaranteed amount of money set in the guaranteed metallicity is obtained.

The guaranteed amount can be set according to the user level or performance of the user account. The higher the user level or the higher the performance, the greater the guaranteed amount.

The user management system can be tied to the company's bank account to verify that the deposit is paid. Each salesperson must enter into the company's bank account with the amount equal to the guaranteed amount when entering the company. Further, when the money is entered, the employee's work number must be noted. After the user management system detects that the money has been credited to the bank account, Read the information in the remarks. If the remark information can be matched to the clerk's job number, the loyalty number of the user account is queried by the job number, and the amount of the payment into the bank account is compared to whether the guaranteed amount is the same. If they are the same, then In the user management system, the verification pass is marked; if it is not the same, the standard margin is insufficient, and a message is sent to the administrator account, so that the administrator can notify the salesperson to make up the amount of the deposit.

Step S430, receiving a trigger of the user account to the departure operation program.

The resignation operation procedure generally pays off the arrears recorded in the user management system and hand over the tasks. At this stage, generally only the money can be collected and the money cannot be paid. The task is generally transferred instead of continuing to process.

After receiving the trigger, the permissions for other operations are suspended in addition to the departure operator. The trigger received by the user management system can be initiated by the salesperson through his or her own user account, or by other user accounts with rights, such as the user account of the superior of the salesperson.

Step S440, determining whether the user account completes the resignation operation procedure.

The resignation operation program may include multiple processes, and each process corresponds to one field. When the process is completed, 1 is written in the corresponding field, and when the characters in the corresponding field of the process are 1, the completion of the resignation operation procedure is determined.

In step S450, if the resignation operation procedure is completed, the funds corresponding to the guaranteed amount are entered into the preset bank account, and the guaranteed amount is changed to zero.

If the resignation operation procedure is completed, the condition of the refund guarantee amount is met, and the deposit paid by the salesperson at the time of paying the deposit is returned to the salesperson's bank account.

If the exit operation procedure cannot be completed, for example, the arrears cannot be returned, then the deposit must be deducted to compensate for the loss to some extent. Preferably, if the resignation operation procedure is not completed, the amount of the arrears can be calculated, and the amount owed is the amount required to complete the resignation operation procedure; then the funds corresponding to the difference between the guaranteed amount and the amount owed are credited to the bank account, and Change the guaranteed amount to zero.

Through the embodiment of the present application, the guarantee metality is set in the user account, and the margin is associated with the departure process in the user management system. When the salesperson is involved in the arrears and cannot be repaid, the technology is automatically deducted from the deposit. The program effectively reduces the economic loss caused by the departure of the salesman.

FIG. 3 is a structural block diagram of an apparatus for managing a user account according to an embodiment of the present disclosure. As shown in FIG. 3, the apparatus includes a first obtaining module 510, a second obtaining module 520, a third obtaining module 530, and a first receiving module 540. The query module 550 and the determination module 560.

The first obtaining module 510 is configured to obtain the created user account, and the hierarchical attribute and the limiting metality are added to the user account.

The second obtaining module 520 is configured to acquire a user level set in the hierarchical attribute.

The third obtaining module 530 is configured to obtain a limit amount set in the limiting metality, and the limit amount corresponds to the user level.

The first receiving module 540 is configured to receive the amount of the money input through the user account.

The query module 550 is configured to query the user level corresponding to the user account, and read the limit amount corresponding to the user level.

The determining module 560 is configured to determine whether the amount of the payment is less than or equal to the limit amount, and determine that the generated audit result is effective when the amount of the payment is less than or equal to the limit amount.

Preferably, the device further includes: a first sending module, configured to send the amount of the payment to the upper-level user account of the user account when the amount of the payment is greater than the limit amount; and the second receiving module is configured to receive and parse the upper level If the audit information is passed, the generated audit result is valid. If the audit information is not passed, the generated audit result is invalid.

Preferably, the device further includes: a second sending module, configured to send the amount of the payment that is valid in the preset time interval to the auditor account; and the third receiving module is configured to receive and analyze the monitoring sent by the auditor account. The information modification module is configured to invalidate the audit result corresponding to the invalid instruction when the monitoring information includes an invalid instruction.

Preferably, the device further includes: a fourth obtaining module, configured to acquire a guaranteed metality added for the user account; a fifth obtaining module, configured to acquire a guaranteed amount of money set in the guaranteed metality; and a fourth receiving module, configured to receive the user The triggering of the account for the resignation operation procedure; the judging module is configured to determine whether the user account completes the resignation operation procedure; the first payment module is configured to enter the funds corresponding to the guaranteed amount into the preset bank account when completing the resignation operation procedure And change the guaranteed amount to zero.

Preferably, the device further comprises: a calculating module, configured to calculate the amount of the arrears when the leaving operation procedure is not completed, the amount of the arrears is the amount required to complete the exit operation procedure; and the second payment module is configured to ensure the amount of the payment The funds corresponding to the difference in the amount of the arrears are credited to the bank account number and the guaranteed amount is changed to zero.

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, only the division of each functional unit described above is exemplified. In practical applications, the above function assignment can be completed by different functional units as needed. The internal structure of the device is divided into different functional units or modules to perform all or part of the functions described above. Each functional unit in the embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit, and the integrated unit may be implemented in the form of hardware. It can also be implemented in the form of a software functional unit. In addition, the specific names of the respective functional units are only for the purpose of facilitating mutual differentiation, and are not intended to limit the scope of protection of the present application. For the specific working process of the unit in the foregoing device, reference may be made to the corresponding process in the foregoing device embodiment, and details are not described herein again.

The above embodiments are only used to illustrate the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still The technical solutions are modified, or the equivalents of some of the technical features are replaced. The modifications and substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

The above is only the preferred embodiment of the present application, and is not intended to limit the application. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are included in the scope of the present application. Inside.

Claims

A method for managing a user account, comprising:

Obtaining a created user account, where the hierarchical attribute and the restricted metality are added;

Get the user level set in the hierarchy attribute;

Obtaining a limit amount set in the limiting metality, the limit amount corresponding to the user level;

Receiving the amount of money input through the user account;

Querying the user level corresponding to the user account, and reading a limit amount corresponding to the user level;

Determining whether the amount of the payment is less than or equal to the limit amount, and if the amount of the payment is less than or equal to the limit amount, determining that the generated audit result is effective.
The method according to claim 1, wherein after the querying the user level of the user account and reading the limit amount corresponding to the user level, the method further comprises:

If the amount of the payment is greater than the limit amount, sending the amount of the payment to the upper-level user account of the user account;

The auditing information sent by the upper-level user account is received and parsed. If the auditing information is passed, the generated auditing result is valid. If the auditing information is not passed, the generated auditing result is invalid.
The method according to claim 1 or 2, wherein after the determining the generated audit result is effective, the method further comprises:

Sending the amount of the payment in effect within the preset time interval to the auditor account amount;

Receiving and parsing the monitoring information sent by the auditor account;

If the invalidation instruction is included in the monitoring information, the audit result corresponding to the invalid instruction is changed to be invalid.
The method of claim 1, after the obtaining the created user account, further comprising:

Obtaining the guaranteed metality added for the user account;

Obtaining a guaranteed amount set in the guaranteed metality;

Receiving a trigger of the user account for the departure operation procedure;

Determining whether the user account completes the resignation operation procedure;

If the exit operation procedure is completed, the funds corresponding to the guaranteed amount are entered into a preset bank account, and the guaranteed amount is changed to zero.
The method of claim 4, further comprising: after determining whether the user account completes the resignation operation procedure,

If the exit operation procedure is not completed, the amount of the arrears is calculated, and the amount of the arrears is the amount required to complete the exit operation procedure;

The funds corresponding to the difference between the guaranteed amount and the amount of the arrears are credited to the bank account, and the guaranteed amount is changed to zero.
An apparatus for managing a user account, comprising:

a first obtaining module, configured to acquire a created user account, where a hierarchical attribute and a restricted metality are added;

a second obtaining module, configured to acquire a user level set in the hierarchical attribute;

a third obtaining module, configured to acquire a limit amount set in the limiting metality, where the limit amount corresponds to the user level;

a first receiving module, configured to receive an amount of money input through the user account;

a querying module, configured to query the user level corresponding to the user account, and read a limit amount corresponding to the user level;

And a determining module, configured to determine whether the amount of the payment is less than or equal to the limit amount, and when the amount of the amount is less than or equal to the limit amount, determining that the generated audit result is effective.
The device of claim 6 further comprising:

The first sending module is configured to send the amount of the payment to the upper-level user account of the user account when the amount of the payment is greater than the limit amount;

a second receiving module, configured to receive and parse the audit information sent by the upper-level user account, if the audit information is passed, the generated audit result is valid, and if the audit information is failed, The generated audit result is invalid.
The device according to claim 6 or 7, further comprising:

a second sending module, configured to send the amount of the payment in which the audit result is valid within a preset time interval to an auditor account;

a third receiving module, configured to receive and parse the monitoring information sent by the auditor account;

And a modification module, configured to: when the invalidation instruction is included in the monitoring information, change the audit result corresponding to the invalid instruction to be invalid.
The device of claim 6 further comprising:

a fourth obtaining module, configured to obtain a guaranteed metality added for the user account;

a fifth obtaining module, configured to acquire a guaranteed amount of money set in the guaranteed metality;

a fourth receiving module, configured to receive a trigger of the user account to the leaving operation program;

a judging module, configured to determine whether the user account completes a resignation operation procedure;

The first payment module is configured to: when the termination operation procedure is completed, the funds corresponding to the guaranteed amount are entered into a preset bank account, and the guaranteed amount is changed to zero.
The device of claim 9 further comprising:

a calculation module, configured to calculate the amount of the arrears when the exit operation procedure is not completed, and the amount of the arrears is the amount required to complete the exit operation procedure;

The second payment module is configured to insert the funds corresponding to the difference between the guaranteed amount and the amount of the arrears into the bank account, and change the guaranteed amount to zero.
A terminal device, comprising: a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable The following steps are implemented when the instruction is executed:

Obtaining a created user account, where the hierarchical attribute and the restricted metality are added;

Get the user level set in the hierarchy attribute;

Obtaining a limit amount set in the limiting metality, the limit amount corresponding to the user level;

Receiving the amount of money input through the user account;

Querying the user level corresponding to the user account, and reading a limit amount corresponding to the user level;

Determining whether the amount of the payment is less than or equal to the limit amount, and if the amount of the payment is less than or equal to the limit amount, determining that the generated audit result is effective.
The terminal device according to claim 11, wherein after the querying the user level of the user account and reading the limit amount corresponding to the user level, the processor executes The computer readable instructions implement the following steps:

If the amount of the payment is greater than the limit amount, sending the amount of the payment to the upper-level user account of the user account;

The auditing information sent by the upper-level user account is received and parsed. If the auditing information is passed, the generated auditing result is valid. If the auditing information is not passed, the generated auditing result is invalid.
The terminal device according to claim 11 or 12, wherein after the determining that the generated audit result is valid, the processor executes the computer readable instructions to implement the following steps:

Sending the amount of the payment in effect within the preset time interval to the auditor account amount;

Receiving and parsing the monitoring information sent by the auditor account;

If the invalidation instruction is included in the monitoring information, the audit result corresponding to the invalid instruction is changed to be invalid.
The terminal device according to claim 11, wherein after the acquiring the created user account, the processor executes the computer readable instructions to implement the following steps:

Obtaining the guaranteed metality added for the user account;

Obtaining a guaranteed amount set in the guaranteed metality;

Receiving a trigger of the user account for the departure operation procedure;

Determining whether the user account completes the resignation operation procedure;

If the exit operation procedure is completed, the funds corresponding to the guaranteed amount are entered into a preset bank account, and the guaranteed amount is changed to zero.
The terminal device according to claim 14, wherein after the determining whether the user account completes the leaving operation procedure, the processor executes the computer readable instructions to implement the following steps:

If the exit operation procedure is not completed, the amount of the arrears is calculated, and the amount of the arrears is the amount required to complete the exit operation procedure;

The funds corresponding to the difference between the guaranteed amount and the amount of the arrears are credited to the bank account, and the guaranteed amount is changed to zero.
A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by a processor, implement the following steps:

Obtaining a created user account, where the hierarchical attribute and the restricted metality are added;

Get the user level set in the hierarchy attribute;

Obtaining a limit amount set in the limiting metality, the limit amount corresponding to the user level;

Receiving the amount of money input through the user account;

Querying the user level corresponding to the user account, and reading a limit amount corresponding to the user level;

Determining whether the amount of the payment is less than or equal to the limit amount, and if the amount of the payment is less than or equal to the limit amount, determining that the generated audit result is effective.
The computer readable storage medium according to claim 16, wherein after the querying the user level of the user account and reading the limit amount corresponding to the user level, the processor executes the The following steps are implemented when the computer readable instructions are described:

If the amount of the payment is greater than the limit amount, sending the amount of the payment to the upper-level user account of the user account;

The auditing information sent by the upper-level user account is received and parsed. If the auditing information is passed, the generated auditing result is valid. If the auditing information is not passed, the generated auditing result is invalid.
The computer readable storage medium according to claim 16 or 17, wherein after the determining that the generated audit result is valid, the processor executes the computer readable instructions to implement the following steps:

Sending the amount of the payment in effect within the preset time interval to the auditor account amount;

Receiving and parsing the monitoring information sent by the auditor account;

If the invalidation instruction is included in the monitoring information, the audit result corresponding to the invalid instruction is changed to be invalid.
The computer readable storage medium according to claim 16, wherein after the obtaining the created user account, the processor executes the computer readable instructions to implement the following steps:

Obtaining the guaranteed metality added for the user account;

Obtaining a guaranteed amount set in the guaranteed metality;

Receiving a trigger of the user account for the departure operation procedure;

Determining whether the user account completes the resignation operation procedure;

If the exit operation procedure is completed, the funds corresponding to the guaranteed amount are entered into a preset bank account, and the guaranteed amount is changed to zero.
The computer readable storage medium according to claim 19, wherein, after said determining whether said user account completes a leaving operation procedure, said processor executing said computer readable instructions implements the following steps:

If the exit operation procedure is not completed, the amount of the arrears is calculated, and the amount of the arrears is the amount required to complete the exit operation procedure;

The funds corresponding to the difference between the guaranteed amount and the amount of the arrears are credited to the bank account, and the guaranteed amount is changed to zero.