A method and device for processing employee data

Abstract

The present invention discloses an employee data processing method and device. A specific implementation method includes responding to a tenant processing request, determining the element information corresponding to the tenant, generating a treatment combination field, and then obtaining the element data of the employee based on the timeline to obtain the employee's multi-version treatment file; responding to the employee's reimbursement request, obtaining the time data of the reimbursement request, calling the employee's multi-version treatment file to locate the treatment level, and executing the corresponding reimbursement procedure according to the treatment level. Therefore, the present invention can meet the flexible configuration of treatment items of different enterprises, realize the fine management of various treatment items of employees, and is extensible and configurable.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and device for processing employee data. Background Art

[0002] At present, the employee management of traditional insurance customer systems is a method with fixed employee information fields. In a multi-tenant scenario, different customer companies consider employee benefits in different dimensions, such as age, length of service, position, rank, health care recipients, etc.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0004] Usually, the reimbursement rules for corporate employees are determined by the employee's company's treatment standards, and the dimensions for measuring employee treatment vary from company to company. Employee treatment sets up a treatment file field in the database, combines multiple treatment items into different treatment files, customizes different treatment files for different companies, and executes the corresponding reimbursement rules for employees according to the treatment files.

[0005] The problem that follows is that this combination of benefits files becomes more and more complicated as the number of benefits for employees of different companies increases. When one of the benefits of an employee changes, the benefit file needs to be readjusted, which makes it difficult to manage employee benefit changes in a refined manner, manage multiple versions of employee benefits, and perform statistical analysis of reimbursement data based on multiple employee benefit dimensions. Summary of the invention

[0006] In view of this, an embodiment of the present invention provides an employee data processing method and device, which can meet the flexible configuration of benefits items of different enterprises, realize the fine management of various employee benefits items, and is expandable and configurable.

[0007] To achieve the above-mentioned purpose, according to one aspect of an embodiment of the present invention, there is provided an employee data processing method, comprising responding to a tenant processing request, determining the element information corresponding to the tenant, generating a treatment combination field, and then obtaining the employee's element data based on the timeline to obtain a multi-version treatment file of the employee; responding to the employee's reimbursement request, obtaining the time data of the reimbursement request, calling the employee's multi-version treatment file to locate the treatment level, so as to execute the corresponding reimbursement procedure according to the treatment level.

[0008] Optionally, determining the element information corresponding to the tenant and generating a treatment combination field includes: calling an extensible employee attribute field table corresponding to the tenant, selecting a corresponding employee attribute field based on the tenant processing request, and generating a treatment combination field.

[0009] Optionally, obtaining the employee's element data based on the timeline to obtain multiple versions of the employee's salary file includes:

[0010] According to the file level setting of each employee attribute field in the benefit combination field, multiple groups of benefit field subset change processes are generated based on the tenant processing request;

[0011] Call the change rule set and match the execution rules for each set of treatment field subset change process;

[0012] The employee attribute field data based on the timeline is obtained, and the corresponding treatment field subset change process is processed based on the execution rules to obtain the multi-version treatment file of the employee.

[0013] Optionally, change the process match execution rules for each subset of treatment fields, including:

[0014] Identify the field identifiers for each set of benefit field subset change processes;

[0015] It is determined whether the field identifier is a dynamic identifier. If so, the runtime execution or the scheduled execution in the change rule set is matched. Otherwise, the customized execution in the change rule set is matched.

[0016] Optionally, multiple versions of salary files of the employee are obtained, including:

[0017] According to the multi-version treatment files of the timeline, set the treatment effective time field and treatment expiration time field for each version treatment file;

[0018] The time zone of each version of the treatment file is determined through the treatment effective time field and the treatment expiration time field, so as to set the treatment status of the version of the treatment file in the time zone as valid.

[0019] Optionally, determining a time zone for each version treatment file to set the treatment status of the version treatment file in the time zone as valid includes:

[0020] Determine whether there are multiple versions of treatment files in the time zone determined by the treatment effective time field and the treatment expiration time field;

[0021] If so, based on the timeline positioning, there are multiple starting time points of the version treatment files, so as to set the treatment status of the version treatment file corresponding to the time zone before the starting time point as valid, and use the starting time point as the treatment end time of the version treatment file, and change the treatment status of the version treatment file to invalid; at the same time, use the starting time point as the treatment effective time of the next version treatment file on the timeline, and change the treatment status of the next version treatment file to valid;

[0022] Otherwise, set the treatment status of the version treatment file corresponding to the time zone to valid.

[0023] Optionally, obtaining the employee's element data based on the timeline to obtain multiple versions of the employee's salary file includes:

[0024] According to the employee attribute field in the treatment combination field, determining the calculation model corresponding to the employee attribute field;

[0025] Obtain employee factor data based on the timeline, obtain the processing results of each employee attribute field through the corresponding calculation model, and then generate multiple versions of the employee's salary file based on the timeline.

[0026] In addition, the present invention also provides an employee data processing device, including an acquisition module, which is used to respond to a tenant processing request, determine the element information corresponding to the tenant, generate a treatment combination field, and then obtain the employee's element data based on the timeline to obtain a multi-version treatment file of the employee; a processing module, which is used to respond to the employee's reimbursement request, obtain the time data of the reimbursement request, call the employee's multi-version treatment file to locate the treatment level, and execute the corresponding reimbursement procedure according to the treatment level.

[0027] One embodiment of the above invention has the following advantages or beneficial effects: the present invention flexibly supports the maintenance of personalized employee benefits for different enterprises, supports enterprises to dynamically maintain employee benefit changes on a monthly, annual, agreed basis or along a timeline, that is, it can meet the personalized employee benefit management needs of enterprises in multi-tenant business scenarios, and can also manage multiple versions of employee benefit information according to a timeline, thereby laying a solid foundation for customer development and rapid response to customer needs; and, utilizes the effective time to realize multi-version information management of employee benefits and time lag and retrospective management of employee benefit changes.

[0028] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0030] Figure 1 is a schematic diagram of the main flow of the employee data processing method according to the first embodiment of the present invention;

[0031] Figure 2 is a schematic diagram of the main flow of the employee data processing method according to the second embodiment of the present invention;

[0032] Figure 3 is a schematic diagram of the main flow of the employee data processing method according to the third embodiment of the present invention;

[0033] Figure 4is a schematic diagram of the main flow of the employee data processing method according to the fourth embodiment of the present invention;

[0034] Figure 5 is a schematic diagram of main modules of an employee data processing device according to an embodiment of the present invention;

[0035] Figure 6 is a diagram of an exemplary device architecture to which embodiments of the present invention may be applied;

[0036] Figure 7 It is a schematic diagram of the structure of a computer device of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0037] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0038] Figure 1 is a schematic diagram of the main flow of the employee data processing method according to the first embodiment of the present invention, the employee data processing method comprising:

[0039] Step S101, in response to a tenant processing request, determining the element information corresponding to the tenant, generating a treatment combination field, and then acquiring the employee's element data based on the timeline to obtain a multi-version treatment file for the employee.

[0040] In some embodiments, determining the element information corresponding to the tenant and generating a treatment combination field includes: calling the extensible employee attribute field table corresponding to the tenant, selecting the corresponding employee attribute field based on the tenant processing request, and generating a treatment combination field.

[0041] In a further embodiment, the employee's element data based on the timeline is obtained to obtain multiple versions of the employee's salary files. Then, according to the grade setting of each employee attribute field in the salary combination field, multiple groups of salary field subset change processes can be generated based on the tenant processing request. For example, the extensible employee attribute field table corresponding to the enterprise tenant is called, and the employee's salary measurement criteria are selected as length of service, employee status, and rank, wherein the length of service grade setting is divided into: 1-5 years is the first grade of length of service, 6-10 years is the second grade of length of service, and more than 10 years is the third grade of length of service. The employee status grade setting is divided into: in service, retired. The rank grade setting is divided into: expert, senior, intermediate, and junior. Based on the tenant processing request, multiple groups of salary field subset change processes are generated: a salary field subset change process including length of service, employee status, and rank composition, and a salary field subset change process including rank composition. Specifically, the process of changing the subset of treatment fields including length of service, employee status, and rank is as follows: (1) In-service, first-grade length of service, and junior high school is the first grade of treatment; (2) In-service, second-grade length of service, and junior high school is the second grade of treatment; (3) In-service, second- and third-grade length of service, and junior high school is the third grade of treatment. The process of changing the subset of treatment fields including rank is as follows: (4) Expert is the fourth grade of treatment; (5) Retired is the fifth grade of treatment.

[0042] Then call the change rule set to match the execution rules for each set of treatment field subset change processes. Obtain the employee attribute field data based on the timeline, process the corresponding treatment field subset change process based on the execution rules, and obtain multiple versions of the employee's treatment files. For example, an employee joined the company on September 1, 2015, and his rank was intermediate when he joined the company. On August 1, 2020, a customized execution change was made to senior, and the effective date was November 1, 2020. There are then two records of this employee in the database: (1) Intermediate, effective from joining the company to November 1, 2020; (2) Senior, effective from November 1, 2020 to the present. The current time is March 1, 2021. At this time, in the employee's change history, from the earliest to the latest timeline, the employee's salary levels are: (1) Salary Level 1, September 1, 2015 - September 1, 2020; (2) Salary Level 2, September 1, 2020 - November 1, 2020; (3) Salary Level 3, November 1, 2020 to the present. In other words, when it is necessary to query the employee's salary level during business operations, enumerable employee attribute field data will be generated based on the employee's element information and time range and based on the execution rules. Finally, the employee's salary level will be returned based on the employee's multiple versions of salary levels to complete the calculation of the employee's salary level.

[0043] In addition, when matching the execution rules for each group of benefit field subset change processes, the field identifier in each group of benefit field subset change processes can be identified, and then it is determined whether the field identifier is a dynamic identifier. If so, the runtime execution or scheduled execution in the change rule set is matched; otherwise, the customized execution in the change rule set is matched. It can be seen that the embodiment of the present invention can flexibly set the employee's benefit execution rules, so that the benefit change rules are expanded to three modes: runtime, scheduled task triggering, and customized operation, which greatly improves the scalability of benefit calculations and reduces the complexity of benefit calculations. In addition, the entire benefit reimbursement rule is to flexibly set the benefit item combination according to the needs of corporate customers, combined with runtime rules, multi-version benefit information of scheduled execution or customized operations, and generate employee benefit file information in combination, and the employee benefit file has continuity on the timeline.

[0044] As some further embodiments, for the employee's multiple versions of salary files, a salary effective time field and a salary expiration time field may be set for each version of the salary file according to the multiple versions of the salary files on the time axis. Then, the time zone of each version of the salary file is determined by the salary effective time field and the salary expiration time field, so as to set the salary status of the version of the salary file in the time zone as valid.

[0045] In a further embodiment, determining the time zone of each version treatment file to set the treatment status of the version treatment file in the time zone as valid includes:

[0046] Determine whether there are multiple version treatment files in the time zone determined by the treatment effective time field and the treatment expiration time field; if so, locate the start time points of the multiple version treatment files based on the time axis, set the treatment status of the version treatment file corresponding to the time zone before the start time point to be valid, and use the start time point as the treatment expiration time of the version treatment file, and change the treatment status of the version treatment file to invalid; at the same time, use the start time point as the treatment effective time of the next version treatment file on the time axis, and change the treatment status of the next version treatment file to valid; otherwise, set the treatment status of the version treatment file corresponding to the time zone to valid.

[0047] For example, an employee is promoted to expert level on October 1, 2020 due to special contributions. This change is made on December 1, 2020, and the specified effective date is October 1, 2020. There are four records of this employee in the database, i.e., multiple versions of employee benefits: (1) Intermediate, effective from joining to October 1, 2020, benefits effective status 1; (2) Intermediate, effective from joining to November 1, 2020, benefits effective status 0; (3) Senior, effective from November 1, 2020 to date, benefits effective status 0; (3) Expert, effective from October 1, 2020 to date, benefits effective status 1.

[0048] It can be seen that if the change has a repeated time period, the new change will overwrite the old change, and the treatment status of the old change with the repeated time period will be set to 0 and invalid, and retained as the change history. When calculating the treatment, you only need to care about the change record with a treatment status of 1. In other words, use the treatment effective time, treatment termination time, and treatment status to generate multiple versions of treatment information, that is, form a continuous timeline of multiple versions of employee treatment files, and quantify the treatment changes based on the timeline after combining them according to the treatment files. At the same time, the employee's treatment information at the time can be accurately matched on the timeline, and the information of multiple versions of employee treatment files that change over time can be intuitively seen, which greatly simplifies the complexity of employee treatment calculations and lays a solid foundation for realizing employee treatment data management for multi-tenant, multi-business line, and multi-supplier unified businesses, that is, it supports the traceability of treatment changes and solves the problem of delayed employee treatment changes.

[0049] It is worth noting that the employee attribute fields in the treatment combination field can determine the corresponding calculation model, and then obtain the processing results of each employee attribute field through the corresponding calculation model according to the employee's timeline-based factor data, and then generate multiple versions of the employee's treatment file based on the timeline. For example, the employee attribute field: length of service is dynamically calculated according to the date of employment. The calculation model is that if it is less than one year, it will be calculated as one year, and if it is more than one year, it will be rounded down. The calculation model is:

[0050] MAX{1,Rounddown(Benefit occurrence date - employment date)}, where rounddown is the round-down function.

[0051] Step S102, in response to the employee's reimbursement request, obtaining the time data of the reimbursement request, calling the employee's multi-version remuneration file to locate the remuneration level, and executing the corresponding reimbursement procedure according to the remuneration level.

[0052] For example, when an employee's reimbursement request has two invoices to be reimbursed, if the invoice date is September 2, 2020, the length of service is calculated as level 2 during operation, and reimbursement is made according to the second level of treatment. If the invoice date occurs on November 2, 2020, the length of service is calculated as level 2 during operation, but the position level is adjusted to senior on November 1, 2020, and reimbursement is made according to the third level of treatment.

[0053] Figure 2 This is a schematic diagram of the main process of the employee data processing method according to the second embodiment of the present invention. In a multi-tenant, multi-business line scenario, the employee data processing method simplifies the complexity of employee benefit changes and benefit calculations in the face of the diverse needs of employee benefits in different companies, including:

[0054] Step S201, in response to a tenant processing request, calling the extensible employee attribute field table corresponding to the tenant, selecting a corresponding employee attribute field based on the tenant processing request, and generating a benefit combination field.

[0055] For example, for different tenants, you can flexibly configure the extensible employee attribute field table according to customer needs, and select the fields that determine employee benefits as the benefit combination fields. For example: a benefit combination field that includes age, length of service, position, rank, and health care object employee attribute fields.

[0056] Step S202, according to the level setting of each employee attribute field in the benefit combination field, a plurality of groups of benefit field subset change processes are generated based on the tenant processing request.

[0057] For example, you can choose to set a salary field subset change process according to tenant needs, for example: change the position and rank in the salary combination field as a set of salary field subset change processes.

[0058] Step S203, identifying the field identifiers in each group of treatment field subset change procedures.

[0059] Step S204, determining whether the field identifier is a dynamic identifier, if so proceeding to step S205, if not proceeding to step S206.

[0060] Step S205, runtime execution or scheduled execution in the matching change rule set, proceed to step S207.

[0061] Step S206, matching the customized execution in the change rule set, and proceeding to step S207.

[0062] For example, the execution rules of the change process of each set of benefit field subsets are determined, including runtime execution, scheduled execution, and customized execution. Among them, runtime execution, for example, fields such as date of birth, date of employment, date of regularization, date of employment, etc., can use preset calculation expressions to dynamically execute and calculate the employee's current benefit items at runtime. The principle of scheduled execution is the same as that of runtime execution. The difference is that scheduled execution is to set scheduled tasks according to the needs of tenants to calculate and generate employee benefit items, such as uniformly calculating and changing the length of service file at a certain time point in the natural year. Customized execution directly changes the employee's static benefit fields, such as rank, position, health care object category, etc., and the effective time or effective time range needs to be set.

[0063] Step S207, determining a calculation model corresponding to the employee attribute field according to the employee attribute field in the benefit combination field.

[0064] Step S208, obtaining employee attribute field data based on the timeline, and obtaining processing results of each employee attribute field through a corresponding calculation model based on the execution rules.

[0065] Step S209, executing the corresponding treatment field subset change process according to the processing result of the employee attribute field, and obtaining multiple versions of the treatment file of the employee.

[0066] Step S210, in response to the employee's reimbursement request, obtaining time data of the reimbursement request.

[0067] Step S211, calling the employee's multi-version salary file to locate the salary level, so as to execute the corresponding reimbursement procedure according to the salary level.

[0068] Figure 3 1 is a schematic diagram of the main flow of the employee data processing method according to the third embodiment of the present invention. Based on the system administrator, the employee data processing method includes:

[0069] Step S301, in response to a tenant processing request, calling the extensible employee attribute field table corresponding to the tenant, selecting a corresponding employee attribute field based on the tenant processing request, and generating a benefit combination field.

[0070] Step S302, according to the level setting of each employee attribute field in the benefit combination field, multiple groups of benefit field subset change processes are generated based on the tenant processing request.

[0071] Step S303, identifying the field identifiers in each group of treatment field subset change procedures.

[0072] Step S304, determining whether the field identifier is a dynamic identifier, if so proceeding to step S305, if not proceeding to step S306.

[0073] Step S305, runtime execution or scheduled execution in the matching change rule set, setting the dynamic field, and then proceeding to step S307.

[0074] For example, the dynamic fields of runtime execution or timed execution may include execution time and the like.

[0075] Step S306, matching the customized execution in the change rule set, setting the customized field, and proceeding to step S307.

[0076] For example, the custom fields can include effective time, effective time range, etc.

[0077] Step S307, obtaining employee attribute field data based on the timeline, processing the corresponding treatment field subset change process based on the execution rules, and obtaining a multi-version treatment file for the employee.

[0078] In an embodiment, when processing the corresponding treatment field subset change process based on the execution rule, each treatment field is respectively processed by calling the corresponding calculation model. For example, the calculation model can be an operation expression.

[0079] Figure 4 1 is a schematic diagram of the main flow of the employee data processing method according to the fourth embodiment of the present invention. Based on the enterprise handling personnel, the employee data processing method includes:

[0080] Step S401, in response to a customized or scheduled execution change instruction, determining a corresponding changed employee attribute field.

[0081] Step S402, setting the effective time or effective time range of the changed employee attribute field.

[0082] In the embodiment, in addition to the scheduled execution and customized execution at runtime, the effective time or effective time range needs to be set. The effective time can be set to take effect immediately, or can be specified as a certain day in the future, or can be specified as a certain day in the past. Among them, specifying a certain day in the past can solve the problem of delayed changes in employee benefits and the need to backtrack.

[0083] Step S403, obtaining the employee multi-version salary file corresponding to the customized execution change instruction.

[0084] Step S404, determine whether there are multiple versions of treatment files in the time zone determined by the treatment effective time field and the treatment expiration time field. If so, proceed to step S405, otherwise proceed to step S406.

[0085] In an embodiment, the treatment file has three fields: treatment effective time, treatment termination time, and treatment status. When an employee's treatment changes, it is specified as a certain effective time. The new effective time will be compared with the effective time of each record in the employee's multi-version treatment file of the historical record. That is, after the history of employee treatment changes is sorted by treatment effective time, it will be a continuous change record on the time axis, and the treatment termination time of the previous record will be the treatment effective time of the next change. Preferably, the treatment effective time and treatment termination time of a record (i.e., a version of the treatment file) adopt the principle of closing first and opening later, that is, the treatment effective time is a closed interval, and the treatment termination time is an open interval.

[0086] Step S405, based on the time axis, locate the start time points of multiple version treatment files, set the treatment status of the version treatment file corresponding to the time zone before the start time point to be valid, and use the start time point as the treatment end time of the version treatment file, and change the treatment status of the version treatment file to invalid. At the same time, use the start time point as the treatment effective time of the next version treatment file on the time axis, and change the treatment status of the next version treatment file to valid. Then, proceed to step S407.

[0087] In the embodiment, if multiple versions of treatment files have overlapping time periods, the new version of the treatment file will overwrite the old version of the treatment file, and the treatment status of the old version of the treatment file with the overlapping time period will be set to 0, that is, invalid, and retained as a change history. It should be noted that when calculating the treatment, only the records of the treatment status of the version of the treatment file with a treatment status of 1 need to be concerned.

[0088] Step S406, set the treatment status of the version treatment file corresponding to the time zone to valid, and proceed to step S407.

[0089] Step S407, updating and storing the employee's multi-version salary files.

[0090] Figure 5 is a schematic diagram of the main modules of the employee data processing device according to an embodiment of the present invention. Figure 5 As shown, the employee data processing device 500 includes an acquisition module 501 and a processing module 502. The acquisition module 501 responds to the tenant processing request, determines the element information corresponding to the tenant, generates a treatment combination field, and then obtains the element data of the employee based on the time axis to obtain the multi-version treatment file of the employee; the processing module 502 responds to the employee's reimbursement request, obtains the time data of the reimbursement request, calls the multi-version treatment file of the employee to locate the treatment level, and executes the corresponding reimbursement procedure according to the treatment level.

[0091] In some embodiments, the acquisition module 501 determines the element information corresponding to the tenant and generates a treatment combination field, including:

[0092] The extensible employee attribute field table corresponding to the tenant is called, and the corresponding employee attribute field is selected based on the tenant processing request to generate a treatment combination field.

[0093] In some embodiments, the acquisition module 501 acquires the employee's element data based on the timeline to obtain the employee's multi-version salary file, including:

[0094] According to the level setting of each employee attribute field in the benefit combination field, multiple groups of benefit field subset change processes are generated based on the tenant processing request;

[0095] Call the change rule set and match the execution rules for each set of treatment field subset change process;

[0096] The employee attribute field data based on the timeline is obtained, and the corresponding treatment field subset change process is processed based on the execution rules to obtain the multi-version treatment file of the employee.

[0097] In some embodiments, the acquisition module 501 matches and executes rules for each group of treatment field subset change process, including:

[0098] Identify the field identifiers in the change process for each set of benefit field subsets;

[0099] It is determined whether the field identifier is a dynamic identifier. If so, the runtime execution or the scheduled execution in the change rule set is matched. Otherwise, the customized execution in the change rule set is matched.

[0100] In some embodiments, the acquisition module 501 obtains multiple versions of the employee's salary files, including:

[0101] According to the multi-version treatment files of the timeline, set the treatment effective time field and treatment expiration time field for each version treatment file;

[0102] The time zone of each version of the treatment file is determined through the treatment effective time field and the treatment expiration time field, so as to set the treatment status of the version of the treatment file in the time zone as valid.

[0103] In some embodiments, the acquisition module 501 determines the time zone of each version treatment file to set the treatment status of the version treatment file in the time zone as valid, including:

[0104] Determine whether there are multiple versions of treatment files in the time zone determined by the treatment effective time field and the treatment expiration time field;

[0105] If so, based on the timeline positioning, there are multiple starting time points of the version treatment files, so as to set the treatment status of the version treatment file corresponding to the time zone before the starting time point as valid, and use the starting time point as the treatment end time of the version treatment file, and change the treatment status of the version treatment file to invalid; at the same time, use the starting time point as the treatment effective time of the next version treatment file on the timeline, and change the treatment status of the next version treatment file to valid;

[0106] Otherwise, set the treatment status of the version treatment file corresponding to the time zone to valid.

[0107] In some embodiments, the acquisition module 501 acquires the employee's element data based on the timeline to obtain the employee's multi-version salary file, including:

[0108] According to the employee attribute field in the treatment combination field, determining the calculation model corresponding to the employee attribute field;

[0109] Obtain employee factor data based on the timeline, obtain the processing results of each employee attribute field through the corresponding calculation model, and then generate multiple versions of the employee's salary file based on the timeline.

[0110] It should be noted that the employee data processing method and the employee data processing device of the present invention have a corresponding relationship in terms of specific implementation contents, so the repeated contents will not be described again.

[0111] Figure 6 An exemplary device architecture 600 is shown to which the employee data processing method or employee data processing device according to the embodiment of the present invention can be applied.

[0112] like Figure 6 As shown, the device architecture 600 may include terminal devices 601, 602, 603, a network 604 and a server 605. The network 604 is used to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links or optical fiber cables.

[0113] Users can use terminal devices 601, 602, 603 to interact with server 605 through network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0114] The terminal devices 601 , 602 , and 603 may be various electronic devices having an employee data processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0115] The server 605 may be a server that provides various services, for example, a backend management server (for example only) that provides support for shopping websites browsed by users using the terminal devices 601, 602, and 603. The backend management server may analyze and process the received product information query request and other data, and feed back the processing results (for example, target push information, product information - for example only) to the terminal device.

[0116] It should be noted that the employee data processing method provided in the embodiment of the present invention is generally executed by the server 605 , and accordingly, the computing device is generally disposed in the server 605 .

[0117] It should be understood that Figure 6 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0118] Reference below Figure 7 , which shows a schematic structural diagram of a computer device 700 of a terminal device suitable for implementing an embodiment of the present invention. Figure 7 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0119] like Figure 7 As shown, the computer device 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the computer device 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0120] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display processor (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage section 708 as needed.

[0121] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above-mentioned functions defined in the device of the present invention are executed.

[0122] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Examples of computer-readable storage media may be - but not limited to - electrical, magnetic, optical, electromagnetic, infrared, or semiconductor devices, devices or components, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution device, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution device, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0123] The flowchart and block diagram in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the device, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based device that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0124] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor. For example, the processor may include an acquisition module and a processing module. The names of these modules do not, in some cases, limit the modules themselves.

[0125] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently and not be assembled into the device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by a device, the device includes responding to a tenant processing request, determining the element information corresponding to the tenant, generating a treatment combination field, and then obtaining the employee's element data based on the timeline to obtain the employee's multi-version treatment file; responding to the employee's reimbursement request, obtaining the time data of the reimbursement request, calling the employee's multi-version treatment file to locate the treatment level, and executing the corresponding reimbursement procedure according to the treatment level.

[0126] According to the technical solution of the embodiment of the present invention, the implementation method of the present invention can meet the flexible configuration of the benefits items of different enterprises, realize the fine management of various benefits items of employees, and be expandable and configurable.

[0127] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for processing employee data, characterized in that: include: In response to a tenant processing request, determine the element information corresponding to the tenant, generate a treatment combination field, and then obtain the employee's element data based on the timeline to obtain a multi-version treatment file for the employee; In response to the employee's reimbursement request, obtaining time data of the reimbursement request, calling the employee's multi-version remuneration file to locate the remuneration level, and executing a corresponding reimbursement procedure according to the remuneration level; Determine the element information corresponding to the tenant and generate a treatment combination field, including: Calling the extensible employee attribute field table corresponding to the tenant, selecting the corresponding employee attribute field based on the tenant processing request, and generating a treatment combination field; Obtaining the employee's timeline-based factor data to obtain multiple versions of the employee's salary files, including: According to the file level setting of each employee attribute field in the benefit combination field, multiple groups of benefit field subset change processes are generated based on the tenant processing request; Call the change rule set and match the execution rules for each set of treatment field subset change process; The employee attribute field data based on the timeline is obtained, and the corresponding treatment field subset change process is processed based on the execution rules to obtain the multi-version treatment file of the employee.

2. The method according to claim 1, characterized in that Change the process matching execution rules for each subset of treatment fields, including: Identify the field identifiers for each set of benefit field subset change processes; It is determined whether the field identifier is a dynamic identifier. If so, the runtime execution or the scheduled execution in the change rule set is matched. Otherwise, the customized execution in the change rule set is matched.

3. The method according to claim 1, characterized in that Get multiple versions of the employee's salary files, including: According to the multi-version treatment files of the timeline, set the treatment effective time field and treatment expiration time field for each version treatment file; The time zone of each version of the treatment file is determined through the treatment effective time field and the treatment expiration time field, so as to set the treatment status of the version of the treatment file in the time zone as valid.

4. The method according to claim 3, characterized in that Determine the time zone of each version treatment file to set the treatment status of the version treatment file in the time zone as valid, including: Determine whether there are multiple versions of treatment files in the time zone determined by the treatment effective time field and the treatment expiration time field; If so, based on the timeline positioning, there are multiple starting time points of the version treatment files, so as to set the treatment status of the version treatment file corresponding to the time zone before the starting time point as valid, and use the starting time point as the treatment end time of the version treatment file, and change the treatment status of the version treatment file to invalid; at the same time, use the starting time point as the treatment effective time of the next version treatment file on the timeline, and change the treatment status of the next version treatment file to valid; Otherwise, set the treatment status of the version treatment file corresponding to the time zone to valid.

5. The method according to any one of claims 1 to 4, characterized in that: Obtaining the employee's timeline-based factor data to obtain multiple versions of the employee's salary files, including: According to the employee attribute field in the treatment combination field, determining the calculation model corresponding to the employee attribute field; Obtain employee factor data based on the timeline, obtain the processing results of each employee attribute field through the corresponding calculation model, and then generate multiple versions of the employee's salary file based on the timeline.

6. An employee data processing device, characterized in that: include: An acquisition module, for responding to a tenant processing request, determining the element information corresponding to the tenant, generating a treatment combination field, and then acquiring the element data of the employee based on the timeline to obtain a multi-version treatment file of the employee; A processing module, for responding to the employee's reimbursement request, obtaining the time data of the reimbursement request, calling the employee's multi-version remuneration file to locate the remuneration level, and executing a corresponding reimbursement procedure according to the remuneration level; The acquisition module is specifically used to: call the extensible employee attribute field table corresponding to the tenant, select the corresponding employee attribute field based on the tenant processing request, and generate the treatment combination field; The acquisition module is specifically used to: generate multiple groups of treatment field subset change processes based on the tenant processing request according to the grade setting of each employee attribute field in the treatment combination field; Call the change rule set to match the execution rules for each group of treatment field subset change processes; obtain the employee attribute field data based on the timeline, process the corresponding treatment field subset change process based on the execution rules, and obtain multiple versions of the treatment files of the employees.

7. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 5.

8. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images