CN116757862A - Billing method based on ESOP maturation log stream and storage medium - Google Patents
Billing method based on ESOP maturation log stream and storage medium Download PDFInfo
- Publication number
- CN116757862A CN116757862A CN202311046505.7A CN202311046505A CN116757862A CN 116757862 A CN116757862 A CN 116757862A CN 202311046505 A CN202311046505 A CN 202311046505A CN 116757862 A CN116757862 A CN 116757862A
- Authority
- CN
- China
- Prior art keywords
- log
- maturation
- date
- change event
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000035800 maturation Effects 0.000 title claims abstract description 154
- 238000000034 method Methods 0.000 title claims abstract description 60
- 230000008859 change Effects 0.000 claims abstract description 181
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims abstract description 165
- 230000001960 triggered effect Effects 0.000 claims abstract description 26
- 238000012544 monitoring process Methods 0.000 claims abstract description 10
- 230000010198 maturation time Effects 0.000 claims abstract description 9
- 238000010200 validation analysis Methods 0.000 claims description 32
- 238000004590 computer program Methods 0.000 claims description 5
- 230000001133 acceleration Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000005070 ripening Effects 0.000 description 4
- 230000002411 adverse Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 230000003111 delayed effect Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000002441 reversible effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000008014 freezing Effects 0.000 description 1
- 238000007710 freezing Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
Abstract
The invention relates to the technical field of stock right incentive, in particular to an ESOP mature log pipelining-based accounting method and a storage medium, wherein the ESOP mature log pipelining-based accounting method provided by the invention comprises the following steps: generating a basic mature log running water based on the effective time of the equity service; monitoring whether a triggering change event exists on the same day; if the change event is triggered, the time, state and quantity of stock maturation after the service effective date are updated according to the stock right task and the service effective date of the change event, and the stock maturation time, state and quantity are used as the current day maturation log stream; generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date; and displaying the daily snapshot data corresponding to the target date selected by the user. The method and the device can realize the view of the data record from the time view of the selected date, and avoid the change of the data to cover the data record of the original time view.
Description
Technical Field
The invention relates to the technical field of equity incentive, in particular to an ESOP maturation log pipelining-based accounting method and a storage medium.
Background
Some enterprises use the means of equity incentive, i.e. ESOP (Employee Stock Ownership Plans, corporate employee equity planning), to grant employees a certain number of corporate shares in a certain way, or to give employees the right to purchase corporate shares at a certain price over a certain period of time, etc. in order to incentivize and keep employees on the long-term evolution of the enterprise. The aim is to give rewards both from the point of view of rewards and from the point of view of the owners, thus achieving a long-term incentive for the staff.
The grant of existing equity incentives, etc. is typically handled on-line and accounting can be done directly on-line. However, the existing billing is usually one-dimensional billing, and if some item of stock right data is modified, the modified data will directly cover the original data, so that the original data before modification cannot be viewed.
Disclosure of Invention
In order to solve the problem that the original data cannot be checked due to direct coverage of the modified data after the modification of certain stock right data in the existing one-dimensional billing, the invention provides a billing method based on ESOP mature log pipelining and a storage medium.
The invention provides a billing method based on ESOP mature log running water, which comprises the following steps:
Generating a basic mature log running water based on the effective time of the equity service;
monitoring whether a triggering change event exists on the same day;
if the change event is triggered, the time, state and quantity of stock maturation after the service effective date are updated according to the stock right task and the service effective date of the change event, and the stock maturation time, state and quantity are used as the current day maturation log stream;
generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date;
and displaying the daily snapshot data corresponding to the target date based on the target date selected by the user.
Preferably, the equity service includes: grant validation service, special cancellation service, accelerated maturation service, deferred maturation service, maturation approval service, entitlement attribution service, outdated cancellation service, off-job termination service, and resume service.
Preferably, monitoring whether there is a trigger change event on the day specifically includes:
it is monitored whether there are varying events of time, status and quantity of stock maturation inserted for the equity task on the same day.
Preferably, if a change event is triggered, the time, state and number of stock maturation after the service validation date are updated according to the stock right task and the service validation date of the change event, and the stock maturation log stream is taken as the current day maturation log, which specifically includes:
If the change event is triggered, determining all basic mature log running water between the service effective date and the current day in the change event;
backtracking all basic mature log running water between the service effective date and the current day to backtrack to the original running water state when the service effective date is not changed before;
and executing the stock right business corresponding to the change event according to the original running water state, sequentially re-executing all operations between the business effective date and the current day, updating the time, state and quantity of stock maturation after the business effective date, generating a new basic maturation log running water, and taking the new basic maturation log running water as the current day maturation log running water.
Preferably, after the base mature log flowing before the triggering date of the change event and the current day mature log flowing corresponding to the triggering date generate corresponding daily snapshot data according to the dates respectively, the method further includes:
and starting a timing compensation task to regenerate the basic mature log flowing water of the non-generated daily snapshot into the corresponding daily snapshot.
Preferably, after the base mature log flowing before the triggering date of the change event and the current day mature log flowing corresponding to the triggering date generate corresponding daily snapshot data according to the dates respectively, the method further includes:
And carrying out delay checking on the daily snapshot data.
Preferably, the daily snapshot data is checked in a delayed manner, which specifically comprises the following steps:
judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot or not;
if yes, marking that the daily snapshot corresponding to the current change event is successful in checking account.
Preferably, after determining whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot, the method further includes:
if not, detecting whether the current day mature log flowing water corresponding to the triggering date of the change event has flowing water data in the daily snapshot which is not generated by the flowing water;
if not, marking that the daily snapshot corresponding to the current change event fails to account, and alarming.
Preferably, after detecting whether the current day mature log flowing water corresponding to the triggering date of the change event has flowing water data in the daily snapshot corresponding to the non-generated flowing water, the method further includes:
if yes, starting a delay compensation task, and enabling the current day mature log flowing water corresponding to the triggering date of the triggering change event to regenerate a corresponding new daily snapshot.
The present invention also provides a computer readable storage medium having a computer program stored thereon, which when executed by a processor implements an accounting method based on ESOP maturation log pipelining as defined in any one of the above.
Compared with the prior art, the billing method based on ESOP maturation log pipelining and the storage medium provided by the invention have the following advantages:
1. the embodiment of the invention provides an ESOP maturation log pipelining-based billing method, which comprises the following steps: generating a basic mature log running water based on the grant effective time of the equity service; monitoring whether a triggering change event exists on the same day; if the change event is triggered, the time, state and quantity of stock maturation after the service effective date are updated according to the stock right task and the service effective date of the change event, and the stock maturation time, state and quantity are used as the current day maturation log stream; generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date; and displaying the daily snapshot data corresponding to the target date based on the target date selected by the user. By generating the basic mature log stream with the effective time of the stock right service, the stock right service can specify the effective time of the task and can be reflected on the basic mature log stream, the basic mature log stream is ordered according to the occurrence time of the service, and a legal change event can be inserted at a certain moment, and the result synchronization caused by the change event affects the subsequent service. After triggering the change event, the time, state and quantity of stock maturation after the service effective date can be updated according to the service effective date in the change event and used as the current day maturation log stream; and generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date. The data before the triggering date and the data on the same day corresponding to the triggering date are independently generated according to the date so as to record and store, so that the change event triggered on the same day does not influence the snapshot on the same day generated before the triggering date, and a user can view the data record at the time from the time view of the selected target date according to the selected target date, and the change data is prevented from covering the original data record of the original time view.
2. In the embodiment of the invention, whether a trigger change event exists in the current day is monitored, which comprises the following steps: it is monitored whether there are varying events of time, status and quantity of stock maturation inserted for the equity task on the same day. By monitoring whether the time, state and quantity of stock maturation aiming at the stock right task change in the current day, whether a trigger change event exists in the current day or not is determined, and the change event is conveniently processed.
3. In the embodiment of the present invention, if a change event is triggered, the time, state and number of stock maturation after the service validation date are updated according to the stock right task and the service validation date of the change event, and the stock maturation time, state and number are used as the current day maturation log stream, which specifically includes: if the change event is triggered, determining all basic mature log running water between the service effective date and the current day in the change event; backtracking all basic mature log running water between the service effective date and the current day to backtrack to the original running water state when the service effective date is not changed before; and executing the stock right business corresponding to the change event according to the original running water state, sequentially re-executing all operations between the business effective date and the current day, updating the time, state and quantity of stock maturation after the business effective date, generating a new basic maturation log running water, and taking the new basic maturation log running water as the current day maturation log running water. Backtracking all basic mature log flowing water between the service effective date and the current day of the change event, executing tasks corresponding to the change event, re-executing all operations between the service effective date and the current day according to the backtracked original flowing water state to generate new basic mature log flowing water, and therefore the task goal of randomly inserting another change event to generate new basic mature log flowing water before a certain flowing water event and executing the change event according to the service effective time is achieved.
4. In the embodiment of the invention, after the base mature log flowing water before the triggering date of the change event and the current day mature log flowing water corresponding to the triggering date generate corresponding daily snapshot data according to the date respectively, the method further comprises the following steps: and starting a timing compensation task to regenerate the basic mature log flowing water of the non-generated daily snapshot into the corresponding daily snapshot. By starting the timing compensation task, the mature log running water which does not generate the daily snapshot is detected at fixed time, so that the mature log running water is prevented from being leaked, and the record of the daily snapshot is affected.
5. In the embodiment of the invention, the method for carrying out delayed account checking on the daily snapshot data specifically comprises the following steps: judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot or not; if yes, marking that the daily snapshot corresponding to the current change event is successful in checking account. After the change event is triggered, checking the generated daily snapshot is realized by judging whether the running water in the current day mature log running water corresponding to the trigger date of the change event is consistent with the running water data in the corresponding generated daily snapshot, so that whether the data of the generated daily snapshot is consistent with the data in the current day mature log running water corresponding to the trigger change event is convenient to detect, and errors in the current day daily snapshot data corresponding to the trigger date after the trigger change event are avoided, and the accuracy of the generated daily snapshot data is improved.
6. In the embodiment of the invention, after judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot, the method further comprises the following steps: if not, detecting whether the current day mature log flowing water corresponding to the triggering date of the change event has flowing water data in the daily snapshot which is not generated by the flowing water; if not, marking that the daily snapshot corresponding to the current change event fails to account, and alarming. The running water data in the corresponding daily snapshot is not generated by detecting that the data in the running water of the current day maturation log is inconsistent with the data in the corresponding daily snapshot, and the running water does not exist in the running water of the current day maturation log corresponding to the triggering date of the change event, namely the change event is indicated to have abnormality, so that an alarm is given, and the prompt of timely processing of staff is facilitated.
7. In the embodiment of the present invention, after detecting whether the current day mature log flowing water corresponding to the trigger date of the change event has flowing water data in the daily snapshot corresponding to the non-generated flowing water, the method further includes: if yes, starting a delay compensation task, and enabling the current day mature log flowing water corresponding to the triggering date of the triggering change event to regenerate a corresponding new daily snapshot. The real-time compensation is performed by starting the delay compensation task, so that after the change event is triggered, the corresponding new daily snapshot is regenerated by the current day mature log flowing water corresponding to the trigger date, the condition that the current day mature log flowing water is inconsistent with the data in the corresponding daily snapshot is avoided, and the accuracy of the data in the generated daily snapshot is further improved. In addition, the problem of inconsistent data after triggering a change event is solved in time, and further expansion of the problem or adverse effect on subsequent equity business is avoided.
8. The invention also provides a computer readable storage medium, which has the same beneficial effects as the billing method based on ESOP maturation log pipelining, and is not described herein.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of steps of a billing method based on ESOP maturation log pipeline according to a first embodiment of the present invention.
FIG. 2 is a flowchart showing the steps of a billing method based on ESOP maturation log stream according to the first embodiment of the present invention.
Fig. 3 is a flowchart showing steps of steps S421 and 422 of the billing method based on the ESOP maturation log pipeline according to the first embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples of implementation in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
The terms "vertical," "horizontal," "left," "right," "upper," "lower," "upper left," "upper right," "lower left," "lower right," and the like are used herein for illustrative purposes only.
Referring to fig. 1, a first embodiment of the present invention provides a billing method based on ESOP maturation log pipelining, which includes the following steps:
s10: generating a basic mature log running water based on the effective time of the equity service;
s20: monitoring whether a triggering change event exists on the same day;
s30: if the change event is triggered, the time, state and quantity of stock maturation after the service effective date are updated according to the stock right task and the service effective date of the change event, and the stock maturation time, state and quantity are used as the current day maturation log stream;
s40: generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date;
s50: and displaying the daily snapshot data corresponding to the target date based on the target date selected by the user.
As will be appreciated, the equity service refers to the relevant service performed by the equity authority in the ESOP after equity is awarded and the employee is awarded equity regarding the time, status and quantity of awarded equity. The creditor task has a service validation time, namely the creation time of the creditor service is not the service execution time, but is an operation validation time determined by the creditor service, and the operation validation time is the service validation time. The basic maturity log pipelining is to record the state and quantity of the stock maturity by taking the grant effective time as the starting point after determining the stock of the staff to be granted, and record the state and quantity of the stock maturity corresponding to each preset interval time according to the preset interval time. And the basic maturity log stream is also ordered according to the effective time of the equity business, so that the number and the state of the equity maturity of the staff are recorded. The number of the matured shares and the state change condition before and after the corresponding share right business is executed are completely recorded. For example: the preset interval time is 1 month, the today is 2021, 5, 18, 12, 1 in 2020, a grant is issued: calculation date: 2021, 1 month 1 day; ripening at uniform speed, and ripening 20% per month; grant number: 10000 strands. The basic mature log pipelining is: 2021.2.1:2000 strands are mature; 2021.3.1:2000 strands are mature; 2021.4.1:2000 strands are mature; 2021.5.1:2000 strands are mature; 2021.6.1:2000 immature strands.
It will be appreciated that daily snapshot data refers to a historical weight data snapshot, and that any point in time of the history may be selected and the data status of any point in time of the grant history may be viewed. Daily snapshot data includes, but is not limited to, current participant's up-to-date information, grant information, and stock summary information. If a change event exists, the latest information of the current participant is updated information of the current participant according to the change event; if the event is not changed, the information of the participators to the current date after the equity service in the event is originally granted is obtained. The grant information includes the maturity state and maturity number corresponding to the shares granted in each time stage. The information of the stock summary includes, but is not limited to, a summary of the maturation status and maturation quantity corresponding to the current stock corresponding to the selected target date.
It can be appreciated that, since the base mature log stream is ordered according to the effective time of the equity service, the equity service can specify the effective time of the task and can be embodied on the base mature log stream. By means of step S10, the base mature log stream is ordered according to the time of service occurrence, so that a legal change event can be inserted at a certain moment, and the result synchronization caused by the change event affects the subsequent equity service. Therefore, whether a change event is inserted at the moment can be monitored through the step S20, after the change event is triggered through the step S30, the time, the state and the number of stock matures after the service effective date in the current basic maturing log flowing water can be updated according to the service effective date in the change event, the stock matures as the current day maturing log flowing water, namely, the result generated by the change event occurring on the current day is recorded in the current day maturing log flowing water, and the basic maturing log flowing water before the triggering date of the change event and the current day maturing log flowing water corresponding to the triggering date respectively generate corresponding daily snapshot data according to the date through the step S40. The data before the triggering date and the data on the same day corresponding to the triggering date are independently generated according to the date so as to record and store, so that the change event triggered on the same day does not influence the snapshot on the same day generated before the triggering date, and therefore, through the step S50, a user can view the data record at that time from the time view of the selected target date according to the selected target date, and the change data is prevented from covering the original data record of the original time view. In addition, four-dimensional billing can be realized through the steps S10 to S50.
It will be appreciated that. In step S50, the target date selected by the user may be a daily snapshot of a single day selected for viewing, or a date range may be specified to display corresponding daily snapshot data of multiple days within the date range, which is not limited in this embodiment, and is determined according to the requirement of the user.
It should be noted that, the four-dimensional time accounting implemented in this embodiment is to add a start time dimension and an end time dimension on the basis of the two-dimensional snapshot, that is, on the basis of the service time and the operation time.
In particular, the operation time and the service validation time are the same, i.e. no additional support is required for this scenario now.
The service validation time in the event of operation time less than service validation, i.e. change, is in the future. For example, the expiration date is 5 months 13 days, i.e., the future time, then when the user selects 5 months 13 days, the number of possible expiration of 5 months 13 days should be subtracted from the current daily snapshot.
When the operation time is longer than the service effective time, that is, the service effective time in the change event is in the past, the daily snapshot needs to be recorded through the two-dimensional time.
Specifically, one dimension: the traffic occurrence period. For example, when a change event occurs at the time of 4 months and 13 days, a grant of 3 months and 13 days for maturity is recorded, and then the business occurrence time period is 3 months and 13 days to 3 months and 14 days.
Two-dimensional: operation time and snapshot end time, for example: and generating a grant on 13 days of 3 months, generating a corresponding daily snapshot at the moment, wherein the operation time is the current time, the daily snapshot ending time is infinite time, and if a change event occurs on the same day, and the service effective time of the change event is the current time, executing the stock right service corresponding to the change event, and directly recording the daily snapshot on the same day. If the next and subsequent days are reached, a change event is triggered, and the equity validation time of the equity service in the change event is prior to today. If the current time is 4 months 13 days, the pen is granted with a 3 months 13 day cancel operation, and the snapshot ending time of the daily snapshot of the 3 months 13 days before the update is required is the current time, namely 4 months 13 days. Then a new snapshot record of the equity service for the change event is created about 3 months 13 days, the operation time of the new snapshot record is still the current time, namely 4 months 13 days, and the snapshot ending time is infinite. Because of the equity service in the execution change event of 3 months 13 days, the same update processing needs to be done for all snapshots granted by the pen after 3 months 13 days. Thereby enabling support for insertion in past scenes and generation of new data while preserving the original data of the original historical temporal perspective.
In some cases, historical rights data of employees of a company are imported. For example, an operation of generating a basic mature log stream is not performed before a certain company, a daily snapshot is not generated, and the operation is performed now to generate a daily snapshot, so that the historical line weight data of the company is imported to the present day, that is, the transaction data of the company is accessed to the basic mature log stream in this embodiment, so that the real line weight date recorded in the basic mature log stream is the order time, that is, the line weight freezing time, and the situation that when the historical line weight data is imported, the line weight time recorded in the basic mature log stream is the order time requested by the transaction side, and the line weight time is not the real line weight date, and conflicts are caused after the expiration date is avoided. For example: the expiration date of the maturation log is 2023 month 6 and 30 days, and all the viable weights on the maturation log are cancelled due to expiration after exceeding 2023 month 6 and 30 days, but the actual viable weight date of the company is 2023 month 6 and 15 days when the company is introduced in 2023 month 7 and 1 day, if the transaction data of the company is not accessed into the basic maturation log stream, the viable weights recorded according to the basic maturation log stream at 2023 month 7 and 1 day are taken as the basis for judging whether an order can be created, and the creation is impossible. After the base mature log is accessed to the running water, the feasible weight of the line weight day 2023, 6, 15 is taken as the basis for judging and determining whether the order can be created, and the creation is successful. Therefore, by accessing the transaction data of the company into the basic mature log stream in the embodiment, the historical row weight data is inserted, and the data of the original historical time view angle is reserved.
Further, the equity service includes: grant validation service, grant maturation service, terminate cancel service, expire cancel service, special cancel service, maturation approval service, speed up maturation service, delay maturation service, and resume service.
It is understood that equity tasks include, but are not limited to, granting validation services, special cancellation services, accelerated maturation services, deferred maturation services, maturation approval services, line rights attribution services, outdated cancellation services, off-job termination services, and re-job restoration services. The equity tasks may also include: a line right attribution service, an off-office termination service, and the like. In this embodiment, in step S10, the basic maturation log is generated according to the grant validation time of the grant validation service, so that it can be known whether a certain employee is granted shares, when shares are granted, when the granted shares are matured, what number of shares are matured at that time, and so on.
Specifically, the service validation time granted to the maturity service is 0 point 0 minutes 0 seconds of the maturity date. If the date of maturation granted is 6 months 1 day, then the "mature" number is increased at 0 minutes 0 seconds at 6 months 1 day 0, and can be found in the daily snapshot.
Specifically, the service validation time for terminating the cancellation service is 0 minutes and 0 seconds at the 0 th day of the termination date. If the expiration date granted is 6 months 1 day, then the number of expiration is increased at 0 minutes 0 seconds at 6 months 2 days 0, and can be found in the daily snapshot. And if the "expiration date" is set before the "maturation date", the "mature" grant stage is changed to "immature" and is terminated.
Specifically, the service validation time of the expiration cancellation service is 0 minutes and 0 seconds at the 0 th day of the expiration date. If the expiration date granted is 6 months 1 day, the number of expired dates is increased at 0 minutes 0 seconds at 2 days 6 months and can be found in the daily snapshot.
Specifically, the special cancellation service is to cancel the number of granted shares mature for some special cases, and the service effective time of the special cancellation service is year, month, day, minute and second.
It should be noted that, the service effective time of the special cancellation service needs to satisfy a certain condition. First, if a company has not previously performed an operation of generating a basic mature log pipeline to generate a daily snapshot, the operation is now performed to generate a daily snapshot, so that the historical line weight data of the company needs to be imported today, thereby generating a basic log pipeline. At this time, the service validation time of the special cancellation service, that is, the special cancellation time must be after the latest date of both the basic mature log pipeline date and the grant start date, and must be today and before. Second, grant of validation is granted after the daily snapshot is online, special cancellation times must be after the earliest of the grant validation date, the calculation date, and must be today and before. Third, if the current maturity stage is in the "terminated" or "expired" state, then the page is specially canceled: at most 0 can be specifically cancelled. Fourth, special cancellation services are performed on the immature stage, and the special cancellation time can only be limited before the "mature date" of this stage. Fifth, if a special cancel time is selected before the maturation date, then "mature" will be changed to "immature" and the corresponding number of "immature" numbers will be specifically canceled. For example; for example: the preset interval time is 1 month, the today is 2021, 5, 18, 12, 1 in 2020, a grant is issued: calculation date: 2021, 1 month 1 day; ripening at uniform speed, and ripening 20% per month; grant number: 10000 strands. The basic mature log pipelining is: 2021.2.1:2000 strands are mature; 2021.3.1:2000 strands are mature; 2021.4.1:2000 strands are mature; 2021.5.1:2000 strands are mature; 2021.6.1:2000 immature strands. Today: 2021.5.18, operating "special cancellation", service validation date of special cancellation is 2021.3.3, three phases 2021.4.1, 2021.5.1, 2021.6.1 will be all special cancellation, data 3.3 days and later in the daily snapshot viewed today: the data granted for this bar are: mature 4000 and cancel 6000.
Specifically, the maturity approval service is to grant no change to the original maturity date. After approval, the number of matures granted will increase by 0 minutes and 0 seconds at 0 on the day of the date of maturation. For example: maturation date: 5 months 1 day, mature number 2000. If the maturation approval business is required, if the maturation approval business is not completed after 5 months and 1 day, looking up the data before today, wherein the maturation quantity is 0; if the maturity approval passes on any day after 5 months and 1 day, the report is queried, and the matured quantity 2000 can be obtained from 5 months and 1 day. Independent of maturation approval time.
In particular, if a certain stage is granted that a "special cancel" is operated, the service validation time to accelerate maturation must be on and after the latest "special cancel" time and today and before. For example: granting 1000 strands, 8.1 mature 500 strands; 9.1 mature 500 strands. And (3) specially cancelling 400 strands in 8.1 stage in 7 months and 15 days, wherein the accelerated maturation in 8.1 stage can only select 7 months and 15 days after the accelerated maturation, and the number of the mature strands is 500-400=100 strands, namely, firstly performing 'special cancelling' business and then executing the maturation action. Regarding acceleration of maturation, if 100 strands were accelerated and decelerated to 1 day of 6 months in 2020, 50 strands were accelerated and decelerated. The immature number 50 strands is specifically cancelled. First, if today 7.18, accelerated maturation is noted at 6.18, i.e., before today, then the special cancel time is 23 of 6.17: 59:59, the first second of maturation day to accelerate maturation, 23:59:59. if today 7.18, the accelerated maturation label is 8.18, i.e. after today, then the special cancellation is the first second of the current operation time. The full acceleration and deceleration synchronous limit, the acceleration and deceleration mature time must be informed to the front end by the rear end on and after the latest special cancel time granted by the front end, the rear end and the front end are both subjected to relevant limit, and the front end can not place ash on the selected date. And full acceleration matures, if any, to a point where no acceleration can be performed. The effect is that the success of acceleration can be accelerated, and the success of acceleration cannot be accelerated, but the success cannot be accelerated but is not prompted.
Specifically, in the resume service, if the resume history is selected to leave the time of resume, the values of cancellation and expiration cancellation are terminated. Then the "expiration date" and "expiration date upon departure" granted to the maturity journal will be reversed and the number of expired or terminated due to departure will be restored.
It should be noted that, the resume business is to eliminate the influence caused by the job departure in the reverse direction, and not to return the corresponding numerical value to the staff on the resume day. For example: grant phase one: maturation date 6 month 1 day, 2000 strands; grant stage two: maturation date 7 months 1 day, 1000 strands. And after the operation is carried out off for 7 months and 1 day, the data of 16 days and later of 6 months are inquired, the expiration number is 2000 strands, and the expiration number is 1000 strands. If the resume service is operated and the grant is resumed, the resume date is marked 8 months 1 day, then the data today, i.e. 8 months 13 days and before, is viewed without an expiration number and a termination number. Rather than the number of expired and terminated after the re-use day, i.e., 8 months 1 day or the re-use operation day.
Further, step 20 specifically includes:
s201: it is monitored whether there are varying events of time, status and quantity of stock maturation inserted for the equity task on the same day.
It will be appreciated that each equity service will cause a change in the time, status and quantity of the granted equity, and if at least one of the time, status and quantity of the granted equity changes, a change event can be determined to occur on the same day. After determining that a change event occurs, determining a specific equity service, thereby determining the service validation time of the equity service in the change event.
Referring to fig. 2, further, step S30 specifically includes:
s301: if the change event is triggered, determining all basic mature log running water between the service effective date and the current day in the change event;
s302: backtracking all basic mature log running water between the service effective date and the current day to backtrack to the original running water state when the service effective date is not changed before;
s303: and executing the stock right business corresponding to the change event according to the original running water state, sequentially re-executing all operations between the business effective date and the current day, updating the time, state and quantity of stock maturation after the business effective date, generating a new basic maturation log running water, and taking the new basic maturation log running water as the current day maturation log running water.
It will be appreciated that, if the change event is triggered, in step S301, all the basic mature log flowing between the service effective date and the current day in the change event is determined first, that is, all the stock right services executed between the service effective date and the current day are determined. And through step S302, backtracking is performed on all the basic mature log running water between the service effective date and the current day, so as to backtrack to the original running water state when the service effective date is unchanged. And backtracking the operation corresponding to the ownership business between the business effective date and the current day to backtrack to the original running state corresponding to the corresponding historical ownership business before the operation corresponding to the ownership business between the non-execution business effective date and the current day. And through step S303, after the change event is inserted into the equity service corresponding to the original running state, the operation corresponding to the equity service of the change event is executed, and the time, state and number of equities corresponding to the service validation date after the equity service of the change event is executed are obtained. And on the basis of the change event, sequentially re-executing the operation corresponding to all the stock right businesses between the business effective date and the current day so as to update the time, state and quantity of stock maturation after the business effective date, generate new basic maturation log running water, and take the new basic maturation log running water as the current day maturation log running water. And when the new basic maturation log stream is taken as the current day maturation log stream, the original current day maturation log stream marks the failure state. Therefore, the task target of inserting another change event before a certain equity service to generate a new basic mature log stream and executing according to the service effective time to obtain the change event is realized. In addition, the change condition of the stock number of the operation can be recorded from the dimension of the mature log.
Further, in step S40, the method further includes:
s41: and starting a timing compensation task to regenerate the basic mature log flowing water of the non-generated daily snapshot into the corresponding daily snapshot.
It can be understood that the timing compensation task refers to checking whether the base mature log flowing water is missing or not at intervals of preset time, so that no daily snapshot is generated, if yes, the base mature log flowing water of the non-generated daily snapshot is regenerated to generate the corresponding daily snapshot, so as to realize compensation, so that the mature log flowing water of the non-generated daily snapshot is detected at fixed time, and the situation that the mature log flowing water is missing is avoided, so that the record of the daily snapshot is affected.
Further, after step S40, the method further includes:
s42: and carrying out delay checking on the daily snapshot data.
It can be appreciated that after the daily snapshot data is generated, the daily snapshot data and the basic mature log stream corresponding to the daily snapshot data are checked, so that errors of the generated snapshot data are avoided.
Referring to fig. 3, further, step SS42 specifically includes:
s421: judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot or not;
S422: if yes, marking that the daily snapshot corresponding to the current change event is successful in checking account.
It can be appreciated that, after the change event is triggered, whether the running water in the current day mature log running water corresponding to the trigger date of the change event is consistent with the running water data in the corresponding generated daily snapshot is determined in step S421, so as to reconcile the generated daily snapshot, and thus, it is convenient to detect whether the data of the generated daily snapshot is consistent with the data in the current day mature log running water corresponding to the trigger change event. Through step S422, if the current day mature log flowing water corresponding to the trigger date of the change event is consistent with the corresponding generated daily snapshot, the time delay accounting success can be marked. Therefore, the occurrence of errors of the daily snapshot data of the same day corresponding to the trigger date after the trigger change event is avoided, and the accuracy of the generated daily snapshot data is improved.
It should be noted that the specific detected data is focused on whether the time, state and quantity of the awarded stock maturation are consistent.
Referring to fig. 3, further, after step S421, the method further includes:
s423: if not, detecting whether the current day mature log flowing water corresponding to the triggering date of the change event has flowing water data in the daily snapshot which is not generated by the flowing water;
S424: if not, marking that the daily snapshot corresponding to the current change event fails to account, and alarming.
It can be appreciated that, in step S423, when it is detected that the data in the current day mature log running water is inconsistent with the data in the corresponding daily snapshot, and that no running water in the corresponding daily snapshot is generated in the current day mature log running water corresponding to the trigger date of the change event is detected, the present reconciliation is marked as failed. The abnormal condition of the inconsistent condition of the current daily snapshot data and the corresponding basic mature log flowing water is indicated, which is probably caused by the fault of a system for executing operation, so that the abnormal condition of the current change event is indicated, the alarm can be given, the staff can be conveniently prompted to process in time, the fault is removed in time, and the daily snapshot generation after the influence is avoided.
Referring to fig. 3, further, after step S423, the method further includes:
s425: if yes, starting a delay compensation task, and enabling the current day mature log flowing water corresponding to the triggering date of the triggering change event to regenerate a corresponding new daily snapshot.
It can be appreciated that if the data in the current day maturation log pipeline is detected to be inconsistent with the data in the corresponding daily snapshot, and the data in the corresponding daily snapshot is not generated in the current day maturation log pipeline corresponding to the triggering date of the change event is detected, the delay compensation task can be started to perform real-time compensation. After the triggering change event, the corresponding new daily snapshot is regenerated by the current day maturation log flowing water corresponding to the triggering date, so that the situation that the current day maturation log flowing water is inconsistent with the data in the corresponding daily snapshot is avoided, and the accuracy of the data in the generated daily snapshot is further improved. In addition, the problem of inconsistent data after triggering a change event is solved in time, and further expansion of the problem or adverse effect on subsequent equity business is avoided.
A second embodiment of the present invention provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a billing method based on ESOP maturation log pipelining as described in the first embodiment.
In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Those skilled in the art will also appreciate that the embodiments described in the specification are alternative embodiments and that the acts and modules referred to are not necessarily required for the present invention.
In various embodiments of the present application, it should be understood that the sequence numbers of the foregoing processes do not imply that the execution sequences of the processes should be determined by the functions and internal logic of the processes, and should not be construed as limiting the implementation of the embodiments of the present application.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, with the determination being made based upon the functionality involved. It will be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Compared with the prior art, the billing method based on ESOP maturation log pipelining and the storage medium provided by the invention have the following advantages:
1. the embodiment of the invention provides an ESOP maturation log pipelining-based billing method, which comprises the following steps: generating a basic mature log running water based on the grant effective time of the equity service; monitoring whether a triggering change event exists on the same day; if the change event is triggered, the time, state and quantity of stock maturation after the service effective date are updated according to the stock right task and the service effective date of the change event, and the stock maturation time, state and quantity are used as the current day maturation log stream; generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date; and displaying the daily snapshot data corresponding to the target date based on the target date selected by the user. By generating the basic mature log stream with the effective time of the stock right service, the stock right service can specify the effective time of the task and can be reflected on the basic mature log stream, the basic mature log stream is ordered according to the occurrence time of the service, and a legal change event can be inserted at a certain moment, and the result synchronization caused by the change event affects the subsequent service. After triggering the change event, the time, state and quantity of stock maturation after the service effective date can be updated according to the service effective date in the change event and used as the current day maturation log stream; and generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date. The data before the triggering date and the data on the same day corresponding to the triggering date are independently generated according to the date so as to record and store, so that the change event triggered on the same day does not influence the snapshot on the same day generated before the triggering date, and a user can view the data record at the time from the time view of the selected target date according to the selected target date, and the change data is prevented from covering the original data record.
2. In the embodiment of the invention, whether a trigger change event exists in the current day is monitored, which comprises the following steps: it is monitored whether there are varying events of time, status and quantity of stock maturation inserted for the equity task on the same day. By monitoring whether the time, state and quantity of stock maturation aiming at the stock right task change in the current day, whether a trigger change event exists in the current day or not is determined, and the change event is conveniently processed.
3. In the embodiment of the present invention, if a change event is triggered, the time, state and number of stock maturation after the service validation date are updated according to the stock right task and the service validation date of the change event, and the stock maturation time, state and number are used as the current day maturation log stream, which specifically includes: if the change event is triggered, determining all basic mature log running water between the service effective date and the current day in the change event; backtracking all basic mature log running water between the service effective date and the current day to backtrack to the original running water state when the service effective date is not changed before; and executing the stock right service corresponding to the change event according to the original running water state, sequentially re-executing all operations between the service effective date and the current day, updating the time, state and quantity of stock maturation after the service effective date, generating a new basic maturation log running water, and taking the new basic maturation log running water as the current day maturation log running water. Backtracking all basic mature log flowing water between the service effective date and the current day of the change event, executing tasks corresponding to the change event, re-executing all operations between the service effective date and the current day according to the backtracked original flowing water state to generate new basic mature log flowing water, and therefore the task goal of randomly inserting another change event to generate new basic mature log flowing water before a certain flowing water event and executing the change event according to the service effective time is achieved.
4. In the embodiment of the invention, after the base mature log flowing water before the triggering date of the change event and the current day mature log flowing water corresponding to the triggering date generate corresponding daily snapshot data according to the date respectively, the method further comprises the following steps: and starting a timing compensation task to regenerate the basic mature log flowing water of the non-generated daily snapshot into the corresponding daily snapshot. By starting the timing compensation task, the mature log running water which does not generate the daily snapshot is detected at fixed time, so that the mature log running water is prevented from being leaked, and the record of the daily snapshot is affected.
5. In the embodiment of the invention, the method for carrying out delayed account checking on the daily snapshot data specifically comprises the following steps: judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot or not; if yes, marking that the daily snapshot corresponding to the current change event is successful in checking account. After the change event is triggered, checking the generated daily snapshot is realized by judging whether the running water in the current day mature log running water corresponding to the trigger date of the change event is consistent with the running water data in the corresponding generated daily snapshot, so that whether the data of the generated daily snapshot is consistent with the data in the current day mature log running water corresponding to the trigger change event is convenient to detect, and errors in the current day daily snapshot data corresponding to the trigger date after the trigger change event are avoided, and the accuracy of the generated daily snapshot data is improved.
6. In the embodiment of the invention, after judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot, the method further comprises the following steps: if not, detecting whether the current day mature log flowing water corresponding to the triggering date of the change event has flowing water data in the daily snapshot which is not generated by the flowing water; if not, marking that the daily snapshot corresponding to the current change event fails to account, and alarming. The running water data in the corresponding daily snapshot is not generated by detecting that the data in the running water of the current day maturation log is inconsistent with the data in the corresponding daily snapshot, and the running water does not exist in the running water of the current day maturation log corresponding to the triggering date of the change event, namely the change event is indicated to have abnormality, so that an alarm is given, and the prompt of timely processing of staff is facilitated.
7. In the embodiment of the present invention, after detecting whether the current day mature log flowing water corresponding to the trigger date of the change event has flowing water data in the daily snapshot corresponding to the non-generated flowing water, the method further includes: if yes, starting a delay compensation task, and enabling the current day mature log flowing water corresponding to the triggering date of the triggering change event to regenerate a corresponding new daily snapshot. The real-time compensation is performed by starting the delay compensation task, so that after the change event is triggered, the corresponding new daily snapshot is regenerated by the current day mature log flowing water corresponding to the trigger date, the condition that the current day mature log flowing water is inconsistent with the data in the corresponding daily snapshot is avoided, and the accuracy of the data in the generated daily snapshot is further improved. In addition, the problem of inconsistent data after triggering a change event is solved in time, and further expansion of the problem or adverse effect on subsequent equity business is avoided.
8. The invention also provides a computer readable storage medium, which has the same beneficial effects as the billing method based on ESOP maturation log pipelining, and is not described herein.
The foregoing describes in detail a billing method and a storage medium based on ESOP maturation log pipelining, which are disclosed in the embodiments of the present invention, and specific examples are applied to illustrate the principles and embodiments of the present invention, and the above description of the embodiments is only for helping to understand the method and core ideas of the present invention; meanwhile, as for those skilled in the art, according to the idea of the present invention, there are changes in the specific embodiments and the application scope, and in summary, the present disclosure should not be construed as limiting the present invention, and any modifications, equivalent substitutions and improvements made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. An ESOP maturation log pipelining-based accounting method is characterized in that: the method comprises the following steps:
generating a basic mature log running water based on the effective time of the equity service;
monitoring whether a triggering change event exists on the same day;
if the change event is triggered, the time, state and quantity of stock maturation after the service effective date are updated according to the stock right task and the service effective date of the change event, and the stock maturation time, state and quantity are used as the current day maturation log stream;
Generating corresponding daily snapshot data according to the date respectively by the basic maturation log flowing water before the triggering date of the change event and the current day maturation log flowing water corresponding to the triggering date;
and displaying the daily snapshot data corresponding to the target date based on the target date selected by the user.
2. The ESOP maturation log pipeline based billing method of claim 1 wherein: the equity service includes: grant validation service, special cancellation service, accelerated maturation service, deferred maturation service, maturation approval service, entitlement attribution service, outdated cancellation service, off-job termination service, and resume service.
3. The ESOP maturation log pipeline based billing method of claim 1 wherein: monitoring whether a triggering change event exists on the same day specifically comprises the following steps:
it is monitored whether there are varying events of time, status and quantity of stock maturation inserted for the equity task on the same day.
4. The ESOP maturation log pipeline based billing method of claim 1 wherein: if a change event is triggered, updating the time, state and number of stock maturation after the service validation date according to the stock right task and the service validation date of the change event, and taking the stock maturation time, state and number as the current day maturation log stream, wherein the method specifically comprises the following steps:
If the change event is triggered, determining all basic mature log running water between the service effective date and the current day in the change event;
backtracking all basic mature log running water between the service effective date and the current day to backtrack to the original running water state when the service effective date is not changed before;
and executing the stock right business corresponding to the change event according to the original running water state, sequentially re-executing all operations between the business effective date and the current day, updating the time, state and quantity of stock maturation after the business effective date, generating a new basic maturation log running water, and taking the new basic maturation log running water as the current day maturation log running water.
5. The ESOP maturation log pipeline based billing method of claim 1 wherein: after the base maturation log flowing before the triggering date of the change event and the current day maturation log flowing corresponding to the triggering date are respectively generated into corresponding daily snapshot data according to the date, the method further comprises the steps of:
and starting a timing compensation task to regenerate the basic mature log flowing water of the non-generated daily snapshot into the corresponding daily snapshot.
6. The ESOP maturation log pipeline based billing method of claim 1 wherein: after the base maturation log flowing before the triggering date of the change event and the current day maturation log flowing corresponding to the triggering date are respectively generated into corresponding daily snapshot data according to the date, the method further comprises the steps of:
And carrying out delay checking on the daily snapshot data.
7. The ESOP maturation log pipeline based billing method of claim 6 wherein: the method for carrying out delay account checking on the daily snapshot data specifically comprises the following steps:
judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot or not;
if yes, marking that the daily snapshot corresponding to the current change event is successful in checking account.
8. The ESOP maturation log pipeline based billing method of claim 7 wherein: after judging whether the current day mature log flowing water corresponding to the triggering date of the change event is consistent with the corresponding generated daily snapshot, the method further comprises the following steps:
if not, detecting whether the current day mature log flowing water corresponding to the triggering date of the change event has flowing water data in the daily snapshot which is not generated by the flowing water;
if not, marking that the daily snapshot corresponding to the current change event fails to account, and alarming.
9. The ESOP maturation log pipeline based billing method of claim 8 wherein: after detecting whether the running data in the daily snapshot corresponding to the running failure generation of the running exists in the current day mature log running corresponding to the triggering date of the change event, the method further comprises:
If yes, starting a delay compensation task, and enabling the current day mature log flowing water corresponding to the triggering date of the triggering change event to regenerate a corresponding new daily snapshot.
10. A computer-readable storage medium having stored thereon a computer program, characterized by: the computer program, when executed by a processor, implements a billing method based on ESOP maturation log pipelining as defined in any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311046505.7A CN116757862B (en) | 2023-08-18 | 2023-08-18 | Billing method based on ESOP maturation log stream and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311046505.7A CN116757862B (en) | 2023-08-18 | 2023-08-18 | Billing method based on ESOP maturation log stream and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116757862A true CN116757862A (en) | 2023-09-15 |
| CN116757862B CN116757862B (en) | 2023-12-08 |
Family
ID=87957593
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311046505.7A Active CN116757862B (en) | 2023-08-18 | 2023-08-18 | Billing method based on ESOP maturation log stream and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116757862B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110990890A (en) * | 2019-11-29 | 2020-04-10 | 山东爱城市网信息技术有限公司 | Block chain-based stock right incentive record management method, equipment and medium |
| CN112288559A (en) * | 2020-11-06 | 2021-01-29 | 平安数字信息科技(深圳)有限公司 | Financial data accounting method, device, equipment and storage medium based on equity |
| WO2021061173A1 (en) * | 2019-12-04 | 2021-04-01 | Futurewei Technologies, Inc. | Data integrity validation on lsm tree snapshots |
| CN114463135A (en) * | 2021-12-24 | 2022-05-10 | 上海金仕达软件科技有限公司 | Stock right management method, system, device, equipment, storage medium and program product |
| CN115033578A (en) * | 2021-03-03 | 2022-09-09 | 腾讯科技（深圳）有限公司 | Method for updating service data, related device and storage medium |
-
2023
- 2023-08-18 CN CN202311046505.7A patent/CN116757862B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110990890A (en) * | 2019-11-29 | 2020-04-10 | 山东爱城市网信息技术有限公司 | Block chain-based stock right incentive record management method, equipment and medium |
| WO2021061173A1 (en) * | 2019-12-04 | 2021-04-01 | Futurewei Technologies, Inc. | Data integrity validation on lsm tree snapshots |
| CN112288559A (en) * | 2020-11-06 | 2021-01-29 | 平安数字信息科技(深圳)有限公司 | Financial data accounting method, device, equipment and storage medium based on equity |
| CN115033578A (en) * | 2021-03-03 | 2022-09-09 | 腾讯科技（深圳）有限公司 | Method for updating service data, related device and storage medium |
| CN114463135A (en) * | 2021-12-24 | 2022-05-10 | 上海金仕达软件科技有限公司 | Stock right management method, system, device, equipment, storage medium and program product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116757862B (en) | 2023-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9361739B2 (en) | Odometer monitoring and redundant storage system | |
| CN110852734B (en) | Scenic spot service settlement method and system based on block chain and electronic equipment | |
| CN108959374B (en) | Data storage method and device and electronic equipment | |
| CN109726048A (en) | Data reconstruction method and device in a kind of transaction system | |
| CN116757862B (en) | Billing method based on ESOP maturation log stream and storage medium | |
| CN106991606B (en) | Transaction data processing method and device | |
| CN108242021B (en) | Accounting data processing system, method and device | |
| Barco | Budgeting for facility repair and maintenance | |
| CN111737255A (en) | Method and system for storing interlocking monitoring data | |
| US20060218155A1 (en) | Method and system for using confidence factors in forming a system | |
| US8452634B2 (en) | Method and system for assessing the progress of a project in terms of its schedule | |
| US8655754B2 (en) | Intercompany transactions elimination system | |
| CN112561506A (en) | Live broadcast data processing method, system, device and medium based on virtual currency | |
| WO2021011688A1 (en) | Pricebook transaction log management systems and methods | |
| CN111210327A (en) | Risk control method and system for motor vehicle to sell unified invoices | |
| CN115619508A (en) | Credit-based deposit-free rental system and method | |
| CN115271694A (en) | Order payment method and system | |
| CN105790975A (en) | Service processing operation execution method and device | |
| CN109190332A (en) | A kind of License Authentication method, system and the relevant device of product | |
| CN114862517A (en) | Automobile leasing method and device based on block chain | |
| CN114119085A (en) | Method and device for point consumption, computer equipment and storage medium | |
| Goldenson et al. | Why make the switch? Evidence about the benefits of CMMI | |
| CN111222928A (en) | Method and system for monitoring enterprise standard invoicing | |
| CN111429060A (en) | Express bill payment management method and equipment | |
| CN111754236B (en) | Clearing transaction data processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |