HR-XML 3.0 Standards, 2009  September  23.

Menu: [ Home  |  Guidelines  |  BODs  |  Nouns  |  Global elements  |  WSDL  |  Packages  |  Code Lists  |  Master Index ]

Trace back: » ch35 | ch35s03 | ch36 | ch36s03 | ch37 »

Chapter 37. Manage Stock Plan Participant

Stock Plan Participant: Overview

HR-XML's Stock Plan Participant noun allows the creation and maintenance of participants within employer stock plans. This would include stock option programs, employee stock purchase plans, and similar employee share plans. For an overview of these processes, see Chapter 32, Stock Plan Scenarios.

It is assumed that an initial participant record is created when an administrative system first goes on-line or when a participant enrolls or begins to participate in the plan. In addition to such "first-time setup" of participants, work and life events as well as events relating to the plan and plan sponsor may necessitate updates and other maintenance of participant data.

Note that participants are usually employees of the plan sponsor, but in some cases may be beneficiaries or parties designated by an employee. For example, a designated beneficiary might inherit the stock options of a participant, which would require that a new account be set up and maintained for the beneficiary.

There are a variety of possible actors and scenarios regarding how participant data might be maintained. The plan sponsor's core HR system or payroll system often would be an original source of the participant census data. However, in some cases, plan record keeping might be nearly entirely outsourced to the administrator after initial setup of participants. The administrator typically would be responsible for supplying other actors (Brokers and / or a Trustee) with relevant participant data and updates. On the other hand, some plan sponsors might have capabilities within their core HR systems to interface with brokers or trustees directly.

Participant data shared among actors connected with the stock plan may include: identifiers (Person Name, social insurance or tax IDs), residential address, date of hire or adjusted service date, and employment status. The Participant's taxation location and available tax rates may also be transmitted to assist with the calculation of tax liabilities upon the exercise of options. Whether or not the employee falls into a classification such as officer, director, or major share holder may be significant under applicable compliance and reporting requirements.

Stock Plan Participant: Trigger / Precondition

As discussed above, there are a variety of possible integration scenarios and event triggers. Examples of events that could trigger the collaboration, include:

  • Outsourced Service Provider Provisioning. Many hosted and outsourced service providers need to be provided with information about the universe of employees or human resources that they will manage or for which they will provide related services. This involves providing the service provider with an initial build of organizational, position, and human resource data and often involves the communication of updates as business and life events change data provided in the initial build.

  • Hire. A "hire event" coincides with the point in time at which a person who has been a candidate becomes associated with an employer as an employee. Sometimes systems are pre-provisioned with information about an individual after he or she has accepted the offer, but before the employee enters-on-duty.

  • Personal Data Changes. These include events such as changes in personal information, such as government identifier, person name, home address, direct deposit account, etc.

Comment on this Component


Use the form below to submit your question or comment about "ch37"

By submitting you indicate that you are accepting HR-XML's Feedback Policy


  * = required field
First/Given Name: *
Last/Family Name: *
Position Title:
Organization:
Country:
Website:
E-mail: *
Topic:

  Please use the area below to write your comment or question: