CN115578199A

CN115578199A - Method, apparatus, device, medium, and product for processing row weight data in stock right incentive

Info

Publication number: CN115578199A
Application number: CN202211301987.1A
Authority: CN
Inventors: 温嘉榕; 王有露
Original assignee: Shenzhen Futu Network Technology Co Ltd
Current assignee: Shenzhen Futu Network Technology Co Ltd
Priority date: 2022-10-24
Filing date: 2022-10-24
Publication date: 2023-01-06
Also published as: WO2024087822A1

Abstract

The application provides a method, a device, equipment, a medium and a product for processing row weight data in stock right incentive, which comprises the following steps: acquiring a request for deducting the stock row right sent by a target client, wherein the request for deducting the stock row right comprises the target row weight quantity; allocating the target number of stocks in the account to be attributed to an employee account of a target client, updating the number of stocks in the employee account according to the target number, transferring the target number of stocks in the account to be attributed to an attributed account, and updating the number of stocks in the attributed account according to the target number; the target quantity is determined by the target row weight quantity and the stock quantity used for deducting the row weight cost corresponding to the target row weight quantity, the account to be attributed is used for hosting stocks which are not actually distributed to the employees, and the account to be attributed is used for hosting stocks which are actually distributed to the employees. The method and the device improve the security and the accuracy of the rights management data when the staff manage the rights, ensure the security of a mode of deducting part of the stock rights management, and improve the stock trading efficiency.

Description

Method, apparatus, device, medium, and product for processing row weight data in stock right incentive

Technical Field

The embodiment of the application relates to the technical field of data processing, in particular to a method, a device, equipment, a medium and a product for processing row weight data in stock right incentive.

Background

A equity incentive is an incentive mechanism for a business to grant a certain amount of stock to employees in order to incentivize them. In the stock right incentive, the employee needs to pay the bank right cost, namely the cost of the granted stock and the fees such as tax, and the bank right mode of paying the bank right cost comprises a mode of deducting the bank right of the stock, and the bank right mode pays the bank right cost by deducting part of the stock granted to the stock.

At present, the existing scheme usually realizes a mode of deducting partial stock rights by manually modifying the stock quantity. However, the manual modification method is time-consuming and labor-consuming, and there is a risk that the stock quantity is modified maliciously or by mistake, so that the method of deducting part of the stock rights is unsafe, and the stock trading efficiency is low.

Disclosure of Invention

The application provides a method, a device, equipment, a medium and a product for processing the row right data in the stock right incentive, so as to improve the safety and the accuracy of the row right data when the personnel carry out the row right, ensure the safety of a part of stock row right deduction modes and improve the efficiency of stock trading.

In a first aspect, a method for processing row weight data in a stock right incentive is provided, which includes: acquiring a request for deducting the stock row right sent by a target client, wherein the request for deducting the stock row right comprises the target row weight quantity; distributing the target amount of stocks in the account to be attributed to an employee account of a target client, updating the stock amount in the employee account according to the target amount, transferring the target amount of stocks in the account to be attributed to an attributed account to the attributed account, and updating the stock amount in the attributed account according to the target amount; the target quantity is determined by the target row weight quantity and the stock quantity used for deducting the row weight cost corresponding to the target row weight quantity, the account to be attributed is used for hosting the stocks which are not actually distributed to the employees, and the account to be attributed is used for hosting the stocks which are actually distributed to the employees.

In a second aspect, there is provided a row weight data processing apparatus in a stock right incentive, comprising: the system comprises a first acquisition module and a warehouse transfer module, wherein the first acquisition module is used for acquiring a request for deducting the row weight of the stocks, which is sent by a target client side, and the request for deducting the row weight of the stocks comprises the weight number of the target row; the warehouse transferring module is used for distributing the target quantity of the stocks in the account to be attributed to the employee account of the target client, updating the quantity of the stocks in the employee account according to the target quantity, transferring the target quantity of the stocks in the account to be attributed to the account to the attributed account, and updating the quantity of the stocks in the attributed account according to the target quantity; the target quantity is determined by the target row weight quantity and the stock quantity used for deducting the row weight cost corresponding to the target row weight quantity, the account to be attributed is used for hosting stocks which are not actually distributed to the employees, and the account to be attributed is used for hosting stocks which are actually distributed to the employees.

In a third aspect, an electronic device is provided, including: a processor and a memory, the memory being adapted to store a computer program, the processor being adapted to invoke and execute the computer program stored in the memory to perform the method as in the first aspect or its implementations.

In a fourth aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to perform the method as in the first aspect or its implementations.

In a fifth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method as in the first aspect or its implementations.

A sixth aspect provides a computer program enabling a computer to perform a method as in the first aspect or implementations thereof.

Through the technical scheme, the server can obtain a request for deducting the stock row rights sent by the target client, wherein the request for deducting the stock row rights comprises the target row weight number, then, the server can distribute the target number of stocks in the account to be attributed to the employee account of the target client, update the number of stocks in the employee account according to the target number, transfer the target number of stocks in the account to be attributed to the attributed account, and update the number of stocks in the attributed account according to the target number; the target quantity is determined by the target row weight quantity and the stock quantity used for deducting the row weight cost corresponding to the target row weight quantity, the account to be attributed is used for hosting stocks which are not actually distributed to the employees, and the account to be attributed is used for hosting stocks which are actually distributed to the employees. In the process, the server can automatically realize a mode of deducting part of the stock rights according to the request for deducting the stock rights sent by the target client without manually modifying the quantity of the stocks, so that the security and the accuracy of the rights data when the staff carry the rights can be improved, the security of the mode of deducting part of the stock rights is ensured, and the time and the labor cost of the staff carry the rights are saved. In addition, the method for deducting part of the stock rights does not need to sell the stocks, and does not need to sell the stocks and wait for the transaction, so that the method can not only avoid communication with a trading exchange, save the processing cost of virtual resources, ensure the success rate of rights management and the trading efficiency, reduce the selling pressure of the sold stocks on prices, but also achieve the effect of reducing the number of times of stock increase.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is an application scenario diagram provided in an embodiment of the present application;

FIG. 2 is a flow chart of a method for processing row weight data in a stock right incentive according to an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating processing of row weight data in a stock incentive according to an embodiment of the present application;

FIG. 4 is a schematic diagram illustrating processing of row weight data in another stock right incentive provided by an embodiment of the present application;

FIG. 5 is a schematic diagram illustrating processing of row weight data in a stock incentive according to an embodiment of the present application;

FIG. 6 is a flow chart of another method for processing row weight data in a stock right incentive according to an embodiment of the present application;

FIG. 7 is a schematic diagram illustrating processing of row weight data in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 8 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 9 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 10 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 11 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 12 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 13 is a schematic diagram illustrating row weight data processing in another exemplary embodiment of the present application;

FIG. 14 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 15 is a schematic diagram illustrating row weight data processing in another equity incentive provided in an embodiment of the present application;

FIG. 16 is a schematic diagram illustrating row weight data processing in another exemplary embodiment of the present application;

FIG. 17 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive offered in accordance with an embodiment of the present application;

FIG. 18 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive offered in accordance with an embodiment of the present application;

FIG. 19 is a schematic diagram illustrating row weight data processing in another exemplary embodiment of the present application;

FIG. 20 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 21 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 22 is a schematic diagram illustrating row weight data processing in another exemplary embodiment of the present application;

FIG. 23 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive provided in an embodiment of the present application;

FIG. 24 is a schematic diagram illustrating row weight data processing in another exemplary equity incentive offered in accordance with an embodiment of the present application;

FIG. 25 is a diagram of a row weight data processing apparatus 2500 in a stock incentive provided by an embodiment of the present application;

fig. 26 is a schematic block diagram of an electronic device 2600 provided by an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

As described above, the existing scheme usually implements a way of deducting partial rights of stocks by manually modifying the stock quantity. However, the manual modification method is time-consuming and labor-consuming, and there is a risk that the stock quantity is modified maliciously or by mistake, so that the method of deducting part of the stock rights is unsafe, and the trading efficiency is low.

In order to solve the technical problem, the inventive concept of the present application is: the server can automatically realize a mode of deducting part of the stock rights according to the request of deducting the stock rights sent by the target client.

It should be understood that the technical solution of the present application can be applied to the following scenarios, but is not limited to:

in some implementation manners, fig. 1 is a diagram of an application scenario provided by an embodiment of the present application, and as shown in fig. 1, the application scenario may include a server 110, an employee end 120, an enterprise end 130, and a third party 140. The employee side 120, the enterprise side 130, or the third party 140 may be connected to the server 110 through a wired network or a wireless network.

For example, the employee end 120 may be a device used by an employee, and the employee may use the employee end 120 to deduct part of the stock rights ways, such as selecting rights ways, filling in target rights amounts, viewing rights records, and the like; the enterprise end 130 may be a device used by an enterprise administrator, and the enterprise administrator may use the enterprise end 130 to select a display field to be displayed on the employee end 120, view employee rights records, and the like; the third party 140 may be a device used by an examining and approving person in the dealer trading software, and the examining and approving person may use the third party 140 to complete manual circulation required by the authority form, view the details of tasks implemented in the authority form, and the like; the server 110 may be configured to respond to a request of the employee terminal 120, the enterprise terminal 130, or the third party 140, where the server 110 may be one server, may also be a server cluster composed of multiple servers, and may also be a cloud platform control center, which is not limited in this application. The employee end 120, the enterprise end 130, or the third party 140 may be a mobile phone, a tablet computer, a desktop, a laptop, a handheld computer, a notebook computer, a vehicle-mounted device, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a Personal Digital Assistant (PDA), an Augmented Reality (AR) \ Virtual Reality (VR) device, and the like, but is not limited thereto. Additionally, the clerk side 120, the enterprise side 130, and the third party 140 may interact with the server 110 based on the dealer transaction software or a web page corresponding to the dealer transaction software.

In addition, fig. 1 exemplarily shows one server, an employee end, an enterprise end, and a third party, and may actually include other numbers of servers, employee ends, enterprise ends, and third parties, which are not limited in this application.

After introducing the application scenario of the embodiment of the present application, the following will explain the technical solution of the present application in detail:

fig. 2 is a flowchart of a method for processing row weight data in a stock right incentive according to an embodiment of the present application, which may be performed by the server 110 shown in fig. 1, but is not limited thereto. As shown in fig. 2, the method may include the steps of:

s201: acquiring a request for deducting the stock row right sent by a target client, wherein the request for deducting the stock row right comprises the target row weight quantity;

s202: the method comprises the steps of allocating a target number of stocks in an account to be attributed to an employee account of a target client, updating the number of stocks in the employee account according to the target number, transferring the target number of stocks in the account to be attributed to an attributed account, and updating the number of stocks in the attributed account according to the target number, wherein the target number is determined by the target row weight number and a share number used for deducting row weight cost corresponding to the target row weight number, the account to be attributed is used for hosting the stocks which are not actually allocated to the employee, and the attributed account is used for hosting the stocks which are actually allocated to the employee.

It should be noted that, in the embodiment of the present application, the target client may be dealer trading software installed on the employee side in fig. 1, but is not limited thereto, and the server may be a server corresponding to the target client. The server may control the display condition of the target client, for example, the server may send data that the target client needs to display to the target client, and the target client may display a related page according to the display data sent by the server.

It should be noted that the account to be attributed and the attributed account may be accounts of the enterprise, and the employee account may be used to host stocks actually assigned to employees by the enterprise. The right-of-way mode for paying right-of-way cost and tax includes: a way of selling the stock rights, a way of paying the bank rights by cash, a way of deducting part of the stock rights, etc. The deduction of part of the stock rights is also called the rights of the stock to be saved to the incentive pool, the incentive pool can be the account to be attributed, and the rights of the stock is paid by deduction of part of the stock granted to the stock. For example: assuming that the enterprise grants 100 shares of stock to the employee and 20 shares of stock are needed to pay the cost and tax corresponding to the 100 shares of stock, when the employee selects the deduction mode of partial stock rights, the 20 shares of stock need to be saved to the account to be attributed to offset the cost and tax corresponding to the 100 shares of stock, and the employee account can obtain 100-20=80 shares of stock, i.e. the employee can actually be allocated 80 shares of stock. It can be seen that the 80 shares belong to the shares actually allocated to employees, and the 100 shares belong to the shares not actually allocated to employees, so that before the partial share right deduction mode is performed, the 100 shares are hosted by the account to be attributed, and after the partial share right deduction mode is performed, the server can leave 20 shares of the 100 shares in the account to be attributed for subsequent incentive allocation, allocate 80 shares of the 100 shares in the account to be attributed to the employee share account, and update the share number in the employee account according to the 80 shares, for example, assuming that before the right deduction, the share number in the employee account is 50 shares, then after the right deduction, the server can update the share number in the employee account to be 50+80=130 shares according to the 80 shares; meanwhile, 80 shares of the 100 shares are transferred to the attributed account, which means that 80 shares of the 100 shares are actually allocated to the employee, and the stock quantity in the attributed account is updated according to the 80 shares, for example, assuming that the stock amount in the attributed account is 1000 shares before the right of action, the server may update the stock amount in the attributed account to be 1000+80=1080 shares according to the 80 shares after the right of action.

In some implementations, the server may open the function of deducting the stock right to the target client, that is, open the function of supporting the manner of deducting part of the stock right. For example, the server may include a central station, as shown in fig. 3 (a), which may add a "deduct stock rights mode" switch under "incentive configuration-row rights application and mode" category, which may default to an off state, and when the central station selects the switch to be in the on state, the target client may display and support deduction of part of the stock rights mode. Alternatively, as shown in fig. 3 (b), the central station in the server may add "get stock-deduct part of stock payment" in the "enterprise setting" module, and may also add corresponding functions in the "personal setting" module. In addition, the middle desk can set a check box corresponding to 'get stock-deduct part of stock payment' as grey, so the EBOS of the server can not directly close the rights management mode.

In some implementations, the target client may send a deduct stock rights request to the server for implementing a deduct partial stock rights mode based on an employee's operation at the target client.

For example, as shown in fig. 4 (a), after the server opens the function of deducting the stock right to the target client, the right selection page of the target client may add a "deduct part of the stock payment cost" or "deduct part of the stock payment fee" option, and the option may coexist with the "sell part of the stock payment right cost" option corresponding to the sell part of the stock right on the right selection page of the target client. The bank right mode corresponding to the option of 'deducting part of the stock payment cost' shows that the file can be 'bank right obtaining corresponding positive stock, selling part of the stock payment option cost and expense' to inform the staff of the stock transfer condition corresponding to the mode of deducting part of the stock bank right. After the target client acquires the click operation of the employee on the option of deducting part of stock payment cost, the target client can trigger the pre-selection bullet layer of the grant number, then the target client can acquire the selection operation of the employee on the grant number in the pre-selection bullet layer of the grant number, and a right order editing page is displayed. As shown in fig. 4 (b), the right order editing page includes: payment of fees, projected net revenue and projected fees, etc. Wherein "deducting partial stock payments" for "fee payments" means that the rights-of-bank approach is to pay rights-of-bank costs and taxes by deducting a portion of the stocks that are awarded in the stocks. When the target client side can display the relevant documents in the disk after acquiring the click of the employee on the 'estimated expense', deducting the number of shares = (cost deducted by a substitute + tax deducted by a substitute) ÷ price in the disk; when the bill is buried in advance, deducting the stock number = (deduction cost + deduction tax money) and dividing the collection price of the last transaction time period, and informing the employee of the expected expense calculation condition corresponding to the right-of-way mode. After the target client obtains the click operation of the employee on the "predicted net profit", a "detailed fee" bullet layer as shown in (c) of fig. 4 may be displayed, the "predicted fee" in the bullet layer corresponds to a bullet layer, so as to inform the employee of the way of calculating the predicted deduction amount, the corresponding file may be as shown in (c) of fig. 4, or when the order corresponding to the right of way is a formal order, the market price in the right of way daily disk is divided by the "predicted deduction amount = (deduction cost + deduction tax money), and is rounded up. After the task flow is completed, the system adopts the closing price of the right of bank to reconfirm the deduction quantity, and when the order corresponding to the right of bank is a formal order, the system collects the closing price in the last transaction time period for' predicted deduction quantity = (deduction cost + deduction tax) and upwards rounded. After the task flow is completed, the system adopts the right-of-way daily closing price to reconfirm the deduction quantity, and the application does not limit the quantity. Next, after the target client acquires the employee's click operation on the "next" button in (b) or (c) in fig. 4, as shown in (a) in fig. 5, a right-of-line order information confirmation page may be displayed, and the page includes: and predicting the cost, the profit-to-account time and the like, and after the target client acquires the click operation of the employee on the profit-to-account time, displaying a pop-up window as shown in (a) in fig. 5 to inform the calculation basis of the profit-to-account time. Finally, after the target client obtains the employee's click operation on the "confirm submit" button in (a) in fig. 5, as shown in (b) in fig. 5, a row right order submission completion page may be displayed, and a request for deducting the stock row right is sent to the server.

It should be noted that, since the way of deducting part of the stock right does not relate to trading, i.e. stock selling, the page related to the embodiment of the present application does not display the options related to selling, such as trade commission estimate, trade fee, order type, selling way, price, sale amount, etc.

In some implementations, the server may set a pre-association before obtaining the request to deduct the stock rights, i.e., the server may associate an autonomous right amount control function. For example, when the server sets that the target client supports deduction of part of the stock rights, the function of controlling the line rights and amount may be started for the target client, and when the function is started, as shown in (b) in fig. 4, after the target client obtains the click operation of the employee on "all line rights", the line rights amount may be displayed as the maximum feasible rights amount; or, the target client may also obtain the row weight amount autonomously input by the employee, and then, the target client may check the row weight amount autonomously input by the employee to check whether the employee has a sufficient row weight amount, and if the amount is greater than the maximum feasible weight amount, the target client may report an error: the current quota is the "maximum feasible right amount", please reduce the row weight amount or apply for more quota.

Fig. 6 is a flowchart of another method for processing row weight data in a stock incentive according to an embodiment of the present application. Based on fig. 2, as shown in fig. 6, before S220, the method further includes:

s610: creating at least one task node, wherein the at least one task node is used for distributing the target number of stocks in the account to be attributed to the employee account, updating the number of stocks in the employee account according to the target number, transferring the target number of stocks in the account to be attributed to the account, and updating the number of stocks in the account to be attributed according to the target number;

s620: and configuring the execution sequence of at least one task node.

The S220 includes:

s630: and executing at least one task node according to the execution sequence.

It is understood that in the manner of deducting partial stock rights, the calculation logic for deducting the stock shares may be: the deduction amount is the sum of the right-of-way cost and tax and the result of asking for quotients for right-of-way daily closing price. Under the calculation logic, the harbor stock and the American stock can not be distinguished. In addition, because the calculation logic does not relate to stock selling, cost tax deduction and payment for enterprises, and the number of the deducted shares needs to be confirmed after tax accounting and verification, floating Buffer and considering whether the number of the deducted shares is the whole number or not can be avoided when the number of the deducted shares is calculated. When the right of bank cost is not deducted, the right of bank cost in the calculation logic can be confirmed as 0, and when the tax is not deducted, the tax in the calculation logic can be confirmed as 0.

Based on the computing logic, the server may confirm that the at least one task node may include: determining a target amount of rights to move, deducting rights to move handling fees, confirming the daily closing price of rights to move, determining the tax to move, calculating the target amount, stock allocation, but not limited thereto.

In some implementations, S630 may include: the server polls at least one task node according to the execution sequence, determines a target task node which needs to be executed in the at least one task node, then the server can generate a target message for executing the target task node, stores the target message in a message queue, then the server can monitor the message queue based on a task flow engine to obtain the target message, and finally the server can consume the target message based on the task flow engine to execute the target task node.

In some implementations, the server needs to perform compatible processing on the way of deducting part of the stock rights, because the way of deducting part of the stock rights is different from the way of setting other rights by the server, such as selling part of the stock rights.

For example, the server may set a template corresponding to each row right mode, where the template is composed of at least one task node, each task node is used to perform a different function, such as deducting a row right commission charge, and the server may configure a circulation sequence, i.e., an execution sequence, of the at least one task node, and then, the server may add the templates corresponding to different row right modes to the task processing template. When the server needs to process a certain row right mode, the server can acquire a corresponding template from the task processing template, and execute at least one task node according to a circulation sequence configured in the template based on the task circulation engine so as to complete the processing of the row right mode. Then, the server can realize the compatibility of the mode of deducting part of the stock rights by carrying out the compatibility of the node circulation mode corresponding to the mode of deducting part of the stock rights. Specifically, as shown in fig. 7, the server may derive a new node for the way of deducting part of the stock rights: deducting part of stock right task nodes A and deducting part of stock right task nodes B, configuring execution sequences of the two task nodes, forming the deducting part of stock right task nodes by the two task nodes to obtain a deducting part of stock right task processing template, adding the deducting part of stock right task processing template into the task processing template by the server, acquiring the deducting part of stock right task processing template from the task processing template when the server needs to process the deducting part of stock right mode, and executing the deducting part of stock right task nodes A and the deducting part of stock right task nodes B according to circulation sequences configured in the deducting part of stock right task processing template based on a task circulation engine to complete the processing of the deducting part of stock right mode.

For example, at least one task node and its corresponding execution sequence may be as shown in fig. 8, wherein the "determine royalty result" includes the "determine target bank amount", "subtract bank fee" and the "subtract bank fee", the "determine royalty tax" includes the "HR tax adjustment", "adjust royalty tax", "tax to account (tax into the attributed account)", and the "stock to account" includes the "stock barter". The task node of 'determining the row weight result' can confirm the row weight quantity of the row weight at this time; the task node of 'deducting the bank right fee' can deduct the bank right commission fee, does not deduct the bank right cost and tax, if the employee account has no cash, deduct the cash and be the negative value; the HR tax adjustment task node can determine the tax to be paid at this time; the task node of 'adjusting the tax of the bank right' only reconfirms the tax and updates the deducted shares without deducting the tax; the task node of "tax goes to account (tax is stored in the attributed account)" can be completed in a manual circulation manner, which is introduced in the subsequent embodiments of the present application and will not be described herein again; the 'stock-to-account' task node can allocate a target amount of stocks to the employee account when adding or subtracting stocks to the employee account, update the stock amount in the employee account according to the target amount, complete the transfer from the account to which the user belongs to the account, namely transfer the target amount of stocks in the account to which the user belongs to the account, update the stock amount in the account to which the user belongs according to the target amount, and can send a message of completing the right of bank to the target client, so as to change the task flow state of the target client and the third-party client to 'right of bank' already; the "CRM delivery confirmation/T +2 completion delivery" task node may be used as a branch link of "deducting the right-of-way cost", and does not affect the task flow to the "confirm the right-of-way daily closing price" task node.

The server can form a deduction part stock rights task processing template by the task nodes, stores the deduction part stock rights task processing template in the database, and then executes the task nodes based on the task processing engine to realize the processing of the deduction part stock rights task mode. For example: here, a manner in which the server executes at least one task node according to the execution sequence is described by taking a task node "validation right result" as an example, and a manner in which the server executes other task nodes is similar to that described here, and is not described in detail herein. As shown in fig. 9, the background of the server includes a timing processing module and a task flow engine, the timing processing module may poll a task node in the database, from which a part of the stock right task processing template is deducted, by means of a timing processing script, and then determine that a target task node to be executed is a "confirmed right result", then the timing processing module may generate a message for executing the task node and store the message in a message queue, and then the task flow engine may monitor the message queue, obtain the message, and consume the message to execute the task node, and at the same time, after consuming the message, the task flow engine may modify the execution state of the task node to be executed, so that the timing processing module may determine that the task node to be executed is a next task node adjacent to the execution order of the task node to be executed, and "deducted right cost".

Illustratively, the database may be a MySQL database, and the message queue may be a RabbitMQ, which is not limited in this application.

It should be noted that, the application does not limit the number, specific content, execution sequence, and the like of the task nodes corresponding to each row right mode. For example: as shown in fig. 10, the task node of "tax to account (tax is deposited into the attributed account)" does not belong to the necessary front link of the task node of "stock to account", so that it can be used as a branch link of "HR tax adjustment" and does not affect the task flow to the task node of "stock to account"; because the mode of deducting part of the stock rights does not relate to a task node of 'adjusting rights and taxes', the server can also remove the task node, and meanwhile, the third-party client side does not display the task node.

It should be noted that, after acquiring the request for deducting the stock rights, the server may start to execute the task node "confirm the rights result", and after the time for feasibility is over, the server may end to execute the "confirm the rights result", and determine the number of rights included in the rights result.

In the above embodiment, the server may obtain the request for deducting the stock quotation right sent by the target client, and then, the server may allocate the target number of stocks in the account to be attributed to the employee account of the target client, update the number of stocks in the employee account according to the target number, transfer the target number of stocks in the account to be attributed to the attributed account, and update the number of stocks in the attributed account according to the target number, so that a partial stock quotation right deduction manner may be automatically implemented without manually modifying the number of stocks, thereby improving the security and accuracy of the quotation right data when the employee quotation right is performed, ensuring the security of the partial stock quotation right deduction manner, and saving the employee quotation right time and labor cost. In addition, the method for deducting part of the stock rights does not need to sell the stocks and does not need to sell the stocks to wait for the closing of the trade, so that the communication with a trading post is not needed, the processing cost of virtual resources is saved, the success rate of the rights of the stocks and the trading efficiency are ensured, the selling pressure of the sold stocks on prices is reduced, and the effect of reducing the number of times of stock increase can be achieved.

Furthermore, the server can realize the processing of each row right mode and the compatibility of a newly added row right mode such as a mode of deducting part of stock row rights by deriving the task nodes and configuring the execution sequence of each task node without additional development work, thereby improving the row right efficiency. Moreover, the server can freely arrange the task nodes, such as adjusting the content, sequence, number and the like of the task nodes, so as to realize the processing of different row right modes or different processing of the same row right mode.

Furthermore, the server can execute the task nodes based on the task processing engine and the message queue, so that asynchronous processing of different task nodes by the server is realized. For example, the message stored in the message queue may have a task result of "confirming the row right result" corresponding to the employee row right 1 and a task node of "deducting the row right fee" corresponding to the employee row right 2, so that the task processing engine may consume the two task nodes at the same time, thereby reducing the delay of the response to the target client and improving the processing capability of the server on the virtual resource.

In some implementation manners, as shown in fig. 11 (a), the target client may display the row right record of the employee in the row right record card, where the specifically displayed content of the page corresponds to the content displayed on the related page when the request for deducting the stock row right is sent, and details of the page are not repeated herein. After the target client sends a request for deducting the stock row right, namely after the order is submitted, the order state in the row right record card can be 'processing'; after the execution of the "stock-to-account" task node is completed, the "order status" can be "authorized" to indicate that the authorization is successful.

In some implementations, as shown in fig. 11 (b), the target client may display a rights progress bar on the rights record details page in the order of: submitting the rights, adjusting the tax, successfully executing the rights, and after the target client sends a request for deducting the rights of the stock, the 'submitting the rights of the line' can be 'lighted up', namely the progress is completed; after the enterprise administrator completes tax accounting and auditing, the tax adjustment can be lightened, namely the progress is completed; after the "stock-to-account" task node is completed, the "right of way success" can be "lighted up", i.e. the progress is completed. Meanwhile, the predicted deduction amount can be displayed on the page so as to show the predicted deduction stock number presented when the staff right issues the order, and backtracking is facilitated. It should be noted that the content specifically displayed on the row right record detail page corresponds to the display content of the related page when the request for deducting the stock row right is sent, and details are not described herein.

It should be noted that, in the embodiment of the present application, a dealer transaction software may be installed at the enterprise end, an enterprise administrator may view contents such as a dealer right record and a display field of a modified target client through a dealer right record page of the dealer transaction software at the enterprise end, and the server may be a server corresponding to the dealer transaction software at the enterprise end. The server can control the display condition of dealer trading software at the enterprise end, for example, the server can send data required to be displayed by the dealer trading software at the enterprise end to the dealer trading software at the enterprise end, and the dealer trading software at the enterprise end can display related pages according to the display data sent by the server.

In some implementations, as shown in fig. 12, the enterprise side may install dealer trading software, and the enterprise administrator may view the employee rights record through the employee rights record page of the dealer trading software of the enterprise side, wherein the rights management mode displayed on the employee rights record page may be added with "acquire stock-deduct part of the stock rights" to support the deduction part of the stock rights mode. Meanwhile, the right bank mode does not relate to stock selling, so that the values corresponding to fields related to selling, such as the selling average price, the selling total amount, the transaction cost, the income, the bargain state and the like, which are displayed on the staff right bank record page are all null values, and if the value is displayed as "-". Meanwhile, the employee row right record page can display the deduction/sale number so as to compatibly display the deduction number or the sale number corresponding to each row right mode under the field. After the dealer trading software at the enterprise acquires the click operation of the enterprise administrator on the "withholding balance", a popup window as shown in fig. 12 may be displayed to explain the calculation of the withholding balance to the enterprise administrator.

In some implementations, as shown in fig. 13, dealer trading software on the enterprise side may set the display logic, such as setting the content to be displayed on the target client, according to the selection operation of the enterprise administrator on the page with the display field set. The dealer trading software of the enterprise end can set the checking state of each field to be not checked, namely default checking is carried out, and then the dealer trading software of the enterprise end can obtain the selection operation of an enterprise administrator on each field to determine the content displayed on the target client.

It should be noted that, in the embodiment of the present application, a third party may install dealer trade software, an approver of the third party may view contents such as a screening right mode, a current link, and the like through a screening page of the dealer trade software of the third party, and the server may be a server corresponding to the dealer trade software of the third party. The server can control the display condition of the dealer trading software of the third party, for example, the server can send data which needs to be displayed by the dealer trading software of the third party to the dealer trading software of the third party, and the dealer trading software of the third party can display related pages according to the display data sent by the server. The dealer trading software of the third party may display related content based on Customer Relationship Management (CRM), where the CRM may be a LIT CRM, and the application is not limited thereto.

In some implementations, as shown in fig. 14, when the dealer trading software of the third party obtains the selection operation of the examining and approving personnel on the "right-of-bank mode" or the "current link", the contents and the sequence of the displayed right-of-bank mode or task node may be as shown in the figure.

In some implementations, as shown in fig. 15, the third party dealer transaction software displays the stock-deducting information, tax information, employee basic information, etc. on the task detail page, where the deduction amount shows the amount of the stock deduction for deducting part of the stock rights task, and the time displayed by the deduction time is the completion time of the "stock-to-account" task node.

The above "tax to account (tax deposited into attributed account)" task node and "CRM delivery confirmation/T +2 complete delivery" task node are described below:

in some implementations, as shown in fig. 16, the dealer transaction software of the third party may implement manual circulation of the "tax to account (tax to the attributed account)" task node based on the operation of the approver. The task node of "tax to account (tax to be deposited into the attributed account)" can be divided into two scenes: the tax needs to be settled and the tax does not need to be settled, when the tax does not need to be settled, the dealer trading software of the third party can acquire the clicking operation of the examining and approving personnel on the 'batch skipping', display a popup window as shown in fig. 16, and complete the task node after acquiring the clicking operation of the examining and approving personnel on the 'confirmation' button; when the taxes need to be settled, the dealer transaction software of the third party can confirm that the taxes are stored in the affiliated account, namely the affiliated custody account, then click operation of the examining and approving personnel on batch processing can be obtained, a popup window shown in fig. 16 is displayed, and after click operation of the examining and approving personnel on a confirmation button is obtained, funds are frozen, settlement task processing is waited to be established, and the task node is completed.

In some implementations, the association logic of the "CRM delivery acknowledgement/T +2 complete delivery" task node in each issue mode is shown in table 1. Wherein, since the way of deducting part of the stock rights does not involve selling stocks, i.e., money transaction, the "money" in table 1 is null "-", and the "goods" in table 1 represents stocks.

TABLE 1

In some implementations, the server may include an EBOS, and the server may complete the processing of the money and stock change during the execution of the rights task flow, i.e., complete the flow of money and stocks during the execution of the task nodes. As shown in fig. 17, for the "money" change, since the tax needs to be settled, the EBOS may generate a task of "tax adjustment (add)" in order to ensure that the settlement task can be created smoothly. It can be understood that, in the method of deducting partial stock rights, the server does not need to deduct taxes from employee accounts, the taxes need to be paid by enterprises, the server can firstly deposit the taxes paid by the enterprises into the attributed account, namely the attributed managed account, then create an aggregation task and initiate an aggregation process, specifically, after the task node of "tax to account (tax to account into the attributed account)" is executed, the EBOS can generate an entry for adding money, the amount is the tax amount of the rights-to-row task, and the amount is frozen, and the corresponding business type is "rights-to-row tax substituted deposit". When creating a tax settlement task, the EBOS may normally generate an add entry. For the goods change, after the EBOS determines that the task node of the stock-to-account is completed, the business type can add row right acquisition stocks and row right deduction stocks to support stock taking change, such as allocating the target amount of stocks in the account to be homed to staff accounts of the target client and transferring the target amount of stocks in the account to be homed to the account already homed.

In some implementations, the server may synchronize the above "money change" such as stock taking change with the target client, as shown in fig. 18, and a change may be displayed in the stock record page of the target client to keep the fund record, so as to solve the problem that the total cash amount of the target client changes to mislead employees in case of loss.

It should be noted that the page diagrams provided in the embodiments of the present application are all corresponding, and the information Icon explanation documents, popup documents, and other documents in each page diagram are all corresponding, which is not described in detail in the present application.

In some implementations, to ensure normal generation of the settlement task, to ensure normal flow of funds, such as the completion of a money order task by an enterprise administrator for this rehearsal mode, the server may subdivide the settlement task corresponding to the rehearsal task into two pieces as shown in table 2. For the first item, when the incentive procedure is time-consuming, the server can create a task with negative net settlement income, and when the net settlement income is 0, the task does not need to be created; for the second item, after the task node of "tax to account (tax to deposit into the attributed account)" is executed and completed, the server may create a task for tax settlement, and "settle and clear income" is the corresponding tax amount when the employee rights, and "tax" may be remarked at "remark".

TABLE 2

In some implementations, before S220 above, the server may obtain a request for modifying the row right sent by the target client before the end of the right-to-be-possible time, and update the target row weight number based on the request for modifying the row right. For example, the modify row right request may include a new row weight number, and the server may update the target row weight number based on the new row weight number. In this embodiment, the server may provide the staff with the opportunity to modify the row weight amount before the right-feasible time is over, and complete the processing of deducting part of the stock row weight manner according to the modified row weight amount, thereby improving the user experience.

In some implementation manners, before S220, the server may determine whether to acquire a revocation authority request sent by the target client before the end of the right-to-be-granted time, and if not, the server may allocate the target number of stocks in the account to be attributed to the employee account, update the number of stocks in the employee account according to the target number, transfer the target number of stocks in the account to be attributed to the attributed account, and update the number of stocks in the attributed account according to the target number; if the line right revocation request sent by the target client before the end of the right-possible time is obtained, the server can send a line right revocation success message to the target client. In this embodiment, the server may provide the employee with an opportunity to revoke the right before the end of the right-possible time, improving the user experience.

In some implementation manners, the server may further perform logical verification on the withholding stock right request before determining whether to acquire the revocation right request sent by the target client before the end of the feasible right time, and then, when the logical verification passes, the server may determine whether to acquire the revocation right request sent by the target client before the end of the feasible right time.

Illustratively, the server logically verifying the withholding stock right request may include at least one of: checking whether the weight number of the target row is smaller than the maximum feasible weight number; checking whether the stock market value corresponding to the target row weight quantity is more than or equal to the row weight cost; and checking whether the current time belongs to the feasible right time. For example, the server may perform a wind control check on the target row weight amount based on the ESOP, determine whether the check target row weight amount is smaller than the maximum feasible weight amount, and confirm that the logical check passes when the check target row weight amount is smaller than the maximum feasible weight amount. If the market value of the stock corresponding to the target row weight amount is smaller than the row weight cost, the server can determine that the row weight cost cannot be deducted after all stocks in the target row weight amount are deducted, and then can determine that the logic check fails and send a notification of the row weight failure to the target client. If the current time does not belong to the right-of-feasibility time, the server can determine that the check bit passes.

In some implementations, before S610, the server may obtain a request for modifying the row right sent by the target client before the end of the right-to-be-possible time, and update the target row weight number based on the request for modifying the row right. Here, similar to the above embodiment where the server obtains the request for modifying the row right before S220, the detailed description of the present application is omitted here.

In some implementations, before S610, the server may determine whether to acquire a revocation row right request sent by the target client before the end of the feasible right time, and if not, the server may execute S610. Here, similar to the above embodiment where the server obtains the request for modifying the right before S220, the detailed description of the present application is omitted here.

In some implementation manners, the server may include an access layer, a service layer, and a database layer, as shown in (a) in fig. 19, in the right-feasible time, the employee may place an order based on the employee terminal, e.g., the target client, that is, the target client may send a request for deducting the stock right to the server, after the access layer obtains the order placement request sent by the employee based on the target client, the access layer may forward the request to the service layer, and then, the service layer may check the request, where the checking method is described in the above embodiment, and details of the checking method are not described herein. Meanwhile, the service layer can process the data of the request, store the data in the request in a database as the row weight amount, finish the persistence of the row weight data and store the row weight record. Before the right-to-live time is over, as shown in (b) and (c) of fig. 19, the employee may change or remove the order based on the employee side, for example, the target client side, and the server may obtain a request corresponding to the change or removal of the order sent by the target client side, so as to implement the change or removal of the order. After the time of availability is over, the server may process the order: order status flow, funding of enterprise and employee accounts, taken position changes, etc. As shown in (d) in fig. 19, the background of the server may obtain the task to be processed at regular time, generate the message to be processed corresponding to the task node, and store the message to be processed in the message queue, and meanwhile, a consumer of the message queue, such as a task processing engine, may monitor the message queue, consume the message to be processed, and process each task node, and then, the task processing engine may update the task: and modifying the state of the task node, such as completed state, pending state and the like, and submitting the asset change, namely the money and goods change. In addition, the employee side, such as the target client, may send query data to the background of the server, and the background of the server may send the latest data to the employee side.

In some implementations, as shown in fig. 20, on the right of way T, the employee, e.g., the target client, sends the deduction stock right of way to the server, and then the server may create a task of deduction stock right of way, and after the right time is over, the server may confirm the result of the right of way, e.g., the number of right of way of this right of way of the employee, and at this time, the server may not hold the employee, e.g., not give stock to the employee. And then, on the right of execution T +1 day, the enterprise end can check the tax according to the tax completion condition of the staff, confirm whether to deduct cost and tax instead, and send the result to the server. Then, the server can process the deduction quantity according to whether the deduction cost is substituted and the tax, specifically, if the deduction cost is substituted, the server considers the tax when calculating the deduction quantity, otherwise, the server does not consider the tax; if the cost is deducted, the server considers the cost when calculating the deduction quantity, otherwise, the cost is not considered. Meanwhile, the server can calculate the deducted stock number according to the cost, tax deduction condition and closing price of the right of bank T. If the royalty fee is generated but the employee account has no funds, the server may set the funds in the employee account to a negative value or exempt the employee fee. The server may then leave the deducted stocks on the account to be attributed as inventory for subsequent distribution, such as subsequent incentive distribution to employees; transferring the difference between the stock of the remaining stock, namely the right-going quantity, and the stock of the deductive quantity to the attributed account, and updating the stock quantity in the attributed account according to the remaining stock number; distributing the residual stocks, namely the stocks with the target quantity, to the employee account, returning the final account quantity to the employee terminal, updating the stock quantity in the employee account according to the residual stock quantity, and adding goods to the employee account. It is understood that the determination of the deducted stock amount based on the deduction cost and tax result does not relate to whether the deduction amount is more or less complementary, i.e. the deducted stock amount determined in this way is accurate. In addition, before the enterprise end checks, for example, before tax amount checks, it needs to confirm in advance which way the employee completes the tax, i.e., the right-of-way cost for paying and the right-of-way for tax amount can be decided by the employee.

In some implementations, as shown in fig. 21, after the server processes the deduction partial stock right management mode, the employee may initiate a stock sale based on the employee side, such as the target client, and send a stock sale request to the server, where the stock sale may be the remaining stock allocated to the employee after the right management mode is completed, and then the server may execute a transaction, such as sending a stock sale request to the server corresponding to the transaction, in response to the stock sale request sent by the employee side. After the transaction is completed, the server may allocate funds, such as returning a transaction result to the employee, and perform a settlement process.

In some implementations, the embodiments of the present application further provide an inter-account stock flow situation in a manner of deducting a part of the stock rights under two scenarios: the method comprises a scheme of batch issuance/port stock inventory of the equity shares and a scheme of single issuance/port stock increase of the equity shares, wherein a mode of deducting partial stock rights can also be called a mode of deducting stock back flow to an incentive pool. For the first scenario, as shown in fig. 22, the stocks in the depository line/post house may be transferred to the ESOP default account and then stored into the account to be attributed, where the stored stock is the line weight minus the position taken in the account to be attributed. Then, after the employee initiates a mode of deducting the stock rights based on the employee end, the enterprise end can carry out tax accounting and verification, determine whether the cost is deducted or not, and send the result to the server, if the cost is deducted, the server can leave the deducted stock in the account to be attributed; if not, the server can transfer the stocks except the deduction cost to the affiliated account and add positions to the employee account. For the second scenario, as shown in fig. 23, the employee may send a request for deducting the rights of the stock line to the depository line/client based on the employee end, and then the depository line/client may transfer the stock stream to the ESOP default account and then store the stock stream in the account to be attributed, where the stock stream is the line weight minus the position taken in the account to be attributed. Then, the enterprise end can carry out tax calculation and verification, determine whether the cost is deducted by others, and send the result to the server, if deduct by others, the server can leave the deducted stock in the account to be attributed; if not, the server can leave the stocks except the deduction cost in the account to be attributed, the rest is used for allocation, position holding is added to the employee account, and the number of the allocated stocks is transferred to the account to be attributed. In addition, when the stock is only once transferred between the account to be attributed and the account to which the stock is attributed, only one added stock flow after deducting the row right and deducting the number of stocks in the account statement to which the stock is attributed/FTBOS flow.

As can be appreciated. Since the storage of the deducted stocks in the attributed accounts may cause reconciliation problems, such as unreasonable account funds during the confirmation of stock circulation, the enterprise is required to open the account to be attributed for storing the deducted stocks.

In some implementations, as shown in fig. 24, the server may include a front module, a middle platform, and an EBOS, and the server may set the front module, the middle platform, the employee-side display condition, and the enterprise-side display condition according to the setting logic shown in fig. 24, which is a specific setting method thereof. The setup content is similar to the above embodiments, and the details are not repeated herein.

It should be noted that, in the embodiments of the present application, related data such as the number of rights of a bank, the manner of rights of a bank, the cost, the profit, etc. are referred to, when the embodiments of the present application are applied to a specific product or technology, user permission, consent, or authorization needs to be obtained, and the collection, use, and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.

Fig. 25 is a schematic diagram of a row weight data processing apparatus 2500 in a stock right incentive according to an embodiment of the present application, and as shown in fig. 25, the apparatus 2500 includes:

a first obtaining module 2501, configured to obtain a request for deducting a stock right sent by a target client, where the request for deducting the stock right includes a target row weight amount;

the transfer module 2502 is configured to allocate the target amount of stocks in the account to be attributed to the employee account of the target client, update the amount of stocks in the employee account according to the target amount, transfer the target amount of stocks in the account to be attributed to the attributed account to the owned account, and update the amount of stocks in the attributed account according to the target amount;

the target quantity is determined by the target row weight quantity and the stock quantity used for deducting the row weight cost corresponding to the target row weight quantity, the account to be attributed is used for hosting stocks which are not actually distributed to the employees, and the account to be attributed is used for hosting stocks which are actually distributed to the employees.

In some implementations, the apparatus 2500 further includes: the system comprises a creation module 2503 and a configuration module 2504, wherein the creation module 2503 is used for creating at least one task node, and the at least one task node is used for distributing the stocks with the target quantity in the account to be attributed to the employee account, updating the stock quantity in the employee account according to the target quantity, transferring the stocks with the target quantity in the account to be attributed to the attributed account, and updating the stock quantity in the attributed account according to the target quantity; the configuration module 2504 is configured to configure an execution sequence of at least one task node; the binning module 2502 is specifically configured to execute at least one task node according to an execution order.

In some implementations, the binning module 2502 is specifically configured to poll at least one task node according to the execution sequence, and determine a target task node that needs to be executed in the at least one task node; generating a target message for executing a target task node, and storing the target message in a message queue; monitoring a message queue based on a task flow engine to obtain a target message; the target message is consumed based on the task flow engine to execute the target task node.

In some implementations, the at least one task node includes: determining the first bank right amount, deducting bank right commission charge, confirming bank right daily closing price, determining bank right tax, calculating target amount and stock transfer.

In some implementations, the apparatus 2500 further includes: the determining module 2505, the determining module 2505 is configured to determine whether to obtain a revocation row right request sent by the target client before the end of the right-possible time; the transfer module 2502 is specifically configured to, if a revocation authority request sent by the target client before the end of the right-to-live time is not obtained, allocate the target number of stocks in the account to be attributed to the employee account, update the number of stocks in the employee account according to the target number, transfer the target number of stocks in the account to be attributed to the account to which the stocks are attributed, and update the number of stocks in the account to which the stocks are attributed according to the target number.

In some implementations, the apparatus 2500 further includes: a sending module 2506, where the sending module 2506 is configured to send a row right revocation success message to the target client if a row right revocation request sent by the target client before the right-possible time is ended is obtained.

In some implementations, the apparatus 2500 further includes: the checking module 2507, the checking module 2507 is used for performing logic checking on the deduction stock right request; the binning module 2502 is specifically configured to, when the logic check passes, determine whether to acquire a revocation authority request sent by the target client before the end of the right-to-live time.

In some implementations, the check module 2507 is specifically configured to check whether the target row weight number is less than the maximum feasible weight number; checking whether the stock market value corresponding to the target row weight quantity is more than or equal to the row weight cost; and checking whether the current time belongs to the right-of-feasibility time.

In some implementations, the apparatus 2500 further includes: a second obtaining module 2508 and an updating module 2509, where the second obtaining module 2508 is configured to obtain a request for modifying the row right sent by the target client before the feasible right time is finished; the update module 2509 is used to update the target row weight amount based on the modify row weight request.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. To avoid repetition, further description is omitted here. Specifically, the apparatus 2500 shown in fig. 25 may perform the above method embodiments, and the foregoing and other operations and/or functions of each module in the apparatus 2500 are respectively for implementing corresponding flows in the above methods, and are not described herein again for brevity.

The apparatus 2500 of an embodiment of the present application is described above in connection with the figures from the perspective of a functional module. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in conjunction with the embodiments in the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps in the above method embodiments in combination with hardware thereof.

Fig. 26 is a schematic block diagram of an electronic device 2600 provided by an embodiment of the present application. As shown in fig. 26, the electronic device 2600 may comprise:

a memory 2610 and a processor 2620, the memory 2610 being configured to store computer programs and to transfer the program codes to the processor 2620. In other words, the processor 2620 may invoke and execute a computer program from the memory 2610 to implement the methods of the embodiments of the present application.

For example, the processor 2620 may be configured to perform the above-described method embodiments according to instructions in the computer program.

In some embodiments of the present application, the processor 2620 may include, but is not limited to:

general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

In some embodiments of the present application, the memory 2610 includes, but is not limited to:

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double Data Rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), SLDRAM (Synchronous link DRAM), and Direct Rambus RAM (DR RAM).

In some embodiments of the present application, the computer program can be divided into one or more modules, which are stored in the memory 2610 and executed by the processor 2620 to perform the methods provided herein. The one or more modules may be a series of computer program instruction segments capable of performing certain functions, the instruction segments being used to describe the execution of the computer program in the electronic device.

As shown in fig. 26, the electronic apparatus may further include:

a transceiver 2630, the transceiver 2630 can be connected to the processor 2620 or the memory 2610.

The processor 2620 may control the transceiver 2630 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 2630 may include a transmitter and a receiver. The transceiver 2630 may further include an antenna, and the number of the antennas may be one or more.

It should be understood that the various components in the electronic device are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The present application also provides a computer storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to perform the method of the above-described method embodiments. Alternatively, the present application also provides a computer program product containing instructions, which when executed by a computer, cause the computer to execute the method of the above method embodiment.

When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application occur, in whole or in part, when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the module is merely a logical division, and other divisions may be realized in practice, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.

Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. For example, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of processing row weight data in a stock right incentive, comprising:

acquiring a request for deducting the stock row right sent by a target client, wherein the request for deducting the stock row right comprises the weight amount of a target row;

allocating a target number of stocks in an account to be attributed to an employee account of the target client, updating the number of stocks in the employee account according to the target number, transferring the target number of stocks in the account to be attributed to an attributed account, and updating the number of stocks in the attributed account according to the target number;

the target quantity is determined by the target row weight quantity and the number of stocks used for deducting the row weight cost corresponding to the target row weight quantity, the account to be attributed is used for hosting stocks which are not actually distributed to the employees, and the account to be attributed is used for hosting stocks which are actually distributed to the employees.

2. The method of claim 1, wherein before allocating a target amount of stocks in the account to be attributed to the employee account of the target client, updating the amount of stocks in the employee account according to the target amount, transferring the target amount of stocks in the account to be attributed to the attributed account, and updating the amount of stocks in the attributed account according to the target amount, the method further comprises:

creating at least one task node, wherein the at least one task node is used for distributing the target amount of stocks in the account to be attributed to the employee account, updating the stock amount in the employee account according to the target amount, transferring the target amount of stocks in the account to be attributed to the account to the attributed account, and updating the stock amount in the attributed account according to the target amount;

configuring an execution order of the at least one task node;

the allocating the target amount of stocks in the account to be attributed to the employee account of the target client, updating the stock amount in the employee account according to the target amount, transferring the target amount of stocks in the account to be attributed to the account to an attributed account, and updating the stock amount in the attributed account according to the target amount comprises:

and executing the at least one task node according to the execution sequence.

3. The method of claim 2, wherein said executing the at least one task node according to the execution order comprises:

polling the at least one task node according to the execution sequence, and determining a target task node which needs to be executed in the at least one task node;

generating a target message for executing the target task node, and storing the target message in a message queue;

monitoring the message queue based on a task flow engine to obtain the target message;

consuming the target message based on the task flow engine to execute the target task node.

4. A method according to claim 2 or 3, wherein the at least one task node comprises: determining target bank amount, deducting bank right commission charge, confirming bank right daily closing price, determining bank right tax, calculating target amount and stock transfer.

5. The method according to any one of claims 1 to 3, wherein before allocating a target amount of stocks in the account to be attributed to the employee account of the target client, updating the amount of stocks in the employee account according to the target amount, transferring the target amount of stocks in the account to be attributed to the attributed account, and updating the amount of stocks in the attributed account according to the target amount, the method further comprises:

judging whether to acquire a revocation row right request sent by the target client before the feasible right time is finished;

the allocating the target amount of stocks in the account to be attributed to the employee account of the target client, updating the stock amount in the employee account according to the target amount, transferring the target amount of stocks in the account to be attributed to the employee account to the attributed account, and updating the stock amount in the attributed account according to the target amount includes:

if the revocation authority request sent by the target client before the end of the feasible authority time is not obtained, the target quantity of the stocks in the account to be attributed is distributed to the employee account, the stock quantity in the employee account is updated according to the target quantity, the target quantity of the stocks in the account to be attributed is transferred to the attributed account, and the stock quantity in the attributed account is updated according to the target quantity.

6. The method of claim 5, further comprising:

and if the line right revocation request sent by the target client before the feasible right time is finished is obtained, sending a line right revocation success message to the target client.

7. The method of claim 5, wherein before the determining whether to obtain the request for revoking the line right sent by the target client before the end of the feasible right time, further comprises:

performing logic verification on the request for deducting the stock row right;

the determining whether to acquire the revocation authority request sent by the target client before the end of the feasible authority time includes:

and when the logic check is passed, judging whether to acquire a revocation authority request sent by the target client before the end of the right-possible time.

8. The method of claim 7, wherein the logically verifying the request to deduct stock rights comprises at least one of:

checking whether the weight number of the target row is smaller than the maximum feasible weight number;

checking whether the stock market value corresponding to the target row weight quantity is more than or equal to the row weight cost;

and checking whether the current time belongs to the right-of-feasibility time.

9. The method according to any one of claims 1-3, wherein before allocating a target amount of stocks in an account to be homed into an employee account of the target client, updating the amount of stocks in the employee account according to the target amount, transferring the target amount of stocks in the account to be homed into an already homed account, and updating the amount of stocks in the already homed account according to the target amount, further comprising:

acquiring a line right modification request sent by the target client before the right-to-run time is finished;

updating the target row right quantity based on the modified row right request.

10. A row weight data processing apparatus in a stock right incentive, comprising:

the system comprises a first acquisition module, a first storage module and a second acquisition module, wherein the first acquisition module is used for acquiring a request for deducting the rights of a stock row sent by a target client, and the request for deducting the rights of the stock row comprises the weight amount of the target row;

the warehouse transferring module is used for distributing the target quantity of the stocks in the account to be attributed to the employee account of the target client, updating the quantity of the stocks in the employee account according to the target quantity, transferring the target quantity of the stocks in the account to be attributed to the account, and updating the quantity of the stocks in the account to be attributed according to the target quantity;

11. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the method of any of claims 1-9 via execution of the executable instructions.

12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of any one of claims 1 to 9.

13. A computer program product comprising instructions for causing an electronic device to perform the method of any of claims 1-9 when the computer program product is run on the electronic device.