PrismHR Help · Public documentation for Microsoft 365 Copilot
This file is a combined export of PrismHR help topics in Onboarding & Benefits Enrollment. Source help system: https://tech-docs.prismhr.com/SP_help/Default.htm Each topic is separated by a heading and includes its original URL.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Assigning_Admin_Roles.htm
Path:
OBE/Benefits Enrollment/Topics/Assigning_Admin_Roles.htm
There are many places in PrismHR that require administrator actions. For more information, see the System Administration Guide, Human Resources User Guide, or Approvals Guide.
When setting up workflows for enrollments, you have the option to require that an administrator approve all enrollments. If you choose to do this, you must have at least one user or worksite trusted advisor for each of these roles.
If the user is a service provider, assign the role Benefit Manager in the Users form.
If the user is a worksite manager or worksite trusted advisor, assign the role Benefit Approver in the Users form.
You must also set up approval policies. Each approval policy specifies who must approve an action before it is finalized.
Use the Global Approval Policies form to define approval policies at the system level.
Use the Approval Policies form to override global approval policies at the client level.
You can set up the following proxy enrollments:
Worksite Managers and Worksite Trusted Advisors who are set up with the Enrollment Proxy user role can act as an employee and execute the employee’s enrollment selections using the Proxy Login form.
Worksite Managers and Worksite Trusted Advisors who are set up with the Onboarding Proxy user role can read employees’ full onboarding workflows. (Note: The system bypasses any field-level security when using this role.)
Worksite Managers and Worksite Trusted Advisors who are set up with the Enrollment Proxy user role can act as an employee and execute the employee’s enrollment selections using the Proxy Login form.Note: If the user is a Worksite Manager or Worksite Trusted Advisor, assign the Enrollment Proxy and Onboarding Proxy roles in the Users form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Assigning_Dependents_Grp_Plans.htm
Path:
OBE/Benefits Enrollment/Topics/Assigning_Dependents_Grp_Plans.htm
You must add validation on group benefit plan types by assigning them to the relationship codes that represent employee dependent relationships. You must also define the age limit for dependents and when the dependent’s age limit takes effect.
These settings allow the correct cost for the offered benefit plans, based on the employee’s dependent selection, to display during enrollments.
If the benefit plan type requires that the employee’s spouse be set as a dependent, select Spouse Required or Domestic Partner Req’d on each Type Code.
Indicate whether the plan covers the employee’s regular dependents, the domestic partner’s children, or both using the Dependent Min/Max Type list.
In the Group Benefit Plans form, define the Dependent’s Age Limit and select when the benefit plan imposes an age limit from the list.
In the Relationships form, assign group benefit Plan Types to each Relationship Code.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Assigning_Offer_Types.htm
Path:
OBE/Benefits Enrollment/Topics/Assigning_Offer_Types.htm
You must assign an offer type to each benefit plan offered to employees during benefit enrollments. The offer type classifies the benefit plan according to type (for example, Medical, Dental, Vision) and assures that the benefit plan displays in the correct form during benefit enrollments.
If benefit plans are not assigned offer types, you cannot include them in benefits enrollment.
To assign offer types on group benefit plans:
Click Back Office.
From System|Change, select Group Benefit Plans. The Group Benefit Plans form opens.
To assign offer types on flexible spending account (FSA), health saving account (HSA), and commuter (COM) benefit plans:
Click Back Office.
From System|Change, select Flex Spend Account Types. The Group Benefit Plans form opens.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Benefit%20Plans%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Benefit Plans Report.htm
Use this form to generate a report that is run at the system level of all group benefit plans in the system. The report includes important plan setup information with the option to include specific G/L account information.
Note: Note: This form does not use Client Access Group Security.
To access the form, click Reports menu. Under System|Report, click Benefit Plans Report.
To generate the Benefit Plans Report:
Field Name — Description
Termination Date Above or Equal to — Enter the date from which you want to run this report.
G/L Template ID — If you want G/L account numbers on the report, enter a G/L template here or click the G/L Template ID link and select it from the Select G/L Template dialog box.
Click Run to generate the report. The Benefit Plans Report shows up on screen.
Click Clear to clear the form at any time
Click Close to close this form.
This report shows the following columns:
Benefit Plan ID
Benefit Plan Description
Insurance Class
Reconciliation Group
Cost Basis
Auto Enroll
Section 125
COBRA Eligible
Report on W2
Deduction Code
125 Deduction Code
Bill Code
Debit G/L Account ID
Credit G/L Account ID
Termination Date
Client Sponsored
Doesn’t Meet Participation Requirements
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Benefit%20Reconciliation%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Benefit Reconciliation Report.htm
Use this form to generate a report to show benefit collections per coverage period based on benefits registers.
Note: Note:
Worksite Managers, Worksite Trusted Advisors, and Service Providers can access the form.
Client Access Group Security and Data Entity security is enabled on this form.
To access the form, either:
Click Reports. Under Benefits|Report, click Benefit Reconciliation Report OR
Under Work Centers, under Onboarding & Benefits, click Benefit Imports & Reporting. Under Benefit Reporting, click Benefit Reconciliation Report.
To generate the Benefit Reconciliation Report:
Field Name — Description
Coverage Year — Select the coverage year to report on from the drop-down. The default is the current year with a 10 year look back option.
Coverage Month — Select the coverage month to report on from the drop-down. The default is the month of January.
Benefit Plan ID — This field is optional. Leave this field blank for this report to run for all benefit plans. If you want to restrict this report to run for selected benefit plans, enter the benefit plan IDs here or click the Benefit Plan ID link and select them from the Select Benefit Plan dialog box.
Client ID — This field is optional. Leave this field blank for this report to run for all clients. If you want to restrict this report to run for selected clients, enter the Client IDs here or click the Client ID link and select them from the Select Clients dialog box.
Click Run to generate the report. The report displays on-screen.
Click Clear to clear the form at any time.
This report displays the following columns:
Plan ID
Plan Name
Client ID
Client Name
Employee ID
Employee Name
Billed
Deducted
Arrearage
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Benefit%20Summary%20Statement%20Setup.htm
Path:
OBE/Benefits Enrollment/Topics/Benefit Summary Statement Setup.htm
Use this form to define the parameters for running the mvQuery version of the benefit confirmation report.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, click the Back Office menu. Under System|Change, click Benefit Summary Statement Setup.
To set up the Benefits Summary Statement:
| Field Name | Description |
|---|---|
| Formats section | |
| Formats | Select one of the following radio buttons: - Client - and select the Client from the Select Client dialog box OR - Employer - and select the employer from the Select Employer dialog box. |
Click Save to save the setup. The form is refreshed.
Click Delete to delete the setup. A dialog box appears asking you to confirm the deletion of the record.
| a. | Click Yes to delete the record. |
|---|---|
| b. | Click No to return to the form. |
| — | — |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Benefit%20Summary%20Statement.htm
Path:
OBE/Benefits Enrollment/Topics/Benefit Summary Statement.htm
Use this form to generate a customizable Benefit Confirmation Statement that can be run for a single client and includes details related to benefits including: benefit enrollments, dependents, coverage amounts, premium amounts. This report uses the information from the Benefit Summary Statement Setup form. The link to the Benefit Summary Statement Setup form is available on this form. This setup form needs to be completed for a client to run this report for the client.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, in the Work Centers panel, under Onboarding & Benefits section, click Benefit Imports & Reporting. Under Benefit Reporting click Benefit Summary Statement.
To generate the Benefit Confirmation Statement:
Field Name — Description
Benefit Summary Statement
Show all employees with coverages effective on this date — If you select this radio button, indicate the date
Show all employees whose coverage starts between — If you select this options, then provide a date range be providing a Start Date and an End Date. Start Date - Coverage for all employees that start from this date. End Date - Coverage for all employees that is up to this date.
Plan Year - Enter Plan Year Start and End date for display on the report only.
Start Date — Indicate the Plan Year start date here.
End Date — Indicate the Plan Year end date here.
Click Generate Report to build the Benefit Confirmation Statements for the client. A job progress window shows the processing steps. Click Close to close the job progress window. The following links appears on the screen.
Click the View Benefit Summary Report link to open the Benefit Confirmation Statement on screen. One employee record is displayed per page in the Benefit Confirmation Statement on screen. This link will not display unless you generate the report.
Click the View Error Report link to review the error message if any. If there is no error then “No Errors Produced” is displayed before the View Benefit Summary Report link. This will not display unless you generate the report.
Click Clear to clear the form at any time.
Following is a sample Benefit Confirmation Statement:
[Image: Benefit Confirmation Statement]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Benefit-Import-Def.htm
Path:
OBE/Benefits Enrollment/Topics/Benefit-Import-Def.htm
Use the Benefit Import Maintenance form to set parameters for benefit imports. Benefit import definitions specify data file layout and provides a template to interpret the data. The import definition also has tables that translate data file codes into standard PrismHR codes.
Note: Note: This form does not use Client Access Group Security.
To set benefit import parameters:
From the Work Centers panel, click Benefit Imports and Reporting.
From Benefit Imports, click Benefit Import Maintenance.
Complete these fields as required:
| Field | Description |
|---|---|
| Import Definition ID / Import Definition Description | Click the Import Definition ID link to select an existing import definition, or enter data to create a new import definition. For existing import definitions, the Import Definition Description fills in. For new import definitions, enter an import description. |
| File Format | Options are Delimited or Fixed Length. Delimited is the default setting. |
| Delimiter | Select Comma or Tab from the drop-down. |
| Header Row | Set to Included to include a header row in your import definition file. |
| Terminate coverage from other plans in the same insurance class when a new enrollment is created in a medical, dental, or vision plan. | Enable this to end coverage from other plans that are in the same insurance class when new enrollments are created in medical, dental, or vision plans. |
| Suppress billing adjustments for new enrollments and benefit terminations made during the benefit import. | Enable this to suppress billing adjustments for new enrollments and benefit terminations made during the benefit import. |
| Suppress COBRA prompts when a benefit enrollment is terminated. | Enable this to: - Suppress COBRA prompts when a benefit enrollment is terminated. - Prevent COBRA enrollee records from being created when benefits coverage is lost. > Note: Note: Do not enable if you need to administer COBRA for terminated benefits. |
| a. | Click + to add an import field. |
|---|
— Click Populate with required fields to fill in required import fields. You must have Company, Employee ID, Plan ID, and Effective Date defined before you can save the template.
— Specify Field Names: Enter one of the standard column tags and the import program will look for that item of information in this position of the data file. The list of field names along with their description is displayed below:
| Field Name | Description | Required |
|---|---|---|
| $ACTION | Action Code | Yes |
| $COMPANY | Company ID | Yes |
| $EMPLOYEE_ID | Employee ID | No |
| $EE_SSN | Employee SSN | Yes (or $CLOCKNO) |
| $CLOCKNO | Employee Clock Number | Yes (or $EE_SSN) |
| $PLAN_ID | Benefit Plan ID | No |
| $OFFER_TYPE | Enrollment Offer Type | No |
| $NETWORK | Network ID | No |
| $DOCTOR_ID | Doctor ID | No |
| $DOCTOR_NAME | Doctor Name | No |
| $PLAN_TYPE | Coverage Level or Tier | Yes |
| $EFFECTIVE_DATE | Effective Date | Yes |
| $PREMIUM | Benefit Premium | No |
| $CONTRIB | Employee Benefit Contribution | No |
| $DEDN_START | Deduction Start Date | No |
| $DEDN_ENDS | Deduction End Date | No |
| $SECTION_125 | Section 125 sheltered | No |
| $EE_COVERAGE | Employee Coverage Amount | No |
| $SPS_COVERAGE | Spouse Coverage Amount | No |
| $DEPN_COVERAGE | Dependent Coverage Amount | No |
| $EE_GI_OVER | Employee GI Overage Amount | No |
| $SP_GI_OVER | Spouse GI Overage Amount | No |
| $DP_GI_OVER | Dependent GI Overage Amount | No |
| $DEPN_ID | Dependent ID | No |
| $DEPN_SSN | Dependent SSN | No |
| $DEPN_FNAME | Dependent First Name | No |
| $DEPN_LNAME | Dependent Last Name | No |
| $DEPN_MNAME | Dependent Middle Name | No |
| $DEPN_SPOUSE | Dependent is Spouse | No |
| $DEPN_BDATE | Dependent Birthdate | No |
| $DEPN_GENDER | Dependent Gender | No |
| $DEPN_RELATION | Dependent Relation | No |
| $DEPN_DOCTOR_ID | Dependent Doctor ID | No |
| $DEPN_DOCTOR_NAME | Dependent Doctor Name | No |
| $BENEF_ID | Beneficiary ID | No |
| $BENEF_TYPE | Beneficiary Type | No |
| $BENEF_PCNT | Beneficiary Percent | No |
| $BENEF_PREC | Beneficiary Precedent | No |
| $PLAN_YEAR | FSA/HSA Plan Year | No |
| $PLAN_OVRD_START_DATE | Plan Override Start Date | No |
| $PLAN_OVRD_END_DATE | Plan Override End Date | No |
| $ACCOUNT_TYPE | FSA/HSA Account Type | No |
| $ACCOUNT_OVRD_START_DATE | Account Override Start Date | No |
| $ACCOUNT_OVRD_END_DATE | Account Override Stop Date | No |
| $ELECTION | FSA/HSA Account Election_ | No |
| $MATCH | Annual Match | No |
| $USER_FIELD_GROUP_ID | Custom<50,1> | No |
| $USER_FIELD_MEMBER_NO | Custom<50,2> | No |
| $WAIVE_REASON | Waive Reason | No |
| $COVRD_DATA | EE and Dependent ids of covered | No |
| $UWQ_DATA | Underwriting questions | No |
| SKIP | Skip this column | No |
| $DEDUCT_AMT | Plan Year to Date Deductions | No |
| $REIMB_AMT | Plan Year to Date Reimbursements | No |
| $DEDN_OVER_AMT | Deduction Override | No |
| $MATCH_OVER_AMT | Match Override | No |
| $PERIODS | Periods | No |
| $TYPE_OVER_DATE | Over Date | No |
| $HDHP_FLAG | HDHP Not Required? | No |
| $OVERRIDE_CONTRIB_LIMITS | Suppress Contribution Limits? | No |
| $HSA_PEO_MATCH_OVERRIDE | HSA PEO Match Override | No |
Note: Note: While importing data on the Benefit Import Maintenance form, you can identify employees by Employee ID, SSN, or Clock Number.
While importing data on the Benefit Import Maintenance form, you can now identify employees by Employee ID, SSN, or Clock Number.
Set up translation tables.
Click Save to update your import definition settings or click Save as New to reuse existing settings and save the definition under a new ID and description. The system displays a success message that all settings were saved.
You also have the option of deleting the import definition.
Use translation tables to convert codes found in the data file to standard action codes that PrismHR software uses. External action codes are located in an external data file, and standard action codes correspond to external action codes.
Options include:
Action Translations: Enter action codes found in the external data file in this column. Enter the corresponding standard action codes in the next column.
Client Translations: Enter company IDs found in the external data file in this column. Enter the corresponding standard company IDs in the next column.
Plan Translations: Enter benefit plan codes found in the external data file in this column. Enter the corresponding standard benefit plan codes in the next column.
Plan Type Translations: Enter plan type (coverage levels) found in the external data file in this column Enter the corresponding standard plan types in the next column.
Network Translations: Enter network codes found in the external data file in this column. Enter the corresponding standard network IDs in the next column.
In the Translation Tables dialog box, click Actions. The Benefit Import Actions Translation Table form opens.
To indicate the action the system should take for each line of data, enter the External Action Codes found in the data file and the corresponding Standard Action Codes from the following table.
Code Name — Description
ADD — Creates a new benefit enrollment.
WAIVE — Waives coverage for an existing enrollment.
CHANGE — Changes the plan type/coverage of an existing enrollment.
TERM — Terminates an existing enrollment.
DEPEN+ — Adds a covered dependent to an existing enrollment. You can also use this to add covered dependents to a new enrollment, as long as the new enrollment occurs in the file before the line that adds the dependent.
BENEF+ — Adds a beneficiary to an existing enrollment. You can also use this to add a beneficiary to a new enrollment, as long as the new enrollment occurs in the file before the line that adds the beneficiary.
DEPEN- — Removes a covered dependent from an existing enrollment.
BENEF- — Removes a beneficiary from an existing enrollment.
ENROLLFSA — Creates a new flexible spending account (FSA) enrollment.
ENROLLHSA — Creates a new health savings account (HSA) enrollment.
TERMFSA — Terminates an existing flexible spending account (FSA) enrollment.
TERMHSA — Terminates an existing health savings account (HSA) enrollment.
CHANGEFSA — Changes the plan type/coverage in an existing flexible spending account (FSA) enrollment.
CHANGEHSA — Changes the plan type/coverage in an existing health savings account (HSA) enrollment.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Benefits_Enrollment_Plan_Details.htm
Path:
OBE/Benefits Enrollment/Topics/Benefits_Enrollment_Plan_Details.htm
To set up information about available benefit plans for new hires and employees to view during their enrollments, upload required documents, and set up benefit plan dependencies, use the Benefits Enrollment Plan Details form.
To select what to do:
Click Back Office.
From System|Change, select Benefits Enrollment Plan Details.
In What would you like to do today? select an option:
Define Offer Type Level Setup. For more information, see Defining Offer Type Setup.
Define Plan Level Setup. For more information, see Defining Plan Level Setup.
The system opens the selected tab, but you can switch to another tab as needed. If you do this, the system prompts you to save or discard any unsaved changes.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Benefits_Enrollment_Trace_Log.htm
Path:
OBE/Benefits Enrollment/Topics/Benefits_Enrollment_Trace_Log.htm
When an employee logs in and begins the enrollment process, the system determines the benefit plans to display and calculates the employee costs for each benefit plan by applying a series of checks on each form in the workflow. You can view a record of these checks in the Benefits Enrollment Trace form.
The Tracing tool is especially useful for troubleshooting and finding errors when you set up benefits and open enrollments. If a user made an error in setting up a workflow or a benefit plan, tracing provides a way to find the error. You can then make any needed corrections to enable employees to access the correct benefit plans and view correct calculations for the costs of the available plans.
The Benefit Enrollment Trace form displays data only for a form that is currently open and active in an enrollment. It can display details for only one form at a time.
Note: Note: You must be logged in to an enrollment using the correct employee credentials. Also, the form whose details you want to view must be open and active to use this tool.
Before you begin:
Verify that the correct client record is shown near the top of the form. If it is not, click it and then select the correct client. If the correct client is not selected, the system cannot access system checks for the client’s enrollments.
Log in to the enrollment using the employee’s login credentials, and open the form to view. The form opens in the enrollment.
To trace benefit enrollment:
On the HR menu, select HR|View > Benefits Enrollment Trace.
Enter the Employee ID and click Reload.
The system checks (for the form that is open and active in the enrollment) are shown in the table.
You can click Download to save a text file of the trace log.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/BEPD_Define_Offer_Type_Level_Setup.htm
Path:
OBE/Benefits Enrollment/Topics/BEPD_Define_Offer_Type_Level_Setup.htm
In the Define Offer Type Level Setup panel, use the Comparison Fields and Offer Type Dependency tabs to set up benefit plan details at the offer type level. The system prompts you to select the offer type to set up and opens the selected tab. You can switch to another tab as needed. Before you switch to the other tab, the system prompts you to save or discard any unsaved settings.
Use this tab — To do this
Comparison Fields — Define the benefit plan information options employees can view for the offer type. Corresponding plan specific information is set up in Plan Details.
Offer Type Dependency — Set up dependencies at the offer type level. The system prompts you to select an offer type from the list. It applies the settings you define to all benefit plans that have that offer type selected.
To define the benefit plan information options employees can view in all plans that have the selected offer type during enrollments, use the Comparison Fields tab. After you set up the options, you can set up the values in each individual benefit plan using the Details tab in the Define Plan Level Setup panel.
An employee can review this benefit plan information, including costs for employee and dependents, co-pays, deductibles, and so on. An employee can also compare information for up to three benefit plans within the offer type during enrollment.
To define the benefit options available to employees:
Click Back Office.
From System|Change, select Benefits Enrollment Plan Details.
In What would you like to do today? select Define Offer Type Level Setup > Comparison Fields.
Select the Offer Type for the benefit plan to configure. The Comparison Fields tab displays.
A table is shown where you can enter the options for the information to include. You can enter as many options as needed. You can also import multiple fields using the Plan Offer Type Import form.
Use this option — To define this
Display Comparison Fields — How to display the benefit plan information options.
…even if empty in all plans — All options entered are displayed, even if there is no corresponding value entered for them at the plan level in the Details tab in the Define Plan Level Setup panel. This is the default setting.
…only if filled in all plans — The only options displayed are those that have a corresponding value entered for them at the plan level in the Details tab in the Define Plan Level Setup panel.
Allow Waive in Benefit Enrollment — The option is allowed to waive coverage to display in all benefit plans that have the offer type selected. See Setting Up Employee Waive Options for more information about other system and client-level settings that affect employee waive options.
| Use this option | To define this |
|---|---|
| Description | The field name to display during enrollments. Required. |
| Display Summary option | Whether to include the field in the Display Summary during enrollments. |
| Display Comparison option | Whether to include the field in the Display Summary during enrollments. |
To modify the name of an option, click [Image: screenshot] (Edit).
To remove an option, click [Image: screenshot] (Delete).
To rearrange options, click and hold [Image: screenshot] (Rearrange) for an option and then drag the option higher or lower in the list. Note that when an option is moved, the values defined for the option on the Details tab of the Define Plan Level Setup panel do not move with the option and must be updated manually. For more information, refer to Defining Plan Level Setup.
To save settings, click Save.
To save settings and close the tab, click Save and Close.
To close the tab without saving settings, click Cancel.
To delete the record, click Delete.
To set up dependencies at the offer type level, use the Offer Type Dependency tab. For example, if plans with the offer type Domestic Partner Medical (MDP) require the employee to enroll in a dependency plan with the offer type Medical (MED), the employee can select any available plan that has the MED offer type.
Tier-based dependencies further limit which benefit plans are available to employees during enrollments. The option to set up additional dependencies is available only in offer types that use tiers. It is not available in life insurance or disability benefit plans, which use coverage levels rather than tiers.
To set up dependencies for offer types:
Open the Offer Type Dependency tab.
Select the offer type to use as a dependency, and then click Add. The Offer Type Dependency is shown in the table.
You can add as many dependencies as needed. The type being viewed in the form requires enrollment in one of the specified dependencies.
To remove a dependency, click [Image: screenshot] (Delete).
Tier — Description
Exact Tier — Dependency plans must have a tier level that is an exact match for the tier or coverage level selected in the plan that requires the dependency.
Limited Tier — Dependency plans can have a tier level that includes the tier or coverage level selected in the plan that requires the dependency.
To save settings, click Save.
To save settings and close the tab, click Save and Close.
To close the tab without saving settings, click Cancel.
To delete the record, click Delete.
If you switch to another tab, the system prompts you to save any unsaved settings.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/BEPD_Define_Plan_Level_Setup.htm
Path:
OBE/Benefits Enrollment/Topics/BEPD_Define_Plan_Level_Setup.htm
In the Define Plan Level Setup panel, you can use the following tabs to set up benefit plan details for specific benefit plans offered during enrollments.
Use this tab — To do this
Plan Details — Enter plan specific information to go with the options set up in Comparison Fields for the benefit plans you offer to employees during enrollments.
Documents — Attach a Summary of Benefits Document and additional Supporting Documents to the benefit plan record.
Plan Dependency — Set up dependencies at the plan level.
Terms & Conditions — Enter content for terms and conditions that the user must acknowledge. This content displays for all confirmation forms
To set up plan details:
Click Back Office.
From System|Change, select Benefits Enrollment Plan Details.
In What would you like to do today? select Define Plan Level Setup > Plan Details.
Select the Offer Type, Plan Description, and Effective Date for the benefit plan to configure. You can enter multiple effective dates as needed for the benefit plan selected in the Plan Description list. Each effective date creates a new record, allowing you to enter contribution information on the same benefit plan for different enrollment periods. You also have the following options:
To enter a new effective date for the plan, click New Date.
To copy all settings to a new effective date and create a duplicate record, click Copy Date.
To enter plan specific information for the benefit plans offered to employees during enrollments, use the Details tab.
To enter specific information about a benefit plan:
For this option — Define this information
Field — The benefit plan information options for the offer type set up in the Comparison Fields tab in the Define Offer Type Level Setup panel.
Value — Corresponding information about the options.
Additional Plan Details displays the following options:
Option — Description
PCP Lists — If benefit plans require primary care physician (PCP) information, the URL where employees can look up their PCP. Typically, these are health maintenance organization (HMO) medical plans, but some dental or voluntary benefit plans might also require this information. This list is shown only for benefit plans that have the Collect PCP Information option enabled in the Web Enrollments Parameters panel on the Group Benefit Plans form.
Participation Requirement — How to track carrier plan participation requirements at the system level to ensure client and employee enrollments abide by carrier guidelines. Percentages must be from 1 to 100%.
Plan Application — At the system level, you can enable employees to complete a carrier plan application through Benefits Enrollment, enter a website URL to a carrier application. When defined, the Plan Application link displays in the Required forms section of the benefit plan tile. When an employee clicks the link, the application opens in a new browser window. > Note: Note: This feature is only for the Medical (MED), Dental (DEN), and Vision (VIS) offer types.
Description Text — Enter a description for the plan application link.
Use aggregate spouse maximum — Whether the maximum coverage for the employee’s spouse should not exceed the aggregate coverage amount of an employee’s basic and additional life insurance plan selections. You must select Require Basic Life Enrollment if you select Use Aggregate Spouse Maximum.
To attach a Summary of Benefits document and additional supporting documents to the benefit plan record, use the Documents tab.
Life insurance and disability plans display an additional option to attach an Evidence of Insurability (EOI) form. If you attach an EOI form, you must also enter an Evidence of Insurability Message to display during enrollments.
Before you begin:
To attach documents to a benefit plan:
Select the Documents tab.
In Summary of Benefits Document, click Add and select a document from the search list that opens.
In Supporting Documents, click Add and select a document to attach from the search list that opens. You can repeat this step to include additional supporting documents.
The names of the selected documents display in Summary of Benefits Document and Supporting Documents.
To update an attached file, click [Image: screenshot] (Edit), make changes if necessary, and then click Upload New Version.
To remove an attached file, click [Image: screenshot] (Delete).
To set up dependencies at the plan level, use the Plan Dependency tab. For example, a domestic partner medical plan that you select might require the employee to enroll in a specific medical benefit plan as well.
If this dependency is set up at the plan level, you can specify which benefit plans are required. The employee can select only those benefit plans.
To set up plan dependencies:
Select the Plan Dependency tab.
In Offer Type, select the offer type.
In Plan Description, select the benefit plan to use as a dependency.
Click Add. The specified plan displays as a dependency in the table.
You can add as many dependencies as needed. The benefit plan being viewed in the form requires enrollments in one of the specified dependencies.
To remove a dependency, click [Image: screenshot] (Delete).
The option to set up additional dependencies is available only in offer types that use tiers. It is not available in life insurance or disability benefit plans, which use coverage levels rather than tiers.
Tier — Description
Exact Tier — Dependency plans must have a tier level that is an exact match for the tier or coverage level selected in the plan that requires the dependency.
Limited Tier — Dependency plans can have a tier level that includes the tier or coverage level selected in the plan that requires the dependency.
In Benefits Enrollment, employees cannot submit their enrollment without affirming the terms and conditions. If they decline, a warning message displays indicating what they must do to proceed. After submitting their enrollment, the affirmation displays on the Benefit Confirmation Statement.
To enter content asking employees to affirm or decline the terms and conditions provided, use the Terms & Conditions tab. This content displays for all confirmation forms, based on the plan offerings.
| Use this option | To define this |
|---|---|
| Display Terms and Conditions | The Terms and Conditions as defined by the carrier for the plan. |
| Acknowledgment Question | The employee and proxy question to show with the acknowledgment check box. - Example employee question: Have you read and understand the Terms and Conditions? - Example proxy message: Have you reviewed the Terms and Conditions with the employee? You can edit the default text in the text boxes. |
To save settings, click Save.
To save settings and close the tab, click Save and Close.
To close the tab without saving settings, click Cancel.
To delete the record, click Delete.
If you switch to another tab, the system prompts you to save any unsaved settings.
In some cases, insurance companies require employees to complete underwriting questions to enroll in benefit plans. Underwriting questions determine whether an employee can enroll in a benefit plan based on the response. For example, when enrolling in a benefit plan, the system could ask an employee, “Does this coverage replace or change any existing insurance?” Based on the response, the system could deny employee enrollment. To configure required questions for enrollment, use the Underwriting Questions option when defining plan level setup.
Underwriting Questions are only available for the following offer types:
| - LTD - Long Term Disability | - ACC - Accident Benefits |
|---|
On the Underwriting Questions tab, click Add. The Add/Edit Underwriting Questions dialog box displays.
Complete the following:
| Use this option | To define this |
|---|---|
| Question | The underwriting question. The character limit is 500 characters. |
| Response Type | The type of response: - Yes/No: The employee selects Yes or No. - Multiple Choice: The employee selects a multiple choice option. To add multiple choice options, click [Image: screenshot] . To delete multiple choice options, click [Image: screenshot] . |
After adding underwriting questions, you can:
Click [Image: screenshot] to move the question in the order of the list.
Click [Image: screenshot] to delete the question.
Click [Image: screenshot] to edit the question.
After adding underwriting questions to a benefit plan in PrismHR, they display in a BE workflow when electing plan coverage. The BE benefit plan tiles now have an Underwriting tab where employees can answer any necessary questions. If a benefit plan requires employees to answer underwriting questions, they cannot elect coverage until they answer.
After an employee answers underwriting questions for an elected benefit plan and submits their enrollment, the questions and responses display on the Benefit Confirmation Statement. The questions and responses also display on the employee benefits enrollment record in PrismHR. You can view this information on the Employee Benefits Enrollment form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/BIP_Benefits_Import_Process.htm
Path:
OBE/Benefits Enrollment/Topics/BIP_Benefits_Import_Process.htm
The Benefits Import Process enables you to enroll employees in group benefit plans using the information in an external data file. The process requires you to set up a data file and a benefit import definition.
Before you begin:
The data file must be either tab-delimited or comma-delimited. It must include the following columns of information, in any order:
Company ID
Employee ID, Employee SSN, or Employee Clock Number
Offer Type
Benefit Plan ID
Benefit Plan Type
Effective Date
Action Codes
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/BIP_Creating_the_Benefit_Import_Definition.htm
Path:
OBE/Benefits Enrollment/Topics/BIP_Creating_the_Benefit_Import_Definition.htm
The benefit import definition defines the layout of the data file and provides a template to interpret the data. It also contains tables that let you translate codes found in the data file into standard PrismHR codes.
To define the data layout:
| Use this option | To define this |
|---|---|
| Import Definition ID | The type of plan to import. The following definition IDs are for Benefits Enrollment only. They are already set up in the system with the correct import fields and translation tables and cannot be changed. - NGBEPOST: Imports group benefit plans into Benefits Enrollment - NGBEFSPOST: Imports flexible spending plans into Benefits Enrollment |
Answer the following questions with either Y for yes, or N for no.
Unless the PrismHR Customer Support Team instructed you to do otherwise, leave Special Program After Import blank.
To enter the import fields:
In the Benefit Import Definition Maintenance form, click F5-Import Fields. The Benefit Import Fields Maintenance form opens.
Enter the Field Names to include in the data file. The fields you enter define the headers and their order in the data file, as shown in the following tables.
For the definition ID NGBEPOST, the field names displayed in the following table are already set up and you cannot change them. (PrismHR Benefits Enrollment only.)
| Field Name | Description | Required? |
|---|---|---|
| $ACTION | Action Type | Yes |
| $COMPANY | Company ID | Yes |
| $EMPLOYEE_ID | Employee ID | Yes |
| $OFFER_TYPE | Offer Type | Yes |
| $PLAN_ID | Benefit Plan ID | Yes |
| $EFFECTIVE_DATE | Benefit Plan Effective Date | Yes |
| $DEDN_START | Deduction Start Date | No |
| $DEDN_ENDS | Deduction End Date | No |
| $SECTION_125 | Section 125 Y/N? | No |
| $NETWORK | Network ID | Yes, if network plans are included |
| $DOCTOR_ID | Employee’s Primary Care Physician ID | No |
| $DOCTOR_NAME | Employee’s Name of Primary Care Physician | No |
| $PLAN_TYPE | Benefit Plan Type | Yes |
| $EE_COVERAGE | Employee Coverage Amount | No |
| $SPS_COVERAGE | Spouse Coverage Amount | No |
| $DPN_COVERAGE | Dependent Coverage Amount | No |
| $EE_GI_OVER | Employee Guaranty Issue Overlimit Amount | No |
| $SP_GI_OVER | Spouse Guaranty Issue Overlimit Amount | No |
| $DP_GI_OVER | Dependent Guaranty Issue Overlimit Amount | No |
| $PREMIUM | Benefit Premium Amount | No |
| $CONTRIB | Employee Contribution Amount | No |
| $DEPN_ID | Dependent ID | Yes, if covered dependent is included |
| $DEPN_DOCTOR_ID | Dependent’s Primary Care Physician ID | No |
| $DEPN_DOCTOR_NAME | Dependent’s Primary Care Physician Name | No |
| $BENEF_ID | Beneficiary ID | No |
| $BENEF_TYPE | Beneficiary Type | No |
| $BENEF_PCNT | Percent of Beneficiary Coverage | No |
| $BENEF_PREC | Beneficiary Precedence | No |
| $WAIVE_REASON | Reason for waiving coverage | No |
| $ENROLL_STATUS | Employee Enrollment Status | No |
| $COVRD_DATA | Employee and Dependent IDs covered | Yes |
For the definition ID NGBEFSPOST, the field names displayed in the following table are already set up and you cannot change them. (PrismHR Benefits Enrollment only.)
| Field Name | Description | Required? |
|---|---|---|
| $ACTION | Action Type | Yes |
| $COMPANY | Company ID | Yes |
| $EMPLOYEE_ID | Employee ID | Yes |
| $OFFER_TYPE | Offer Type | Yes |
| $EFFECTIVE_DATE | Benefit Plan Effective Date | Yes |
| $PLAN_ID | Benefit Plan ID | Yes |
| $PLAN_TYPE | Benefit Plan Type | Yes |
| $PLAN_YEAR | Benefit Plan Year | No |
| $PLAN_OVERD_START_DATE | Plan Override Deduction Start Date | No |
| $PLAN_OVERD_END_DATE | Plan Override Deduction End Date | No |
| $ACCOUNT_TYPE | Flex Spending Account Type | No |
| $ELECTION | Employee Election Amount | No |
| $ACCOUNT_OVERD_START_DATE | Account Override Deduction Start Date | No |
| $ACCOUNT_OVERD_END_DATE | Account Override Deduction End Date | No |
| $MATCH | Employer Matching Contribution | Yes |
For any other definition ID, you can enter the field names displayed in the following table.
| Field Name | Description | Required? |
|---|---|---|
| $ACTION | Action Type | Yes |
| $COMPANY | Company ID | Yes |
| $EE_SSN | Employee SSN | Yes (or $CLOCKNO) |
| $CLOCKNO | Employee Clock Number | Yes (or $EE_SSN) |
| $PLAN_ID | Benefit Plan ID | Yes |
| $EFFECTIVE_DATE | Benefit Plan Effective Date | Yes |
| $PLAN_TYPE | Benefit Plan Type | Yes |
| $DEDN_START | Deduction Start Date | No |
| $PREMIUM | Benefit Premium Amount | No |
| $CONTRIB | Employee Contribution Amount | No |
| $SECTION_125 | Section 125 Y/N? | No |
| $NETWORK | Network ID | Yes, if network plans are included |
| $DEPN_SSN | Dependent Social Security Number | Yes if adding or removing a covered dependent |
| $DEPN_FNAME | Dependent First Name | Yes if adding a covered dependent |
| $DEPN_LNAME | Dependent Last Name | Yes if adding a covered dependent |
| $DEPN_SPOUSE | Dependent is a Spouse? | Yes if adding a covered dependent |
| $EE_COVERAGE | Employee Coverage Amount | No |
| $SPS_COVERAGE | Spouse Coverage Amount | No |
| $DEPN_COVERAGE | Dependent Coverage Amount | No |
The system uses translation tables to convert codes found in the data file to the standard action codes that PrismHR uses. Each line of the data file must be mapped to an action code (set up in the Benefit Import Action Translation Table form).
The definition IDs NGBEPOST and NGBEFSPOST are already set up in the system with the correct translation tables. You cannot change these settings. If you enter any other definition ID, use the following procedures.
In the Benefit Import Fields Maintenance form, click F6-Translation Tables.
In the Translation Tables dialog box, select the translation table to set up:
Actions
Company
Plan IDs
Plan Types
Networks
First, you must specify the action codes found in the data file and map them to the standard action codes used by PrismHR. This is required.
In the Translation Tables dialog box, click Actions. The Benefit Import Actions Translation Table form opens.
To indicate the action the system should take for each line of data, enter the External Action Codes found in the data file and the corresponding Standard Action Codes from the following table.
Code Name — Description
ADD — Creates a new benefit enrollment.
WAIVE — Waives coverage for an existing enrollment.
CHANGE — Changes the plan type/coverage of an existing enrollment.
TERM — Terminates an existing enrollment.
DEPEN+ — Adds a covered dependent to an existing enrollment. You can also use this to add covered dependents to a new enrollment, as long as the new enrollment occurs in the file before the line that adds the dependent.
BENEF+ — Adds a beneficiary to an existing enrollment. You can also use this to add a beneficiary to a new enrollment, as long as the new enrollment occurs in the file before the line that adds the beneficiary.
DEPEN- — Removes a covered dependent from an existing enrollment.
BENEF- — Removes a beneficiary from an existing enrollment.
ENROLLFSA — Creates a new flexible spending account (FSA) enrollment.
ENROLLHSA — Creates a new health savings account (HSA) enrollment.
TERMFSA — Terminates an existing flexible spending account (FSA) enrollment.
TERMHSA — Terminates an existing health savings account (HSA) enrollment.
CHANGEFSA — Changes the plan type/coverage in an existing flexible spending account (FSA) enrollment.
CHANGEHSA — Changes the plan type/coverage in an existing health savings account (HSA) enrollment.
In the Translation Tables dialog box, click Company. The Benefit Import Company Translation Table form opens.
To denote the company, enter the External Company Code found in the data file and the corresponding Translated Company Code.
Press F2-Save. The system returns you to the Translation Tables dialog box.
In the Translation Tables dialog box, click Plan IDs. The Benefit Import Plan Translation Table form opens.
To denote the benefit plans to include, enter the External Plan ID found in the data file and the corresponding Translated Plan ID.
Press F2-Save. The system returns you to the Translation Tables dialog box.
In the Translation Tables dialog box, click Plan Types. The Benefit Import Plan Type Translation Table form opens.
To denote the benefit plan types or coverage levels, enter the External Plan Type found in the data file and the corresponding Translated Plan Type.
Press F2-Save. The system returns you to the Translation Tables dialog box.
In the Translation Tables dialog box, click Networks. The Benefit Import Network Translation Table form opens.
To denote the benefit networks to include, enter the External Network ID found in the data file and the corresponding Translated Network ID .
Press F2-Save. The system returns you to the Translation Tables dialog box.
Click Exit. The system returns you to the Benefit Import Definition Maintenance form.
Click F2-Save.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/BIP_Using_the_Benefit_Rules_Import_Definition.htm
Path:
OBE/Benefits Enrollment/Topics/BIP_Using_the_Benefit_Rules_Import_Definition.htm
Use the following procedures to create the benefit rules import file and to import benefit rules information into PrismHR from a tab-delimited text file.
Note: Note: You can download data import template files for importing benefit rules information. Log on to the Customer Resource Center and search for import template file for more information.
The following table shows the layout of the tab-delimited text file to use to import benefit rules.
| XLS | Field Name | Field # | Type | Length | Req? | Description |
|---|---|---|---|---|---|---|
| A | ACTION | 1 | A | 6 | R | Enter the action code for this import (Add, Change, or Term only). |
| B | COMPANY.ID | 2 | A | 7 | R | A valid COMPANY.MASTER item. |
| C | GROUP.ID | 3 | A | 8 | R | Needs to be a valid BENEFIT.GROUPS item |
| D | PLAN.ID | 4 | A | 8 | R | Needs to be a valid BENEFIT.PLANS item that is also set up with a COMPANY.BENEFITS item. |
| E | NETWORK.ID | 5 | A | 8 | O | Must be a valid network ID for a Plan where Billing Rates vary by Network |
| F | EFF.DATE | 6 | D | 10 | R | MM-DD-YYYY format |
| G | SEQ | 7 | N | 5 | R | Numeric integer starting with 1 and incremented by 1 for each additional row. Columns 1 thru 6 need to be repeated for each sequence. |
| H | CONTRIB.BY | 8 | A | 1 | R | - E - Employee - C - Client - Null Value |
| - E - Employee | ||||||
| - C - Client | ||||||
| - Null Value | ||||||
| I | TAKE.ON.XMPT | 9 | A | 1 | O | Must be Y or N or Null value |
| J | CONTRIB.PLAN.ID | 10 | A | 8 | O | Must be a valid BENEFIT.PLANS item |
| K | CONTRIB.RATE.GROUP | 11 | A | 8 | O | Must be a valid Billing Rate Group RATE.GROUPS item |
| L | PLAN.TYPE | 12 | A | 4 | O | - E1 - Employee + 1 - EC - Employee + Child - EE - Employee - FAM - Family |
| - E1 - Employee + 1 | ||||||
| - EC - Employee + Child | ||||||
| - EE - Employee | ||||||
| - FAM - Family | ||||||
| M | CONTRIB.MTHD | 13 | A | 2 | O | P - Percentage F - Fixed FP - Fixed (EE), Percent (DEP) PF - Family |
| N | CONTRIB.AMT | 14 | N | 8 | R | Must be a valid amount greater than zero. |
| O | DEP.CONTRIB.AMT | 15 | N | 8 | R | Must be a valid amount greater than zero. |
| P | ELIG.STATUS | 16 | A | 3 | O | Must be a valid Employment Status Class: A - Active L - On Leave T - Terminated |
| Q | ELIG.AGE | 17 | N | 2 | O | Must a numeric integer from 0 to 99 |
| R | ELIG.TYPE | 18 | A | 3 | O | Must be a valid Employee Type Code EMPLOYEE.TYPE.CODES item |
| S | ELIG.DAYS | 19 | N | 3 | O | Must a numeric integer from 0 to 999 |
| T | ELIG.DAYS.FROM | 20 | A | 1 | O | Must be ‘H’ or ‘S’ or a null value |
| U | ELIG.FLSA.STATUS | 21 | A | 1 | O | Must be ‘E’ or ‘N’ or a null value |
| V | UPDATE.PLAN.TO.GROUP | 22 | A | 1 | 0 | Must be Y or N or a null value. |
| W | DAYS.OR.MONTHS | 23 | A | 1 | 0 | Indicates days or months service until employees are eligible for plan (defines ELIG.DAYS): D - Days M - Months Null value - Plan does not base eligibility on service days/months.. |
| X | ELIG.DATE.USED | 24 | A | 1 | 0 | Eligibility date used: O - If calculated date is the first of the month, use that date. Otherwise, use the first day of the following month. F - First of month after calculated date. C - Use calculated eligibility date. Null value - No eligibility date calculation used for plan. |
| Y | PLAN.APPLICATION.URL | 25 | The plan’s application URL. | |||
| Z | PLAN.APPLICATION.DESC | 26 | The plan’s application description. | |||
| AA | MULTIPLIER | 27 | The pay multiplier. | |||
| AB | ROUND.METHOD.120 | 28 | The rounding method. | |||
| AC | ROUND.TIMING | 29 | Round before or after. | |||
| AD | COVERAGE.MIN | 30 | Coverage minimum. | |||
| AE | COVERAGE.MAX | 31 | Coverage maximum. | |||
| AF | COVERAGE.AMT | 32 | Coverage amount. | |||
| AG | ADD.TO.COV | 33 | Add to calculated coverage. | |||
| AH | LIFE.YOS | 34 | Years of service for life. | |||
| AI | LIFE.YOS.PAY.MULT | 35 | Pay multiplier for life. | |||
| AJ | MULT.PAY.CODE | 36 | Multiplier pay basis. | |||
| AK | PERCENT.BASE.115 | 37 | Percentage base. | |||
| AL | BENEFIT.AMT | 38 | The benefit amount. | |||
| AM | LTD.YOS | 39 | Years of service for long term disability. | |||
| AN | LTD.MAX.COVERAGE | 40 | Maximum coverage for long term disability. | |||
| AO | LTD.BASE.CALC | 41 | Alternate base calculation for long term disability. | |||
| AP | FROM.SALARY.D | 42 | From annual salary (for salary banded disability plans only). | |||
| AQ | TO.SALARY.D | 43 | To annual salary (for salary banded disability plans only). | |||
| AR | LTD.STD.COV | 44 | Coverage for short and long term disability (for salary banded disability plans only). | |||
| AS | NETWORK.STOP.DATE | 45 | Network availability stop date. |
Use the following procedure to import benefit rules information from a tab-delimited text file.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/BIP_Using_the_Benefits_Import_Definition.htm
Path:
OBE/Benefits Enrollment/Topics/BIP_Using_the_Benefits_Import_Definition.htm
Use the following procedures to create the benefit import file and import benefits information into the system from a tab-delimited text file.
Note: Note: The PrismHR Customer Support Team provides import file templates for Company Benefits, Group Benefit Plans, Flex Spending Plans, and Benefit Rules. To download these templates, search for Knowledge Base article Import Template for Company Benefits in the Customer Resource Center.
You must create the Company Benefits Import file to convert your company benefits data. The following tables show the layout for the tab-delimited text file. You can use the field names listed in the tables as headers in the Benefits Import file:
If you used the Definition ID NGBEPOST to import group benefit plans, use the field names provided in the following table. (PrismHR Benefits Enrollment only.)
| XLS | Field Name | Field # | Type | Length | Req? | Description |
|---|---|---|---|---|---|---|
| A | ACTION | 1 | A | 6 | R | Enter the action code for this import (Add, Change, or Term only). |
| B | COMPANY | 2 | A | 7 | R | A valid Company ID |
| C | EMPLOYEE_ID | 3 | A | 6 | R | A valid Employee ID |
| D | OFFER_TYPE | 4 | A | 3 | R | A valid Offer Type. |
| E | EFFECTIVE_DATE | 5 | D | 10 | R | MM-DD-YYYY format |
| F | PLAN_ID | 6 | A | 10 | R | A valid Benefit Plan ID |
| G | PLAN_TYPE | 7 | A | 2 | R | A valid Plan Type. |
| H | DEDN_START | 8 | N | 10 | O | Deduction Start Date, MM-DD-YYYY format |
| I | DEDN_ENDS | 9 | D | 10 | O | Deduction End Date, MM-DD-YYYY format |
| J | SECTION_125 | 10 | D | 1 | O | Indicate Section 125 Y/N? |
| K | NETWORK | 11 | A | 10 | R | Network ID, if network plans are included |
| L | DOCTOR_ID | 12 | A | 1O | O | Employee’s Primary Care Physician ID |
| M | DOCTOR_NAME | 13 | A | 20 | O | Name of employee’s Primary Care Physician |
| N | EE_COVERAGE | 14 | N | 10 | O | Employee Coverage Amount |
| O | SPS_COVERAGE | 15 | N | 10 | O | Spouse Coverage Amount |
| P | DPN_COVERAGE | 16 | N | 10 | O | Dependent Coverage Amount |
| Q | EE_GI_OVER | 17 | N | 10 | O | Employee’s Guaranty Issue Overlimit Amount |
| R | SP_GI_OVER | 18 | N | 10 | O | Employee Spouse’s Guaranty Issue Overlimit Amount |
| S | DP_GI_OVER | 19 | N | 10 | O | Employee Dependent’s Guaranty Issue Overlimit Amount |
| T | PREMIUM | 20 | N | 10 | O | Benefit Premium Amount |
| U | CONTRIB | 21 | N | 10 | O | Employee Contribution Amount |
| V | DEPN_ID | 22 | N | 4 | R | Dependent ID if covered |
| W | DEPN_DOCTOR_ID | 23 | A | 10 | O | Dependent’s Primary Care Physician ID |
| X | DEPN_DOCTOR_NAME | 24 | A | 20 | O | Dependent’s Primary Care Physician Name |
| Y | BENEF_ID | 25 | N | 4 | O | Beneficiary ID |
| Z | BENEF_TYPE | 26 | A | 1 | O | Beneficiary Type (P/C) |
| AA | BENEF_PCNT | 27 | N | 6 | O | Percent of Beneficiary Coverage |
| AB | BENEF_PREC | 28 | N | 6 | O | Beneficiary Precedence |
| AC | WAIVE_REASON | 29 | A | 20 | O | Reason for waiving coverage |
| AD | ENROLL_STATUS | 30 | A | 2 | O | Employee Enrollment Status |
| AE | COVRD_DATA | 31 | A | 20 | O | Employee and Dependent IDs covered |
If you used the Definition ID NGBEFSPOST to import flexible spending plans, use the field names provided in the following table. (PrismHR Benefits Enrollment only.)
| XLS | Field Name | Field # | Type | Lgth. | Req? | Description |
|---|---|---|---|---|---|---|
| A | ACTION | 1 | A | 6 | R | Enter the action code for this import (Add, Change, or Term only). |
| B | COMPANY | 2 | A | 7 | R | A valid Company ID |
| C | EMPLOYEE_ID | 3 | A | 6 | R | A valid Employee ID |
| D | OFFER_TYPE | 4 | A | 3 | R | A valid Offer Type. |
| E | EFFECTIVE_DATE | 5 | D | 10 | R | MM-DD-YYYY format |
| F | PLAN_ID | 6 | A | 10 | R | A valid Flex Plan ID |
| G | PLAN_TYPE | 7 | A | 2 | R | A valid Plan Type. |
| H | PLAN_YEAR | 8 | N | 4 | O | MM-DD-YYYY format |
| I | PLAN_OVERD_START_DATE | 9 | D | 10 | O | MM-DD-YYYY format |
| J | PLAN_OVERD_END_DATE | 10 | D | 10 | O | MM-DD-YYYY format |
| K | ACCOUNT_TYPE | 11 | A | 4 | O | MM-DD-YYYY format |
| L | ELECTION | 12 | N | 10 | O | Employee election amount. |
| M | ACCOUNT_OVERD_START_DATE | 13 | D | 10 | O | MM-DD-YYYY format |
| N | ACCOUNT_OVERD_END_DATE | 14 | D | 10 | O | MM-DD-YYYY format |
| O | MATCH | 15 | N | 10 | R | Employee match amount |
If you used any other Definition ID, use the field names in the following table.
| XLS | Field Name | Field # | Type | Length | Req? | Description |
|---|---|---|---|---|---|---|
| A | ACTION | 1 | A | 6 | R | Enter the action code for this import (Add, Change, or Term only). |
| B | COMPANY.ID | 2 | A | 7 | R | A valid COMPANY.MASTER item. |
| C | PLAN.CLASS | 3 | A | 1 | R | - G - Group - F - Flexible Spending - H - HSA Match - R - Retirement - M - Employer Match |
| - G - Group | ||||||
| - F - Flexible Spending | ||||||
| - H - HSA Match | ||||||
| - R - Retirement | ||||||
| - M - Employer Match | ||||||
| D | PLAN.ID | 4 | A | 10 | R | Needs to be an existing Group Benefit Plan BENEFIT.PLANS item for Plan Class G. |
| E | STATUS | 5 | A | 2 | R | A or T |
| F | START.DATE | 6 | A | 10 | R | MM-DD-YYYY format |
| G | STOP.DATE | 7 | A | 10 | R | MM-DD-YYYY format |
| H | COMPANY.BENE.TPA.OVER RIDE | 8 | A | 10 | O | Allows a TPA code to be associated with a Plan at the COMPANY level, where needed. |
| I | RATE.GROUP | 9 | A | 6 | O | Must be an existing rate group RATE.GROUPS item. |
| J | PEND.RATE.GROUP | 10 | A | 6 | O | Must be an existing rate group RATE.GROUPS item. |
| K | PEND.RATE.GROUP.DATE | 11 | D | 10 | O | MM-DD-YYYY format |
| L | BEN.TEMPL.ID | 12 | A | 15 | O | Must be an existing Benefit Rule Template. |
| M | BENE.PREPAY | 13 | A | 1 | R | Y or N |
| N | PREPAY.OFFSET | 14 | A | 1 | O | Y, N, or null value |
| O | YRLY.DEDNS | 15 | N | 2 | R | 48 or 52 |
| P | BEN.COV.ENDS | 16 | A | 3 | R | - T - Benefit coverage ends on termination date - E - Benefit coverage ends on the end of the month - D{99} - where 99 is day of the month coverage ends. (For example, if coverage ends on 14th of month, enter “D14”.) - X - If the employee’s termination date in on or before the 15th of the month, then coverage ends on the 15th, otherwise coverage ends at the end of the month (PrismHR only) |
| - T - Benefit coverage ends on termination date | ||||||
| - E - Benefit coverage ends on the end of the month | ||||||
| - D{99} - where 99 is day of the month coverage ends. (For example, if coverage ends on 14th of month, enter “D14”.) | ||||||
| - X - If the employee’s termination date in on or before the 15th of the month, then coverage ends on the 15th, otherwise coverage ends at the end of the month (PrismHR only) | ||||||
| Q | BENE.CAFE.ELIG | 17 | A | 1 | O | Y, N, or null value |
| R | BENE.FIL.FREQ | 18 | A | 2 | O | - P - Pay Period - M - Monthly - M2 - Monthly, Start Dedn Period 2 - M3 - Monthly, Start Dedn Period 3 - M4 - Monthly, Start Dedn Period 4 |
| - P - Pay Period | ||||||
| - M - Monthly | ||||||
| - M2 - Monthly, Start Dedn Period 2 | ||||||
| - M3 - Monthly, Start Dedn Period 3 | ||||||
| - M4 - Monthly, Start Dedn Period 4 | ||||||
| S | DEDUCT.CYCLE | 19 | A | 2 | O | - P - Pay Period - M - Monthly - M2 - Monthly, Start Dedn Period 2 - M3 - Monthly, Start Dedn Period 3 - M4 - Monthly, Start Dedn Period 4 |
| - P - Pay Period | ||||||
| - M - Monthly | ||||||
| - M2 - Monthly, Start Dedn Period 2 | ||||||
| - M3 - Monthly, Start Dedn Period 3 | ||||||
| - M4 - Monthly, Start Dedn Period 4 | ||||||
| T | OVER.MONTH | 20 | N | 2 | O | Must be in a range of 1 to 12. |
| U | OVER.DAY | 21 | N | 2 | O | Must be in a range of 1 to 28. |
| V | FRINGE.PAY.CODE | 22 | A | 10 | O | Must be a valid Fringe Benefit Pay Code |
| W | HI.MED.BASE.PLAN | 23 | A | 8 | O | Must be an existing Medical Benefit Plan |
| X | BENE.GROUP.1 | 24 | A | 6 | O | Must be a valid Company Benefits Group |
| Y | HI.MED.CALC.1 | 25 | A | 1 | O | Must be Y or N |
| Z | BENE.GROUP.2 | 26 | A | 6 | O | Must be a valid Company Benefits Group |
| AA | HI.MED.CALC.2 | 27 | A | 1 | O | Must be Y or N |
| AB | BENE.GROUP.3 | 28 | A | 6 | O | Must be a valid Company Benefits Group |
| AC | HI.MED.CALC.3 | 29 | A | 1 | O | Must be Y or N |
| AD | BENE.GROUP.4 | 30 | A | 6 | O | Must be a valid Company Benefits Group |
| AE | HI.MED.CALC.4 | 31 | A | 1 | O | Must be Y or N |
| AF | BENE.GROUP.5 | 32 | A | 6 | O | Must be a valid Company Benefits Group |
| AG | HI.MED.CALC.5 | 33 | A | 1 | O | Must be Y or N |
| AH | BENE.GROUP.6 | 34 | A | 6 | O | Must be a valid Company Benefits Group |
| AI | HI.MED.CALC.6 | 35 | A | 1 | O | Must be Y or N |
| AJ | PREM.RISK.FACTOR.DATE.1 | 36 | A | 10 | O | MM-DD-YYYY format |
| AK | PREM.RISK.FACTOR.1 | 37 | A | 10 | O | Must be Y or N |
| AL | PREM.RISK.FACTOR.DATE.2 | 38 | A | 10 | O | MM-DD-CCYY format |
| AM | PREM.RISK.FACTOR.2 | 39 | A | 10 | O | Must be numeric |
| AN | PREM.RISK.FACTOR.DATE.3 | 40 | A | 10 | O | MM-DD-CCYY format |
| AO | PREM.RISK.FACTOR.3 | 41 | A | 10 | O | Must be numeric |
| AP | PREM.RISK.FACTOR.DATE.4 | 42 | A | 10 | O | MM-DD-CCYY format |
| AQ | PREM.RISK.FACTOR.4 | 43 | A | 10 | O | Must be numeric |
| AR | PREM.RISK.FACTOR.DATE.5 | 44 | A | 10 | O | MM-DD-CCYY format |
| AS | PREM.RISK.FACTOR.5 | 45 | A | 10 | O | Must be numeric |
| AT | PREM.RISK.FACTOR.DATE.6 | 46 | A | 10 | O | MM-DD-CCYY format |
| AU | PREM.RISK.FACTOR.6 | 47 | A | 10 | O | Must be numeric |
| AV | PEND.PREM.RATE.GROUP | 48 | A | 6 | O | Must be an existing rate group RATE.GROUPS item. |
| AW | PEND.PREM.RATE.GROUP.DATE | 49 | D | 10 | O | MM-DD-YYYY format |
Use the following procedure to import company benefit information from a tab-delimited text file that will populate the Company Benefits form.
To import the company benefits import file:
Use this option — To define this
Import Pc Folder — The path to the location where the import file is stored.
Import Pc Filename — The filename of the import file. It must be a tab delimited text file, including the file extension (.TXT).
Click F2 - Import.
Verify the information in the company benefits import by selecting Company Administration > File > Company Benefits > Company Benefits.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Bulk-Benefit-Workflows.htm
Path:
OBE/Benefits Enrollment/Topics/Bulk-Benefit-Workflows.htm
This new form is a new bulk creation tool that can create enrollment records simultaneously, so information no longer needs to be added one record at a time. This is especially helpful for take-on clients. Service providers also now have the ability to launch life events in bulk. The form is called Bulk Launch Benefit Workflow and provides these options:
Employee record check boxes where you can select a single or multiple employees. You can also Select All employees with a check box.
Column sorting and filtering.
A record counter at the bottom of the table that displays the total number of items, the number of items displayed that are based on filtering, and the number of items selected or checked.
Data displayed in the table is pulled from the Employee Detail record.
Pre-filtering options for clients, employment type, and employment status.
Two action buttons exist on this form: Launch Life Event and Launch Benefit Enrollment.
View and download reports associated with benefit enrollment changes.
These columns of data are included in the table:
| Column Name | Description | Filter Type |
|---|---|---|
| Client ID | Name of the client. | None |
| Employee ID | ID for an employee. | Type ahead search |
| Employee Name | Name of an employee. | Type ahead search |
| Hire Date | The last hire date for this employee. | Search range, from - through. Format is MM/DD/YYYY. |
| Employer Start Date | The date the employee started with this employer. | Search range, from - through. Format is MM/DD/YYYY. |
| Benefit Group | Description of an employee’s benefit group. | Drop-down search |
| Employment Status | Status of an employee’s employment. | Drop-down search |
| Employment Type | Type of employment. | Drop-down search |
| Active Workflow | Displays the existing workflow ID. If there is no existing workflow, select None. | Modal search |
| Enrollment Type | Displays the type of enrollment, either Benefit Enrollment (BE), Anytime Enrollment (AE), Open Enrollment (OE), or Life Event (LE). | Drop-down search |
Note: Note: You can turn column display on or off by selecting the column name from the drop-down menu next to Enrollment Type.
For employees displayed in the table:
Employees are the same employees listed on the Web Enrollment Configuration form.
All eligible employees are listed, including employees without a workflow enrollment record and employees with a workflow enrollment record.
All employee statuses are displayed except Terminated.
Security restrictions require enforcement on this form, and Service Providers, Worksite Managers, and Worksite Trusted Advisers need access. Security measures determine the companies that these users can view, as well as other data such as department, location, division, and so forth. It also determines what table data these users can see.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Bulk-Launch-Life-Event.htm
Path:
OBE/Benefits Enrollment/Topics/Bulk-Launch-Life-Event.htm
Use the Bulk Launch Life Event form to make bulk life event changes for multiple employees and eliminate the administrative burden of launching individual life event workflows.
To perform bulk life event changes:
Navigate to the Bulk Launch Benefit Workflow form.
Pre-filter clients, employment types, and employment statuses, then click Continue. See Pre-Filtering Bulk Launch Benefit Workflowsfor more information.
Select the desired client and employees (they must have an active workflow).
Click the Launch Life Event button. .The Active Workflows(s) Detected form opens.
Click Continue. The Launch Life Event form opens.
Select a life event from the Select Life Event drop-down (all life event codes are available for selection). For example, changing from Part Time to Full Time.
Select a Life Event Date from the calendar picker. For example, the date when employees become Full Time employees.
Select a notification date from the Date Notified calendar picker.
Click Continue to commit changes. The system runs a process that archives existing workflows (if any) and creates life event workflows. The Bulk Workflow Results form opens and displays a success message if the process completed correctly.
Click Download Results to download the report as a CSV file (the report name is Launch Life Event Results). You cannot access the report after viewing it the first time.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Bulk_Workflow_Results.htm
Path:
OBE/Benefits Enrollment/Topics/Bulk_Workflow_Results.htm
You can download these results as a CSV file by clicking Download Results. The downloaded report name is Launch Benefit Enrollment Results.
The Bulk Workflow Results form provides a way to validate and track bulk changes. You can download these results as a CSV file.
To access this form:
Note: Note: Benefit workflow launch results that are successful displays a Status of Success in the results table.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Changing-Benefit-Workflows-for-Multiple-Employees.htm
Path:
OBE/Benefits Enrollment/Topics/Changing-Benefit-Workflows-for-Multiple-Employees.htm
Use the Bulk Launch Benefit Workflow form to launch benefit workflows for multiple employees at a time.
To access this form and change benefit workflows for multiple employees:
Click Back Office.
From Operations|Action, select Bulk Launch Benefit Workflow. Or, from Work Centers, select Benefit Enrollment Maintenance|Bulk Change Tools|Bulk Launch Benefit Workflow.
Select one or more pre-filter options (optional). You can specify Client(s), Employment Type(s), and Employment Status.
Click Continue to complete pre-filtering. The main Bulk Launch Benefit Workflow form displays.
Note: Note: The form is also available in the Benefit Enrollment Maintenance work center under Bulk Change Tools > Bulk Launch Workflows.
Select one or more employees from the list by clicking the check box next to their names. The employees must be in the same benefit group.
You can narrow the displayed items by filtering or searching for specific items using these column headings:
Column — Description
Client ID — The unique identifier for the client. Click the link to open a multi-select search modal.
Employee ID — The unique identifier for the employee.
Employee Name — The name of the employee.
Hire Date — Date the employee was hired (from - through)
Employer Start Date — The date the employee started with this employer.
Benefit Group — The benefit group the employee is assigned to.
Employment Status — A text string describing an employment status. For example, A for active. This value is defined on the Employee Statuses form.
Employment Type — A text string describing the employment type. For example, FT for full-time. This value is defined on the Employee Types form.
Active Workflow — Displays an existing workflow ID. Search for an ID or select it from the drop-down. If there is no existing workflow, select None.
Enrollment Type — Displays the type of enrollment. Search for an enrollment type or select it from the drop-down. If left blank, it displays all enrollment types. Options are Benefit Enrollment (BE), Anytime Enrollment (AE), Life Event (LE), or OE (Open Enrollment).
For life events, click Launch Life Event (see Bulk Launch Life Event
Click Continue. The Review Workflows form opens.
Review the results. You can change Workflow, Effective Date, Start Date, and End Date.
Make changes as needed, then click Continue. The Bulk Workflow Results form displays.
Click Download Results to download the report as a CSV file (see Downloading Bulk Workflow Results
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Client_Enrollment_Status_by_Workflow.htm
Path:
OBE/Benefits Enrollment/Topics/Client_Enrollment_Status_by_Workflow.htm
The Client Enrollment Status by Workflow Report shows how many employees have either completed or not yet begun the enrollment process. (PrismHR Benefits Enrollment only.)
You can run the report for a specific client or workflow as needed. You can also limit the report to enrollments with a specific starting, ending, or effective date.
If the start, end, or effective dates are missing from a record, one or more of the employees included either has an enrollment assigned that is missing this information or does not have an enrollment assigned. You must fix this by either creating a custom enrollment for employees who do not have an enrollment assigned or by updating their existing enrollments with the correct dates. You can run the Enrollment Status by Workflow/Client report to identify the employees who require this update.
To run the Client Enrollment Status by Workflow report:
Click Reports.
From Benefits|Report, select Client Enrollment Status by Workflow. The Client Enrollment Status by Workflow form opens.
| Use this option | To define this |
|---|---|
| Starting Date | The start date for enrollments to include in the report. |
| Ending Date | The ending date for enrollments to include in the report. |
| Effective Date | The effective date for enrollments to include in the report. |
| Client ID | The client to include in the report. Required. |
| Workflow Type | The workflow type to include in the report. Required. - Enrollment: The workflow is for benefits enrollments (BE), open enrollments (OE), or life event enrollments. - Onboarding: For future development. Does not currently impact the functionality of PrismHR. |
Column — Description
Workflow — The workflow for the enrollment.
Client — The client for the enrollment.
Start Date — The start date for the enrollment.
End Date — The end date for the enrollment.
Effective Date — The effective date for the enrollment.
Not Started — The number and percentage of the client’s employees who have not started the enrollment process.
In Progress — The number and percentage of the client’s employees whose enrollments are currently in progress.
Completed — The number and percentage of the client’s employees whose enrollments are completed.
Total Employees — Total number of the employees whose enrollments are not started, in progress, or completed.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Client_Enrollment_Summary.htm
Path:
OBE/Benefits Enrollment/Topics/Client_Enrollment_Summary.htm
The Client Enrollment Summary Report displays a summary of all enrollments for clients using Benefits Enrollment. It displays the percentage of employees who have not started, have enrollments in progress, or have completed their enrollments.
To run the Client Enrollment Summary report:
Click Reports.
From Operations|Report, select Client Enrollment Summary Report. The Client Enrollment Summary Report form opens. The report displays information in the following columns.
Column — Description
Client ID — The client’s ID number. If needed, you can view more detail by clicking the link to run the Client Enrollment Status by Workflow Report.
Client Name — The client’s name.
Enrollment Type — The enrollment type (New Hires, Open Enrollment, or both).
Not Started (%) — The percentage of employees whose enrollments are not yet started.
In Progress(%) — The percentage of employees whose enrollments are in progress.
Completed (%) — The percentage of employees whose enrollments are completed.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Client_Workflow_Grid.htm
Path:
OBE/Benefits Enrollment/Topics/Client_Workflow_Grid.htm
Use the Client Workflow Grid form to assign, at the client level, the workflows to use during enrollments.
You create enrollment workflows in the Workflow Library. You can also assign workflows at the system level. Settings you define at the client level override system-level settings.
The Min # of Overlap days designates the limited amount of time an employee has to complete the open enrollment workflow when the workflow start date plus the Min # of Overlap days extends beyond the open enrollment window. This option is used only in an enrollment workflow overlap scenario.
If the start date is the date the first workflow is submitted, 4/25/19, the system checks the Min # of Overlap days on the grid and adds that number of days to the Start Date Window. It then calculates a date of 4/27/19. The system then checks the End Date Window on the grid.
If the calculated date is greater than the end date on the grid, the system uses the calculated date.
If the end date is in the past, 4/23/19, the system uses the calculated date of 4/27/19 for the workflow end date.
If the dates are equal, 4/27/19, the system uses the calculated date of 4/27/19 for the workflow end date.
If the end date is in the future, 5/3/19, the workflow end date is 5/3/19.
If the Min # of Overlap days is left blank, the system uses the current logic of same length as window dates; the length between start date window and end date window.
Use the Filter Records panel to filter system-level workflows by entering the OE Start Date and OE End Date, and then clicking Search.
Use First, Prev, Next, and Last to navigate through the workflow history.
View the total number of records, which displays in the lower right-hand corner.
Use the Filter Records panel to filter system-level workflows by entering the OE Start Date and/or OE End Date, then clicking Search.
Use First, Prev, Next, and Last to navigate through the workflow history in the records table.
View the total number of records, which displays in the lower right-hand corner.
To create a new workflow assignment to use during enrollments:
Click Back Office.
From System|Change, select Client Workflow Grid. The Client Workflow Grid form opens.
Click Add Row. The Add a New Record panel opens.
| Use this option | To define this |
|---|---|
| Client ID | The Client ID. Required. You can hover over a Client ID to view the corresponding Client Name. |
| Effective Date | The date that the benefits that are offered in the workflow become effective for an employee. For example if the enrollment elections start coverage on 06/01/2018,enter that date. Required. |
| BE Workflow | The BE Workflow to use for benefit enrollments. The list displays all active workflows in the Workflow Library. |
| BE Open Window Length | The number of days from the Effective Date during which an employee can enroll in benefits. |
| Min # of Overlap days | The Min # of Overlap days designates the limited amount of time an employee has to complete the open enrollment workflow when the workflow start date plus the Min # of Overlap days extends beyond the open enrollment window. This option is used only in an enrollment workflow overlap scenario. |
| AE Workflow | The Anytime Enrollment workflow. |
| OE Workflow | The OE Workflow to use for open enrollments. The list displays all active workflows in the Workflow Library. |
| OE Start Date and OE End Date | The start and end dates to use for open enrollments. The OE Start Date is the first day that employees can review and make elections during the Open Enrollment period. The OE End Date is the last day that the employees can submit elections. The OE Start Date and OE End Date must fall before the workflow Effective Date. |
| WF End Date | The last day that benefits are active and cover the employee. If the Effective Date for the benefits is 06/01/2018, the WF End Date is 05/31/2019, the End Effective Date. This option is required and cannot be earlier than the OE End Date. |
| Enable Notifications | The Enable Notifications option to use for the record. You must set up notifications to enable notifications on workflows. - All OFF: Disable notifications for all enrollment types - BE Only: Turn on notifications only for benefit enrollments - OE Only: Turn on notifications only for open enrollments - AE Only: Turn on notifications only for anytime enrollments - All ON: Enable notifications for all enrollment types |
Click Save. The record displays in the records table.
If needed, assign additional workflows.
Click Save.
You use an existing workflow assignment as the basis of a new one by copying it and assigning a new effective date. For example, you can copy the information from a previous year to use for the current year.
To copy a workflow assignment:
In the System Workflow grid, click Copy New. The Copy an Existing Record panel displays.
Enter the Client ID for the workflow to copy.
Enter the Effective Date for the record to copy.
Enter the New Effective Date for the record to create.
Click Save. The record maintains the settings from the original record and displays the new effective date in the Records panel.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Configuring_Web_Enrollment.htm
Path:
OBE/Benefits Enrollment/Topics/Configuring_Web_Enrollment.htm
Use the following settings in the Group Benefit Plans Web Enrollment Parameters panel when setting up enrollments.
Some medical and dental benefit plans enable or require employees to enter information about their primary care provider (PCP) during enrollment.
To offer the benefit plan in open enrollments, select Include in Open Enrollments. If you do not select this option, the benefit plan is not included.
To give employees the option to enter PCP information, select Collect PCP Information. When you select this option, PCP Required becomes active.
To require employees to enter PCP information, select PCP Required.
You must also specify a URL where employees can look up their PCP in PCP Lists in the Details tab in the Benefits Enrollment Plan Details form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Create-Ben-Enroll-Statements.htm
Path:
OBE/Benefits Enrollment/Topics/Create-Ben-Enroll-Statements.htm
Benefits Enrollment Statements contain employee election data required to complete enrollment with an insurance carrier. To generate and download Benefits Enrollment Statements, use the Create Enrollment Statements form and the Download Enrollment Statements form. These statements can also be viewed, downloaded, and printed using the Manage Documents form if the user’s role has been granted access to the Benefits Enrollment Statements document category. Benefits Enrollment Statements are for Service Providers only.
Note: Note: You can only create and download enrollment statements for batches posted on June 13th, 2020, and later.
To add the document category to your user role:
Click Back Office.
From System|Change, select User Roles. The User Roles form opens.
In Role ID, select your user role.
ClickActions menu [Image: screenshot] and select Document Security. The Document Security form displays.
Click Add. The Document Security Selection form displays.
From the list, select Benefits Enrollment Statements and click Accept. The document category displays on the Document Category Security form.
Click Save.
After adding the document category to your user role, you can create and download employee enrollment statements.
To create enrollment statements:
Click Back Office.
From Operations|Action, select Create Enrollment Statements. The Create Enrollment Statements form opens.
Complete the following:
| Use this option | To do this |
|---|---|
| Start Date | Select a start date. Required. Date cannot be in the future. |
| End Date | Select an end date. Required. Date cannot be in the future. |
| Batch ID | Select a posted batch number from the selected date range. |
In Batch ID, select the posted batch number to create enrollment statements. If the batch has documents to generate, the Generate button displays.
Click Generate.
Click Status. The panel shows information about the PDFs created and the PDFs that failed to generate. For any PDFs that fail to generate, click Generate to run the process again.
After creating enrollment statements, you can download them with the Download Enrollment Statements form.
To download enrollment statements:
Click Back Office.
From Operations|Action, select Download Enrollment Statements. The Create Enrollment Statements form opens.
In Select Batch Id, select the posted batch number to download enrollment statements.
Click Get Employees. The list shows employees with generated PDF enrollment statements.
Click Download Statements. The statements download to your machine in a compressed zip file.
[Image: screenshot]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Create_Custom_Form_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Create_Custom_Form_BE.htm
You can create a custom form in the Form Library. If you use this option, you are building the form from scratch and must add and configure all of the fields you want to include.
To create a custom form:
Click Back Office.
From System|Change, select Form Library. The Form Library opens.
Click Create New Form. The Create New Custom Form opens.
For this option — Define this information
New Form ID — The ID for the new form. Required.
Form Name — A name for the form. Required. PrismHR recommends using spaces, not hyphens. Hyphenated words do not wrap correctly in Benefits Enrollment.
Description — A description of the form.
Workflow Type — Benefit Enrollment. Required.
Onboarding — For Onboarding only.
General Tab
The New Form ID, Version, Revision, Status, Start Date, End Date, Workflow Type, and Offer Type are read-only. The system populates Form Name and Description with the information entered on the previous form, but you can edit it as needed.
Layout Tab
In Fields, select the type of field to include (Text, Inline Image, Checkbox, and so on). Enter the number of fields to include, then click Add New Field. The form displays the new fields.
Expand the field and click Field ID to configure content. The Field Details panel opens. The parameters vary, depending on the field type selected.
For File Hyperlink and Inline Image, click Add File to attach documents, images, or other media to the field.
Add and configure fields as needed until you have built the form.
To preview the form before saving, click Preview Form.
To return to the Form Library without saving changes, click Back to Forms Library.
Option — Description
Immediately — The system sets the form status immediately to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the form status to Inactive, changing it to Active on the start date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the start date for the new version as its End Date.
Save as Draft — The form status is set to Draft. The system does not set a Start Date nor does it set version or revision numbers for the form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Creating%20Confirmation%20Forms_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Creating Confirmation Forms_BE.htm
The Confirmation form is where the employee submits benefit selections and completes the enrollment process during enrollments. It can include a message, documents, images, and other media.
The Confirmation Form template includes a header and a series of prebuilt fields that you can modify as needed.
The Confirmation form works in conjunction with the Benefit Summary form, the previous form in the workflow. The employee can access the Confirmation form only after clicking Next on the Benefit Summary form. This summarizes the employee’s benefit selections and lets the employee review and make changes to benefit selections.
The Benefit Summary and Confirmation forms are both required for benefits and open enrollments to process correctly.
When you submit a form, the system sets the form’s version and revision numbers.
To create a new Confirmation form:
Click Back Office.
From System|Change, select Form Library. The Form Library opens.
Click the Name on the Confirmation Form template. The Confirmation Form Template opens.
Click the form ID to edit the form. The Edit Custom Form form opens.
General Tab
The Version, Revision, Status, Start Date, End Date, Workflow Type, and Offer Type are read-only.
| For this option | Define this information |
|---|---|
| Form ID | A unique ID for the new form. Required. |
| Form Name | The editable name of the form. Required. |
| Description | The editable description of the form. Required. |
Layout Tab
Click Header and Footer to expand the Header/Footer Detail panel and customize the Field Default Value as needed. The Field ID and Field Type are read-only.
Configure fields as needed until you have built the form. You can click any of the prebuilt paragraph fields to expand the Field Details panel and customize the Field Default as needed. The Field Type and Field ID are read-only.
In Confirmation Verbiage, set up a confirmation statement to display above the e-signature field during enrollments. The Field Default Value displays the default verbiage but you can change it. The Confirmation Verbiage is required and you cannot delete it.
Select one of the following options:
To preview the form before saving, click Preview Form.
To return to the Form Library without saving changes, click Back to Forms Library.
Option — Description
Immediately — The system sets the form status immediately to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the form status to Inactive, changing it to Active on the start date. Since there can only be one active version of the form, the system changes the status of any prior active version to Inactive and sets the start date for the new version as its End Date.
Save as Draft — The form status is set to Draft. The system does not set a Start Date nor does it set version or revision numbers for the form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Creating%20Welcome%20Forms_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Creating Welcome Forms_BE.htm
The Welcome form introduces the employee to the enrollment process and the workflow. It is recommended but optional. It can include introductory material or a message, including documents, images, and other media.
The Welcome Form template includes a header and a series of prebuilt options that you can modify as needed.
When you submit a form, the system sets the form’s version and revision numbers.
To create a new Welcome form:
Click Back Office.
From System|Change, select Form Library. The Form Library opens.
On the Welcome Form template, click Name. The Welcome Form Template opens.
Click the form ID to edit the form. The Customize Prebuilt Form form opens.
General Tab
In the General tab, the Version, Revision, Status, Start Date, End Date, Workflow Type, and Offer Type are read-only.
| For this option | Define this information |
|---|---|
| Form ID | A unique ID for the new form. Required. |
| Form Name | The editable name of the form. Required. |
| Description | The editable description of the form. Required. |
Layout Tab
You can click any of the prebuilt paragraph fields to expand the Field Details panel and customize the Field Default as needed. The Field Type and Field ID are read-only.
Configure fields as needed until you have built the form.
Select one of the following options:
To preview the form before saving, click Preview Form.
To return to the Form Library without saving changes, click Back to Forms Library .
Option — Description
Immediately — The system sets the form status immediately to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the form status to Inactive, changing it to Active on the start date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the start date for the new version as its End Date.
Save as Draft — The form status is set to Draft. The system does not set a Start Date nor does it set version or revision numbers for the form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Creating_a_Workflow_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Creating_a_Workflow_BE.htm
To create workflows for enrollments, use the Workflow Library form. You can also use this form to add notifications to send to employees or groups during enrollments. As you create the workflow, you are also building the workflow’s navigation menu structure that the employee views during the enrollment. The forms in the workflow display in the navigation menu in the same order in which you arrange them.
To create a custom workflow for enrollments:
Click Back Office.
From System|Change, select Workflow Library. The Workflow Library opens.
Click Create New Workflow. The Create New Workflow form displays.
For this option — Define this information
ID — A unique workflow ID. Required.
Name — A unique name for the workflow. Required.
Workflow Type — Enrollment. The type of enrollment. The Onboarding workflow type is used only to create workflows in Onboarding
Start Date, End Date — Inactive. You set these dates when you submit the workflow.
To create a custom workflow for enrollments based on an existing form:
Click Back Office.
From System|Change, select Workflow Library. The Workflow Library opens.
Click Duplicate on the form to clone. The Duplicate Form form displays.
| For this option | Define this information |
|---|---|
| ID | A unique workflow ID. Required. |
| Name | A unique Name for the workflow. Required. |
| Version | Select the version of the form to be duplicated. Required. |
The lists displayed in the Process tab are for the Welcome, Benefits Summary, and Confirmation forms.
You can click
[Image: screenshot]
(Edit) next to the list to edit the form’s display name.
To define the process:
Select the Process tab.
Select the form to use from each list. You can clear the I-9 option if you do not want to include the I-9 forms in the workflow.
Select Approve Every Employee Enrollment if an administrator must approve all enrollments.
You must set up a user as a Benefit Approver (if the user is a worksite manager) or Benefit Manager (if the user is a service provider) for this option to be available. You must also set up an approval policy at the system level.
Select HSA Request to inform employees that they must complete certain forms when selecting a high deductible health plan and provide a link to download the forms. Then, enter a message in the Title field and the Message field. Options are available for both English and Spanish. To add documents for employees to download, click Add to select a document to upload.
Click Save.
You can add forms to the workflow by dragging them from the Forms Available panel to the Forms Selected panel and organizing them in the appropriate order. Forms in bold are prebuilt forms.
You can organize forms into categories. This is especially helpful for workflows that include many forms. The category displays in the navigation menu, and the included forms for each category display as sub-menu items.
To add forms:
Select the Forms tab.
Click Add Category in the Forms Selected panel. The Category Name dialog box opens.
Enter the Category Name and click Save. The category displays in the Forms Selected panel.
Click and drag forms into the Form Selected panel and arrange in categories in the appropriate order. You can change the name of a category or form by clicking [Image: screenshot] (Edit). To remove a category or form from the Forms Selected panel, click x.
You must create notifications and set up recipients for them to be available to assign to workflows. See Notification Templates (Enrollments) for more information about creating notification templates. See Notification Recipients (Enrollments) for more information assigning notification recipients.
When you submit a workflow, the system sets the workflow’s version and revision numbers.
To create notifications and submit the workflow:
Select the Notifications tab.
Select Enabled for each notification to attach to the workflow.
Click Save. The Submit Workflow dialog box opens.
Select one of the following options:
Option — Description
Immediately — The system sets the workflow status immediately to Active, and sets the current date as the Start Date. Since there can be only one active version of the workflow, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the workflow status to Inactive, changing it to Active on the start date. Since there can be only one active version of the workflow, the system changes the status of any prior active version to Inactive and sets the start date for the new version as its End Date.
Save as Draft — The workflow status is set to Draft. The system does not set a Start Date nor does it set version or revision numbers for the workflow .
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Creating_Benefits_Summary_Forms_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Creating_Benefits_Summary_Forms_BE.htm
The Benefit Summary form summarizes the employee’s benefit selections and enables the employee to review and make changes to benefit selections during enrollments. It can include introductory material, a message, documents, images, and other media.
The Benefit Summary and Confirmation forms are required for enrollments to process correctly. The prebuilt Benefit Summary form includes a header and footer that you can modify as needed. The rest of the content is prebuilt for you. The Benefit Summary form works in conjunction with the Confirmation form. The employee must click Next on the Benefit Summary form during an enrollment to access the Confirmation form, submit benefit selections, and complete the enrollment process.
When you submit a form, the system sets the form’s version and revision numbers.
To create a new Benefit Summary form:
Click Back Office.
From System|Change, select Form Library. The Form Library opens.
Click the Name on the Benefit Summary Form template. The Benefit Summary Form Template opens.
Click the form ID to edit the form. The Customize Prebuilt Form form opens.
General Tab
In the General tab, the Version, Revision, Status, Start Date, End Date, Workflow Type, and Offer Type are read-only.
| For this option | Define this information |
|---|---|
| Form ID | A unique ID for the new form. Required. |
| Form Name | The editable name of the form. Required. |
| Description | The editable description of the form. Required. |
Layout Tab
Insert Link: For future development. Does not currently impact the functionality of PrismHR.
Click ConfirmHeader, ConfirmFooter, ProxyHeader, and ProxyFooter and modify as needed.
Select one of the following options:
To preview the form before saving, click Preview Form.
To return to the Form Library without saving changes, click Back to Forms Library.
Option — Description
Immediately — The system sets the form status immediately to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the form status to Inactive, changing it to Active on the start date. Since there can only be one active version of the form, the system changes the status of any prior active version to Inactive and sets the start date for the new version as its End Date.
Save as Draft — The form status is set to Draft. The system does not set a Start Date nor does it set version or revision numbers for the form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Creating_New_Welcome_Etc_Forms_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Creating_New_Welcome_Etc_Forms_BE.htm
Benefits Enrollment provides special templates in the Form Library, similar to the prebuilt forms. You can use the templates to create Welcome and Confirmation forms for enrollments. The Form Library also provides a prebuilt Benefits Summary form that works in conjunction with the Confirmation form.
Note: Note: A Welcome form is recommended for workflows, but optional. The Benefit Summary and Confirmation forms are required for enrollments to process correctly.
You can filter the list of forms and find the template or prebuilt form you need by entering a Name, Date of Creation, Status, or Workflow Type, and clicking Filter.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Dashboard_BE.htm
Path: OBE/Benefits Enrollment/Topics/Dashboard_BE.htm
The PrismHRDashboard provides quick access to company information and relevant features. The information shown in the Chart and List sections of the Perspective panel reflects the client selected.
To view onboarding tasks within Benefits Enrollment, in the Chart section of the Perspective panel, select Benefit Enrollments by Status from the list.
[Image: screenshot]
The chart in the Perspective panel displays enrollment tasks and their statuses. You can use the type list to filter the type of enrollment to view in the Dashboard (All Types, Benefit Enrollment Only, Open Enrollment Only, Life Event Only, Anytime Enrollment Only). When you select an enrollment type, the system displays the number of employee enrollments available.
| Status | Description |
|---|---|
| In Progress | The employee has either not started, or has started but not yet completed the enrollment. |
| Waiting for Approval | The employee has submitted the enrollment, and the enrollment is awaiting approval. |
| Ready to Review | The employee’s enrollment is approved, and in the posting queue. At this point, the enrollment might be included or not yet included in a batch. |
| Ready to Post | The employee’s enrollment is in a batch, has passed review, and is ready to post. |
| Post/Review Failure | The employee’s enrollment is in a batch, but has either not passed review or failed to post. |
| OE Eligible | Employees included in this status are eligible for open enrollment. OE eligibility is determined as follows: - Benefits Enrollment Enabled must be selected in the Global Configuration form. - If the client restricts eligible benefit plans (by Department, Benefit Group, Division, or Location) using the Eligible Benefits Determinant in Client Details, the system checks list of Eligible Benefits at the restriction level to see if the benefit plans are active and the employee is OE eligible. If no list of Eligible Benefits is entered at the restriction level, the system excludes the employee’s benefit group and the employee is not OE eligible. - If the client lists the employee’s status as eligible in the Benefits Enrollment Eligibility Criteria panel in the Client Details form, the employee is OE eligible. If the client has not listed eligible statuses in this panel, the system excludes terminated employees from being OE eligible. Employees who are not terminated are OE eligible. - If the client lists the employee’s type as eligible in the Benefits Enrollment Eligibility Criteria panel in the Client Details form, the employee is OE eligible. If the client has not listed eligible types in this panel, the employee’s type must have Eligible For On-line Benefit Enrollment selected at the system-level in Employee Types for the employee to be OE eligible. |
The List section displays the individual benefit enrollment records for the type selected. You can further filter benefit enrollment records that display in the list by clicking a status in the pie chart. The list updates, and the colored dot that displays next to each item matches the color in the pie chart section.
The table displays the following columns.
| Column | Description |
|---|---|
| Employee Name | The employee’s name. |
| Employee ID | The employee’s ID. |
| Start Date | The start date for the enrollment workflow. |
| End Date | The end date for the enrollment workflow. |
| Effective Date | The enrollment effective date. |
| Workflow | The name of the enrollment workflow. |
| Status | The status for the enrollment. |
| Actions | An action to perform for a specific enrollment record. The following options are available: - Archive: Archives the enrollment record. The system displays an informative message and prompts you to confirm Yes or No. If you click Yes, the system archives the record and displays a confirmation message when complete. Click OK to close.Click OK to close. - Extend: Changes the enrollment End Date and extends the enrollment period for the employee. The system displays a dialog box where you can enter the new end date and click Extend to save. - Proxy: Performs a proxy enrollment in the Proxy Login form. - View Web Enrollment: Displays the enrollment record in the Web Enrollment Configuration form. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Document_Repository.htm
Path:
OBE/Benefits Enrollment/Topics/Document_Repository.htm
Use the Document Repository to upload and manage documents. You can upload pdf, jpg, jpeg, tif, tiff, png, and gif files. When uploaded, you can use the files to create forms for enrollments in the Form Library. Benefits Enrollment users can attach documents to benefit plan records in the Comparison Fields tab in the Benefits Enrollment Plan Details form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/DR_Editing.htm
Path: OBE/Benefits Enrollment/Topics/DR_Editing.htm
You can modify file settings to maintain and organize your files.
To edit a document:
Click Back Office.
From System|Change, select Document Repository.
Click the Name of the file. The Document Settings dialog box opens.
Modify the File Label, Description, File Classification, File Tags, and File Version Number. The Security Level for the document is read-only and you cannot change it. The File Classification and at least one File Tag are required to save changes.
Select one of the following options:
To update the document with a new version, click Upload New Version. The system prompts you to navigate to the location of the file to upload and select the file.
To save changes, click Save.
To delete the file, click Delete.
To view the file, click Preview.
To download the file, click Download.
To return to the Document Repository without saving changes, click Close.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/DR_SearchingFiltering.htm
Path:
OBE/Benefits Enrollment/Topics/DR_SearchingFiltering.htm
PrismHR provides various ways to search and filter files in the Document Repository. The total number of documents displays in the lower left-hand corner of the Document Repository.
| Search Option | Description |
|---|---|
| Select documents to display | Displays a specific set of documents. - Public and Client—The set contains all public and client documents. This is the default. - Employee for Client ID—The set contains all employee documents for the selected client ID. The set does not contain public and client documents. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/DR_Uploading.htm
Path: OBE/Benefits Enrollment/Topics/DR_Uploading.htm
You can upload a single document to the Document Repository. You can also upload a .ZIP file containing multiple documents.
You must assign uploaded documents unique names within their selected security level. The system displays an error message if you assign a document the same name and security level as an existing document in the Document Repository.
To upload a document:
Click Back Office.
From System|Change, select Upload a Document. The Document Upload dialog box opens.
| For this option | Define this information |
|---|---|
| File Label | The label to display when you include the document in forms (for example, Blue Cross Blue Shield PPO Benefit Summary). The file label is optional. If you do not enter a file label, the name of the file displays by default (for example, BCBS_PPO.pdf). |
| Description | A description of the document. Required. |
| File Classification | A classification for the form. Required. |
| File Tags | One or more tags to categorize the file (Medical, Dental, Forms, Images, and so on). File tags are shown in the Document Repository and are used to organize files so that users can find them easily. At least one file tag is required. |
| File Version | A version number for the file if you plan to maintain different versions of it. The system does not update file versions. If you upload a later version of the file, you must manually enter the new version number. |
| Select level for saving file | A level for the file to determine who can access the document. - Public - All users can access the document. - Client - The system prompts you to enter the Client ID. All employees who work for the client you specify can access the document. - Employee - The system prompts you to enter both Client and Employee IDs. Only the employees that you specify will be able to access the document. |
Click Choose File, navigate to the location of the file to upload, and then select the file.
Click Upload.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/DR_Uploading_Multiple_Documents.htm
Path:
OBE/Benefits Enrollment/Topics/DR_Uploading_Multiple_Documents.htm
Using .ZIP file format, you can upload multiple documents to the Document Repository. Documents can include logos and other images, PDF files, spreadsheets, and other types of files.
For bulk uploads, construct .ZIP files exactly as follows. Any variation causes the upload to fail.
Use PKZIP or the Compressed (zipped) folder option in Windows Explorer to create a .ZIP file that contains the documents for bulk upload.
Do not use any implementation‑specific features or the file does not extract correctly.
Encryption, passwords, or other security measures are not supported, and cause the upload to fail.
Arrange the folders and files in the .zip file following the directory structure, with three sub-folders (client, employee, public) contained in the root folder.
Files placed in the root directory (that is, outside the sub-folders shown) and files placed in any other sub-folders are not supported and cause the upload to fail. Directory names must be in lowercase.
| Sub-folder | Description |
|---|---|
| client | Files in this folder are restricted by Client ID after upload in the Document Repository. - The folder name and all sub-folder names must be in lowercase (client). - The client folder must contain one sub-folder per client, with the folder name set to match the Client ID (including any leading zeroes). For example, if the Client ID is 1908, the sub-folder for that client must be named 1908. - The client documents should be placed inside the client sub-folder. No additional sub-folders are permitted. |
To upload the .ZIP file:
Click [Image: screenshot] (Back Office).
From System|Change, select Document Repository.
Click Bulk Upload (Zip). The Upload window opens.
Click Choose File and select the .ZIP file to upload.
Click Submit. After the upload completes, the system automatically extracts the documents, stores them in the Document Repository, and generates a metadata.csv file. You can review for errors and edit as needed, with the following restrictions:
Do not change the value in the first column (uuid).. The system uses this value to locate the files in the document repository. Do not remove the first row containing the column headings.
The columns userClassification, label, description, and version are strings and are always treated as a single value.
Classification labels must match the classifications in the Document Repository.
To avoid processing errors, do not use quotation marks inside any of the column values.
In the userTags column, specify multiple tags by separating them with a comma.
To import the metadata.csv file into PrismHR, use the Metadata Import Entry form, located in the Back office menu under System > Action. The metadata.csv file is generated when you upload multiple files to the Document Repository using the bulk upload.
This is the final step in uploading multiple files to the Document Repository. You must complete it for the files the files to display correctly.
To import the metadata.csv file into PrismHR:
Click Back Office.
From System|Action, select Metadata Import Entry.
Click Start Import. The Upload window opens.
Click Choose File, and select the file to upload.
Click Submit. The imported data displays. If the file contains invalid information, the system displays an error.
To view the data, click Done with Errors
To scroll through the report, click Next Page and Previous Page.
To discard the data, click Cancel.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/EDI%20History%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/EDI History Report.htm
more of an audit report to compare the employee bill rate to the actual premium rate being paid to the carrier and see the variance if any. This is not a billing reconciliation report based on actual payroll data and generates the billed vs. premium amounts from the Group Benefit Plan Billing and Premium rates.
Note: Note: This form does not use Client Access Group Security.
To access the form, click Reports. Under Operations|Report, click EDI History Report.
To generate the EDI History Report:
Field Name — Description
EDI File ID — This field is optional. Leave it blank for the report to run for all EDI files. If you want to run it for a particular EDI file, enter it here.
Original Client ID — This field is optional. This is the original billed Client ID. This would normally be blank for a test download. Leave this field blank for this report to run for all clients. If you want to restrict this report to run for a selected client, enter the Client ID here or click the Original Client ID link and select it from the Select Client dialog box.
Process Date On or After — This is the date the invoice was processed. This field is optional. Leave this field blank for the report to run for all EDI process dates. If you want to restrict this report to run from a particular EDI process date, enter it here.
Process Date On or Before — This is the date the invoice was processed. This field is optional. Leave this field blank for the report to run for all EDI process dates. If you want to restrict this report to run up to a particular EDI process date, enter it here.
Invoice Date On or After — This is the invoice date for the item being submitted through EDI. This field is optional. Leave this field blank for the report to run for all invoice dates. If you want to restrict this report to run from a particular invoice date, enter it here.
Invoice Date On or Before — This is the invoice date for the item being submitted through EDI. This field is optional. Leave this field blank for the report to run for all invoice dates. If you want to restrict this report to run up to a particular invoice date, enter it here.
EDI Agent ID — Enter the EDI Agent ID here.
Click Run to generate the report. The report shows up on screen.
Click Clear to clear the form at any time.
Click Close to close this form.
This Detail report shows the following columns:
EDI File ID
Invoice Date
Original Client Name
Cill to Client ID
EDI Amount
Invoice Number
Location Code
Agent Type
Agent ID
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Employee%20Benefit%20Register%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Employee Benefit Register Report.htm
Use this form to generate a report to show the various employee benefit registers for a client. You can also view this report for the various employee benefit registers broken out by worksite location codes.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, in the Work Centers panel, under Onboarding & Benefits, click Benefit Imports & Reporting. Under Benefit Reporting, click Employee Benefit Register Report.
To generate the Employee Benefit Register Report:
| Field Name | Description |
|---|---|
| Enrollment Status Codes | Enter the status of the benefit plans for the employee that you want to report on. Select one or more from the following options: - Eligible Unenrolled - Active Enrollment - Terminated Enrollment - COBRA Enrollment - Waived Enrollment |
Click Generate Report. The report shows up on the screen.
Click XLS to download the report.
Click Clear to refresh the screen at anytime.
The Report has the following columns:
Location/Description
Employee Name/Title
Group - Benefit Group
Plan ID
Network ID
St - Enrollment Status Codes
Cov Eff Date - Coverage Effective Date
Type
EE/SP/DE Cov
Premium Amount
Company Contribution
Employee Contribution
HI 1.5% - Hawai 1.5% Benefit Plan
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Employee_Enrollment_Progress_Report.htm
Path:
OBE/Benefits Enrollment/Topics/Employee_Enrollment_Progress_Report.htm
The Employee Enrollment Progress Report lists the enrollment progress for employees participating in an enrollment. This enables you to review which workflow steps in an employee’s enrollment are complete, and which are still pending. (PrismHR Benefits Enrollment only.)
You can run this report for a specific client, employee, or workflow as needed. You can also limit the report to enrollments with a specific starting, ending, or effective date.
If the start, end, or effective dates are missing from a record, one or more of the employees included either has an enrollment assigned that is missing this information or does not have an enrollment assigned. You must fix this by either creating a custom enrollment for employees who do not have an enrollment assigned or by updating their existing enrollments with the correct dates. You can run the Enrollment Status by Workflow/Client report to identify the employees who require this update.
To run the Employee Enrollment Progress report:
Click Reports.
From Benefits|Report, select Employee Enrollment Progress Report. The Employee Enrollment Progress Report form opens.
| Use this option | To define this |
|---|---|
| Starting Date | The start date for enrollments to include in the report. |
| Ending Date | The ending date for enrollments to include in the report. |
| Effective Date | The effective date for enrollments to include in the report. |
| Client ID | The client to include in the report. Required. |
| Workflow Type | The workflow type to include in the report. Required. - Enrollment: Tthe workflow is for benefits enrollments (BE), open enrollments (OE), and life event enrollments. - Onboarding: For future development. Does not currently impact the functionality of PrismHR. |
Column — Description
Workflow — The workflow ID.
Client — The client’s name and ID.
Employee ID — The employee’s name and ID.
Start Date — The start date for the enrollment.
End Date — The end date for the enrollment.
Effective Date — The effective date for the enrollment.
Progress Step — The step number and name in the workflow.
Status — The employee’s enrollment status (Eligible, Not Eligible, Pending, Waived, Completed) for the specified step.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Enrollment_Form_Library_Fields.htm
Path:
OBE/Benefits Enrollment/Topics/Enrollment_Form_Library_Fields.htm
The Form Library is where you create and manage forms by adding field options to them. You use forms to create workflows in the Workflow Library. Some options use the images or documents uploaded in the Documents Repository form.
To add fields to a custom form:
Click [Image: screenshot] (Back Office).
From System|Change, select Form Library. The Form Library opens.
Using the Layout tab on the Edit Custom form, drag the preferred Field Types from the Field Type list to the designated section on the right. Users of the custom form can change Field Types noted as editable. For example, they can select or clear a Check box.
Select a field type and click Configure. The Field Details panel opens. Field parameters vary, depending on the type of field selected, and they are required.
Click Save.
All fields require the following parameters in the Field Details panel.
Parameter — Description
Field ID — Enter a new Field ID. It must begin with an alphabetic character, contain at least two characters, and have no spaces.
Field Type — Select the field type from the list.
Field Label — Enter the field label to display in the form to indicate what the user should enter in the field (for example, Last Name for a Text field).
Field Group — For future development. Does not currently impact the functionality of PrismHR.
The following table describes the types of fields available in the Form Library and describes any additional parameters required for each field.
Field — Description
Text Area — A field where employees can enter multiple lines of information. Additional Parameters: | Field Constraints | The constraints for the data in the field: . | | — | — | | Field Default Value | The default value to display in the field. | | Required | Whether data is required for the field. Yes or No. | | Disabled | Whether the field is disabled. Yes or No. |
Field Constraints — The constraints for the data in the field: .
Field Default Value — The default value to display in the field.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Textfield — A field where employees can enter a valid e-mail address. Additional Parameters: | Field Constraints | The constraints for the data in the field: . | | — | — | | Field Default Value | The default value to display in the field. | | Required | Whether data is required for the field. Yes or No. | | Disabled | Whether the field is disabled. Yes or No. |
Field Constraints — The constraints for the data in the field: .
Field Default Value — The default value to display in the field.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
E-mail — A field where employees can enter a valid e-mail address. Additional Parameters: | Field Default Value | The default value to display in the field. | | — | — | | Required | Whether data is required for the field. Yes or No. | | Disabled | Whether the field is disabled. Yes or No. |
Field Default Value — The default value to display in the field.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Password — A field where employees can enter a password. Additional Parameters: | Field Constraints | The constraints for the data in the field: . | | — | — | | Min, Max | The minimum and maximum number of characters to enter in the field. | | Field Default Value | The default value to display in the field. | | Required | Whether data is required for the field. Yes or No. | | Disabled | Whether the field is disabled. Yes or No. |
Field Constraints — The constraints for the data in the field: .
Min, Max — The minimum and maximum number of characters to enter in the field.
Field Default Value — The default value to display in the field.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Radio Button — A field where employees can select one option from a set of related options. You can enter as many radio buttons as needed. Additional Parameters: Field Options — Click Add Option to add radio buttons as needed. Enter labels for each item in the fields provided. Required — Whether data is required for the field. Yes or No. Disabled — Whether the field is disabled. Yes or No.
Field Options — Click Add Option to add radio buttons as needed. Enter labels for each item in the fields provided.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Checkbox — A field where employees can select more than one option from a set of related options. You can enter as many checkboxes as needed. Additional Parameters: Field Options — Click Add Option to add check boxes as needed. Enter labels for each item in the fields provided. Required — Whether data is required for the field. Yes or No. Disabled — Whether the field is disabled. Yes or No.
Field Options — Click Add Option to add check boxes as needed. Enter labels for each item in the fields provided.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Drop-Down List — A field where employees can select one option from a list of related options. You can add as many items to the listas needed. Additional Parameters: Field Options — Click Add Option to add check boxes as needed. Enter a label for each item in the fields provided. Required — Whether data is required for the field. Yes or No. Disabled — Whether the field is disabled. Yes or No.
Field Options — Click Add Option to add check boxes as needed. Enter a label for each item in the fields provided.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Date — A field where employees can enter a date or select one from the calendar that opens. Additional Parameters: | Field Default Value | The default value to display in the field. | | — | — | | Required | Whether data is required for the field. Yes or No. | | Disabled | Whether the field is disabled. Yes or No. |
Field Default Value — The default value to display in the field.
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Time — A field where employees can enter a time. Additional Parameters: | Required | Whether data is required for the field. Yes or No. | | — | — | | Disabled | Whether the field is disabled. Yes or No. |
Required — Whether data is required for the field. Yes or No.
Disabled — Whether the field is disabled. Yes or No.
Paragraph — A block of text to display in the form (for example, instructions on how to use the form). Enter a separate field for each paragraph you want to include. Paragraph cannot include HTML formatting. If you want to use HTML (for example, to create a bold heading) you must select Markdown. Additional Parameter: | Field Default Value | The default value to display in the field. | | — | — |
Field Default Value — The default value to display in the field.
Markdown — Text that includes markdown or HTML formatting (for example, a bold heading) to display in the form. You can select Paragraph if you do not need to use markdown or HTML formatting. Additional Parameter: | Field Default Value | The default value to display in the field. | | — | — |
Field Default Value — The default value to display in the field.
E-Signature — A field where the employee can submit an electronic signature. Additional Parameter: | Required | Whether data is required for the field. Yes or No. | | — | — |
Required — Whether data is required for the field. Yes or No.
File Hyperlink — A hyperlink to a file in the Document Repository.
Inline Image — An image from the Document Repository (for example, a logo).
Video — A video. Videos must be hosted on an external server. Additional Parameters: Video Source URL — The source URL for the video to display in the form. Video Aspect Ratio — The video aspect ratio to use: 16x9 or 4x3. Aspect ratio is the ratio between the width and the height of a picture.
Video Source URL — The source URL for the video to display in the form.
Video Aspect Ratio — The video aspect ratio to use: 16x9 or 4x3. Aspect ratio is the ratio between the width and the height of a picture.
URL — A field where the Field Label links to a website on the Internet. The Field Label is a universal parameter. Additional Parameters: Video Source URL — The URL for the website to link from the Field Label. Employees can access the website by clicking the link during enrollments.
Video Source URL — The URL for the website to link from the Field Label. Employees can access the website by clicking the link during enrollments.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Enrollment_Posting_Logs.htm
Path:
OBE/Benefits Enrollment/Topics/Enrollment_Posting_Logs.htm
To view posting information for Benefits Enrollment, use the Enrollment Posting Logs form.
This form is intended for high-level Service Provider users only. Contact the PrismHR Customer Support Team before using this feature.
To view posting information:
Click Back Office.
Select System|View > Enrollment Posting Logs.
Enter the required information.
| For this option | Define this information |
|---|---|
| Show Logs | The logs to view (from batch, with job #, for client, with EE ID). |
| Logs | The log to view. |
| Display | The number of rows to display. |
| Delete Log | Whether to delete the log. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Enrollment_Status_by_Workflow_or_Client.htm
Path:
OBE/Benefits Enrollment/Topics/Enrollment_Status_by_Workflow_or_Client.htm
The Enrollment Status by Workflow/Client Report lists the enrollment status for employees participating in an enrollment. (PrismHR Benefits Enrollment only.)
You can run the report for a specific client, employee, or workflow. You can also limit the report to enrollments with a specific starting, ending, or effective date.
If the start, end, or effective dates are missing from a record, one or more of the employees included either has an enrollment assigned that is missing this information or does not have an enrollment assigned. You must fix this by either creating a custom enrollment for employees who do not have an enrollment assigned or by updating their existing enrollments with the correct dates. You can run the Enrollment Status by Workflow/Client report to identify the employees who require this update.
To run the Enrollment Status by Workflow/Client report:
Click Reports.
From Benefits|Report, select Enrollment Status by Workflow/Client. The Enrollment Status by Workflow/Client form opens.
| Use this option | To define this |
|---|---|
| Starting Date | The start date for enrollments to include in the report. |
| Ending Date | The ending date for enrollments to include in the report. |
| Effective Date | The effective date for enrollments to include in the report. |
| Client ID | The client to include in the report. Required. |
| Workflow Type | The workflow type to include in the report. Required. - Enrollment: Tthe workflow is for benefits enrollments (BE), open enrollments (OE), and life event enrollments. - Onboarding: For future development. Does not currently impact the functionality of PrismHR. |
| Column | Description |
|---|---|
| Workflow | The workflow name and ID. |
| Client | The client’s name and ID. |
| Employee ID | The employee’s name and ID. |
| Start Date | The start date for the enrollment. |
| End Date | The end date for the enrollment. |
| Effective Date | The effective date for the enrollment. |
| Status | The employee’s enrollment status (Eligible, Not Started, In Progress, Completed). - If the enrollment is In Progress, information about the step that is in progress displays. - If the enrollment is Completed, the enrollment confirmation ID displays. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_Assign_Workflows.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_Assign_Workflows.htm
Use the System Workflow Grid and Client Workflow Grid forms to assign the workflows to use for enrollments at the system or client levels.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_Config_Client_Settings.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_Config_Client_Settings.htm
The following client-level settings are specific to Benefits Enrollment. You must define them for the benefit plan information to display correctly during enrollments. Client-level settings override settings established at the system level.
The client-level settings for Benefits Enrollment are in the Benefits and Control tabs in Client Details form. Refer to the Benefits Administration User Guide for more information.
To set up group benefits, workers’ compensation, and retirement plan information:
Select the Client menu.
From Client|Change select Client Details. The Client Details form opens.
On the Benefits tab, in the Group Benefits panel, select a Benefit Plan ID.
Use this option — To define this
Section 125 Plan — The Section 125 Plan in which the client participates.
HSA Plan — The HSA Plan in which the client participates.
Maintains Own HDHP — Whether the client maintains a high deductible health plan. This suppresses the system’s validation when setting up an employee HSA.
Eligible Benefits Determinant — Whether to make benefits available to an employee if the client makes different sets of benefits available to their employees based on department, division, location, or benefit group. The system determines the benefits employees are eligible for based on the determinant.
Suppress Automatic Benefit Adjustment — Whether the client wants to suppress automatic benefit adjustment calculations.
Control Group Client — The control group client that acts as a master company for the control group, if any. Use control groups to aggregate data when multiple clients are treated as related entities for Affordable Care Act (ACA) or retirement plan reporting purposes. For example, if an employee works 20 hours at company A and 20 hours at company B, the system treats that employee as having worked 40 hours for the purposes of the ACA, and reports that for both companies A and B.
Auto Create Open Enrollments — Whether to create employee web enrollment forms automatically.
Auto Post Open Enrollments — Whether to post employee web enrollment forms automatically.
Include Employer Cost in Employee Self-Service — Whether to include employer cost in employee self-service. (PrismHR Benefits Enrollment only.)
Employee Calculation Based On — The method (Pay Period, Per Month, or System Default) for calculating employee costs during enrollments. (PrismHR Benefits Enrollment only.)
To set up new hires and employees:
Select Client in the menu bar.
From Client|Change select Client Details. The Client Details form opens.
Click the Control tab.
Access the New Hire/Employee Detail Controls and complete these fields as required:
| Use this option | To define this |
|---|---|
| Employee Numbers Used | A unique number that identifies the employee. |
| Auto Employee Number | Whether to automatically assign an employee number to new hires. |
| Next Employee Number | The next employee number to use. |
| Allow First Period Hours | Whether users of the New Hire form can enter prorated hours for the new employee for the client if their start date is in the middle of a pay period. This is typically used for salaried employees who have auto time sheet hours. This list displays if your organization selected Enable New Hire First Period Hours in System Parameters. - System Default: The New Hire form displays the First Pay Period Hours only if Enable New Hire First Period Hours is selected in System Parameters. - Enabled: The First Pay Period Hours is available in the New Hire form, regardless of the setting in System Parameters. - Disabled: The New Hire form does not display the First Pay Period Hours, regardless of the setting in System Parameters. |
To configure enrollment and onboarding controls:
Select Client in the menu bar.
From Client|Change select Client Details. The Client Details form opens.
Click the Control tab.
Access the Enrollment/Onboarding Controls and complete these fields as required:
| Use this option | To define this |
|---|---|
| Electronic Enrollment | Enable this field to complete enrollment in Benefits Enrollment. |
| Electronic On‑Boarding | Whether new employees use Electronic On‑boarding: - Always: Employees always do their own onboarding online. - Never: Employees never do their own onboarding. Instead, administrators enter employee information in the New Hire form. - Prompt: The New Hire form prompts the user to indicate whether the employee will complete the onboarding process online, or whether an administrator will enter the information in the New Hire form. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_Maintaining_Web_Enrollments.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_Maintaining_Web_Enrollments.htm
You maintain web enrollments using the following forms:
To view an employee’s enrollment activity during enrollments, use the Web Enrollments History form.
To extend the end date in an enrollment for an employee who needs more time to enroll, use the Web Enrollment Configuration form.
To create a custom enrollment period for an employee, use the Web Enrollment Configuration form.
To assign a new workflow to active enrollments, use the Web Enrollments Bulk Update form.
To modify the start and end dates on active enrollment workflows, use the Web Enrollments Date Update form.
To create enrollment batches and post benefit enrollments, use the Post Benefit Enrollments form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_Reports.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_Reports.htm
You can generate reports about benefit enrollments in Benefits Enrollment.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_Setting_BP_Information.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_Setting_BP_Information.htm
To set up information about available benefit plans, use the Benefits Enrollment Plan Details form. For example, you can set up costs for employee contributions, co-payments, deductibles), attach detailed benefit plan summaries and other supporting documents, and set up benefit plan dependencies.
You can enter benefit plan information fields manually in the Comparison Fields tab in the Benefits Enrollment Plan Details form. You can also use the Plan Offer Type Import form to import multiple benefit plan information fields.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_Setting_Forms_Workflows.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_Setting_Forms_Workflows.htm
A workflow is essentially a wizard—a script that presents employees with a series of forms to guide them through well-defined and highly customizable steps during onboarding and benefit enrollments.
In the Form Library, you can create custom versions of the forms or use the prebuilt versions provided with their default language and settings. Prebuilt forms are shown in bold.
If you plan to include any media items (such as documents or images) in forms or workflows, upload them to the Document Repository before you create the forms in the Form Library.
After you create the forms, you can use them as components to create workflows in the Workflow Library.
[Image: screenshot]
A typical enrollment workflow might begin with an optional Welcome form and then present forms for medical, dental, and vision plans; long-term and short-term disability plans; and so on. You can organize forms into categories for easier navigation.
The final forms in a workflow include the following required forms:
A Benefits Summary form that summarizes the employee’s benefit selections and provides the opportunity to make changes.
A Confirmation form where the employee submits benefit selections and completes the enrollment process.
A Welcome form is recommended for workflows, but optional. The Benefit Summary and Confirmation forms are required for enrollments to process correctly.
Before you begin:
Use the following libraries to manage documents, forms, and workflows for enrollments.
Library — Description
Document Repository — Upload and maintain documents to use when creating forms (graphic files for logos, PDF files containing benefit information, and so on).
Form Library (Enrollments) — Build the forms, typically using documents from the Document Repository. PrismHR provides prebuilt forms that you can use as templates to create new forms, as well as templates for the Welcome and Confirmation forms. You can also build your own custom forms.
Workflow Library (Enrollments) — Create workflows using forms from the Forms Library as components.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_Setting_Up_Notifications.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_Setting_Up_Notifications.htm
To set up notifications to send during enrollments, use the Notification Templates and Notification Recipients forms.
Before you begin:
To access the Notification Templates form:
Click Back Office.
From System|Change, select Notification Templates. The Notification Templates form opens.
To access the Notification Recipients form:
Click Back Office.
From System|Change, select Notification Recipients. The Notification Recipients form opens.
To access the Notification Control Panel:
Click Back Office.
From Operations|Action, select Notification Control Panel. The Notification Control Panel opens.
You must set up an enrollment user in PrismHR with the User ID called Enrollment. .
The Enrollment user serves as the administrator and sender for all notifications. The email address set up on the user account displays in From for all notifications sent to employees and new hires. If this user account is not set up, the notifications engine does not send notifications.
The User ID must be as follows, spelled correctly, and with no punctuation: Enrollment
To test the Enrollment user:
In the Notification Templates form, set up a test notification template recipient.
In the Notification Recipients form, set up a test recipient.
In the Notification Control Panel, turn on the notification engine using a test client.
Send a test message from the Enrollment user to confirm that it is set up correctly.
If the Enrollment user is set up correctly, the test recipient receives the notification.
After you set up the Enrollment user, you can set up content for notifications in the Notification Templates form.
You can designate recipients for notifications in the Notification Recipients form.
The notifications that you create are available in the Workflow Library where you can add them to workflows.
To specify how often the system should send the notifications and to start the notifications engine, use the Notification Control Panel.
You can run the Notification Audit Report to review notifications sent to all recipient types (for example, employees, generic recipients, message groups).
Messages are also stored in the Messages center in PrismHR. You can also set up your SMTP server to retain a copy of every email sent.
There are two possible circumstances that can result in notifications not reaching their recipient.
The email address is not entered correctly. For example, it is entered as @example.com instead of jsmith@example.com. PrismHR logs this error but it is not accessible to the user. Users should contact the PrismHR Customer Support Team.
The email address is entered correctly, but is otherwise not deliverable (for example, the email address is no longer active). In this case, PrismHR simply sends the email. There is no error log, and in most cases there is no way to know that it was not received. Many email servers are configured not to send notifications of undeliverable emails.
To track notifications, set up the Notification Recipients form to send copies of all notifications to an administrator in your organization. This also enables you to forward notifications as needed.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Chapter_SystemLevelSetup.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Chapter_SystemLevelSetup.htm
The following sections describe system-level settings that are specific to setting up benefits and open enrollments. You must define these settings for benefit plan information to display correctly during enrollments.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Front_Matter/BE_UG_Setting-Up-Anytime-Enrollments.htm
Path:
OBE/Benefits Enrollment/Topics/Front_Matter/BE_UG_Setting-Up-Anytime-Enrollments.htm
Anytime Enrollment enables employees to enroll in Anytime Benefits at any point during a plan year. A date or event does not trigger the Anytime Enrollment process — you can enroll in Anytime Benefits at any time. One example of an Anytime Benefit plan is pet insurance. If you acquire a pet and want to enroll in a pet insurance benefit plan, you can do so at any time outside of annual enrollment restrictions. To set up Anytime Enrollment, you must:
Configure a benefit plan to include in an Anytime Enrollment workflow
Set up a notification template
Set up notification recipients
Create an Anytime Enrollment workflow
Add the workflow to the system or client workflow grids
To begin, you must configure an Anytime Benefit plan to include in an Anytime Enrollment workflow.
To include a benefit plan in an Anytime Enrollment workflow, use the Group Benefit Plans form.
To include a benefit plan in an Anytime Enrollment workflow:
Click Back Office.
From System|Change, select Group Benefit Plans. The Group Benefit Plans form opens.
Configure a benefit plan for Anytime Enrollment or use the Benefit Plan ID link to select a plan from the list.
In the Web Enrollment Parameters panel, enable Include in Anytime Enrollment Workflow.
Click Save.
After configuring a benefit plan to include in an Anytime Enrollment workflow, you must set up a notification template.
To set up a notification template for an Anytime Enrollment workflow, use the Notification Templates form.
To set up a notification template for an Anytime Enrollment workflow:
Click Back Office.
From System|Change, select Notification Templates. The Notification Templates form opens.
Configure a notification template for Anytime Enrollment or use the Template Id link to select a template from the list.
In the Workflow Type panel, enable Anytime Enrollment. You can combine with other workflow types except for Onboarding.
Click Save.
After configuring a notification template for an Anytime Enrollment workflow, you must set up notification recipients.
To set up notification recipients for an Anytime Enrollment workflow, use the Notification Recipients form.
To set up notification recipients for an Anytime Enrollment workflow:
Click Back Office.
From System|Change, select Notification Recipients. The Notification Recipients form opens.
To configure notification recipients for Anytime Enrollment, click Setup a new Notification. Or, to select a recipient group from the list, use the Notification Id link.
In the Notification Template panel, to assign the recipient group to a template configured for Anytime Enrollment, click Template Id. For more information, see Setting Up an Anytime Enrollment Notification Template.
If you select a notification template configured for Anytime Enrollment, the Workflow Type and Message Delivery Method panels are disabled.
After configuring notification recipients for an Anytime Enrollment workflow, you must create the workflow.
To create an Anytime Enrollment workflow, use the Workflow Library form.
To create an Anytime Enrollment workflow:
Click Back Office.
From System|Change, select Workflow Library. The Workflow Library form opens.
In the Type list, select Enrollment.
To edit an existing workflow for Anytime Enrollment, select a workflow from the list. To create a new workflow, click Create New Workflow.
On the Process tab, enable Anytime Enrollment.
On the Forms tab, select forms to include in the workflow.
On the Notifications tab, enable the notification template configured on the Notification Template form. For more information, see Setting Up an Anytime Enrollment Notification Template.
Click Save.
After creating the workflow, you must add it to the system or client workflow grids.
To add an Anytime Enrollment workflow to the system workflow grid, use the System Workflow Grid form.
To add an Anytime Enrollment workflow to the system workflow grid:
Click Back Office.
From System|Change, select System Workflow Grid. The System Workflow Grid form opens.
In the Anytime Enrollment column, select a workflow from the list to add it to the workflow grid.
You can also click Add Row to add another row to the workflow grid. In the Add a New Record section, you can select an Anytime Enrollment workflow from the AE Workflow list.
After submitting your changes, the workflow is now available at the system level. You can also assign the workflow at the client level using the Client Workflow Grid form. Client‑level settings override system‑level settings.
To add an Anytime Enrollment workflow to the client workflow grid, use the Client Workflow Grid form.
To add an Anytime Enrollment workflow to the client workflow grid:
Click Back Office.
From System|Change, select Client Workflow Grid. The Client Workflow Grid form opens.
In the Anytime Enrollment column, select a workflow from the list to add it to the workflow grid.
You can also click Add Row to add another row to the workflow grid. In the Add a New Record section, you can select an Anytime Enrollment workflow from the AE Workflow list.
All OFF: Disable notifications for all enrollment types. Applies only if you combine multiple workflow types on the notification template.
AE Only: Enable notifications only for Anytime Enrollment
All ON: Enable notifications for all enrollment types. Applies only if you combine multiple workflow types on the notification template.
After submitting your changes, the workflow is now available at the client level.
In Employee Portal (EP), you can add a widget displaying available Anytime Benefits enabling employees to enroll directly from EP. A link from EP opens directly to an Anytime Enrollment workflow (through SSO) where they can enroll in any of the available benefit plans. For more information on creating the widget, see Adding Anytime Benefits to Employee Portal (EP) on the Customer Resource Center.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global%20Dependent%20Information%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global Dependent Information Report.htm
Use the Global Dependent Information Report form to generate a report for one or more clients to produce a detailed output of all employees who have a listed dependent.
Note: Note: Client Access Group Security is enabled on this form.
To access this form, clickReports menu. Under Benefits|Report, click Global Dependent Information Report.
To generate the Global Dependent Information Report:
Field Name — Description
Client ID — This field is not mandatory. Leave this field blank to select allclients. If you want to run this report for specific clients, enter the Client IDs here or click the Client ID link and select them from the Select Clients list. The corresponding Client Name displays.
Click Run to generate the report on-screen.
Click Clear to clear this form at any time.
Click Close to close this form at any time.
The Global Dependent Information Report is sorted by Client ID and displays the following columns:
Client ID
Client Name
Employee Last Name
Employee First Name
Dependent Last Name
Dependent First Name
Relation
Soc-Sec-Num
For example:
[Image: screenshot]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global%20Employee%20Benefit%20Detail%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global Employee Benefit Detail Report.htm
Use the Global Employee Benefit Detail Report form to generate a report that provides benefit enrollment detail for multiple clients including the effective date, plan information, and coverage information. Information can be reported based on the payroll processor assigned to a group of clients.
Note: Note: Client Access Group Security is enabled on this form.
To access this form, clickReports menu. Under Benefits|Report, click Global Employee Benefit Detail Report.
To generate the Global Employee Benefit Detail Report:
Field Name — Description
Client ID — This field is not mandatory. Leave this field blank to select allclients. If you want to run this report for specific clients, enter the Client IDs here or click the Client ID link and select them from the Select Clients list. The corresponding Client Name displays.
Click Run to generate the report on-screen.
Click Clear to clear this form at any time.
Click Close to close this form at any time.
The Global Employee Benefit Detail Report is sorted by Payroll Rep, provides a Record Count on the last page, and displays the following columns:
Payroll Rep.
Client ID
Client Name
Employee Name
Plan Name
Effective Date
Coverage Start Date
Coverage Amount
Toral Premium
Employee Contrib.
Client Contrib.
For example:
[Image: screenshot]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global%20Employee%20Deduction%20Setup%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global Employee Deduction Setup Report.htm
Use the Global Employee Deduction Setup Report form to generate a global report on employee deductions set up for all employees. This report provides a global list of deductions set up by employee. The report can be customized by Client, Deduction Code, and employee Status Class.
Note: Note: Client Access Group Security is enabled on this form.
To access this form, clickReports menu. Under Operations|Report, click Global Employee Deduction Setup Report.
To generate the Global Employee Deduction Setup Report:
| Field Name | Description |
|---|---|
| Client ID | This field is optional. Leave this field blank to include all clients for your report. If you want to run this report for a specific clients, enter the Client IDs here or click the Client ID link and select them from the Select Clients dialog box. |
| Deduction Code | This field is optional. Leave this field blank to include all deduction codes in PrismHR for your report. If you want to run this report for a specific deduction codes, enter them here or click the Deduction Code link and select them from the Select Deduction Codes dialog box. |
| Status Class | This field is optional. Select from the following options: - All - This is the default form option. Select this option to include all employee statuses in PrismHR in your report. - Active - Select this option to include only active employees in PrismHR in your report. - Terminated - Select this option to include only terminated employees in PrismHR in your report. - Leave of Absence - Select this option to include only employees who are leave of absence in PrismHR in your report. |
Click Run to generate the report on screen.
Click Clear to clear this form at any time.
Click Close to close this form at any time.
The Global Employee Deduction Setup Report displays the following columns:
| Columns |
|---|
| - Employee ID - Employee Name - Deduction Code - Type - Method - Description - Amount - Periods |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global%20Employee%20Garnishment%20by%20Date%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global Employee Garnishment by Date Report.htm
Use the Global Employee Garnishment by Date Report form to generate a report for one or more employers and a specified pay date range of all garnishments during the period including the pay date, garnishment type, docket information, and amount.
Note: Note: Client Access Group Security is enabled on this form.
To access this form, clickReports menu. Under Operations|Report, click Global Employee Garnishment by Date Report.
To generate the Global Employee Garnishment by Date Report:
Field Name — Description
Starting Pay Date — Enter the starting pay date of the reporting period.
Ending Pay Date — Enter the ending pay date of the reporting period.
Employer ID — This field is not mandatory. Leave this field blank to select all employers. If you want to run this report for specific employers, enter the Employer IDs here or click the Employer ID link and select them from the Select Employer list. The corresponding Employer Name displays.
Click Run to generate the report on-screen.
Click Clear to clear this form at any time.
Click Close to close this form at any time.
The Global Employee Garnishment by Date Report is sorted by Employer ID and displays the following columns:
Employer ID
Employee Name
Soc-Sec-Num
Pay Date
Voucher
Check No.
Type
Issue Authority
Docket ID
Amount Garnished
For example:
[Image: screenshot]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global%20Employee%20Garnishment%20Setup%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global Employee Garnishment Setup Report.htm
Use the Global Employee Garnishment Setup Report form to generate a global report of employee garnishments with amount paid to date. This report will show the garnishments that are set up across clients based on selected employee status in PrismHR.
Note: Note: Client Access Group Security is enabled on this form.
To access this form, clickReports menu. Under Operations|Report, click Global Employee Garnishment Setup Report.
To generate the Global Employee Garnishment Setup Report:
Field Name — Description
Employee Status — This field is optional. Leave this field blank to report for all employee statuses.
Include Inactive Garnishments — This field is optional. By default this box is unchecked, and will report garnishments that are active in PrismHR on the day this report is run. Check this box if you also want to include inactive garnishments in your report.
Click Run to generate the report on screen.
Click Clear to clear this form at any time.
Click Close to close this form at any time.
The Global Employee Garnishment Setup Report displays the following columns:
| Columns |
|---|
| - Client ID - Client Name - Employee ID - Employee Name - Issuing Authority - Soc-Sec-Num - Receipt Date - Docket No. - Payee ID - Payee Name - Total Amount - Flat Amount - Base Code - Pct - Amount Paid |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global%20Payroll%20Deduction%20by%20Date%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global Payroll Deduction by Date Report.htm
Use the Global Payroll Deduction by Date Report form to generate a report on employee deductions for all or selected clients by a pay date range.
Note: Note: Client Access Group Security is enabled on this form.
To access this form, clickReports menu. Under Operations|Report, click Global Payroll Deduction by Date Report.
To generate the Global Payroll Deduction by Date Report:
| Field Name | Description |
|---|---|
| Pay Date From | Enter the first date of the pay date range for your report. |
| Pay Date To | Enter the first date of the pay date range for your report. |
| Include Cost Center | This field is optional. By default this field is unchecked. Check this field is you want to your report to show cost centers. |
| Cost Center | This field is optional. Leave this field blank to include all cost centers for your report. If you want to run this report for a specific cost center, enter it here or click the Cost Center link and select it from the Select Cost Center dialog box. |
| Employer ID | This field is optional. Leave this field blank to include all employers for your report. If you want to run this report for a specific employer, enter the Employer ID here or click the Employer ID link and select it from the Select Employer dialog box. |
| Client ID | This field is optional. Leave this field blank to include all clients for your report. If you want to run this report for a specific client, enter the Client ID here or click the Client ID link and select it from the Select Client dialog box. |
| Deduction Code | This field is optional. Leave this field blank to include all deduction codes for your report. If you want to run this report for a specific deduction codes, enter them here or click the Deduction Code link and select them from the Select Deduction Codes dialog box. |
| Report Type | Select the report type that you want to generate from the following options: - Summary - This is the default option. This report provides an employee wise total amount for all deduction codes for an employee. - Detail - This report provides a further breakdown of the deduction amount of each employee by individual deduction codes. |
Click Run to generate the report on screen.
Click Clear to clear this form at any time.
Click Close to close this form at any time.
The Global Payroll Deduction by Date Report displays the following columns:
| Report Name | Columns |
|---|---|
| Summary Report | - Cost Center - Employee Name - Pay Date - Check Number - Deduct Amount - Status - Client ID - Client Name - Deduction Code This report also provides you with: - a total deduction amount for each employee, - a total deduction amount for each cost center and - a Report Totals on the last page. |
[Image: Global Payroll Deduction by Date Report - Summary Report]
Example of Detail Report:
[Image: Global Payroll Deductions by Date Report - Detail Report]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global%20Voucher%20Liability%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global Voucher Liability Report.htm
Use the Global Voucher Liability Report form to generate a report to produce a detailed or summary output of payroll voucher gross pay, net pay, taxes, and deductions for a subset of clients by date range. You can also run a grand totals report that will total the list of clients and vouchers.
Note: Note: Client Access Group Security is enabled on this form.
To access this form, clickReports menu. Under Operations|Report, click Global Voucher Liability Report.
To generate the Global Voucher Liability Report:
| Field Name | Description |
|---|---|
| Starting Pay Date | Enter the starting pay date of the reporting period. |
| Ending Pay Date | Enter the ending pay date of the reporting period. |
| Client ID | This field is not mandatory. Leave this field blank to select allclients. If you want to run this report for specific clients, enter the Client IDs here or click the Client ID link and select them from the Select Clients list. The corresponding Client Name displays. |
| Report Type | Select the type of report that you want to generate from the following options: - Summary (Default) - Detail - Grand Total |
Click Run to generate the report on-screen.
Click Clear to clear this form at any time.
Click Close to close this form at any time.
The Global Voucher Liability Report for clients displays the following columns:
| Report Name | Columns |
|---|---|
| Summary Report | - Client ID - Client Name - Gross Pay - Net Pay - Employee Taxes - Deductions - Employer Taxes - Report Totals |
[Image: screenshot]
Example of Detail Report:
[Image: screenshot]
Example of Grand Total Report:
[Image: screenshot]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Global_FSA_HSA_Deduction_Report.htm
Path:
OBE/Benefits Enrollment/Topics/Global_FSA_HSA_Deduction_Report.htm
Use this form to generate a report that displays the liability for FSA and HSA deductions and contributions.
Note: Note:
Only service providers can access the form.
Uses Client Access Group security.
To access the form, click Reports. Under Benefits|Report, click Global FSA/HSA Deduction Report.
To generate the Global FSA/HSA Deduction Report:
Field Name — Description
Starting Pay Date — Enter or select the Starting Pay Date (required) for the pay date range for which you want to run this report.
Ending Pay Date — Enter or select the Ending Pay Date (required) for the pay date range for which you want to run this report.
Employer ID — This field is optional. Leave this field blank for this report to run for all employers. If you want to restrict this report to run for selected employers, enter the employer IDs here or click the Employer ID link and select them from the Select Employer list.
Client ID — This field is optional. Leave this field blank for this report to run for all clients. If you want to restrict this report to run for selected clients, enter the client IDs here or click the Client ID link and select them from the Select Clients list.
Section 125 Plan ID — This field is optional. Enter or select the Section 125 Plan ID for the benefit plan that falls under Section 125.
HSA Plan ID — This field is optional. Enter or select the HSA Plan ID for the health savings account (HSA).
Click Run to generate the report. The report displays on-screen.
Click Clear to clear the form at any time.
Click Close to close the form at any time.
This report displays the following columns:
Employer ID
Client ID
Client Name
Employee ID
Employee SSN
Employee Name
Plan Type
Deduction
Match
PEO Match
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/LEM_Creating_a_New_Life_Event.htm
Path:
OBE/Benefits Enrollment/Topics/LEM_Creating_a_New_Life_Event.htm
You can create a new life event workflow code, modify a predefined code, or modify a code that you created.
After you save the life event workflow code, the Code is read-only and you cannot modify it. If you are editing a predefined life event code, you cannot change the value in the Code field.
To create a life event workflow code:
Click Back Office.
From System|Change, select Life Event Maintenance. The Life Event Maintenance form opens.
Select the Codes tab and click Add Life Event. The Add Life Event form opens.
| For this option | Define this information |
|---|---|
| Life Event Name | The name of the life event workflow code. Required |
| Code | The code for the life event workflow. Required |
To modify a life event workflow code:
To remove a life event workflow code:
To specify general settings for the workflow, use the General tab in the Add Life Event form. For example, you can specify the required documents, effective date, and the window length for the enrollment.
| For this option | Define this information |
|---|---|
| Doc Required | Whether supporting documents are required for the life event. For example, if the life event code is for the birth or adoption of a child, the employee might need to upload a birth certificate or adoption papers during the life event enrollment. If you select Yes, the Specify Document(s) list displays. Document options that display in the list are set up in the Enrollment Options form. Select the document to use and click [Image: screenshot] . The document name displays below the list. You can specify as many documents as necessary. You can click [Image: screenshot] to delete a selection. |
| Window Length | The number of days from the Effective Date during which an employee can complete the life event enrollment. |
| Days to Notify | The number of days from the date of the life event itself that the employee must notify the employer of the life event to be eligible for the life event enrollment. |
| Initiated By | Who can initiate or assign the life event (Sponsor/Client, Employee, Either). If you select Sponsor/Client, an administrator assigns the life event in the Life Event form only. If you select Employee or Either, you must also set up the components the employee can access in EP in the Employee Portal Components tab. - If you select Employee, the employee assigns the life event in EP only. - If you select Either, an administrator can assign the life event in the Life Event form or the employee can assign it in EP. |
To select and view the offer types included in the life events workflow, use the OFFER TYPE RULES tab. You can also view what the employee can do during the enrollment in the Actions Allowed panel. The actions vary depending on the offer type.
To view offer rules:
In the Add Life Event form, select the Offer Rules tab.
Under Codes Assigned, select an assigned code.
Select the OFFER TYPE RULES tab.
Select an Offer Type. The offer type displays below the list, and the offer type’s settings display in the Actions Allowed panel. These settings show the enrollment options that are allowed for the employee for the offer type in the life event enrollment.
To select the Welcome, Summary, and Confirmation forms to use in the life event workflow, use the Process tab in the Add Life Event form.
The forms you select in the Welcome, Summary, and Confirmation lists override the forms that are set up in the benefit enrollment workflow that is being used as the basis for the life event workflow. For example, if you do not select a Welcome form, no welcome form displays in the life event workflow, even if one is set up in the original benefit enrollment workflow.
To select the forms to use in the workflow:
In the Add Life Event form, select the Process tab.
Select the Welcome form to use. This form is optional.
Select the benefit Summary form to use. This form works in conjunction with the Confirmation form and is required.
Select the Confirmation form to use. This form is required.
If needed, select Approve every employee enrollment for this Life Event. To use this option, you must set up a global approvals policy. .
To select the notifications to use for the life event workflow, use the Notifications tab in the Add Life Event form.
The notifications you select override the notifications that are set up in the benefit enrollment workflow that is being used as the basis for the life event workflow. If you do not enable a notification for the life event workflow in this tab, it is not sent, even if it is set up in the original benefit plan workflow.
You must set up notifications before they can be assigned to a life event workflow. The notification’s template must have the Workflow Type Life Event selected, and must be set up with recipients to display in the table and be available for life events.
To select notifications:
In the Add Life Event form, select the Notifications tab.
In the Enabled column, select each notification to use for the life event workflow. You can select as many as needed.
Option — Description
Notification Template — The name of the notification template.
Type — The Trigger Type specified in the notification template.
Condition — The Trigger Condition specified in the notification template.
Days — If the Type is Time-based, the number of days applied to the Trigger Condition in the notification template displays. Otherwise, the table displays N/A.
Recipients — The Notification ID for the notification recipient record attached to the notification.
To apply notifications to clients, use the Client List tab in the Add Life Event form.
To make notifications available to clients:
For this option — Define this information
Apply to All Clients — Whether the life event available in the Life Event form is available to all clients at the system level.
Apply to Selected Client(s) — Whether the life event is available to a specific client or a selected list of clients. If selected, the client selection settings display. Select a client from the Available Clients panel and use the arrows to move it to the Selected Client(s) panel. You can add as many clients as needed. Selected clients can access the life event in the Life Event form. You can use the Search box to search for a specific client.
Override Existing Code — Whether the life event code is meant to replace an existing code. For example, you might create an alternate Birth life event code with different settings that are intended for a specific client. In such a case, select Override Existing Code and select the existing Birth code to override for the client selected from the list.
If you want the employee to be able to initiate the life event in EP, select the components the employee can access in the Employee Portal Components tab in the Add Life Event form.
Note: Note: The Initiated By option in the General tab must be set to either Employee or Either for the life event available in EP.
You can add as many components as needed and use Search to find a specific component in the list. The available components are:
Address
Contact Info
Direct Deposit
Emergency Contacts
Personal Info
Tax Withholding
To enable employees to initiate a life event in the employee portal:
After you create and save a life event workflow code it displays in the table, where you can click Edit to modify it.
The Audit tab displays in the Edit Life Event form if you edit the workflow code. This tab displays any changes that were made.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/LEM_Viewing_Life_Events.htm
Path:
OBE/Benefits Enrollment/Topics/LEM_Viewing_Life_Events.htm
The Life Event Maintenance form is divided into two tabs, Codes and Clients. Existing life event work codes display in the main table in the Codes tab, and client information displays in the main table in the Clients tab.
You can:
Sort your view of the tables in the Codes and Clients tabs by clicking the column headers and selecting Sort Ascending, Sort Descending, or Hide Column.
Use the Search box to search for a specific record as needed.
Use the View list to select the number of records to view in either table (25, 50, 100).
Use the navigation arrows to scroll through records.
If you edit settings, the settings change for all clients, not just the client you are viewing. If you want to change settings for just one client, create an alternate life event workflow code.
To access the Life Event Maintenance form:
Click Back Office.
From System|Change, select Life Event Maintenance. The Life Event Maintenance form opens. The Codes tab is displayed by default.
The Codes tab displays information about the event workflow codes. The main table list all codes you created, as well as the pre-defined life event codes provided in Benefits Enrollment.
The system provides the following predefined codes. You can modify them as needed.
Predefined codes have default settings, but you need to reconfigure them base on the settings your organization requires. Review and modify the settings as needed before you use them for life events.
| Code | Life Event |
|---|---|
| MRG | Marriage |
| DP | Domestic partnership |
| BTH | Birth or adoption |
| ADPT | Placement for adoption |
| DIV | Dissolution of marriage |
| SDTH | Death of spouse |
| DDTH | Dependent’s Death |
| DLE | Dependent Ceases to Satisfy Eligibility |
| DDIS | Dependent becomes disabled |
| SGC | Spouse becomes employed |
| LCOV | Loss of existing coverage |
| PF | Part Time to Full-Time |
| LFT | Loss of full-time status (20-29 hours per week) |
| BLOA | Begin unpaid leave (30+ days) |
| RLOA | Return from unpaid leave (30+ days) |
| COR | Change of Residence |
To customize the pre-defined codes:
Click Back Office.
From System|Change, select Life Event Maintenance. The Life Event Maintenance form opens.
Select the Codes tab.
For this option — Define this information
Life Event — The name of the life event workflow code.
Code — The code for the life event workflow.
Override Code — In some instances, you might create a version of a life event workflow code to override another existing code for a specific client or group of clients. The overridden code displays in this column.
Client List — The clients who are assigned the life event code.
Offer Type — The offer types included in the life event workflow code. You can click Show All to display the offer type icons, or click Show Less to display only the number of offer types.
Action — Click Remove to delete the life event workflow code. Click Edit to modify the life event workflow code’s settings.
The Clients tab displays information about clients and lists the codes assigned to them. You can also view details on individual clients as needed.
To view clients and the codes assigned to them:
Click Back Office.
From System|Change, select Life Event Maintenance. The Life Event Maintenance form opens.
Select the Clients tab. The following information is shown about each client.
| Column | Description |
|---|---|
| Client ID | The client’s ID. |
| Client Name | The name of the client. |
| Codes Assigned | The life event workflow codes assigned to the client. You can click Show All to display the code icons, or click Show Less to display only the number of codes. |
| Action | You can click View Details for a detailed view of the codes assigned to the client. The View Details form displays. - You can select any code and view its settings as needed. The code settings display in read-only format. - All code information is read-only with the exception of the Omit Code option. You can select this option to remove a life event workflow code for the client. - If you need to edit settings for the code, you can click Go To [Code] Life Event Details. The Edit Life Event form opens, where you can edit settings. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Life%20Insurance%20Reconciliation%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Life Insurance Reconciliation Report.htm
Use this form to generate a report to reconcile life insurance policy information for age banded life insurance plans.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, under Work Centers, under Onboarding & Benefits, click Benefit Imports & Reporting. Under Benefit Reporting, click Life Insurance Reconciliation Report.
To generate the Life Insurance Reconciliation Report:
Field Name — Description
Coverage Effective As of — Enter the date for which to report effective coverages. For OPEN ENROLLMENT verification use one day after the effective date OR
Coverage Starts Between — Start Date - Enter the beginning date of the report period. End Date - Enter the ending date of the report period.
| Field Name | Description |
|---|---|
| Report Type | Select the report type that you want to generate from the following options: - Detail - this is the default option. - Summary |
| Field Name | Description |
|---|---|
| Age as of Date | Enter the date to be used to calculate participant ages. |
| Status Class | This field is optional. Select the employee employment status class for whom you want to run this report. Leave this field blank to run for all employee employment status classes or select one from the following options: - Active - On Leave - Terminated |
Click Run to generate the report. The report shows up on screen. Click XLS to download the report.
Click Clear to clear the form at any time.
The detail report shows the following columns:
Client ID
Department
Plan ID
Cost Center
Band
Smoker Status
Employee ID
Employee Name
Coverage
Rate
Employee Premium Amount
The summary report shows the following columns:
Client ID
Plan ID
Cost Center
Band - Age Band for example age 54 to 54 as on the As of Date.
Smoker Status
Number of Employees - Number of employees in that age band for that Client ID.
Coverage
Rate
Employee Premium Amount
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Life_Event.htm
Path: OBE/Benefits Enrollment/Topics/Life_Event.htm
Use the Life Event form to assign life event workflows to employees. When you assign the workflow, the system creates a web enrollment record for the employee, and the employee can complete the enrollment in EP. You create life events in Life Event Maintenance.
To assign life event workflows to employees:
Click the HR menu.
From HR|Action, select Life Event. The Life Event form opens.
Complete these fields as required:
Field — Description
Employee — Click Employee to open an Employee selector. Select from the displayed list, or type in a search term to refine the search results.
Life Events — Select a life event to apply to the employee. Life events include items such as Marriage or Change in Spouse Employment.
Life Event Date — Select a date when the life event occurred from the calendar picker.
Date Notified — Select a notification date for the life event from the calendar picker.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Life_Event_Maintenance.htm
Path:
OBE/Benefits Enrollment/Topics/Life_Event_Maintenance.htm
To set up workflow codes for employee life events such as marriage, divorce, and birth, use the Life Event Maintenance form. Benefits Enrollment provides predefined life event codes that your organization can configure as needed, but you can also create your own as needed.
After you set up the life event workflow, administrators can assign the life events to employees in the Life Event form.
After you save the life event assignment, the system generates an enrollment workflow and the employee can complete the life event workflow in EP.
You must set up the following settings before creating a new life event record:
Set up all benefit plans to include in the life event workflow. Assign them the correct Offer Type to include in the offer type forms assigned to the workflow.
In the Client Workflow Grid, assign a benefit enrollment workflow that corresponds to the effective date to use for the life event workflow. The life event workflow is based on this pre-existing benefit enrollment workflow, and the life event code settings serve as overrides.
Set up Benefit Summary and Confirmation forms to use in the life event workflow in the Forms Library. You can also set up an optional Welcome form. You can customize these forms as needed for the life event.
Set up the notifications to send for each life event. The notification templates must have the Workflow Type Life Event selected, and must be set up with recipients for the notifications to be available.
If you want the system to automatically approve every employee enrollment for the life event, set up a global approvals policy. See the System Adminstration Guide or Approvals Guide.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Logging%20in%20as%20an%20Employee.htm
Path:
OBE/Benefits Enrollment/Topics/Logging in as an Employee.htm
Service providers, worksite managers, and worksite trusted advisors who are set up with the appropriate user role can use the Proxy Login form to access Benefits Enrollment and Onboarding on behalf of an employee.
Access to an employee’s Benefits Enrollment requires the Enrollment Proxy user role, and access to an employee’s Onboarding requires the Onboarding Proxy user role.
Note: Note: User roles are assigned using the User Roles form. By acting as a proxy for the employee, users acknowledge that they have received authorization to view the employee’s data and, for Benefits Enrollment, to make elections on the employee’s behalf.
To log in as an employee:
Note: You can also proxy login as a worksite manager/worksite trusted advisor by selecting Worksite Manager Proxy on the Actions menu
[Image: screenshot]
. When the Proxy Login form displays, the system automatically displays the Worksite Manager/Trusted Advisor option in the Activity field and the selected employee’s username displays in the User ID field.
Field — Description
Activity — Select whether to access Benefits Enrollment or Onboarding as an employee (Benefits Enrollment) or a user (Worksite Manager/Trusted Advisor).
Employee ID/User ID — Enter the ID number of the employee or user as whom to log in. Alternatively, click the link to select an employee or user from a list. > Note: Note: The Employee ID field automatically changes to the User ID field if you select the Worksite Manager/Trusted Advisor option in the Activity field.
Date — Enter the date the proxy login is being performed. This must be the current date or a previous date.
Proxy approval received by — Select the method used to obtain the employee’s approval for the proxy login.
Proxy Reason — Enter the reason for the proxy login.
Note: Note: When Onboarding is accessed using the Proxy Login form, changes to the forms included in the workflow can be made, but changes cannot be saved and forms cannot be submitted.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Managing%20the%20Workflow%20Library%20(BE).htm
Path:
OBE/Benefits Enrollment/Topics/Managing the Workflow Library (BE).htm
Use the Workflow Library to create workflows for enrollments. A typical enrollment workflow might begin with an optional Welcome form, then present forms for medical, dental, vision plans, long-term and short-term disability plans, and so on. You can organize forms into categories for easier navigation.
The final forms in a workflow include a Benefits Summary form (which summarizes the employee’s benefit selections and allows the opportunity to make changes), and a Confirmation form (where the employee submits benefit selections and completes the enrollment process). These are required.
Before you begin:
To view workflows used for Benefits Enrollment:
Click Back Office.
From System|Change,select Workflow Library. The Workflow Library opens.
In Workflow Type, select Enrollment. You can sort the table view by clicking the column headings.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Managing_Forms_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Managing_Forms_BE.htm
To create and maintain forms, use the Form Library.
These forms include Benefit Summary forms and Confirmation forms, which are required for enrollments to process correctly, as well as optional Welcome forms. PrismHR provides prebuilt forms that can be used with minimal customization and the ability to create custom forms for additional enrollment options.
To open the Form Library:
Click Back Office.
From System|Change, select Form Library. The Form Library displays.
| Field | Description |
|---|---|
| Name | The name of the form. |
| ID | The ID assigned to the form when the form was created on the Create New Custom Form form. |
| Version | The version number of the form. |
| Form Type | - Default: This indicates that the form is a prebuilt form. - Custom: This indicates that the form was created manually. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Managing_Versions_Revisions.htm
Path:
OBE/Benefits Enrollment/Topics/Managing_Versions_Revisions.htm
The Form Library and Workflow Library both maintain multiple versions and revisions for forms and workflows. Revisions are set automatically when you submit a new form or workflow or modify an existing one.
When you create a new form or workflow, the Version automatically sets to 1.0.
If you change a form or workflow and select the option to have the changes go into effect immediately, the system adds a revision number after the decimal point in the version number (1.1, 1.2, and so on).
The system also immediately sets the Status to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any previous active version to Inactive and sets the current date as its end date.
The system sets the new version’s status to Active on the start date, which you assign when you submit the form or workflow. Since there can only be one active version, the system changes the status of any previous active version to Inactive and sets the current date as its end date.
You can view and compare different versions and revisions in both libraries by clicking the form ID or workflow ID in the table. The Versions form opens, displaying all existing versions and revisions.
To modify a form or workflow version or revision, click the ID.
To compare two versions or revisions of a form or workflow, select the two you want to compare and click Compare. The Comparison panel opens below the main table in the form (you must scroll down to view data) and displays settings for both.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/New_Hire_Suspension_Process.htm
Path:
OBE/Benefits Enrollment/Topics/New_Hire_Suspension_Process.htm
The new hire suspension process lets organizations suspend benefit enrollments for new hires if the benefits setup is not yet finalized for the client. The purpose is to ensure that new hires are not offered benefits based on obsolete settings. (PrismHR Benefits Enrollment only.)
The new hire suspension process works as follows:
On the System Parameters form, the organization enters the SUSPENDENH custom feature code. This code activates the new hire suspension process at the system level.
On the Client Details form Benefits tab, administrators setting up benefits for a client define the Benefits Rules Good Through Date to indicate the date up to which the current enrollment offerings for new hires is valid.
When the validity date passes, the system initiates the new hire suspension process to prevent benefits from being offered online to new hires.
The system runs the new hire suspension process automatically once a day when the first administrator logs on to a SCORPEO or HRP.ADMIN account and applies the suspension to any new hires. (PrismHR customers must log on to their HRP.ADMIN account every day for this process to run). Administrators can also manually run the process once a day (at any time) using the Suspended Employee Enrollment Process form.
A benefits administrator then reviews and updates the benefits offered, and adjusts the Benefits Rules Good Through Date when the benefit offerings are ready for new enrollments. As long as the enrollment workflow has the notification enabled, employees receive a notification that they can now enroll online.
Users can run the Suspended Enrollment Employee Report to view employees whose benefits enrollments are suspended or on hold.
The Benefits Good Thru Date cannot be blank if the client had a Good Thru Date at any time in their record.
To enable the new hire suspension process at the system level:
Click Back Office.
From System|Change, select System Parameters. The System Parameters form opens.
Click the Custom Feature Codes link. From the list, select SUSPENDENH.
Click Save.
To indicate the latest validity date for enrollment offerings for new hires:
Click the Client menu.
From Client|Change, select Client Details. The Client Details form opens.
On the Benefits tab, enter a date in Benefits Rules Good Through Date. When this date passes, the system initiates the new hire suspension process. If the system finds that an employee’s earliest potential eligibility date exceeds the Benefits Rules Good Through Date, it suspends the employee’s enrollment.
On the Employee Details form Other tab, you can view records for employees whose enrollments are suspended. They display a date in the Enrollment Suspended Until field. This date indicates the next date that the new hire suspension process will review the record again. The date automatically advances by one day each time the process determines that the record should remain suspended. For more information, see the Human Resources User Guide.
The system runs the New Hire Suspension Process automatically once a day and applies the suspension to any new hires. If needed, administrators can use the Suspended Employee Enrollment Process form to manually suspend benefit enrollments for new hires at any time.
You can also run the Suspended Enrollment Employee Report to view employees whose benefits enrollments are suspended. For more information, see Suspended Employee Enrollment.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Notification_Audit_Report.htm
Path:
OBE/Benefits Enrollment/Topics/Notification_Audit_Report.htm
The Notification Audit Report provides a listing of notifications sent to all recipient types (for example, employees, generic recipients, message groups). You can run the report for a specific client and employee or for all clients and employees.
Note: Note: The Notification Audit Report form contains client and employee‑level security. Only clients and employees you have access to display in the report.
To run the Notification Audit report:
Click Reports.
From Benefits|Report, select Notification Audit Report. The Notification Audit Report form opens.
Enter the Client ID for the report. If you leave the Client ID blank, the report runs for all clients. The Employee ID field displays.
If you want to run the report for a specific employee, enter an Employee ID. If you leave Employee ID blank, the report runs for all employes.
Select the Start Date and the End Date from the respective date pickers. Please ensure that the date range you provide in these fields must be a range within a year. These two fields are mandatory.
Click Run. The report displays information in the following columns.
Column — Description
Client ID — The client ID.
Employee ID — The employee ID.
Notification Type — The notification trigger type specified in the template.
Notification Date — The date the notification was sent.
Notification Time — The time the notification was sent.
Triggering Workflow — The ID that is created when new messages are triggered.
Notification Template ID — The Notification template sent, including information on language (for example, en_US) and the template ID number.
Notification template name — The name of the notification template for you to understand the nature of the notification sent to users.
Recipients — Recipients for the notification.
Recipient Email — Email of the recipients where the notification is to be sent.
Message ID — Message ID generated by the engine that identifies the notification sent.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Notification_Control_Panel_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Notification_Control_Panel_BE.htm
Use the BE Notify section in the Notification Control Panel to:
Start or stop the notifications engine during enrollments
Determine the frequency at which the notifications engine sends notifications
Note: Note: Settings are at the system level. You can also access the New Message form in the Actions menu
[Image: screenshot]
.
Notifications are added to workflows in the Workflow Library. During enrollments, the system sends out event and time-based notifications attached to the workflows to the notification recipients specified.
Note: Note: The system sends notifications only for organizations that have the Enabled Benefits Enrollment option selected in Global Configuration. If the option is not checked, the Notification Control Panel does not send notifications. You can turn notifications off at the client-level in the Client Workflow Grid.
Open enrollment notifications are sent once a day (typically at midnight).
Benefits enrollment notifications are sent at the interval specified.
Approval notifications are sent immediately.
Note: Note: The background process automatically runs BE Notify, Payday Notify, ACH Processing, and Payroll Reminders. However, if BE Notify is turned off, the other processes continue to run.
The PrismHR Customer Support Team recommends that you set up open enrollment workflows at least one day before the window opens.
To set up benefits enrollment notification controls:
Click Back Office.
From Operations|Action, select Notification Control Panel. The Notification Control Panel opens.
For this option — Define this information
BE Notify Interval (mins) — The number of minutes to use for the current benefits enrollment interval. This interval determines how often the system checks for new hires and sends the notifications specified in the benefits enrollment workflow. You can enter a number from 5 to 1440 minutes. > Note: Note: The OB Notify Interval (mins) and OB Notify Date options in the OB Notify section are used only in Onboarding and do not affect Benefits Enrollment.
OE Notify Date — The most recent date when the system sent notifications for open enrollment. It populates automatically. By default, the notifications engine sends notifications for open enrollment every day. If you need to manually resend a notification for an enrollment (for example, if the notification was not received by employees, or if there is a change to the notification template), delete the displayed date, and then click Submit. The system resends notifications using the current date. When the process completes, the current date displays. > Note: Note: The OB Notify Interval (mins) and OB Notify Date options in the OB Notify section are used only in Onboarding and do not affect Benefits Enrollment.
Client — Whether to restrict notifications to one specified client. This is typically done only for testing notifications using a test client (for example, when you test to confirm that the enrollment user works correctly). Leave this field blank to apply settings at the system level.
Click this in the BE Notify section — To do this
Status — Check whether the notifications engine is running or not running. The status displays the process ID (PID) number.
Stop — Stop the system from sending notifications. The Stop option changes to Start and the status changes to not running. The request to stop notifications takes effect immediately. However, it can take a few minutes for the updated status to display correctly. > Note: Note: The Stop button in the OB Notify section is used only in Onboarding and does not affect Benefits Enrollment.
Start — Start the notifications engine without changing settings. The Start option changes to Stop and the status changes to running. If you stop and then restart the notifications engine, the PID number resets and a new PID displays.
Cancel — Close without changing settings.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Notification_Recipients_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Notification_Recipients_BE.htm
To set up recipients for enrollment notifications created using the Notification Templates form, use the Notification Recipients form.
This form can also be used to modify or delete existing notification recipient records. However, recipient records that are currently associated with a notification template cannot be deleted.
[Image: screenshot]
To set up notification recipients:
Click Back Office.
From System|Change, select Notification Recipients. The Notification Recipients form opens.
Complete the following fields:
Field — Action
Notification ID — Enter an existing notification ID, or click Setup a new Notificationcreate a new notification.
Name — Enter a name for the notification recipient group. The name displays on the Workflow Library form in the list of notification users you can add to workflows.
Description — (Optional) Enter a description for the notification.
Panel — Description
To Group Recipients — Primary recipients for the notification, organized by group (for example, Internal Employees, Managers, and so on). To set up groups, use the Message Center Groups form. > Note: Note: Message groups that include client records cannot be used in notification recipient records.
To Generic — Primary recipients for the notification, organized by role: Employee, Client Benefit Rep, Human Resources, Client Manager, I-9 Section 2 Approver. The Client Benefit Rep, Human Resources, and Client Manager roles can be assigned to users using the Users form. The I-9 Section 2 Approver role is specific to Onboarding and is not used in Benefits Enrollment.
CC Group Recipients — Additional recipients to copy publicly, organized by group.
CC Generic — Additional recipients to copy publicly, organized by role.
BCC Group Recipients — Additional recipients to copy privately, organized by group.
BCC Generic — Additional recipients to copy privately, organized by role.
In the Notification Template panel, enter the ID number of the template to use in the Template ID field. The name and description associated with the template are automatically entered in the appropriate fields, and the appropriate check boxes are selected for the associated workflow type and message delivery method.
Click Save.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Notification_Templates_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Notification_Templates_BE.htm
The Notification Templates form is used to create templates for the notifications that are sent to employees or groups during benefit enrollments, open enrollments, anytime enrollments, or life event enrollments. Each template specifies the content that is included in the notification, such as the subject and message body, as well as the criteria for sending the notification and the communication method used to send the notification.
When defining notification content, substitution variables can be used to replace generic information with specific information from PrismHR.
Once the template has been created, the Notification Recipients form can be used to define the recipients who receive the notification. Refer to Setting Up Notification Recipients (Benefits Enrollment) for more information. In addition, the notifications can be added to a workflow using the Workflow Library. Refer to Creating a Workflow (Benefits Enrollment) for more information.
Note: Note: Notification templates that have been attached to a workflow or a notification recipient record cannot be deleted.
To set up a notification template:
Click Back Office.
From System|Change, select Notification Templates. The Notification Templates form displays.
In the Notification Templates panel, complete the following fields:
Field — Action
Template Id — To modify an existing template, enter a template ID or click Template Id to display a list of existing templates. To create a new template, click Create a New Template. An available template ID is entered in the Template Id field.
Name — Enter a name for the template. This name identifies the template and displays in the list of available templates when assigning notification recipients.
Description — Enter a description of the template.
Language Default — For future development. Does not currently impact the functionality of PrismHR.
Subject — Enter a subject for notifications sent using the template. > Note: Note: Do not use square brackets ([ or ]) in this field as doing so will prevent recipients from receiving notifications sent using this template.
Message Body — Enter the body text for the notifications sent using the template.
SMS Body — For future development. Does not currently impact the functionality of PrismHR.
In the Workflow Type panel, select the type of enrollment during which to send notifications using this template.
In the Notification Triggers panel, complete the following fields:
| Field | Action |
|---|---|
| Trigger Type | Select a notification trigger type. - Time Based: Notifications are sent a specific number of days before the workflow’s start date or due date. If the notification engine is set up to check in the morning, the notifications are sent in the morning. If the notification engine is set up to check every other day, the notifications are sent every other day. Notification engine settings are defined using the Notification Control Panel. Refer to Using the Notification Control Panel (Benefits Enrollment) for more information. - Event Based: Notifications are sent when a specific event occurs, such as when a benefits enrollment workflow is completed. The notification engine runs in the background and periodically checks to see whether there are notifications to send and sends event-based notifications when they turn up during the check. |
Note: Note: The Send SMS option is for future development and does not currently impact the functionality of PrismHR.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Over%20Age%20Dependents%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Over Age Dependents Report.htm
Use this form to generate a report of any dependents associated with a COBRA benefit plan whose age is greater than the dependent age limit defined on the benefit plan.
Note: Note:
Worksite Managers, Worksite Trusted Advisors, and Service Providers can access the form.
Client Access Group Security and Data Entity security is enabled on this form.
To access the form, click Reports. Under Benefits|Report, click Overage Dependents Report.
To generate the Overage Dependents Report:
Field Name — Description
Client ID — This field is optional. Leave this field blank for this report to run for all clients. If you want to restrict this report to run for selected clients, enter the Client IDs here or click the Client ID link and select them from the Select Clients dialog box.
Click Run to generate the report. The report shows up on screen.
Click Clear to clear the form at any time.
Click Close to close this form.
This report shows the following columns:
Client ID
Employee ID
Employee Name
Dependent ID
Dependent Name
Birth Date
Age
Benefit Plan ID
Benefit Plan Name
Cutoff Age
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Overage_Enrollees_Report.htm
Path:
OBE/Benefits Enrollment/Topics/Overage_Enrollees_Report.htm
Use this form to run a report of overage enrollees for benefit plans where Maximum Age has been defined in the Benefit Rules eligibility criteria.
Note: Note:
To access this form and run the report:
Click Reports.
From Benefits|Report, select Overage Enrollees Report. The Overage Enrollees Report form opens.
Under the Selection Criteria section, enter the Client ID for the report. If you leave the Client ID blank, the report runs for all clients.
Click Run to generate the report. The report shows up on screen.
Click Clear to clear the form at any time.
Click Close to close this form.
This report shows the following columns:
Client ID
Employee ID
Employee Name
Birth Date
Age
Benefit Plan ID
Benefit Plan Name
Cutoff Age
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/PBE_Creating_a_New_Batch.htm
Path:
OBE/Benefits Enrollment/Topics/PBE_Creating_a_New_Batch.htm
To create a new batch for posting, use the Post Benefit Enrollment form. Once created, the new batch displays in the table. You can then review the batch. After all enrollments pass review and their status display as Ready to Post, you can post the batch.
Click Back Office.
From Operations|Action, select Post Benefit Enrollments. The Post Benefit Enrollments form opens.
Click Start New Batch. The New Batch View displays, where you can filter and select the enrollments to include.
Use Batch Filters to filter the list and narrow the view to only those enrollments you want to include. The Batch Filters panel includes:
Column — Description
Client ID — The Client ID for the client whose enrollments to display. You can also click a Client ID listed in the table to populate this field. Additionally, you can select multiple Client IDs using the selection modal.
Effective On or After — A date to view enrollments that are on or after that date.
Effective On or Before — A date to view enrollments that are on or before that date.
Name Starting — Letters from the start of an employee’s name to filter enrollments and locate a specific employee.
Name Ending — Letters from the end of an employee’s name to filter enrollments and locate a specific employee.
Enrollment Type — Whether to filter enrollments by (OE) Open Enrollments or (BE) Benefit Enrollments.
Status Class — The status of the employee. You can select from Active, On Leave, or Terminated.
Life Event — The life event code and description.
Benefit Group — A benefit group by which to filter enrollments.
Pay Group — A pay group by which to filter enrollments.
When the enrollments to include in the batch display in the filtered view, click Create Batch. The Batch Name box opens.
Enter the Batch Name.
Click Create. The system prompts for confirmation.
Click Yes. The system creates the batches and automatically generates the Batch Number. The new batch displays in the Batch Detail View, listing the selected enrollments.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/PBE_Posting_a_Batch.htm
Path:
OBE/Benefits Enrollment/Topics/PBE_Posting_a_Batch.htm
When all enrollments in the batch are reviewed and display the Ready to Post enrollment status, you can post the batch by clicking Post.
The system runs a final check on the enrollments included in the batch.
If any enrollments contain errors, the posting process stops. You must fix the errors or remove the failed enrollments from the batch before you can post the batch. The system prompts you to specify whether to save the failed enrollments to a new batch.
If posting is successful, the Batch Detail View of the form displays with the Enrollment Status Post Complete.
When your organization selects Auto post BE/OE enrollments when overlap with OE in the Enrollment Options form, the system automatically posts any new enrollment records created for employees during an active open enrollment period. If the enrollment posts successfully, a new enrollment record is automatically created for the employee for the active open enrollment.
If posting for this new enrollment record fails, the posting batch that includes the new enrollment does not post but remains in the posting queue in the Post Benefit Enrollments form. The enrollment record displays the status Review Failed. In such a case, you must manually fix all errors in the enrollment before it can post.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/PBE_Reviewing_a_Batch.htm
Path:
OBE/Benefits Enrollment/Topics/PBE_Reviewing_a_Batch.htm
Click Review to review a batch when its status is Ready to Review. When the review is complete, the Batch Detail View displays. If the review process finds no errors in an enrollment, it returns the enrollment status Ready to Post. The enrollment can now be posted.
Note: Note: All enrollments included in the batch must have the Ready to Post enrollment status to successfully post.
If the review process finds errors in any of the enrollment records:
The system displays the following alert: Would you like to move the enrollments that failed review to a new batch so you can continue to post this batch? and prompts you to click Yes or No.
Records that failed to post are not removed from the batch. The Error Report and Change Report options display at the bottom of the batch table:
Click Error Report to run the Benefit Enrollment Review Error Report to review specific enrollment errors in the batch.
Click Change Report to run the Benefit Enrollment Review Change Report to review the changes and fixes made to the enrollments.
If Yes, the system prompts you to enter a batch name and to confirm that you want to proceed. The system displays the following message: Failing enrollments have been moved to a new batch [Batch Name] [Batch Number].
The system moves the Benefit Enrollment Review Error Report and the Benefit Enrollment Review Change Report for these enrollments to the new batch where you can view them without doing another review. The system allows you to remain in the original batch where you can then post the batch with the remaining enrollment records.
You must fix all enrollment errors before the enrollment can be posted with a batch. You can remove an enrollment from the batch at any time by clicking selecting one or more enrollments and clicking Remove. When you remove an enrollment, it returns to the list of available enrollments.
After you fix the enrollment errors, review the batch again until the errors are fixed. Each time you review, the Benefit Enrollment Review Error Report and the Benefit Enrollment Review Change Report are updated. You can review the batch as many times as needed before posting.
Use the Benefit Enrollment Review Error Report to review errors in the enrollment records that can occur when posting a batch in the Post Benefit Enrollments form. You must fix all errors for the system to successfully post the enrollment record.
The following information is shown for each error.
Company: The client ID.
Employee: The employee ID.
Employee Name: The employee name.
Offer Type: The offer type for the benefit plan that generated the error message.
Error Message: The error message.
After posting a batch on the Post Benefit Enrollments form and correcting any errors, you can use the Benefit Enrollment Review Change Report to review changes made to the enrollment records during that process.
The following information is displayed on the report:
Company: The client ID.
Employee: The employee ID.
Employee Name: The employee name.
Offer Type: The offer type for the benefit plan that generated the error message.
Plan ID: The plan ID for the benefit plan.
Plan Name: The name of the benefit plan.
Type: The plan type or tier selected for the benefit plan.
Action: A description of the change that was made to the enrollment.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/PBE_Viewing_Batches.htm
Path:
OBE/Benefits Enrollment/Topics/PBE_Viewing_Batches.htm
Before you can post benefit enrollments, you must organize the enrollment records to include into batches. By default, the Post Benefit Enrollments form displays a list of batches that are not yet posted.
The number of enrollments that are not included in a batch displays in parentheses next to the Start New Batch link. You can click Start New Batch to create a new batch using these available enrollments.
You can view batches that were successfully posted by selecting Display Posted Batches Only.
The table lists information about each batch in the following columns.
Column — Description
Batch Name — The batch’s name. Click to open the Batch Detail View.
Batch Number — The batch’s number. Click to open the Batch Detail View.
Status — The batch status.
Date Created — The date the batch was created.
Last Updated — The date of the latest change made to the batch.
Enrollments — The number of enrollments included in the batch.
Needs Review — The number of enrollments in the batch that need to be reviewed before posting. You can view the enrollments in the Batch Detail View.
To view a specific batch and the enrollments it includes, enter the Batch Number and press Enter. You can also access the Batch Detail View by clicking the Batch Name or Batch Number of a batch displayed in the batch list.
The Batch Detail View displays information about the batch selected and lists the included enrollments.
| Column | Description |
|---|---|
| Confirm # | The confirmation number for the enrollment record. You can click this link to view the enrollment details in the Employee Enrollment Summary in the Benefit Enrollment Detail Inquiry form. |
| Client Name | The client name. |
| Client ID | The client ID. |
| Employee Name | The employee name. |
| Employee ID | The employee ID. |
| Enrollment Type | The enrollment type (Open Enrollment or New Hire Enrollment). |
| Start Date | The enrollment start date. |
| End Date | The enrollment end date. |
| Effective Date | The enrollment effective date. |
| Enrollment Status | The enrollment status. - If the status is Ready to Post for all enrollments in the batch, you can post the batch. - If the status for any included enrollment is Ready to Review, the batch was not reviewed for posting. You must review the batch before you can post. - If the status for any included enrollment is Review Failed, the review process found a problem in the enrollment record. You must fix the enrollment record and run the review process again, or remove the enrollment from the batch before you can post. - You can remove an enrollment from the batch by clicking [Image: screenshot] (Remove). Once removed, the enrollment is returned to the list of available enrollments. |
To view the enrollment summary:
The form displays the following information:
| Column | Description |
|---|---|
| Employee Name | The employee name. |
| Company | The name of the company. |
| Confirmation # | The confirmation number of the enrollment record. |
| Employee ID | The employee ID. |
| Workflow | The name of the enrollment workflow. |
| Enrollment Type | The enrollment type (Open Enrollment, Benefits Enrollment). |
| Post Status | The posting status for the enrollment. |
| Status Date | The date the post status was updated. |
| Effective Date | The enrollment effective date. |
| Start Date | The start date for the enrollment. |
| End Date | The end date for the enrollment. |
The employee’s benefit elections display in the main table.
Column — Description
Offer Description — The type of benefit plan and the benefit plan’s offer type. You can click this field to view the enrollment details in the Employee Enrollment Detail in the Benefit Enrollment Detail Inquiry form.
Elected — The name of the benefit plan elected.
Elected Description — A description for the benefit plan elected.
Plan Type — The benefit plan type.
Waived — Whether the employee waived coverage (Yes or No).
Plan Eff Date — The benefit plan effective date.
Flex Plan — Whether the plan is a flexible spending plan (Yes or No).
Flex Year — The coverage year for the flexible spending plan.
Offer Status — The status for the benefit plan.
Status Date — The date the offer status was updated.
The Employee Enrollment Detail in the Benefit Enrollment Detail Inquiry form displays information about the employee’s enrollment for a specific offer type.
The form displays the following information in the Employee Enrollment Detail panel.
| Column | Description |
|---|---|
| Employee Name | The employee name. |
| Company | The name of the company |
| Confirmation # | The confirmation number of the enrollment record. |
| Employee ID | The employee ID. |
| Workflow | The name of the enrollment workflow. |
| Enrollment Type | The enrollment type (Open Enrollment, Benefits Enrollment). |
| Post Status | The posting status for the enrollment. |
| Status Date | The date the post status was updated. |
| Effective Date | The enrollment effective date. |
| Start Date | The start date for the enrollment. |
| End Date | The end date for the enrollment. |
The form displays the following information in the Offer Type panel.
| Column | Description |
|---|---|
| Offer Type | The Offer Type and the Post Status display at the top of the panel. |
| Offered Plans | All plans offered in the enrollment for the selected offer type. |
| Description | The plan description. |
| Effective Date | The plan’s effective date |
| Selected | The plan selected by the employee displays in bold with a checkmark in this column. |
The following additional information can display depending on the type of benefit plan selected and its settings.
Column — Description
Plan Type Enrolled In — The plan type used for the enrollment in the plan.
Employee Contribution Rate — The employee’s contribution.
PCP ID — The ID for the employee’s primary care physician.
PCP Name — The name of the employee’s primary care physician.
Plan Guaranteed Issue Amount — The guaranteed issue (GI) amount for a life insurance or disability plan.
Coverage — The amount of coverage provided for the employee up to the GI limit in a life insurance or disability plan. Coverage amounts for spouse and dependents display depending on plan type.
Premium — Premium amounts for spouse and dependents display depending on plan type.
GI Overage — The amount of coverage that is over the GI limit.
The form displays the following information in the Covered Dependents panel.
| Column | Description |
|---|---|
| ID | The dependent’s ID. |
| Name | The dependent’s name. |
| Relation | The dependent’s relationship to the employee. |
| DOB | The dependent’s date of birth. |
| Age | The dependent’s age. |
| Disabled | Whether the dependent is disabled. |
| Tobacco User | Whether the dependent is a tobacco user. |
| Student | Whether the dependent is a student. |
| PCP ID | The ID for the dependent’s primary care physician. |
| PCP Name | The name of the dependent’s PCP. |
The form displays the following information in the Beneficiaries panel.
| Column | Description |
|---|---|
| ID | The beneficiary’s ID. |
| Name | The name of the beneficiary. |
| Relation | The beneficiary’s relationship to the employee. |
| Primary | The percentage allocated by the employee for primary beneficiaries. |
| Contingent | The percentage allocated by the employee for contingent beneficiaries. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Pending%20Benefit%20Self-Billing%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Pending Benefit Self-Billing Report.htm
Use this form to show benefit enrollment billing and liability data, with counts by plan and coverage to report to insurance carriers.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, under Work Centers, under Onboarding & Benefits, click Benefit Imports & Reporting. Under Benefit Reporting, click Pending Benefit Self-Billing Report.
To generate the Pending Benefit Self-Billing Report:
Field Name — Description
As Of Date — Enter the effective date of this report.
Client ID — Enter the client ID for which you want to run this report or click the Client ID link and select one from the Select Client dialog box. This field is optional. Leave it blank to run for all clients.
Cost Center — Enter the Cost Center code for which you want to run this report or click the Cost Center link to select one from the Select Cost Centers dialog box. This field is optional. Leave it blank to run for all cost centers.
Sort by Network — Check this box is you want to sort this report by Network ID. By default this box is unchecked wherein the report sorts by Benefit Plan ID.
Benefit Plan ID — Enter the benefit Plan IDs for which you want to run this report or click the Benefit Plan ID link and select from the Select Plan dialog box. This field is optional. Leave it blank to run for all applicable benefit plans.
Click Run to generate the report. The report shows up on screen. Click XLS to download the report.
Click Clear to clear the screen at any time.
This report displays the following information:
Plan ID
Plan Name
Employee ID
Employee Name
Employee Social Security Number
Employer ID
Cost Center
Plan Type
Plan Status
Employee Coverage
Spouse Coverage
Depends Coverage - Dependent’s Coverage
Coverage Start Date
Coverage End Date
Billed Premium
Insurance Premium
Variance
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Pending%20COBRA%20Participants%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Pending COBRA Participants Report.htm
Use this form to generate a report of pending COBRA participant records with the date of the qualifying event and the status and status date.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, under Work Centers, under Onboarding & Benefits, click COBRA Processing. Under COBRA Reports, click Pending COBRA Participants Report.
To generate the Pending COBRA Participants Report:
Field Name — Description
Client ID — This field is optional. Leave this field blank for this report to run for all clients. If you want to restrict this report to run for selected clients, enter the Client IDs here or click the Client ID link and select them from the Select Clients dialog box.
Click Run to generate the report. The report shows up on screen.
Click Clear to clear the form at any time.
This report shows the following columns:
Qualifying Event Date
Status
Status Date
Employee ID
Employee Name
Client ID
Client Name
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Post_Benefit_Enrollments.htm
Path:
OBE/Benefits Enrollment/Topics/Post_Benefit_Enrollments.htm
Use the Post Benefit Enrollments form to view, create, review, and post benefit enrollments in Benefits Enrollment.
To work with the Post Benefit Enrollments form:
Click Back Office.
Select Operations|Action > Post Benefit Enrollments.
Enter the required information.
| Option | Description |
|---|---|
| Batch Number | Limits posting to a specified batch. |
| Display Posted Batches Only | Includes only posted batches. |
| Start New Batch | Starts a new batch based on your specifications. - Batch Number - Batch Filters - Client ID - You can select multiple Client IDs using the selection modal. - Effective On or After/Effective On or Before - Name Starting/Name Ending - Enrollment Type - Status Class - Benefit Group - Pay Group |
See the following:
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Pre-Filter_Options.htm
Path:
OBE/Benefits Enrollment/Topics/Pre-Filter_Options.htm
Before launching the Bulk Launch Benefit Workflow form, pre-filtering options display that let you select specific criteria (clients, employhment type, employment status) to narrow results, which improves response time. None of these filters are required.
To set a pre-filter:
Select one or more pre-filter options. You can specify Client(s), Employment Type(s), and Employment Status.
Click Continue to complete pre-filtering. The main Bulk Launch Benefit Workflow form displays.
Note: Note: You can return to pre-filtering by clicking Return To The Pre-Filter Selections Page.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Prebuilt_Form_BE.htm
Path:
OBE/Benefits Enrollment/Topics/Prebuilt_Form_BE.htm
You can create a new form in the Form Library using one of the prebuilt forms that Benefits Enrollment provides. Using this option, you can edit the default text in the headers and footers. The rest of the content is prebuilt for you. It is best practice to use a consistent convention for naming forms.
When you submit a form, the system sets its version and revision numbers.
To create a new form based on a prebuilt form:
Click Back Office.
From System|Change, select Form Library. The Form Library opens.
In the row of the prebuilt form to use (medical, dental, vision, life insurance, and so on), select Duplicate. The Duplicate Form displays.
Enter a New ID and New Name for the form.
Click Duplicate. The Customize Prebuilt Form form opens.
On the General tab Version, Revision, Status, Start Date, End Date, Workflow Type, and Offer Type are read-only.
| Use this option | To define this |
|---|---|
| Form ID | A unique ID for the new form. |
| Form Name | The name of the form. Editable and Required. |
| Description | A description of the form. Editable and Required. |
| Use this option | To define this |
|---|---|
| Field Default Value | The default value for the option. |
| Insert Link | For future development. Does not currently impact the functionality of PrismHR. |
To preview the form before saving, click Preview Form.
To return to the Form Library without saving changes, click Back to Forms Library.
Option — Description
Immediately — The system sets the form status immediately to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the form status to Inactive, changing it to Active on the start date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the start date for the new version as its End Date.
Save as Draft — The form status is set to Draft. The system does not set a Start Date nor does it set version or revision numbers for the form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Required_Document_Rulesets.htm
Path:
OBE/Benefits Enrollment/Topics/Required_Document_Rulesets.htm
To assign one or more required documentation rulesets to a benefit plan, use the Required Documentation Rulesets panel in the Plan Enrollment Details form.
Benefits Enrollment provides the following rulesets:
Domestic Partner
Dependents with Different Last Names
Disabled Dependents
Disabled Over-Age Dependents (Florida residents)
Disabled Over-Age Dependents (New York residents)
Florida Contract Benefit Plans
To set up required documentation and dependent eligibility rulesets, use the Required Documentation Rulesets panel in the Plan Enrollment Details form. This panel displays only for offer types that might require special documents.
To set up required document and dependent eligibility rulesets:
Click Back Office.
From System|Change, select Group Benefit Plans. The Group Benefit Plans form opens.
Click the Actions menu [Image: screenshot] and select Enrollment Details.
In the Required Documentation Rulesets panel, select the effective date for the benefit plan to modify.
A benefit plan can have multiple effective dates with different settings, which are then used for different enrollments. You can click New Effective Date to create a new effective date.
| Rule | Domain | Ruleset |
|---|---|---|
| Domestic Partner | PRISMHR-BE | DOCUMENT-PARTNER |
| Dependents with Different Last Names | PRISMHR-BE | DOCUMENT-LASTNAME |
| Disabled Dependents | PRISMHR-BE | DOCUMENT-DIS |
| Disabled Over-Age Dependents (Florida residents) | PRISMHR-BE | DOCUMENT-FLO |
| Disabled Over-Age Dependents (New York residents) | PRISMHR-BE | DOCUMENT-NYO |
| Florida Contract Benefit Plans | PRISMHR-BE | DOCUMENT-FLCT |
| Rule | Domain | Ruleset |
|---|---|---|
| Dependent Eligibility | PRISMHR-BE | DEPEN-ELIGIBILITY |
This rule is required. Before evaluating an employee’s dependents for the benefit plan’s rulesets, the system checks the employee’s dependents’ eligibility for the benefit plan. This check runs only if the Dependent Eligibility rule is set up.
PCP Required: For future development. Does not currently impact the functionality of PrismHR.
Click Save.
The following sections explain how the system evaluates and applies documentation rulesets.
Before evaluating an employee’s dependents for the benefit plan’s rulesets, the system checks the employee’s dependents’ eligibility for the benefit plan.
This check runs only if the domain and ruleset are set up for the Dependent Eligibility rule. If the domain and ruleset are not set up for the Dependent Eligibility rule, the benefit plan does not display in the enrollment, and the system does not apply any of the documentation rulesets.
When the Dependent Eligibility rule determines that the employee’s dependents are eligible for a benefit plan, the benefit plan displays in the employee’s enrollment.
The system then evaluates the employee’s dependents to see whether they satisfy the conditions for the required documentation rulesets that are set up in the benefit plan. If a required documentation ruleset applies to the dependent (for example, if the employee includes a domestic partner as a dependent in the enrollment), the system triggers the required document for the employee to complete.
You must upload required documents to the Document Repository and tag them correctly.
Documents attached to a benefit plan display in the employee’s Benefit Summary when the enrollment is complete.
If the Dependent Eligibility rule is set up, the system evaluates dependent eligibility for the benefit plan before determining whether the employee’s dependents satisfy the conditions for the required documentation rulesets.
If the dependent is a domestic partner or has a different last name, the system proceeds to the next step and determines whether the dependent satisfies the required documentation ruleset eligibility conditions. If the dependent does not satisfy these conditions, one of the following sets of conditions must apply for the dependent to be determined to be eligible for the benefit plan.
| Condition Set | Conditions |
|---|---|
| Condition Set #1 | - The dependent is set up with the Relationship Type Dependent in the Employee Dependents form. - The dependent is a Florida resident, as determined by the dependent’s state (if the dependent has no state entered, the system defaults to the employee’s state). - The benefit plans is either a medical (MED) or gap (GAP) plan, and the dependent’s age is less than 30. |
After the system determines dependent eligibility, it evaluates the employee’s dependents to see whether they satisfy the conditions for the required documentation rulesets. If a dependent satisfies the conditions, the system triggers the required document for the employee to complete.
| Rule | Conditions |
|---|---|
| Domestic Partner (DOCUMENT-PARTNER) | - The dependent is set up with the Relationship Type Dependent and has the Relation set to Domestic Partner in the Employee Dependents form. The Relationship Code Domestic Partner must also be set in the Relationships form with the Domestic Partner Relationship Type. - Your organization must set up the required document with the File Tag DP in the Document Repository. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Restart_NCP.htm
Path: OBE/Benefits Enrollment/Topics/Restart_NCP.htm
If you are re-sending a time-based notification, the trigger condition must match today’s date for the system to send the notification. For example, to re-send the open enrollment (OE) welcome notification to employees, the start date of the OE enrollment period on the Workflow Grid must be today’s date.
Before you restart the notification control panel:
To restart the Notification Control Panel:
Click Back Office.
From Operations|Action, select Notification Control Panel. The Notification Control Panel opens.
Click BE Stop. The message SHUTDOWN REQUESTED displays.
Click Status. The status displays NOT RUNNING.
To restart notifications, select BE Start.
Click Save. The current date populates the OE Notify Date.
Click Status. The status displays RUNNING.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Retirement%20Adjustment%20Transaction%20Audit%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Retirement Adjustment Transaction Audit Report.htm
Use this form to generate an audit report for all transactions relating to retirement plan adjustments.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, under Work Centers, under Onboarding & Benefits, click Benefit Imports & Reporting. Under Benefit Reporting click Retirement Adjustment Transaction Audit Report.
To generate the Retirement Adjustment Transaction Audit Report:
Field Name — Description
Adjustment Date On or After — Enter the start date of your report period.
Adjustment Date On or Before — Enter the end date of your report period.
Client ID — This field is optional. Leave it blank to run for all clients. Enter the client IDs for which you want to run this report or click the Client ID link and select the ones from the Select Client dialog box.
Click Run to generate the report. The report shows up on screen. Click XLS to download the report.
Click Clear to clear the form at any time.
Click Close to close this form.
This report shows the following columns:
Client ID
Transaction ID
Entry Date
Entry Time
User Name
Employee ID
Employee Name
Adjustment Date
Plan Year
Period
Retirement Earnings
Employee Contribution
Catch-up Contribution
Post Tax Contribution
ROTH Contribution
ROTH Catch-up Contribution
Employer Contribution
Non-Elect Contribution
Loan Payment
Safe Harbor Type 1 Contribution
Safe Harbor Type 2 Contribution
Successor Retirement Deferral
Successor Catch-up Deferral
Successor ROTH Deferral
Successor ROTH Catch-up Deferral
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Retirement%20Auto%20Enrollment%20Report.htm
Path:
OBE/Benefits Enrollment/Topics/Retirement Auto Enrollment Report.htm
Use this form to generate a report to show the list of employees auto enrolled for a retirement plan based on their following auto enrollment statuses:
Active – This report shows retirement enrollments for active employees who were automatically enrolled in the system. Their status on the Retirement Plan Enrollment form is Active Enrolled.
Eligible – This report shows new hire employees who were automatically enrolled into a retirement plan upon hire, but their status on the Retirement Plan Enrollment form is still Eligible Unenrolled. This is the status of all new hire employees retirement enrollment until they are calculated in a payroll. The payroll calculation will automatically apply the Benefit Plan Setup Auto Enrollment Percent, and change the status to Active Enrolled. These employees will appear on this report until the status is changed to Active Enrolled.
Note: Note: If the Auto Enrollment Percent on the Benefit Plan Setup form is not set up, the employee does not change to Active Enrolled upon payroll calculation.
Note: Note: Client Access Group Security is enabled on this form.
To access the form, under Work Centers, under Onboarding & Benefits, click Benefit Imports & Reporting. Under Benefit Reporting click Retirement Auto Enrollment Report.
To generate the Retirement Auto Enrollment Report:
| Field Name | Description |
|---|---|
| Auto Enrolled Status | Select the auto enrollment status of the employee for whom you want to run this report from the following options: - Active - this is the default option - Eligible |
| Field Name | Description |
|---|---|
| Updated on or After | Enter the date from which you want to report on. |
| Updated on or Before | Enter the date up to which you want to report on. |
Click Run to generate the report. The report shows up on screen. Click XLS to download the report.
Click Clear to clear the form at any time.
This report shows the following fields:
Client ID
Client Name
Employee ID
Employee Name
Start Date
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Review_Workflow_Request.htm
Path:
OBE/Benefits Enrollment/Topics/Review_Workflow_Request.htm
The Review Workflow Request form builds workflow information and populates it with data. You can review and make updates for selected employees.
To access this form:
From the main Bulk Launch Workflows form, click Launch Benefit Enrollment. The Review Workflow Request form opens.
Select one or more employees by checking the box next to the Client ID.
Change the workflow, effective date, start date, or end date. Client ID, Employee ID, and Employee Name are read-only.
Click Continue to archive existing workflows and to create benefit enrollment workflows.
Note: Note: If you have blank fields, the system outlines them in red and the process does not occur.
You can run the process and then view the results or download the results to a CSV file (on Bulk Workflow Results). Once you leave this report view without downloading, the report is no longer available.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Setting_Up_Waive_Options%20_on_Benefit_Plans.htm
Path:
OBE/Benefits Enrollment/Topics/Setting_Up_Waive_Options _on_Benefit_Plans.htm
Organizations can establish whether employees have the option to waive coverage for benefit plans during enrollment using settings at both the system and client level in PrismHR. (PrismHR Benefits Enrollment only.)
The system runs the following checks to determine whether to display the employee option to waive coverage during enrollments.
When the option is … — Then …
Selected — The option to waive coverage displays in all benefit plans assigned the offer type. This setting overrides all other settings.
Not Selected — The option to waive coverage is not set up at the system level for the offer type. The system checks the employee’s contribution to determine employee waive options.
When the employee’s contribution is … — Then …
Greater than $0 — The employee has the option to waive coverage in the benefit plan.
$0 — The option to waive coverage is not set up for the benefit plan. The system checks the Auto Enroll setting on the benefit plan to determine employee waive options.
When the option is set to … — Then …
N for No — The employee has the option to waive coverage in the benefit plan.
Y for Yes — The employee auto enrolls in the benefit plan and does not have the option to waive coverage.
Company Decision — The system checks the Auto-Enrollment setting on the benefit plan at the client level to determine employee waive options.
When the option is … — Then …
Selected — The employee auto enrolls in the benefit plan and does not have the option to waive coverage.
Not selected — The employee has the option to waive coverage in the benefit plan.
The employee waive option displays in the form for the benefit plan offer type during enrollment. If settings on even one benefit plan included in an offer type establish that employees can waive coverage, the option to waive displays in the form for the offer type and employees can waive coverage.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/SP_Enrollment_Options.htm
Path:
OBE/Benefits Enrollment/Topics/SP_Enrollment_Options.htm
Enter medical waive reasons and employee cost calculations and determine whether to display employer costs for benefit plans during enrollments with the Enrollment Options form.
Click Close to close this form at any time. All unsaved changes will be lost.
To enter enrollment options:
Click Back Office.
From System|Change, select System Parameters.
Click the Actions menu [Image: screenshot] and select Enrollment Options. The Enrollment Options form opens.
Use this option — To define this
Medical Waive Reasons — Reasons for waiving medical insurance (such as other group medical coverage or covered by Medicare) that display in a list when the employee waives healthcare benefits for a spouse.
Medical Waive Reasons (Spanish) — Reasons for waiving medical insurance in Spanish.
Valid Waiver Reason — Indicates whether the reason is valid (Yes or No (default). When activating pending enrollments, all waiver reasons (valid or invalid) are included in the total waived employee count.
Life Events - Documents Required — The documents to use for life event enrollments. Documents entered in this panel are shown in the Specify Document(s) list in Life Event Maintenance where they can be selected to include in life event workflow codes.
Life Events - Documents Required (Spanish) — The documents to use for life event enrollments in Spanish.
Include Employer Costs in Employee Self-Service — Enables viewing of employer benefit plan contributions by employees during enrollment periods. You can override this setting at the client level in the Client DetailsBenefits tab.
Employee Calculation Based on — Basis for calculating employee costs (Per Month, Per Period). This setting determines how the system calculates employee costs to display for the benefit plan. You can override this setting at the client level in the Client Details>Benefits tab.
Require Approval for Proxy Enrollments — Enables the requirement for administrative approval on proxy enrollments in Benefits Enrollment (PrismHR Benefits Enrollment only.)
Auto post BE/OE enrollments when overlap with OE — Allows the system to automatically create open enrollment records for employees who already have a benefit enrollment record that overlaps with open enrollment.
Allow Actions on Dashboard for Service Provider Users Only — Restrict access to actions on the dashboard to only allow service providers to access the Actions menu.
Allow Edit Dependents in Enrollment Workflow — Allows employees to make changes to their dependents during the Onboarding process and enrollment workflow.
Archive unsubmitted enrollment workflows X days after worfklow end date — Allows clients to automatically archive enrollment workflows after the designated time period. When this option is enabled, records from employees in all employment statuses are archived automatically.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Suspended_Employee_Enrollment_Process.htm
Path:
OBE/Benefits Enrollment/Topics/Suspended_Employee_Enrollment_Process.htm
To manually suspend benefit enrollments for new hires if the benefits setup is not yet finalized for the client, use the Suspended Employee Enrollment Process form.
Note: Note: The New Hire Suspension Process runs automatically once a day; this form allows you to run it on demand.
This process updates employee records, removes the suspended status for employees who are now eligible, and displays the results.
Note: Note: On the System Parameters form, your organization must enter the SUSPENDENH custom feature code for this manual process to work. For more information, see Suspending Benefit Enrollments.
[Image: screenshot]
To launch the suspended employee update process:
Enter the Client for which you want to launch the New Hire Suspension Process. If you leave this field blank, the system runs the process for all clients.
Click Run. When the process is finished, the results display in a form.
[Image: screenshot]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Suspended_Employee_Enrollment_Report.htm
Path:
OBE/Benefits Enrollment/Topics/Suspended_Employee_Enrollment_Report.htm
The Suspended Employee Enrollment Report lists all employees whose enrollments are currently suspended or on hold. (PrismHR Benefits Enrollment only.)
To run the Suspended Employee Enrollment report:
Click Reports.
From Benefits|Report, select Suspended Employee Enrollment Report. The Suspended Employee Enrollment Report form opens.
Enter the Client ID.
Click Run. The report displays information in the following columns.
Column — Description
Client ID — The client ID.
Client Thru Date — The date through which the client’s benefits are available.
Employee Name — The employee’s name.
Employee Thru Date — The next date when the system will review the employee’s suspension. This date automatically advances by one day each time the system determines that the employee record should remain suspended.
Plan ID — The benefit plan in which the employee was enrolled.
Coverage Start Date — The date the employee is first eligible for coverage.
Type — The enrollment type (NextGen or OnHRP).
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/System_Workflow_Grid.htm
Path:
OBE/Benefits Enrollment/Topics/System_Workflow_Grid.htm
To assign workflows to use for enrollments at the system level, use the System Workflow Grid form. You can also assign workflows at the client level. Settings defined at the client level override global settings. For more information, see Assigning Workflows at the Client Level.
The Min # of Overlap days designates the limited amount of time an employee has to complete the open enrollment workflow when the workflow start date plus the Min # of Overlap days extends beyond the open enrollment window. This option is used only in an enrollment workflow overlap scenario.
If the start date is the date the first workflow is submitted, 4/25/19, the system checks the Min # of Overlap days on the grid and adds that number of days to the Start Date Window. It then calculates a date of 4/27/19. The system then checks the End Date Window on the grid.
If the calculated date is greater than the end date on the grid, the system uses the calculated date.
If the end date is in the past, 4/23/19, the system uses the calculated date of 4/27/19 for the workflow end date.
If the dates are equal, 4/27/19, the system uses the calculated date of 4/27/19 for the workflow end date.
If the end date is in the future, 5/3/19, the workflow end date is 5/3/19.
If the Min # of Overlap days is left blank, the system uses the current logic of same length as window dates - the length between start date window and end date window.
Use the Filter Records panel to filter system-level workflows by entering the OE Start Date and OE End Date, then clicking Search.
Use First, Prev, Next, and Last to navigate through the workflow history.
View the total number of records, shown in the lower right-hand corner.
To create a new workflow assignment to use during enrollments:
Click Back Office.
From System|Change, select System Workflow Grid. The System Workflow Grid form opens.
Click Add Row. The Add a New Record panel opens.
Use this option — To define this
Effective Date — The date that the benefits that are offered in the workflow become effective for an employee. For example if the enrollment elections start coverage on 06/01/2018,enter that date. Required.
BE Workflow — The BE Workflow to use for benefit enrollments. The list displays all active workflows in the Workflow Library.System Onboarding Workflow Grid
BE Open Window Length — The number of days from the Effective Date during which an employee can enroll in benefits.
Min # of Overlap days — The Min # of Overlap days designates the limited amount of time an employee has to complete the open enrollment workflow when the workflow start date plus the Min # of Overlap days extends beyond the open enrollment window. This option is used only in an enrollment workflow overlap scenario.
AE Workflow — The Anytime Enrollment workflow.
OE Workflow — The OE Workflow to use for open enrollments. The list displays all active workflows in the Workflow Library.
OE Start Date and OE End Date — The start and end dates to use for open enrollments. The OE Start Date is the first day that employees can review and make elections during the Open Enrollment period. The OE End Date is the last day that the employees can submit elections. The OE Start Date and OE End Date must fall before the workflow Effective Date.
WF End Date — The last day that benefits are active and cover the employee. If the Effective Date for the benefits is 06/01/2018, the WF End Date is 05/31/2019, the End Effective Date. This option is required and cannot be earlier than the OE End Date.
Audit — Click to display audit logs. The system displays a message if no logs are available.
Click Save. The record displays in the records table.
If needed, assign additional workflows.
Click Save.
You use an existing workflow assignment as the basis of a new one by copying it and assigning a new effective date. For example, you can copy the information from a previous year to use for the current year.
To copy a workflow assignment:
In the System Workflow grid, click Copy New. The Copy an Existing Record panel opens.
Enter the Effective Date for the record to copy.
Enter the New Effective Date for the record to create.
Click Save. The record maintains the settings from the original record and displays the new effective date in the Records panel.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Update-Employee-Name-Address-Case.htm
Path:
OBE/Benefits Enrollment/Topics/Update-Employee-Name-Address-Case.htm
This process converts employee names and/or addresses to either all upper case or proper case (the first letter of each word is in upper case). The data changed depends on the New Hire Proper Case Conversion setting in System Parameters. You can change the case for Employee Name, Employee Address, or both fields.
Note: Note: This form does not use Client Access Group Security.
To update the case of the employee name and address:
Click Back Office.
From System|Action, select Update Employee / Name Address Case.
Click Update Case. The following occurs:
If set to Employee Name, the system converts all Employee Names to uppercase.
If set to Employee Address, the system converts all Employee Addresses to uppercase.
If set to Both Name and Address, the system converts all Employee Names and Addresses to uppercase.
The system displays a job progress window and processes the required employees. It lists a running count of the number of employees processed. For example, Processing 1/500 employees.
Click Close when complete.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/View_Web_Enrollments_History.htm
Path:
OBE/Benefits Enrollment/Topics/View_Web_Enrollments_History.htm
To view an employee’s enrollment activity during enrollments, use the Web Enrollments History form.
The information you can view includes:
The dates and times the employee viewed a workflow, as well as each form in the workflow.
The effective dates, plan types (tiers), premium rates, and coverage details for each benefit plan viewed by the employee.
The benefit plans the employee selected.
Whether the employee waived benefits individually or for a spouse.
If the employee waived benefits for a spouse, the waive reason the employee selected.
To view an employee’s enrollment activity:
Select HR in the menu bar.
From HR|View, select Web Enrollments History. The Web Enrollments History form opens.
Enter the Employee ID.
Click Load. A detailed record of the employee’s enrollment activity displays in the table. You can click Next or Previous to navigate multiple screens of data.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Web_Enrollment_Maintenance.htm
Path:
OBE/Benefits Enrollment/Topics/Web_Enrollment_Maintenance.htm
Use the Web Enrollment Configuration form to extend or customize an employee’s enrollment period. For example, you may need to extend the date for an employee who needs more time to enroll.
To extend or customize an employee’s enrollment period:
The Web Enrollment Configuration form opens.
| For this option… | Define this information… |
|---|---|
| Employee | The ID of the employee. If there is a current enrollment, the enrollment Effective Date, Start Date, End Date, and Workflow name display. Otherwise, these fields remain blank. - If there is a current enrollment, you can change its end date and extend the enrollment period for the employee. All other fields are read-only. - If there is no current benefits or open enrollment, you can create a custom enrollment period for the employee. |
| Field | Description |
|---|---|
| Status Code | The status of a web enrollment, such as Ready to Post. |
| Confirmation # | The confirmation number for a web enrollment. |
| Approval Id | The approval ID for a web enrollment |
| Batch # | The batch number for a web enrollment. |
| Next Overlap Effective Date | The Effective Date of the Next Overlapping Open Enrollment, if applicable. |
To delete the enrollment record, click Delete.
To close the enrollment record without saving changes, click Cancel.
To archive the enrollment record, click Archive. The system displays an alert and prompts you to confirm Yes or No to archive the record.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Web_Enrollments_Bulk_Archive.htm
Path:
OBE/Benefits Enrollment/Topics/Web_Enrollments_Bulk_Archive.htm
To view enrollment records that have passed their end date and archive them as needed, use the Web Enrollments Bulk Archive form.
To sort the records displayed in the table:
To select columns to display or hide:
To select records to archive:
Click Back Office.
Select System|Change > Web Enrollment Bulk Archive. The Web Enrollments Bulk Archive form opens.
Select the records to archive in any of the following ways:
To select records individually, click the check mark in the column next to each record.
To select more than one record, press the Ctrl or Shift key.
To select or clear all records, click the check mark in the header area.
Click Archive Selected Enrollments. The system displays an alert and prompts you to confirm.
Click Yes or No.
If you click Yes, the system archives the record(s).
If you click Archive Selected Enrollments but no enrollments are selected to archive, the system displays the No Enrollments Selected alert. Click OK to return to the form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Web_Enrollments_Bulk_Update.htm
Path:
OBE/Benefits Enrollment/Topics/Web_Enrollments_Bulk_Update.htm
To assign a new workflow to active enrollments, use the Web Enrollments Bulk Update form. You can apply this change to one client, or to all clients.
Employees who have already completed enrollments do not receive workflow updates made in this form. If you want these employees to enroll again using the new workflow, you must manually assign the new workflow to them using the Web Enrollment Configuration form.
To assign a new workflow to active enrollments:
Click Back Office.
Select System|Change > Web Enrollments Bulk Update. The Web Enrollments Bulk Update form opens.
For this option — Define this information
Client ID — The Client ID. If blank, the update applies to all clients.
Enrollment Type — The Enrollment Type for the workflow to replace (Benefits Enrollment, Open Enrollment).
In Progress Workflow — The In Progress Workflow to replace. The list includes active workflows assigned the Enrollment Type selected.
Replacement Workflow — The Replacement Workflow. The list includes all active workflow revisions in your workflow library.
Click Update. The system displays an alert notifying you of the number of employee records to be affected by the change and prompts you to confirm.
Click Yes to save the settings.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Benefits%20Enrollment/Topics/Web_Enrollments_Date_Update.htm
Path:
OBE/Benefits Enrollment/Topics/Web_Enrollments_Date_Update.htm
To modify the start and end dates on active enrollment workflows, use the Web Enrollments Date Update form. You can limit the update to one client or apply it to all clients. You can also limit the update to workflows with a specific start and end date, or select a specific workflow to update.
To change enrollment workflow start and end dates:
Click Back Office.
Select System|Change > Web Enrollments Date Update. The Web Enrollments Date Update form opens.
For this option — Define this information
Client ID — The Client ID. If blank, the update applies to all clients.
Workflow — The Workflow to modify. The list includes all active workflows. If blank, the system applies the update to all active workflows for the client or, if the Client ID is blank, to all clients.
Start Date and End Date — The Start Date and End Date to further filter workflows if needed. The system limits the update to only the active workflows with the specified Start Date and End Date.
Replace matches with — The Start Date and End Date to use in place of the original values. If the updated workflow is for a benefits enrollment, employees whose effective dates are later than the replacement end date are not affected by the update. If the updated workflow is for an open enrollment, employees whose effective dates are earlier than the replacement end date are not affected by the update.
Click Update. The system displays an alert notifying you of the number of employee records that will be affected by the change and prompts you to confirm
Click Yes to confirm the change.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Activating_Onboarding.htm
Path:
OBE/Onboarding/Front_Matter/Activating_Onboarding.htm
The following are required system and client-level settings to activate Onboarding.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Assigning_OB_Workflows.htm
Path:
OBE/Onboarding/Front_Matter/Assigning_OB_Workflows.htm
To assign onboarding workflows at the system and client levels, use the System Onboarding Workflow Grid and the Client Onboarding Workflow Grid.
You can access the forms by selecting the System or Client links at the top of both forms.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Configuring_Client_Settings.htm
Path:
OBE/Onboarding/Front_Matter/Configuring_Client_Settings.htm
The following are required client‑level settings for Onboarding. For more information, see the Client Administration User Guide.
To configure the required client‑level settings:
Click the Client menu.
From Client|Change, select Client Details. The Client Details form opens.
Select the Control tab.
In the Enrollment/Onboarding Controls panel, complete the following fields:
| Field | Select… |
|---|---|
| Electronic Enrollment | NextGen: Employees complete their enrollment in Benefits Enrollment. |
| Electronic On‑boarding | - Always: Employees always complete their onboarding online. - Prompt: The New Hire form prompts you to indicate whther the employee completes the onboarding process online, or whether you enter the employee information on the New Hire form. Never is for clients that do not use Onboarding. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Configuring_Electronic_Pay_Stubs.htm
Path:
OBE/Onboarding/Front_Matter/Configuring_Electronic_Pay_Stubs.htm
Electronic pay stubs enable employees to receive their pay stubs electronically through Employee Portal (EP) instead of in a paper format. For employees setting up their direct deposit in Onboarding, the pay stub format options are dependent on PrismHR configuration.
The state rules regarding electronic pay stubs are not pre‑configured and must be set up in PrismHR on the State Rules form.
To open State Rules:
Click Back Office.
From System|Change select States Rules. The State Rules form opens.
In the State Rules panel, see Electronic Pay Stubs Allowed.
Option — Description
Allowed, Employee may not un‑enroll — The state allows electronic pay stubs. You can configure direct deposit to disable employees from un‑enrolling.
Allowed, Employee may un‑enroll — The state allows electronic pay stubs. You can configure direct deposit to enable employees to un‑enroll.
Not allowed by the State — The state does not allow electronic pay stubs.
Allowed, Employee must Opt‑In — The state allows electronic pay stubs, but employees must select electronic pay stub when setting up their direct deposit. Employee defaults to paper pay stubs.
State rules control the pay stub format options shown to employees during onboarding and their default values. You can override this configuration at the client level found on the Client Details form Other tab.
To open Client Details:
Select the Client menu.
From Client|Change select Client Details. The Client Details form opens.
Select the Other tab. The Client Other form opens.
In the Other Options panel, see Electronic Pay Stubs.
Option — Description
Not Used — Electronic pay stubs are not used. All pay stubs are paper.
Employee may not un‑enroll — Employees are enrolled in electronic pay stubs by default and cannot un‑enroll.
Employee may un‑enroll — Employees are enrolled in electronic pay stubs by default, but can un‑enroll when setting up their direct deposit.
The pay stub format options shown to employees during onboarding and their default values depend on the configuration between the State Rules Electronic Pay Stubs Allowed option and the Client Other Electronic Pay Stubs option. These values also affect the Un‑Enroll in Electronic Pay Stub option on the Employee Details form Other tab. The following table details the relationship between the various options.
| State Rules | Client Details - Other tab | Onboarding - Direct Deposit Form | Onboarding - Direct Deposit Form | Employee Details - Other tab |
|---|---|---|---|---|
| Electronic Pay Stubs Allowed | Electronic Pay Stubs | Choose your Pay Stub format dialog box | Default Pay Stub Format | Un‑Enroll in Electronic Pay Stub |
| Allowed, Employee may not un‑enroll | Employee may not un‑enroll | Hide | N/A | Disabled |
| Allowed, Employee may not un‑enroll | Employee may un‑enroll | Show | Electronic | Disabled |
| Allowed, Employee may un‑enroll | N/A | Show | Electronic | Disabled |
| Not allowed by the State | N/A | Hide | N/A | Enabled |
| Allowed, Employee must Opt‑In | N/A | Show | Paper | Enabled |
| N/A | Not Used | Hide | N/A | Enabled |
| N/A | N/A | Hide | N/A | Enabled |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Configuring_System_Settings.htm
Path:
OBE/Onboarding/Front_Matter/Configuring_System_Settings.htm
The following are required system‑level settings in Onboarding.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Cross_Hiring_EEs.htm
Path: OBE/Onboarding/Front_Matter/Cross_Hiring_EEs.htm
A cross hire employee works for multiple clients under the same service provider. If the system identifies a new hire employee as a cross hire and their employee information does not match the existing employee information, the system generates a conflict. Cross hire conflicts prevent the system from launching new hire onboarding workflows. The following outlines how the system identifies cross hire employees, checks for cross hire conflicts, and enables you to review or resolve those conflicts:
When entering a new hire, if the Social Security number (SSN) matches the SSN of an existing employee, the system identifies the employee as a cross hire.
After identifying the employee as a cross hire, the system checks for conflicts to determine if the new hire is the same person as the existing employee. However, system does not check for cross hire conflicts when a service provider enters a new hire on the New Hire form. For more information on these exceptions, see Service Providers and Worksite Managers.
If cross hire conflicts exist, they display on the Review Cross Hire Conflicts form.
The following details how the system checks for cross hire conflicts.
To identify cross hire conflicts, the system verifies that the new hire is the same person as the existing employee with three key fields - First Name, Last Name, and Date of Birth. If any of these values do not match, the onboarding workflow does not launch, the system creates a conflict, and an email sends to the service provider assigned to the client Human Resources and Payroll accounts (Client Details > Accounts tab). A message also displays in My Messages. Service providers must resolve the conflict on the Review Cross Hire Conflicts form.
The system identifies cross hire conflicts when launching their onboarding workflow in the following scenarios:
Entering a new hire on the New Hire form. See Manually Entering a Cross Hire New Hire.
Importing a new hire with the Expanded Employee Import. See Importing Cross Hires with the Expanded Employee Import.
Importing a new hire with the API Import. See Importing Cross Hire Employees with the API Import.
Launching a new workflow for a new hire with the Launch New Workflow action on the Workflow Maintenance form. Launching a New Workflow for a Cross Hire New Hire.
In some cases, when onboarding a new hire to more than one client at the same time, the system may not identify a cross hire until a workflow launches and the new hire is completing their onboarding forms. In this scenario, the system performs a cross hire check on the Form I-9 Section 1 and the Employee Information form. See Employee Submits Forms in Onboarding Workflow.
When you enter a new hire on the New Hire form, the system identifies whether the new hire is also a cross hire. The system supports entering cross hires for the following user types:
Service providers
Worksite managers
Worksite trusted advisors
For service providers, the following table details the results of saving a new hire employee that is also a cross hire. The results differ when the employee is set up for Onboarding.
| Onboarding? | Result |
|---|---|
| Yes | - Employee fields populate. - The system does not check for a cross hire conflict. - Onboarding workflow launches. |
For worksite managers, the following tables detail the results of saving a new hire employee that is also a cross hire.
| Onboarding? | Result |
|---|---|
| Yes | - Employee fields do not populate. - The system checks for a cross hire conflict. - If a conflict does not exist, the onboarding workflow launches. - If a conflict exists, the conflict displays in the Review Cross Hire Conflicts form and the onboarding workflow does not launch. |
For worksite trusted advisors, the following table details the results of saving a new hire employee that is also a cross hire. The results differ when the employee is set up for Onboarding.
| Onboarding? | Result |
|---|---|
| Yes | - Employee fields do not populate. - The system checks for a cross hire conflict. - If a conflict does not exist, the onboarding workflow launches. - If a conflict exists, the conflict displays in the Review Cross Hire Conflicts form, and the onboarding workflow does not launch. |
The Expanded Employee Import in HRPyramid System Administration > Process > Conversion Processing > Expanded Employee Import) supports importing and converting cross hire employees set up for Onboarding into the backend system of PrismHR. First, you must import the employees (Expanded Employee Import > Import Employees).
Note: Note: To import an employee as a cross hire, you must include the employee ID in column GQ (field 199). For more information, see Expanded Employee Import File Specifications on the Customer Resource Center.
The import process loads an external file and creates IMPORT.EMPLOYEE records you can import into the Employee Master file. During the import, the system checks for cross hire conflicts. If a conflict exists, a warning displays in the import report. You can fix it by correcting the data in the external file. After importing, you must convert the employees (Expanded Employee Import > Convert Employees).
The conversion process moves valid employees from the IMPORT.EMPLOYEES file into the Employee Master file. If a conflict exists, the conflict displays on the Review Cross Hire Conflicts form, and their onboarding workflow does not launch. If a conflict does not exist, the system launches their onboarding workflow.
The API Employee Import supports importing cross hire employees set up for Onboarding into the backend system of PrismHR. First, you must import the employees.
Note: Note: To import an employee as a cross hire, you must include the employee ID.
The import process checks the data and creates a Data Import Errors Report to identify any data issues. If a cross hire conflict exists, a warning displays in the import report. You can fix the conflict by correcting the data. After importing, you must commit the employees.
The commit process updates the data in PrismHR. If a conflict exists, the conflict displays on the Review Cross Hire Conflicts form, and their onboarding workflow does not launch. If a conflict does not exist, the system launches their onboarding workflows.
When you launch a new workflow on the Workflow Maintenance form, the system identifies whether the new hire is also a cross hire. If a cross hire conflict does not exist, the onboarding workflow launches. If there is a cross hire conflict, it displays on the Review Cross Hire Conflicts form, and the onboarding workflow does not launch.
When an employee submits forms in their onboarding workflow, the system checks for cross hire conflicts at three points. When the employee:
Clicks Back or Next on the Form I‑9 Section 1, Employee Information page.
Clicks Back or Next on the Employee Information form, Personal Information page.
Clicks Save and Continue on the Employee Information form, Emergency Contacts page.
If a conflict exists, the system informs the employee they cannot proceed because either the First Name, Last Name, or Date of Birth does not match what is already in the system. The employee can resolve the conflict by entering the correct values. If the employee resolves the conflict, the system removes it from the Review Cross Hire Conflicts form and sends an email indicating that the conflict is resolved to the service provider. A message also displays in My Messages. If the employee cannot resolve the conflict, the service provider can correct it on the Review Cross Hire Conflicts form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Launching_New_Hire.htm
Path:
OBE/Onboarding/Front_Matter/Launching_New_Hire.htm
To enter new hire employee information into PrismHR, use the New Hire form (located in the HR menu under HR|Action). After entering the employee information, the system displays the prehire ID when you click Save. The new hire can then register and log in to Onboarding to complete the onboarding process.
If the new hire is a cross hire employee and the First Name, Last Name, Birth Date, and Social Security Number values do not match values on the employee record from the original client, the system creates a conflict. The system also creates a prehire record for the new hire without an Onboarding workflow. To review and manage cross hire conflicts, see Managing Cross Hire Conflicts.
For more information about hiring a new employee, see the Human Resources User Guide.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Maintaining_Workflow_Actions.htm
Path:
OBE/Onboarding/Front_Matter/Maintaining_Workflow_Actions.htm
Use the Workflow Maintenance form to perform onboarding‑related workflow actions,.
To complete an action on the Workflow Maintenance form:
Click Back Office.
From System|Change select Workflow Maintenance. The Workflow Maintenance form opens.
In Workflow Type, select Onboarding.
Note: Note: If you select Benefit Enrollments as a workflow type, the system displays a message that it is not currently supported.
| Action | Description |
|---|---|
| Reopen Workflow | Shows new hires with: - Completed onboarding workflows - A Form I‑9 Section 1 in their workflow with the Form I‑9 Section 2 either complete or in progress. See Reopening a Workflow. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Setting_up_Chapter_Notifications.htm
Path:
OBE/Onboarding/Front_Matter/Setting_up_Chapter_Notifications.htm
The Notification Templates and Notification Recipients forms enable you to set up notifications you want to send and to specify recipients for notifications.
For notifications to work, you must first set up Email Services. For more information, see the System Administration Guide.
You can set up content for notifications in the Notification Templates form. For more information, see Setting Up Notification Templates (Onboarding).
You can designate recipients for notifications in the Notification Recipients form. For more information, see Setting Up Notification Recipients (Onboarding).
Notifications are available in the Workflow Library where you can add them to workflows. For more information, see Creating a Workflow for Onboarding.
To specify how often the system should send the notifications, to resend time-based notifications if needed, and to stop or start the notifications engine, use the Notification Control Panel. For more information, see Managing the Notification Control Panel (Onboarding).
There are two possible circumstances that can result in notifications not reaching the recipient:
The email address is not entered correctly (for example, it is entered as @example.com instead of jsmith@example.com). PrismHR logs this error but it is not accessible to the user. Users should contact the PrismHR Customer Support Team.
The email address is entered correctly, but is otherwise not deliverable (for example, the email address is no longer active). In this case, PrismHR simply sends the email. There is no error log, and in most cases, there is no way to know that it was not received. Many email servers are configured not to send notifications of undeliverable emails.
You can track notifications by setting up the Notification Recipients form to send copies of all notifications to an administrator in your organization. This also enables you to forward notifications.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Setting_Up_Forms_Workflows.htm
Path:
OBE/Onboarding/Front_Matter/Setting_Up_Forms_Workflows.htm
A workflow is essentially a wizard—a script that presents employees with a series of forms to guide them through well-defined and highly customizable steps during onboarding and benefit enrollments.
If you plan to include any media items in a workflow, such as documents or images, in forms or workflows, upload them to Document Management before you create the forms in the Form Library.
In the Form Library, you can create custom versions of the forms or use the prebuilt versions provided with their default language and settings. Prebuilt forms display in bold.
After you create the forms, you can use them as components to create workflows in the Workflow Library.
Use the following libraries to manage documents, forms, and workflows for onboarding.
Library — Description
Document Management — Upload and maintain documents to use when creating forms (graphic files for logos, PDF files containing onboarding information, and so on).
Form Library (Onboarding) — Configure forms to include in a workflow. PrismHR provides prebuilt forms that you can use as templates to create new forms. You can also build your own custom forms.
Workflow Library (Onboarding) — Create workflows using forms from the Forms Library as components.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Working_with_Data_Issues.htm
Path:
OBE/Onboarding/Front_Matter/Working_with_Data_Issues.htm
During the onboarding process, data‑related problems automatically generate emails and messages sent to service providers describing the issues, and what must be done to correct them.
You can identify the set of recipients in PrismHR.
To identify the set of recipients:
Click Client.
From Client|Change select Client Details. The Client Details form opens.
Click the Account tab.
In the Account Assignments panel, the set of recipients includes those assigned as the Payroll and Human Resources employee representative.
If… — The system sends the email and message to…
The representative for each role is different — Both representatives receive an email and message.
The same representative is assigned to both roles — Only one email and message are sent to that individual.
A Payroll and Human Resources representative does not exist in Account Assignments — The email and message are delivered to the service provider assigned as the Human Resources Representative and Payroll Manager Account Management Role on the Users form.
Emails are sent directly to their email address and messages appear in My Messages. These scenarios include:
Issue — Solution
On the Form I-9 Section 1 or the Employee Information form, if an employee enters a key field (First Name, Last Name, DOB, or SSN) that does not match the value stored in PrismHR, an error message displays and the employee is unable to save changes. — The service provider must review the message to identify the mismatched values. If the employee entered the incorrect value, the service provider must inform the employee to enter the correct value. If the incorrect value is in PrismHR, the value must be corrected in Workflow Maintenance using the Edit New Hire action.
On the Form I‑9 Section 1, if an employee attempts to submit the form with no I‑9 Section 2 approver in the system, an error message displays and the employee is unable to submit the form. Employees must contact their employer. — The service provider must assign an I‑9 Section 2 approver on the Approval Policies form in PrismHR. For more information on approvals, see the Human Resources User Guide. Once an I-9 Section 2 approver exists, the employee can submit the Form I‑9 Section 1 and continue with the onboarding process.
On the Employee Information form, if an employee enters their resident address manually, a GeoCode is not stored. Without a GeoCode, employees cannot receive pay. This must be corrected for a payroll to be run for this employee. — The service provider must go to the Employee Details Address tab to enter the employeeGEO Code under Resident Address.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Working_with_OB_Dashboard.htm
Path:
OBE/Onboarding/Front_Matter/Working_with_OB_Dashboard.htm
The PrismHR Dashboard provides quick access to company information and relevant features. The information shown in the Chart and List sections of the Perspective panel reflects the client selected.
To view onboarding tasks within Onboarding, in the Chart section of the My Perspective panel, select Onboarding Tasks by Status from the list.
[Image: screenshot]
The Chart displays onboarding tasks and their statuses (Not Due, Due Today, Past Due, and Completed) for a date range. The Chart includes the following filters:
The Show list enables you to select the date range you want to view (Active, Last 7 Days, Last 30 Days). The Chart and List display tasks in the date range.
The Tasks list enables you to select which type of task you want to view in the Dashboard (I-9 Section 1, Employee Information, I-9 Section 2, All Other Forms, or Approve Paycard). The Chart and List display the task selected.
The List section displays information about new hire tasks. The number of tasks that display is determined by the filters selected in the Chart section of the My Perspective panel.
| Field | Description |
|---|---|
| New Hire (Search) | Search for a new hire record for the task selected. Information displayed in the List is relevant to the Task selected. |
| New Hire | The person being onboarded. |
| Performer | The person performing the tasks for the person being onboarded. |
| Forms | The Form Symbols for all custom forms display in the workflow when All Other Forms is selected in the Task list. |
| Due Date | The date the task is due. |
| Submit Date | The date the task was submitted. |
| Status | Status of the workflow (Not Due, Due Today, Past Due, Completed) |
| Actions | The reminders to send about an employee’s onboarding workflow. Reminders sent depend on the task selected in the Tasks list. - I-9 Section 2: Send approval-pending reminders to I-9 Section 2 approvers. - I-9 Section 1, Employee Information, All Other Forms: Send reminders to employee’s with incomplete forms in their workflow. |
Select a new hire from the list to view the New Hire Task List.
[Image: screenshot]
| Field | Description |
|---|---|
| Tasks performed by | The new hire completing the tasks. |
| Workflow Status | The status of the new hire workflow. - Not Started: Forms in the workflow have not been started - In Progress: At least one form has been started - Complete: All forms, Including the I‑9 Section 2, are complete |
Export dashboard data in CSV format.
Related Topic
Onboarding Dashboard for Worksite Managers
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Front_Matter/Working_with_Pay_Card_Dir_Dep_Accts.htm
Path:
OBE/Onboarding/Front_Matter/Working_with_Pay_Card_Dir_Dep_Accts.htm
Onboarding supports the use of pay cards for direct deposit. Pay cards offer employees without a bank account an alternative to paper paychecks that can be lost or stolen.
To use pay card direct deposit accounts, you must configure system‑level and client‑level settings in PrismHR.
To configure the financial institution used for pay cards:
Click Back Office.
From System|Change select Bank Routing. The Bank Routing form opens.
Enter the Routing Code for the financial institution (also known as the transit number). The remaining fields populate automatically.
To indicate that your organization uses the account for pay cards, select PayCard (Automove).
[Image: screenshot]
To define the default pay card for all clients at the global level, use the System Parameters form.
To add pay card accounts in System Parameters:
Click Back Office.
From System|Change select System Parameters. The System Parameters form opens.
[Image: screenshot]
In Pay Card Account, enter a valid pay card account number, or select the link to choose from a list. Values in the list are defined on the Bank Routing form (see Bank Routing for Pay Cards).
Click Save.
To establish the pay card account used by the client, use the Client Details form Account tab.
To add pay card accounts in Client Details:
From Client|Change select Client Details. The Client Details form opens.
Select the Account tab.
[Image: screenshot]
In Pay Card Account, enter a valid pay card account number, or select the link to choose from a list. Values in the list are defined on the Bank Routing form (see Bank Routing for Pay Cards).
Select Save.
When an employee selects Pay Card as a direct deposit account in Onboarding, the account number is assigned to the employee via a pay card account approval in PrismHR.
Pay card approval policies can be set up at the system level using the Global Approval Policies form or the client level using the Approval Policies form.
For more information about setting up approval policies at the system level, see the System Administration Guide or Approvals Guide. For more information about setting up approval policies at the client level, see the Human Resources User Guide or Approvals Guide.
To define pay card account approvals by service type at the global level, use the Global Approval Policies form.
To assign system-level pay card account approvers:
Click Back Office.
From System|Change select Global Approval Policies. The Global Approval Policies form opens.
[Image: screenshot]
In Service Type, select Professional Employer.
In Approval Type, select Pay Card Account.
In HR Role or A/M Role, select a User ID and designate the user as a Pay Card Account Approver. For more information about user role types, see the System Administration User Guide.
Click Save.
To define pay card account approvals by service type at the client level, use the Approval Policies form.
To assign client-level pay card account approvers:
[Image: screenshot]
In Approval Type, select Pay Card Account.
In HR Role or A/M Role, select a User ID, and permit them as a Pay Card Account Approver. For more information about user role types, see User Roles in the System Administration User Guide.
Click Save.
After users create their direct deposit pay card account, the system creates an approval and assigns it to designated approvers in PrismHR. The approval is used to assign the pay card account number. Use the Approvals Pending form to select a pending pay card account approval.
To open the form, from Client|Action select Approvals Pending.
[Image: screenshot]
Approvals in the Approvals Pending (Available to You) panel are approvals available to multiple designated approvers.
[Image: screenshot]
To select a pay card account approval, use the Approvals Pending (Assigned to You) panel. The approval is used to assign the pay card account number.
[Image: screenshot]
In Pay Card Account, enter the employee pay card account number. This is the account number on the pay card you are providing to the employee.
To save the pay card account number, click Apply.
Note: Note: If an employee removes the pay card account from their direct deposit during the approval process, an alert message displays informing the designated approvers that their approval is no longer necessary.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Adding_Form_Library_Fields_OB.htm
Path:
OBE/Onboarding/Topics/Adding_Form_Library_Fields_OB.htm
When creating a custom form, construct the layout using fields from the Field Type list on the Edit Custom Form. You must configure field types used on the form.
To add fields to a custom form:
Some field types are editable. For example, Checkbox is an editable field type since the user can enable or disable the checkbox on the form.
To open the Field Details panel and configure field types, select Configure on the field type. Field parameters vary.
Click Save.
The following table describes the types of fields available in the Form Library. It also describes any additional parameters required for each field.
Note: Note: If additional languages are configured on your system, they will display as options for these field types. For example, if Spanish is the preferred language, the File Hyperlink form will have an English and a Spanish field label.
| Field | Description |
|---|---|
| Text Area | Creates a field where employees can enter multiple lines of information. Additional Options: - Field Value: The default value to display in the field. - Field Constraints: The constraints for the data in the field: alpha, alpha-numeric, date, decimal, email, phone number, whole number, zip/zip+4, ssn. - The minimum and maximum characters to enter in the field. - Required: Whether data is required for the field. Yes or No. - Disabled: Whether the field is disabled. Yes or No. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Approving_Forms_I-9.htm
Path: OBE/Onboarding/Topics/Approving_Forms_I-9.htm
When an onboarding workflow contains the Form I-9, there must be a Form I-9 approval.
For Onboarding, you must set up a user as an I-9 Approver. Employees are unable to submit their Form I-9 Section 1 without an I-9 Section 2 approver. The I-9 Section 2 approval is not created unless an approver exists. For more information, see the System Administration Guide.
Note: Note: If E-Verification is enabled for an employee, it is flagged after Form I-9 Section 2 is completed.
The user set up with this role must approve the I-9 Forms for new hires to complete the onboarding process. For more information about processing approvals, see the Human Resources User Guide.
After the new hire submits the I-9 Section 1, an I-9 Section 2 approval is created, and the approval displays in the approval queue of the Approvals Pending form in PrismHR. The approver can select one of the following options:
Deny the Form I-9 Section 1
Complete and submit the Form I-9 Section 2
Return the approval to the queue for another approver to complete
For more information about pending approvals, see the Human Resources User Guide or Approvals Guide.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Assigning_Workflows_Client_Level_OB.htm
Path:
OBE/Onboarding/Topics/Assigning_Workflows_Client_Level_OB.htm
Use the Client Onboarding Workflow Grid form to assign a workflow to Onboarding at the client level.
To access this form:
Click Back Office.
From System|Change, select Client Onboarding Workflow Grid.
Existing onboarding workflows display in the records table. You can:
View workflows for a specific client by entering the Client ID or the Client Name, then clicking Search. You can also select Search without entering client information to view workflows for all clients.
Select a different workflow to use in a record from multiple Workflow drop-downs (New Hire, Rehire, Take On).
Modify record settings for the Window Length by clicking the link.
Copy a record to a new Effective Date by clicking Copy.
To enter a new onboarding workflow assignment:
Click Back Office.
From System|Change, select Client Onboarding Workflow Grid. The Client Onboarding Workflow Grid form opens.
Click Add. The Add Workflow Effective Date form opens.
Complete the following fields:
| Field | Action |
|---|---|
| Client Id | Enter the client ID. The Client Name displays. This field is required to save the workflow. |
| Workflow Effective Date | Enter the date when onboarding begins. This field is required to save the workflow. |
| New Hire Workflow | Select the workflow you want to use for a New Hire from the drop-down. The drop-down displays all active Onboarding workflows in the Workflow Library. This field is required to save the workflow. For New Hire workflows, the Client Start Date and the Employer Start Date are the same. |
| Rehire Workflow | Select the workflow you want to use for a Rehire from the drop-down. The drop-down displays all active Onboarding workflows in the Workflow Library. For Rehire workflows, the Last Hire Date is greater than the Original Hire Date. |
| Take On Workflow | Select the workflow you want to use for a Take On from the drop-down. The drop-down displays all active Onboarding workflows in the Workflow Library. For Take-On workflows, the Client Start Date / Original Hire Date is before the Employer Start Date. |
| Window Length | Enter the number of days from the Workflow Effective Date during which an employee can log in and complete their onboarding workflow. The Window Length defines the window for all forms except the Form I-9. The Form I-9 window is as follows: - The Form I-9 Section I is due on the employee hire date. - The Form I-9 Section II is due three (3) days from the employee hire date. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Assigning_Workflows_System_Level_OB.htm
Path:
OBE/Onboarding/Topics/Assigning_Workflows_System_Level_OB.htm
Use the System Onboarding Workflow Grid form to assign a workflow to Onboarding at the system level.
To access this form:
Click Back Office.
From System|Change, select System Onboarding Workflow Grid. [Image: screenshot]
Existing onboarding workflows display in the records table. You can view and modify them as follows:
Use the buttons located at the bottom of the table to navigate through the workflow history in the records table.
View the total number of records in the lower right-hand corner.
Select a different workflow to use in a record from multiple Workflow drop-downs (New Hire, Rehire, Take On).
Modify a record’s setting for the Window Length by clicking the field.
Copy a record to a new Workflow Effective Date by clicking Copy in the Copy column.
To enter a new onboarding workflow assignment:
Click Add to open the Add Workflow Effective Date form.
Complete these fields as required:
| Field | Description |
|---|---|
| Workflow Effective Date | Date on which the worfklow will be available. This field is required to save the workflow. |
| New Hire Workflow | Select the workflow you want to use for a New Hire from the drop-down. The drop-down displays all active Onboarding workflows in the Workflow Library. This field is required to save the workflow. For New Hire workflows, the Client Start Date and the Employer Start Date are the same. |
| Rehire Workflow | Select the workflow you want to use for a Rehire from the drop-down. The drop-down displays all active Onboarding workflows in the Workflow Library. For Rehire workflows, the Last Hire Date is greater than the Original Hire Date. |
| Take On Workflow | Select the workflow you want to use for a Take On from the drop-down. The drop-down displays all active Onboarding workflows in the Workflow Library. For Take-On workflows, the Client Start Date / Original Hire Date is before the Employer Start Date. |
| Window Length | Starting on the day of hire, this is the number of days an employee has to complete the onboarding process. The Window Length defines the window for all forms with the exception of the I-9 Form. The I-9 Form window is as follows: - I-9 Section I is due on the employee’s hire date. This is a preset condition. - I-9 Section II is due three (3) days from the employee’s hire date. This is a preset condition. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Conditional_Notifications.htm
Path:
OBE/Onboarding/Topics/Conditional_Notifications.htm
Conditional notifications are event-based notifications triggered by content in a form field or a business rule. This feature helps clients with custom forms ask questions of an employee, whose Yes response triggers a notification to previously specified recipients. For example, a custom form might ask if employees have received a COVID-19 vaccine.
In the form library, fields need to be identified where these notifications apply. For instance, a new radio button is added with Yes or No options for response.
Additional attributes are needed to trigger a notification for a Form Field Response. Notification triggers are event-based, such as when a workflow is completed. When an employee submits a workflow, conditional notifications are triggered.
A single notification template is allowed for each field type. The user is unable to choose a different notification template per response. There is one chosen template that is sent based on the responses selected. A user can choose multiple responses for sending the notification.
The conditional notifications workflow operates like this:
Notification logic is updated to account for the Send Notification configuration on the field type of a form.
When a trigger is enabled. employees submit a workflow and the system examines the notifications attached to a workflow to determine whether this form has field types that require notification.
If yes, the system then determines if an employee’s response is selected to send a notification.
If yes, the system sends the notification.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Creating_a_Workflow_OB.htm
Path: OBE/Onboarding/Topics/Creating_a_Workflow_OB.htm
Use the Workflow Library form to create workflows for onboarding. You can also use this form to add notifications to send out to employees or groups during onboarding.
You can create a workflow using prebuilt forms. Enter the workflow ID and Name (these are required), select the workflow type Onboarding, and save the workflow.
You can also customize settings, select different process forms, and add additional forms to the workflow. The forms you select display in the navigation menu during onboarding in the same order in which they are arranged.
To create a new workflow:
Click Back Office.
From System|Change, select Workflow Library. The Workflow Library form opens.
Click Create New Workflow. The Create New Workflow form opens.
On the General tab, complete the following:
Field — Action
ID — Enter a unique workflow ID.
Name — Enter a unique workflow name.
Workflow Type — Select Onboarding. The Workflow Type Enrollment is used only to create workflows for Benefits Enrollment.
The Start Date and End Date fields are read only. These dates are set when you submit the workflow.
Click Save. The Process, Forms and Documents, and Notifications tabs are enabled.
Select the Process tab. You can save, change, and retrieve data. Autosave occurs when the drop-down selector is changed.
The following forms are required for all onboarding workflows. If additional languages are configured on the system, these form fields will appear in multiple languages.
Initial Visit
Return Visit
Employee Information
Summary
Submit
The following forms are optional.
Electronic Consent:
When creating a new workflow, the form is enabled by default. You can disable it to not include the form in the workflow.
When editing a preexisting workflow, the form is disabled by default and must be enabled to include in the workflow.
For information on including the Electronic Consent form at the beginning of a workflow, see Including the Electronic Consent Form.
Use the lists to select forms. To edit a form label, click [Image: screenshot] .
Select the Forms and Documents tab.
Add forms and form sets to the workflow by dragging and dropping them from the Available Items panel to the Selected Items panel. Forms in bold are prebuilt forms. If additional languages are configured on your system, both the form title and category title display additional language fields.
Note: Note: The forms included in the workflow display in the navigation menu of Onboarding in sequential order.
You must create notifications and set up recipients to assign them to workflows. For more information about creating notification templates, seeSetting Up Notification Templates (Onboarding). For more information assigning notification recipients, see Setting Up Notification Recipients (Onboarding).
For each notification to attach to the workflow, click Enabled. When a notification is enabled, the Object field is enabled.
Select the Object to apply to the enabled notification. The options available depend upon the notification’s Type and Condition. For more information about these options, see Working with Objects and Tasks for Onboarding Notifications.
Click Save. The Submit Workflow dialog box opens.
When does the change need to go into effect? — Definition
Immediately — The system sets the workflow status to Active and sets the current date as the Start Date. Since there can only be one active version of the workflow, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — The form prompts you to enter a Start Date. The system sets the workflow status to Inactive and changes it to Active on the specified start date.
Save as Draft — The workflow status is set to Draft. The system does not set a Start Date, version, or revision number for the workflow.
Parent Topic
Managing the Workflow Library (Onboarding)
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Creating_Business_Rule_OB.htm
Path:
OBE/Onboarding/Topics/Creating_Business_Rule_OB.htm
To define the name and type of a business rule, use the Create Business Rule form.
To create a business rule:
The Business Rules Library opens.
| Field | Action |
|---|---|
| Business Rule ID | Enter a unique ID. |
| Business Rule Name | Enter a title. |
| Description | Enter a brief description. |
| Workflow Type | Select Onboarding. |
The following global variables are available:
Client Category Code
Employee 1099 Contractor
Employee FLSA Exempt
Employee Gender
Employee Preferred Language
Employee Pay Method
Employee Resident Address State
Employee Employment Type
Employee Employer ID
Employee Worksite Location State
Note: Note: Global-level values are the same across all business rules.
In addition to the global variables, the following client-level variables are available for use:
Client Category Code
Employee 1099 Contractor
Employee Benefit Group
Employee Position Code
Employee Worksite Location Code
Employee Work Department Code
Employee Work Division Code
Note: Note: Client-level values vary for business rule as they depend on the clients selected in the business rule.
You can edit the Business Rule Name. This field is required, and must be unique.
You can edit the Rule Type. If you change the business rule type, a confirmation message informs you that the current expression will be overwritten.
You can edit the rule Description. This field populates with the value defined on the Create Business Rule form.
In the Choose a variable list, select a variable. This applies only to the GlobalRule Type. If using a ClientRule Type, the variable list is read only.
In the Choose Operator list, select an operator.
Equal To: The variable or client ID is equal to the value.
Not Equal To: The variable or client ID is not equal to the value.
To select one or more values, click Choose Value.
You can flag certain global and client level variables as obsolete when used in a business rule expression to prevent further use. Values assigned to these variables do not display in the business rule drop-downs when in use.
For more information on Employee Worksite Location, Employee Work Division Code, and Employee Work Department Code, see the Client Administration User Guide.
For more information on Employee Position Code and Employee Employment Type, see the Human Resources User Guide.
For more information on Employee Benefit Group, see the Benefit Administration User Guide.
Parent Topic
See Managing Business Rules (Onboarding)
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Creating_Custom_Forms_OB.htm
Path:
OBE/Onboarding/Topics/Creating_Custom_Forms_OB.htm
Use the Form Library to create a custom form. When creating a custom form, the fields to include on the form must be added and configured manually.
To create a custom form:
Click Back Office.
From System|Change select Form Library. The Form Library displays.
Click Create New Form. The Create New Custom Form form displays.
Complete the following:
Field — Action
Form ID — Enter a unique ID for the form. Required.
Form Name — Enter a title for the form. Required. PrismHR recommends using spaces, not hyphens. Hyphenated words do not wrap correctly in Onboarding. If additional languages are configured on the system, clicking this field causes a Form Name window to display, where a form name for each language can be entered.
Description — Enter a brief description of the form.
Workflow Type — Select Onboarding. Required.
On the General tab, entries are made automatically in the Form Name field and the Description field based on the information entered on the Create New Custom form. These entries can be edited if necessary.
Field — Action
Form Symbol — Enter a symbol for the form (any two characters A-Z, 0-9). Required.
Business Rules — Click this field to display a list of business rules that can be applied to the form. For more information, see Business Rules Library (Onboarding) . > Note: Note: If a business rule is applied to Form I-9 Section 1, the same business rule must be applied to Form I-9 Section 2.
Form Set — Click this field to display a list of form sets that can be assigned to the form. For more information, see Form Sets (Onboarding).
PDF Integration — Upload PDFs with the capability of mapping them to the custom form. For more information, see PDF Integration.
To modify the form layout:
Select the Layout tab.
From Field Type, drag field types to the layout on the right. Field types are customizable and vary depending on the type of form.
Some field types, such as Textfield, Text Area, Checkbox, Select List, Radio Button, and E-signature, can be edited. Others are read-only. Editable field types allow employees to enter unique data.
Note: Note: If a field type is configured for additional languages, the languages for which the field is available displays in the Languages column.
If PDF integration is used, the PDF Fields list displays. From here, the editable fields extracted from the PDF can be selected for inclusion on the custom form. For more information, see PDF Integration.
Note: Note: When PDF files are uploaded in an additional language, the file’s mappable fields are parsed and compared to the field map of the English PDF file. If there is a mismatch of fields and field IDs with the English field map, it is rejected by the system.
When previewing a form in a different language, text that is not translated displays in red. This can help identify missing translation strings.
When previewing a form with conditional form fields, these conditions should correctly be displayed or hidden when the parent field conditions are changed.
Option — Description
Immediately — The system sets the form status to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the form status to Inactive and changes it to Active on the specified start date.
Save as Draft — The system sets the form status to Draft. The system does not set a Start Date, version, or revision number for the form.
Parent Topic
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Creating_Forms_From_Prebuilt_Forms_OB.htm
Path:
OBE/Onboarding/Topics/Creating_Forms_From_Prebuilt_Forms_OB.htm
To create customized copies of prebuilt forms, use the Form Library. You can edit the default text in the prebuilt form. The text varies depending on the form selected. The rest of the content is prebuilt for you.
To create a new form based on a prebuilt form:
Click Back Office.
From System|Change select Form Library. The Form Library opens.
In the row of the prebuilt form to use (medical, dental, vision, life insurance, and so on), select Duplicate. The Duplicate Form displays.
Enter a New ID and New Name for the form.
Click Duplicate. The Customize Prebuilt Form form opens.
On the General tab in the Form ID field, enter a unique ID for the form. Required.
You can edit the Form Name, Description, and Form Symbol. On the Onboarding Tasks by Status Dashboard, form symbols are used to display a summary view of forms in the workflow. Form symbols allow characters A-Z and 0-9 only.
Note: Note: Business rules and form sets are not available for prebuilt forms.
To preview the form before saving, click Preview Form.
To return to the Form Library without saving changes, click Back to Form Library.
To customize field types, click Configure. Field Type parameters vary. For more information about setting up field parameters and settings, see Adding Form Library Fields.
Click Done and then click Save. The Submit Form dialog box opens and prompts you to specify when the change goes into effect.
Option — Description
Immediately — The system sets the form status to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the status of any prior active version to Inactive and sets the current date as its End Date.
Future Date — You are prompted to enter a Start Date. The system sets the form status to Inactive and changes it to Active on the specified start date.
Save as Draft — The system sets the form status to Draft. The system does not set a Start Date, version, or revision number for the form.
Parent Topic
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Deactivating_Workflow.htm
Path: OBE/Onboarding/Topics/Deactivating_Workflow.htm
On the Workflow Library form, you can deactivate unused workflows giving them an inactive status. You can only deactivate active workflows.
To deactivate workflows:
Click Back Office.
From System|Change, select Workflow Library. The Workflow Library opens.
Using the checkmarks next to workflows in the list, select one or more workflows to deactivate. The system enables the Deactivate button.
[Image: screenshot]
If the workflow is in use, a dialog box displays indicating why you cannot deactivate the workflow. For example, the workflow is in a draft state, it is in use on the Client Workflow Grid, it is a prebuilt or default workflow, and so on.
If the workflow is in use on one or more of the following grids, you must remove the workflow from the grid before deactivating:
System Workflow Grid
Client Workflow Grid
Systen Onboarding Workflow Grid
Client Onboarding Workflow Grid
After deactivating a workflow, it does not show in the system as an available option for configuration.
Click Yes, deactivate.
Click Save.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Deleting_Workflow_OB.htm
Path: OBE/Onboarding/Topics/Deleting_Workflow_OB.htm
The following details how to launch a workflow with the Launch New Workflow action.
To delete a workflow:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
Field — Description
New Hire — The employee’s name.
SSN — The employee’s Social Security Number. The value shown may be masked or hidden depending on settings at the system or client level.
Employee ID — The employee’s ID number.
Employer Start Date — The date the employee started with the employer.
Client Start Date — The date the employee started with the client.
Workflow — The workflow name and version number.
Launch Date — The date the prehire record was created.
Action — Delete: Enables you to delete an onboarding workflow.
If the employee entered data on one or more of the forms in the workflow, a confirmation dialog box warns that the system deletes and cannot recover employee data.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Document%20Set%20Workflow%20Library.htm
Path:
OBE/Onboarding/Topics/Document Set Workflow Library.htm
Instead of creating a form for each document set (and needing to build a new field type), you can add the document set directly to the workflow.
To add a document set to a workflow:
Click Back Office.
From System|Change, select Workflow Library. The Workflow Library form opens.
Create a new workflow or edit an existing workflow.See Creating a Workflow (Onboarding)
Select the Forms and Document tab.
(Optional) Select a filter from the Filter Type drop-down to filter the available forms and sets by type in the Available Items section.
(Optional) Enter a keyword in the Search field to filter the available forms and sets by keyword in the Available Items section.
Review the items in the Available Items section. You can click the column header to sort the items by name or by type.
Drag and drop one or more item from the Available Items section to the Selected Items section.
(Optional) Edit the field label of the item.
| a. | Click the edit button for an item in the Selected items section. |
|---|---|
| b. | Update the field label in the English field or the Spanish field. |
| — | — |
| c. | Click Save to complete the label change. |
| — | — |
(Optional) Click the Remove button for one or more items in the Selected items section to remove the item(s) from the list.
Click Save to save changes to the Forms and Documents tab.
Indicate when the change needs to take effect by selecting one of the following:
Immediately
Future Date and enter a date in the Start Date field
Save as Draft
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Editing_New_Hire_OB.htm
Path: OBE/Onboarding/Topics/Editing_New_Hire_OB.htm
The following details how to edit new hire information using the Edit New Hire action.
To edit new hire information:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
Field — Description
New Hire — The employee’s name.
SSN — The employee’s Social Security Number. The value shown may be masked or hidden depending on settings at the system or client level.
Employee ID — The employee’s ID number.
Employer Start Date — The date the employee started with the employer.
Client Start Date — The date the employee started with the client.
Personal Email — The employee’s personal email address.
Work Email — The employee’s email address with the client.
Action — Edit: Enables you to edit new hire information.
In the Action column, click Edit. The Edit New Hire, Personal Information, Employment Details, Pay Details, and User panels display.
Editing new hire information without an employee record:
If the employee has not submitted their Employee Information form (the employee does not have an employee record in the system), you can edit the following fields:
| Field | Description |
|---|---|
| Work Location | The location where the employee works. When selecting a new location, the New‑Hire Questions form opens. Required. |
| Social Security Number | The employee’s Social Security number. Required. |
| First Name, Last Name, Middle Name | The employee’s first and last name. Required. The employee’s middle name. Configure as required or optional on the Global New Hire Fields and New Hire Optional Fields forms. |
| Date of Birth | The employee’s date of birth. |
| Personal Email, Work Email | The employee’s personal and work email addresses. To send an email indicating that the workflow is launched, click Send “Workflow Launched” Email. The link is disabled if: - The notification is not set up for the Employee recipient - The notification is not enabled on the workflow - The Personal Email and Work Email fields are blank |
Editing new hire information with an employee record:
If the employee has submitted their Employee Information form (creating an employee record in the system), you can edit the following fields:
| Field | Description |
|---|---|
| Social Security Number | The employee’s Social Security number. Required. |
| First Name, Last Name, Middle Name | The employee’s first and last name. Required. The employee’s middle name. Configure as required or optional on the Global New Hire Fields and New Hire Optional Fields forms. |
| Date of Birth | The employee’s date of birth. |
| Personal Email, Work Email | The employee’s personal and work email addresses. To send an email indicating that the workflow is launched, click Send “Workflow Launched” Email. The link is disabled if: - The notification is not set up for the Employee recipient - The notification is not enabled on the workflow - The Personal Email and Work Email fields are blank |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Enabling_Onboarding.htm
Path: OBE/Onboarding/Topics/Enabling_Onboarding.htm
To enable Onboarding, use the Global Configuration form in PrismHR.
Click Back Office.
From System|Change, select Global Configuration. The Global Configuration form opens.
Select Enable Onboarding.
Click Save.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Enabling_Spanish_OB.htm
Path: OBE/Onboarding/Topics/Enabling_Spanish_OB.htm
To help onboard your Spanish-speaking employees, refer to the following:
Viewing Default Forms Translations
Enabling Spanish for the Onboarding Process
Configuring the Custom Forms in the Form Library
Creating a Workflow in Spanish
Working with the Custom Form Library in Spanish
Working with PDFs in Spanish and English
Changing the Language While Reviewing a Form
PrismHR includes default employee-facing forms in Spanish for the onboarding process.
Custom forms are translated by the user (see Configuring the Custom Forms in the Form Library).
[Image: screenshot]
To enable Spanish:
[Image: screenshot]
Click Save.
In the New Hire form, enter the required information and select Spanish in the Preferred Language field.
[Image: screenshot]
Use the Form Library to build custom forms in Spanish.
To use the Form Library:
[Image: screenshot]
Enter the Form ID.
When you click in the Form Name field, the Form Name form displays, Enter Form Name in English and then in Spanish.
Click Save.
Enter the Description and Workflow Type.
[Image: screenshot]
Click Continue.
Enter the Form Symbol in the Form Symbolfield.
[Image: screenshot]
Click Save.
Select when the change needs to go into effect.
[Image: screenshot]
Select Submit Form.
Click Done.
Use the Workflow Library form to manage the workflow.
To use the workflow library:
Go to the Workflow Library form.
Click Create New Workflow.
[Image: screenshot]
The Create New Workflow form displays. Enter the ID, Name, and Workflow type.
Click Save.
Select the Process tab.
[Image: screenshot]
[Image: screenshot]
Click Save.
Select the Forms and Documents tab.
[Image: screenshot]
Note: Form names in the workflow can be in English and Spanish.
Go to the Form Library. Click Create New Form.
Enter Form ID, Form Name, Description, and Workflow Type.
Click Continue.
Select the Layout tab. The Edit Custom Form displays.
[Image: screenshot]
To edit a form, drag the form from the Field Type left column to the Field Label section on the right.
Click Update. The Configure checkbox form displays.
[Image: screenshot]
[Image: screenshot]
Click Done.
Configure the existing form by selecting the pencil icon.
[Image: screenshot]
The Configure checkbox form displays. You can customize the Field Labels in both English and Spanish.
Click Done.
You can configure custom forms in Spanish (including PDFs) in the Form Library.
English: Select Upload English PDF.
Spanish: With Spanish selected, select Upload PDF.
Note: You must select Upload English PDF first and then select Spanish Upload PDF.
[Image: screenshot]
Click Save.
If there is a mismatch of fields, an error message displays when the form uploads. For example:
[Image: screenshot]
While reviewing forms in the Form Library, you can change languages by selecting a language from the Profile drop-down field.
[Image: screenshot]
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Form_I-9_Section1-Employee-Process.htm
Path:
OBE/Onboarding/Topics/Form_I-9_Section1-Employee-Process.htm
To complete Section 1 of Form I-9:
If necessary, the employee can click View Instructions to review instructions for completing Form I-9 directly on the USCIS website.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Generating_PDF_Files_OB.htm
Path: OBE/Onboarding/Topics/Generating_PDF_Files_OB.htm
When a new hire completes and submits a form in their onboarding workflow, a copy of the PDF file stores in the Document Repository and Employee Documents forms in PrismHR.
Note: Note: PrismHR runs a daily process to generate any missing custom form PDF files. This is important for clients that started using Onboarding after the introduction of the custom form PDF generation feature in March of 2019.
To upload and manage documents, use the Document Repository. Documents can include logos and other images, PDFs, spreadsheets, and so on. You can also view PDF copies of submitted forms by employees during their onboarding workflow.
To view employee forms in the Document Repository:
Click Back Office.
From System|Change select Document Repository. The Document Repository opens.
In Classification, select Onboarding. A list of onboarding‑related documents displays.
In Select documents to display, select Employee for Client ID. Then use the search function to select a client. A list of employee documents for the selected client displays.
To view PDF copies of employee submitted forms during their onboarding workflow, use the Employee Documents form.
To view employee forms in Employee Documents:
In the HR menu under HR|Change, select Employee Details. The Employee Details formopens.
In Employee, enter an employee ID or select Employee to choose from a list.
In the Actions menu [Image: screenshot] , select Documents. The Documents form opens.
For more information on the Employee Documents form, see the Human Resources User Guide.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Including_Electronic_Consent.htm
Path:
OBE/Onboarding/Topics/Including_Electronic_Consent.htm
The Form Library and Workflow Library enable you to configure and include an electronic consent form at the beginning of a workflow. In the Form Library, the prebuilt Electronic Consent form provides a template for you to configure. In the Workflow Library, you can include the form in a workflow. The Electronic Consent form displays on the Process tab in the Start Process section.
When creating a new workflow, the form is enabled by default. You can disable it to not include the form in the workflow.
When editing a preexisting workflow, the form is disabled by default and must be enabled to include in the workflow.
When the form is in a workflow, an employee can accept or decline electronic consent during the onboarding process.
| When an employee accepts the Electronic Consent form… | When an employee declines the Electronic Consent form… |
|---|---|
| - The employee can continue to complete additional forms electronically. - A PDF generates and stores in the Document Repository in PrismHR. The PDF is also available in Employee Documents. During onboarding, the employee can download a copy. | - The employee cannot complete onboarding electronically. They must complete onboarding using paper forms. - The employee can edit their electronic consent and select Accept. - A PDF generates and stores in the Document Repository in PrismHR. During onboarding, the employee can download a copy. - With the OBCONSENTDECLINED message template, an email is sent to the service provider of the client with instructions about how to complete the employee onboarding process using paper forms. The set of recipients include those with the Account Management Roles of Human Resource and Payroll Representative in PrismHR. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Including_State-Required_Forms.htm
Path:
OBE/Onboarding/Topics/Including_State-Required_Forms.htm
When including state‑required forms in a workflow (such as the South Carolina Terms of Employment Notice or the Washington D.C. Notice of Hire), you must:
Create the form business rule
Create the form
Enter the state‑required questions
To access form PDFs, see State‑Required Forms for Onboarding on the Customer Resource Center.
The following explains creating the form business rule in the system.
To create the form business rule:
Click Back Office.
From System|Change, select Business Rules Library. The Business Rules Library opens.
Click Create Rule. The Create Business Rule form opens.
Complete the following:
| Use this option… | To define this… |
|---|---|
| Business Rule ID | - CAWage - CaliforniaTheft Notice to Employee (CA Wage) - DCWage - Washington D.C. Notice of Hire — Employment Status and Acknowledgment of Wage Rate(s) (DC Wage) - MNWage - Minnesota Employee notice (MN Wage) - NYWageHourly: Notice for Hourly Rate Employees (NY Wage Hourly) - NYWageSalary: Notice for Exempt Employees (NY Wage Salaried) - SCWage - South Carolina: Terms of Employment Notice (SC Wage) |
Click Next.
Configure the business rule expression as follows:
| Choose A Variable | Choose Operator | Choose Values |
|---|---|---|
| Employee Worksite Location State | Equal To | - California - District of Columbia - Minnesota - New York - South Carolina |
| Choose A Variable | Choose Operator | Choose Values |
|---|---|---|
| Employee FLSA Exempt | Equal To | No |
For the New York Wage (Hourly and Salary), see the additional considerations following this procedure.
Click Done.
Click Save.
After selecting New York for the Employee Worksite Location State , click
[Image: screenshot]
twice to create two additional rows. Configure the business rule expressions as follows.
For the New York Wage Hourly:
| Choose A Variable | Choose Operator | Choose Values |
|---|---|---|
| Employee FLSA Exempt | Equal To | No |
| Employee Pay Method | Equal To | Hourly |
For the New York Wage Salary:
| Choose A Variable | Choose Operator | Choose Values |
|---|---|---|
| Employee FLSA Exempt | Equal To | Yes |
| Employee Pay Method | Equal To | Salary |
The following explains creating the custom form in the system. First, you assign the form identifiers (such as an ID and a name), construct the form layout using PDF field types, and then save it as a draft. Then, after applying the business rule to the draft version of the form, you save and submit the final version.
To create the form:
Click Back Office.
From System|Change, select Form Library. The Form Library opens.
Click Create New Form. The Create New Custom form opens.
Complete the following:
| Use this option… | To define this… |
|---|---|
| Form ID | - CAWage - CaliforniaTheft Notice to Employee (CA Wage) - DCWage - Washington D.C. Notice of Hire — Employment Status and Acknowledgment of Wage Rate(s) (DC Wage) - MNWage - Minnesota Employee notice (MN Wage) - NYWageHourly: Notice for Hourly Rate Employees (NY Wage Hourly) - NYWageSalary: Notice for Exempt Employees (NY Wage Salaried) - SCWage - South Carolina: Terms of Employment Notice (SC Wage) |
Click Continue. The Edit Custom Form opens.
Complete the following:
On the GENERAL tab:
| Use this option… | To |
|---|---|
| Form Symbol | Enter a form symbol: - CA - CA Wage - DC - DC Wage - MN - MN Wage - NY - NY Wage - SC - SC Wage |
On the LAYOUT tab:
| Use this option… | To do this… |
|---|---|
| Field Type | Add Markdown to the form layout. 1. Click Configure. 2. In Field Default Value, enter: 3. Click Done After the markdown field type, add PDF Frame to the form layout. |
Click Save.
In the dialog box, select Save as Draft and click Submit Form. The Form Library opens.
Select the form from the list to open the Edit Custom Form.
In Business Rule, select the appropriate business rule from the list.
Click Save.
In the dialog box, select Save as Immediately and click Submit Form.
On the LAYOUT tab:
Click Configure.
In Field Label, enter Language Group.
In Required, select Yes.
Change Choice1 to English.
Change Choice2 to Not English.
Click Done.
On the LAYOUT tab, add the Copy Of Notice field type to the layout after the PDF Frame.
Click Configure.
In Field Label, enter I Reviewed Copy Of Notice.
In Required, select Yes.
Change Choice1 to Yes.
Change Choice2 to No.
Click Done.
The following explains entering the state‑required questions in the system on both the New Hire Questions and State Rules forms. First, you must enter the state‑required questions on the New Hire Questions form.
To enter the state questions on the New Hire Questions form:
Click Back Office.
From System|Change select New Hire Questions. The New Hire Questions form opens.
Click New Question.
Enter the information found in the following tables.
| Question ID | Question Text | Field Type | Default Value, Dropdown Code | Radiobutton Desc, Dropdown Desc |
|---|---|---|---|---|
| ca_has_written_agreement | Does a written agreement exist providing the rate(s) of pay? | Dropdown | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| ca_all_contained | If yes, are all rates(s) of pay and bases thereof contained in that written agreement? | Dropdown | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| ca_entered_allowance | Allowances, if any, claimed as part of minimum wage (including meal or lodging allowances): | Text | N/A | N/A |
| ca_sick | The following applies to the employee identified on this notice (Select One) | Dropdown | - 1 - 2 - 3 - 4 | - Accrues paid sick leave only pursuant to the minimum requirements stated in Labor Code 245 et seq. with no other employer policy providing additional or different terms for accrual and use of paid sick leave. - Accrues paid sick leave pursuant to the employer’s policy which satisfies or exceeds the accrual, carryover, and use requirements of Labor Code 246. - Employer provides no less than 24 hours (or 3 days) of paid sick leave at the beginning of each 12-month period. - The employee is exempt from paid sick leave protection by Labor Code 245.5. |
| - 1 | ||||
| - 2 | ||||
| - 3 | ||||
| - 4 | ||||
| - Accrues paid sick leave only pursuant to the minimum requirements stated in Labor Code 245 et seq. with no other employer policy providing additional or different terms for accrual and use of paid sick leave. | ||||
| - Accrues paid sick leave pursuant to the employer’s policy which satisfies or exceeds the accrual, carryover, and use requirements of Labor Code 246. | ||||
| - Employer provides no less than 24 hours (or 3 days) of paid sick leave at the beginning of each 12-month period. | ||||
| - The employee is exempt from paid sick leave protection by Labor Code 245.5. | ||||
| ca_extra | Please complete the next question ONLY if you selected “The employee is exempt from paid sick leave protection” in the question above | N/A | N/A | N/A |
| ca_sick_4 | If the employee is exempt from paid sick leave, state exemption and specific subsection for exemption | Text | N/A | N/A |
| Question ID | Question Text | Field Type | Default Value, Dropdown Code | Radiobutton Desc, Dropdown Desc |
|---|---|---|---|---|
| DC_ALLOWANCES | Are any allowances claimed as part of wage? | Radiobutton | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| DC_TIPS_AMOUNT | If tip allowances were taken, enter the amount per hour. | Text | N/A | N/A |
| DC_MEAL_AMOUNT | If meal allowances were taken, enter the amount per meal. | Text | N/A | N/A |
| DC_LODGING_AMOUNT | If lodging allowances were taken, enter the amount per time period (day, week, month, etc). | Text | N/A | N/A |
| DC_OTHER_AMOUNT | If other allowances were taken, enter the amount per time period (day, week, month, etc). | Text | N/A | N/A |
| DC_TIPPED_EMPL | Does this employee participate in a company tip pool? | Radiobutton | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| DC_TIP_POLICY | If this employee participates, what is your Tip Pool Policy? | Text | N/A | N/A |
| DC_BASIS_WAGE | What is the basis of wage payment for this employee? | Dropdown | - MW - LW - LWE - EDW | - Minimum Wage - Living Wage - Living Wage Exempt - Employer Determined Wage Rate |
| - MW | ||||
| - LW | ||||
| - LWE | ||||
| - EDW | ||||
| - Minimum Wage | ||||
| - Living Wage | ||||
| - Living Wage Exempt | ||||
| - Employer Determined Wage Rate | ||||
| DC_PAY_BASIS | What is the pay basis (hourly, shift, week, salary, piece, commission)? | Dropdown | - Hourly - Shift - Weekly - Salary - Piece - Commission | - Hourly - Shift - Weekly - Salary - Piece - Commission |
| - Hourly | ||||
| - Shift | ||||
| - Weekly | ||||
| - Salary | ||||
| - Piece | ||||
| - Commission | ||||
| - Hourly | ||||
| - Shift | ||||
| - Weekly | ||||
| - Salary | ||||
| - Piece | ||||
| - Commission | ||||
| DC_PAID_EXEMPTION | If exempt from overtime which is the Pay Exemption for bona fide? | Dropdown | - Admin - Exec - Prof | - Administrative - Executive - Professional |
| - Admin | ||||
| - Exec | ||||
| - Prof | ||||
| - Administrative | ||||
| - Executive | ||||
| - Professional | ||||
| DC_MULTIPLE_OVERTIME | If there are multiple Rates or Basis, for each basis please list what is the Rate of Pay and Overtime Rate per time period. | Text | N/A | N/A |
| DC_CLASSIFICATION | If prevailing rates apply for this Employee, list all classifications and the prevailing rate of pay for each classification. | Text | N/A | N/A |
| Question ID | Question Text | Field Type | Default Value, Dropdown Code | Radiobutton Desc, Dropdown Desc |
|---|---|---|---|---|
| employee_exempt_status | Is this an Exempt or Non-Exempt employee? | Dropdown | - Exempt - Non-Exempt | - Exempt Employee - Non‑Exempt Employee |
| - Exempt | ||||
| - Non-Exempt | ||||
| - Exempt Employee | ||||
| - Non‑Exempt Employee | ||||
| minimum_wage_exempt | Is this employee exempt from minimum wage? | Dropdown | - Y - N | - Yes - No |
| - Y | ||||
| - N | ||||
| - Yes | ||||
| - No | ||||
| mn_other_exempt | Is this employee exempt from other provisions of Minnesota Statutes 177? | Dropdown | - Y - N | - Yes - No |
| - Y | ||||
| - N | ||||
| - Yes | ||||
| - No | ||||
| exemption_basis | Legal basis for exemption | Text | N/A | N/A |
| hours_before_overtime | Number of hours before overtime is effective for this employee | Text | N/A | N/A |
| allowances_claimed | Allowances claimed by this employee | Text | N/A | N/A |
| amount_claimed_per_meal | How much is this employee entitled to per lunch (if Applicable)? | Text | N/A | N/A |
| lodging_allowance_per_day | How much lodging allowance is this employee entitled to per day? (if Applicable) | Text | N/A | N/A |
| sick_leave | Is this employee eligible for a sick leave? | Dropdown | - Y - N | - Yes - No |
| - Y | ||||
| - N | ||||
| - Yes | ||||
| - No | ||||
| paid_vacation | Is this employee eligible for a paid vacation? | Dropdown | - Y - N | - Yes - No |
| - Y | ||||
| - N | ||||
| - Yes | ||||
| - No | ||||
| other_paid_time_off | Does this employee have other paid time off? | Dropdown | - Y - N | - Yes - No |
| - Y | ||||
| - N | ||||
| - Yes | ||||
| - No | ||||
| benefits_accrual_basis | Benefits for this employee are accrued per: | Dropdown | - YEAR - MONTH - PAY PERIOD - HOUR | Benefits accrue per: - Year - Month - Pay Period - Hours Worked |
| - YEAR | ||||
| - MONTH | ||||
| - PAY PERIOD | ||||
| - HOUR | ||||
| - Year | ||||
| - Month | ||||
| - Pay Period | ||||
| - Hours Worked | ||||
| terms_of_benefits | What are terms of benefits Use? | Text | N/A | N/A |
| wage_deduction | Deductions to be made from employee’s pay | Text | N/A | N/A |
| other_employment_information | What, if any, are the other information related to this new hire? | Text | N/A | N/A |
| date_of_first_pay | This employee’s first day of pay | Date | N/A | N/A |
| hours_before_benefits | Hours before benefits come into effect? | Text | N/A | N/A |
| days_before_benefits | Days before benefits come into effect? | Text | N/A | N/A |
| Question ID | Question Text | Field Type | Default Value, Dropdown Code | Radiobutton Desc, Dropdown Desc |
|---|---|---|---|---|
| ny_allow_none | Are any allowances taken? | Dropdown | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| ny_allow_tips | Are any tip allowances taken? | Dropdown | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| ny_allow_tips_amt | If tip allowances were taken, enter the amount per hour | Text | N/A | N/A |
| ny_allow_meals | Are meal allowances taken? | Dropdown | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| ny_allow_meals_amt | If meal allowances were taken, enter the amount per meal | Text | N/A | N/A |
| ny_allow_lodging | Are lodging allowances taken? | Dropdown | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| ny_allow_lodging_amt | If lodging allowances were taken, enter the amount | Text | N/A | N/A |
| ny_allow_other | Are there other allowances taken? | Dropdown | - Yes - No | - Yes - No |
| - Yes | ||||
| - No | ||||
| - Yes | ||||
| - No | ||||
| ny_allow_other_amt | If other allowances were taken, enter the amount | Text | N/A | N/A |
| ny_exempt_under | This employee is exempt from overtime under the following exemption: | Text | N/A | N/A |
| Question ID | Question Text | Field Type | Default Value, Dropdown Code | Radiobutton Desc, Dropdown Desc |
|---|---|---|---|---|
| sc_vacation | What will be the vacation policy for this employee? | Text | N/A | N/A |
| sc_holiday | What will be the paid holidays for this employee? | Text | N/A | N/A |
| sc_sick | What will be the sick leave policy for this employee? | Text | N/A | N/A |
| sc_terms | What, if any, are the additional terms for this employee? | Text | N/A | N/A |
| sc_deductions | Deductions to be made from wages such as insurance deductions | Text | N/A | N/A |
| sc_hoursofwork | What are the normal hours of work (number or range of hour per week, day, other, etc) | Text | N/A | N/A |
| sc_commission | What is this employee’s commission rate? | Text | N/A | N/A |
After entering the new hire questions, enter the same questions on the State Rules form in the State Default Questions panel.
To enter the state-default questions on the State Rules form:
Click Back Office.
From System|Change select State Rules. The State Rules form opens.
Enter the appropriate State Code (CA, DC, MN, NY, SC).
In State Default Questions, enter the information found in the previous tables. You must add these questions in the same order as the table above.
Click Save.
The state-required forms are now available in the system to include in employee onboarding workflows.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Launching_New_Workflow_OB.htm
Path:
OBE/Onboarding/Topics/Launching_New_Workflow_OB.htm
The following details how to launch new workflows using the Launch New Workflow action.
To launch a new workflow:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
Field — Description
New Hire — The employee’s name.
SSN — The employee’s Social Security Number. The value shown may be masked or hidden depending on settings at the system or client level.
Employee ID — The employee’s ID number.
Client ID — The client ID number.
Employer Start Date — The date the employee started with the employer.
Client Start Date — The date the employee started with the client.
Closed Workflow — The name and version of the closed workflow.
Closed Date — The date the prehire record was created.
New Workflow — The name and version of the new workflow to be launched.
Action — Launch: Enables you to launch a new workflow.
In the Action column, click Launch.
Launching a new workflow without an employee record:
At the start of the onboarding process, new hires do not have an employee record (they have only a prehire record). In the Launch Options panel, you can specify the following information for employees with a prehire record:
Select — To
Workflow that will be launched — Allows you to select any of the active onboarding workflows from a drop-down.
Launch new workflow immediately — Enables you to launch a new workflow immediately.
Go to New Hire page to enter employee data and launch new workflow — Opens the New Hire form where you must enter the new hire information again to launch a new onboarding process.
Launching a new workflow with an employee record:
In the Launch Options panel, you can specify the following information for employees with an employee record:
Select — To
Workflow that will be launched — Allows you to select any of the active onboarding workflows from a drop-down.
Launch new workflow immediately — Launches a new workflow immediately. If the new workflow has a cross hire conflict, a confirmation dialog box displays. The message indicates that the Social Security Number matches an employee in a different company, but the First Name, Last Name, or Date of Birth do not match. If you continue, the conflict will be saved. However, the workflow will not be launched until you resolve the conflict on the Review Cross Hire Conflicts form.
Go to Employee Details to make changes and launch new workflow — Opens Employee Details where you can enter employee information.
[Image: screenshot]
On the Employee Details form, you can:
Click Save & Onboard Now after entering the employee’s data to save their changes and launch the new workflow. The Employee Details form refreshes.
Click Remove Onboarding to cancel the launch of the new workflow. The Employee Details refreshes to its original state prior to launching a new workflow.
Onboarding-related information appears on every tab of the Employee Details form in the upper right‑hand corner.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Maintaining_Message-Templates.htm
Path:
OBE/Onboarding/Topics/Maintaining_Message-Templates.htm
To maintain templates for emails and reminders sent automatically by PrismHR, use the Message Templates form.
Onboarding offers the following message templates specific to the onboarding process. You can edit the Body content as needed.
| Message ID | Description | Subject | Action |
|---|---|---|---|
| OBECONSENTDECLINED | Employee declines the Electronic Consent form. | Declined Electronic Consent for <<EMPLOYEE.NAME>>
(< |
A detailed message is sent to the service provider describing the issue and the actions necessary to solve it. The set of recipients include those with the Account Management Roles of Human Resource and Payroll Representative. |
| OBNOGEOCODEMESSAGE | No GeoCode is saved for onboarding workflow. This occurs when a user enters the Resident Address manually. | No geocode saved for <<EMPLOYEE.NAME>>
(< |
A detailed message is sent to My Messages for a set of recipients. |
| OBEMPLOYEEDASHBOARDREMINDER | Onboarding employee dashboard reminder. | Onboarding forms to complete for < |
Reminder sent to employee Performer using Send Reminder action on the Onboarding Task by Status dashboard or the Enhanced Dashboard. |
| OBAPPROVERDASHBOARDREMINDER | Onboarding approver dashboard reminder. | Onboarding approval is pending for <<EMPLOYEE.NAME>>
from < |
Reminder sent to approver Performer using Send Reminder action on the Onboarding Task by Status dashboard or the Enhanced Dashboard. |
Related Topic
Setting Up Automated Email Messages
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing%20the%20Workflow%20Library%20(OB).htm
Path:
OBE/Onboarding/Topics/Managing the Workflow Library (OB).htm
To configure onboarding workflows, use the Workflow Library.
To create and configure onboarding workflows:
Click Back Office.
From System|Change, select Workflow Library. The Workflow Library opens.
Filter these fields as required:
| Field | Description |
|---|---|
| Name | The workflow name. |
| Id | The workflow ID assigned on the Create New Workflow form. |
| Version | The workflow version number. |
| Type | Onboarding. |
| Status | - Active: The workflow is in use. - Draft: The workflow is saved in Draft mode. - Inactive: The workflow is not in use. |
See the following to create new workflows:
You can also add notifications that you want to send to employees or groups to workflows. To do this, you must first set up notification templates and recipients. When created, notifications are available in the Notifications tab in the Workflow Library where you can add them to workflows as needed.
To set up the content for the notifications you want to send out to employees or groups during enrollments, and specify when to send the notifications, see Setting Up Notification Templates (Onboarding).
To set up recipients for the notifications. Notification recipients can be specified by group (for example, Internal Employees, Managers), by user role (for example, Client Benefit Representative), or both, see Setting Up Notification Recipients (Onboarding).
The Workflow Library also maintains multiple versions and revisions of workflows:
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing-Approvals-Queue.htm
Path:
OBE/Onboarding/Topics/Managing-Approvals-Queue.htm
Important! The Manage Approvals Queue form has been retired. Instead, use the Manage Pending Approvals form (Refer to the PrismHR Human Resources Guide for more information.)
When you select Manage Approvals Queue on the Operations|Utility Processing menu a message displays, “Managing pending approvals has been moved to the new Manage Pending Approvals form. You will be redirected.” Click OK to display the Manage Pending Approvals form for the active client.
Note: Note: If you had access to the Manage Approvals Queue form but you do not have access to the Manage Pending Approvals form, when you access this form a message displays, “Managing pending approvals has been moved to the new Manage Pending Approvals form. Access to the Manage Pending Approvals form will need to be added to your user role.”
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing-Form-Doc-Sets/Creating_Form_Set_OB.htm
Path:
OBE/Onboarding/Topics/Managing-Form-Doc-Sets/Creating_Form_Set_OB.htm
To create a new form set:
The system displays the Create Form Set form.
Use the Create Form Set form to create form sets.
To create a new form set:
Click Back Office.
Under System|Change, select Form Sets.
Click Create Form Set.
Complete the following fields in the GENERAL section:
| Field | Action |
|---|---|
| Set Name | Enter a name for the form set. This field is required. |
| Description | Enter a brief description for the form set. |
| Workflow Type | Onboarding is the only option. |
Note: Note: The Continue button only becomes active once required fields are filled in.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing-Form-Doc-Sets/Editing_A_Form_Set_OB.htm
Path:
OBE/Onboarding/Topics/Managing-Form-Doc-Sets/Editing_A_Form_Set_OB.htm
Use this form to change settings for a form set.
To edit a form set:
| Field | Action |
|---|---|
| Form Set Name | Enter a name for the form set. This field is required. |
| Description | Enter a brief description for the form set. |
| Workflow Type | Read-only field, set to Onboarding. |
| Set Type | Select Form or Document from the drop-down. |
| Method for Choosing Forms | Select a method for how you want forms displayed within a form set. This setting is required. Options are: - Display only client forms – If no client forms, display global forms - When an onboarding process is created, use business rules to include client forms. If no client forms exist, include any global forms. - Display both client and global forms – When an onboarding process is created, include both client forms and global forms. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing-Form-Doc-Sets/Viewing%20Forms.htm
Path:
OBE/Onboarding/Topics/Managing-Form-Doc-Sets/Viewing Forms.htm
Use View Forms to review forms attached to a form set. Please note:
If a form is associated with a client (through a business rule), the business rule and client display.
If a form is associated with multiple clients, each form and client is shown in a separate row.
To access this form:
From Edit Form Set, click the View Forms tab.
Click View Forms to view the list of forms in the form set.
The system displays a list of forms or displays the following message:
No forms currently associated to this form set.
The following table describes the fields that display in a form list:
| Field | Description |
|---|---|
| Form ID | The ID assigned to the form in the Form Library. |
| Form Name | The name assigned to the form in the Form Library. |
| Business Rule | The business rule assigned to the form in the Form Library. This field can be blank. |
| Process As | - Client Form – This form is associated with a client. - Global Form – This form is not associated with a client. > Note: Note: This designation is used by the Method for Picking Forms to determine if the form is included in the workflow. |
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing_Business_Rules_OB.htm
Path:
OBE/Onboarding/Topics/Managing_Business_Rules_OB.htm
To create and manage business rules, use the Business Rules Library. When attached to forms, business rules determine if a form displays in a workflow.
The Business Rules Library is located in the Back Office under System|Change.
To open the Business Rules Library:
Click Back Office.
From System|Change select Business Rules Library. The Business Rules Library opens.
| Field | Description |
|---|---|
| Business Rule | The name of the business rule. |
| Date of Creation | The date the business rule was created. |
| Type | Onboarding. |
| In Use | Business rules currently in use display a green check mark [Image: screenshot] . |
| Action | Delete business rules by clicking [Image: screenshot] . |
Default business rules available for onboarding include:
CA-WAGE
NY-WAGE-HOURLY
NY-WAGE-SALARIED
SC WAGE
Select a business rule from the list to edit the configuration on the Edit Business Rule form. Or, to create a custom business rule, click Create Rule.
Related Topics
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing_Forms_OB.htm
Path: OBE/Onboarding/Topics/Managing_Forms_OB.htm
To create and maintain forms, use the Form Library.
These forms are the components used to build workflows for Onboarding. PrismHR provides prebuilt forms that can be used with minimal customization and the ability to create custom forms for additional onboarding options.
To open the Form Library:
Click Back Office.
From System|Change, select Form Library. The Form Library displays.
| Field | Description |
|---|---|
| Name | The name of the form. |
| ID | The ID assigned to the form when the form was created on the Create New Custom Form form. |
| Version | The version number of the form. |
| Form Type | - Default: This indicates that the form is a prebuilt form. - Custom: This indicates that the form was created manually. |
Title — Description
I-9 Section 1 — Employee enters I-9 Section 1 information.
I-9 Section 2 — Manager enters I-9 Section 2 information.
Direct Deposit — Employee enters direct deposit information.
Disability — Employee enters Disability Status information.
Elect W-2 — Employee can choose to receive Form W-2 electronically. > Note: Note: This form should not be added to workflows for clients with electronic Form W-2 settings already defined at the client level.
Electronic Consent — Employee can accept or decline the electronic consent of their onboarding process.
Employee Information — Employee enters personal information.
Initial Visit — Employee views this form at the start of the initial visit.
Onboarding Summary — Employee views this form to display a summary status of all forms.
Race/ Ethnicity — Employee enters EEO-1 information.
Return Visit — Employee views this form at the start of any visit after the initial visit.
Submit — Employee submits all onboarding forms at the end of the workflow.
Tax — Employee enters tax information.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing_Notification_Objects_Tasks_OB.htm
Path:
OBE/Onboarding/Topics/Managing_Notification_Objects_Tasks_OB.htm
You can specify sending Onboarding notifications based on the object specified in the Notification tab when setting up a workflow in the Workflow Library. For event based notifications an object can be a workflow, specific form, or the I-9 Section 2 form.
The objects that display in the Object column differ depending on the notification Trigger Condition. For time based notifications, an object can be a task.
A task is an action that an employee or administrator must completed by the employee (or an administrator) by a fixed due date. Notifications that have the time‑based Trigger Type display tasks in the Object drop-down.
The following tables lists all of the notification conditions and their associated objects or tasks you can select when attaching a notification to an onboarding workflow.
| Trigger Type | Trigger Condition | Object or Task Options Available |
|---|---|---|
| Event Based | Workflow is launched | Workflow (no additional objects or task list displays) |
| Event Based | Workflow is completed | Workflow (no additional objects; no drop-down displays) |
| Event Based | Employee submits form | - I-9 section 1 - Employee Information - Selected Forms - Submit |
| Task | Due Date |
|---|---|
| I-9 Section 1 | Employee’s date of hire |
| Employee Information | Employee’s date of hire |
| I-9 Section 2 | Approval due 3 days after date of hire |
| All Other Forms | Onboarding end date |
For example, if the task I-9 Section 1 is set up with the time based Trigger Condition X Days before due date, and the number Days are defined as 5, the notification is sent 5 days before the employee’s date of hire.
Note: Note: The date of hire is defined as the later of Client Start Date and Employer Start Date. It is the day the new hire begins employment.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Managing_Versions_and_Revisions_OB.htm
Path:
OBE/Onboarding/Topics/Managing_Versions_and_Revisions_OB.htm
The Form Library and Workflow Library both maintain multiple versions and revisions for forms and workflows. The system sets revisions automatically when you submit a new form or workflow or modify an existing one.
When you create a new form or workflow, the system automatically sets the Version to 1.0.
If you change the form or workflow and select the option to have them go into effect immediately, the system adds a Revision number after the decimal point in the Version number (1.1, 1.2, and so on).
The system also immediately sets the Status to Active, and sets the current date as the Start Date. Since there can be only one active version of the form, the system changes the Status of any prior active version to Inactive and sets the current date as its End Date.
The system sets the new version’s Status to Active on the Start Date, which you assign when you submit the form or workflow. Since there can be only one active version, the system changes the Status of any prior active version to Inactive and sets the current date as its End Date.
You can view and compare different versions and revisions in both libraries by clicking the form or workflow ID in the table. The Versions form opens, displaying all versions and revisions that exist.
Click the ID if you want to modify a form or workflow version or revision.
To compare two versions or revisions of a form or workflow, select the two you want to compare and click Compare. The Comparison panel opens below the main table in the form (you must scroll down to view data) and displays settings for both.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Message_Templates.htm
Path: OBE/Onboarding/Topics/Message_Templates.htm
Create and maintain email templates for automatically sent email with the Message Templates form. For example:
[Image: screenshot]
Note: Note: You can assign templates to specific actions in the Email Services form, which you can access from the Actions menu on the System Parameters form.
To configure message templates:
Field — Description
Message ID — Enter or select an ID for the template. For example, Password Reset could be identified as PWDRESET. When you enter or select a Message ID, additional language fields display.
Description — Enter the description of the template. For example, HR Action Approval Email Template.
Content Type — Set the content type as either TEXT or HTML.
Display Language — Displays the default language on the system (US English). Additional languages can be selected from the drop-down in the box on the right that displays after you select the Message ID. For example, you can configure a Spanish message template, which will display a notification in Spanish for employees whose preferred language is set to Spanish in the Personal tab on the Employee Details form.
Subject — Enter the subject line for the message template.
Body — Enter the body text for the message template. (You can use HTML in the message body if the Content Type is set to HTML.)
Note: Note: You can use substitution variables for Subject and Body to customize the message appearance. (See Using Substitution Variables.)
Note: Note: The HTML format prevents users from entering JavaScript constructs that could lead to issues with cross-site scripting (XSS).
Related Topic
Setting Up Automated Email Messages
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Metadata_Editor.htm
Path: OBE/Onboarding/Topics/Metadata_Editor.htm
The Metadata Editor form is used to edit the metadata for Benefits Enrollment and Onboarding documents. This metadata can be used to optimize document organization and search results.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Notification_Control_Panel_OB.htm
Path:
OBE/Onboarding/Topics/Notification_Control_Panel_OB.htm
Use the OB Notify section in the Notification Control Panel to:
Start and stop the notification engine during onboarding
Determine the frequency at which the notifications engine sends notifications
During onboarding, the system sends event and time-based notifications attached to the workflows to notification recipients. The system:
Sends time-based notifications daily, typically shortly after midnight. This applies only to incomplete forms in the onboarding workflow.
Sends event-based notifications when the event specified by the trigger condition occurs (for example, when the employee completes the workflow). The notification engine runs in the background and periodically checks to see whether there are notifications to send. If so, it sends event-based notifications when they turn up during the check.
[Image: screenshot]
Note: Note: The options in the BE Notify section are only used in Benefits Enrollment and do not affect Onboarding.
To check for and send available event-based notifications:
Click Back Office.
From Operations|Action select Notification Control Panel. The Notification Control Panel form opens.
In OB Notify Interval (mins), enter the number of minutes. You can enter values from 5 to 1440 minutes.
Note: The state of the process, ENABLED or DISABLED, displays next to the OB Notify Interval (mins) field.
OB Notify Date populates automatically with the date the system last sent time-based notifications.
If you need to manually resend a notification (for example, if employees did not receive the notification, or if there is a change to the notification template), you can delete the displayed OB Notify Date, and click Save. The system resends time-based notifications for that day with the current date. When the notifications are resent, the current date displays.
Click this in the OB Notify section — To do this
Stop — Stop the system from sending notifications — Stop changes to Start, and the status changes to NOT RUNNING. The request to stop notifications takes effect immediately. However, it can take a few minutes for the updated status to display correctly. Note: The status displays next to the Stop button.
Start — Start the notifications engine without changing settings — Start changes to Stop, and the status changes to RUNNING. If you stop and then restart the notifications engine, the process ID (PID) number resets and a new PID displays. Note: The status displays next to the Start button.
Cancel — Close without saving changes.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Notification_Recipients_OB.htm
Path:
OBE/Onboarding/Topics/Notification_Recipients_OB.htm
To set up recipients for onboarding notifications created using the Notification Templates form, use the Notification Recipients form.
This form can also be used to modify or delete existing notification recipient records. However, recipient records that are currently associated with a notification template cannot be deleted.
[Image: screenshot]
To set up notification recipients:
Click Back Office.
From System|Change, select Notification Recipients. The Notification Recipients form opens.
Complete the following fields:
Field — Action
Notification ID — Enter an existing notification ID, or click Setup a new Notificationcreate a new notification.
Name — Enter a name for the notification recipient group. The name displays on the Workflow Library form in the list of notification users you can add to workflows.
Description — (Optional) Enter a description for the notification.
Panel — Description
To Group Recipients — Primary recipients for the notification, organized by group (for example, Internal Employees, Managers, and so on). To set up groups, use the Message Center Groups form. > Note: Note: Message groups that include client records cannot be used in notification recipient records.
To Generic — Primary recipients for the notification, organized by role: Employee, Client Benefit Rep, Human Resources, Client Manager, I-9 Section 2 Approver. The Client Benefit Rep, Human Resources, and Client Manager roles can be assigned to users using the Users form. Before selecting I-9 Section 2 Approver as a generic recipient, I-9 Section 2 approval policies must be set up at the system level using the Global Approval Policies form and at the client level using the Approval Policies form. An administrator must also be assigned to the I-9 Approval role using the Users form. For more information, see Configuring System Settings.
CC Group Recipients — Additional recipients to copy publicly, organized by group.
CC Generic — Additional recipients to copy publicly, organized by role.
BCC Group Recipients — Additional recipients to copy privately, organized by group.
BCC Generic — Additional recipients to copy privately, organized by role.
In the Notification Template panel, enter the ID number of the template to use in the Template ID field. The name and description associated with the template are automatically entered in the appropriate fields, and the appropriate check boxes are selected for the associated workflow type and message delivery method.
Click Save.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Notification_Templates_OB.htm
Path:
OBE/Onboarding/Topics/Notification_Templates_OB.htm
The Notification Templates form is used to create templates for the notifications that are sent to employees or groups during onboarding. Each template specifies the content that is included in the notification, such as the subject and message body, as well as the criteria for sending the notification and the communication method used to send the notification.
When defining notification content, substitution variables can be used to replace generic information with specific information from PrismHR.
Once the template has been created, the Notification Recipients form can be used to define the recipients who receive the notification. Refer to Setting Up Notification Recipients (Onboarding) for more information. In addition, the notifications can be added to a workflow using the Workflow Library. Refer to Creating a Workflow (Onboarding) for more information.
Note: Note: Notification templates that have been attached to a workflow or a notification recipient record cannot be deleted.
To set up a notification template:
Click Back Office.
From System|Change, select Notification Templates. The Notification Templates form displays.
In the Notification Templates panel, complete the following fields:
Field — Action
Template Id — To modify an existing template, enter a template ID or click Template Id to display a list of existing templates. To create a new template, click Create a New Template. An available template ID is entered in the Template Id field.
Name — Enter a name for the template. This name identifies the template and displays in the list of available templates when assigning notification recipients.
Description — Enter a description of the template.
Language Default — For future development. Does not currently impact the functionality of PrismHR.
Subject — Enter a subject for notifications sent using the template. > Note: Note: Do not use square brackets ([ or ]) in this field as doing so will prevent recipients from receiving notifications sent using this template.
Message Body — Enter the body text for the notifications sent using the template.
SMS Body — For future development. Does not currently impact the functionality of PrismHR.
| Field | Action |
|---|---|
| Trigger Type | Select a notification trigger type. - Time Based: Notifications are sent a specific number of days before or after the workflow’s due date. If the notification engine is set up to check in the morning, the notifications are sent in the morning. If the notification engine is set up to check every other day, the notifications are sent every other day. Notification engine settings are defined using the Notification Control Panel. Refer to Using the Notification Control Panel (Onboarding) for more information. - Event Based: Notifications are sent when a specific event occurs, such as when an onboarding workflow is completed. The notification engine runs in the background and periodically checks to see whether there are notifications to send and sends event-based notifications when they turn up during the check. |
Note: Note: The Send SMS option is for future development and does not currently impact the functionality of PrismHR.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/OB_Dashboard_WSM.htm
Path: OBE/Onboarding/Topics/OB_Dashboard_WSM.htm
The following procedure details the steps required to add the Onboarding dashboard to the worksite manager role in PrismHR.
Log in to PrismHR as a service provider.
Open Users (found in the Back Office menu under System|Change).
In the User Roles panel, enter the worksite manager’s Role ID with a brief Role Description.
Open User Roles (found in the Back Office menu under System|Change).
Enter the user Role ID (from Step 3), and select Add. The User Role Maintenance from displays.
Select the Process ID HRPY.WORK*DASH, and select Accept.
Select Save on the User Roles form.
Log out of PrismHR, and log back in as the worksite manager.
Open My Home (found in the Client menu under Client|Dashboard).
Select Onboarding Tasks by Status from the My Persepctive drop-down to view information relevant to Onboarding.
Note: Note: Save the My Home form as a favorite for convenience.
Parent Topic
Working with the Onboarding Dashboard
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Onboarding_Options.htm
Path: OBE/Onboarding/Topics/Onboarding_Options.htm
Maintain global onboarding parameters with the Onboarding Options form.
Use this option… — To do this…
Complete All Forms to Activate Payroll — Define the system default option for allowing employees to be added to payroll before all onboarding‑related forms in their workflow are completed. When the Complete All Forms to Activate Payroll field on the Control tab on the Client Details form is set to System Default, the system uses this option to determine whether the client’s employees can be added to payroll before all onboarding-related forms in their workflow are completed. When the Complete All Forms to Activate Payroll field on the Control tab on the Client Details form is set to Enabled or Disabled, the system uses the setting in that field to determine whether the client’s employees can be added to payroll before all onboarding-related forms in their workflow are completed.
Enable Benefit Enrollment After Final Submit — Define the system default option for allowing employees to access their benefit enrollment workflow through Onboarding after submitting all onboarding‑related forms. When the Enable Benefit Enrollment After Final Submit field on the Control tab on the Client Details form is set to System Default, the system uses this option to determine whether the client’s employees can access their benefit enrollment workflow through Onboarding after submitting all onboarding‑related forms. When the Enable Benefit Enrollment After Final Submit field on the Control tab on the Client Details form is set to Enabled or Disabled, the system uses the setting in that field to determine whether the client’s employees can access their benefit enrollment workflow through Onboarding after submitting all onboarding‑related forms.
Disable Pay Rate Change Approval for Rehire — Disable approval requests for rehire pay rate changes on the Pay tab on the Employee Details form.
Suspend Workflow When “Onboarding in Progress” Manually Unchecked — Enable this option to suspend employee onboarding workflows when the Onboarding in Progress option on the Other tab on the Employee Details form is manually disabled. If this option is disabled and a manager also disables the Onboarding in Progress option, the employee onboarding workflow stays in progress.
Allow Upload of Supporting Documents (I-9) — Define the system default option for allowing employees to upload supporting I-9 documents during the I-9 workflow. When the Allow Upload of Supporting Documents (I-9) field on the Control tab on the Client Details form is set to System Default, the system uses this option to determine whether the client’s employees are allowed to upload supporting I-9 documents. When the Allow Upload of Supporting Documents (I-9) field on the Control tab on the Client Details form is set to Enabled or Disabled, the system uses the setting in that field to determine the client’s employees are allowed to upload supporting I-9 documents.
Archive Prehire Workflows for Terminated Employees Older Than — Select the number of months after which prehire records and onboarding workflows for terminated employees are archived. By default, 12 Months is selected. > Note: Note: A number of months that is shorter or longer than the onboarding window length can be selected using this option. To also archive onboarding workflows for active employees and employees on leave of absence, in addition to terminated employees, select the Include Non-Terminated Employees check box. When this check box is selected, a message displays to indicate that existing workflows will be archived and that electronic onboarding will be unable to continue for the affected employees. However, completed onboarding documents will remain available as normal. After a prehire record or onboarding workflow has been archived, the record can be restored using the Workflow Maintenance form. See Maintaining Workflow Actions.
Enable Logging in Rules Engine — Enable this option to turn on logging. When you select this option and the system creates a prehire record, a trace logging file is also created for the prehire record if the employee for whom the prehire record was created is assigned an Onboarding workflow that includes forms to which business rules are applied. (Disable this field to prevent the system from creating the trace logging file for the prehire record, which can increase performance.)
OB background PDF generator — Enable a background process that locates and generates missing PDF documents for completed Onboarding workflows.
Employee Information Form Fields — Define which fields on the Employee Information form are required in onboarding workflows.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Registering_by_Proxy_OB.htm
Path: OBE/Onboarding/Topics/Registering_by_Proxy_OB.htm
Cross hire employees can have multiple employee IDs in the system. For example, this occurs when an employee works for both a PEO and ASO. It also occurs when an employee works for both an ASO (Employer 1) and another ASO (Employer 2).
Cross hire employee onboarding with a newly generated employee ID for Employer 1 have only a prehire record. Since the Users form in PrismHR does not display employee IDs from prehire records, the service provider cannot create a new user record for Employer 2. To create a user record, you can use the Proxy Registration action.
The following details how to register by proxy with the Proxy Registration action.
To create a user record by proxy:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
Field — Description
New Hire — The employee’s name.
SSN — The employee’s Social Security number. The system may hide the value shown depending on settings at the system or client level.
Employee ID — The employee’s ID number.
Employer Start Date — The date the employee started with the employer.
Client Start Date — The date the employee started with the client.
Personal Email — The employee’s personal email address.
Action — Register: Lets you register the employee in the system by proxy.
In the Action column, click Register. The Proxy Registration panel displays.
Complete the following required fields:
| Use this option | To do this |
|---|---|
| Email Address | Enter the employee’s email address. |
| Username | Enter the employee’s username. |
| Password | Enter the employee’s password. |
| Confirm Password | Reenter the employee’s password. |
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Reopening_Workflow_OB.htm
Path: OBE/Onboarding/Topics/Reopening_Workflow_OB.htm
The following details how to reopen a workflow using the Reopen Workflow action.
To reopen a workflow:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
| Field | Description |
|---|---|
| New Hire | The employee’s name. |
| SSN | The employee’s Social Security Number. The value shown may be masked or hidden depending on settings at the system or client level. |
| Employee ID | The employee’s ID number. |
| Employer Start Date | The date the employee started with the employer. |
| Client Start Date | The date the employee started with the client. |
| Workflow | The workflow name and version number. |
| Submit Date | The date the new hire submitted the onboarding workflow. If the workflow includes the Form I-9, the Submit Date is the later of the following: - The date the onboarding workflow is submitted - The approval date for the I-9 Section 2 If the workflow does not include the Form I-9 Section 2, the Submit Date is the date the onboarding workflow is submitted. |
In the Action column, click Reopen. The Reopen Workflow and Reopen Options panels display.
Complete the following:
Use this option — To do this
Unlock I‑9 Section 1 for employee (Reopens workflow and I‑9 Section 2) — Unlock the Form I‑9 Section 1 and reopen the workflow and Form I‑9 Section 2 Approval. This option is available if the I‑9 Section 2 Approval is in progress or was submitted by the approver.
Reopen workflow for employee — Reopen the workflow. This options is available if the employee submitted the workflow.
Reopen I‑9 Section 2 for approver — Reopen the Form I‑9 Section 2 Approval. This option is available if the approver submitted the I‑9 Section 2 Approval.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Reviewing_Cross_Hire_Conflicts.htm
Path:
OBE/Onboarding/Topics/Reviewing_Cross_Hire_Conflicts.htm
Note: Note: On the User Roles form, you can only grant full access (Full) or deny access (Deny) to the Review Cross Hire Conflicts form. Currently, the Inquiry option functions the same as granting full access.
On the Review Cross Hire Conflicts form, you must review the conflict shown to decide whether the new hire is the same person as the existing employee. This may involve speaking with the manager who entered the new hire, the new hire, or the existing employee. To help you communicate with these people, the Review Cross Hire Conflicts form shows the person who entered the conflict, as well as contact information for the manager who entered the new hire, the new hire, and the existing employee.
If the new hire is the same person as the existing employee, you can correct the mismatched fields so the system can automatically launch the workflow. If the data correction involves an active onboarding workflow, that workflow resets so the employee can resign all forms with the correct information. If the new hire is not the same person as the existing employee, you can delete the new hire.
To open the Review Cross Hire Conflicts form:
Click Back Office.
From System|Action, select Review Cross Hire Conflicts. The Review Cross Hire Conflicts form opens.
| Column | Description |
|---|---|
| New Hire Name | The new hire’s first and last name (last name, first name). |
| SSN | The new hire’s Social Security number. |
| Client ID | The client’s unique identification number. |
| Client Name | The client’s name. |
| Conflict Date | The date the conflict was entered into the system. |
| Data Entered By | The person that entered the conflict in the system. |
| User Type | The user type of the person that entered the conflict. - Service Provider - PEO employee or other users at your organization - Worksite Manager - Manager for a client - Worksite Employee - Employee for a client - Worksite Trusted Advisor - User who works for one or more clients and is not necessarily an employee |
Select a new hire from the list. The Review Conflict tab displays.
| Section | Description |
|---|---|
| New Hire Company | The client with the conflict. - Client ID - The client’s unique identification number. - Client Company - The client’s name. |
After identifying that the new hire is the same person, you can fix the conflict to make the existing employee and new hire records match.
To fix the conflict:
Click Fix Conflict. The Fix Conflicts dialog box displays.
In Update data for both records, correct the conflicts and click Update.
In the confirmation dialog box, click Yes, Update. The Review Cross Hire Conflicts form displays. Both records update to match correctly, and the conflict is removed from the list.
After identifying that the new hires are not the same person, you can delete the new hire record.
To delete the new hire:
Click Delete New Hire.
In the confirmation dialog box, click Yes, Delete. The Review Cross Hire Conflicts form displays. The record deletes and the conflict is removed from the list.
To view the person that entered the conflict in the system, use the Conflict Entered By tab.
To view contact information for the manager who entered the new hire, new hire, and existing employee in the system related to the conflict, use the Contact Information tab.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Setting_Up_Approval_Policies_(Global_and_Client_Level).htm
Path:
OBE/Onboarding/Topics/Setting_Up_Approval_Policies_(Global_and_Client_Level).htm
Set up the I-9 Section 2 approval policies for your organization at the system or client level in the Global Approval Policies and the Approval Policies forms.
An I-9 Approver role is available in both forms. You can use that role, or any other role, for I-9 Section 2 approvals.
For more information about setting up approval policies at the system level, see the System Administration Guide or Approvals Guide. For more information about setting up approval policies at the client level, see the Human Resources User Guide or Approvals Guide.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Setting_Up_Form_I-9_Approvers.htm
Path:
OBE/Onboarding/Topics/Setting_Up_Form_I-9_Approvers.htm
For Onboarding, you must set up an administrator as an I-9 Approver.
To define an administrator as an I‑9 Approver:
Click Back Office.
From System|Change, select Users.
In User ID, enter the administrator ID.
In User Type:
For a service provider, in the Account Management Roles panel, select I‑9 Approver.
For a worksite manager, in the Human Resource Roles panel, select I‑9 Approver.
For more information on editing user roles in PrismHR, see the System Administration Guide.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Suspending_Workflow_OB.htm
Path: OBE/Onboarding/Topics/Suspending_Workflow_OB.htm
The following details how to suspend a workflow with the Suspend Workflow action.
To suspend a workflow:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
Field — Description
New Hire — The employee’s name.
SSN — The employee’s Social Security Number. The value shown may be masked or hidden depending on settings at the system or client level.
Employee ID — The employee’s ID number.
Employer Start Date — The date the employee started with the employer.
Client Start Date — The date the employee started with the client.
Workflow — The workflow name and version number.
Launch Date — The date the onboarding workflow was initially launched.
Action — Suspend: Enables you to suspend onboarding workflows.
In the Action column, click Suspend.
Suspending a workflow without an employee record:
At the start of the onboarding process, new hires do not have an employee record (they have only a prehire record). For employees with only a prehire record, clicking Suspend displays a confirmation dialog box indicating that you are suspending the workflow, and a message shows when the employee logs in that their onboarding process is unavailable. To suspend the workflow, click Yes. The system returns you to the Workflow Maintenance form.
Suspending a workflow with an employee record:
For employees with only an employee record, clicking Suspend displays the Suspend Workflow and Suspend Options panels. In the Suspend Options panel, you can specify the following options for employees with an employee record:
Select — To
Display Onboarding unavailable message to the new hire. Use when you plan to launch a new onboarding workflow. — Show a message when an employee logs in that their onboarding process is unavailable.
Allow the new hire to access Employee Portal (EP) with Payroll enabled. Use when you do not plan to electronically onboard this person. — Enable the employee to access EP with payroll functionality enabled. If this option is selected, the employee cannot be electronically onboarded.
Click Continue. The system returns you to the Workflow Maintenance form.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Unarchiving%20a%20Workflow.htm
Path: OBE/Onboarding/Topics/Unarchiving a Workflow.htm
The following details how to restore prehire records and onboarding workflows using the Unarchive Workflow action.
To restore a prehire record and the associated workflow:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
Field — Description
New Hire — The employee’s name.
SSN — The employee’s Social Security Number. The value shown may be masked or hidden depending on settings at the system or client level.
Employee ID — The employee’s ID number.
Client ID — The client ID number.
Employer Start Date — The date the employee started with the employer.
Client Start Date — The date the employee started with the client.
Workflow — The workflow name and version number.
Action — Unarchive: Allows you to restore the corresponding prehire record and associated workflow.
Note: Note: This feature can be used to view archived records and workflows based on the archiving time period defined on the Onboarding Options form plus an additional 180 days. For example, if 12 Months is entered in the Archive Prehire Workflows for Terminated Employees Older Than option on the Onboarding Options form, you can view archived records and workflows from the previous 12 months and an additional 180 days, for a total of 18 months.
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Uploading_PDF_Files.htm
Path: OBE/Onboarding/Topics/Uploading_PDF_Files.htm
To upload and map PDF files to custom forms, use the PDF Integration option. Upload state‑required or custom PDF files to include in employee onboarding workflows. To download the following PDFs, see State‑Required Forms for Onboarding on the Customer Resource Center.
The following state‑required PDF files are supported for mapping:
California: Theft Notice to Employee (CA Wage)
New York: Notice for Hourly Rate Employees (NY Wage Hourly)
New York: Notice for Exempt Employees (NY Wage Salaried)
South Carolina: Terms of Employment Notice (SC Wage)
Washington D.C. Notice of Hire — Employment Status and Acknowledgment of Wage Rate(s) (DC Wage)
Minnesota Employee notice (MN Wage)
To upload a PDF file for mapping:
Click Back Office.
From System|Change, select Form Library. The Form Library opens.
Select the custom form from the list to open to the Edit Custom Form.
On the General tab, click Please upload a compatible PDF for mapping. Then, select a document to upload.
The Confirm PDF Upload message displays if the layout of the form currently contains editable field types that will be removed. The editable field types are removed because all editable fields must be mapped to a PDF field.
On the PDF Fields Map tab, you can view a complete list of the fields extracted from the uploaded file. If the uploaded file is a state-required PDF, the PDF field is automatically assigned the map. This value displays in the PDF Mapping field.
[Image: screenshot]
| Field | Description |
|---|---|
| PDF Field | The name of the field on the PDF file. |
| PDF Mapping | The value assigned to the PDF file field in the system. |
| Action | Edit to assign a different map (source) to the PDF file field. The default value is None. |
To configure the PDF file field mapping:
[Image: screenshot]
| Field | Description |
|---|---|
| PDF Field (Target) | The name of the field on the PDF file. |
| PDF Field Type | The type of field on the PDF file. PrismHR supports the two most common field types found on PDF forms: - FIELD_TYPE_TEXT: Text field to enter data. - FIELD_TYPE_RADIOBUTTON: Option to select one of two items. |
In the example, the PDF Field (Employee Name) is populated with the Map (Source) Employee Full Name. On the PDF, the employee’s full name displays in the Employee Name field.
The Map (Source) list currently contains the set of maps needed for the CA and NY Wage state‑required forms. If the system recognizes a field on the uploaded PDF, it automatically assigns the map from the list to the PDF field. If the system does not recognize a field on the uploaded PDF, no map is assigned.
On the Layout tab, you can construct the form using the Field Type and PDF Fields lists. When a PDF uploads, the PDF Frame option displays in the Field Type list, and the PDF Fields list displays. The PDF Fields list contains the PDF fields mapped to custom form field types. You can view these PDF fields on the PDF Fields Map tab.
[Image: screenshot]
To construct the layout:
In the Field Type list, drag and drop the PDF Frame to the layout on the right.
In the PDF Fields list, drag and drop each entry list to the layout on the right.
The PDF fields available vary depending on the uploaded PDF.
To view the form output after configuring the layout, click Preview Form.
Click Save.
Parent Topic
========================================================================
Source:
https://tech-docs.prismhr.com/SP_help/Content/OBE/Onboarding/Topics/Viewing_Prehire_Audit_Log_OB.htm
Path:
OBE/Onboarding/Topics/Viewing_Prehire_Audit_Log_OB.htm
The Prehire Audit action lets you see audit log information for new hires. For example, the user ID and date the employee was entered in the system. The search results display all prehires in the system for the client and employee IDs selected.
Note: Note: In some cases, employees can have multiple employee IDs in the system. For example, this occurs when an employee works for both a PEO (Professional Employer Organization) and ASO (Administrative Services Organization). It also occurs when an employee works for both an ASO (Employer 1) and another ASO (Employer 2). Therefore, there may be prehires in the list for multiple clients.
The following details how to view a prehire audit log with the Prehire Audit action.
To view a prehire audit log:
In the Filters panel, you can filter the search results by client or by new hire information. To filter by client, enter a client ID number in the Client ID field or click the Client ID link to select a client ID number from a list. To filter by new hire information, enter a new hire’s last name, first name, Social Security Number, or employee ID in the New Hire field.
Click Search. The Search Results panel displays the following information:
Field — Description
New Hire — The employee’s name.
SSN — The employee’s Social Security number. The system may hide the value shown depending on settings at the system or client level.
Employee ID — The employee’s ID number.
Prehire Create Date‑Time — The date and time the system created the prehire employee.
Prehire ID — The ID assigned to the prehire.
Status — The employment status.
Action — Audit: Lets you view the prehire audit log.
In the Action column, click Audit. The File Audit form displays.
To view log details, click the Log ID link.
To close the audit log, click Close.