PrismHR Help · Public documentation for Microsoft 365 Copilot

PrismHR Help — Release Notes 2024-2026

Release Notes

This file is a combined export of PrismHR help topics in Release Notes. Source help system: https://tech-docs.prismhr.com/SP_help/Default.htm Each topic is separated by a heading and includes its original URL.

========================================================================

Updates to the Retirement Adjustment Register form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA-129%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA-129 (Epic).htm

Updates to the Retirement Adjustment Register form

Previously, the Retirement Register Adjustment form only had an option to enter Successor Retirement Deferral amounts. This functionality did not allow you to specify what portion of the amount entered (if any) should be allocated to Successor Catch-up Deferral bucket. With the new addition of the 3 Successor fields (Successor Catch-up Deferral, Successor ROTH Deferral and Successor ROTH Catch-up Deferral) you will be able to correct any previous retirement register adjustment entry amounts that caused the employee to exceed the retirement deferral tax year limit. A negative amount for the overage can be entered in the Successor Retirement Deferral field and a positive amount can be entered into the Successor Catch-up Deferral field. Now that the amounts are in the correct buckets, the desired tax year limits will be looked at and applied.

The following three fields will now also display under the Successor Deferrals section of this form:

Catchup Limit = Catch-up Contributions + Roth Catch-up Contributions + Successor -Catch-up Deferral + Successor ROTH Catch-up Deferral

JIRA # 2600, 2601, 2602, 2604, 2605, 2606, 2607, 2608, , 2631 2671

Updates to the Retirement Export form

On the Retirement Export form, when you select 401K Extended Download as the Vendor/Template, you will now see a new checkbox called Include Successor Deferrals.

JIRA # 2609

========================================================================

System Parameters: Remove Dependent Required Fields Settings

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA-1938.htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA-1938.htm

System Parameters: Remove Dependent Required Fields Settings

In a prior release, the Employee Dependent Required fields settings from the System Parameters form were added to the New Hire and Dependent Required Fields (Global) and New Hire and Dependent Field Overrides forms. With this ticket, the following Employee Dependent Required fields settings have been removed from the System Parameters form:

JIRA # BA-1938

========================================================================

Enhancements to the ACA Eligibility Calculation Process

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA-2488%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA-2488 (Epic).htm

Enhancements to the ACA Eligibility Determination Process

Background

There is an automatic PrismHR process which checks an employee’s eligibility for health insurance coverage under the Affordable Care Act (ACA). This process is triggered by different events in the system, such as new hires, rehires, imports, and employment type changes.

Under the Affordable Care Act, employees with part-time hours that exceed a certain threshold can become eligible for offers of coverage under certain plans. When this occurs, the employee enters a “Stability Period”. During the Stability Period, their hours are measured to determine whether they still qualify for coverage.

Typically, when an employee enters a Stability Period, a manual or automatic process then adds them to the ACA Offered Employees form. The employee remains part-time, but their placement on this form indicates that the system should treat them as full-time employees for ACA reporting purposes. This means that any listed employees who were eligible for at least one month of coverage under the ACA will receive a copy of Form 1095-C at the end of the year.

[Image: ACA Offered Employees with Stability start and end dates highlighted]

However, the automatic eligibility check process did not account for part-time employees listed on this form. Due to their part-time status, they were considered ineligible for an offer of coverage. The following enhancements address this issue.

Enhancement to the Eligibility Check

Note: Note: To use these new features, you must enable the STATUS.CHG.ELIG custom feature code on the System Parameters form.

[Image: Custom Feature Codes grid, showing STATUS.CHG.ELIG]

The enhanced process treats employees on the ACA Offered Employees form as though they are full-time employees. If they meet the other requirements for ACA plan eligibility (outlined below) the system offers them coverage.

With these enhancements, the system determines eligibility as follows:

  1. Eligibility calculation is triggered for a specific employee and benefit plan.

  2. Is the employee part-time but otherwise eligible for coverage, based on the benefit rule? If yes, continue.

  3. Is the plan eligible under the ACA? (Insurance Class is “Medical” and Do NOT Include in ACA Reporting is not selected). If yes, continue.

  4. Does the employee have an ACA Stability Start and End Date? (Listed on the ACA Offered Employees form). If yes, continue.

  5. Does the Coverage Start Date fall within their stability period? If yes, the employee is eligible for an ACA coverage offer under this plan.

Enhancements to the Employee Benefits Enrollment Form

Whenever you select an employee and a benefit plan on the Employee Benefits Enrollment form, the system runs the eligibility check process to determine if the employee is eligible for that plan.

With these new enhancements, if the employee fails the eligibility check but a future-dated Stability Period is listed on the ACA Offered Employees form, the system displays a message:

Employee not eligible for this benefit until [Stability Period Start Date, MM/DD/YYYY] based on the ACA Offered Employees grid.

If the employee is automatically determined to be eligible under this plan, the Coverage Details panel displays the message “There is an ACA Eligibility Override”.

[Image: There is an ACA Override]

Disabling the Enhancements

You can use a new System Parameters option, called Suppress ACA Eligibility Check, to disable these enhancements.

Note: Note: If you select this option, part-time employees on the ACA Offered Employees form will be considered ineligible for coverage.

[Image: System Param to suppress ACA Eligibility]

For more information about ACA and benefits features in PrismHR, see the ACA User Guide, the Benefits Enrollment User Guide, and the Benefits Administration User Guide.

JIRA # BA-2488, 2646, 2577, 2580

========================================================================

Changes to the Group Benefit Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA-2489%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA-2489 (Epic).htm

Changes to the Group Benefit Plans form

From now on, the Offer Type field will only show the list of compatible options based on the selection made for the Insurance Class field on this form.

There are seven insurance classes that can be assigned to a Group Benefit Plan. The corresponding Offer Types are as follows:

Insurance Class: Medical

Insurance Class: Dental

Insurance Class: Vision

Insurance Class: Life Insurance

Insurance Class: Short-Term Disability

Insurance Class: Long-Term Disability

Insurance Class: Other

Insurance Class: Bond

Note:

When no Insurance Class is available, the Offer Type dropdown lists –Select One– as the only option.

For an existing Offer Type in PrismHR which is not compatible with the Insurance Class selected, PrismHR will now display the words (Not Valid) next to the Offer Type name. If you try to save a Group Benefit Plan record which has a non-compatible Offer Type, the following message displays:

Offer Type “XXXX” is not compatible with the current Insurance Class.

Select a compatible Offer Type from the dropdown or set this field to the default value of “–Select–”. Once you select a compatible Offer Type, the invalid Offer Type is removed from the dropdown list.

JIRA # BA-2511, 2513

========================================================================

Changes to the Benefits Summary Statement Setup form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA-2527.htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA-2527.htm

Changes to the Benefits Summary Statement Setup form

A new checkbox named Display 401k and ROTH 401k Catch-Up Amounts? is introduced on this form as shown in the screenshot below.

[Image: screenshot]

[Image: screenshot]

JIRA # 2527

========================================================================

Tab order updated in the Benefit Rules form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA-2773%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA-2773 (Epic).htm

Tab order updated in the Benefit Rules form

The tab order has been updated on this form to enable you to tab through all the fields in a logical order for data entry, so you don’t have to use the mouse. The tab order now flows through each section in the correct sequence in their entirety before moving on to the next section. Also, within each section, you can now tab all the fields in the left column and then proceed to the next column on the right. If any field that has an associated field to the right of it comes next, before you move on to the next line and keep moving down. Once you have completed the button panel, you will be directed to the main navigation bar.

Following is the screenshot of the tab order for the various sections in this form for your reference.

Section: Benefit Rules

In this section, you must FIRST select a Benefit Group, then a Benefit Plan. When you arrive at this section, the initial field in focus is the Benefit Group.

[Image: screenshot]

Section: Contribution Rules

[Image: screenshot]

[Image: screenshot]

Section: Coverage Rules

[Image: screenshot]

Section: Disability Coverage Rules

[Image: screenshot]

Section: Eligibility Rules

[Image: screenshot]

Button Panel

[Image: screenshot]

JIRA # BA-2851

========================================================================

Benefit Rates Import

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA-314%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA-314 (Epic).htm

Benefit Rates Import

Use this Benefit Rates Import form to initiate a new import or complete an existing import in progress of benefit rates (premium or billing) into PrismHR using a predefined benefit rates import template. You can also view completed benefit rates imports on this form. This benefit rates import process cannot be used to change or overwrite existing benefit rates.

Note: Note: Client Access Group security is not enabled on this form.

To access the form, on the Work Centers panel, under Onboarding & Benefits, click Benefit Imports & Reporting. Under Benefit Imports, click Benefit Rates Import.

[Image: screenshot]

You can also search for this form on the search box in the main navigation search bar.

[Image: screenshot]

This form has the following two sections:

Imports in Progress

When you access this form for the first time, all the tables will be blank and you should select the New Import button to proceed to the Benefit Rates Import Setup & File Import form to define and begin a new benefit rate import.

[Image: screenshot]

User - This field is a dropdown. By default, the user id of the user who has logged in will display here. You can also select a different user from the drop-down.

This section displays all benefit rate imports that are not completed successfully for the selected user. This section will display the last 7 imports in progress at a glance on-screen for the selected user. In case there are more than 7 imports in progress for the selected user, you will see a scroll bar on the right. Scroll to view all the imports in progress for the selected user. The information is displayed in a table that has the following columns:

  1. Name - This is the import name that was provided for that benefit rate import. If you click one of the names, it will take you to the Benefit Rates Import Setup & File Import form for further action to complete the import.

  2. Type - This is the benefit rate type that you are importing for the import. This will be:

a. Premium Rates OR
b. Billing Rates
— —

  1. Plan Used for Template - This is the Benefit Plan ID used for the import template.

  2. Last Modified Date - This shows when this import was last worked upon.

  3. Last Modified User - This shows the user id of the user who worked on the import last.

  4. Status - This shows the status of the import in progress and can be any one of the following:

a. Template Defined – When an import has been defined but no import file is uploaded.
b. Ready for Import - When an import has been defined AND an import file is uploaded.
— —
  1. — Import Errors - When an import attempt has failed. This will produce a Benefit Rate Import Error Report
  1. Error Report - When the Status above is either Template Defined or Ready for Import, this column will display a ‘-’ [dash]. When the Status above is Import Errors, then this column will display a link to open and view the error report for the corresponding import that was not successful. It provides a list of all the errors that this import encountered. You can correct these errors and try again to complete the import. Following is a sample Benefit Rate Import Error Report.

[Image: screenshot]

  1. Actions - If you want to delete an existing import in progress, you can click the Recycle Bin icon. If you select delete, you will receive a verification message stating Are you sure you want to delete this import? This cannot be undone.

New Import - If you want to initiate a new Benefit Rates Import using a predefined benefit rates import template, click this button which will take you to the Benefit Rates Import Setup & File Import screen. All the fields will be blank on that screen. You will need to fill up the necessary fields to set up and complete the import.

Past Imports

This section lists all the benefit rate imports completed successfully for the selected date range. By default the date range is a calendar month ending on the current date. You can manually change the date range. This section will display the last 7 completed imports at a glance on-screen for the selected date range. In case there are more than 7 completed imports for the selected date range, you will see a scroll bar on the right. Scroll to view all the completed imports for the selected date range.

Past Imports that are older than one year (since completion date) are automatically deleted and no longer display in the table.

The completed imports are sorted first by Date Completed and then by Name. The latest imports are listed at the top.

[Image: screenshot]

The information is displayed in a table that has the following columns:

  1. Name - This is the import name that you had provided for that benefit rate import.

  2. Type - This is the benefit rate type that you imported. This will be:

  1. Plan Used for Template - This is the Benefit Plan ID used for the import template.

  2. Date Completed - This is the date when the benefit rate was imported into PrismHR.

  3. Processed by User - This is the user ID of the user who completed the benefit rate import.

  4. Import File - This is the benefit rates import file that was used for the import. Following is a sample import file used for Billing Rates plan type:

[Image: screenshot]

The headers will vary depending on the plan type you are importing.

  1. Import Report - This link will provide you with the Benefit Rates Import Success Report for the import which shows a summary of Plans, records and line items imported that correlate with the total number of successful record imported as reported in the toast message.

[Image: screenshot]

The following is a sample Benefit Rates Import Success Report using the Import File above.

[Image: screenshot]

JIRA # BA-2637,2639, 2641, 2668, 2696, 2865, 2902

Benefit Rates Import Setup & File Import

Use this Benefit Rates Import Setup & File Import form to set up and import new benefit rates (premium or billing) into PrismHR using a predefined benefit rates import template. You also need to use this form to complete existing Imports in Progress.

Note:

Using the New Import button

When you click the New Import button on the Benefit Rates Import form, you come to this form. All fields on this form will be blank.

  1. Complete the following fields:

Note: You cannot manually enter a Plan ID if for that Plan ID the Manual Calculation field is set to Coverage Entered Manually in the Group Benefit Plans form. Since these plans do not have rate tables, there are no rates that can be imported in Group Benefit Plans, and they cannot be supported in the Benefit Rate Import. If try to do it, you will get an error message stating Plan ID has Coverage & Premiums Entered Manually. Not supported for Import. These plans, however, will not show up when you are using the Select Benefit Plan selector.

Please note that:

For Premium Rates import, the following is a sample selector which you can customize according to your needs:

[Image: screenshot]

For Billing Rates import, the following is a sample selector which you can customize according to your needs:

[Image: screenshot]

  1. You can click Cancel at this point to remove all the data in this form and return to the Benefit Rates Import form.

  2. Click Save to save your import template once you have provided a valid input for all the three required fields noted above. A line item is listed in the Imports in Progress section on the Benefit Rates Import form. Upon save, the Import Name field and the rate type become read only. However, you can still edit the Plan ID field. If you do so, you will receive a warning message stating Are you sure you want to change the plan this import is based on? It may affect the plans that can be included in this import. If an import file has been uploaded, it will be removed. You either click Yes or No accordingly.

What is an Import Template Builder?

Based on the benefit plan that you enter in the Plan ID field, you can import numerous benefit plans that have the same setup.

For example, if the Plan ID used to define the template is a plan with Age Banded Medical Rates and Rate Groups for Premium Rates, then a plan with only Age Banded Medical Rates WOULD NOT be included in a Premium Rate Table but WOULD be included in a Billing Rate Table since Rate Groups for Premium Rates is not used for Billing Rates. If BOTH plans do not have any values checked, then these are considered to match.

For example, if you put in a medical Plan that is age banded, any medical, dental and vision plan that is age banded can be imported together. Please note, the benefit plans need to be an exact match. Using the prior example, it cannot be age banded and tobacco banded.

Once you save your import template, the following section shows up on screen where you will see a list of all plans that match the setup as the selected Plan ID. This table is a reference for all the different setups that can be. In our example above, we have selected a medical plan that is age banded, so that column is populated below.

Note: If you now try to change the Plan ID, you will receive a warning message stating Are you sure you want to change the plan this import is based on? It may affect the plans that can be included in this import. If an import file has been uploaded, it will be removed.

Since in our example, we are importing billing rates, therefore we see a Billing Rates Template button below.

[Image: screenshot]

  1. Click the Billing Rates Template button to get the template.

Fill up this template with your import data to prepare your Import File for the import. Following is the billing rates composite rates template from our example for age banded medical plan:

[Image: screenshot]

These are all the fields required for this import. These headers will be unique to a particular type of import.

Note: If you are importing Premium Rates, then you will see the Premium Rates Template button. The headers in the premium rates template will be different from the billing rates template.

[Image: screenshot]

Once you click the Premium Rates Template button the .csv template file will be downloaded on your system. Following is a sample premium rates composite rates template:

[Image: screenshot]

  1. Click the Select File button in the Upload Billing Rates section once you have created your import file.

[Image: screenshot]

  1. Click the Add Files button in the Select files dialog box to select the relevant benefit rates import file for the import from your system.

[Image: screenshot]

PrismHR provides the following import templates based on the selected Benefit Plan ID. For each type of template the validations will vary and so will the error messages.

  1. Click Start Upload once you have added your benefit rates import file for the import to upload it. Once the upload is complete click Close to close the Select files dialog box.

[Image: screenshot]

  1. The file name will display in the Upload Billing Rates section.

[Image: screenshot]

  1. Click the Import Rates button to import the benefit rates into PrismHR. This button will not be visible until the import file has been uploaded. A job progress window opens showing the processing steps.
  1. — If the processing completes without errors, click Close to close the job progress window. When the import is successful, you will be returned to the Benefit Rates Import form and receive a confirmation message. The said import will be listed under the Past Imports section on the Benefit Rates Import form.

[Image: screenshot]

  1. — If the processing completes with errors, click Close to close the job progress window. The Benefit Rate Import Error Report opens up for the import showing all the errors preventing a successful import. You can correct all the listed errors in your import file, delete the existing import file on the system, upload the corrected import file and continue.
  1. Click Close to close this form at any time. If you close this form before successfully completing an import, then the import will be listed under the Imports in Progress section on the Benefit Rates Import form with the appropriate Status. You can click that import anytime to resume your import from where you left off.

If the Status of the Import is:

To validate what was imported, go to the Group Benefit Plans form. Enter the Benefit Plan ID for which you have imported the rates. Select Actions and then select Premium Rates or Billing Rates whichever is applicable. Then complete the information on the form that matches what you imported.

JIRA # BA-2640, 2642, 2645, 2647, 2663, 2704 CSH 2092

========================================================================

Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/BA_Data_Import_Tool_Enhancements_QR202403.htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/BA_Data_Import_Tool_Enhancements_QR202403.htm

Data Import Tool

The following enhancements now reside in the Data Import Tool, which is available on the Operations|Import Processing menu.

New Import Template

A new import template, Eligible ZIP Codes, is now available. For example:

[Image: screenshot]

You can use this import template to import eligible ZIP codes for the client to reduce the amount of manual work required.

Note: The Eligible ZIP Codes import template is only available for service providers.

To import this data and display an on-screen report:

  1. Select Eligible ZIP Codes from the Import Template menu.

  2. Enter or select a Plan ID.

  3. Click Find File to upload the file.

  4. After importing the file a message displays, “File content successfully uploaded and ready to be imported.” Click OK. The imported ZIP codes display and an Import button. For example:

[Image: screenshot]

  1. Click Import. After the import finishes a message displays, “File content successfully imported. View report for details.” Click OK. A Report button displays.

  2. Click Report. An on-screen report displays the imported ZIP codes and their location. (You can also download this report.) For example:

[Image: screenshot]

  1. As part of this import process, the imported ZIP codes now display in the Eligible Zip Codes form, which you can access by selecting Eligible Zip Codes on the Actions menu in the Group Benefit Plans form. For example:

[Image: screenshot]

Note: Note the following when using the Eligible ZIP Codes import template:

Support for FSA/HSA/COM Offer Types

Previously, the system only supported offer types available on the Group Benefit Plans form when using the Plan Comparison Data import template. (This import template allows you to import benefit plan comparison information.)

The system now provides additional support for the FSA, HSA, and Commuter offer types available on the Flex Spend Account Types form.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # BA-2473, BA-2547, and BA-2548

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2003Mar%20QR/VAP%20202403QR.htm Path: BA/Release-Notes/Enhancements/2024/2024 03Mar QR/VAP 202403QR.htm

Other Enhancements

PCP Validation Format

On the Group Benefit Plans form, under the Web Enrollment Parameters section, when you select the Collect PCP Information checkbox, a new field named PCP Validation Format becomes visible. This field is used to validate the Primary Care Physician ID format on the Employee Benefits Enrollment form for the Benefit Plan ID.

[Image: screenshot]

Click the Edit Format link, to open the Edit PCP Validation Format form, where you can enter or edit the format of the Primary Care Physician ID for the selected Benefit Plan ID. The Primary Care Physician ID format can have four types of characters on any position:

[Image: screenshot]

Note: The Edit Format link will not be visible to users who only have Inquiry access to the Group Benefit Plans form.

On the Employee Benefits Enrollment form:

JIRA # BA-3002

Benefit Adjustment Audit

If audit logs for benefit adjustments were formerly displayed on the Employee Details form, then any new logs can now be viewed on the Benefit Adjustments Entry form.

JIRA # BA-2913

Access Billing Rates for Insurance Class “Bond”

JIRA # BA-2912, 2914

========================================================================

Enhancement to Benefit Plan Setup Form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-1316.htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-1316.htm

Enhancement to Benefit Plan Setup Form

A new field, Only apply to S-Corp Principal Employees, now displays in the Fringe Benefit Pay Codes panel on the Benefit Plan Setup form. For example:

[Image: screenshot]

The Only apply to S-Corp Principal Employees field defines whether only S-Corp Principal employees will have the client benefit portion treated as a fringe benefit for the Fringe Benefit Pay Code. Otherwise, this portion is treated as a normal deduction.

Note: Note the following:

For more information, see the in-product help or PrismHR Benefits Administration User Guide.

JIRA # BA-1316 and PD-16716

========================================================================

Enhancement to Benefit Groups Form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-2544.htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-2544.htm

Enhancement to Benefit Groups Form

Users can no longer delete the Primary (1) Benefit Group on the Benefit Groups form, which is the default Benefit Group assigned to all clients. (Previously when this occurred, the Primary Benefit Group would reappear after users saved updates in the Client Details form.)

Note: The system automatically assigns the Primary Benefit Group as “1,” which cannot be changed. (This Benefit Group Name automatically defaults to “PRIMARY,” which can be changed.)

If you enter or select the Primary (1) Benefit Group and click Delete, the following message now displays:

[Image: screenshot]

Click OK to continue.

For more information, see the in-product help or PrismHR Benefits Administration User Guide.

JIRA # BA-2544

========================================================================

Tab Order Updated in Benefit Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-2773%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-2773 (Epic).htm

Tab Order Updated in Benefit Forms

The tab order has been updated in the Benefit forms described below, so you can tab through all the fields in a logical order for data entry and avoid using the mouse.

The tab order now flows through each section in the correct sequence in their entirety before moving on to the next section. Also, within each section, you can now tab all the fields in the left column and then proceed to the next column on the right. If any field that has an associated field to the right of it comes next, before you move on to the next line and keep moving down. Once you have completed the button panel, you will be directed to the main navigation bar.

This enhancement affects the following forms:

Note: To tab in order through the entire form, you must enter or select an existing Employee ID.

Note: To tab in order through the entire form, you must enter or select an existing Employee ID, then select a Dependent ID or click New.

[Image: screenshot]

[Image: screenshot]

Note: To tab in order through the entire form, you must enter or select an existing Employee ID.

JIRA # BA-2953, BA-2954, BA-2961, BA-2962, BA-2963, and BA-2964

========================================================================

New Rate Group Selectors with filters added

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-2906%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-2906 (Epic).htm

New Rate Group Selectors with filters added

Billing Rate Group Selector

Now, upon selecting Billing Rates under the Actions menu on the Group Benefit Plans form, when you click the Rate Group link:

[Image: screenshot]

JIRA # BA-2980, 2994, 2995, 2996, 2997, 2998, 3001, 3008, 3010, 3011

Premium Rate Group Selector

Now, upon selecting Premium Rates under the Actions menu on the Group Benefit Plans form, when you click the Rate Group link:

[Image: screenshot]

JIRA # BA-2981, 3012, 3013, 3015

New Rate Group Selector on the Benefit Plan Setup form

Now on the Benefit Plan Setup form, under the Group Benefits Setup section, when you click the link named:

There is also a filter option available named Group Code or Name in all the rate group selectors noted above to narrow down your search.

JIRA # BA-3259, 2982, 2984, 2983

Alternative Contribution Rate Group

Now, on the Benefit Rules form, and on the Employee Benefit Rule Overrides form when you click the Alternative Contribution Rate Group link:

There is also a filter option available named Group Code or Name.

JIRA # 3070, 3072

========================================================================

Changes to Benefit Imports & Reporting Landing Page

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-2917%20&%203195%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-2917 & 3195 (Epic).htm

Changes to Benefit Imports & Reporting Landing Page

A link to the Data Import Tool form now resides on the Benefit Imports & Reporting landing page. For example:

[Image: screenshot]

You can select this link to immediately access the import templates in the Data Import Tool form, including the following benefits-related import templates:

Note: You must have either Full or Inquiry access set in your User Role for the Data Import Tool form (HRPY.WORK*DATABASE.IMPORT.ENTRY). Otherwise, this link does not display.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # BA-1849

Changes to the Data Import Tool form

Now the Import Template named “Plan Comparison Data” on the Data Import Tool form, include additional fields at the end of the sample header file which can be imported into the fields in the Additional Plan Details section on the Benefit Enrollment Plan Details form. For a particular Offer Type, you can view the names of the fields in the Additional Plan Details section of the Benefit Enrollment Plan Details form under the Category Description column on the Data Import Tool form.

JIRA # BA-2915

Changes to the Group Benefit Plans form

The following three existing fields on the Group Benefit Plans form are now relocated to the Other Processing Parameters section:

  1. Use Extended Precision Risk Factors

  2. Risk Factors Apply To

  3. Risk Factors By Network

JIRA # BA-2439

When a benefit plan is set up to use networks (for billing, premium or both) and a network is then marked as Inactive, the inactive network now displays in the Network ID dropdown with ‘(Inactive)’ next to it. All inactive networks filter to the bottom of the list in the order that they appear on the networks grid.

[Image: screenshot]

You cannot modify or add new rates for Inactive networks. However, you can view existing rates for Inactive networks. When an inactive network is selected, the table is disabled. The Save and Delete buttons are also disabled. A warning message displays stating The selected network is inactive. No modifications can be made. Click the OK button to acknowledge the message.

JIRA # BA-2694, 3318

On the Group Benefit Plans form, under the Actions menu, a new form named Clients Assigned To has been introduced. After you have selected a Benefit Plan ID on the Group Benefit Plans form, the Clients Assigned To form displays the clients assigned to the selected benefit plan. You cannot find this form using normal search means. This form need to be added to your User Role to access this form.

[Image: screenshot]

JIRA # BA-2891, 3200, 3220, 3408

Changes to the Benefit Plan Setup form

From now on the Benefit Plan Setup form, for a Plan Class selected as Group Benefit, the following fields under the Group Benefits Setup section will display a brief description beside each of the following fields when selected:

JIRA # BA-1575

From now on, if no Billing Rate Group has been setup for the Benefit Plan ID selected on the Group Benefit Plans form (meaning that there are no Effective Dates tied to a Rate Group for the Benefit Plan ID in question at the system level), then on the Benefit Plan Setup form, no Billing Rate Groups will display when you click the Billing Rate Group or Pending Billing Rate Group hyperlink and open the Rate Group selector. A warning message will display stating There are no items to display. Click the OK button to acknowledge and close the message and return to the Benefit Plan Setup form.

JIRA # BA-1055

From now on, if no Premium Rate Group has been setup for the Benefit Plan ID selected on the Group Benefit Plans form (meaning that there are no Effective Dates tied to a Rate Group for the Benefit Plan ID in question at the system level), then on the Benefit Plan Setup form, no Premium Rate Groups will display when you click the Premium Rate Group or Pend Premium Rate Group hyperlink and open the Rate Group selector. A warning message will display stating There are no items to display. Click the OK button to acknowledge and close the message and return to the Benefit Plan Setup form.

JIRA # BA-3197

Changes to the Employee Benefit Rule Override form

Also from now on, if no Billing Rate Group has been setup for the Benefit Plan ID selected on the Group Benefit Plans form (meaning that there are no Effective Dates tied to a Rate Group for the Benefit Plan ID in question at the system level), then on the Employee Benefit Rule Override form, no Billing Rate Groups will display when you click the Alternative Contribution Rate Group hyperlink and open the Rate Group selector. A warning message will display stating There are no items to display. Click the OK button to acknowledge and close the message and return to the Benefit Plan Setup form.

JIRA # BA-3199

========================================================================

Import Quick Links Now Available for Benefit Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-2927%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-2927 (Epic).htm

Import Quick Links Now Available for Benefit Forms

Quick links are now available on the following forms to directly access their respective import form or import template in the Data Import Tool:

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

Note: To access the Eligible Zip Codes form, access the Group Benefit Plans form, select a Benefit Plan ID, then select Eligible Zip Codes on the Actions menu.

[Image: screenshot]

Note: To access the Benefit Network Locations form, access the Group Benefit Plans form, select a Benefit Plan ID, then select Network Zip Codes on the Actions menu.

Note: Note the following about these quick links:

For more information, see the in-product help, PrismHR Benefits Administration User Guide, PrismHR Human Resources User Guide, or PrismHR Payroll Administration Guide.

JIRA # BA-2928, BA-2929, BA-2930, BA-2931, BA-2932, BA-2933, and BA-2934

========================================================================

Changes to Benefit Group History

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-2946%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-2946 (Epic).htm

Changes to Benefit Group History

Previously, the Benefit Group History form did not keep a full history causing administrative challenges with future dated changes when manually updating the Benefit Group on the Employee Details form. PrismHR has implemented the following changes to mitigate this from this release:

For entering a past date in the Benefit Group Start Datefield:

For entering a current date in the Benefit Group Start Datefield:

JIRA # BA-2947, 2948, 2949, 2950, 2951, 2952, 3299, 3304

========================================================================

Changes to the Billing & Premium Rate forms for Inquiry Access

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-3032%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-3032 (Epic).htm

Changes to the Billing & Premium Rate forms for Inquiry Access

Users with Inquiry access can view information but cannot make any changes to data. From now on, when you have Inquiry access, you will see the following changes to the fields noted below on the following forms:

BENEFIT.RATES*BENEFIT.FRMED.NETWORK.RATES.MNT

BENEFIT.RATES*BENEFIT.MD.RATES.MNT

BENEFIT.RATES*BENEFIT.MD.NETWORK.RATES.MNT

BENEFIT.RATES*BENEFIT.FRMED.RATES.MNT

BENEFIT.RATES*BENEFIT.FRMED.NETWORK.RG.RATES.MNT

BENEFIT.RATES*BENEFIT.FRMED.RG.RATES.MNT

BENEFIT.RATES*BENEFIT.MD.NETWORK.RG.RATES.MNT

BENEFIT.RATES*BENEFIT.MD.RG.RATES.MNT

BENEFIT.RATES*NETBILL.MD.COMPOS.RATES.MNT

BENEFIT.RATES*NETBILL.MD.RATES.MNT

BENEFIT.RATES*BILLING.MD.RATES.MNT

BENEFIT.RATES*COMBO.BILL.MD.RATES.MNT

BENEFIT.RATES*COMBO.BILL.MD.COMPOS.RATES.MNT

BENEFIT.RATES*BILLING.OTH.RATES.MNT

BENEFIT.RATES*BILLING.FRMED.RATES.MNT

BENEFIT.RATES*BILLING.LI.RATES.MNT

BENEFIT.RATES*BILLING.DI.SALARY.RATES.MNT

BENEFIT.RATES*BILLING.DI.EXT.RATES.MNT

BENEFIT.RATES*BILLING.DI.RATES.MNT

BENEFIT.RATES*BILLING.MD.COMPOS.RATES.MNT

Benefit Plan ID - This field will remain disabled and will be pre-populated with the Benefit Plan ID selected on the Group Benefit Plans form.

Network ID - The drop-down will remain enabled if applicable to the specific form.

Rate Group - The hyperlink and this field will remain disabled. All existing Rate Groups (for the Network ID selected above - if applicable to the specific form) that have rates with an existing Effective Date will be listed on the right side of the form under “Existing Rate Groups”. When a Rate Group is selected from the “Existing Rate Groups” list, that Rate Group will populate in the “Rate Group” field.

Plan Type - This drop-down will remain enabled. (if applicable to the specific form)

Employee Gender - This drop-down will remain enabled if applicable for the specific form. Once you select a gender along with the other applicable choices noted above specific to the form, a list of corresponding Effective Dates for the options selected will populate on the right side of the form under “Existing Effective Dates”. When an Effective Date is selected from the “Existing Effective Dates” list, that date will populate in the “Effective Date” field and the corresponding billing/premium rates will be displayed.

Spouse Gender - This drop-down will remain enabled if applicable for the specific form. Once you select a spouse gender along with the other applicable choices noted above specific to the form, a list of corresponding Effective Dates for the options selected should populate on the right side of the form under “Existing Effective Dates”. When an Effective Date is selected from the “Existing Effective Dates” list, that date will populate in the “Effective Date” field and the corresponding billing/premium rates will be displayed.

Effective Date - This field will remain disabled. Once you select the other applicable choices noted above specific to the form, a list of corresponding Effective Dates for the options selected should populate on the right side of the form under “Existing Effective Dates”. When an Effective Date is selected from the “Existing Effective Dates” list, that date will populate in the “Effective Date” field and the corresponding billing/premium rates will be displayed.

Rate Table - All fields on the table will remain disabled.

Save - This button will remain disabled. You cannot make any changes to the data.

Delete - This button will remain disabled. You cannot make any changes to the data.

Cancel - Use this button to clear the form.

Close - Use this button to close the form.

Action Bar - The Copy from Premium Rates option (if applicable for the specific form) will not display.

JIRA # BA-3056, 3055, 3054, 3053, 3052, 3051, 3050, 3049, 3045, 3044, 3042, 3041, 3040, 3039, 3038, 3037, 3036, 3035, 3034, 3033

========================================================================

Existing Rate Groups display on Premium Rate Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/BA-3285%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/BA-3285 (Epic).htm

Existing Rate Groups display on Premium Rate Forms

For now on, depending upon the parameters selected on the Premium Rates form, a list of Existing Rate Groups that have an Effective Date tied to them for the Benefit Plan ID on that Premium Rates form will display on the right hand side of the form for the following Premium Rate Forms:

Premium Rate Form: BENEFIT.RATES*BENEFIT.MD.RG.RATES.MNT

Premium Rate Form: BENEFIT.RATES*BENEFIT.MD.NETWORK.RG.RATES.MNT

Premium Rate Form: BENEFIT.RATES*BENEFIT.FRMED.RG.RATES.MNT

Premium Rate Form: BENEFIT.RATES*BENEFIT.FRMED.NETWORK.RG.RATES.MNT

Benefit Plan ID - This field will remain disabled and will be pre-populated with the Benefit Plan ID selected on the Group Benefit Plans form.

Network ID - Use the drop-down to select a network if applicable to the specific form.

Rate Group - All existing Rate Groups (for the Network ID selected above - if applicable to the specific form) that have rates with an existing effective date will be listed on the right side of the form under “Existing Rate Groups”. When a Rate Group is selected from the “Existing Rate Groups” list, that Rate Group will populate in the “Rate Group” field. You can also click the Rate Group hyperlink to select a rate group from the Select Rate Group dialog box.

Plan Type - Use the drop-down to select a network if applicable to the specific form.

Effective Date - This field will remain disabled. Once you select the other applicable choices noted above specific to the form, a list of corresponding Effective Dates for the options selected should populate on the right side of the form under “Existing Effective Dates”. When an Effective Date is selected from the “Existing Effective Dates” list, that date will populate in the “Effective Date” field and the corresponding premium rates will be displayed.

Rate Table - All fields on the table will remain disabled.

Save - Use this button to save any changes that you have made to a premium rate group.

Delete - Use this button to delete a premium rate group.

Cancel - Use this button to clear the form.

Close - Use this button to close the form.

Following is a sample premium rate group form. The fields displayed on your premium rate group form will vary according to the Benefit Plan ID selected on the Group Benefit Plans form and other selections made there.

[Image: screenshot]

JIRA # BA-3286, 3287, 3288, 3289

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2006Jun%20QR/Other%20Enhancements%20BA202406.htm Path: BA/Release-Notes/Enhancements/2024/2024 06Jun QR/Other Enhancements BA202406.htm

Other Enhancements

Benefit Adjustments Warning Range

You can now configure a system-level range of acceptable benefit adjustment amounts. If a range is specified, the system displays a warning when manual or imported benefit adjustment amounts fall outside the range.

Enter the values in the Benefit Adjustment Warning Range, located on the System Parameters form. The warning displays if the following fields contain a value outside the range:

For more information, see the System Administration User Guide and the Payroll Administration User Guide.

JIRA # WSP-12, 13, 14

Enhancements to the Benefit Plan Setup Form

Most PrismHR forms support navigating from field to field with the Tab key. However, on this form, pressing Tab caused the cursor to jump around the page unexpectedly. The tabbing pattern was improved for this form so the cursor now advances in a logical order from field to field.

JIRA # WSP-16

Enhancements to the Group Benefit Plans Form

In the Carrier Code Maintenance panel of the Group Benefit Plans form, you can now include the Carrier Policy ID.

Note: Note: The Carrier Policy ID and Carrier Group Number are distinct identifiers.

JIRA # WSP-25

Enhancements to the Retirement Adjustments Import

The Retirement Adjustments Import now applies the same validations as the Retirement Register Adjustment form, and generates the same kind of errors. This process creates a new voucher for each valid entry on the import, and updates the appropriate retirement registers and reports.

In addition, the import Preview and Sample Header File were updated to reflect the new optional import columns.

[Image: Updated preview panel for the Retirement Adjustments Import, with new and renamed columns.]

The table summarizes the changes to the columns.

Column Title Details
Client ID
Employee Changed from: SSN/EE ID
Employer ID New
Plan Changed from: Retirement Plan ID
Adjustment Date (MM/DD/YYYY) Changed from: Trans Date (MM/DD/YYYY)
Annotation (Optional) Changed from: Annotation
Retirement Earnings (Optional) New
Employee Contribution (Optional) New
Catch-up Contribution (Optional) New
Post Tax Contribution (Optional) New
ROTH Contribution (Optional) New
ROTH Catch-up Contribution (Optional) New
Matching Contribution (Optional) Changed from: Matching Amount (Optional)
Non-Elect Contribution (Optional) Changed from: Non-Elect Amount (Optional)
Safe Harbor Type 1 Match (Optional) Changed from: Safe Harbor Type 1 Match
Safe Harbor Type 2 Match (Optional) Changed from: Safe Harbor Type 2 Match
Successor Retirement Deferral (Optional) New
Successor Catch-up Deferral (Optional) New
Successor ROTH Deferral (Optional) New
Successor ROTH Catch-up Deferral (Optional) New
Loan (Optional) New
Loan Payment (Optional) New

JIRA # WSP-15, 18

New Wash Rule Option “End of Month”

On the Benefit Plan Setup form, the Wash Rule Date On/Before now supports an option called “End of Month”. If selected and an employee is enrolled in a group benefit plan mid-month, the system creates benefits charges for the entire month.

Note: Note: During terminations, if the client benefit plan’s Coverage Ends On option is set to “End of Month Following Termination Date”, the new wash rule setting has no impact. However, any other Coverage Ends On option will cause the system to generate a full month’s charge upon termination.

JIRA # WSP-313

Bug Fixes

Jira # Issue Resolution
WSP-27 For group benefit plans with Insurance Class set to “Bond”, an issue with two different forms in the Actions menu (Billing Rates and Premium Rates) prevented deleting the Effective Date value on those forms. This is fixed and the Effective Date now deletes successfully.
WSP-340 The Retirement Adjustments Import did not respect user-level client access security, allowing data imports to prohibited clients. This is fixed. Now, users can only import adjustments for clients allowed by their client access setup.

========================================================================

New Employee Selector added

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-2837%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-2837 (Epic).htm

New Employee Selector added

The new Employee Selector has have been added to the following forms:

[Image: screenshot]

JIRA # BA-3403, BA-3413, BA-3414, BA-3415, BA-3416, BA-3616, BA-3617

========================================================================

Changes to the Client Benefit Plan Defaults form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3077%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3077 (Epic).htm

Changes to the Client Benefit Plan Defaults form

The layout of this form has been completely changed. The purpose of this form is to allow you to set up benefit plans in bulk for multiple clients at once. You can create templates for repeated use or set up a template for one time use. This makes it convenient for customers who bring in new clients and have standard plans for them. You will not have to go to the Benefit Plan Setup form for each client to set up those standard benefit plans but can do that in bulk instead using the Client Benefit Plan Defaults form.

Following is a sample of the Client Benefit Plan Defaults form.

[Image: screenshot]

Complete the following steps to assign benefit plans to clients:

Field Name Description
Saved Plan Defaults This field is optional. If you already have saved plan defaults that you want to apply to other clients, enter it here or you can click the Saved Plan Defaults hyperlink to open the Select Saved Benefit Plan Defaults dialog box and select one from there. Once a default plan is selected here the Last Updated date and time for the default plan template will display.
Plan ID If you are using the Saved Plan Defaults field above, then this field will be pre-populated with the selected plans. You can make changes like add plans or delete them. The Save Plan Defaults button shown above will not display in this case, but the following buttons will display: - Save Changes - Select this button if you make further changes to the existing template. - Save as New - Select this button if you made changes to the existing template and want to save it as a different template. This will bring up the Save Benefit Plan Defaults form. - Delete - Select this button to delete the existing template. If not, then enter the Plan ID here or click the Select Plan hyperlink and select one or more plans from the Select Plan dialog box. The following details of all plan defaults selected will reflect on the right of the Client Benefit Plan Defaults form to provide an at a glance view of the numerous plans and their setups. In case there are more than three plans selected, you can scroll to view them all. - Plan ID - Plan Description - Billing Rate Group - Premium Rate Group - Rule Template ID - One Month Prepay : You cannot enable Prepay when Billing Wash Rule is used. - Add One Month for Prepay : You cannot enable Prepay when Billing Wash Rule is used. - Annual Periods - Use Billing Wash Rule : You cannot enable Billing Wash Rule when Prepay is used. - Wash Rule Date On/Before - Cafe Plan Eligible - Coverage Ends On - Benefit Billing Frequency - Pay Deduction Frequency

========================================================================

Alternative Contribution Rate Group field validations added to the Benefit Rules form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3104%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3104 (Epic).htm

Alternative Contribution Rate Group field validations added to the Benefit Rules form

We have now added the following validations to the Alternative Contribution Rate Group field on the Benefit Rules form:

JIRA # BA-3067

Alternative Contribution Rate Group field validations added to the Employee Benefit Rule Overrides form

We have now added the following validations to the Alternative Contribution Rate Group field on the Employee Benefit Rule Overrides form:

JIRA # BA-3068

========================================================================

Changes to the Tax Rates for Taxable Life Coverage form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3107%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3107 (Epic).htm

Changes to the Tax Rates for Taxable Life Coverage form

The following changes were made to the Tax Rates for Taxable Life Coverage form which you can access from the

[Image: screenshot]

menu on the System Parameters form.

[Image: screenshot]

Note: Note:

If you pull up an existing tax year record (say 2023), make changes but do not save the record and click the Copy Rates hyperlink, you will receive a warning message stating There are unsaved changes that will not be copied. Do you wish to continue?

The Tax Rates for Taxable Life Coverage form now also has the following buttons:

Cancel - Click Cancel to clear the form at any time. All unsaved changes will be lost.

Close - This button is displayed when this form is opened in a modal. Click Close to close the form. All unsaved changes will be lost.

JIRA # BA-3157, BA-3434

========================================================================

Calculate Safe Harbor 2 Match automatically during New Hire

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3127%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3127 (Epic).htm

Calculate Safe Harbor 2 Match automatically during New Hire

Given that an employee is hired into a Client which has a Retirement Plan that is not setup to auto enroll but has a Safe Harbor 2 Match or a non-elective match defined, during the new hire process, an eligibility calculation will be triggered which then creates an Eligible Unenrolled Retirement Plan enrollment record for the applicable employees with an effective date that coincides with their calculated eligibility date. Once the first payroll processes that coincides with their eligibility date, the record will be flipped to an Active Enrollment and the match taken.

The setups that will trigger the auto enroll of the Safe Harbor 2 / Non Elective matches are:

JIRA # BA-3505

========================================================================

Rate Group selector search functionality to include Group Name

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3256%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3256 (Epic).htm

Rate Group selector search functionality to include Group Name

The Billing Rate Group selector now allows you to search by Group Name along with Group Code. Previously, this filter option only searched by Group Code when populating data in the table.

[Image: screenshot]

The following fields will be using this enhanced selector:

The Premium Rate Group selector now allows you to search by Group Name along with Group Code. Previously, this filter option only searched by Group Code when populating data in the table. The following fields will be using this selector:

JIRA # BA-3257, BA-3258

========================================================================

Changes to the Benefit Plan Setup form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3279%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3279 (Epic).htm

Changes to the Benefit Plan Setup form

Now if you have “Inquiry” access, for the Benefit Plan Setup form, after you have selected Group Benefit for the Plan Class field and selected a Plan, you will not be able to edit any one of the following fields:

JIRA # BA-1068

The following validation are now enforced on the Benefit Plan Setup form:

JIRA # BA-3542

View HSA/DEP Deduction Carryover Calculation on Processed Payroll Vouchers

Previously, you could view the HSA/DEP Deduction Carryover calculation summary (trace log), when it existed, using the link on the Deductions tab on calculated payroll vouchers. Now you can view the HSA/DEP Deduction Carryover calculation summary (trace log), when it exists, using the link on the Deductions tab of processed payroll vouchers also.

JIRA # BA-3281

Changes to the Flex Spend Account Types form

On this Flex Spend Account Types form, under the Flexible Spending Accounts section the Stamp Term Date as Override Stop Date At EE Term? field has now been renamed to Stamp Date Used as Override Stop Date When EE is Terminated.

[Image: screenshot]

This field now has the following drop-downs:

JIRA # BA-1674

Changes to the Benefit Groups form

On this Benefit Groups form, after you have entered a Benefit Group, under the

[Image: screenshot]

menu, the form named Employees Assigned To has been redesigned. Use this form to view all employees who are assigned to the selected Benefit Group for the client. If you do not enter a Benefit Group and try to open the Employees Assigned To form, you will receive an error stating You must enter a benefit Group first!

You cannot search this form using normal search means.

[Image: screenshot]

The Benefit Group and the Group Name will be listed on this form.

The Active employee count displays the number of active employees assigned to the selected Benefit Group regardless of the filter option selected for the Status field below.

Status : By default the total number of Active employees assigned to the selected Benefit Group will be listed here. You can change this to any one of the options from the drop-down.

The grid will have the following columns:

Employee ID :- If you click on this hyperlink, the Employee Details form opens for the employee.

Employee Name : The employee name is listed here.

Employment Status : The employment status of the employee will display here.

You can sort this grid by any of the three headers noted above.

You can scroll to see all employees on a page. There are 11 employees listed per page. If there are more than 11 employees listed, then you can scroll to subsequent pages.

Click Close to close this form and return to the Benefit Groups form.

JIRA # BA-1641

========================================================================

Support for Spanish

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3314%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3314 (Epic).htm

Support for Spanish

PrismHR is enhancing its support for Spanish. The following new optional fields are introduced which will accept Spanish characters on the following forms:

JIRA # BA-3336, BA-3365, BA-3366, BA-3367, BA-3368, BA-3369, BA-3390, BA-3628

========================================================================

60-63 Catch Up

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3398%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3398 (Epic).htm

60-63 Catch Up

The Secure 2.0 Act includes a new provision taking effect from January 1, 2025 where employees turning between 60 and 63 during the tax year are provided a higher catchup contribution limit. PrismHR now supports this feature.

On the Tax Year Limits Maintenance form (System Parameters>Actions>Tax Year Limits) AND on the Retirement Plans form, under the Plan Year Deferral Limits section a new column named 60-63 Catch Up is introduced after the Catch Up Limit column.

You will be able to enter and save value in this field if you have full access to the forms.

This field is optional.

This field will only accept numerical values.

JIRA # BA-3423, BA-3424

========================================================================

New Button Styles introduced

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3442%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3442 (Epic).htm

New Button Styles introduced

PrismHR has adopted a new button style as shown below. If the form if opened as a modal, then there will be additional Close button.

[Image: screenshot]

JIRA # BA-3333, BA-3441, BA-3442, BA-3538, BA-3543, BA-3570, BA-3572, BA-3573, BA-3574, BA-3575, BA-3576

========================================================================

New Plan ID Selector added

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/BA-3532%20&%20BA-3541%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/BA-3532 & BA-3541 (Epic).htm

New Plan ID Selector added

The new Plan ID selector as shown below has have been added to the following forms:

HSA Form | Benefit Plan Setup

HSA Form | HSA Plan Years

HSA Form | HSA Plans

Flexible Spending Form | Benefit Plan Setup

Flexible Spending Form | Section 125 Plan Years

Flexible Spending Form | Section 125 Benefit Plans

Retirement Form | Retirement Register Adjustment

Retirement Form | Employee Retirement Plan Register

Retirement Form | Retirement Plan Enrollment

Retirement Form | Benefit Plan Setup

Retirement Form | Bulk Change Retirement Plan

Retirement Form | Retirement Plans

[Image: screenshot]

JIRA # BA-3549, BA-3550, BA-3551, BA-3552, BA-3553, BA-3554, BA-3555, BA-3556, BA-3558, BA-3561, BA-3562, BA-3563

========================================================================

New View Deduction/Bill Codes Link

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/WSP-126%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/WSP-126 (Epic).htm

A new link, View Deduction/Bill Codes, now displays on the Benefit Plan Setup form when you select the Group Benefit option in the Plan Class field. For example:

[Image: screenshot]

After selecting the Plan ID and Status, selecting the View Deduction/Bill Codes link opens the Plan Deduction and Billing Codes form. For example:

[Image: screenshot]

The Plan Deduction and Billing Codes form displays the deduction codes used for the selected plan. In addition, this form displays whether the plan is set up as a Section 125 plan, which assists in determining the deduction code for most enrollees.

Note: The Section 125 Eligible field is enabled on the Group Benefit Plans form.

For more information, see the in-product help or PrismHRBenefits Administration User Guide.

JIRA # WSP-523

========================================================================

Updates to States Offered In Panel

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/WSP-138%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/WSP-138 (Epic).htm

Updates to States Offered In Panel

The following updates now reside on the States Offered In panel on the Group Benefit Plans form:

[Image: screenshot]

For more information, see the in-product help or PrismHRBenefits Administration User Guide.

JIRA # WSP-375

========================================================================

New Officer Details Link

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/WSP-211%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/WSP-211 (Epic).htm

A new link, Officer Details, now displays on the Employee Benefits Enrollment form for selected employees who are designated company officers. For example:

[Image: screenshot]

Note: The Officer Details link only displays if at least one of the four conditions that display in the bottom half of the dialog below is enabled (that is, set to “Yes”).

Selecting the Officer Details link opens a read-only dialog where the following information displays:

[Image: screenshot]

Note: This information is based on the selections on the Tax tab and the Work tab in the Employee Details form for the selected employee.

This enhancement is helpful in determining whether an employee should have a pre-tax deduction based on company officer status by adding more visibility about their officer status and the company type (for example, C-Corporation, LLC, or S-Corporation).

For more information, see the in-product help or PrismHRBenefits Administration User Guide.

JIRA # WSP-579

========================================================================

New Deduction Code Field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/WSP-212%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/WSP-212 (Epic).htm

New Deduction Code Field

A new field, Deduction Code, now displays on the Employee Benefits Enrollment form. For example:

[Image: screenshot]

The read-only Deduction Code field indicates the deduction codes used in the employee’s benefits enrollment. (The system references these deduction codes from the Group Benefit Plans form for the selected plan.)

Note: Note the following:

JIRA # WSP-573

========================================================================

New EDI File Field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/WSP-315%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/WSP-315 (Epic).htm

New EDI File Field

A new field, EDI File, now resides on the Group Benefit Plans form. For example:

[Image: screenshot]

You can enable the EDI File field to include the group benefit plan in the EDI file feed.

Note: The system only uses this field for reporting/tracking purposes.

For more information, see the in-product help or PrismHRBenefits Administration User Guide.

JIRA # WSP-314

========================================================================

Changes to the Employee Benefit History form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/WSP-344.htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/WSP-344.htm

Changes to the Employee Benefit History form

Previously, the Employee Benefit History form did not capture the complete benefit coverage history sequence. For example, when an employee waived coverage, then elected Employee Only Coverage, and then changed to Employee and Spouse coverage, then terminated coverage, then elected Family coverage, then terminated employment etc. Besides, if an active employee was terminated and then rehired to become active again, the Employee Benefit History form did not demonstrate the gap in coverage. It appeared as if the employee was having continuous coverage from the original Coverage Starts date.

PrismHR has now implemented a common utility program to generate the employee benefit history records that will solve the above issues.

Note: Note: You must DELETE the terminated record and create a new active, eligible, or waived record for the history to display. This will allow the record to reflect the accurate start date for the latest active record.

On the Employee Benefits Enrollment form, after you have selected an Employee and a Benefit Plan, under the

[Image: screenshot]

menu, click History to open the Employee Benefit History form.

[Image: screenshot]

From the above example, every blank status denotes an enrollment. The other statuses like Terminated, Waived etc. are self explanatory which show different Coverage Starts date.

As earlier, you can click on the different Sequences to view the status in detail on the Employee Benefit History Detail form.

Note: Note: Currently, COBRA enrollments & deletions are not being captured by this utility.

JIRA # WSP-344

========================================================================

New Terminated - COBRA Data Field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2009Sep%20QR/WSP-590%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 09Sep QR/WSP-590 (Epic).htm

New Terminated - COBRA Data Field

A new data field, Terminated - COBRA, now displays on the Employee Benefits Enrollment form. For example:

[Image: screenshot]

The Terminated - COBRA data field automatically displays when the employee moves from a COBRA status to a Terminated status, indicating that the termination status is a termination from COBRA. (This data field is useful in differentiating between coverage termination to offer COBRA and coverage termination after the employee has elected COBRA and subsequently terminates COBRA coverage.)

Note: If you subsequently change the employee’s status from Terminated back to COBRA, this data field no longer displays.

For more information, see the in-product help or PrismHRBenefits Administration User Guide.

JIRA # WSP-587

========================================================================

Changes to the Employee Dependents form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2010Oct%20MR/BA-3521.htm Path: BA/Release-Notes/Enhancements/2024/2024 10Oct MR/BA-3521.htm

Changes to the Employee Dependents form

The Close button has been added to the Employee Dependents modal form.

[Image: screenshot]

JIRA # BA-3521

========================================================================

Changes to the Relationships form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-1127%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-1127 (Epic).htm

Changes to the Relationships form

Additional validation has been added when deleting an existing Relationship Code on the Relationships form. Now:

JIRA # BA-2988

Changes to the Group Benefit Plan Types form

Additional validations have been added when deleting an existing Type Code on the Group Benefit Plan Types form. Now:

JIRA # BA-3815

Now you cannot enter a zero in the Type Code field on the Group Benefit Plan Types form. If you do, you will get an error message stating Invalid Type Code. Click OK. The zero will be removed from the Type Code field.

JIRA # BA-3933

Changes to the Group Benefit Plans form

Additional validation has been added when deleting an existing Type Code under the Plan Types section on the Group Benefit Plans form. Now:

JIRA # BA-3816

Changes to the Benefit Plan Setup form

JIRA # BA-3821

Now you cannot delete a benefit plan using the Benefit Plan Setup form if there are existing benefit rules for that Plan ID for the client as this will orphan the associated benefit rules and can cause payroll errors along with other issues. If you try to delete a benefit plan from the Benefit Plan Setup form and if there are existing benefit rules for that Plan ID for the client, you will receive an error stating There are Benefit Rules assigned to this benefit plan. Please remove all rule references. You can only delete a benefit plan from the Benefit Plan Setup form if there are no existing benefit rules for that Plan ID for the client or after you have removed all the benefit rules for that Plan ID for the client.

JIRA # BA-3822

Now you cannot delete a benefit plan using the Benefit Plan Setup form if there are associated Employee Benefit Enrollment records for the client for the selected Plan ID that have a status of Active, Terminated, or COBRA as this will orphan the associated Employee Benefit Enrollment records and can cause payroll errors along with other issues.

You can only delete a benefit plan from the Benefit Plan Setup form if there are no associated Employee Benefit Enrollment records for the client for the selected Plan ID that have a status of Active, Terminated, or COBRA.

JIRA # BA-3823

Changes to the Benefit Rules form

JIRA # BA-3824

========================================================================

Changes to the Employee Dependents form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3364%20&%203676%20(Epics).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3364 & 3676 (Epics).htm

Changes to the Employee Dependents form

The earlier Phone field under the Address Details section on the Employee Dependents form is renamed to Primary Phone.

JIRA # BA-3932

Changes to the Benefit Plan Setup form

New fields added

As part of the SECURE 2.0 Act, a new auto-enrollment requirement goes into effect on January 1, 2025, giving employers time to prepare and update their plans to comply with new regulations. New 401(k) and 403(b) plans established after the passing of SECURE 2.0 (December 29, 2022) must automatically enroll all eligible employees at a default contribution rate between 3 and 10%. In addition to auto-enrollment at a default contribution rate, plans must also automatically escalate contributions by 1% each year until they reach a predetermined rate by the employer (between 10 and 15%).

Note: Note: Though we put in the fields, but there is not yet any logic tied to these. No auto escalation will occur at this time. This is prep work to allow Service Providers to begin entry of these provisions prior to the effective date.

[Image: screenshot]

On the Benefit Plan Setup form, after you select the Plan Class as Retirement, and after you have checked the Auto Enrollment field, the following additional fields will display:

Field Name Description
Auto Escalator This field will only display if the Auto Enrollment field is checked for a Retirement Plan. - Unchecked - (Default) Plans will not automatically escalate contributions annually. - Checked - In addition to auto-enrollment at a default contribution rate, plans will automatically escalate contributions by 1% each year until they reach a predetermined rate by the employer (between 10 and 15%).

Changes to the Hawaii 1.5% Rule section

From now on, the Hawaii 1.5% Rule section will only display on the Benefit Plan Setup form for Plan Class selected as Group Benefit. For all other Plan Class, this section will not display on the Benefit Plan Setup form.

JIRA # BA-3793

Changes to the Retirement Plan Enrollment form

On the Retirement Plan Enrollment form, under the Election Details section, a new field named Auto Escalation is available to indicate whether Auto Escalation applies to an Elective Percent. This field will display only if the Auto Escalator field is checked for this retirement plan on the Benefit Plan Setup form.

[Image: screenshot]

JIRA # BA-3812

Changes to the Client Details form

The Secure 2.0 Act includes a new provision taking effect January 1, 2025, where employees turning between 60 and 63 during the tax year are provided with a higher catchup contribution limit. Like “normal” catchup, this is expected to be a standard, but not a guaranteed plan feature. This means that you need the capacity to “turn off” this functionality at the client level.

PrismHR now supports this requirement.

[Image: screenshot]

On the Client Details form, under the Benefits tab, under the Group Benefits section, a new field named Disable Accelerated Catchup? has been added.

JIRA # BA-3596

========================================================================

Updated Benefit Plan Selector

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3544%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3544 (Epic).htm

Updated Benefit Plan Selector

A new filter named HDHP (High Deductible Plan) is added to the Benefit Plan Selector. It has the following dropdown options:

[Image: screenshot]

This updated Benefit Plan selector has been applied to the following:

The Benefit Plan ID and the Domestic Partner Plan hyperlinks under the Group Benefit Plans section on the Group Benefit Plans form.

The Plan hyperlink under the Benefit Plan Setup section on the Benefit Plan Setup form.

The Benefit Plan ID hyperlink on the Participation Requirement Maintenance form.

The Benefit Plan ID hyperlink on the Default Network By Benefit Plan form.

JIRA # BA-3704, BA-3705, BA-3706, BA-3707, BA-3722

Updated Network Zip Codes form

[Image: screenshot]

The following updates are made to this form:

JIRA # BA-3708

New Benefit Plan ID Selector created

[Image: screenshot]

The new selector shown above is added to the following fields:

Once you click any of the hyperlinks, the Benefit Plan selector opens (as shown above) which displays the list of Group Benefit Plans offered by the client. You can use the various filters on the Benefit Plan selector to refine your search, for example Plan ID or Name. You also use the following additional filters:

The following update was also made to the Adjustment Details form:

JIRA # BA-3713, BA-3714, BA-3715, BA-3716

========================================================================

Secondary Email Address added to the Payees form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3615%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3615 (Epic).htm

Secondary Email Address added to the Payees form

A new optional field named Secondary Email Address has been added to the Payees form as shown below so that customers can enter the email address of the COBRA contact or other contacts as needed. This field is a freeform text field which displays for all Payee Types.

[Image: screenshot]

JIRA # BA-3510

========================================================================

Changes to the Benefit Adjustments form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3645%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3645 (Epic).htm

Changes to the Benefit Adjustments form

[Image: screenshot]

JIRA # BA-3724, BA-3893

Changes to the Adjustment Details form

[Image: screenshot]

JIRA # BA-3726, BA-3727, BA-3728, BA-3891

Changes to the Benefit Adjustment Report

[Image: screenshot]

Please note the following changes to the Benefit Adjustment Report:

JIRA # BA-3810

Changes to the Data Import Tool

[Image: screenshot]

On the Data Import Tool form, for the Benefit Adjustments Import Template, the Category Description Cycles Billed which was Column 10 is now removed.

This change will also reflect when selecting Download Sample Header File. The Sample Header File will now have 12 column headers instead of 13 earlier. When importing new Benefit Adjustment records, Cycles Billed will no longer be included as a column that you can enter a value for. Cycles Billed will automatically be set to 0 for each imported Benefit Adjustment record.

JIRA # BA-3894

========================================================================

New Benefit Selector applied to different benefit forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3663%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3663 (Epic).htm

New Benefit Selector applied to different benefit forms

A new Benefit Group selector has been introduced and applied to various benefit forms to provide a consistent user experience.

[Image: screenshot]

The above benefit selector is now applied to the following:

The Benefit Group hyperlink under the Benefit Groups section on the Benefit Groups form. The Group hyperlink on this form is renamed to Benefit Group.

The Benefit Group hyperlink under the Hawaii 1.5% Rule section on the Benefit Plan Setup form.

The Benefit Group hyperlink on the Eligibility By Benefit Group form. The Group hyperlink on this form is renamed to Benefit Group.

The Benefit Group hyperlink under the When hiring employees assigned to this position: section on the Positions form.

The Benefit Group hyperlink under the Retirement Match Rules section on the Retirement Match Rules form.

The New Benefit Group hyperlink on the Benefit Group Change form.

The Benefit Group hyperlink under the Employment Details section on the New Hire form.

The Benefit Group hyperlink under the Employment Details section on the Rehire form.

The Benefit Group hyperlink on the Terminated Take-On Employee Entry form.

The Benefit Group hyperlink on the Terminated Take-On Employee Maintenance form.

The Benefit Group hyperlink on the PTO Auto-Enrollment Rules Maintenance form.

The Benefit Group hyperlink under the Lowest Cost Calculation Table section on the Client ACA Parameters (Overrides) form. The Benefit Group ID hyperlink on this form is renamed to Benefit Group.

JIRA # BA-3693, BA-3694, BA-3695, BA-3696, BA-3697, BA-3703, BA-3734, BA-3735, BA-3736, BA-3737, BA-3738, BA-3739

========================================================================

Consistent Dropdown displays applied to filters

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3669%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3669 (Epic).htm

Consistent Dropdown displays applied to filters

The field ID along with the field description now appears as a dropdown option for easy reference and selection for different types of filters across various forms wherever applicable. This concatenation can be of the Plan ID and Plan Description for the or existing filter as shown on the Benefit Plan Setup form below, or a concatenation of the Employee Type ID and Employee Type Description for the Employment Type filter on the Retirement Plans form or any other such filters on any other form.

[Image: screenshot]

Following is the list of forms where such filters are applied:

JIRA # BA-3786, BA-3787, BA-3788, BA-3789, BA-3790, BA-3792, BA-3794, BA-3795, BA-3796, BA-3797, BA-3799, BA-3800, BA-3801, BA-3802, BA-3803, BA-3804, BA-3805

========================================================================

Changes to the Retirement Plan Enrollment form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3670%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3670 (Epic).htm

Changes to the Retirement Plan Enrollment form

Change to the Action menu

On the Retirement Plan Enrollment form, after you have selected the Employee field, the Loan details option will no longer display under the

[Image: screenshot]

menu. On the User Roles form, the Loans Details / EMPLOYEE.401K.PLANS.LOANS*INQUIRY is no longer an available option for Service Provider or Worksite Manager user role types.

JIRA # BA-3859

A new Quicklink to the Employee Retirement Plan Register form is added on the top right of the Retirement Plan Enrollment form, which will display only after the Employee and the Retirement Plan fields are selected on the Retirement Plan Enrollment form. This provides ease of access to the Employee Retirement Plan Register form for the selected employee directly from the Retirement Plan Enrollment form.

[Image: screenshot]

When you click the Quicklink to the Employee Retirement Plan Register form from the Retirement Plan Enrollment form, the Employee Retirement Plan Register form opens in a modal where:

Note: Note: This Quicklink will not be visible if you do not have access to the Employee Retirement Plan Register form.

JIRA # BA-3749, BA-3867

New Sections added

After the Employee Overrides/Deferral section, the following two new sections are added to the Retirement Plan Enrollment form.

[Image: screenshot]

Employee Retirement Loans section

Now you can directly access existing employee retirement loan information for the selected Employee, for the Retirement Plan field selected on the Retirement Plan Enrollment form and processed for the selected client using this form. If an employee has been in more than one retirement plan, only those Employee Retirement Loans that were processed for the selected Retirement Plan field will display. This section lists the employee retirement loans for the selected employee in an ascending order by Loan No. by default. This grid has the following columns:

You can click on any of the column headers in the grid to sort the retirement loans as you choose.

JIRA # BA-3746, BA-3857, BA-3948, BA-3880

Retirement Register Adjustments section

Now you can access existing employee retirement register adjustment information for the selected Employee, for the Retirement Plan field selected on the Retirement Plan Enrollment form and processed for the selected client using this form. If an employee has been in more than one retirement plan, only those Retirement Register Adjustments that were processed for the selected Retirement Plan field will display. This section lists the existing employee retirement register adjustments in an ascending order by Transaction No. by default. This grid has the following columns:

You can click on any of the column headers in the grid to sort the retirement register adjustments as you choose.

JIRA # BA-3747, BA-3948

JIRA # BA-3748

========================================================================

Changes to the Employee Flexible Spending Accounts form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/BA-3671%20(Epic).htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/BA-3671 (Epic).htm

Changes to the Employee Flexible Spending Accounts form

Changes to the Action menu

The Flexible Spending Accounts Reimbursement form is now listed under the

[Image: screenshot]

menu, on the Employee Flexible Spending Accounts form. This link will not be visible if you do not have access to the Flexible Spending Accounts Reimbursement form.

JIRA # BA-3863

A new Quicklink to the Employee Flexible Spending Accounts Inquiry form is added on the top right of the Employee Flexible Spending Accounts form. This Quicklink will only display after you have selected the Employee and the Plan Year fields on the Employee Flexible Spending Accounts form. This provides ease of access to the Employee Flexible Spending Accounts Inquiry form for the selected employee and plan year directly from the Employee Flexible Spending Accounts form. The Employee Flexible Spending Accounts Inquiry form will have the Employee and the Plan Year fields auto-populated from the Employee Flexible Spending Accounts form and will be read only.

Note: Note: This Quicklink to the Employee Flexible Spending Accounts Inquiry form will not display on the Employee Flexible Spending Accounts form if you do not have access to the Employee Flexible Spending Accounts Inquiry form.

JIRA # BA-3745

[Image: screenshot]

Changes to the Flexible Spending Account Activity section

Under the Flexible Spending Account Activity section on the Employee Flexible Spending Accounts form, all the valid vouchers listed are now hyperlinks. You can click the click the hyperlink to open the corresponding payroll voucher for the employee. When a voucher is automatically created due to the carry forward process, the voucher number is displayed as 00000 which is not a valid voucher number. No hyperlink is displayed for these vouchers.

JIRA # BA-3744

========================================================================

Changes to the Benefit Rules form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/WSP-227.htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/WSP-227.htm

Changes to the Benefit Rules form

New labels as shown below have been added for the different contribution fields for users to clearly understand which ones are employee contributions and which ones are employer contributions for each plan type. This label addition is for better visibility with no change to existing functionality.

[Image: screenshot]

JIRA # WSP-227

========================================================================

Changes regarding the Offer Type field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2024/2024%2011Nov%20QR/WSP-657.htm Path: BA/Release-Notes/Enhancements/2024/2024 11Nov QR/WSP-657.htm

Changes regarding the Offer Type field

The Offer Type field will become a required field in the Q1 2025 quarterly release. So, from now on, you will get a warning message as shown below when you enter a plan with a blank offer type in any of the following forms:

[Image: screenshot]

JIRA # WSP-662

Changes to the Data Import Tool form

A new Import Template named Offer Types is added to the Data Import Tool form as shown below. Use this option to update only the Offer Types field for existing Benefit Plan IDs on the Group Benefit Plans form. If you try to modify any other field using this process, you will receive an error.

[Image: screenshot]

  1. To access this form, click [Image: screenshot] (Back Office). Under Operations|Import, click Data Import Tool.

  2. Select Offer Types from the Import Template dropdown.

  3. Click the Download Data File hyperlink to download the sample header file. The header file will have the four columns under the File Format tab as shown in the picture above. Fill up the necessary data for all the Benefit Plan IDs for which you want to update the Offer Type to build your Import file. If you want to update the Offer Type for all such Benefit Plan IDs in bulk that do not have an associated offer type, then select the checkbox named Prepopulate file (all plans with BLANK Offer Type). A csv file will get downloaded to your system prepopulated with all the Benefit Plan IDs that do not have an Offer Type.

  4. Click Find File to open the File Upload dialog box.

  5. Click Add Files in the File Upload dialog box.

  6. Select the specified Import File from your system that you have created. Once selected the Import File will display in the File Upload dialog box.

  7. Click Start Upload to upload the file.

  8. Click Close on the File Upload dialog box.

  9. The uploaded Import File name will display under the File Name field on the form. The content of the file will display under File Content tab. Errors if any will display in the Messages tab. Correct the errors and redo the process.

  10. Click Import to import the content into PrismHR.

  11. Click Report to display the Imported Offer Types Report. The Import Status field will tell you if that Offer Type for that Plan ID was imported or not. If not, then the Comments field will tell you the reason.

Once the import is successful, the Offer Type field on the Group Benefit Plans form will be updated for the plans contained in the Import File.

Following is a compatibility list of all offer types and insurance classes:

JIRA # WSP-660, WSP-661

========================================================================

Changes to the Plan Enrollment Details form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-3539%20&%20BA-3732%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-3539 & BA-3732 (Epic).htm

Changes to the Plan Enrollment Details form

You can no longer access this form using normal search means. Now, you can only access this form using the Group Benefit Plans form. Select a Benefit Plan ID. Click the

[Image: screenshot]

menu and the select Enrollment Details.

Note: Note: Your access to the Plan Enrollment Details form now will be based on your existing access to the Group Benefit Plans form. For example, if you previously had deny access to the Plan Enrollment Details form, but had full access to the Group Benefit Plans form, now you will have full access to the Plan Enrollment Details form.

[Image: screenshot]

Also note the following changes:

JIRA # BA-4035, BA-4052, BA-4121

Changes to the Billing Rates form

The Benefit Plan ID text box earlier on this form has now been removed. The Benefit Plan ID field is now read only field and displays the <Benefit Plan ID - Benefit Plan Description> (as shown below) for the selected Benefit Plan ID selected on the Group Benefit Plans form.

[Image: screenshot]

JIRA # BA-4120

Changes to the Premium Rates form

The Benefit Plan ID text box earlier on this form has now been removed. The Benefit Plan ID field is now read only field and displays the <Benefit Plan ID - Benefit Plan Description> (as shown below) for the selected Benefit Plan ID selected on the Group Benefit Plans form.

[Image: screenshot]

JIRA # BA-4122

Changes to the Network Zip Codes form

The Benefit Plan ID text box earlier on this form has now been removed. The Benefit Plan ID field is now read only field and displays the <Benefit Plan ID - Benefit Plan Description> (as shown below) for the selected Benefit Plan ID selected on the Group Benefit Plans form.

[Image: screenshot]

JIRA # BA-4123

========================================================================

New Benefit Salary Maintenance form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-3590%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-3590 (Epic).htm

New Benefit Salary Maintenance form

A new form named Benefit Salary Maintenance has been introduced. Use this form to add an effective date to change employee Benefit Salary and track historical Benefit Salary changes. Thus managing changes to Benefits Salary can be done proactively without real-time changes being necessary for Benefit calculation accuracy.

To access this form, click HR. Under HR|Action, click Benefit Salary Maintenance.

The form contains the fields listed below:

You can save or modify the benefit salary and effective date.

[Image: screenshot]

JIRA # BA-4290, BA-4371

New Benefit Salary History Section

A new section named Benefit Salary History section has been added to streamline the process of viewing employee’s benefit salary information.

The current and future dates under the Date Effective column are hyperlinks. Click any link to edit the selected Benefit Salary record and add a new effective date.

JIRA # BA-4285, BA-4286

On the New Hire form, under the Pay Details section, if you enter a value in the Benefits Calculation Salary field, then that value populates the Benefit Salary field under the Pay tab of the Employee Details form, which creates a new history record for that Benefit Salary in the Benefit Salary History section.

JIRA # BA-4399

Changes to the Rehire form

On the Rehire form, when you select an employee to rehire and save the form, then if the employee had a historical benefit salary record, the rehire process will create a new Benefit Salary History record to match the previous Benefit Salary amount with the current date’s effective date. Also, if a new Benefit Salary History record is created in the rehire process, an alert notification stating The employee’s benefit salary was reinstated as part of the rehire process. Review benefit salary history for accuracy. is displayed.

JIRA # BA-4310

Validations for the Effective Dates

The following validations have been added while selecting Past/Current/Future effective dates for a Benefit Salary History record:

  1. — If a Benefit Salary History record currently exists with an Effective Date equal to the past date entered in the Benefit Salary Start Date field, then an alert message stating, A change record with an effective date equal to already exists. If you continue the existing record will be replaced. Do you wish to continue? is displayed.
  1. — If a Benefit Salary History record currently exists with an Effective Date greater than the past date entered in the Benefit Salary Start Date field, then an alert message stating, A future dated change record with an effective date equal to currently exists. Are you sure you want to continue? is displayed.
  1. — If a Benefit Salary History record currently exists with an Effective Date equal to the past date and a Benefit Salary History record exists with an Effective Date greater than the past date entered in the Benefit Salary Start Date field, then an alert message stating, A change record with an effective date equal to already exists. If you continue the existing record will be replaced. There is also a future dated change record with an effective date equal to . Do you wish to continue? is displayed.
  1. — If a Benefit Salary History record currently exists with an Effective Date equal to the current date in the Benefit Salary Start Date field, then an alert message stating, A change record with an effective date equal to already exists. If you continue the existing record will be replaced. Do you wish to continue? is displayed.
  1. — If a Benefit Salary History record currently exists with an Effective Date greater than the current date entered in the Benefit Salary Start Date field, then an alert message stating, A future dated change record with an effective date equal to currently exists. Are you sure you want to continue? is displayed.
  1. — If a Benefit Salary History record currently exists with an Effective Date equal to the current date and a Benefit Salary History record exists with an Effective Date greater than the current date entered in the Benefit Salary Start Date field, then an alert message stating, A change record with an effective date equal to already exists. If you continue the existing record will be replaced. There is also a future dated change record with an effective date equal to . Do you wish to continue? is displayed.
  1. — If a Benefit Salary History record currently exists with an Effective Date equal to the future date in the Benefit Salary Start Date field, then an alert message stating, A change record with an effective date equal to already exists. If you continue the existing record will be replaced. Do you wish to continue? is displayed.
  1. — If a Benefit Salary History record currently exists with an Effective Date greater than the future date entered in the Benefit Salary Start Date field, then an alert message stating, A future dated change record with an effective date equal to currently exists. Are you sure you want to continue? is displayed.

Note: If there are multiple future dates, the warning message uses the next available pending future date.

  1. — If a Benefit Salary History record currently exists with an Effective Date equal to the future date and a Benefit Salary History record exists with an Effective Date greater than the future date entered in the Benefit Salary Start Date field, then an alert message stating, A change record with an effective date equal to already exists. If you continue the existing record will be replaced. There is also a future dated change record with an effective date equal to . Do you wish to continue? is displayed.

JIRA # BA-4326, BA-4327, BA-4328

Changes to the Employee Details form

On the Employee Details form, under the Pay tab, under the Compensation section, a new hyperlink named Change is added next to the Benefit Salary field.

Click this link to open the Benefit Salary Maintenance form to manage changes to the Benefits Salary seamlessly from the employee record.

[Image: screenshot]

JIRA # BA-4330

Under the Pay tab, when an employee has a benefit salary defined but does not have a Benefit Salary History record, then the Benefit Salary History section is created for that employee on the Benefit Salary Maintenance form.

Under the Pay tab, when you delete the current Benefit Salary then the Benefit Salary change is recorded with a null value in the Benefit Salary History section on the Benefit Salary Maintenance form.

JIRA # BA-4397, BA-4398

Under the Pay tab, under the Compensation section, beside the Benefit Salary field, if you have:

JIRA # BA-4416

========================================================================

New Benefit Utilities form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-3592%20&%20BA-3898%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-3592 & BA-3898 (Epic).htm

New Benefit Utilities form

A new form named Benefit Utilities has been introduced to manage Benefit related utilities.

[Image: screenshot]

To access this form, click Back Office. Under Operations|Utility Processing, click Benefit Utilities.

The form has the following filter:

Manage Orphaned Benefit Records Filter

When you select the Manage Orphaned Benefit Records, based on the Orphaned Record Type filter that follows, you can choose the Client ID and the Benefit Plan ID from the respective tables that is displayed in the Report Filters section.

JIRA # BA-4354, BA-4355, BA-4518

Select Orphaned Record Type as Plan Types and then click Search. The list of orphaned records caused by deleting the Group Benefit Plan Type are displayed. The list of orphaned records displayed in the Results section helps you to reconcile the records.

The Results section displays the following columns:

[Image: screenshot]

JIRA # BA-4404

SH2 Auto Enroll Filter

When you select the SH2 Auto Enroll filter, the Report Filters section is displayed. Here, you can choose the Client ID and the Retirement Plan ID selectors and select the clients, or the retirement plans the employees are enrolled in. You can also leave these selectors blank if you want the search results to appear for all clients and all retirement plans.

Now, click Search. A job control runs. Once the job control process is completed, click Close to view the list of eligible employees for Safe Harbor 2 Match that do not have an active Retirement Plan Enrollments records in the Results section.

[Image: screenshot]

The Results section displays the following columns:

Select the employees that you want to update the retirement plans for and click Update. Based on the number of records you have selected, a confirmation message stating, Retirement Plan Enrollments will be created. Are you sure? is displayed.

[Image: screenshot]

JIRA # BA-3818, BA-4366, BA-4483, BA-4491, BA-4512

========================================================================

Selectors Changed

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-3720%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-3720 (Epic).htm

Selectors Changed

The Select Benefit Plan selector on the following forms have changed:

Once you click the Benefit Plan ID hyperlink on the noted forms, the following Select Benefit Plan selector opens.

[Image: screenshot]

JIRA # BA-4166, BA-4329, BA-4331, BA-4332

The Select Employees selector on the Flexible Spending Account Statement Report has changed

On the Flexible Spending Account Statement Report form, once you click the Employee ID hyperlink the following multivalue selector is now available.

[Image: screenshot]

This selector will only populate employees for the Client ID/s selected on the form.

JIRA # BA-4349

Change to the Benefit Plan Setup form

On this form, now if you select a Plan Class of either Retirement or Employer Match, then under the Eligibility Criteria section, the Eligibility Days From field will remain disabled.

[Image: screenshot]

JIRA # BA-4102

Changes to the Employee Benefit Rule Overrides form

For a life and disability benefit plan on this form:

JIRA # BA-3798

Change to the Group Benefit Plans form

New PEO Master Plan Field

Under the Group Benefit Plans section, a new field, named PEO Master Plan, which is a checkbox has been introduced. This field is used as an indicator to identify a Group Benefit Plan as being one of the PEO’s Master Benefit Plans.

Unchecked - This Group Benefit Plan is not one of the PEO’s Master Benefit Plans. The Benefit Plan Report will display Y for the PEO Master Plan column.

Checked - This Group Benefit Plan is one of the PEO’s Master Benefit Plans. The Benefit Plan Report will display Y for the PEO Master Plan column.

JIRA # BA-3537

Change to the Employee Dependents form

When setting up a new dependent using this form, now if you click Save without filling in all the required fields (fields marked in red), you will receive an error message stating When setting up a dependent, the following fields are required: (list of all the required fields on this form that are yet to be filled in for the selected dependent).

[Image: screenshot]

JIRA # BA-2106

========================================================================

Benefit Plan ID selector changed on the following benefit forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-3906%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-3906 (Epic).htm

Benefit Plan ID selector changed on the following benefit forms

In order to provide a consistent and contextual customer experience across various benefit forms, we have changed the Benefit Plan ID selector on the following forms:

Group Benefit Auto Enrollment (Global) form

The following multivalue selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

JIRA # BA-4077

Group Benefit Auto Enrollment (Client) form

The following selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

You cannot manually enter a Benefit Plan that is not assigned to the client. If you do, you will receive an error message stating Benefit Plan is not assigned to Client . Click OK to clear the value entered and redo the process.

[Image: screenshot]

JIRA # BA-4078, BA-4162

Deduction Register Report form

The following multivalue selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

The earlier Benefit Plans hyperlink has been renamed to Benefit Plan ID.

JIRA # BA-4039

Benefit Billing Detail Report form

The following multivalue selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

The earlier Benefit Plan hyperlink has been renamed to Benefit Plan ID.

JIRA # 4038

Client Benefit Plan Defaults form

The following multivalue selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

The earlier Plan ID hyperlink has been renamed to Benefit Plan ID.

JIRA # 4034

Benefit Reconciliation Report form

The following multivalue selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

JIRA # BA-4007

Employee Deduction Arrears form

Once you open the Employee Deduction Arrears Detail form using the Employee Deduction Arrears form for an employee, the following Select Benefit Plan selector as shown below has been applied to the Benefit Plan ID hyperlink which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

The earlier Plan hyperlink has been renamed to Benefit Plan ID.

JIRA # BA-4006

Departments form

The following multivalue selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

The earlier Benefit Plan hyperlink has been renamed to Benefit Plan ID.

JIRA # BA-4005

Benefit Groups form

The following multivalue selector as shown below has been applied to this form which displays the Benefit Plans that are assigned to the client.

[Image: screenshot]

The earlier Plan hyperlink has been renamed to Benefit Plan ID.

JIRA # BA-4004

Delete Unused Group Benefit Enrollments form

The following selector as shown below has been applied to this form.

[Image: screenshot]

JIRA # BA-3992

Group Benefit Auto Enrollment (Client)

The following selector as shown below has been applied to this form which displays benefit plans that are assigned to the selected client.

[Image: screenshot]

JIRA # BA-3991

Benefit Eligibility Rules (ACA)

The following selector as shown below has been applied to this form.

[Image: screenshot]

JIRA # BA-3990

Group Benefit Auto Enrollment (Global) form

The following multivalue selector as shown below has been applied to this form.

[Image: screenshot]

The Plan to Process hyperlink has been renamed to Benefit Plan ID.

The Benefit Plan ID field is a required field. If you click Create Enrollments without entering at least one Benefit Plan ID, then you will receive and error message stating Benefit Plan ID is required.

JIRA # BA-3929

========================================================================

Validations added to the Group Benefit Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-3930%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-3930 (Epic).htm

Validations added to the Group Benefit Plans form

The following validations are now added to the Group Benefit Plans form:

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

If you save the Benefit Rules form with any of the invalid options shown above in the Eligibility Date Used field, then a warning message stating Mid-Month Coverage Dates has been checked for this plan which requires the Eligibility Date Used on this form to be set to Calculated Eligibility Date. Continue? is displayed.

[Image: screenshot]

Also, you cannot delete a benefit plan if there are any company benefits assigned to the plan. The system will show an error message which asks you to delete the company benefits records first to delete the benefit plan.

[Image: screenshot]

JIRA # BA-771, BA-1061, BA-1581, BA-3819

Validations added to the Employee Benefit Rule Overrides form

On the Employee Benefit Rule Overrides form, when you select any Benefit Plan other than Insurance Class of Medical, Dental, or Vision, then under the Employee Contribution Rules section if you have entered a value in the Contribution amount or the DEP Contribution Amount field, then the Contribution Method field becomes a mandatory field.

If you save the form without fulfilling the above criteria then an error message displays stating Contribution Method is required..

[Image: screenshot]

JIRA # BA-2969

Validation added to the Benefit Rules form

On the Benefit Rules form, when you select any Benefit Plan other than Insurance Class of Medical, Dental, or Vision, then under the Contribution Rules section if you have entered a value in the Contribution amount or the DEP Contribution Amount field, then the Contribution Method field becomes a mandatory field.

If you save the form without fulfilling the above criteria then an error message displays stating Contribution Method is required..

[Image: screenshot]

JIRA # BA-3946

Validation added to the Benefit Adjustments form

On the Benefit Adjustments form, when you select a Benefit Plan for an Employee, then on the Adjustment Details form, the Adjust Cycles hyperlink is enabled only when the Cycles Billed value is equal to 0. If the value is greater than 0, then the Adjust Cycles hyperlink is disabled.

[Image: screenshot]

JIRA # BA-4019

========================================================================

Benefit Plan Type selector changed on the following benefit forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-3945%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-3945 (Epic).htm

Benefit Plan Type selector changed on the following benefit forms

In order to provide consistent and contextual customer experience across various benefit forms, the Benefit Plan Type selector on the following forms have been enhanced:

Relationships form

The following multivalue selector as shown below has been applied to this form which displays the benefit plan types that are assigned to the selected relationship.

[Image: screenshot]

JIRA # BA-4085

Group Benefit Plan Types

The following selector as shown below has been applied to this form which displays the benefit plan types that are assigned to the selected benefit group.

[Image: screenshot]

JIRA # BA-4086

Employee Benefit Rule Overrides

The following multivalue selector as shown below has been applied to this form which displays the benefit plan types associated with the Plan ID on the Group Benefit Plans form.

[Image: screenshot]

JIRA # BA-4087

Benefit Plan Setup form

When you select Plan Class as HSA Contribution, then under the Company HSA Contribution section, if you select Contribution Calculation Method as Tiered or Fixed, then the following selector as shown below has been applied.

[Image: screenshot]

JIRA # BA-4088

========================================================================

Changes to the Benefit Adjustments form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-4047%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-4047 (Epic).htm

Changes to the Benefit Adjustments form

Note: The Adjust Cycles hyperlink is available only if there are no Cycles Billed for that benefit adjustment record.

[Image: screenshot]

There is no change in the existing calculation functionality.

Also, a new row named Total has been added at the bottom of this grid that displays the total values for each of the newly added columns of the vouchers.

[Image: screenshot]

[Image: screenshot]

JIRA # BA-4270, BA-4271, BA-4272

========================================================================

Dependent and Beneficiaries selector changed on the following forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-4132%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-4132 (Epic).htm

Dependent and Beneficiaries selector changed on the following forms

In order to provide consistent and contextual customer experience across various forms, the Dependent and Beneficiaries selector on the following forms have been enhanced:

Employee Benefits Enrollment form

The following selector as shown below has been applied to this form which displays the covered dependent or the beneficiary that are assigned to the benefit plan for the selected employee.

[Image: screenshot]

JIRA # BA-4173, BA-4174

Employee Dependents form

The earlier Dependent ID drop-down is now a hyperlink named Dependent, which has the following selector as shown below which lists all covered dependent or beneficiaries for the selected employee.

[Image: screenshot]

JIRA # BA-4175

========================================================================

Changes on the Relationships form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-4136%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-4136 (Epic).htm

Changes on the Relationships form

On the Relationships form, the Relationship Code selector has been enhanced in order to provide a consistent customer experience as shown below.

[Image: screenshot]

JIRA # BA-4172

========================================================================

Changes to the Benefit Group Maintenance form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-4138%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-4138 (Epic).htm

Changes to the Benefit Group Maintenance form

[Image: screenshot]

JIRA # BA-4265, BA-4266, BA-4267, BA-4269, BA-4334, BA-4370

Changes to the Employee Details form

On the Employee Details form, under the Work tab, under the Assignments section, beside the Benefit Group field, if you have:

JIRA # BA-4396

========================================================================

Eligible Benefits Determinant field validations added to the Client Benefit form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/BA-4224%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/BA-4224 (Epic).htm

Eligible Benefits Determinant field validations added to the Client Benefit form

On the Client Benefit form, under the Benefits tab, for the Eligible Benefits Determinant field, the following validations has been added for the following selections:

[Image: screenshot]

Note: If you select any All Plans Eligible then on the Eligible Benefits section on the corresponding forms will be displayed as a read only section.

JIRA # BA-4225, BA-4226, BA-4227, BA-4228

Benefit Plan ID selector for Eligible Benefits changed on the following forms

Worksite Locations form

The Plan ID selector is now a hyperlink and has been renamed to Benefit Plan ID. The following selector as shown below has been applied to this form.

[Image: screenshot]

JIRA # BA-4229

Divisions form

The Plan selector is now a hyperlink and has been renamed to Benefit Plan ID. The following selector as shown below has been applied to this form.

[Image: screenshot]

JIRA # BA-4230

Changes to the Data Import Tool form

A new Import Template named Eligible Benefits is added to the Data Import Tool form as shown below. This option is available only for Service Providers. You can click the Download Data File to download the Eligible Benefits template in a csv format.

[Image: screenshot]

  1. To access this form, click [Image: screenshot] (Back Office). Under Operations|Import Processing, click Data Import Tool.

  2. Select Eligible Benefits from the Import Template drop-down.

  3. Click the Download Data File hyperlink to download the Eligible Benefits sample template. The template file will have the nine columns under the File Format tab as shown in the picture above. Fill up the necessary data for all the Eligible Benefits for which you to build your Import file.

  4. If you want a prepopulated data of the clients, then you will have to select the clients from the Client ID selector.

  5. Click the Client ID selector to open the Select Clients dialog box. Another way to enter client details is by providing the Client ID in the box.

[Image: screenshot]

  1. Click Done to add the selected clients. The added clients will be displayed on the Data Import Tool page.

  2. Now, click the Download Data File hyperlink to download the file of prepopulated data for all the clients selected.

  3. Check the Include Obsolete/Expired values checkbox based on your requirement. The default is unchecked.

  1. Click Find File to open the File Upload dialog box.

  2. Click Add Files in the File Upload dialog box.

  3. Select the specified Import File from your system that you have created. Once selected, the Import File will display in the File Upload dialog box.

  4. Click Start Upload to upload the file.

  5. Click Close on the File Upload dialog box.

  6. The content of the file will display under File Content tab. Errors, if any, will display in the Messages tab. Correct the errors and redo the process.

  7. Click Import to import the content into PrismHR.

  8. Click Report to display the Imported Eligible Benefits Report. The Import Status column will tell you if that Eligible Benefits for that Client was imported or not. If not, then the Comments column will tell you the reason.

JIRA # BA-4232, BA-4233

Changes to the Eligible Benefits section

A new Quicklink named Import Eligible Benefits is now added under the Eligible Benefits section of the following forms:

[Image: screenshot]

JIRA # BA-4237

On the following forms:

if the Eligible Benefits section is disabled and there is any existing data in this section, then on saving the forms, a message stating Do you wish to clear the existing Benefit Plan IDs in the Eligible Benefits section? Y/N is displayed.

JIRA # BA-4238

========================================================================

Changes to the System Parameters form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1010.htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1010.htm

Changes to the System Parameters form

On the System Parameters form, under the Global Codes Setup section, under the Retirement sub-header, four new fields have been introduced, namely:

[Image: screenshot]

JIRA # WSP-1010

========================================================================

Changes to the Group Benefit Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-123,%20WSP-140,%20WSP-1186%20(Epic)%20&%20WSP-1241%20(Part).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-123, WSP-140, WSP-1186 (Epic) & WSP-1241 (Part).htm

Changes to the Group Benefit Plans form

Changes to the Group Benefit Plans Section

On the Group Benefit Plans form, in the Offer Type field, if you select any Offer Type other than Voluntary, the system will automatically assign the Insurance Class field without the user having to assign it manually. The system will display the Insurance Class field as a read-only field. When you select Offer Type as Voluntary, the Insurance Class field becomes a required field, and you must manually select the corresponding insurance class.

[Image: screenshot]

Note: The Offer Type field is mandatory. If you leave it blank, you will receive an error message stating Offer Type is mandatory.

Please note the following list of insurance class and their corresponding offer types:

JIRA # WSP-942

New Dependent Reduction Provision Field

Under the Group Benefit Plans section, when the Insurance Class field is selected as Life Insurance, then under the Age Reduction Schedule section, two new fields appear:

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-1072, WSP-1192

New Brokers form

Under the Actions menu, a new form named Brokers has been added. To access this form, users must have FULL access to BROKERMAINT and BENEFIT.PLANSMAINT.

[Image: screenshot]

This modal form creates a repository of the Brokers information in the system. The form contains fields listed below:

Users can add new brokers, delete or modify an existing broker information.

[Image: screenshot]

On the Brokers form, you can search for a broker information by keying in the Broker ID in the respective field. If you enter a value that is not in the record, you will get a warning message that states, Record not on file, please click ‘New Record.’

JIRA # WSP-1221, WSP-1223, WSP-1224, WSP-1304

Changes to the Broker Field

Under the Other Processing Parameters section, the Broker field now is a hyperlink. You can either enter the listed broker name here or click the Broker hyperlink to select a broker from the list.

[Image: screenshot]

JIRA # WSP-1222

New Coverage Ends On Field

Under the Other Processing Parameters section, a new field named Coverage Ends On has been introduced. This field defines the date on which you want the coverage to end.

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-1397, WSP-1399, WSP-1403

New Use Billing Wash Rule? Field

Under the Other Processing Parameters section, a new field named Use Billing Wash Rule? has been introduced.

[Image: screenshot]

This field has two options:

JIRA # WSP-1398

========================================================================

Changes to the Data Import Tool form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1252%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1252 (Epic).htm

Changes to the Data Import Tool form

A new Import Template named Retirement Loans is added to the Data Import Tool form as shown below. This option is available only for Service Providers. You can click the Download Sample Header File to download the Retirement Loans template csv file.

[Image: screenshot]

  1. To access this form, click [Image: screenshot] (Back Office). Under Operations|Import Processing, click Data Import Tool.

  2. Select Retirement Loans from the Import Template drop-down.

  3. Click the Download Sample Header File hyperlink to download the Retirement Loans sample template. The template file will have the thirteen columns under the File Format tab as shown in the picture above. Fill up the necessary data for all the Retirement Loans for which you to build your Import file.

  4. Click Find File to open the File Upload dialog box.

  5. Click Add Files in the File Upload dialog box.

  6. Select the specified Import File from your system that you have created. Once selected, the Import File will display in the File Upload dialog box.

  7. Click Start Upload to upload the file.

  8. Click Close on the File Upload dialog box.

  9. The uploaded Import File name will display under the File Name field on the form. The content of the file will display under File Content tab. Errors, if any, will display in the Messages tab. Correct the errors and redo the process.

  10. Click Import to import the content into PrismHR.

  11. Click Report to display the Imported Retirement Loans Report. The Import Status field will tell you if that Retirement Loans for that Employee or the Client was imported or not. If not, then the Comments field will tell you the reason.

JIRA # WSP-1330, WSP-1331

========================================================================

Changes to the Clients Assigned To form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1254%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1254 (Epic).htm

Changes to the Clients Assigned To form

On the Group Benefit Plans form, after you have entered a Benefit Plan ID, under the

[Image: screenshot]

menu, on the Clients Assigned To form, a new button named Report is now added for you to run report and export the data.

[Image: screenshot]

JIRA # WSP-1391

Changes to the Employees Assigned To form

On this Benefit Groups form, after you have entered a Benefit Group, under the

[Image: screenshot]

menu, on the Employees Assigned To form, a new button named Report is now added for you to run report and export the data.

[Image: screenshot]

JIRA # WSP-1392

========================================================================

Changes to the Pay Code Selector

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1348%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1348 (Epic).htm

Changes to the Pay Code Selector

The Pay Code selector has been enhanced across the following forms:

[Image: screenshot]

JIRA # WSP-1355, WSP-1356, WSP-1357, WSP-1358, WSP-1359, WSP-1360

========================================================================

Changes to the Deduction Code Selector

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1349%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1349 (Epic).htm

Changes to the Deduction Code Selector

The Deduction Code selector has been enhanced across the following forms:

[Image: screenshot]

JIRA # WSP-1361, WSP-1362, WSP-1363, WSP-1364, WSP-1365, WSP-1366, WSP-1367

========================================================================

Changes to the Bill Code Selector

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1350%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1350 (Epic).htm

Changes to the Bill Code Selector

The Bill Code selector has been enhanced across the following forms:

[Image: screenshot]

JIRA # WSP-1368, WSP-1369, WSP-1370

========================================================================

New Account Codes Selector

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1351%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1351 (Epic).htm

New Account Codes Selector

The earlier Account Type selector has been renamed to Account Code and has also been enhanced across the following forms:

[Image: screenshot]

JIRA # WSP-1371, WSP-1372, WSP-1373, WSP-1374

========================================================================

Changes to the Benefit Plan Setup form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-146,%20WSP-153%20(Epic)%20&%20WSP-1241%20(Part).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-146, WSP-153 (Epic) & WSP-1241 (Part).htm

Changes to the Benefit Plan Setup form

Changes to the Eligibility Date Used Field

Under the Benefit Plan Setup section, when you select Plan Class as:

then, under the Eligibility Criteria section, in the Eligibility Date Used field, a new drop-down option named First Semi-Annual after Calculated Date, has been introduced, which will enable you to easily administer retirement plans and calculate employer match eligibility with semi-annual enrollment criteria with date of either January 1 or July 1.

[Image: screenshot]

JIRA # WSP-229, WSP-1219

Changes to the System HSA Language

The earlier Plan Class option named, HSA Match has been renamed as HSA Contribution. All over the form, HSA Match is also renamed as HSA Contribution as shown in the image below:

[Image: screenshot]

There is no change in the existing functionality.

JIRA # WSP-1169

New Contribution Applies To Field

Under the Company HSA Contribution section, a new field named Contribution Applies To, has been introduced. This field has two drop-down values:

[Image: screenshot]

When you select All HDHP Employees, a new field named Account Type displays. Enter the HSA account type the HDHP employees are enrolled in here or click the Account Type hyperlink and select it from the HSA Account Type dialog box.

[Image: screenshot]

JIRA # WSP-1170

Changes to the Use Billing Wash Rule? Field

When you select Plan Class as Group Benefit, then under the Group Benefits Setup section, the Use Billing Wash Rule? field is now displayed as a selector instead of a checkbox.

The Use Billing Was Rule? field now displays Default in parenthesis next to the selected option based on the selection made in this field on the Group Benefit Plans form so that the user is aware of what is selected at the system level.

[Image: screenshot]

JIRA # WSP-1402, WSP-1405

========================================================================

Changes to the Notification Audit Report form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-1470.htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-1470.htm

Changes to the Notification Audit Report form

On the Notification Audit Report form, when you run a report, a new column named Notification template name is added to the report results as shown in the image below.

[Image: screenshot]

JIRA # WSP-1470

========================================================================

Changes to the Retirement Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-251%20&%20WSP-1347%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-251 & WSP-1347 (Epic).htm

Changes to the Retirement Plans form

Changes to the Deduction/Bill Code Overrides section

The earlier Deduction/Bill Code Setup section has been renamed to Deduction/Bill Code Overrides.

The existing codes under this section are now divided into two tables:

[Image: screenshot]

This allows you the visibility as to what is set up at the system level to aid in setting up overrides.

Note: For a particular line item, if the Global Setting for the Deduction Code is blank, then the corresponding Deduction Code Override becomes mandatory.

JIRA # WSP-1011

Changes to the Payee ID Selector

Under the Retirement Plans section, the Payee ID selector has been enhanced for you to have a consistent user experience.

[Image: screenshot]

JIRA # WSP-1353

========================================================================

Changes to Arrears Report

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-766%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-766 (Epic).htm

Changes to Arrears Report

Now, the Payroll Deduction in Arrears Report and the Global Payroll Deduction in Arrears Report, has the following two new columns added:

Payroll Deduction in Arrears Report

[Image: screenshot]

Global Payroll Deduction in Arrears Report

[Image: screenshot]

JIRA # WSP-1105

========================================================================

Changes to the Retirement Plan Enrollment form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-766%20(Part)%20&%20WSP-1246%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-766 (Part) & WSP-1246 (Epic).htm

Changes to the Retirement Plan Enrollment form

Changes to the Retirement Plan Enrollment section

Under the Retirement Plan Enrollment section, once you select an employee, the selected employee’s age is now displayed below the employee name.

[Image: screenshot]

JIRA # WSP-1163

Changes to the Exclude / Include Pay Codes Section

The earlier Excluded Pay Codes section has been renamed to Exclude / Include Pay Codes as shown in the image below:

[Image: screenshot]

There is no change in existing functionality.

JIRA # WSP-1379

Changes to the Election Details Section

The Election Details section has been enhanced with the following features:

[Image: screenshot]

There is no change in existing functionality.

JIRA # WSP-1380

Changes to the Extra Contributions Section

The earlier Extra Options section has been renamed to Extra Contributions as shown in the image below:

[Image: screenshot]

Earlier Field Name Current Field Name
Extra Elective Elective
Extra Roth Roth
Extra Match Amount Elective Match
Extra Non-Elect Match Non-Elective Match
Extra Safe Harbor One Match Safe Harbor One Match
Extra Safe Harbor Two Match Safe Harbor Two Match

There is no change in existing functionality.

JIRA # WSP-1381

========================================================================

Changes to the Employee Dependents form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2003Mar%20QR/WSP-873%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 03Mar QR/WSP-873 (Epic).htm

Changes to the Employee Dependents form

On the Employee Dependents form, under the Dependent Details section, a new checkbox named SSN Applied For has been introduced.

[Image: screenshot]

Note: On theEmployee Dependents form, if you leave the Social Security Number field blank and the SSN Applied For checkbox is unchecked simultaneously in the Dependent Details section, then you will receive an error message stating When setting up a Dependent, the following fields are required: Social Security Number or SSN Applied For.

If the Social Security Number field in the Dependent Details section already contains a value and you check the SSN Applied For checkbox, then you will see a pop-up alert, Do you want to clear the dependent Social Security Number?

[Image: screenshot]

JIRA # WSP-943, WSP-1182

========================================================================

New Gross Wage % Functionality

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/BA-4046%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/BA-4046 (Epic).htm

New Gross Wage % Functionality

A new option has been added to define when a medical plan allows plan elections for employee and dependent with contributions up to a certain percent of gross wages for the employee portion.

Changes to the Group Benefit Plans form

Under the Group Benefit Plans section, a new checkbox named Allow Gross Wage % Contribution Method has been added to allow you to set the Percent of Gross Wages as the employee contribution towards a medical plan (employee premium only).

[Image: screenshot]

JIRA # BA-4472, BA-4507, WSP-1762

Changes to the Benefit Rules form

Under the Contribution Rules section, a new field named Percent of Gross Wages has been added to override the Gross Wage % value assigned on the Group Benefit Plans form for medical plans.

[Image: screenshot]

JIRA # BA-4473

Changes to the Employee Benefit Rule Overrides form

Under the Employee Contribution Rules section, a new field named Percent of Gross Wages has been added to override the Gross Wage % value assigned on the Group Benefit Plans form and the Benefit Rules form (if applicable) for Medical plans.

[Image: screenshot]

This newly added field will only display if you have selected the Allow Gross Wage % Contribution Method checkbox and defined the Effective Date for that medical benefit plan on the Group Benefit Plans form. If this criteria is not met then a message stating Not applicable for this plan is displayed.

JIRA # BA-4474

Changes to the Employee Benefits Enrollment form

Under the Coverage Details section, a new field named Percent of Gross Wages has been added to indicate if an employee is enrolled in a medical plan which uses the Gross % of Wages to calculate the employee’s portion of the premium which displays the Gross % of Wages value that is being used.

[Image: screenshot]

Note: The Percent of Gross Wages field will not be displayed for the COBRA plans.

JIRA # BA-4476, WSP-1723

Changes to the Payroll Calculations

On the Process Payroll form, the payroll calculation process now includes the gross wages and calculates the employee contribution based on the Benefit Rules and value assigned to the Benefit Plan for Gross % of Wages.

The logic to determine the Percent of Gross Wages being used is as follows:

The payroll calculation is as below:

JIRA # WSP-1679

========================================================================

Changes to the Data Import Tool form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/BA-4126%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/BA-4126 (Epic).htm

Changes to the Data Import Tool form

[Image: screenshot]

[Image: screenshot]

JIRA # BA-4451, BA-4452

Changes to the Group Benefit Plans form

The earlier Manual Calculation field has been renamed to Calculation Method as shown in the image below.

[Image: screenshot]

This has been renamed wherever applicable on the form including in the Audit modal form and the Display Data Mapping option under the Actions menu. However, the historical changes will still display as Manual Calculation.

There is no change in existing functionality.

JIRA # BA-4466

Changes to the Group Benefit Auto Enrollment (Global) form

On the Group Benefit Auto Enrollment (Global) form, entering a duplicate Benefit Plan ID is not allowed. If you enter or select a Benefit Plan ID that has already been provided, then an error message stating Value has already been entered here. is displayed.

[Image: screenshot]

JIRA # BA-4492

Changes to the Benefit Register Employer Report form

On the Benefit Register Employer Report form, when you generate a report for an employer, then the earlier Plan/Calss Sub-total label which showed the total Billed Amount and Premium Amount for the month has been corrected to Plan/Class Sub-total label.

[Image: screenshot]

JIRA # BA-4510

========================================================================

Changes to the Benefit Utilities form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/BA-4503%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/BA-4503 (Epic).htm

Changes to the Benefit Utilities form

[Image: screenshot]

The Results section displays the following columns:

[Image: screenshot]

The Results section displays the following columns:

[Image: screenshot]

JIRA # BA-4408. BA-4410, BA-4513

========================================================================

Changes to the Group Benefit Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-1237%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-1237 (Epic).htm

Changes to the Group Benefit Plans form

On the Group Benefit Plans form, a new table for Deduction/Bill Code has been added to view your Deduction and Billing codes easily in a tabular format.

[Image: screenshot]

The table has the following columns for each of the Deduction or Bill Codes:

Following are the validations with regard to the display of different deduction and bill codes:

Note: If you do not enter or select a Benefit Plan ID, then clicking any of the deduction or bill codes hyperlink in the table will display an error message stating, Benefit Plan ID is mandatory.

JIRA # WSP-1382, WSP-1383

========================================================================

Changes to the Benefit Plan Setup form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-1240%20(Epic)%20&%20WSP-1242%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-1240 (Epic) & WSP-1242 (Epic).htm

Changes to the Benefit Plan Setup form

Under the Benefit Plan Setup section, a new hyperlink named View Benefit Rules has been added to view the list of Benefit Rules and their effective dates for the Plan ID indicated on the Benefit Plan Setup form. Click this hyperlink to open the Benefit Rules modal form.

[Image: screenshot]

JIRA # WSP-1386, WSP-1387

Relocating the Default Network ID field

After selecting the Plan Class as Group Benefit, under the Group Benefits Setup section, the Default Network ID field has now been located below the Suppress Benefit Adjustment on Employee Termination checkbox and above the Rule Date to Use for Take-On field as shown in image below.

[Image: screenshot]

JIRA # WSP-1393

Validations for Auto Enroll

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-1394, WSP-1395

========================================================================

Changes to the Benefit Import Maintenance form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-1253%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-1253 (Epic).htm

Changes to the Benefit Import Maintenance form

On the Benefit Import Maintenance form, under the Import Fields table, the following Field Names has been added to streamline the import process for FSA and HSA elections.

[Image: screenshot]

Addition of these new import fields will be available on the Employee Flexible Spending Accounts form as shown in the table below.

Import Field Name Field Name on the Employee Flexible Spending Accounts form
DEDUCTAMT * |*PlanYeartoDate − Deductions*||*REIMB_AMT Plan Year to Date - Reimbursements
DEDNOVERAMT * |*DeductionOverride*||*MATCH_OVER_AMT Match Override
PERIODS * |*Periods*||*TYPE_OVER_DATE Over Date
HDHPFLAG * |*HDHPNotRequired?*||*OVERRIDE_CONTRIB_LIMITS Suppress Contribution Limits?
$HSA_PEO_MATCH_OVERRIDE HSA PEO Match Override

[Image: screenshot]

Note: These newly added Import Fields are not mandatory.

JIRA # WSP-1486

========================================================================

Changes to the Benefit Rules form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-1269%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-1269 (Epic).htm

Changes to the Benefit Rules form

On the Benefit Rules form, a quick link named Group Benefit Auto Enrollment (Client) now displays if a plan has been labeled as Auto-Enroll at the global or client level for you to easily enroll eligible employees in the plan.

[Image: screenshot]

Click the Group Benefit Auto Enrollment (Client) quick link. A pop-up warning appears with a message stating You have unsaved changes. Are you sure you want to leave?:

While saving the form, if the plan is set to auto-enroll, an additional routine is called to check for employees within the selected client who meet the eligibility requirements of the plan but are not enrolled. A message stating We have identified eligible employees who are not enrolled in this plan. Would you like to be taken to the Group Benefit Auto Enrollment (Client) form to enroll these employees? is displayed to notify you of the eligible employees.

JIRA # WSP-1337, WSP-1338

========================================================================

New Plan Renewal Date field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-133%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-133 (Epic).htm

New Plan Renewal Date field

In order to allow you to provide a plan renewal date for a benefit plan, a new field named Plan Renewal Month has been added to the following forms:

Group Benefit Plans form

Under the Other Processing Parameters section, a new field named Plan Renewal Month has been added as shown below.

[Image: screenshot]

JIRA # WSP-1474

Benefit Plan Setup form

Under the Group Benefits Setup section, a new field named Client Plan Renewal Month/Day has been added as shown below.

[Image: screenshot]

Click the drop-down to select the month and the day. Select is the default option in both the month and day drop-down lists. This field is used as an override to the date specified on the Group Benefit Plans form (if one exists for the Benefit Plan selected).

A tool-tip is also provided with a message stating This field will be used as an override to the date specified on the Group Benefit Plans form. If one exists for the Benefit Plan selected, the Group Benefit Renewal date will be displayed. which explains the functionality of the newly added field.

Note: On the Group Benefit Plans form, when you assign a value to the Plan Renewal Month field, then that value is displayed as read-only field to the right of the Client Plan Renewal Month/Day field with a label named Group Benefit Renewal on the Benefit Plan Setup form.

JIRA # WSP-1475, WSP-1750

========================================================================

Payee ID selector changed on the following benefit forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-1347%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-1347 (Epic).htm

Payee ID selector changed on the following benefit forms

In order to provide a consistent and contextual customer experience across various benefit forms, we have changed the Payee ID selector on the following forms:

Payees form

The following selector as shown below has been applied to this form which displays the payees that are assigned to the client.

[Image: screenshot]

JIRA # WSP-1352

Group Benefit Plans form

The following selector as shown below has been applied to this form which displays the payees that are assigned to the client.

[Image: screenshot]

JIRA # WSP-1354

========================================================================

Changes to the Notification Audit Report form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-1479%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-1479 (Epic).htm

Changes to the Notification Audit Report form

Now, on Notification Audit Report form, when you run a report, the report has the following two new columns added:

[Image: screenshot]

JIRA # WSP-1553, WSP-1554

========================================================================

Changes to the Retirement Match Nomenclature on different forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-252%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-252 (Epic).htm

Changes to the Retirement Match Nomenclature on different forms

Changes to the Retirement Match Rules form

Under the Maximum Matching Contribution Per Calendar Year (Per Employee) section, the earlier Non-Elective and Safe Harbor fields have been renamed as shown in the table below:

Earlier Field Name Current Field Name
Safe Harbor 1 Match Safe Harbor 1 Contribution
Safe Harbor 2 Match Safe Harbor 2 Contribution
Non-Elective Match Non-Elective Contribution

[Image: screenshot]

JIRA # WSP-1576

Changes to the Payroll Voucher form

On the Payroll Voucher form, under the Benefits tab, the earlier Non-Elective and Safe Harbor fields have been renamed as shown in the table below:

Earlier Field Name Current Field Name
Non-Elective Match Non-Elective Contribution
Safe Harbor Type One Match Safe Harbor 1 Contribution
Safe Harbor Type Two Match Safe Harbor 2 Contribution

[Image: screenshot]

JIRA # WSP-1578

Changes to the Retirement Register Adjustment form

Under the Contributions section, the earlier Non-Elective and Safe Harbor fields have been renamed as shown in the table below:

Earlier Field Name Current Field Name
Non-Elect Contribution Non-Elective Contribution
Safe Harbor Type 1 Match Safe Harbor 1 Contribution
Safe Harbor Type 2 Match Safe Harbor 2 Contribution

[Image: screenshot]

JIRA # WSP-1579

Changes to the Retirement Plans form

Under the Retirement Plans section, the following fields has been renamed as shown in the table below:

Earlier Field Name Current Field Name
Employer Match Pay Stub Description Employer Contribution Pay Stub Description
Non-Elect Match Pay Stub Description Non-Elective Contribution Pay Stub Description
Limit Safe-harbor Match Based On Match Date Limit Safe Harbor Contribution Based On Match Date

[Image: screenshot]

JIRA # WSP-1580

========================================================================

Changes to the Retirement Plan Enrollment form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2004Apr/WSP-766%20(Epic)%20&%20WSP-252%20(Part).htm Path: BA/Release-Notes/Enhancements/2025/2025 04Apr/WSP-766 (Epic) & WSP-252 (Part).htm

Changes to the Retirement Plan Enrollment form

Changes to the Election Details section

Under the Election Details section, if you select the New Effective Date prior to the date set in the Status Date field, then a warning pop-up stating Effective date cannot precede the Status Date on the Enrollment Record is displayed.

[Image: screenshot]

JIRA # WSP-1388

Changes to the Extra Contribution form

The following earlier fields in the table has been renamed as shown in the table below:

Earlier Field Name Current Field Name
Non-Elective Match Non-Elective Contribution
Safe Harbor One Match Safe Harbor 1 Contribution
Safe Harbor Two Match Safe Harbor 2 Contribution

[Image: screenshot]

JIRA # WSP-1581

========================================================================

New Exempt take on employees from Minimum Days of Service Requirement checkbox

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2005May/BA-4402%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 05May/BA-4402 (Epic).htm

New Exempt take on employees from Minimum Days of Service Requirement checkbox

Benefit Plan Setup form

Under the Benefit Plan Setup section, after you select Plan Class as:

then a new checkbox named Exempt take on employees from Minimum Days of Service Requirement has been added to allow the waiting period to be waived for take-on employees.

[Image: screenshot]

then a new checkbox named Exempt take on employees from Minimum Days of Service Requirement has been added to allow the waiting period for 401(k) employer match to be waived so that the employee can continue receiving contributions without interruption.

[Image: screenshot]

Note: When the new Exempt take on employees from Minimum Days of Service Requirement field is checked, then

JIRA # WSP-1699. WSP-1700, WSP-1701, WSP-1907

Retirement Plans form

Under the Retirement Plans section, a new checkbox named Exempt take on employees from Minimum Days of Service Requirement has been added to allow the waiting period the 401(k) employee contributions to be waived for take-on employees.

[Image: screenshot]

JIRA # WSP-1903

========================================================================

Changes to the Benefit Utilities form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/BA-4681%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/BA-4681 (Epic).htm

Changes to the Benefit Utilities form

[Image: screenshot]

then upon clicking Search, a job is run and the Results section is displayed. In the Results section, a new column for Employment Status Class is also displayed. Additionally, the Employee Status Class column displays null value for any records that do not have an Employee ID.

JIRA # WSP-2085, WSP-2086, WSP-2087, WSP-2088

========================================================================

New Outstanding Billing Section

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-118%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-118 (Epic).htm

New Outstanding Billing Section

In order to allow you to view the scheduled deductions, arrears, and outstanding benefit adjustments for an employee’s benefits in one view, a new section named Outstanding Billing has been added to the following forms:

[Image: screenshot]

Note: The information in this section will also be displayed for terminated and COBRA participants if the Service Providers needs to view the outstanding funds.

This section is expandable and when expanded, it provides the following sub-sections:

Please note the following:

Please note the following:

Please note the following:

JIRA # WSP-1654, WSP-1655, WSP-1767, WSP-1768, WSP-1769, WSP-1770

========================================================================

Changes to the Employee Deduction Arrears form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-120%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-120 (Epic).htm

Changes to the Employee Deduction Arrears form

Removing the Delete column and Introducing Convert to Adjustment Button

The earlier Delete column has now been removed from the Employee Deduction Arrears form. Enhancement to the Change Status button and a new button named Convert to Adjustment has been introduced for users to convert an arrears record into a Benefit Adjustment.

[Image: screenshot]

[Image: screenshot]

Please note the following:

JIRA # WSP-1627, WSP-1628, WSP-1642, WSP-1941, WSP-2005, WSP-2050

Changes to the Employee Deduction Arrears Detail form

On the Employee Deduction Arrears form, when you click an arrears record to open the Employee Deduction Arrears Detail modal form, the earlier Done and Cancel buttons have been replaced by Save, Delete, and Close buttons.

[Image: screenshot]

JIRA # WSP-2048

Replacing Delete Arrears Button with Delete Button

The earlier Delete Arrears button has now been removed and a new button named Delete has been introduced at the bottom of the Employee Deduction Arrears form.

[Image: screenshot]

The Delete button is enabled only when you select one or more arrears records.

JIRA # WSP-2049

========================================================================

Changes to the Benefit Adjustments form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-1238%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-1238 (Epic).htm

Changes to the Benefit Adjustments form

Under the Benefit Adjustments section, after you select an Employee and select the Benefit Plan record, then on the Adjustment Details modal form, that is displayed, two new read-only fields named Bill Code and Deduction Rebate Bill Code have been added to take the Bill Code and Rebate Bill Code available on the Deduction Codes form into account and accurately assess and calculate the value displayed in the Net Inv Effect field.

[Image: screenshot]

System Parameters form (Require Prepay Benefit Account No. field) Benefit Plan Setup form (One Month Prepay field) The Bill Code displayed on the Benefit Adjustments form
No Unchecked Bill Code
Setup Unchecked Bill Code
Yes Unchecked Bill Code
Yes Checked Prepay Bill Code

Note: If the identified Bill Code field is empty in any of the scenarios above, then the Bill Code field on the Adjustment Details modal form will display N/A as the value.

System Parameters form (Require Prepay Benefit Account No. field) Benefit Plan Setup form (One Month Prepay field) Employee Benefits Enrollment (Section 125 field) The Deduction Code displayed on the Benefit Adjustments form
No Unchecked Unchecked Deduction Code
Setup Unchecked Unchecked Deduction Code
No Unchecked Checked 125 Deduction Code
Setup Unchecked Checked 125 Deduction Code
Yes Unchecked Unchecked Deduction Code
Yes Unchecked Checked 125 Deduction Code
Yes Checked Unchecked Deduction Code Prepay
Yes Checked Checked 125 Deduction Code Prepay

Note: If the identified Deduction Rebate Bill Code field is empty in any of the scenarios above, then the Deduction Rebate Bill Code field on the Adjustment Details modal form will display N/A as the value.

With the introduction of these two new fields, the calculation method for Net Inv Effect has also changed. The following table illustrates the calculation method based on the values fetched in the Bill Code and the Deduction Rebate Bill Code fields:

Bill Code found? Deduction Rebate Bill Code found? Net Inv Effect Calculation
Yes N/A Bill Amount - Employee Contribution
N/A Yes (- EE Contribution)
N/A N/A 0.00
Yes Yes (Bill Amount - Employee Contribution) - Employee Contribution

Please note the following:

JIRA # WSP-1833, WSP-2033, WSP-2034, WSP-2035

Changes to the Employee Benefits Enrollment form

Under the Employee Benefits Enrollment section, after you have selected an Employee and the Benefit Plan, three new read-only fields named Bill Code, Deduction Rebate Bill Code, and Net Inv Effect have been added for users to easily and accurately view what impact the pay period premium will have on invoice billing.

[Image: screenshot]

The values in all these newly added fields are fetched as per the logic discussed in the See Changes to the Benefit Adjustments form release notes.

JIRA # WSP-1834

========================================================================

Changes to the Group Benefit Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-1239%20(Epic),%20WSP-1259%20(Epic)%20&%20WSP-1248%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-1239 (Epic), WSP-1259 (Epic) & WSP-1248 (Epic).htm

Changes to the Group Benefit Plans form

New Do Not Allow EE Contribution checkbox

Under the Group Benefit Plans section, a new checkbox named Do Not Allow EE Contribution has been added which ensures that clients are informed that the plans are client-paid while setting up benefit rules.

[Image: screenshot]

then, while saving the benefit rules, a warning message stating, This plan configuration prevents employee contributions, please review the Contribution Rules and verify the plan meets this requirement. is displayed.

Click OK to close the warning message and save the benefit rule.

JIRA # WSP-1327, WSP-1328, WSP-1335, WSP-1389

New Override Dependent Age Limits By State field

On the Group Benefit Plans form, under the Other Processing Parameters section, below the Disabled Dependent Eligible field, a new checkbox field named Override Dependent Age Limits By State has been added to allow you to configure state level override(s) for Dependent Age Limits so that you can easily manage differences in plans at the state level.

[Image: screenshot]

If there are no states listed in this table, then upon saving the form an error message stating No state listed in the dependent age limit override table is displayed.

Also, if you do not input any value in any one of the row in the table, then upon saving the form an error message stating The [field name] for the state of [State value] is missing from the dependent age limit override table is displayed.

Note: The system uses the State’s Dependent Age limit and its related Calculation Method and Disabled Eligibility Limit as an override for determining when the Dependent Age Limit becomes effective. If there is no override configured for a given state in the Dependent Age Limit Override table, then the system uses the existing Dependent Age Limit (and related field’s) values as default.

JIRA # WSP-1378, WSP-1385

Group Benefit Plans form Redesign

When accessing the Group Benefit Plans form, now only the top section that is the Group Benefit Plans section is visible. The remaining section of the form is displayed only when you select an existing Benefit Plan ID which has an Insurance Class setup or set up a new plan and select their Insurance Class.

[Image: screenshot]

JIRA # WSP-1810

========================================================================

New Billing History Section

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-1273%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-1273 (Epic).htm

New Billing History Section

In order to allow you to view the billing history for a specific employee/plan along with the ability to select custom date range to review billing history, a new section named Billing History has been added to the following forms:

[Image: screenshot]

This section is expandable and when expanded, it provides the Selection Parameters section.

Under the Selection Parameters section, the Defined Ranges drop-down field is available for you to select from a list of pre-defined date ranges or enter your own date range to review billing history.

The Defined Ranges drop-down contains the following options:

Note: This drop-down option is not available under the Billing History section on the Employee Benefit Overview form.

Note: This drop-down option is not available under the Billing History section on the Employee Benefit Overview form.

Please note the following:

Note: This Pay Date range for this drop-down option is limited to 6 months. If the date range entered is longer than 6 months, then a warning message stating, Pay Date range is limited to 6 months. Please select a Pay Date which is greater than or equal to . is displayed.

Note: The Download Report button is disabled when there are no results for a defined date range.

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-1428, WSP-1429, WSP-1430, WSP-1431, WSP-1465

========================================================================

Changes to the Benefit Billing Detail Report form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-1416%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-1416 (Epic).htm

Changes to the Benefit Billing Detail Report form

New Defined Ranges Drop-down

Under the Selection Parameters section, a new field drop-down named Defined Ranges has been added for users to select from a list of pre-defined date ranges or enter their own date range for easy user experience while running the report.

[Image: screenshot]

The drop-down contains the following options:

Please note the following:

JIRA # WSP-1434, WSP-1588, WSP-2007

Changes to the Sort Parameters Section

The earlier Sort Criteria drop-down is now removed and has been replaced by the following options:

a. Select
b. Employee
— —
c. Benefit Plan
— —
d. Location
— —
e. Department
— —
a. Select
b. Employee
— —
c. Benefit Plan
— —
  1. — Detail- When you select Report Type as Detail, then the report generated displays the results based on the payroll voucher/pay date level detail. Below are the following columns that are displayed in the report results:
  1. — Summary (default)- If you select Report Type as Summary, then the report output aggregates the report results into segments dictated by sort parameters.

[Image: screenshot]

Please note the following validations:

JIRA # WSP-1448, WSP-1721

New Insurance Class Report Filter

Under the Report Filters section, a new hyperlink for report filter named Insurance Class has been added for users to run the report to filter results based on Insurance Class.

[Image: screenshot]

JIRA # WSP-1482

========================================================================

Changes to the Benefit Rules form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-1603%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-1603 (Epic).htm

Changes to the Benefit Rules form

Under the Contribution Rules section, the earlier contribution rule header displayed different font colors for Insurance Class with Medical/Dental/Vision plans with non-banded plans and the banded plans.

Now, the contribution rule header font color displays the same across different banded and non-banded plans to maintain consistency.

[Image: screenshot]

JIRA # WSP-1713

Changes to the Group Benefit Plans form

When you save a Group Benefit Plan with a Rebate Bill Code in any of the Deduction Code fields and if any Bill Codes are present, then the system displays a warning message stating, WARNING: A deduction code with a value in the Rebate Bill Code field added to a Group Benefit Plan with Bill Codes will cause the employee deduction amount to be returned twice since the bill code already handles both billing & reimbursement. Are you sure you want to continue?.

[Image: screenshot]

JIRA # WSP-1860

Changes to the Retirement Plan Enrollment form

While creating a new election/contribution or updating an existing election/contribution under the Election Details and the Extra Contributions sections, a new default option named –Select– has been added when the values in the fields under these sections are null.

[Image: screenshot]

then an error message stating, Percent or Dollar selection must be made for election amount. is displayed.

then an error message stating, Percent or Dollar selection must be made for catch-up election amount. is displayed.

[Image: screenshot]

then an error message stating, Percent or Dollar selection must be made for extra contribution amount. is displayed.

[Image: screenshot]

JIRA # WSP-1954

Changes to the Benefit Salary Maintenance form

Under the Benefit Salary History section, you can now delete a future dated benefit salary record.

[Image: screenshot]

JIRA # WSP-1969

Changes to the Employee Flexible Spending Accounts form

Under the Flexible Spending Accounts section, a new read-only field named Next Pay Date has been added for you to view the employee’s next scheduled pay date on the form.

[Image: screenshot]

Note: For the Next Pay Date field to be displayed, the payroll process must be in timesheet entry state and the payroll must not be calculated. If a payroll has been calculated and finalized then the Next Pay Date field will display as expected.

JIRA # WSP-2019

========================================================================

Changes to Client Benefit Plan Import form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-2023%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-2023 (Epic).htm

Changes to Client Benefit Plan Import form

A new hyperlink named Download Sample Header File has been added on the Client Benefit Plan Import form. Click this hyperlink to download a sample header file in a .csv format on your system with all the applicable column headers.

[Image: screenshot]

Additionally, a new column for Only apply to S-Corp Principal Employees has also been added to the sample import file available on the Client Benefit Plan Import form.

JIRA # WSP-2014, WSP-2032

========================================================================

ZIP Code selector changed on the Payees form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-2026%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-2026 (Epic).htm

ZIP Code selector changed on the Payees form

In order to provide a consistent and contextual customer experience on the Payees form, we have changed the ZIP Code selector on this form.

[Image: screenshot]

JIRA # WSP-2112

========================================================================

Employee selector changed on the following FSA/HSA forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-2027%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-2027 (Epic).htm

Employee selector changed on the following FSA/HSA forms

In order to provide a consistent and contextual customer experience along with the convenience of using filters across FSA/HSA forms, we have changed the Employee selector on the following forms:

Employee Flexible Spending Accounts form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2094

Employee Flexible Spending Accounts Inquiry form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2095

Flexible Spending Accounts Reimbursement form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2096

========================================================================

New Employee Assigned To option

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-2037%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-2037 (Epic).htm

New Employee Assigned To option

Benefit Plan Setup form

Under the Benefit Plan Setup section, after you have selected the Plan Class and the Plan ID, then under the

[Image: screenshot]

menu, a new option named Employee Assigned To has been added to display employees that are enrolled in the selected Benefit Plan.

Note: The Employee Assigned To option is available only if the Plan Class field is set to Group Benefit.

[Image: screenshot]

JIRA # WSP-2015

Enhanced Dashboard form

On the Enhanced Dashboard screen, under the At a Glance section, when you select Benefit Plans from the drop-down, then in the grid that is displayed, a new hyperlink to the count of employees enrolled in is added to the Enrollments columns.

[Image: screenshot]

JIRA # WSP-2038

========================================================================

Changes to the Retirement Match Nomenclature on different forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-2054%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-2054 (Epic).htm

Changes to the Retirement Match Nomenclature on different forms

Changes to the Employee Retirement Plan Register form

Under the Employee Retirement Plan Register) section, the earlier Employer Match and Employer Safe Harbor fields have been renamed as shown in the table below:

Earlier Field Name Current Field Name
Employer Matching Contributions Employer Contribution
Employer Safe Harbor Match (Type 1) Employer Safe Harbor Type 1 Contribution
Employer Safe Harbor Match (Type 2) Employer Safe Harbor Type 2 Contribution
PEO Matching Contribution PEO Contribution

[Image: screenshot]

JIRA # WSP-1990

Changes to the Retirement Adjustment Transaction Audit Report form

Now, on Retirement Adjustment Transaction Audit Report form, when you run a report, the following column names have been renamed:

Earlier Column Name Current Column Name
Matching Contribution Employer Contribution
PEO Match PEO Contribution
Safe Harbor Type 1 Match Safe Harbor Type 1 Contribution
Safe Harbor Type 2 Match Safe Harbor Type 2 Contribution

[Image: screenshot]

JIRA # WSP-1991

Changes to the Retirement Adjustments Import form

Under the Preview section, the earlier Employer Match and Safe Harbor columns have been renamed as shown in the table below:

Earlier Column Name Current Column Name
Matching Contribution (Optional) Employer Contribution (Optional)
Safe Harbor Type 1 Match (Optional) Safe Harbor Type 1 Contribution (Optional)
Safe Harbor Type 2 Match (Optional) Safe Harbor Type 2 Contribution (Optional)

[Image: screenshot]

JIRA # WSP-1992

Changes to the Retirement Contributions Register Report form

Now, on Retirement Contributions Register Report form, when you run a report, the following column names have been renamed:

Earlier Column Name Current Column Name
Employer Match Employer Contrib
Non-Elect Match Non-Elect Contrib
Safe Harbor (1) Match Safe Harbor Type 1 Contrib
Safe Harbor (2) Match Safe Harbor Type 2 Contrib

[Image: screenshot]

JIRA # WSP-1993

Changes to the Retirement Register Adjustment form

Under the Contributions section, the earlier Matching and Safe Harbor fields have been renamed as shown in the table below:

Earlier Field Name Current Field Name
Matching Contribution Employer Contribution
Safe Harbor 1 Contribution Safe Harbor Type 1 Contribution
Safe Harbor 2 Contribution Safe Harbor Type 2 Contribution

[Image: screenshot]

JIRA # WSP-2042

========================================================================

New High Deductible Plan Indicator

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2006June/WSP-2148%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 06June/WSP-2148 (Epic).htm

New High Deductible Plan Indicator

In order to for users to easily view whether or not a plan is an HDHP plan, a new indicator for High Deductible Plan has been added on the following forms:

Benefit Plan Setup form

Under the Benefit Plan Setup, a new read-only field named High Deductible Plan has been added between the TPA Plan ID Override and the View Deduction/Bill Codes fields.

[Image: screenshot]

Please note the following validations:

JIRA # WSP-2147

Employee Benefits Enrollment form

Under the Employee Benefits Enrollment section, a new read-only field named High Deductible Plan has been added between the Reported To Carrier and the Doctor ID fields.

[Image: screenshot]

Please note the following validations:

JIRA # WSP-2149

Client Benefits Overview form

Under the Client Benefits Overview section, a new column named HDHP Plan has been added between the Plan Description and the Rate Group columns.

[Image: screenshot]

Please note the following validations:

JIRA # WSP-2153

Employee Benefit Overview form

Under the Employee Benefit Overview table, a new column named HDHP Plan has been added between the Pre Tax and the Coverage Level columns.

[Image: screenshot]

Please note the following validations:

JIRA # WSP-2154

========================================================================

Changes to the Group Benefit Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2007July/WSP-1248%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 07July/WSP-1248 (Epic).htm

Changes to the Group Benefit Plans form

On the Group Benefit Plans form, the earlier States section has now been made a collapsible section and is located below the Web Enrollment Parameters section.

[Image: screenshot]

JIRA # WSP-1811

========================================================================

Changes to the Rate Groups form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2007July/WSP-2017%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 07July/WSP-2017 (Epic).htm

Changes to the Rate Groups form

Changes to the Billing Rate Group form Nomenclature

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-2152

New Rate Groups Import Template on the Data Import Tool form

A new Import Template named Rate Groups is added to the Data Import Tool form as shown below. This option is available only for Service Providers. You can click the Download Data File to download the Rate Groups template in a .csv file.

[Image: screenshot]

You can use this import template to import new Rate Groups for the client.

To import rate groups and display an on-screen report:

  1. Select Rate Groups from the Import Template menu.

  2. Select the Prepopulate file checkbox if you want to download the data file that includes all the fields that are being imported from the list of Rate Groups configured with a full export of all existing Rate Group data in a .CSV file.

  3. Click Find File to upload the file.

  4. After importing the file a message displays, File content successfully uploaded and ready to be imported. Click OK. The imported rate groups display and an Import button.

  5. Click Import. After the import finishes a message displays, File content successfully imported. View report for details. Click OK. A Report button displays.

  6. Click Report. An on-screen report displays the imported Rate Groups. (You can also download this report.)

  7. As part of this import process, the imported Rate Groups now display in the Rate Groups form.

Note: Note the following when using the Rate Groups import template:

Note: When you import the rate groups and generate a report, the heading of the report page displays an incorrect report title name. This issue will be fixed in the upcoming August release.

JIRA # WSP-2151

========================================================================

Changes to the Retirement Adjustment Transaction Audit Report form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2007July/WSP-2025%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 07July/WSP-2025 (Epic).htm

Changes to the Retirement Adjustment Transaction Audit Report form

New Columns Added

On the Retirement Adjustment Transaction Audit Report form, when you run a report, then on the report that is displayed, the following new columns have been added:

[Image: screenshot]

Note: On the Retirement Register Adjustment form, any existing data associated with these fields will automatically be displayed in the reports in their respective columns.

JIRA # WSP-2256, WSP-2257, WSP-2258, WSP-2260

Remove PEO Contribution Column

On the Retirement Adjustment Transaction Audit Report form, when you run a report, then on the report that is displayed, the PEO Contribution column, which was located between Loan Payment and Safe Harbor Type 1 Contribution columns has now been removed. This column is also not displayed on the XLS file that you export for the report.

Note: Any contributions made by the Employer will be displayed in the Employer Contribution column.

JIRA # WSP-2259

========================================================================

Selectors Changed

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2007July/WSP-2026%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 07July/WSP-2026 (Epic).htm

Selectors Changed

State selector changed on the Payees form

In order to provide a consistent and contextual customer experience on the Payees form, we have changed the State selector on this form.

[Image: screenshot]

JIRA # WSP-2113

ZIP Code selector changed on the Eligible ZIP Codes modal form

On the Group Benefit Plans form, under the Actions menu, when you select Eligible ZIP Codes, then on the Eligible ZIP Codes modal form, the following multivalue selector as shown below has been applied which displays the ZIP Codes that are assigned to City/Town or State.

[Image: screenshot]

The earlier Eligible Zip Codes modal form name has been renamed to Eligible ZIP Codes to include ZIP in all capital letters.

JIRA # WSP-2114

ZIP Code selector changed on the Network ZIP Codes modal form

On the Group Benefit Plans form, under the Actions menu, when you select Network ZIP Codes, then on the Network ZIP Codes modal form, the following multivalue selector as shown below has been applied which displays the ZIP Codes that are assigned to City/Town or State.

[Image: screenshot]

The earlier Network Zip Codes modal form name has been renamed to Network ZIP Codes to include ZIP in all capital letters.

JIRA # WSP-2115

Broker selector changed on the Group Benefit Plans form

In order to provide a consistent and contextual customer experience on the Group Benefit Plans form, we have changed the Broker selector on this form.

[Image: screenshot]

JIRA # WSP-2116

Debit Account selector changed on the Group Benefit Plans form

In order to provide a consistent and contextual customer experience on the Group Benefit Plans form, we have changed the Debit Account selector under the Corporate Account section on this form.

[Image: screenshot]

Additionally, the Debit Account selector has also been changed on the Corporate/Staffing Accounting modal form when you access it through the Actions menu and click Corporate/Staffing Accounting on the Group Benefit Plans form as shown in the image below:

[Image: screenshot]

Note: To view the Corporate/Staffing Accounting menu, you must add the BLENDED-STAFFING custom feature code on the System Parameters form.

JIRA # WSP-2117, WSP-2129

Credit Account selector changed on the Group Benefit Plans form

In order to provide a consistent and contextual customer experience on the Group Benefit Plans form, we have changed the Credit Account selector under the Corporate Account section on this form.

[Image: screenshot]

Additionally, the Credit Account selector has also been changed on the Corporate/Staffing Accounting modal form when you access it through the Actions menu and click Corporate/Staffing Accounting on the Group Benefit Plans form as shown in the image below:

[Image: screenshot]

Note: To view the Corporate/Staffing Accounting menu, you must add the BLENDED-STAFFING custom feature code on the System Parameters form.

JIRA # WSP-2118, WSP-2130

ZIP Code selector changed on the Employee Dependents form

In order to provide a consistent and contextual customer experience on the Employee Dependents form, we have changed the ZIP Code selector under the Address Details section on this form.

[Image: screenshot]

JIRA # WSP-2119

Plan Year Number selector changed on the following forms

In order to provide a consistent and contextual customer experience, we have changed the Plan Year Number selector on the following forms:

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-2120, WSP-2121, WSP-2122

Rule Template selector changed on the Benefit Plan Setup form

In order to provide a consistent and contextual customer experience, we have changed the Rule Template selector on the Benefit Plan Setup form when you select Plan Class as Group Benefit on this form.

[Image: screenshot]

JIRA # WSP-2123

Loan selector changed on the Retirement Register Adjustment form

In order to provide a consistent and contextual customer experience, we have changed the Loan selector on the Retirement Register Adjustment form.

[Image: screenshot]

JIRA # WSP-2124

========================================================================

Group Benefit Plans form Redesign

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-1248%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-1248 (Epic).htm

Group Benefit Plans form Redesign

Networks Section

On the Group Benefit Plans form, the Network related fields have been removed from the earlier States section and is now available in a separate collapsible section and is located above the States section. The Networks section is visible only when you select an existing Benefit Plan ID which has an Insurance Class setup as Medical, Dental, or Vision.

[Image: screenshot]

Earlier Drop-down options in the Billing Rates Vary By field Renamed to
No Rate Group
Yes Network
Both Rate Group and Network

JIRA # WSP-1812

ACA Section

When accessing the Group Benefit Plans form, the ACA section is visible only when you select an existing Benefit Plan ID which has an Insurance Class setup as Medical.

[Image: screenshot]

JIRA # WSP-1813

Carrier Code Maintenance Section

On the Group Benefit Plans form, the earlier Carrier Code Maintenance section has now been made a collapsible section and is located at the bottom of the form.

[Image: screenshot]

JIRA # WSP-1814

Online Enrollment Section

On the Group Benefit Plans form, the earlier Web Enrollment Parameters section has now been renamed to Online Enrollment.

[Image: screenshot]

JIRA # WSP-1815

========================================================================

Changes to the Eligibility by Benefit Group modal form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2025%20(Epic)%20WSP-2030.htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2025 (Epic) WSP-2030.htm

Changes to the Eligibility by Benefit Group modal form

On the Benefit Plan Setup form, after selecting a plan, when you navigate to the Actions menu and select Eligibility by Benefit Group, then on the Eligibility by Benefit Group modal form, a new field named Eligibility Days From has been added to use the employee’s Hire Date for eligibility calculations.

[Image: screenshot]

This field has the following drop-down options:

JIRA # WSP-2030

========================================================================

Changes to the Benefit Rules Import form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2025%20(Epic)%20WSP-2548.htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2025 (Epic) WSP-2548.htm

Changes to the Benefit Rules Import form

On the Benefit Rules Import form, a new link named Download Sample Header File has been added to download a sample header file with all applicable column headers in a CSV file format.

[Image: screenshot]

JIRA # WSP-2548

========================================================================

Selectors Changed

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2026%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2026 (Epic).htm

Selectors Changed

Rate Group selector changed on the Rate Groups form

In order to provide a consistent and contextual customer experience on the Rate Groups form, we have changed the Rate Group selector on this form.

[Image: screenshot]

JIRA # WSP-2018

Loan Number selector changed on the Employee Retirement Loans form

In order to provide a consistent and contextual customer experience on the Employee Retirement Loans form, we have changed the Loan Number selector on this form.

[Image: screenshot]

JIRA # WSP-2125

Transaction selector changed on the Retirement Register Adjustment form

In order to provide a consistent and contextual customer experience on the Retirement Register Adjustment form, we have changed the Transaction selector on this form.

[Image: screenshot]

JIRA # WSP-2126

Reference Number selector changed on the Flexible Spending Accounts Reimbursement form

In order to provide a consistent and contextual customer experience on the Flexible Spending Accounts Reimbursement form, we have changed the Reference Number selector on this form.

[Image: screenshot]

JIRA # WSP-2127

Client (Optional) selector changed on the Bulk Change Retirement Plan form

In order to provide a consistent and contextual customer experience on the Bulk Change Retirement Plan form, we have changed the Client (Optional) selector on this form.

[Image: screenshot]

JIRA # WSP-2128

ZIP Code selector changed with State filter option

In order to provide a consistent and contextual customer experience, we have changed the ZIP Code selector to add a new State filter option on the following forms:

[Image: screenshot]

JIRA # WSP-2240, WSP-2380

State selector changed on the Brokers modal form

On the Group Benefit Plans form, under the Actions menu, when you select Brokers, then on the Brokers modal form, the following selector as shown below has been applied for the State selector.

[Image: screenshot]

JIRA # WSP-2241

Multivalue ZIP Code selector with State filter option

The following multivalue selector as shown below has been applied to the following modal forms on the Group Benefit Plans form:

[Image: screenshot]

A filter for State has also been added to narrow down your ZIP Code search to the related state.

JIRA # WSP-2381

========================================================================

Employee selector changed on the following Benefit forms

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2028%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2028 (Epic).htm

Employee selector changed on the following Benefit forms

In order to provide a consistent and contextual customer experience along with the convenience of using filters across benefit forms, we have changed the Employee selector on the following forms:

Employee Benefits Enrollment form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2100

Employee Benefit Rule Overrides form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2101

Employee Benefits Register form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2102

Employee Benefit Overview form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2103

Employee Dependents form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2104

Benefit Adjustments form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2105

Wellness Status Change form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2106

Wellness Status History form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2107

Benefit Group Maintenance form

The following selector as shown below has been applied to this form which displays the employee details.

[Image: screenshot]

JIRA # WSP-2108

========================================================================

Changes to the Employee Dependents form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2391%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2391 (Epic).htm

Changes to the Employee Dependents form

Validations added to the Gender drop-down on the Employee Dependents form

The following validations are now added to the Employee Dependents form:

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-2392

New Gender Designation field

On the Employee Dependents form, under the Dependent Details section, a new field named Gender Designation has been added to allow you to define the gender designation of the dependents.

[Image: screenshot]

The newly added field is setup on the Self Identity Codes form as shown in the image below:

[Image: screenshot]

JIRA # WSP-2393

New Preferred Pronoun field

On the Employee Dependents form, under the Dependent Details section, a new field named Preferred Pronoun has been added to allow you to define the preferred pronoun of the dependents.

[Image: screenshot]

The newly added field is setup on the Self Identity Codes form as shown in the image below:

[Image: screenshot]

JIRA # WSP-2394

========================================================================

Changes to the Benefit Utilities form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2458%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2458 (Epic).htm

Changes to the Benefit Utilities form

Under the Benefit Utilities section, when you select Utility as Manage Orphaned Benefit Records, then under the Orphaned Record Type, a new drop-down option named Relationships have been added which displays the orphaned records due to missing relationship code.

[Image: screenshot]

The Results section displays the following columns:

[Image: screenshot]

JIRA # WSP-1703, WSP-2449

New Report button

When you select Utility as Manage Orphaned Benefit Records, then for the options under the Orphaned Record Type drop-down, when you click Search to run the report filters, then under the Results section that is displayed, a new button named Report has been added to allow you to export the report of orphaned records for the selected orphaned record types.

[Image: screenshot]

Additionally, the report header name that is displayed on clicking the Report button for each of the options under the Orphaned Record Type drop-down are as follows:

Orphaned Record Type Report Name Header
Benefit Plan Setup Orphaned Benefit Plan Setup Records
Group Benefit Plan Types Orphaned Group Benefit Plan Type Records
Plan Types Orphaned Plan Type Records

JIRA # WSP-2451, WSP-2452, WSP-2453

========================================================================

Changes to the Data Import Tool form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2460%20(Epic)%20WSP-2462.htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2460 (Epic) WSP-2462.htm

Changes to the Data Import Tool form

On the Data Import Tool form, when you select Import Template as Employee Dependents, then two new fields named Gender Designation and Preferred Pronoun have been added in columns 19 and 20. These two new fields are also available in the downloadable sample header file.

[Image: screenshot]

You can use these new fields to do the following:

Additionally, the following validations has been added to the Gender field:

JIRA # WSP-2462

========================================================================

Changes to the New Hire and Dependent Field Overrides form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2460%20(Epic)%20WSP-2463.htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2460 (Epic) WSP-2463.htm

Changes to the New Hire and Dependent Field Overrides form

On the New Hire and Dependent Field Overrides form, under the Dependents section, the following two new rows have been added:

[Image: screenshot]

JIRA # WSP-2463

========================================================================

Changes to the New Hire and Dependent Required Fields (Global) form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2460%20(Epic)%20WSP-2464.htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2460 (Epic) WSP-2464.htm

Changes to the New Hire and Dependent Required Fields (Global) form

On the New Hire and Dependent Required Fields (Global) form, under the Dependents section, the following two new rows have been added:

[Image: screenshot]

JIRA # WSP-2464

========================================================================

Insurance Carrier URL field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2008Aug/WSP-2786.htm Path: BA/Release-Notes/Enhancements/2025/2025 08Aug/WSP-2786.htm

Insurance Carrier URL field

On the Group Benefit Plans form, under the Online Enrollment section, the earlier deprecated field, Insurance Carrier URL is now available for users to provide detail about the insurance carrier. Additionally, all the previously assigned values to the Insurance Carrier URL field is also displayed.

Note: This field is available with a hidden Custom Feature Code, which is enabled only upon request from the clients.

JIRA # WSP-2786

========================================================================

Changes to the Benefit Rules form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/BA-4734%20(Epic)%20WSP-1788.htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/BA-4734 (Epic) WSP-1788.htm

Changes to the Benefit Rules form

On the Benefit Rules form, when you select a Benefit Plan and the Effective Date, the system now checks if the Allow Gross Wage % Contribution Method field has been flagged for the selected Benefit Plan on the Group Benefit Plans form and also if the plan has a value in the Max Contribution column, then a warning message stating, Benefit Plan had a Max Contribution previously assigned and is now setup to use ‘Allow Gross Wage % Contribution Method’. This record must be saved in order to resolve this conflict. is displayed.

[Image: screenshot]

JIRA # WSP-1788

========================================================================

Group Benefit Plans form Redesign

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-1248%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-1248 (Epic).htm

Group Benefit Plans form Redesign

Relocating the Allow Gross Wage % Contribution Method checkbox

When accessing the Group Benefit Plans form, the earlier Allow Gross Wage % Contribution Method checkbox has now been relocated under the ACA section.

Note: The ACA section is visible only when you select an existing Benefit Plan ID which has an Insurance Class setup as Medical.

[Image: screenshot]

JIRA # WSP-2485

========================================================================

New Overage Enrollees Report form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2016%20(Epic)%20WSP-2206.htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2016 (Epic) WSP-2206.htm

New Overage Enrollees Report form

A new form named Overage Enrollees Report has been introduced to run a report of overage enrollees for benefit plans where Maximum Age has been defined in the Benefit Rules eligibility criteria.

[Image: screenshot]

Note: This form is for Employee enrolles only.

To access this form, click Reports. Under Benefits|Report, click Overage Enrollees Report.

The form has the following section:

The report page displays the following columns:

Note: You can export the report results into XLS file format.

JIRA # WSP-2206, WSP-2231

========================================================================

New Maximum Age field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2016%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2016 (Epic).htm

New Maximum Age field

In order to set a maximum age value for eligibility in a given plan while administering client Benefit Plan Rules, a new field named Maximum Age has been added under the Eligibility Rules section of the following form:

[Image: screenshot]

JIRA # WSP-2205, WSP-2481, WSP-2487

========================================================================

Changes to the Data Import Tool form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2025%20(Epic)%20WSP-2529.htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2025 (Epic) WSP-2529.htm

Changes to the Data Import Tool form

On the Data Import Tool form, when you select Import Template as Employee Dependents, an informational message stating, Required fields may vary based on client setup for New Hire and Dependent Field Overrides has been added. Additionally, the Required? status has been set to Yes for only those fields that are always required. These fields are:

All the remaining fields have been set as No and the columns header for these fields display as Optional in the sample header file.

[Image: screenshot]

JIRA # WSP-2529

========================================================================

Changes to the Employee Dependents form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2025%20(Epic)%20WSP-2546.htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2025 (Epic) WSP-2546.htm

Changes to the Employee Dependents form

On the Employee Dependents form, the Social Security Number is now masked based on the option that you choose to mask SSN from the SSN Mask Option field on the System Parameters form.

For example, on the System Parameters form, if you choose Show Last Four (###-##-6789) as the option from the SSN Mask Option field, then on the Employee Dependents form, when you add SSN for the dependent, the SSN will be masked to display only the last four digits as shown in the image below:

[Image: screenshot]

Note: If there is a client level override for the SSN Mask Option, then that option will override the System Level setting.

JIRA # WSP-2546

========================================================================

Update to the Transaction selector on the Retirement Register Adjustment form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2025%20(Epic)%20WSP-2631.htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2025 (Epic) WSP-2631.htm

Update to the Transaction selector on the Retirement Register Adjustment form

On the Retirement Register Adjustment form, the Transaction selector has been updated to include Name in the Search criteria for you to search by Employee Name when trying to find an employee’s Retirement Register Adjustment transaction. Additionally, two new columns named First Name and Last Name has been added to display results when you search by Name.

[Image: screenshot]

JIRA # WSP-2631

========================================================================

Changes to the Group Benefit Plans form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2025%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2025 (Epic).htm

Changes to the Group Benefit Plans form

[Image: screenshot]

[Image: screenshot]

Once you choose the month from the drop-down, the options in the Day drop-down field automatically updates to the total number of days available for the selected month.

[Image: screenshot]

[Image: screenshot]

JIRA # WSP-1689, WSP-1730, WSP-1771, WSP-1773

========================================================================

Changes to the Retirement Plan Enrollment form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2250%20(Epic)%20WSP-2544%20&%20WSP-2513.htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2250 (Epic) WSP-2544 & WSP-2513.htm

Changes to the Retirement Plan Enrollment form

On the Retirement Plan Enrollment form, under the Election Details section, the Auto Escalation? field is now available to indicate whether Auto Escalation applies to an Elective Percent. This field will display only if the Auto Escalator field is checked for this retirement plan on the Benefit Plan Setup form.

A new read-only field named Next Auto Escalation Date is also added to display the next escalation date. This field is displayed only if you have checked the Auto Escalation? field. Additionally, when an employee is auto enrolled in a retirement plan, the Auto Escalation? field is automatically checked.

[Image: screenshot]

Please note the following validations on the Retirement Plan Enrollment form:

JIRA # WSP-2513, WSP-2544

========================================================================

Changes to the Benefit Plan Setup form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2250%20(Epic)%20WSP-2549.htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2250 (Epic) WSP-2549.htm

Changes to the Benefit Plan Setup form

On the Benefit Plan Setup form, after you have selected the Plan Class as Retirement, then under the Eligibility Criteria section, when you deselect the Auto Escalator field and save the form, then the system checks for any active retirement plan enrollment records that have the Auto Escalation? checkbox selected on the Retirement Plan Enrollment form and if there are any active retirement plan enrollment records, then a warning message stating, Auto escalator cannot be unchecked. There are employees using this auto escalator with active enrollments. Example: Employee Enrollment for Employee ID <Employee’s ID> and Effective Date <plan’s effective date> is displayed.

[Image: screenshot]

JIRA # WSP-2549

========================================================================

New Auto Escalate On field

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2250%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2250 (Epic).htm

New Auto Escalate On field

On the Benefit Plan Setup form, after you have selected the Plan Class as Retirement, then under the Eligibility Criteria section, a new field named Auto Escalate On has been added to define when the auto escalation must occur at the client level.

[Image: screenshot]

JIRA # WSP-2512

========================================================================

Changes to the Rate Groups form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2009Sep/WSP-2294%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 09Sep/WSP-2294 (Epic).htm

Changes to the Rate Groups form

On the Rate Groups form, when you select an existing Rate Group and save the form, the following validations have been added for the Premium Rate Group checkbox:

Note: If any Billing Rate or Premium Rate is found in any of the above mentioned validation, an error message stating, Rates are currently associated with this Rate Group. Changes to the ‘Premium Rate Group’ are not allowed. is displayed.

JIRA # WSP-2345

========================================================================

Group Benefit Plans form Redesign

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2010Oct/WSP-1248%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 10Oct/WSP-1248 (Epic).htm

Group Benefit Plans form Redesign

New Billing Section

On the Group Benefit Plans form, the Billing related fields from different sections have been moved to the newly created Billing section which is now available below the Group Benefit Plans section and it displays for all the insurance classes. Additionally, the earlier Corporate Accounts section has been removed and the fields that were present under that section have been moved to the Billing section.

[Image: screenshot]

The Billing section has now the following fields which were earlier under different sections:

Note: There is no change in the existing functionality.

JIRA # WSP-1816

New Plan Provisions Section

On the Group Benefit Plans form, the fields related to plan provisions from different sections have been moved to the newly created Plan Provisions section which is now available below the Billing section. This section displays only for all insurance class plans.

[Image: screenshot]

The Plan Provisions section has now the following fields which were earlier under different sections:

Dates and Timing

Participation Requirement

JIRA # WSP-1817

New Age Parameters Section

On the Group Benefit Plans form, the fields related to Age Parameters from different sections have been moved to the newly created Age Parameters section which is now available below the States section. This section displays only for plans that has Insurance Class as Medical, Dental, Vision, Disability, and Life Insurance.

[Image: screenshot]

The Age Parameters section has now the following fields which were earlier under different sections:

Note: There is no change in the existing functionality.

JIRA # WSP-1818

========================================================================

Changes to the Benefit Utilities form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2010Oct/WSP-1432%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 10Oct/WSP-1432 (Epic).htm

Changes to the Benefit Utilities form

Under the Benefit Utilities section, a new utility named Unarchive Enrollments has been added to unarchive employees web enrollment configurations so that the users can re-enable an online workflow that had previously been archived.

[Image: screenshot]

When you select the Unarchive Enrollments utility, the Report Filters section is displayed.

Under the Reports Filters section:

Now, click Search. A job control runs. Once the job control process is completed, click Close to view the list of archived employees.

The Results section displays the following columns:

Select the employee(s) that you want to unarchive and click Unarchive. Based on the number of records you have selected, a confirmation message stating, Archived Enrollments will be unarchived. Are you sure? is displayed.

JIRA # WSP-1433

========================================================================

New Prohibit 401(k) Deductions functionality

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2010Oct/WSP-2060%20(Epic).htm Path: BA/Release-Notes/Enhancements/2025/2025 10Oct/WSP-2060 (Epic).htm

New Prohibit 401(k) Deductions functionality

On the Retirement Plans form, under the Deduction/Bill Code Overrides grid, a new column named Prohibit Deductions and Prohibit Billing has been added to prevent employee Retirement Plan Enrollments from being created with deduction types indicated as Prohibited on this form.

[Image: screenshot]

Additionally, when you save the form with a Retirement Plan record, the system check for the following validation for each Deduction or Billing Code on the form:

JIRA # WSP-2655

Changes to the Retirement Plan Enrollment form

On the Retirement Plans form, under the Deduction/Bill Code Overrides grid, when the Prohibit Deductions is checked for a Retirement Plan Deduction Code then on the Retirement Plan Enrollment form, under the Election Details section, when you create a new Retirement Election detail, the corresponding Retirement Plan Enrollment Election Type field(s) gets disabled.

Additionally, if a previous election exists with values in the now prohibited Election Type, the new effective date does not populate data in to the prohibited (now disabled) field.

If an election amount already exists on the detail record for a prohibited deduction code type, and when you try to save the form, then a warning message stating, This retirement plan prohibits [deduction type] elections. Create a new enrollment detail record to update the employee elections. is displayed.

JIRA # WSP-2656

Changes to the Process Payroll form

[Image: screenshot]

Below is the table that shows the affected Retirement Plan Enrollment Deferrals for contributions due to prohibited Retirement Plan Deduction Code:

Prohibited Retirement Plan Deduction Code on the Retirement Plans form — Retirement Plan Enrollment Deferrals for contributions that shows calculation error/ payroll warning on the Process Payroll form

Employee Deferral Deduction Code — Pre-Tax Contribution

Employee Catch-Up Deduction Code — Catch-Up Contribution

Employee Post-Tax Deduction Code — Post-Tax Contribution

Roth Post-Tax Deduction Code — Roth Contribution

Roth Catch-Up Deduction Code — Roth Catch-Up Contribution

JIRA # WSP-2657, WSP-2787

Changes to the Slavic 401K Import form

On the Slavic 401K Import form, while performing the Slavic 401K import process, the following validations has been added:

[Image: screenshot]

JIRA # WSP-2664

Changes to the Benefit Plan Setup form

On the Retirement Plans form, if a retirement plan is configured with the Employee Deferral Deduction Code flagged to Prohibit Deductions, then on the Benefit Plan Setup form, when you set Plan Class as Retirement and select the retirement plan, then under the Eligibility Criteria section, the Auto Enrollment and the Auto Enrollment Percent fields are disabled.

For the prohibited retirement plan, if there is a value in the Auto Enrollment and Auto Enrollment Percent fields, then the existing values are displayed as it is but the fields remains disabled. When you save the form with existing values in these fields, then a warning message stating, This Retirement Plan has been updated to prohibit pre-tax contributions used for Auto-enrollment functionality. Saving this record will clear the values in the Auto-enrollment fields. Would you like to proceed? is displayed.

[Image: screenshot]

JIRA # WSP-2669

Changes to the Payroll Validation Report form

On the Payroll Validation Report form, when you run the report for a payroll batch and if an employee in the batch has a retirement plan deferral election for one or more deduction types flagged as Prohibit Deductions on the Retirement Plans form, then an error message stating, has retirement elections in prohibited by the plan setup. Deductions will not be taken. is displayed in the Payroll Validation Report output. This error message is displayed on the report shown on the screen as well as in the downloaded .csv output file.

[Image: screenshot]

JIRA # WSP-2702

========================================================================

Update to the Reference Number selector on the Flexible Spending Accounts Reimbursement form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2010Oct/WSP-2662%20(Epic)%20WSP-2640.htm Path: BA/Release-Notes/Enhancements/2025/2025 10Oct/WSP-2662 (Epic) WSP-2640.htm

Update to the Reference Number selector on the Flexible Spending Accounts Reimbursement form

On the Flexible Spending Accounts Reimbursement form, following updates have been made to the Reference Number selector:

[Image: screenshot]

JIRA # WSP-2640

========================================================================

Changes to the Employee Flexible Spending Accounts form

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Enhancements/2025/2025%2010Oct/WSP-2662%20(Epic)%20WSP-2665.htm Path: BA/Release-Notes/Enhancements/2025/2025 10Oct/WSP-2662 (Epic) WSP-2665.htm

Changes to the Employee Flexible Spending Accounts form

On the Employee Flexible Spending Accounts form, when you select an Employee and the Plan Year, then under the Flexible Spending Account Activity section, the earlier column names, Reimbursement and Log No. has been renamed to Reimbursement Amt. and Reference No. respectively.

[Image: screenshot]

JIRA # WSP-2665

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202401_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202401_MR.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
BA-1705 Previously, if you added a Life Insurance Benefit Plan for an employee prior to adding a Medical Plan for the same employee on the Employee Benefits Enrollment form (Benefit Enrollment Maintenance > Benefit Enrollments > Employee Benefits Enrollment), an incorrect error message displayed which listed the previously selected Life Insurance Plan ID as a Medical Plan: “Warning! Employee is already active in another medical plan [Currently Selected Medical Plan ID]. Warning! Employee is already active in another medical plan [Previously Selected Life Insurance Plan ID].” You could then select the Life Insurance Plan in the Plan to Replace field (with a Medical Plan still selected in the Benefit Plan field) and complete the enrollment record. This resulted in the employee’s previously added Life Insurance Benefit Plan being updated to a Status of Terminated. This issue is fixed.
BA-1792 On the At a Glance panel of the Enhanced Dashboard in Employee Benefit Enrollments > Employees view (with an employee selected to view the employee details), if you selected Actions > Benefit Adjustments on a Plan ID line item, the Employee field was editable instead of Read Only as it had been in prior releases. This issue is fixed. Now, when you navigate from the At a Glance panel of the Enhanced Dashboard in Employee Benefit Enrollments > Employees view to access an employee’s Benefit Adjustments, the Employee field is Read Only.
BA-1801 On the At a Glance panel of the Enhanced Dashboard in Employee Benefit Enrollments > Employees view (with an employee selected to view the employee details), if you clicked a Plan ID link to view the Employee Benefit Enrollments form, the Employee field label was being overwritten by other text causing it to be illegible. Additionally, the Employee field was editable instead of Read Only as it had been in prior releases. This issue is fixed. Now, when you navigate from the At a Glance panel of the Enhanced Dashboard in Employee Benefit Enrollments > Employees to view the Employee Benefits Enrollments form by clicking the Plan ID link, the Employee field label is no longer being overwritten by other text and Employee field is Read Only.
BA-1816 Previously, the date formatting of the Birth Date column on the File Content tab of the Employee Dependents Data Import (Operations > Import Processing > Data Import Tool > Import Template = Employee Dependents) was inconsistent as it displayed date values as formatted in the import file. Examples: 2/5/20, 02/05/2020, 02/05/20. This issue is fixed. Now, the Birth Date column displays all date values in the same two-digit month, two-digit day, and four-digit year format which is the same format they will be in once imported into the system. Example: 02/05/2020.
BA-1960 Previously, on the Benefit Adjustments form (Benefit Enrollment Maintenance > Benefit Enrollments > Benefit Adjustments) the Filter by Plan dropdown selector field overlapped part of the Benefit Plan description (i.e., Plan Name) that displays to the right of the field. This issue occurred when the Plan Name was longer than approximately 17 characters. This issue is fixed.
BA-2111 Previously, you could not manually add a Benefit Plan ID that contained any lowercase letters to the Plan field of the Eligible Benefits - Group Benefits Plans section on the Benefit Groups form (Benefit Plan Maintenance > Group Benefit Plans (Client) > Benefit Groups). This issue is fixed. Now you can manually add a Benefit Plan ID containing lowercase letters to the Benefit Groups form.
BA-2126 Previously, you could not enter negative numbers in the Transaction Amount field with a Transaction Type of Service Fee or Adjustment on the COBRA Transaction Entry form (COBRA Processing > COBRA Processing > COBRA Transaction Entry). This issue is fixed. You can now enter negative amounts for Service Fee and Adjustment on the COBRA Transaction Entry form.
BA-2157 Previously, there was a form refresh issue when accessing an Employee Dependent record from the Employee Benefits Enrollment form using the specific scenario below: 1. Access the Employee Benefits Enrollment form, select an employee (using the Employee link), and select a Benefit Plan. 2. Select Dependents on the Actions menu and then select a Dependent ID on the Employee Dependents form. 3. Close the Employee Dependents form. 4. Select a different employee on the Employee Benefits Enrollment form (using the Employee link), and select a Benefit Plan. 5. Select Dependents on the Actions menu and then select a Dependent ID on the Employee Dependents form. 6. Close the Employee Dependents form. 7. Now, select the same employee originally selected in Step 1 (using the Employee link), and select a Benefit Plan. 8. Select Dependents on the Actions menu and then select a Dependent ID on the Employee Dependents form. Prior Result:The dependent record for the previously selected employee (Step 4) displayed. This issue is fixed.
BA-2158 Previously, enabling the PENDING-BILL-RATE-CLIENT or PENDING-BILL-RATE-GLOBAL custom feature codes created a field display issue on the Benefit Plan Setup form. When you changed the Plan Class on the Benefit Plan Setup form from Group Benefits to any other Plan Class, two fields related to the custom feature codes (Pend Prem Rate Group and Pend Prem Rate Group Effective Date) that were previously displaying in the Group Benefits Setup section of the Benefit Plan Setup form moved to the top of the form. The fields appeared to be “floating” as they were no longer anchored to a section of the form. This issue is fixed.
BA-2168 Previously, when you used the multi-select function to add additional plans to a Benefit Group (Benefit Plan Maintenance > Group Benefit Plans (Client) > Benefit Groups) and there were one or more previously selected plans already displayed in the “Eligible Benefits - Group Benefit Plans” section, the system attempted to add the existing selections to the list again while also the newly selected plans. This resulted in the following error: “Value [Plan ID] has already been entered here.” This issue is fixed.
BA-2194 Previously, COBRA Election Notice Monthly Premium calculation incorrectly used Premium Rates (i.e., Actual Cost) when the COBRA Premiums Based On field on the COBRA Processing Parameters form (COBRA Processing > COBRA Setup > COBRA Processing Parameters) was set to Standard Billing. This issue is fixed. Now, the COBRA Election Notice Monthly Premium calculations are derived as follows: - When the COBRA Premiums Based On field on the COBRA Processing Parameters form is set to Standard Billing, the Monthly Premium equals Billing Rate plus the percentage entered in the COBRA Insurance Premium Markup field. - When the COBRA Premiums Based On field on the COBRA Processing Parameters form is set to Actual Cost, the Monthly Premium equals Premium Rate plus the percentage entered in the COBRA Insurance Premium Markup field. > Note: Note: The default COBRA Premium Markup is 2%.
BA-2260 Previously, if you moved an employee to a new benefit group, any prior Life Insurance enrollment record could not be accessed (Benefit Enrollment Maintenance > Benefit Enrollments > Employee Benefits Enrollment) if there was no benefit rule on the new client or the new benefit group dating back to the original coverage start date of the enrollment. An error displayed and the record could not be opened. This issue is fixed. Now, the enrollment record displays with the following warning message: “No Benefit Rule date found for coverage date {coverage start date} BENEFIT RULE MISSING, Client# {client number} Group: {group ID}” Click OK on the warning message to proceed with opening the enrollment record.
BA-2490 Previously, if you cloned a client (Client > Action > Clone Client) and the Benefit Groups option was not selected under “What to Clone”, the system incorrectly created a Benefit Group association using the New Client ID value as the Benefit Group ID. The associated Benefit Group ID did not actually exist. Therefore, when you added benefit plans to the newly cloned client record, the following error displayed: “Warning: There are issues with this plan’s set-up. Please fix the items listed. Unable to find any Benefits Rules for Benefit Group [Associated Benefit Group ID].” This issue is fixed. Now, when you clone a client, only the default PRIMARY Benefit Group is associated with the cloned client if the Benefit Groups option is not selected as an item to clone in the “What to Clone” section of the Clone Client form. If the Benefit Groups option is selected as an item to clone in the “What to Clone” section of the Clone Client form, the benefit groups associations on the “cloned from” record are added to the cloned client record.
BA-2493 Previously, the validation of Gender on the Employee Dependents Import (Operations > Import Processing > Data Import Tool > Import Template = Employee Dependents) was incorrect. A correct Gender value of M or F resulted in the system erroneously displaying “Error uploading file content. See Messages tab for details.” during the import. The Messages tab displayed: “Error: Gender on line 2 must be M or F”. This issue is fixed. This system now properly evaluates and validates M or F Gender values and no longer displays the import errors.
BA-2499 Previously, when adding a new Employee Benefit Rule Override (Benefit Enrollment Maintenance > Benefit Enrollments > Employee Benefit Rule Overrides) for a Life Insurance Plan and selecting a Multiplier Pay Basis in the Coverage Rules section, upon Save, the Multiplier Pay Basis selection was not held. When you returned to the record the field was reset to –Select–. This issue is fixed. The Multiplier Pay Basis selection is now held upon Save.
BA-2503 Previously, the first occurrence of the word “maximum” was misspelled on the following error message that displays on the Employee Benefits Enrollment form (Benefit Enrollment Maintenance > Benefit Enrollments > Employee Benefits Enrollment) when you enter a life insurance plan with an age reduction schedule whereby the coverage amount entered causes the maximum coverage basis to be exceeded: “An age reduction schedule is being applied based on the group benefit plan setup. The coverage amount $X,XXX,XXX.XX entered results in a coverage basis, $X,XXX,XXX.XX that exceeds the maximum amount of $X,XXX,XXX.XX . The maximum coverage amount you can enter is $X,XXX,XXX.XX.” This issue is fixed.
BA-2509 Previously, when you used Copy Benefit Plan on the Group Benefit Plan Actions menu (Benefit Plan Maintenance > Group Benefit Plans (Global) > Group Benefit Plans > Actions) to copy to a new Plan ID containing lowercase letters in the Benefit Plan ID to Copy to field (Client > Change > Copy Benefit Plan), the copy function converted all lowercase letters to uppercase. The issue is fixed. Now, the new Plan ID is copied as entered.
BA-2526 Previously, the drop down selector for the Extra Voucher Types field located in the Extra Options section of the Retirement Plan Enrollment form (Benefit Enrollment Maintenance > Retirement Enrollments > Retirement Plan Enrollment) did not display for certain users due to a caching issue. This issue is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202402_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202402_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the February 2024 monthly release.

JIRA Number Issue Summary Resolution
BA-2678 Previously, under the Benefits tab on the Client Details form, if you made changes to the HSA Plan field, the File Audit form would incorrectly display the Field Name changed as Coverage Ends On instead of HSA Plan ID. Now, under the Benefits tab on the Client Detailsform, if you make changes to theHSA Plan field, the File Audit form would correctly display the Field Name changed as HSA Plan ID.
BA-2591 Previously, when using an Import Template file to import Network Zip Codes on the Data Import Tool form, PrismHR did not import those network zip codes from the import template file that contained spaces. However, it incorrectly provided an on-screen confirmation stating “File content successfully imported. View report for details.” Now, when using an Import Template file to import Network Zip Codes on the Data Import Tool form, PrismHR correctly imports network zip codes from the import template file that contain spaces.
BA-2189 Previously, on the Benefit Rules form after you had selected an Effective Date for a Benefit Plan, if you clicked on the Search Bar above, then the values in the Total Contribution column under the Contribution Rules section did not display on screen. This happened when either Employee or Company was selected for the Contribution rule amounts made by Company or Employee field. Now, on the Benefit Rules form after you have selected an Effective Date for a Benefit Plan, if you click on the Search Bar above, then the values in the Total Contribution column under the Contribution Rules section display correctly. This happens when either Employee or Company is selected for the Contribution rule amounts made by Company or Employee field.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202403_QR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202403_QR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the March 2024 quarterly release.

Jira Number Issue Summary Resolution
BA-3163 Previously, life coverage amount was getting auto updated to salary multiplier and/or max coverage when previously enrolled in $0 coverage. When coverage is entered manually and when the employee coverage amount is zero or less than the minimum coverage defined, payroll should not alter the coverage amount and the coverage min/max should be ignored. However, when the employee coverage amount is zero, the payroll process in PrismHR was updating the employee coverage to the calculated coverage maximum based on the defined plan parameters. This is now resolved via hotfix CM-3858. Now, when coverage is entered manually and when the employee coverage amount is zero or less than the minimum coverage defined, payroll does not alter the coverage amount and the coverage min/max is ignored.
BA-2667 Previously, for a medical plan that was Tobacco Banded, Gender Banded, Spouse Gender Banded, Age Banded, and Premium Rates Vary by Network was set to Yes, on the Group Benefit Plans form, then on the Premium Rates form: - The value in the To Age field in the first line was getting cleared out AND - The value in the From Age field in the second line defaulted to 1. Now, for a medical plan that is Tobacco Banded, Gender Banded, Spouse Gender Banded, Age Banded, and Premium Rates Vary by Network is set to Yes, on the Group Benefit Plans form, then all the fields on the Premium Rates form behave as expected.

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202404_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202404_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the April 2024 Monthly release.

Jira Number Issue Summary Resolution
BA-3163 Previously, life coverage amount was getting auto updated during payroll to salary multiplier and/or max coverage when previously enrolled in $0 coverage. Now, when coverage is entered manually and when the employee coverage amount is zero or less than the minimum coverage defined, payroll does not alter the coverage amount and the coverage min/max is ignored.
BA-3048 Previously, from the Group Benefit Plans form, using the Actions menu, once you open the Benefit Network Locations modal form, the system incorrectly provided an option to save it to your favorites. Now, from the Group Benefit Plans form, using the Actions menu, once you open the Benefit Network Locations modal form, the system correctly does not provide you any option to save it to the your favorites.
BA-2920 Previously, the system incorrectly allowed the Benefit Plan ID field to be editable for Billing Rates or Premium Rates for an Insurance Class other than Medical, Dental or Vision. Now, the system correctly does not allow the Benefit Plan ID field to be editable for Billing Rates or Premium Rates for any Insurance Classes.
BA-2855 Previously, for a benefit plan set up as Gender Banded or Spouse Gender Banded, on the Premium Rates and Billing Rates forms, if you used the Employee Gender dropdown, the Gender defaulted to red font even for existing rates which was incorrect. Now, for a benefit plan set up as Gender Banded or Spouse Gender Banded, on the Premium Rates and Billing Rates forms, even if you use the Employee Gender dropdown, the Gender displays the correct font color, that is Black if rates exist or Red if rates do not exist.
BA-2825 Previously, for a benefit plan set up as Billing Rates Vary By Network set as Both, on the Billing Rates Form, when you reviewed benefit rates after you input the required information, there was no Audit option available under the Actions menu. Now, for a benefit plan set up as Billing Rates Vary By Network set as Both, on the Billing Rates Form, when you review benefit rates after you input the required information, there is an Audit option available under the Actions menu.
BA-2822 Previously, for a benefit plan set up as Billing Rates Vary By Network set as Both, and at least one Network ID had been selected, then the Billing Rates Form incorrectly displayed a blank pop-up when you clicked anywhere on the form after you filled in the Network ID or Rate Group or Plan Type of Effective Date. Now, for a benefit plan set up as Billing Rates Vary By Network set as Both, and at least one Network ID had been selected, then the Billing Rates Form does not display any blank pop-up when you click anywhere on the form after you fill in the Network ID or Rate Group or Plan Type of Effective Date. Only once you save the form after making changing do you see a confirmation message.
BA-2745 Previously, if you clicked the Emp ID hyperlink on the Retirement Match P-T-D Register Report, it incorrectly displayed an error stating User Does not have access to form even for an employee actively enrolled in a retirement plan as per the Retirement Plan Enrollment form and who had either: - a past payroll having deduction for the retirement plan that was run or, - a Retirement Register Adjustment processed in a retirement plan year. Now, under similar conditions, if you click the Emp ID hyperlink on the Retirement Match P-T-D Register Report, it correctly displays the Employee Details form in a modal for the employee.

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202405_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202405_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following is a recent known issues that we’ve fixed in the May 2024 Monthly release.

Benefit Group History record created for every manual change

To ensure that the system always correctly captures any manual change made to the Benefit Group field, from now on, a Benefit Group History record will be created when a user manually changes the Benefit Group assigned to an employee on the Work tab of the Employee Details form. This change becomes effective immediately and the Benefit Group History record is stamped with an Effective Date which matches the date the change was made.

The Benefit Group field on the Employee Details form will remain enabled. When a user changes the value assigned to this field and selects “Save”, a Benefit Group History record will be created and stamped with the current date as the Effective Date. Benefit Group History records will be displayed on the Benefit Group History form and Benefit Group History Adjustment form.

Warning Scenario 1:

If a Benefit Group History record currently exists with an Effective Date equal to the current date (say if the current date is 04/24/2024), then the following warning message will display when the user enters a new value in the Benefit Group field:

[Image: screenshot]

Warning Scenario 2:

If a Benefit Group History record currently exists with an Effective Date greater than the current date (say Effective Date of 04/26/2024 if the current date is 04/24/2024), then the following warning message should display when the user enters a new value in the Benefit Group field:

[Image: screenshot]

Warning Scenario 3:

If a Benefit Group History record currently exists with an Effective Date equal to the current date (say current date is 04/24/2024) AND a Benefit Group History record also exists with an Effective Date greater than the current date (say 05/01/2024), the following warning message should display when the user enters a value in the Benefit Group field:

[Image: screenshot]

JIRA # BA-3298

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202406_QR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202406_QR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the June 2024 quarterly release.

Jira Number Issue Summary Resolution
BA-3502 Previously, users were unable to select a qualifying event in the COBRA Dependent Participant Questions form for one of their dependents who lost their coverage. Instead, the “Invalid dependent” error message displayed. Now, this is fixed.
BA-3370 Previously, in some scenarios, when importing benefit enrollment records using the Benefits Import form, some of the benefit enrollment records were missing a coverage detail effective date and details. Now, this is fixed.
BA-3249 Previously, when processing a Benefit Import for Fully Automatic Disability plans, the Coverage Amounts in the Coverage Details displayed as zero. Now, this is fixed.
BA-3069 Previously, Worksite Managers and Worksite Trusted Advisors were able to see the Import Benefit Adjustment hyperlink on the Benefit Adjustments form. Now, this has been fixed. Worksite Managers and Worksite Trusted Advisors do not get to see the Import Benefit Adjustment hyperlink on the Benefit Adjustments form.
BA-3021 Previously, if you selected Group Benefits as the Plan Class on the Benefit Plan Setup form and then selected a Plan ID from the drop-down and then changed the Plan Class to class any other than Group Benefits from the drop-down, then the system incorrectly displayed the Risk Factor table on the form. Now, this is fixed.
BA-2628 Previously, the Benefit Summary Statement for a client did not display the employees who had HSA for the plan year. However, the Benefit Confirmation Statement for the employee displayed that information. Now, this is fixed.
BA-2538 Previously, when an employee was flagged as an S-Corp Principal under the Miscellaneous section on the Tax tab of the Employee Details form, and from the Actions menu when you opened the Employee Benefits Enrollment form and selected a benefit plan that was pre-tax, the pop up warning did not display that says ‘Warning! Employee is an S-Corp principal and you have selected a pre-tax plan. S-Corp Principals SHOULD NOT participate in Section 125 eligible plans’. However, if you went directly to the Employee Benefits Enrollment form, and pulled up the same employee and benefit plan, you did get that warning. Now, this is fixed.
BA-2504 Previously, the system did not allow to enter coverage or rates for life insurance, short term disability and long term disability plans which were set to Coverage and Premiums entered manually. Now, this is fixed.
BA-1756 Previously, on the Group Benefit Plans form, under the Coverage Details section, the Age field was displaying for Insurance Classes that it should not. Now, on the Group Benefit Plans form, under the Coverage Details section, the Age field will only display for Insurance Class set as Life Insurance, Short Term Disability or Long Term Disability, when a spouse coverage amount is entered.
BA-1753 Previously, for Life Insurance class plans, the conditional Age field under the Coverage Details section on the Employee Benefits Enrollment form was not always working as desired. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202407_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202407_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the July 2024 monthly release.

Jira Number Issue Summary Resolution
BA-3519 Previously, on the Retirement Plan Years form, under the Plan Year Reporting Periods section, a second line could not be entered as the system gave an error message. Now, you will be able to enter multiple Plan Year Reporting Periods on the Retirement Plan Years form.
BA-3518 Previously, on the Retirement Plans form, the drop-down for the Tax Class field had a blank option and the 408K - Simplified Employee Pension (SEP) option did not display. Now, on the Retirement Plans form, the drop-down for the Tax Class field does not have the blank option and 408K - Simplified Employee Pension (SEP) is displayed.
BA-3517 Previously, if you moved an employee to a new Benefit Group, any prior Disability Insurance (LTD or STD) enrollment record could not be accessed (Benefit Enrollment Maintenance > Benefit Enrollments > Employee Benefits Enrollment) if there was no benefit rule on the new client or the new Benefit Group dating back to the original coverage start date of the enrollment. Payroll calculation failed with an error stating Cannot calculate Coverage Basis on Plan for Employee . Now, this is fixed.
BA-3463 Previously, on the Deduction Carryover Calculation form, the logs for Total Plan Year EE Deduction to Date and Total Plan Year Company Match to Date fields did not reflect the correct values. Now, this is fixed.
BA-3449 Previously, Cafe Plan Contribution Benefit Plan flagged as prepay was looking ahead one month at cafe plan contribution amounts. Now, the Cafe Plan Contributions look one month ahead for Café Plans flagged as prepay.
BA-3374 Previously, Existing Effective Dates incorrectly displayed on Premium Rates form for Family Rated Network plans even before a Network ID was selected. Now, Existing Effective Dates display only after a Network ID is selected for Family Rated Network plans on Premium Rates form.
BA-3363 Previously, when a future dated update was made for an employee to any of the following forms, that value was incorrectly updating the Assessment Completion Date field under the Status section on the Employee Details form for that employee: - Division Change - Location Change - Benefit Group Change - Department Change - New Hire - Rehire - Employee Field Imports - Bulk Change Benefit Group - Standard Employee Import - Benefit Group Update API Now, this is fixed.

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202408_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202408_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the August 2024 monthly release.

Jira Number Issue Summary Resolution
BA-3643 Previously, the contribution pool was being applied per plan instead of an accumulative amount across all cafe eligible plans. Now, this is fixed.
BA-3580 Previously, access to Benefit Network Locations form (Group Benefit Plans > Actions > Network Zip Codes) had security defined on it’s own stand alone form. Now, the access to the Network Zip Codes form is based on the security settings set up for the Benefit Plan Maintenance form.
BA-3176 Previously, on the Group Benefit Plans form, you could select Wellness Banded Rates even for plans which did not have Medical as the Insurance Class. Now, on the Group Benefit Plans form, you can only select Wellness Banded Rates for plans which have Medical as the Insurance Class.
BA-3136 Previously, users with Inquiry Access only to the Retirement Adjustments Import form were able to successfully import in adjustments. Now, all fields are disabled for users with Inquiry Access only to the Retirement Adjustments Import form.
BA-2960 Previously, in some scenarios, an incorrect double error message was appearing when selecting the Actions menu on the Group Benefit Plans form. Now, this is fixed.
BA-2766 Previously, after you entered a value on the Retirement Register Adjustment form and switched to another employee, the value for the previous employee did not clear on the form. Now, after you enter a value on the Retirement Register Adjustment form and switch to another employee, the value for the previous employee is cleared on the form.
BA-1169 Previously, resizing the browser while viewing the Employee Benefit Enrollments > Employee-specific dashboard view changed to Employee Benefit Enrollments > All Employees view. Now, this is fixed

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202409_QR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202409_QR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the September 2024 quarterly release.

Jira Number Issue Summary Resolution
BA-3600 Previously, the Retirement Register Adjustment incorrectly showed an error stating This transaction has already been posted. You may not post it again for new transactions when clicking save after resizing browser window. Now, this is fixed.
BA-3560 Previously, on the Retirement Plan Years form, under the Plan Year Reporting Periods section, you could enter the same value multiple times for the Period column. Now, on the Retirement Plan Years form, under the Plan Year Reporting Periods section, you can only enter unique values for the Period column. No duplicate values will be allowed.
BA-3405 Previously, when a change was made to the Wellness Qualification Status and Assessment Completion Date fields on the Employee Details form, the Wellness Status History form did not keep a full history causing administrative challenges with future dated changes. Now, this is fixed.
BA-3334 Previously, when an employee was hired mid-month (say 06/08/2024) in an auto enrolled plan with a 30 day waiting period (where Coverage Starts on 07/08/2024), the system was incorrectly creating a negative Benefit Adjustment for the prior month (202406), which is before the Benefit Effective Date. Now, this is fixed.
BA-3329 Previously, from the Group Benefit Plans form, under Actions menu when you chose the Premium Rates form BENEFIT.FRMED.NETWORK.RG.RATES.MNT, after selecting an option from the drop-down for the Network ID field the Service Area did not display on the right of the field. Now, from the Group Benefit Plans form, under Actions menu when you choose the Premium Rates form BENEFIT.FRMED.NETWORK.RG.RATES.MNT, after selecting an option from the drop-down for the Network ID field the Service Area displays on the right of the field.
BA-3191 Previously, when a plan was set up on the Group Benefit Plans form with: Insurance Class = Medical, Dental, or Vision Gender Banded = Selected Spouse Gender Banded = Selected AND With a Plan Type that is for Employee + Spouse or Family Coverage AND At least one existing Effective Date, then the Existing Effective Dates dropdown list did not appear for certain scenarios. Now, this is fixed
BA-3096 Previously, regarding: Enrollment: Given that an employee has coverage in a GTL eligible Life plan where the Deduction Start Date is after the Coverage Start Date, the taxable fringe pay amount (GTL) is not triggered when payroll is calculated/processed for a pay date that falls between the Deduction Start Date and Coverage Start Date. This situation usually occurs when an enrollment record is created and the current date is after the Coverage Start Date on the enrollment. In most cases, Benefit Adjustments have been created for the premium owed for this period of time. AND Termination: Given that an employee has coverage in a GTL eligible Life plan where the Deduction End Date is before the Coverage End Date, the taxable fringe pay amount (GTL) is not triggered when payroll is calculated/processed for a pay date that falls between the Deduction End Date and Coverage End Date. In most cases, Benefit Adjustments have been created for the premium owed for this period of time. Now this issue is fixed. The GTL logic will be utilized during the payroll process so that Benefit Deductions (to include Benefit Adjustments) for applicable Benefit Plans are included. The current GTL rounding, age, and basic calculation logic will not be changed. Given that an employee has coverage in a GTL eligible Life plan as of their pay date, the GTL calculation will be triggered, specified by using the lesser of the Coverage Start vs Deduction Start and greater of the Coverage End vs Deduction End dates to determine if the GTL calculation should occur.
BA-3009 Previously, on the Employee Benefit Rule Overrides form, once you clicked the New Effective Date hyperlink and entered a new Effective Date, then the all the relevant fields were not clearing as expected. Now, this is fixed.
BA-2957 Previously, on the Employee Benefit Rule Overrides form, once you clicked the Alternate Contribution Plan hyperlink, the Description column on the selector was blank. Now, on the Employee Benefit Rule Overrides form, once you click the Alternate Contribution Plan hyperlink, all the columns on the selector display as expected.
BA-2736 Previously, when a Benefit Plan was flagged as One Month Prepay and Add One Month For Prepay, and a Pending Premium Rate Group was assigned, the Pending Premium Rate Group was not being applied to the prepay premium cost on the payroll. Now, this is fixed.
BA-1588 Previously, when setting up an Import Definition in Benefit Import Maintenance, the system did not allow more than one SKIP field. Now, when setting up an Import Definition in Benefit Import Maintenance, the system allows as many SKIP fields necessary.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202410_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202410_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the October 2024 monthly release.

Jira Number Issue Summary Resolution
BA-3784 Previously, for a medical, dental or vision benefit plan with networks, where premium rate groups vary by network, the premium rate group form did not display the Rate Group on form report after a Network is displayed. Now, this is fixed.
BA-3961 Previously, after completing a transaction on the Retirement Register Adjustments form, if you moved away to a different form and then came back to the Retirement Register Adjustments form and reopened the transaction mentioned above, then the Plan field displayed blank for that transaction which was incorrect. Now, after completing a transaction on the Retirement Register Adjustments form, if you move away to a different form and then come back to the Retirement Register Adjustments form and reopen the transaction mentioned above, then the Plan field displays the correct benefit plan for that transaction.
BA-3943 Previously, when a new Effective Date was entered on the Employee Benefit Rule Overrides form, the date immediately disappeared from the form. Now, when a new Effective Date is entered on the Employee Benefit Rule Overrides form, the new date does not disappear from the form.
BA-3916 Previously, on the Retirement Plan Enrollment form, after selecting an employee without an active retirement enrollment record if you selected a Retirement Plan, and then resized the window to a smaller window and then back to full size, then the Retirement Plan field cleared out. Now, this is fixed.
BA-3899 Previously, on the Benefit Rules form, when the Contribution rule amounts made by Company or Employee field was set to Company, and under the Contribution Rules section the Contribution Method was set to Percentage, then the Total Contribution and the Total Billed fields did not populate the correct values. Now, this is fixed.
BA-3884 Previously, the Employee ID field got cleared upon resizing the browser on the standalone Employee Retirement Loans form. Now, this is fixed.
BA-3829 Previously, on the Employee Retirement Plan Register form, for a selected Employee ID, the Plan ID dropdown displayed the current plan along with any other prior plans which the employee was enrolled in, all with the status of the current enrolled plan. Now, on the Employee Retirement Plan Register form, for a selected Employee ID, the Plan ID dropdown displays only the current plan as having an active status and any other prior plans which the employee was enrolled in with no status.
BA-3806 Previously, if there was an HSA and a Dependent care flex spend account type on a posted payroll voucher, both hyperlinks only opened one Deduction Carryover Trace. It wasn’t pulling up the correct applicable trace when there were more than one flex spend account type hyperlink on the posted payroll voucher. (This was only applicable to HSA and Dependent care flex spend account types that are mid-year plans) Now, this is fixed.
BA-3761 Previously, whenever you clicked Save on the Employee Details form for an employee, a new Benefit Group History record was being created for that employee even if the Benefit Group was not changed. Now, this is fixed.
BA-3686 Previously, on the Group Benefit Plans form, under the Web Enrollment Parameters section, you incorrectly received an error message stating That is not a defined attribute when tabbing through blank column under the Process Attribute field. Now, this is fixed.
BA-3655 Previously, on the Benefit Plan Setup form, when adding a Flexible Spending Plan Class, under some scenarios, upon Save the Employment Type(s) field options selected were not saved for the FSA plan. Now, this is fixed.
BA-3654 Previously, under some scenarios, the custom feature code FAILINITSCORPFLEX was not working. Now, this is fixed.
BA-3641 Previously, on the Employee Benefits Enrollment form, in some scenarios, an additional blank dependent row was added to the Covered Dependents section after adding more than one covered dependent. Now, this is fixed.

Other Fixes

The following are some other issues that we’ve fixed in the October 2024 monthly release.

Jira Number Issue Summary Resolution
WSP-863 Previously, on the Enrollment Options form, the Spanish Header incorrectly read Life Events Documents Required (Spanish). Now, on the Enrollment Options form, the Spanish Header correctly reads Life Events - Documents Required (Spanish).
WSP-820 Previously, if an eligible record was created manually on the Employee Benefits Enrollment form for an employee having a dependent spouse, having Insurance Class selected as Life Insurance, Short Term Disability or Long Term Disability, and the Status is changed to Active, then a user was unable to enter a coverage amount in the Coverage field for the spouse. Now, if an eligible record is created manually on the Employee Benefits Enrollment form for an employee having a dependent spouse, having Insurance Class selected as Life Insurance, Short Term Disability or Long Term Disability, and the Status is changed to Active, then a user is able to enter a coverage amount in the Coverage field for the spouse.
WSP-821 Previously, even if a user did not have access to the Employee Details form but had full access to the any of the following forms, they were still able to access employee details on the Employee Details form by clicking the Employee ID hyperlink on the Employees Assigned To form listed under the [Image: screenshot] menu on that form. 1. Benefit Groups 2. Divisions 3. Departments 4. Positions 5. Projects 6. Worksite Locations 7. Shifts 8. Skills Now, this is fixed.
  1. Benefit Groups
  2. Divisions
  3. Departments
  4. Positions
  5. Projects
  6. Worksite Locations
  7. Shifts

  8. Skills

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202411_QR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202411_QR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the November 2024 monthly release.

Jira Number Issue Summary Resolution
BA-4016 Previously, in some scenarios, while processing payrolls, the system incorrectly generated an error stating Retirement Plan match rules not setup for Group:0 for an employee even though Group 0 did not exist under the Benefit Groups form. You had to soft save the Employee Retirement Plan Register for the employee to process payroll for that employee. Now this is fixed.
BA-4014 Previously, once you arrived at the Retirement Match Rules form for the first time for a client, and clicked the Benefit Group hyperlink, the selector showed only one benefit group. However, if you visited the Benefit Groups form and clicked the Benefit Group hyperlink, the selector showed all the applicable benefit groups. Now when you revisited the Retirement Match Rules form for the same client, and clicked the Benefit Group hyperlink, the selector showed all the applicable benefit groups. Now, this is fixed.
BA-4003 Previously, when you accessed the Benefit Adjustments form for an employee via the Enhanced Dashboard option, and then for a listed Benefit Plan once you changed the number of Cycles, the listed Benefit Plan ID disappeared once you returned to the Adjustment Details form after you clicked the Adjust button. Now, this is fixed.
BA-3923 Previously, when Relation was set up as a required field either on the New Hire and Dependent Field Overrides form or on the New Hire and Dependent Required Fields (Global) form, then on the Employee Dependents form if you selected the – Select – option after selecting any other option from the dropdown, then you received an incorrect error message stating Since the Relation Type is (D)ependent, you must indicate the Dependent Relation Code for this person! Press F3 for help. Now, this is fixed. On the Employee Dependents form, you only get an error message stating Relation is required when setting up a Dependent if you try to save a dependent without assigning a Relation from the dropdown.
BA-3905 Previously, users who did not have access to employee payroll vouchers were still able to view them using the Voucher hyperlink under the Account Activity section on the Employee Flexible Spending Accounts Inquiry form. Now, this is fixed.
BA-3889 Previously, on the Benefit Rules form, the description of the selected Benefit Group and Benefit Plan fields still displayed on the right even after it was included in the dropdown. Now, this is fixed.
BA-3880 Previously, the Retirement Plan field on the Employee Retirement Loans form was not disabled for an existing employee loan. Now, the Retirement Plan field on the Employee Retirement Loans form is disabled for an existing employee loan.
BA-3849 Previously, if you had Inquiry access to the Employee Retirement Plan Register form, you could not select the dropdown options for the fields on the form. Now, this is fixed.
BA-3465 Previously, on the Employee Benefit Rule Overrides form, if an Alternative Contribution Rate Group was entered but if there was no value in the Alternate Contribution Plan field, then upon Save, the values, if any, on the Employee Contribution Rules section were not getting cleared out. Now, on the Employee Benefit Rule Overrides form, if an Alternative Contribution Rate Group is entered but if there is no value in the Alternate Contribution Plan field, then upon Save, the value in the Alternative Contribution Rate Group field and the values if any on the Employee Contribution Rules section will clear out. You will receive a message stating An Alternate Contribution Plan has not been defined. The Alternative Contribution Rate Group and the Contribution Rules table (if applicable) will be cleared out.
BA-3000 Previously, mid year HSA plans with deduction carryover were not stopping HSA Matches when reaching tax year limit. Now, for mid year HSA plans, once the combined Company/PEO Match and Employee Contributions have met the tax year limit, no further Company/PEO Match and Employee Contributions are taken. Only ‘Standard’ HSA Match types are supported at this time.

Other Fixes

The following are some other issues that we’ve fixed in the October 2024 quarterly release.

Jira Number Issue Summary Resolution
WSP-821 Previously, even if a user did not have access to the Employee Details form but had full access to the any of the following forms, they were still able to access employee details on the Employee Details form by clicking the Employee ID hyperlink on the Employees Assigned To form listed under the [Image: screenshot] menu on that form. 1. Benefit Groups 2. Divisions 3. Departments 4. Positions 5. Projects 6. Worksite Locations 7. Shifts 8. Skills Now, this is fixed.
  1. Benefit Groups
  2. Divisions
  3. Departments
  4. Positions
  5. Projects
  6. Worksite Locations
  7. Shifts

  8. Skills

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2024/BA_Fixes_202412_MR.htm Path: BA/Release-Notes/Fixes/2024/BA_Fixes_202412_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the December 2024 monthly release.

Jira Number Issue Summary Resolution
BA-4314 Previously, mid-year HSA Deduction Carryover was calculating incorrect estimated total tax year amounts. Now, this is fixed. Only Standard HSA Match types are supported at this time.
BA-4152 Previously, in some scenarios, the Network ID dropdown on Employee Benefits Enrollment form displayed as blank and incorrectly generated an error stating 0 is not a valid network for plan . Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202501_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202501_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the January 2025 monthly release.

Jira Number Issue Summary Resolution
BA-4264 Previously, on the Group Benefit Plans form, all fields other than the Benefit Plan ID field cleared out when the browser was resized down. Now, this is fixed.
BA-4258 Previously, for Pre-Pay plans, when a Deduction Start Date was prior to the Coverage Starts Date, an incorrect benefit adjustment was being created Now, this is fixed.
BA-4178 Previously, on the Benefit Group Change form, if you entered a Benefit Group Start Date and then removed it, even before you saved the form, an error message stating New Job Start Date is mandatory displayed which was not correct. Now, on the Benefit Group Change form, under a similar circumstance, the error message reads New Start Date is mandatory.
BA-4165 Previously, when a future-dated Cafe Dollar contribution was added to an employee’s Benefit Group, that contribution was incorrectly applied to the employee’s current deduction. Now, future-dated Cafe Dollar contributions will not be applied to an employee’s benefit deduction until the effective date of that contribution.
BA-4110 Previously, on the Retirement Plan Enrollment form, after you had selected an Employee and without making any changes on the form clicked on the Import Retirement Plan Adjustment Quicklink under the Retirement Register Adjustments section, you got an error stating You have unsaved changes. Are you sure you want to leave? which was incorrect. Now, this is fixed.
BA-4097 Previously, when you had a Benefit Plan ID selected on the Group Benefit Plans form, and then you used the Back Office button to navigate to the Group Benefit Plans form again, you received an error stating Record BENEFIT.PLANSMAINT is not on file BENEFIT.PLAN.TYPES*. However, you could access the Group Benefit Plans form again using the search bar above without any error. Now, this is fixed.
BA-4084 Previously, if you got a message stating Create Your PrismONE ID either on My Home or on the Enhanced dashboard, upon closing the message the dashboard did not display the required information. Now, this is fixed.
BA-4068 Previously, though the Employee Benefits Rule Overrides form opened in a collapsed state until you selected a Benefit Plan or an existing plan to expand it, upon Save, Delete or Cancel, the form did not return to its initial collapsed state but remained in the expanded state. Now, this is fixed.
BA-4065 Previously, when you accessed the Employee Benefit Overview form using the [Image: screenshot] menu from the Employee Details form, the Dependent and the Coverage History information for the selected employee did not populate on the form in the first selection. Now, this is fixed.
BA-4029 Previously, on the Benefit Plan Setup form, after you had selected Flexible Spending as the Plan Class, once you checked the Use Benefit Groups field, a white space appeared below the section. This was purely a display issue with no impact on functionality. Now, this is fixed.
BA-4018 Previously, if you had INQUIRY access only to the Employee Retirement Plan Register form, if you opened a payroll voucher and then closed it on the form for an employee, then the Plan Year and Plan Year Period dropdowns wiped out and all applicable data. Now, this is fixed.
BA-4002 Previously, on the Adjustment Details form, you were able to adjust Cycles to a value lower than Cycles Billed which was incorrect. Now, this is fixed.
BA-3999 Previously, when an employee had been in multiple retirement plans and had transactions processed in a plan that was not the plan he was currently enrolled in, then on the Retirement Register Adjustment form, if you selected the prior transaction, the Plan ID populated with the current enrollment plan and not the plan the transaction was for. This was a display only issue and the data were correct. Now, this is fixed.
BA-3972 Previously, the system allowed you to incorrectly assign employees using the Employee Details form to a Benefit Group which had a Stop New Use On date in the past. Now, this is fixed.
BA-3766 Previously, enabling the PENDING-BILL-RATE-CLIENT or PENDING-BILL-RATE-GLOBAL custom feature codes created a field display issue on the Benefit Plans Setup form. When you changed the Plan Class on the Benefit Plans Setup form from Group Benefits to any other Plan Class, two fields related to the custom feature codes (Pend Prem Rate Group and Pend Prem Rate Group Effective Date) that previously displayed in the Group Benefits Setup section of the Benefit Plans Setup form moved to the top of the form. The fields appeared to be “floating” as they were no longer anchored to a section of the form. Now, this is fixed.

Other Fixes

The following are some other issues that we’ve fixed in the January 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-1288 Previously, on the Benefit Rules form, after you had selected the Benefit Group, Benefit Plan and the Effective Date fields, if you resized the window, then the Contribution Rules section disappeared from the form. You had to reselect all the above fields to make it reappear on the form. Now, this is fixed.
WSP-1283 Previously, on the Benefit Plan Setup form, for Plan Class selected as Flexible Spending and the Use Benefit Groups field being checked, if you opened the Eligibility by Benefit Group form using the [Image: screenshot] menu and the closed it, then a drop-down incorrectly displayed in the gray area at the bottom of the form. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202502_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202502_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the February 2025 monthly release.

Jira Number Issue Summary Resolution
BA-4432 Previously, using the Benefit Rules Import form, a change made to the Percent of Base updated the Benefit Rule record but the system was not using the updated amount for calculations. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202503_QR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202503_QR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the March 2025 quarterly release.

Jira Number Issue Summary Resolution
BA-4525 Previously, on the Employee Details form, under the Work tab, if the Retirement Benefit Group field had no value, then on the Benefit Utilities form, under the Results section for SH2 Auto Enroll utility, the Retirement Benefit Group column displayed the value of Benefit Group field. Now, this is fixed. On the Employee Details form, under the Work tab, if the Retirement Benefit Group field is not assigned for an employee, then the Retirement Benefit Group column in the Results section of Benefit Utilities form is displayed as blank.
BA-4440 Previously, on the Employee Details form, under the Pay tab, once you changed the Benefit Salary amount using the Change hyperlink and made another change to the Benefit Salary with the same effective date, the Benefit Salary field displayed the original change amount. It did not update the changed benefit salary to the newest record. This was a display issue only on the Pay tab as the last updated Benefit Salary History record displayed the updated amount. Now, this is fixed.
BA-4437 Previously, when a Check History Import was being done with HSA/FSA deductions, not all HSA/FSA deductions were importing for all employees. Now, this is fixed.
BA-4411 Previously, on the Employee Benefits Enrollment form, if the Coverage Starts Date is before the Deduction Starts Date for an Active plan for an employee, and upon Save if you wanted to review the billing adjustments, then when you first arrived on the Benefit Adjustment form, the Filter by Status field was missing. It appeared after you clicked somewhere on the form. Now, this is fixed.
BA-4383 Previously, if you had Inquiry access to the Benefit Group Maintenance form (formerly Benefit Group Change form), you could see and click the New Benefit Group hyperlink which was not desirable. Now, if you have Inquiry access to the Benefit Group Maintenance form (formerly Benefit Group Change form), the New Benefit Group hyperlink is disabled.
BA-4333 Previously, on the Benefit Group Maintenance form (formerly Benefit Group Change form), for a selected employee, if you clicked the New Benefit Group hyperlink in order to change the Benefit Group for the employee, the Select Benefit Group filter only displayed the current Benefit Group for the employee unless you clicked the Reset Search and Filters hyperlink. Now, on the Benefit Group Maintenance form (formerly Benefit Group Change form), for a selected employee, if you click the New Benefit Group hyperlink in order to change the Benefit Group for the employee, the Select Benefit Group filter displays all available benefit groups available for the client.
BA-4124 Previously, upon importing successor retirement deferrals using the Retirement Adjustments Import form, the Successor Retirement Deferral amount on the Retirement Match P.T.D Register Report for some such employees incorrectly showed double the amounts actually imported. Now, upon importing successor retirement deferrals using the Retirement Adjustments Import form, the Successor Retirement Deferral amount on the Retirement Match P.T.D Register Report for all such employees show the exact amounts actually imported.
BA-4069 Previously, when processing a Client Benefit Plan Import, you could not import the Wash Rule Day = EOM. You got an error stating WASH.RULE.DAY IS NOT IN THE RANGE OF 10 TO 20. Now, when processing a Client Benefit Plan Import, you can import the Wash Rule Day = EOM in addition to the current allowed range of 10-20.
BA-3966 Previously, on the Benefits Adjustments form, even after you opened an existing adjustment and while on the Adjustment Details form, the Filter By Status drop-down on the Benefits Adjustments form in the background did not get disabled. Now, this is fixed.
BA-3953 Previously, while on the Benefits Adjustments form, if you changed the client, the form did not clear completely as you would find it when you first arrived at the form. Now, this is fixed.
BA-3936 Previously, if the Stamp Date Used as Override Stop Date When EE is Terminated field on the Flex Spend Account Types form was set to Employee’s Date of Termination, then on the Employee Flexible Spending Accounts form, the Override Stop Date field reflected the Employee’s Date of Termination even for plan years which did not include the Employee’s Date of Termination. Now, the Override Stop Date will only populate when the Employee’s Date of Termination falls within the current FSA/HSA plan year or is before a future plan year.
BA-3836 Previously, in some scenarios, the age reduction was not occurring correctly if on the Group Benefit Plan form, under the Other Processing Parameters section, the Age Calculation Month was set to be Calculate as of 1st of Month of Employee’s birthday. Now, this is fixed.
BA-2991 Previously, on the Data Import Tool form, using the Import Template named Plan Comparison Data, if you tried to upload a .txt file, you would receive an error stating NO data was extracted from the file.$ and under the Messages tab an Error Message stating Error: The column headers in the data file do not match the headers set up for the offer type . Now, this is fixed.
BA-2876 Previously, on the Benefit Import Maintenance form, for a selected an Import Definition ID, under the Action Translations section, for the Standard Action Codes field you could not select DEPEN- option from the Select Benefit Import Action Codes filter and would receive an error message stating The Benefit Import Field ‘DEPEN-’ does not exists! Now, this is fixed.

Other Fixes

The following are some other issues that we’ve fixed in the March 2025 quarterly release.

Jira Number Issue Summary Resolution
WSP-1318 Previously, using the Offer Type template of the Data Import Tool, if you downloaded the data file with the Prepopulate file (all plans with BLANK Offer Type) field checked, then system incorrectly stripped the commas in the Plan Description field of the downloaded data file. So when you tried to populate the Offer Type and upload the data file, the system generated an error stating Plan Description on Line # may not be changed using this import. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202504_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202504_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the April 2025 monthly release.

Jira Number Issue Summary Resolution
BA-4586 Previously, on the Benefit Plan Setup form, when you assign a value in the Default Network ID field for a network plan, then on the Employee Benefits Enrollment form, the Network ID field did not display the assigned default network ID value as the first option in the drop-down list. Now, this is fixed.
BA-4577 Previously, on the Group Benefit Plans form, the Special Options section header and the Number of Years Guaranty field under the Special Options section was not displayed. Now, this is fixed.
BA-4540 Previously, on the Benefit Plan Setup form, after selecting Plan Class as Group Benefit, when you zoomed in the form, tool-tips were displayed for some fields which was incorrect. Now, this is fixed.
BA-4521 Previously, on the Purge COBRA Enrollees form, you were unable to select Participant ID from the Participant ID hyperlink. When you clicked this hyperlink, a message stating There are no items to display was displayed. Now, this is fixed.
BA-4469 Previously, on the Enhanced Dashboard screen, under the At a Glance section, when you selected Onboarding Tasks and then changed the client by clicking the client title at the top of the dashboard, then an error message stating Invalid Task Id was displayed. Now, this is fixed.
BA-4241 Previously, using the Retirement Exports form, for Vendor/Template selected as Pinnacle, you could download records for all employees for all clients even if you did not have full access to all the clients. The system did not honor restricted access to clients based on Client Access Group security. Now, using the Retirement Exports form, for Vendor/Template selected as Pinnacle, you could download records for all employees for only such clients for which you have full access only. The system honors restricted access to clients based on Client Access Group security.

Other Fixes

The following are some other issues that we’ve fixed in the April 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-1529 Previously, on the Data Import Tool form, after selecting the Import Template as Offer Type, when you imported a file with Plan Description value that had a comma (,) and the pipe (\ ) symbol then an error message stating Plan description on line 2 may not be changed using this import. was displayed in the Messages tab. Now, this is fixed. Also, the validation on the Plan Description field has been removed which means that this field is now not a required field.
WSP-1715 Previously, on the Pending Benefit Self-Billing Report form, when you select a date in the As Of Date field and run the report, the report results displayed the current or most recent effective coverage details date. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202505_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202505_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the May 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-1757 Previously, on the Benefit Rules form, the Percent of Gross Wages and Plan Setting fields overlapped with their input and read-only fields respectively when the browser was resized down. Now, this is fixed.
WSP-1758 Previously, on the Employee Benefit Rule Overrides form, the Percent of Gross Wages and Plan Setting fields overlapped with their input and read-only fields respectively when the browser was resized down. Now, this is fixed.
WSP-1809 Previously, on the Enhance Dashboard form, under the At a Glance drop-down, when you select Employee Benefit Enrollments and then under the Actions drop-down, when you click Employee Details, then the Close button overlapped with another button on each tab of the Employee Details form. Now, this is fixed.
WSP-1917 Previously, on the Benefit Plan Setup form, when a plan is assigned for both Retirement and Employer Match and when you changed the Plan Class, the plan option stayed selected but the applicable information was not populated. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202506_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202506_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the June 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-1710 Previously, the Remaining Plan Year Election Amount was calculated incorrectly where the system incorrectly used values for Total Plan Year Deductions to Date as the sum of Total Plan Year EE Deductions to Date, Total Plan Year Company Match to Date, and Total Plan Year PEO Match to Date. Now, this is fixed. The calculation of Remaining Plan Year Election Amount now takes the value used for Total Plan Year Deductions to Date as the Total Plan Year EE Deductions to Date only. Additionally, Standard Company HSA Match Contribution Method is the only method supported in preventing the limit from being exceeded. The other methods of Fixed, Scheduled, or Tiered are not supported in preventing the limit from being exceeded.
WSP-1711 Previously, on the Retirement Plan Enrollment form, after you have selected an Employee and entered a Retirement Plan, and then when you select an Effective Date and save the form, a pop-up message stating, Please re-enter the detail effective date. was displayed which was incorrect. Now, this is fixed.
WSP-1870 Previously, on the Employee Deduction Arrears form, toggling between employees caused the form to stuck on the first selected employee’s display. Now, this is fixed.
WSP-2089 Previously, on the Data Import Tool form, when you selected the Import Template as Plan Comparison Data and then selected an Offer Type, then on importing, the plan information was not being imported on the Benefits Enrollment Plan Details form. Now, this is fixed.
WSP-2139 Previously, on the Benefits Import form, when you selected an Import Definition Template that did not contain any $DEPN fields, then an error message stating, Import definition does not include $DEPN_SSN but file includes dependents was displayed. Now, this is fixed.
WSP-2140 Previously, when you accessed the Retirement Plan Enrollment form in a modal form through Navigation Search and when you selected an existing Effective Date under the Election Details section, a warning message stating, A detail record for that date already exists. Select it from the dropdown list. was displayed. Upon the display of the warning message, the data on the form cleared out and the Financial Details section was disabled, which was incorrect. Now, this is fixed.
WSP-2145 Previously, on the Retirement Adjustments Import form, when you uploaded a changed import file, the changes made on that import file were not displayed under the Preview section. You had to refresh the browser to view the changes made on the uploaded file. Now, this is fixed.
WSP-2175 Previously, when a Benefit Plan Setup for HSA Contribution is configured with Contribution Applies to for all HDHP-enrolled employees without an HSA account added to their Flex Spending Account Setup Elections, then the system automated the addition of an HSA account with a $0.00 Plan Year Election in the employee’s Employee Flexible Spending Account setup, even when the employee was already enrolled in an FSA plan. Now, this is fixed.
WSP-2176 Previously, when the Custom Feature Code USEWEEKLYBENEFITS was enabled, then on the Employee Deduction Arrears form, when an employee had enough deduction arrears to create a scroll, the scrolling caused the arrears to not display at the bottom of the page. Once a user selected the arrears checkbox, then only the hidden arrears record were displayed. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202507_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202507_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the July 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-2197 Previously, on the Enhanced Dashboard screen, from the At a Glance drop-down list, when you select Employee Benefit Enrollments and then navigate to the Actions column and select Employee Details modal form, then the Save & Close and the Close buttons overlapped on each tabs except the Name tab. Now, this is fixed.
WSP-2233 Previously, on the Employee Benefits Enrollment form, when you changed the employee, the Enter New Date field was pre-populated with the date value from the previous employee’s enrollment details, which was incorrect. Now, this is fixed.
WSP-2234 Previously, on the Employee Benefits Enrollment form, when you selected an Employee and choose an active Benefit Plan and then again selected the same employee, the screen retained data for some of the fields from the previous active plan that was selected for the employee, instead of refreshing the data. Now, this is fixed.
WSP-2255 On the Benefit Plan Setup form, under the Company HSA Contribution section, when you selected Contribution Applies To as All HDHP Employees, the system did not execute the auto-enrollment functionality for employees who did not meet all the eligibility criteria outlined in all fields of the Eligibility Criteria section. Now, this is fixed.
WSP-2262 Previously, the Notification Audit Report form allowed to filter results only by Client ID and Employee ID. This caused issues while running reports for larger clients. Now, two additional fields named Start Date and End Date has been added where you can provide a date range which must be within 1 year range to run and view the generated reports efficiently. Additionally, these newly added fields are mandatory.
WSP-2329 On the Employee Benefit Overview form, under the Billing History section, when different Benefit Plans have the same description, then the report combined the Billing Amounts under one of the Plans that had the duplicate plan description. Now, this is fixed.
WSP-2335 Previously, on the Benefit Billing Detail Report form, when you selected the Defined Ranges option as Last Batch and set the Primary Sort to Employee and the Secondary Sort to Benefit Plan, and then run the report, the report that was displayed sorted the results by Benefit Plan as the primary sort, which was incorrect. Now, this is fixed.
WSP-2338 Previously, on the Benefit Billing Detail Report form, under the Sort Parameters section, when you set Primary Sort to Location, Secondary Sort to Benefit Plan, and select Report Type as Detail and then run the report, then in the results that was displayed, the Total line displayed Total For Department instead of Total For Location, which was incorrect. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202508_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202508_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the August 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-1704 Previously, the system calculated a Non-Elective Match for the payroll even after the employee had attained or crossed the Compensation Limit under the Plan Year Deferral Limits section on the Retirement Plans form when the Non-Elective Match field on the Retirement Match Rules form is blank for the corresponding retirement plan. Now, the system will not calculate a Non-Elective Match for the payroll once the employee has attained or crossed the Compensation Limit under the Plan Year Deferral Limits section on the Retirement Plans form irrespective of whether the Non-Elective Match field on the Retirement Match Rules form is blank for the corresponding retirement plan or not.
WSP-1705 Previously, on the Group Benefit Plans form, under the Age Reduction Schedule section, the spouse or dependents premium for Voluntary Life was calculated incorrectly while enrolling the employee and the spouse. But when you selected the Reduce coverage and premium (default is reduce coverage only) checkbox, then the premium was calculated without an issue. Now, this is fixed.
WSP-1707 Previously, on the Benefit Rules form, while deleting a Benefit Rules for a specific Benefit Group that has enrollments as terminated/waived/pending, an error message stating, This benefit rule cannot be deleted. There are employees using this benefit rule with active enrollments. was displayed which was incorrect. Now, this is fixed.
WSP-1874 Previously, on the Benefit Rules Import form, when you uploaded a file and then clicked the Validate Import File button, the screen went blank without returning any values, which was incorrect. Now, this is fixed. While the job control is run an error, if any, is displayed on the job control screen to let you know about the mismatch of headers.
WSP-1976 Previously, on the Employee Deduction Arrears form, the Change Status button was displayed for users even if the Custom Feature Code named USEWEEKLYBENEFITS was not set, which was incorrect. Now, this is fixed.
WSP-2344 Previously, on the Employee Details form, under the Actions menu, when users accessed the Benefit Adjustments modal form, the users were unable to select the benefit adjustments record checkbox in a single click. To select the checkbox, users had to click for a second time. Now, this is fixed.
WSP-2413 Previously, when you accessed Employee Voucher either from the Process Payroll form or from the Employee Details form, then under the Deductions tab, when you clicked the HSA hyperlink, you could not view the calculations on the voucher and it showed a blank screen instead. Now, this is fixed.
WSP-2496 Previously, on the Benefit Utilities form, when you ran any of the orphaned utility options and then changed the option from the Orphaned Record Type drop-down and then resized the browser, the search results from the prior ran utility was displayed. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202509_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202509_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the September 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-1706 Previously, on the Employee Dependents form, when you created a dependent COBRA participant, it created under the wrong client. Now, this is fixed.
WSP-2401 Previously, on the Employee Benefit Rule Overrides form, when you used the tab functionality under the Employee Contribution Rules section, it caused inconsistency and validation issues. This issue also prevailed if the Max Contribution column had values in their multi-value grid components on the Benefit Rules form. Now, this is fixed.
WSP-2445 Previously, on the Group Benefit Plans form, under the Other Processing Parameters section, when you tried deleting an extra row from the Override Dependent Age Limits By State table, it did not delete the row. Now, this is fixed.
WSP-2579 Previously, on the Rehire form, when you select an employee, then under the Employee Details section, when you click the Benefit Group hyperlink, the Retirement or Benefit Plans Only column displayed Retirement Only Benefit Groups instead of Benefit or Both as values. Now, this is fixed.
WSP-2606 Previously, on the Benefit Plan Setup form, the Suppress Benefit Adjustment on Employee Termination field overlapped with the Default Network ID field when the browser was resized down. Now, this is fixed.
WSP-2627 Previously, on the Benefit Plan Setup form, when you set the Use Billing Wash Rule? to Yes, then the conditional field, Wash Rule Date On/Before that displayed did not display when the browser was resized down. Now, this is fixed.
WSP-2630 Previously, on the Retirement Register Adjustment form, when you selected a transaction from the Transaction selector, it resulted in displaying the Employee ID as the label for the Employee field instead of the Employee Name, which was incorrect. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Fixes/2025/BA_Fixes_202510_MR.htm Path: BA/Release-Notes/Fixes/2025/BA_Fixes_202510_MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the October 2025 monthly release.

Jira Number Issue Summary Resolution
WSP-1695 Previously, on the Benefit Summary Statement form, the SSN masking option for the client was not applied to the Benefit Summary Statement Report output. Additionally, on exporting to XLS file, the report omitted the SSN in the downloaded file. Now, this is fixed. The Benefit Summary Statement report now considers the client-level selection made for the SSN Mask Override field on the Report Print Options form while displaying the report results. Also, if there is no client-level override, then the Benefit Summary Statement report considers the selection made in the SSN Mask Option field on the System Parameters form while displaying report results.
WSP-2040 Previously, on the Benefit Plan Setup or Retirement Plans form, even when no eligibility rules were setup, the system allowed the enrollment of employees, which was incorrect. Now, this is fixed. On the Benefit Plan Setup form, when you select Plan Class as Retirement, and if the plan class does not have any eligibility criteria defined, then the system now looks at the Retirement Plans form for eligibility criteria. If eligibility criteria is not defined on the Retirement Plans form as well, then no employee is eligibile.
WSP-2281 Previously, on the Flexible Spending Accounts Reimbursement form, when you selected an existing Reference Number record for an employee and then selected the employee from the Employee selector, the values on the screen did not clear. Now, this is fixed. When you select an existing record, the Employee field now displays as a read-only field. Additionally, on saving a new record, the values in all the fields clears including the Employee ID.
WSP-2673 Previously, on the Employee Retirement Loans form, after selecting the Loan Number, under the Adjustments section, when you entered an amount in the Paid Back Adjustment field, then the read-only value displayed in the New balance equals field did not update the amount correctly. This issue was a ‘Display Only’ issue. Now, this is fixed.
WSP-2742 Previously, when you accessed an existing retirement loan record from the Employee Retirement Loans modal form, it did not allow to update any changes made to the form. Additionally, the modal form did not allow to delete a retirement loan record. While updating or deleting the record, a message stating, This record cannot be written as not all key parts have been filled was displayed, which was not the correct behavior. Now, this is fixed. The Employee Retirement Loans modal form now allows updating and deleting an existing record without any error.
WSP-2809 Previously, on the Group Benefit Plans form, when you selected a Benefit Plan ID and then reopened the Group Benefit Plans form, the Percent of Gross Wages multivalue grid overlapped on the screen. This issue also occurred while opening the Group Benefit Plans form in a modal window. Now, this is fixed.
WSP-2864 Previously, on the COBRA Participant Record form, when you created a Cobra Participant Record, then an error message stating, Error! This enrollee has no company number. You should print out their information, delete this record and then enter it again. was displayed, which was incorrect. Now, this is fixed.

========================================================================

Known Issue

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Known-Issues/2024/BA-3829.htm Path: BA/Release-Notes/Known-Issues/2024/BA-3829.htm

Known Issue

If an employee is enrolled in multiple Retirement Plans, on the Employee Retirement Plan Register form, the Plan ID dropdown displays the current Retirement Plan’s enrollment status for all those retirement plans.

[Image: screenshot]

This is a display issue. This will be resolved in an upcoming release.

JIRA # BA-3829

========================================================================

Known Issue

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Known-Issues/2024/BA-3999.htm Path: BA/Release-Notes/Known-Issues/2024/BA-3999.htm

Known Issue

When an employee had multiple retirement plans and had transactions processed in a plan that is not the plan they are currently enrolled in, on the Retirement Register Adjustment form, when you select the prior Transaction, the prior Plan ID is populated with the details from the current enrollment record and not the plan the transaction was for. The Annotation (plan description) is correct. This is a display issue and will be resolved in a future release.

[Image: screenshot]

JIRA # BA-3999

========================================================================

BA_Revision_202401_MR

Source: https://tech-docs.prismhr.com/SP_help/Content/BA/Release-Notes/Revisions/2024/BA/BA_Revision_202401_MR.htm Path: BA/Release-Notes/Revisions/2024/BA/BA_Revision_202401_MR.htm

Revision 01

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202401/CMP-Enhancements%20Jan-2024%20MR.htm Path: CMP/Release-Notes/Enhancements/2024/MR202401/CMP-Enhancements Jan-2024 MR.htm

Enhancements

This section describes general enhancements that were made in the PrismHR January 2024 monthly release.

Support for Iowa Form W-4

PrismHR now supports the updated 2024 Iowa Form W-4 effective 1/1/2024.

Read the following article on the Customer Resource Center for more information.

Montana & Iowa 2024 W-4 and Tax Withholding Updates

JIRA # CMP-5363

Support for Iowa State Withholding Tax Rate Table 2024

Effective 1/1/24, Iowa has revised their State Withholding Tax Rate Table. Read the following article on the Customer Resource Center for more information.

Montana & Iowa 2024 W-4 and Tax Withholding Updates

[Image: screenshot]

[Image: screenshot]

Note: Note: If the IA filing status override method is BLOCK WITHHOLDING no changes are applied.

JIRA # CMP-5365

Support for Montana Form W-4

PrismHR now supports the updated 2024 Montana Form W-4 effective 1/1/2024. Read the following article on the Customer Resource Center for more information.

Montana & Iowa 2024 W-4 and Tax Withholding Updates

JIRA # CMP-5319

Support for Montana State Withholding Tax Rate Table 2024

Effective 1/1/24, Montana has revised their State Withholding Tax Rate Table. PrismHR now supports the 2024 State Withholding Tax Rate Table, including those employees who have a filing status of Married Filing Jointly with Both Spouses Working. Read the following article on the Customer Resource Center for more information.

Montana & Iowa 2024 W-4 and Tax Withholding Updates

[Image: screenshot]

JIRA # CMP-5366

New Form I-9 - Remote Verification Indication

A new field named Remote Verification Used has been added under the Employment Verification section on the Tax tab of the Employee Details form to track if an employee’s I-9 documents are verified remotely or not. When an employee’s I-9 documents are remotely verified, the I-9 approver indicates that in Section 2 of the Form I-9. Then this Remote Verification Used field gets checked automatically.

[Image: screenshot]

JIRA # CMP-5255

Send Company Accounting Record in PTS file

A new field named Send Company Accounting Record in PTS file has been added to the MasterTax Interface Parameters form. If you are a PEO managing multiple client accounts, you can now populate the Company General Ledger record 105 within the PTS file for both SBEA and non-SBEA clients.

[Image: screenshot]

JIRA # CMP-5352

105 record now added to the PTS download file

The PTS download file has been updated to add the 105 record. This record only appears when the Send Company Accounting Record in PTS file field is checked on the MasterTax Interface Parameters form. This will be included in the 100 record for the PTS download.

Note: Note: At this time, the F code 100 record will be blank from positions 16-420.

JIRA # CMP-5307

Changes to Campbell Country Occupational License Fee

Effective 1/1/2024, Campbell County, KY has updated their Occupational License Fee. Campbell County Occupational License Fee of 1.05% will no longer be calculated under a single tax code. The tax will be broken out into three new tax IDs, with differing rates and maximum wages:

JIRA # CMP-5313

New Client Custom Feature Code DISABLE.OVERTIME.EXCEPTION.PAY

A new client level custom feature code named DISABLE.OVERTIME.EXCEPTION.PAY is now available in PrismHR. It is available on the Custom Features form which you can access from the Actions menu on the Client Details form. You can either enter this client level custom feature code directly on the form or click the Feature Code link and select it from the Select Available Feature Codes dialog box.

To support AL Overtime exemption effective 1/1/24, the custom feature code OVERTIME.EXCEPTION.PAY must be enabled at the system level. Prior to the client level custom feature code, you could enable this functionality for the entire system or none of the system. Now using this client level custom feature code, you can disable the logic for certain clients if they choose not to change their payroll method to support the automated calculations. For example, when OVERTIME.EXCEPTION.PAY is entered at the system level, the AL OT logic is activated. Adding DISABLE.OVERTIME.EXCEPTION.PAY in addition to the system code then deactivates the logic for that client only.

[Image: screenshot]

JIRA # CMP-5362

Updated Maryland State EFW2 export file

For tax year 2023 and beyond, the state of Maryland requires the RW (Employee) Record in the EFW2 download file. PrismHR now supports this update. The EFW2 download file for employees for the state of Maryland will now include the RW (Employee) Record in the specified format as per SSA Publication No. 42-007 EFW2 for Tax Year 2023.

JIRA # CMP-5288

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202402/CMP-Enhancements%20Feb-2024%20MR.htm Path: CMP/Release-Notes/Enhancements/2024/MR202402/CMP-Enhancements Feb-2024 MR.htm

Enhancements

This section describes general enhancements that were made in the PrismHR February 2024 monthly release.

Updates to VisionSTD_SP_FullPTO to Incorporate Custom Check Formatting

To support varying requirements in California and other states, a new check format named VisionSTD_ER_SP_FullPTO has been added to the Default Report Form dropdown in the Print Service Check Maintenance form. This new format will be included in the standard Compliance check options.

[Image: screenshot]

This format is similar to the existing format VisionSTD_SP_FullPTO; however, the memo section includes additional information regarding the Employer. On the Print Service Options form, when the Source of Name/Address on Checks field is set to Use Employers Address the memo section will report the Employer using the Client Legal Name and Address. The standard Service Provider information will be listed below the memo.

[Image: screenshot]

This format is available for specific use cases and may not be necessary for everyone.

JIRA # RRT-5648, CMP-5160

Updates to Form W-4 for Georgia

The state of Georgia updated its employee state withholding certificate (Form W-4) to indicate any changes in marital status, allowances, or other withholding considerations. PrismHR now supports the changes to support the data flowing from Employee Portal or Onboarding, and options presented in the New Hire and Employee Details forms.

In the Employee Details form, under the Tax tab, under the State Tax Filings section, when GA is selected as the State, and you click the Filing Status link:

[Image: screenshot]

[Image: screenshot]

JIRA # 5402

Updates to MTA-305 Report (Zone 1 and 2)

The state of New York updated the specifications for their New York Form MTA-305 Tax download electronic file. Effective July 1, 2023, for purposes of the MCTMT (Metropolitan Commuter Transportation Mobility Tax), the MCTD (Metropolitan Commuter Transportation District) is now divided into the following two district zones:

[Image: screenshot]

A summary of the changes are as follows:

[Image: screenshot]

Employers must file quarterly MCTMT returns if they are required to withhold New York State income tax from wages paid to employees and their payroll expense for all covered employees in the MCTD exceeds $312,500 in any calendar quarter.

For tax filing periods Q3 2023 and later, PrismHR now support the changes which result in the following changes to the New York Form MTA-305 Tax download electronic file:

JIRA # CMP-5169

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202404/CMP-Enhancements%20Apr-2024.htm Path: CMP/Release-Notes/Enhancements/2024/MR202404/CMP-Enhancements Apr-2024.htm

Enhancements

This section describes general enhancements that were made in the PrismHR April 2024 monthly release.

Added County to the 601 record for WV unemployment

In MasterTax V46 and above (for both SBEA and non-SBEA clients), the 601 record for West Virginia (tax code 49-24) now includes the county worked in for the employee in positions 400-414. For example positions 400-414 will report Kanawha if majority of the employee’s job duties were performed in the Kanawha County.

The system will use the county name of the home location in the state of West Virginia.

In the event the employee’s home location has been changed when the RTS is run and is no longer in WV, the system will blank fill the record. For example, an employee’s home location was WV and the employee had WV SUTA to report. When the RTS is run, home location is now any state other than WV. The system will blank fill the record and will not report the county of the other state.

JIRA # CMP-5587

Position-based Union Fringe Benefits Enhancement

When employees work between multiple local areas with different unions and between multiple jobs such as electrical, structural, etc. you now have more flexibility to leverage the Position based union override to manage fringe benefits. When the Labor Union is not applied to the Employee Detail record and the Labor Union is applied to the Position Code:

JIRA # CMP-5432

Added SOC codes/Job Title to the RTS for WA and WV

In the Positions form, if:

For more information on SOC code reporting for multiple states, please refer to to the article titled Updating SOC Codes on the Customer Resource Center.

JIRA # CMP-5526

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202407/CMP-Enhancements%20Jul-2024.htm Path: CMP/Release-Notes/Enhancements/2024/MR202407/CMP-Enhancements Jul-2024.htm

Enhancements

This section describes general enhancements that were made in the PrismHR July 2024 monthly release.

Updates to WH347 Report

The WH-347 form generated by PrismHR has been updated to the latest version with an expiration date of 9/30/2026.

JIRA # CMP-5659

Changes to Employer Quarterly SUTA Tax Export - South Carolina

The state of South Carolina now requires the Standard Occupational Classification (SOC) Code and Hours Worked on this report. The system has been enhanced to incorporate this for both versions of the available reports.

JIRA # CMP-5475

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202410/CMP-Enhancements%20Oct-2024%20MR.htm Path: CMP/Release-Notes/Enhancements/2024/MR202410/CMP-Enhancements Oct-2024 MR.htm

Enhancements

This section describes general enhancements that were made in the PrismHR October 2024 monthly release.

Addition to PrismHR Work Centers

Under the PrismHR Work Centers, under the Tax section, a new group named PrismHR Tax Processing is added. This is a central location to access the PrismHR tax setup and reporting forms.

WARNING: This work center is currently released as BETA with further functionality to be released in 2025. The parameters and reports should only be used by customers who are engaged in the BETA testing of the JSON exports. Existing customers should continue to use the CSV report downloads at this time.

[Image: screenshot]

The following two sections are available under PrismHR Tax Processing work center:

JIRA # CMP-5981

PrismHR Tax Client Setup Export

Use this form to build the PrismHR Client Setup JSON export file. This will create an initial JSON export for setting up an initial group of client data in PrismHR Tax.

Note: Note: Client Access Group security is not enabled on this form.

WARNING: This form is currently released as BETA with further functionality to be released in 2025. This form should only be used by customers who are engaged in the BETA testing of the JSON exports. Existing customers should continue to use the CSV report downloads at this time.

To access this form, on the Work Centers under Tax, click PrismHR Tax Processing. Under Setup, click PrismHR Tax Client Setup Export.

To set up an initial group of client data in PrismHR Tax:

  1. Complete the following fields:

Field Name — Description

Tax Date Start — Enter the starting tax date of the group of clients to be included in the client setup files.

Tax Date End — Enter the ending tax date of the group of clients to be included in the client setup files. > Note: Note: We suggest using a period that does not exceed a single quarter for each setup export.

  1. Click Build to build the PrismHR Client Setup JSON export file for the selected tax year and the tax quarter.

  2. Click Cancel to clear this form at any time.

JIRA # CMP-6025

PrismHR Tax Parameters

Use this form to set up parameters to be used for various needs in the PrismHR Tax files. This form is currently informational only with future development planned for future quarters.

Note: Note: Client Access Group security is not enabled on this form.

WARNING: This form is currently released as BETA with further functionality to be released in 2025. This form should only be used by customers who are engaged in the BETA testing of the JSON exports. Existing customers should continue to use the CSV report downloads at this time.

To access this form, on the Work Centers under Tax, click PrismHR Tax Processing. Under Setup, click PrismHR Tax Parameters.

To set up PrismHR Tax Parameters:

  1. Complete the following fields:
Field Name Description
PrismHR Tax Interface Active
PrismHR Periodic File Version Select one of the following options: - Version 01 - This is the only options available at this time.
  1. Click Save to save the parameters set on this form.

JIRA # CMP-5981

Quarterly Tax JSON Export

The quarterly tax JSON export will be supported in a future release. More information will be available in a future release.

Note: Note: Client Access Group security is not enabled on this form.

WARNING: This form is currently released as BETA with further functionality to be released in 2025. This form should only be used by customers who are engaged in the BETA testing of the JSON exports. Existing customers should continue to use the CSV report downloads at this time.

To access this form, on the Work Centers under Tax, click PrismHR Tax Processing. Under File Exports, click Quarterly Tax JSON Export.

To build the quarterly tax JSON export file:

  1. Complete the following fields:
Field Name Description
Tax Year Select the appropriate tax year from the dropdown. The default is the current year with a 10 year look back.
Tax Quarter Select the appropriate tax quarter for which you want to build export from the following options: - 1 - This is the default option. - 2 - 3 - 4

  1. Click Build to build the quarterly tax JSON export file for the selected tax year and the tax quarter.

  2. Click Clear to clear this form at any time.

JIRA # CMP-6000

Changes to the MasterTax Interface Parameters form

MasterTax RTS is updated to Version 47 in PrismHR

[Image: screenshot]

MasterTax PTS is updated to Version 29 in PrismHR

[Image: screenshot]

JIRA # CMP-5955, CMP-6016

Changes to Print Employee 1099 Forms form

On the Print Employee 1099 Forms form, the Form Type named NEC: 2-up Smplx NEC has been removed from the dropdown as it is not a valid Form Type and was generating an error message. The following valid Form Types are now available on this form:

JIRA # CMP-5573

Changes to Employer Quarterly SUTA Tax Export file format for West Virginia

West Virginia has added the Employee Job Title, SOC Code, and County of Employment as required fields on the S record of their SUTA file upload. PrismHR will support this change. The S record had been updated to include the following:

JIRA # CMP-5513

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202410/Other%20Enhancements%20CMP202410.htm Path: CMP/Release-Notes/Enhancements/2024/MR202410/Other Enhancements CMP202410.htm

Other Enhancements

This section describes some other enhancements that were made in the PrismHR October 2024 monthly release.

New Native American Tribes added to Form I-9 ID Authority lookup

On the Employee Details form, under the Work tab, under the Employment Verification section, for the Form I-9 ID Document field, once you select B - Native American tribal document and then click the Form I-9 ID Authority hyperlink, a lookup shows the list Native American tribes. The following Native American tribes and an additional option named “Other” have been added to the Form I-9 ID Authority lookup.

[Image: screenshot]

JIRA # WSP-781

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202412/CMP-Enhancements%20Dec-2024.htm Path: CMP/Release-Notes/Enhancements/2024/MR202412/CMP-Enhancements Dec-2024.htm

Enhancements

This section describes general enhancements that were made in the PrismHR December 2024 monthly release.

Changes to the Quarterly Tax JSON Export (BETA) form

Reporting Filters

A new Report Filters section has been added to this form.

Reporting Filters

Limit to Client ID — If you want to limit this export for a particular client, enter the Client ID here. Leave this field blank to build the export file for all clients.

Limit to Employer ID — If you want to limit this export for certain employers, enter their Employer IDs here. Leave this field blank to build the export file for all employers.

[Image: screenshot]

PSD Codes added

PSD codes have been applied to the quarterly tax JSON export to ensure the data matches the daily tax JSON export.

JIRA # CMP-6213, CMP-6105

PSD codes added to Daily Tax JSON export

As a PTM user, to accurately report PA local taxes, the Daily Tax JSON export file from now on will have the work and resident PSD codes in the Employee Wage Detail node.

JIRA # CMP-6112

Changes to the PrismHR Tax Parameters (BETA) form

JIRA # CMP-6065

Changes to the Tax Deductions form

On the Tax Deductions form, the field named Suppress Reporting to Mastertax has been renamed to Suppress Reporting toPrismHRTax & Mastertax. Thus, you can set this up both for PrismHR Tax and MasterTax in one go from this form.

[Image: screenshot]

JIRA # CMP-6004

Changes to the Quarterly Tax JSON Export (BETA)

The PrismHR JSON file exports remain in a BETA testing mode. Only customers who are involved in the BETA testing program should leverage these reports for reporting purposes. The BETA Quarterly Tax JSON download build process reviews the various tax registers and generates a file in a JSON format for PrismHR Tax processing. Run this process quarterly and use it to reconcile the wage and tax amounts that were reported through the Periodic JSON Tax report for the previous quarter. This format currently only supports the non-SBEA required output. The SBEA format will be released in 2025. State specific information has been added to the JSON quarterly download. If data point is missing that state specific field is not populated for example, if LASUI is missing, then that position will not be populated.

JIRA # CMP-5846, CMP-6022

Changes to the FLSA Exempt Compensation Report

The FLSA Exempt Compensation Report now has an additional column named FLSA Exemption Category.

[Image: screenshot]

If an employee’s Position is marked as FLSA Exempt on the Employee Details form and has an associated FLSA Exemption Category indicated therein, it will now reflect in this report.

JIRA # CMP-5984

ACA Efile update to Transmission file for 2024

When you create the ACA transmission file for 2024 using the ACA Transmission File form in PrismHR, the SoftwareId on the manifest file will be 24A0019620.

JIRA # CMP-5970

VT CCC EE contribution added to MasterTax RTS

For both SBEA and non-SBEA clients, the employee contribution amount towards Vermont Child Care Contribution Tax (tax code 46-27) is now included in the 616 record of MasterTax v47 RTS file in positions 93-106.

JIRA # CMP-6003

Create Employee W-2C Forms

The Create Employee W-2 Forms form will not have the W-2c radio button anymore. You will use this form to only create Form W-2s for employees.

A new form named Create Employee W-2C Forms has been introduced. Use this form to create the electronic W-2c form data that needs to be uploaded to federal, state, and local government agencies.

JIRA # CMP-6082

W2 Form Year 2024 now available in PrismHR

On the W-2 Form Layout form, the W2 Form Year field now has the year 2024 available for you to configure and print Form W-2s in house for your employees.

JIRA # CMP-5877

1099 Form Year 2024 now available in PrismHR

On the 1099 Form Layout form, the 1099 Form Year field now has the year 2024 available for you to configure and print Form 1099s in house for your employees.

JIRA # CMP-5876

EFW2 Reports support multivalued Common Pay Agent data

The EFW2 download for Social Security Administration in PrismHR has been modified to include the multivalued Common Pay Agent data as per the Report Option field under the Common Pay Agent for Form W-2 Processing section on the Employer Details form so that the Employer reported EFW2 download for SSA now follows the new common pay agent options namely Agent|Employer or Agent Only, and the year.

JIRA # CMP-5871

Disable 60-63 catch up by client retirement plan

When Accelerated Catchup is disabled, retirement calculations ignore the 60-63 Catch Up amount and the pretax amount is based on the normal Catch Up Limit.

[Image: screenshot]

JIRA # CMP-5909

Automatic Tax Suppression for WA Cares Opt Out

Previously, if an employee was exempt from Washington Cares Tax (tax code 48-53) for an employee, you had to:

Now, if you select Opt Out for Washington Cares Tax under the Special Tax Rules section under the Tax tab on the Employee Details form, on the MasterTax RTS, the Washington Cares Tax (tax code 48-53) for the employee will automatically be suppressed. You do not need to use the Suppress Taxes form using the

[Image: screenshot]

menu from the Tax Calculation Overrides form for the employee.

JIRA # CMP-5999

New Tax Codes added

To support Paid Family and Medical Leave for the states of Delaware and Maine, the following new tax codes have been added to PrismHR.

You can use these tax codes for tax adjustments and will flow to the MasterTax RTS and PTS as well as the Daily and Quarterly Tax Exports.

Note: Note: ME and DE PFML tax will calculate for pay dates beginning January 1, 2025.

JIRA # CMP-5915, CMP-5920, CMP-6132

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/MR202412/CMP-Other%20Enhancements%20Dec-2024.htm Path: CMP/Release-Notes/Enhancements/2024/MR202412/CMP-Other Enhancements Dec-2024.htm

Other Enhancements

This section describes other enhancements that were made in the PrismHR December 2024 monthly release.

Changes to the 1095C Report Download form

Previously using this form, you could generate Form 1095-C PDFs for a limited number of employees in one download for a client. Now you can generate Form 1095-C PDFs for a maximum of 50,000 employees for a client. Once the job is completed, you will receive an email stating 1095C Download for by initialized at . Once the 1095-C is generated, you will need to retrieve it using the Operations / Action / Transfer Downloads File to PC form.

In January MR, the process will create an immediate download from the main form.

Note: Note: Depending on the number of employee records being processed, this can take a while. However, you can continue with your work while this process works in the background. For example, if you are processing records for about 40,000 employees, it can take about two hours.

JIRA # WSP-1211

Changes to the Employee Details form

On the Employee Details form, under the Tax tab, under Federal Tax Filing section, a new field named Form W8 Filed has been added.

[Image: screenshot]

This field is unchecked by default. Check this box if the employee has submitted Form W-8 BEN or Form W-8 BEN-E. This setting is applied to tax reports. Tax suppression is managed using individual tax suppression or by using the Tax Exemption field on the Employee Types form.

JIRA # CMP-1038

MasterTax PTS now supports Form W-8-BEN reporting

For both SBEA and non-SBEA clients, MasterTax PTS Version 29 and later has been updated to separately report on Form W-8-BEN tax withholding.

210 record - Any employee who has filed Form W-8-BEN in PrismHR will have a separate associated record for federal or state income tax such as 00-10W8, 2XX-20W8.

500 record - The Form W-8 employees and Form W-2 employees will be split between tax codes 00-10W8 (federal income tax) and XX-20W8 (state income tax).

JIRA # WSP-1037

MasterTax RTS now supports Form W-8-BEN reporting

For both SBEA and non-SBEA and client reporting taxes, MasterTax RTS Version 47 and later now splits out the Form W-8 income tax withholdings under 00-10W8 (federal income tax) and XX-20W8 (state income tax) on the 500 and 600 records.

JIRA # WSP-1039

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/QR202403/CMP-Enhancements%20Mar-2024%20QR.htm Path: CMP/Release-Notes/Enhancements/2024/QR202403/CMP-Enhancements Mar-2024 QR.htm

Enhancements

This section describes general enhancements that were made in the PrismHR March 2024 quarterly release.

Updated CA Pay Data Reporting to Support TY 2023 Reporting Period

On February 1, 2024, California released the FAQs for Tax Year 2023 Pay Data Reporting. New this year is the requirement to report whether an employee is a remote employee. You must also report whether they are remote within CA or outside of CA. To support this requirement, PrismHR released an updated reporting template for tax year 2023 that now includes the additional reporting fields: Employees that do not work remotely, Remote employees located within California, Remote employees located outside of California. Additionally, the EEO Export has been modified to include a new data record Remote Employee.

To determine a Remote Employee, the new logic is based on the most prevalent configuration and assumes:

  1. All remote employees are assigned to home worksite locations that are distinctly for remote employees only.

  2. Employees are assigned to remote worksite locations with an address matching their states of residence.

  3. These remote worksite locations are configured with an EEO Override Location, as all remote employees should be reported under the physical establishment to which they report.

  4. No physical establishments contain an EEO Override Location.

The table below depicts if and how employees will be reported on PrismHR California Pay Data files based on the state(s) of their home worksite locations and the associated EEO Override Location.

[Image: screenshot]

For more information, please refer to the article named 2024 California Pay Data Updates on the Customer Resource Center.

JIRA # CMP-5474, 5473, 5438,5437

Updated 1099 data in the RTS file for 00-10NEC and any XX-20NEC

With the enhancement to withhold Income tax on 1099 contractors, the Mastertax RTS required modifications to remove this withholding from the reporting. Starting in Q1 2024, we will break this data out in the RTS.

JIRA # CMP-5280

SOC code added for all states in the Quarterly Tax Export

The Quarterly Tax Export in PrismHR has been updated to include the Standard Occupational Classification (SOC) code for all states in column 32 whenever applicable. The SOC code can be found on the Positions form in PrismHR.

Note: Alaska continues to require a specific Alaska Job Code configured separately on the Positions form in PrismHR.

JIRA # CMP-5385

Changes to EFW2C download report

From now on, the EFW2C download report generated by PrismHR will only include those employees who have an existing Form W-2c in the system. You will not see any employee reported in the file who does not have an actual Form W-2c to report.

Original Data

Corrected Data

We will continue to refine the file output based on SSA Specifications in the Q2 Quarterly Release.

JIRA # CMP-5218, 5464 & 5217

Updated Client Details form

The Misc Tax ID and the Misc Tax Code fields under the State Tax Setup section in the Client Details form have been updated in PrismHR.

JIRA # CMP-5327, 5028

System Parameters form is updated

On the System Parameter form, a new field named Tax Adjustment Date Validation has been added. This field is a dropdown having the following three options:

The last two options noted above are added to allow your group to restrict future dated tax adjustments.

Be sure to check out the January and February Compliance Maintenance Release Notes to remain up to date with several other important tax and reporting changes effective in 2024.

JIRA # CMP-5480

MasterTax RTS is updated to Version 46

MasterTax RTS is updated to V46 in PrismHR.

[Image: screenshot]

[Image: screenshot]

Regardless of whether E, C, CL or CR reporting, for both SBEA and non-SBEA clients, the MasterTax v46 produces the following changes which the prior MasterTax versions do not:

JIRA # CMP-5370, 5371

Prevailing Wage Calculation Logic Enhancement

When processing certified payrolls and using the option “Use Higher of Prevailing Wage Rate or Employee’s Pay Rate” , the pay rate for the position is determined based on the higher of the employees standard hourly rate or the prevailing wage of the position on the project. In some instances, the calculated overtime rate for the prevailing wage is less than the calculated overtime rate for the employee’s standard hourly rate. A new Custom Feature Code has been created (OTPREVAILINGWAGE) to compare the calculated prevailing wage overtime rate with the standard hourly overtime rate. When the standard overtime rate is greater, the pay rate will equal their regular overtime rate. If the regular prevailing wage rate is higher, this will still be used and only the overtime rate would follow the employees standard hourly rate.

JIRA # CMP-5087

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/QR202406/CMP-Enhancements%20Jun-2024.htm Path: CMP/Release-Notes/Enhancements/2024/QR202406/CMP-Enhancements Jun-2024.htm

Enhancements

This section describes general enhancements that were made in the PrismHR June 2024 quarterly release.

Changes to the Labor Unions form

The Labor Unions form has been enhanced to allow assignment of union dues table rules to a unique union deduction code. When using Position Union overrides, you can now apply multiple union deduction codes to an employee based on the timesheet sensitive position code entered and allocate deductions amounts appropriately. When using position based Union code overrides, you can now differentiate between the union deductions without requiring the union applied to the employee directly.

An additional column named Union Dues Table Rules has been added to the union deduction code table.

[Image: screenshot]

For a Union Deduction Code that does not have Union Dues Table set as the Calculation Method for that union deduction code on the Deduction Codes form, you will see the

[Image: screenshot]

icon. If you click the

[Image: screenshot]

icon, you will get an error message stating The deduction code has an invalid calculation method. The code must have a calculation method of Union Dues Table to be assigned union dues table rules.

For a Union Deduction Code that has Union Dues Table set as the Calculation Method for that union deduction code on the Deduction Codes form, you will see the

[Image: screenshot]

icon. When you click it, a new form named Included Union Dues Table Rules will open. This form allows you to associate specific Union Dues Table Rules with a specific Union Deduction Code.

[Image: screenshot]

OR

Using the Included Union Dues Table Rules form, if you remove the rule assigned to the Union Deduction Code, you can remove the rule from the Union Dues Table.

With the enhanced Labor Unions form, you can now have unique union deduction codes with the calculation of union dues table to differentiate between various union deductions allowing unique deductions for better visibility to clients and employees. This enhancement will allow for better reporting will continue to be enhanced in our September Quarterly Release. Watch out for more on this in our future releases.

JIRA # CMP-5493, 5562, 5578, 5605

Recalculate Alabama Income Tax Exempt Wages

Use this new form to recalculate the overtime payroll hours and wages that are exempt from income tax for employees in the state of Alabama for a client.

You must enable the system level custom feature code OVERTIME.EXCEPTION.PAY and disable the client level custom feature code DISABLE.OVERTIME.EXCEPTION.PAY for this form to work correctly for the client, else you will get an error message stating Overtime Exemption Pay is not enabled or is disabled for this client.

Click OK to acknowledge the message.

PrismHR Path Payroll>Payroll\ Action>Recalculate Alabama Income Tax Exempt Wages

Security

Note: Note: This process will not modify any existing payroll voucher data including exempt earnings, taxable earnings, and tax withheld for AL Income Tax 01-20. This recalculation will provide a report of the recalculation results. The recalculated values will be applied to MasterTax reporting, W-2 reporting, and Report Center reporting of actual exempt hours and wages for AL Overtime Income tax exemption. Tax adjustments will be required if the recalculated values do not align with the payroll data when it was processed.

JIRA # PORT-5449, 5630

EFW2C Download Enhancements - Corrected Wages & W2 Box Values in EFW2C file

If there is an employee W2c record where the wages or the W-2 box values have been corrected, the EFW2C file output has been refined to meet specifications for the Social Security Administration.

Note:

JIRA # CMP-5230

Correcting Employee SSN & Name in EFW2C file

If the W-2 and W2c data are the same, but there has been an SSN change that is necessary to report to the SSA, the file will now only populate the original and corrected value for the SSN change. Money fields are blank filled.

If the W-2 and W2c data are the same, but there has been a Name change that is necessary to report to the SSA, the file will now only report the original and corrected values for the name change. Money fields are blank filled. The employee SSN if same as the original W-2 is populated in positions 13-21.

Following are a few frequently asked questions that you might find helpful.

If the Employee’s Originally Reported SSN is entered in the RCW (Employee) Record (positions 4-12), then the Employee’s Correct SSN (positions 13-21) must also be entered.

If the Originally Reported SSN and Name is entered in the RCW Record, the Correct SSN and Name must also be entered.

For an SSN/Name correction, only one RCW (Employee) correction report is needed.

Complete the RCW (Employee) Record original “Social Security Number”, original “Employee First Name”, original “Employee Middle Name or Initial” and original “Employee Last Name” fields for all SSN/Name corrections.

Enter the name exactly as shown on the individual’s Social Security card. If you are correcting the employee’s name, the employee’s originally reported first name, middle name or initial and last name fields must be completed as originally submitted.

JIRA # CMP-5219

PTM Identifier Number added to Employer Details form

To support PTM customers who are using both the full service option and the self-service option, a new field name PTM Identifier Number has been added under the Employer Details section of the Employer Details form to provide the ability to record two different PTM Identifiers.

[Image: screenshot]

JIRA # CMP-5399, 5479

Form I-9 remote verification enabled at the client level

A new field named Enable I9 Remote Verification is now available under the Process Controls section under the Control tab on the Client Details form.

[Image: screenshot]

If you want to disable Form I-9 remote verification for any particular worksite, you can do so using the Enable Remote Verification for this Location field under the Other Parameters section on the Worksite Locations form for that worksite.

[Image: screenshot]

This option will allow I-9 Approvers to remotely examine supporting documents for a new hire’s Form I-9 using an alternative procedure authorized by the Department of Homeland Security (DHS). Now you can select one of the following options:

JIRA # CMP-5364

Support for 1099 contractor reporting

To support 1099 contractor Federal and State Income Tax reporting, when the Custom Feature Code 1099WITHHOLDING is enabled, the wages and tax withholdings for a 1099 contractor will NOT be included in the Employer 941 Quarterly Report for any 1099 contractor with tax withholding. Additionally, release enhancements for the PTS and RTS to support 1099 withholding will only be present in the files using the NEC tax code when the Custom Feature Code 1099WITHHOLDING is enabled.

Note: Note: When leveraging the Custom Feature Code 1099WITHHOLDING, you will need to have a separate Employee ID for any 1099 contractor who has tax withheld. Previously, the system allowed a 1099 Contractor in one client and a W-2 employee in a second client using the same Employee ID. For purposes of 1099 income tax withholding and reporting, the 1099 contractor must NOT be a W-2 employee in any other client.

JIRA # CMP-4886, 5676

Changes to calculation of Boone County, KY, Mental Health tax

Boone County KY Mental Health tax historically calculated on the locality level which affected the maximum county based tax when employees work between various localities in Boone County. As a resolution, a Custom Feature Code BCKYMHCAP has been created which will transfer the local tax to the county level tax deduction code 180150000-34. When calculated on the county level, the maximum tax amount will be honored regardless of where the employee worked in Boone County, KY. If enabling this custom feature mid-year, the Boone County Mental Health tax register will restart. User Action will be required to move taxable wages out of the locality tax deduction code to the county level tax code to ensure employees who have already met the maximum tax do not have tax withheld with the addition of the CFC.

JIRA # CMP-5584, 5668

Support for Vermont Childcare Employee Tax Rate

As an employer in the state of Vermont, effective 7/1/24 you are required to pay a 0.44% tax on wages paid to an employee in the state of Vermont. You can pay the full 0.44% or you may choose to deduct and withhold a maximum of 25 percent of the required contribution (0.11% of wages paid) from the employee.

To support this Vermont Childcare rate shifting, a new field named State Misc 2 Employee Rate has been added to the following forms. This field is only to be used for Vermont Childcare Employee Tax Rate bearing tax code 48-27.

[Image: screenshot]

[Image: screenshot]

Note: Note: The functionality for supporting the employee tax rate override may not be included in the Wave 1 release. However, it will be added to the release prior to the time-line to calculate July 1, 2024 payrolls.

JIRA # CMP-5599, 5455

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/QR202406/Other%20Enhancements%20CMP202406.htm Path: CMP/Release-Notes/Enhancements/2024/QR202406/Other Enhancements CMP202406.htm

Other Enhancements

Change to Default Value of Non-Residency Certificate

On the Employee Details form, in the Local Tax Filings panel under the Tax tab, the Local Non-Residency Certificate field no longer defaults to “Yes” when you create a new row in the grid. Instead, the field defaults to the neutral “‑‑Select‑‑” option.

Note: Note: This change only applies to newly created rows in the grid.

JIRA # WSP-209

Employer Details form now Validates FEINs

The system now validates entries in the Federal EIN and Common Pay Agent EIN fields, located on the Employer Details form.

Valid values now must be in one of two formats:

Note: Note: If an existing employer FEIN does not follow this format, you will receive an warning message the next time you open Employer Details and try modifying any data for that employer. After you fix the affected FEINs, you can save all the changes.

JIRA # WSP-179

End Dates for State Unemployment and Income Tax

The State Tax panel of the Employer Details form now includes two new fields: Rpt Entity End Date and SIT End Date. This override applies to any payroll calculations that occur before the end dates. On the day after its end date, the tax reverts back to the default State Rules setting.

[Image: Highlighting new Rpt Entity and SIT End Dates in State Tax panel of Employer Details.]

Note: Note: These new fields may be overridden by the client reporting fields on the Client Details > Tax tab: “Client Reporting Start Date” and “Client Reporting End Date”, located under State Tax Setup.

JIRA # WSP-182

Enhancements to Change SUTA Flag On Vouchers (PEO/Client)

The Change SUTA Flag on Vouchers (PEO/Client) form provides two new settings:

These settings mimic the behavior of the “Rebuild Vouchers Flag” and “Send adjusting entries to MasterTax PTS file” options located on the Change Employer IDs for a Voucher form.

You can choose to “Update Existing Vouchers” with the new SUTA flag, or “Create New Adjustment Vouchers” for this change. If you choose to create new vouchers and you need to represent these changes on the MasterTax PTS file, set Send to Mastertax to “Yes”. The PTS file will indicate the original wages/taxes with a negative value and the new, correct wages/taxes with a positive value.

JIRA # WSP-114

Review and Download Historical SUTA Recalculation Reports

The Recalculate Taxes on Vouchers form now provides an archive of previously generated previews. Click the Recalculate Taxes on Vouchers Report History link to open a modal form containing the past reports. Preview reports are only saved when the Update Tax Values option is enabled.

This form is only available to Service Provider users who have user role access to the parent form. The link does not display for users who have their form access set to Inquiry.

Note: Note: If a user’s Client Access Group restricts access to one or more clients, they cannot access this new form. Only users with total client access can view these historical reports.

JIRA # WSP-178

Start and End Dates for System-wide Tax Suppression

You can now set tax suppression date ranges on the Miscellaneous Global Parameters form (located in the Actions menu of the System Parameters form).

In the Suppress Tax Code grid, enter an optional From Date and To Date. These fields specifically denote start and end pay dates.

The system suppresses the specified tax code only during this period (inclusive of the start and end pay dates).

JIRA # WSP-180

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/QR202409/CMP-Enhancements%20Sep-2024.htm Path: CMP/Release-Notes/Enhancements/2024/QR202409/CMP-Enhancements Sep-2024.htm

Enhancements

This section describes general enhancements that were made in the PrismHR September 2024 quarterly release.

Changes to Alabama Overtime Exemption rule

Alabama updated the OT wage exemption to include Salary non-exempt employees and exclude Hourly exempt effective 10/1/2024. PrismHR will now support this change. For any pay date 10/1/24 or greater, AL OT exempt wage logic will apply to:

For more information, please visit the article named Alabama Overtime Exemption Amendments on the Customer Resource Center.

JIRA # CMP-5921, CMP-5939

Changes to the W-2 Form Layout form

For tax year 2023 and forward, the W-2 Form Layout form in PrismHR will have the following additional fields:

Note: Note: At this time this option is available for printing W2 Form Type S, LB and GHF only.

JIRA # CMP-5569, CMP-5724, CMP-5845

Changes to Common Pay Agent for Form W-2 Processing

On the Employer Details form, the layout of the Common Pay Agent for Form W-2 Processing section has been updated as follows:

[Image: screenshot]

To display Common Pay Agent information on the Form W-2 or Form W-2c PDF, even if this was used in the past, you will need to select a Report Option and Save the changes on the Employer Details form.

The grid has the following columns:

Note: Note: This field can be blank only if there is no data. If there is data in the grid, then this field needs to be filled up. If you already had data for this section earlier, now you will need to go in and update the year and save the record. The screen defaults to 2023 since before 2023 PrismHR did not report the common pay agent on the Form W-2 or Form W-2c PDFs.

Note: Note: Common Pay Agent Name Control is not applied to W2’s built by Client Federal Entity Registers for SBEA W2 Reporting.

JIRA # CMP-5660, CMP-5711

Changes to the FLSA Exempt Compensation Report form

The following highlighted fields are added to the FLSA Exempt Compensation Report form.

[Image: screenshot]

[Image: screenshot]

Note: Note: Depending on whether the employee is paid weekly, biweekly, semi-monthly or monthly, PrismHR will divide this Minimum Salary by 52 or 26 or 24 or 12 to get the Period Minimum. The Period Minimum multiplied by Pay Per Date Range (5 for a 5 day work week) will provide the Total Compensation Expected on the FLSA Exempt Compensation Report. The difference between the Total Compensation Expected and the Actual Total Compensation is the Deficiency on the FLSA Exempt Compensation Report.

JIRA # CMP-5695, CMP-5696, CMP-5699, CMP-5700

Changes to the ACA Offered Employees form

[Image: screenshot]

JIRA # CMP-5482, CMP-5650

Override State added for Creditor Wage Garnishment

There are instances when a creditor garnishment needs to follow the withholding limit requirements of the issuing state rather than the employee’s work state. PrismHR now supports this option.

On the Employee Garnishments form, when Creditor Wage Garnishment is selected from the drop-down under the Category field, then under the Limit Overrides section, a new field appears named Override State Code. This field is optional.

When an Override State Code is selected for an employee on the Employee Garnishments form for Creditor Wage Garnishment, the employee creditor wage garnishment will follow State Garnishment Rules for the selected Override State on the Employee Garnishments form and not the SUTA state. For example, if an employee is working in NY with NY SUTA and has a creditor garnishment with GA selected for the Override State Code field on the Employee Garnishments form, then creditor garnishment for that employee will be calculated based on State Garnishment Rules for GA instead of NY.

The creditor garnishment will now follow the withholding limits based on the State Garnishment Rules form for the state selected in the Override State Code above instead of the employee’s SUTA state.

JIRA # CMP-5783, CMP-5586

Employee Details Garnishments form

Previously from the Employee Details form, when you clicked Garnishments under Actions menu, the Employee Garnishments form opened. Then you had to select a Docket Number to open a docket for an employee. This form included all dockets for all applicable employees for a single client. These dockets were not specific to the employee record. There was no easy way to find all the garnishments for an employee under one form.

To solve this, a new form named Employee Details Garnishments is introduced. Once you select an employee on the Employee Details form, click Garnishments under Actions menu to open this form. If no garnishments are applied to this employee a message will appear: “No garnishments for this employee”.

Note: Note: This new form must be added to the User Roles for user. You cannot find this form using normal search means.

Security

[Image: screenshot]

Use this form to view all garnishments associated with the selected employee on the Employee Details form.

The form will show the following information in a table:

Click Close to close this form and return to the Employee Details form for the employee.

Adding the Employee Details Garnishments Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click

[Image: screenshot]

(Back Office). Select User Roles from the System|Change menu.

  1. Select or enter the Role ID.

  2. Click Add. The User Role Maintenance form displays.

  3. Select the Employee Details Garnishments form from the list. (To quickly find this item, select HR in the Type Filter

box.)

  1. Click Accept.

  2. Click Save. Log out and login for this action to take effect.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click

[Image: screenshot]

(Back Office). Select User Roles from the System|Change menu.

  1. Select Bulk Role Update from the

[Image: screenshot]

Actions menu. The Bulk Role Update form opens.

  1. Click Form and then select EMPLOYEE.GARNISHMENTSEE.SPECIFIC.GARNISHMENTS from the Search Processes list. (To quickly find this item, enter Employee Details Garnishments in the Form Description* field and click Refine, then select the form that displays.)

  2. A list of user roles displays.

  3. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  4. Click Accept. The User Roles form displays.

  5. Click Save.

JIRA # CMP-5603

Remove Global PTO CFC Requirement

Previously, all Global PTO functionality for the following forms was hidden unless the custom feature code GLOBAL.PTO was enabled. All Global PTO functionality are now available on the following forms without using the custom feature code GLOBAL.PTO.

Note: Note: The custom feature code is still required to calculate Global PTO accruals. This requirement will be removed in an upcoming release.

JIRA # CMP-5741

Change to the Global PTO Benefit Plans form

A new field named Apply Carryover toward- Maximum Accrual Per Year has been added under the Flat Amount per Hours Worked section on the Global PTO Benefit Plans form.

[Image: screenshot]

When this field is checked, accruals will stop when Carryover Hours plus the Accrued Hours reach the Maximum Amount Accrued per Year. No additional accruals will be made for the remainder of the year. For example, if the “Maximum Amount Accrued per Year” is 40 hours, and the Carryover Hours is 39 hours, the employee can only accrue 1 hour for the current year.

JIRA # CMP-5740

Special Tax Rules has a new drop-down

On the Employee Details form, under the Tax tab, under the Special Tax Rules section, for the Tax Event Code field, a new drop-down named Washington Cares Tax is added. If you select this option, the Opt In / Opt Out field defaults to Opt Out. If you select Opt In from the drop-down, you will receive an error stating ‘Opt Out’ is the only valid option for Tax Event Code - ‘Washington Cares Tax’.

You can only assign this if an employee is exempt from WA Cares Tax. With the September Quarterly release, any employee who is set to Opt Out for Washington Cares Tax, the MasterTax RTS WA0000-14 601 employee record position 100 will report Y, otherwise will report blank. This option will not suppress the tax for the employee at this time. Functionality to suppress the tax when applied to the Special Tax Rules will follow in an upcoming release.

JIRA # CMP-5277, CMP-5712

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/QR202409/Other%20Enhancements%20CMP202409.htm Path: CMP/Release-Notes/Enhancements/2024/QR202409/Other Enhancements CMP202409.htm

Other Enhancements

This section describes other enhancements that were made in the PrismHR September 2024 quarterly release.

Warning Report available under Recalculate Taxes on Vouchers Report History

On the Recalculate Taxes on Vouchers form, now when you click the Recalculate Taxes on Vouchers Report History hyperlink, it will also show if any warnings were generated on the Job Control while processing.

[Image: screenshot]

When you click the warning hyperlink shown above, the following Job Control Status Report opens which shows the details of the warnings.

[Image: screenshot]

Note: Note: On the Recalculate Taxes on Vouchers form, the Include SUTA/FUTA Successor Wages should be Yes for this to work.

JIRA # WSP-288

Bulk download ACA Form 1094-C for all Clients

Now, you do not have to print client by client the ACA Form 1094-Cs. The 1094C Report Download form has been enhanced to allow bulk printing of ACA Form 1094-Cs for all clients that you have access to. A new field named Generate All Clients has been added to the form. By selecting this option, you will only receive a PDF for the clients you have access to.

[Image: screenshot]

Once you click Run, a Job Control window opens showing the progress and the number of clients selected clients. Click Close to close the Job Control window. In case of any errors, redo the process.

A zip file containing a Form 1094-C PDF for each client that you have access to, gets downloaded to you system.

[Image: screenshot]

Click the zip file to view all the PDFs downloaded. Each PDF file is for a client that you have access to.

[Image: screenshot]

Click any PDF to view the Form 1094-C for that client. Scroll to see all the pages.

[Image: screenshot]

JIRA # WSP-308

Extra Validation Now Required for Client Tax IDs

To ensure that the correct client tax IDs are entered in the State Tax Setup panel on the Tax tab in the Client Details form, you must now re-enter the ID for the following fields when you enable the new REKEY.TAXID global custom feature code on the System Parameters form:

After you enter an ID for those fields the following prompt displays:

[Image: screenshot]

Re-enter the ID and click Continue.

Note: If the values do not match, an error message displays prompting you to re-enter the ID again.

JIRA # WSP-325

Clone Employer Detail form

A new form has been introduced named Clone Employer Detail. Use this form to copy an existing Employer Detail record to a new Employer Detail Record. Using this form, you can avoid setting up all the state information for a new employer. You can just clone it from an existing employer.

Note: Note: Client Access Group security is not enabled on this form.

To access this form, click

[Image: screenshot]

(Back Office). Under Employer|Action, click Clone Employer Detail.

[Image: screenshot]

To clone an existing employer record to a new employer:

  1. Complete the following fields:

Field Name — Description

From Employer ID — Enter the existing Employer ID from whom you want to clone the employer record, or click the From Employer ID hyperlink and select it from the Select Employer dialog box. If you enter an employer ID that does not exist, you will receive an error stating Record is not on file EMPLOYER.MASTER.

New Employer ID — Enter the Employer ID of the new employer. If you enter an employer ID that already exists, you will receive an error stating Employer ID already exists.

New Employer Name — Enter the name of the new employer

  1. Click Clone to copy the existing employer details to the new employer. All information on the original employer record will clone to the new employer except Initialization History. This is because you would not want to clone the initialization history of an existing employer from prior years for a new employer.

  2. Click Clear to clear this form at any time.

The following information of the existing employer will be copied to the new employer:

JIRA # WSP-348, WSP-780

Audit available for Edit 1094 Form

Now Audit is available under the

[Image: screenshot]

menu for the Edit 1094 Form.

If any change is made to the Edit 1094 Form, or if you manually update data in Part 1,2,3,4 or if you select the Update Form Counts and ALE Info button on the top of the form, the changes will now reflect within the audit.

Note: Note: If you select the Update Form Counts and ALE Info button, it would only reflect in the audit if a change actually occurs on the form and you select Save.

[Image: screenshot]

JIRA # WSP-351

Employer Details template available in the Data Import Tool

A new template named Employer Details is now available in the Import Template drop-down on the Data Import Tool form. Use this template to bulk update the account numbers and other information on the State Tax section on the Employer Details form.

[Image: screenshot]

You can also directly access this import template using the

[Image: screenshot]

Import icon on the Employer Details form.

When you select the Employer Details template on the Data Import Tool form, the required file layout displays in the form. Before you can upload and import data, your file must be saved in either comma-separated values (.csv) tabular format or text tab delimited (.txt) format with no spaces or special characters in the file name.

Note: Note: You can click Download Sample Header File to download a sample Excel data file in .csv format, which can be saved in either .csv or .txt format before importing it.

The layout requirements are as follows::

Field Description
Column Number The corresponding column number for the imported data.
Category Description - Employer (Required) - Must be a valid Employer that is currently in the system. If you try to import an employer who is not in the system, you will receive and error stating Record is not on file. - State Code (Required) - Must be a valid state code. If you try to import a state code that is not in the system, you will receive and error stating Record is not on file on STATE.CODES. - Licensed - Any one of the following options only: - Yes - No - Blank - Taxpayer ID / UI Account - Only Alpha-Numeric characters are allowed for this field. If you try to import non-Alpha-Numeric characters for this field, you will receive and error stating Only Alpha-Numeric characters allowed.. - State Tax Nbr - Only Alpha-Numeric characters are allowed for this field. If you try to import non-Alpha-Numeric characters for this field, you will receive and error stating Only Alpha-Numeric characters allowed.. - Mag Authority ID - Only Alpha-Numeric characters are allowed for this field. If you try to import non-Alpha-Numeric characters for this field, you will receive and error stating Only Alpha-Numeric characters allowed.. - Misc ID 1 - Only Alpha-Numeric characters are allowed for this field. If you try to import non-Alpha-Numeric characters for this field, you will receive and error stating Only Alpha-Numeric characters allowed.. - Misc ID 2 - Only Alpha-Numeric characters are allowed for this field. If you try to import non-Alpha-Numeric characters for this field, you will receive and error stating Only Alpha-Numeric characters allowed.. - SUTA Rpt Entity - Any one of the following options only: - C - Company - P - PEO - Blank - Rpt Entity Eff. Date - Must be a valid date. - Rpt Entity End Date - Must be a valid date after the Rpt Entity Eff. Date. If not you will receive an error message stating End date must be after the effective start date. - SIT Rpt Entity - Any one of the following options only: - C - Client - E - Employer - Blank - SIT Eff. Date - Must be a valid date. - SIT End Date - Must be a valid date after the SIT Eff. Date. If not you will receive an error message stating End date must be after the effective start date. - GL Segment EEHL - Only Alpha-Numeric characters are allowed for this field. If you try to import non-Alpha-Numeric characters for this field, you will receive and error stating Only Alpha-Numeric characters allowed..

[Image: screenshot]

Note: Note the following when using the Employer Details import template:

JIRA # WSP-387

Validating School District ID and Tax Code on Tax Adjustments form

Previously, you could enter more than one line for school taxes on the Tax Adjustments form. When this information was posted to the registers, the system only included the first line item because the posting program did not expect any tax code duplications.

The system now validates that you cannot enter more than one line for a school tax in the same state, which prevents entering duplicate tax codes.

JIRA # WSP-448

New Fields in Print Service Check Maintenance Form

To allow more flexibility in check printing, two new fields, Default Payee Font and Void After _ Days Placement, now reside on the Print Service Check Maintenance form. For example:

[Image: screenshot]

You can use these new fields as follows:

Note: This enhancement only applies to the following Default Report Form types:

Note: Note: Increased font size will affect window size adjustments.

JIRA # WSP-464, WSP-465

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/QR202411/CMP-Enhancements%20Nov-2024.htm Path: CMP/Release-Notes/Enhancements/2024/QR202411/CMP-Enhancements Nov-2024.htm

Enhancements

This section describes general enhancements that were made in the PrismHR November 2024 quarterly release.

Changes to the MasterTax RTS & PTS

For both SBEA and non-SBEA clients, the MasterTax v47 RTS will include Work Out of State Flag which is either Y or N in position 15 for the 500, 501, 601, and 616 records for Pennsylvania resident tax codes not including Philadelphia. This does not apply to Philadelphia residents and this position will remain blank for Philadelphia locality taxes.

For both SBEA and non-SBEA clients, the MasterTax v29 PTS will include Work Out of State Flag which is either Y or N in position 15 for the 210 and 500 records for Pennsylvania resident tax codes not including Philadelphia. This does not apply to Philadelphia residents and this position will remain blank for Philadelphia locality taxes.

JIRA # CMP-6016, CMP-6018

Changes to the State Rules form

When processing Global PTO for states that have different state and local requirements for PTO, you now have the ability to limit enrollment and accrual to the local plan when an employee is working in a specific locality. On the State Rules form, under the Global PTO section a new field named Apply Local PTO Plan Only when applicable is added.

[Image: screenshot]

Note: Note: The client must be enabled for Global PTO.

When this field is:

Note: Note: If an employee is enrolled in a local plan with no state plan, and then moves to a location which is without a local plan but is subject to the state plan, then PTO will accrue according to the state plan from the time the employee has moved. Prior payroll vouchers for the employee will remain unaffected on account of this change.

JIRA # CMP-4983

Changes to the EES Puerto Rico W-2 Export

From now on, EES Puerto Rico W-2 Export generated by PrismHR will end at position 1600 with a total of 13 zero filled positions (position 1587 to 1600) at the end of the file as required.

JIRA # CMP-5424

Alabama exempt overtime wages added to Form W-2

Alabama Department of Revenue proposes that exempt overtime wages be reported in Box 14 of employees Form W-2 using “EX OT WAGES” as the indicator, for example, EX OT WAGES- $15,250. PrismHR now supports this.

From tax year 2024, EX OT WAGES with the dollar amount will be reported in Box 14 on the employee the Form W-2. If a recalculation was applied this amount may differ from the voucher amounts.

JIRA # CMP-5631

Form Type GHF name changed

On the Print W-2 Forms form, the Form Type “GHF - LB Custom Legal Size, Simple, Four” is updated to “GHF - Legal Size, Simplex, Four-Up, Self-Mailed w/ EE ID and Address Panel on Bottom”. The form output remains the same.

JIRA # CMP-5571

VT Childcare (EE tax withheld) added to W2 Build

From tax year 2024, for both SBEA and Non-SBEA clients, the YTD employee portion of the Vermont Child Care Contribution (tax code 46-27) will be added to Box 14 on the Form W-2 and Form W-2c generated by the system. This will report as VT CCC with the dollar amount. This information will reflect on the following forms:

JIRA # CMP-5454

Form 1099 generated by PrismHR- updated

From tax year 2024, for an employee who is a 1099 contractor and has federal or state income tax withheld by the employer, the employee 1099 Build process in PrismHR will include the following information apart from Non-Employee Compensation:

JIRA # CMP-4890

Layout changes to EFW2 File for tax year 2024

For the tax year 2024 there are record layout changes. RO (Employee Optional) Record & RU (Total Optional) Record were updated to add BOX 12 code II Income from Exclusion of Medicaid Waiver Payments. PrismHR has updated the EFW2 format to support this change. From tax year 2024, the EFW2 output file will have record RO positions 144 - 154 and RU positions 190 - 204 zero-filled.

JIRA # CMP-5897

Employee Child Care Contribution amount added to the VT EFW2 File

Effective 7/1/24, an employer in the state of Vermont is required to pay a 0.44% tax on subject wages paid to an employee in the state of Vermont and is allowed to deduct up to 0.11% from the employee’s pay. For more information on this, please refer to the knowledge article named Vermont Child Care Contribution Tax on the Customer Resource Center.

Beginning in Tax Year 2024, the Vermont EFW2 RS record positions 338 - 348 will contain the Vermont Employee Child Care Contribution amounts to tax code 46-27 (Employee Withholding) and will remain blank if there is no employee withholding.

JIRA # CMP-5835

Secure 2.0 Increased Catch Up Contributions

As a result of the Secure 2.0 Act of 2022, effective 1/1/2025, for employees who will turn 60, 61, 62 or 63 as of 12/31 of the defined tax year, are permitted to contribute an additional amount to their catch-up contribution. To support this change, the increased contribution amount should be entered in the 60-63 Catch Up field on the following forms for the employee contribution to be treated as a pre-tax amount:

• In the December Maintenance release, additional functionality will be available to suppress this amount on the client level retirement plan.

JIRA # CMP-5834

Changes to Oregon Creditor Garnishment calculation

From 1/1/2025 up to 06/30/2027, Oregon Creditor Garnishment calculations have been programmed by effective date to use the following exempt amounts as defined by Oregon State Law based on the pay period for each of the effective dates. These amounts will be applied when the Minimum Wage Rate Multiplier field for the state of Oregon is set to 30.

Pay Period Weekly Bi-Weekly Semi-Monthly Monthly
01-Jan-2025 thru 30-Jun-2025 $305 $611 $655 $1309
01-Jul-2025 thru 30-Jun-2026 $338 $675 $737 $1458
01-Jul-2026 thru 30-Jun-2027 $400 $832 $912 $1792

On July 1, 2027, calculations will default to State Garnishment Rules for the state of Oregon:

Note: Note: It is recommended that for the state of Oregon, on the State Garnishment Rules form, the Minimum Wage Rate Multiplier field be set to 30 until July 2027.

JIRA # CMP-5937

========================================================================

Change to the Register Rebuilds form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2024/QR202411/Other%20Enhancements%20CMP202411.htm Path: CMP/Release-Notes/Enhancements/2024/QR202411/Other Enhancements CMP202411.htm

Change to the Register Rebuilds form

You now have the option to rebuild the 941 Tax Registers for all or select employers.

[Image: screenshot]

The following new fields have been added:

JIRA # WSP-345

Change to the Employee Types form

A new field named Tax Exemption has been added to the Employee Types form.

[Image: screenshot]

This field is optional. You can enable a specified form of income tax suppression for the selected Employee Type instead of setting income tax suppression at an employee level. You can select one of the following options:

Note: Note: This Tax Exemption field has field level security. It is set to DENY by default. You can add this field to a user role and set it to Enable, Disable or Hidden.

JIRA # WSP-585, WSP-823

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/MR202501/CMP-Enhancements%20Jan-2025.htm Path: CMP/Release-Notes/Enhancements/2025/MR202501/CMP-Enhancements Jan-2025.htm

Enhancements

This section describes general enhancements that were made in the PrismHR January 2025 monthly release.

Changes to the Create Employee W-2C Forms

The default for the Clear Options on this form has been changed to Do not clear existing forms as you can see from the screenshot below. Since the Clear all existing forms option will delete all Form W-2c records in the system, it has been removed from being the default option. There is no change in existing functionality.

[Image: screenshot]

The EFW2C form has been renamed to EFW2C Download and Maintenance

Since the earlier form name was not descriptive enough, it has been renamed as stated above. There is no change in existing functionality.

[Image: screenshot]

JIRA # CMP-6247

Tax Year format changed on Form 1099 prints

Now the Form 1099 printed by PrismHR will be in the YYYY format instead of YY.

JIRA # CMP-6242

Changes to the EFW2 Download form

Now, the File Name field on the EFW2 Download form by default reflects W2REPORT.txt (the file extension in lower case) instead of W2REPORT.TXT. The file extension for the EFW2 download file will be lowercase txt. This change is implemented as the State of Ohio specifically requires lowercase txt extension. This change will apply to any Export File Type namely, SSA (Federal), State or Local for any State.

[Image: screenshot]

JIRA # CMP-5849

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/MR202502/CMP-Enhancements%20Feb-2025.htm Path: CMP/Release-Notes/Enhancements/2025/MR202502/CMP-Enhancements Feb-2025.htm

Enhancements

This section describes general enhancements that were made in the PrismHR February 2025 monthly release.

Changes to the EFW2 for the state of Maryland

Maryland changed the requirements of their state EFW2. The following changes are implemented for Employer Reporting of Form W-2 so that your files do not get rejected:

JIRA # CMP-6342

Changes to the EFW2C Download and Maintenance form

Previously using this form, though you could generate downloads that reported the original and corrected employee Form W-2c data. Since this download was run many times in a tax year, you kept getting the original group of employees over and over. There was no option to automatically deselect the employees for whom the Form W-2c data was already successfully submitted to the Social Security Administration earlier and was not needed to be resubmitted. This required your manual intervention to segregate the Form W-2c data for the right employees and potentially caused errors.

To mitigate this, starting tax year 2024 and beyond, this form will generate the download files in batches, with each batch identified by a system generated Filename on the Generated EFW2C Files section. One batch will not include any employee from another batch, thus reducing your manual intervention and chances of errors.

The following changes have been made to this form.

[Image: screenshot]

JIRA # CMP-5956, CMP-6366

The Edit EFW2C File Status form

Use this form to change/update the Status of the EFW2C download file in the Generated EFW2C Files grid on the EFW2C Download and Maintenance form mentioned above.

[Image: screenshot]

Click Save to save the changes made on this form so that it reflects correctly on the Generated EFW2C Files grid on the EFW2C Download and Maintenance form. If you do no wish to save the changes, then you can close this form using the

[Image: screenshot]

button on the top right of this form.

JIRA # CMP-6276, CMP-6338

CFC ACADATABUILD is now activated in PrismPrismHR

Previously, the Custom Feature Code ACADATABUILD used to be activated anytime when someone logged in to HRPyramid to build the ACA data for the prior month. Now, this Custom Feature Code ACADATABUILD is activated in PrismHR. The purpose of this CFC is to allow ACA data to build from the beginning of the year in an ongoing manner because when trying to build for the entire year the process sometimes can take many days for larger companies. This CFC will now incrementally build data used for ACA reporting throughout the year. This however does not replace the need to use the Rebuild ACA Data process already existing in PrismHR. You may still need to use the Rebuild ACA Data process if data for employees change or if the client is not set up as a large employer in PrismHR.

JIRA # CMP-6162

PrismHR now shelters local wages under the 60-63 Catch Up

Previously, PrismHR did not shelter local wages under the 60-63 Catch Up for Secure 2.0 when the contributions were Pre-Tax. It only sheltered up to the regular Catch Up Limit. Enhancements made to PrismHR now shelters local wages under the 60-63 Catch Up for Secure 2.0 when the contributions are Pre-Tax.

For payrolls available for processing in 2025:

PrismHR includes the full catchup amount in all Federal, State, and Local sheltered earnings.

JIRA # CMP-6058

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/QR202503/CMP-Enhancements%20Mar-2025.htm Path: CMP/Release-Notes/Enhancements/2025/QR202503/CMP-Enhancements Mar-2025.htm

Enhancements

This section describes general enhancements that were made in the PrismHR March 2025 quarterly release.

Changes to the MasterTax Interface Parameters form

On the MasterTax Interface Parameters form, the MasterTax RTS Import File Version is updated to Version 48.

[Image: screenshot]

JIRA # CMP-6455

MasterTax v48 will include NYC and Yonkers tax

The Employee Wage (601) - New York Unemployment record in MasterTax v48 will include the New York City tax and the Yonkers tax withheld for 33-24 (NY SUTA), zero-filled and right justified.

JIRA # CMP-6403

MasterTax V48 - ME PFML

In MasterTax V48 and above, for Tax Year 2025 and beyond, every instance of tax code 20-40 (ME PFML Employee Contribution) will be reported as a major tax code ME0000-014 (Maine Paid Family and Medical Leave) both on the Employer and the Client level for both SBEA and non-SBEA clients.

JIRA # CMP-6458

MasterTax V48 - DE PFML

In MasterTax V48 and above, for Tax Year 2025 and beyond, every instance of tax code 08-40 (DE PFML Employee Contribution) will be reported as a major tax code DE0000-014 (Delaware Paid Family and Medical Leave) both on the Employer and the Client level for both SBEA and non-SBEA clients.

JIRA # CMP-6457

Changes to the Benefits Per Hour form

For customers required to submit Certified Payroll Reports, new payroll voucher fields have been created for future reporting requirements. Now, when an employee has the Benefit Per Hour form set with the pay code reference to a fringe benefit, the data will be stored with the employee payroll voucher.

Note: Note: To better support Certified Payroll and WH-347 reporting, we have incorporated the values entered in the Benefit Per Hour form to the reporting payroll file. In an upcoming release, you will find this information populating on the certified payroll reports, employee check stubs, and Form WH-347.

JIRA # CMP-6212

Changes to the Client EEO-1 & Pay Data Files form

To support Illinois Equal Pay Registration Certificate reporting, the Client EEO-1 and Pay Data form has been enhanced with the IL Pay Data Report option. This report includes employees who worked at your factory/facility/office in Illinois plus the 100% remote employees who report directly to Illinois management.

[Image: screenshot]

This form has been enhanced to support the reporting of Illinois Pay Data for your employees. Under the Generate File section on this form:

Following is a sample IL Pay Data Report:

[Image: screenshot]

JIRA # CMP-6178, CMP-6179

Garnishment Capping Logic extended to State Tax Levy

From now on, when the Enhanced Garnishment Capping field is checked on the System Parameters form, the system will ensure that the garnishment amount for a State Levy docket does not exceed the flat amount of a given State Levy docket minus the sum of all garnishment deductions made for said docket, during the applicable pay cycle. If an employee has been paid in a previous payroll batch for the same pay period with garnished wages, the State Levy garnishment will only deduct the difference of the total flat amount less the amount garnished on a prior batch for that period. If the State Levy garnishment is reduced to zero, then the system will not calculate garnishment fee for the State Levy as the garnishment for State Levy on current payroll is not deductible.

JIRA # CMP-6138

Changes to the State Garnishment Rules form

Certain states have varying requirements on how to calculate a State tax levy when an employee has other garnishments. To allow flexibility to better support states allowing other garnishments including creditor garnishment deduction before calculating the amount due to the state levy, a new option has been added to the form. To support this feature, a new field named Allow Creditor Garnishment deduction before State Levy is added under the Rules for Calculating Withholding for Creditor Garnishments section on this form. This field is a checkbox.

[Image: screenshot]

If for a selected state, this checkbox is:

  1. Child Support (Spousal Support)

  2. Bankruptcy

  3. Levies (IRS Tax Levy, FTB)

  4. Creditor Wage Garnishment / Student Loan

  5. State Tax Levy

  1. Child Support (Spousal Support)

  2. Bankruptcy

  3. Levies (IRS Tax Levy, FTB)

  4. State Tax Levy

  5. Creditor Wage Garnishment / Student Loan

Note: Note: When using the new option to prioritize Creditor Wage Garnishments prior to the State Tax Levy, you should ensure that the State Tax Levy maximum percent has been entered for the applicable State Code on the State Garnishment Rules form.

JIRA # CMP-6069

Changes to the Employer Details form

From now on, if for an employer, under the Form W-2/1099 Initialization Audit & Control section on this form, the Mask SSN on W-2’s Beginning In field:

[Image: screenshot]

JIRA # CMP-4452

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/QR202503/CMP-Other%20Enhancements%20Mar-2025.htm Path: CMP/Release-Notes/Enhancements/2025/QR202503/CMP-Other Enhancements Mar-2025.htm

Other Enhancements

This section describes other enhancements that were made in the PrismHR March 2025 quarterly release.

Changes to the System Parameters form

A new field named Require change reason on critical forms has been added as shown below. This field will help you to track the reason provided by users when they make changes to any of the following critical forms:

[Image: screenshot]

This field is a dropdown. Select one of the following options:

[Image: screenshot]

JIRA # WSP-1213, WSP-1220, WSP-1228, WSP-1229,

Change Reason History form

Under the

[Image: screenshot]

menu on each of the following critical forms, a new form named Change Reason History has been introduced.

This form will provide the change reason history for each of the critical forms noted above.

Note: Note: This form will be able to capture the change reason history only if the field named Require change reason on critical forms on the System Parameters form is either selected as Optional (and the user has entered a reason for record update) or Required. When you make any change to any of the above forms, you will be presented with the following dialog box. Once you record the reason for the change herein, the same will be presented in the Change Reason History form.

[Image: screenshot]

On this form the following two fields are available:

Click Close to close this form and return to the base form.

Following is a sample Change Reason History of the State Rules form.

[Image: screenshot]

Following is a sample Change Reason History of the Employer Details form.

[Image: screenshot]

Following is a sample Change Reason History of the Client Details form.

[Image: screenshot]

JIRA # WSP-1234

Changes to the Employer Details form

The tab order on this form has been enhanced to ensure that it is sequential and does not skip any field.

Under the State Tax section of this form, under the State column, the state codes from now on will display in alphabetical order once any changes are saved.

[Image: screenshot]

JIRA # WSP-1101

Changes to the Client Details form

On this form, under the Tax tab, under the State Tax Setup section, under the State column, the state codes with or without suffixes from now on will display in alphabetical order once any changes are saved.

[Image: screenshot]

JIRA # WSP-1058, WSP-1571

Changes regarding W-8 employees

941 Quarterly Report

From now on, the 941 Quarterly Report built either by Employer, All Clients, Client or with Schedule R breakout will not include wages and tax withholdings for any W-8 employee. This change will also affect the following:

JIRA # WSP-1041

W-8 employees excluded from the W2/W2C builds

From now on, when you withhold federal and/or state income tax for W-8 employees, this data for the W-8 employees will be omitted from the W2 and W2C builds. Consequently, the following reports in PrismHR will not include data for W-8 employees:

JIRA # WSP-1040

Note: Note: A W-8 employee in PrismHR is one who according to the Employee Details form, under Tax tab, under the Federal Tax Filing section has the Form W8 Filed field checked.

[Image: screenshot]

========================================================================

Change to the PrismHR Tax Parameters form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202504/Change%20to%20the%20PrismHR%20Tax%20Parameters%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202504/Change to the PrismHR Tax Parameters form.htm

Change to the PrismHR Tax Parameters form

On the PrismHR Tax Parameters form, a new field named Include Schedule R Reporting is added. This field is a checkbox. When this option is selected, the Quarterly JSON Tax Export will generate the SBEA version of the file.

[Image: screenshot]

JIRA # CMP-6421

========================================================================

Changes to the 1095C Report Download form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202504/Changes%20to%20the%201095C%20Report%20Download%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202504/Changes to the 1095C Report Download form.htm

Changes to the 1095C Report Download form

Previously using this form, when you downloaded the report and opened the zip file, there was a lack of visibility as to which employee the Form-1095C belonged to on the file itself. To address this issue, from now on the zip file will contain the PDF files in the format COMPANYID.YEAR.EMPLOYEEID.f1095c.pdf as shown in the sample below.

[Image: screenshot]

JIRA # WSP-1657

========================================================================

Display Benefit Per Hour pay code on Certified Payroll Report

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202504/Display%20Benefit%20Per%20Hour%20pay%20code%20on%20Certified%20Payroll%20Report.htm Path: CMP/Release-Notes/Enhancements/2025/R_202504/Display Benefit Per Hour pay code on Certified Payroll Report.htm

Display Benefit Per Hour pay code on Certified Payroll Report

The Certified Payroll Report for an employee will now report the Benefits Per Hour memo pay codes as a calculated amount as shown below:

[Image: screenshot]

If:

On the Projects form, the Subtract Benefit/Hour from calculated Pay Rate field for the project is checked as shown below AND

[Image: screenshot]

On the Employee Details form, under the Pay tab, the said employee has Benefits Per Hour entered as shown below AND

[Image: screenshot]

On the Benefits Per Hour form for that employee, the Pay Codes are duly added as shown below.

[Image: screenshot]

Note: NOTE:

The Include in Certified Pay Report Fringe Summary field under the Processing Options section must be checked for all the Benefits Per Hour memo (Pay Class) pay codes listed in the above noted Certified Payroll Report on the Pay Codes form as shown below:

[Image: screenshot]

JIRA # CMP-6010

========================================================================

Employer override to PEO when the State is set to combined reporting

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202504/Employer%20override%20to%20PEO%20when%20the%20State%20is%20set%20to%20combined%20reporting.htm Path: CMP/Release-Notes/Enhancements/2025/R_202504/Employer override to PEO when the State is set to combined reporting.htm

Employer override to PEO when the State is set to combined reporting

Previously, when a state was set as for SUTA reporting based on the PEO but reported on the client level (in the State Rules form the SUTA PEO/Client Based field was selected as SUTA is PEO Based and the Client SUTA Report Only field was checked and on the Employer Details form, under the State Tax section, the SUTA Rpt Entity is selected as PEO for that state) then the system did not remove the Client Reporting only flag resulting in CR on the tax reporting rather than reporting under the Employer. On the employee payroll voucher, under the Employer Tax section for that state tax code the Client Reporting Only field for that state tax code displayed Y.

From now on, when a state has an override on the Employer Details form (as indicated above) to report at the PEO level, the Tax Basis will be P and the Client Reporting Only field for that state tax code display N.

Note: Note: If an override for the state exists on the Client Details form, then the state will be Client Reporting (tax basis - C) only when under the Tax tab, under the State Tax Setup section, a Client Reporting Start Date is entered for that state, otherwise it will be ignored.

JIRA # CMP-6045

========================================================================

Exclude Fringe Benefits from Gross Pay on Pay Stubs

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202504/Exclude%20Fringe%20Benefits%20from%20Gross%20Pay%20on%20Pay%20Stubs.htm Path: CMP/Release-Notes/Enhancements/2025/R_202504/Exclude Fringe Benefits from Gross Pay on Pay Stubs.htm

Exclude Fringe Benefits from Gross Pay on Pay Stubs

Now you have the ability to exclude Fringe Benefits from being recorded in Gross Pay on Pay Stubs.

On the Print Service Global Check Parameters form, under the Global Check Configuration section, for the Check Options field, a new drop-down named Exclude Non-Cash Fringe from Gross Wages is added.

[Image: screenshot]

Note: Note: You need to select this option along with the Always Display Gross Wages option as shown above. If you try to select the option Exclude Non-Cash Fringe from Gross Wages when the Always Display Gross Wages option is not selected, you will receive an error message stating Always Display Gross Wages selection is required to Exclude Non-Cash Fringe from Gross Wages.

JIRA # CMP-5612

========================================================================

Supporting Check Stub Requirements for Maryland

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202504/Supporting%20Check%20Stub%20Requirements%20for%20Maryland.htm Path: CMP/Release-Notes/Enhancements/2025/R_202504/Supporting Check Stub Requirements for Maryland.htm

Supporting Check Stub Requirements for Maryland

To support check stub requirements for the state of Maryland, for each of the following check stub formats supported by PrismHR, the following will be included:

Following is a sample:

[Image: screenshot]

JIRA # CMP-6164

========================================================================

Warning Message for misaligned Alternate Employer

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202504/Warning%20Message%20for%20misaligned%20Alternate%20Employer.htm Path: CMP/Release-Notes/Enhancements/2025/R_202504/Warning Message for misaligned Alternate Employer.htm

Warning Message for misaligned Alternate Employer

If a client is assigned to an employer who is a Certified Professional Employer Organization (CPEO), then for this client, using the Client Details form, under the Other tab, under the Alternate Employers section, if you try to add an employer who is not a Certified Professional Employer Organization, then from now on, you will receive the following warning message:

[Image: screenshot]

JIRA # CMP-6379

========================================================================

Changes to the Create Employee W-2C Forms form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202505/Changes%20to%20the%20Create%20Employee%20W-2C%20Forms%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202505/Changes to the Create Employee W-2C Forms form.htm

Changes to the Create Employee W-2C Forms form

As a service provider, you now have the option to import a list of employees for which Form W-2cs are to be created using the Create Employee W-2C Forms form.

[Image: screenshot]

A new button named Upload Employees is now available beside the Employee table.

JIRA # WSP-762, WSP-1673

========================================================================

Changes to the Periodic Tax JSON Export form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202505/Changes%20to%20the%20Periodic%20Tax%20JSON%20Export%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202505/Changes to the Periodic Tax JSON Export form.htm

Changes to the Periodic Tax JSON Export form

The PrismHR Tax Processing Work Center now has the Periodic Tax JSON Export form added to it as shown below.

[Image: screenshot]

The File Type of JSON is no longer available on the Daily Tax Export form. You will need to use this form instead to generate or regenerate the PTS periodic tax JSON export file.

[Image: screenshot]

Use the Periodic Tax JSON Export form to generate PTS periodic tax JSON export file or to regenerate processed PTS periodic tax JSON export file.

Note: Note: Client Access Group security is not enabled on this form.

To access this form, on the Work Centers under Tax, click PrismHR Tax Processing. Under File Exports, click Periodic Tax JSON Export.

To build the periodic tax JSON export file:

  1. Complete the following fields:
Field Name Description
Build File by Select one of the following options from the following: - All Clients and Employers - This is the default option. Select this option to build the JSON tax export for a selected date range. - Employer ID - Client ID - Regenerate Processed PTS File - Select the appropriate Processed PTS File from the drop-down to regenerate. When you select this option then the following two options, namely Tax Date Start and Tax Date End disappear and cannot be selected.

  1. Click Build to build the regenerate processed PTS periodic tax JSON export file. As a PTM user, to accurately report PA local taxes, the Daily Tax JSON export file has the work and resident PSD codes in the Employee Wage Detail node.

  2. Click Cancel to clear this form at any time.

JIRA # CMP-6206

========================================================================

Changes to the PrismHR Client Setup JSON Export File

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202505/Changes%20to%20the%20PrismHR%20Client%20Setup%20JSON%20Export%20File.htm Path: CMP/Release-Notes/Enhancements/2025/R_202505/Changes to the PrismHR Client Setup JSON Export File.htm

Changes to the PrismHR Client Setup JSON Export File

When generating the PrismHR Tax Client Setup JSON file using the PrismHR Client Setup JSON Export form, any client reported taxes will include a 00-10 and 00-17 (FIT and FUTA tax code) required for set up.

JIRA # CMP-6591

========================================================================

Changes to the Quarterly Tax JSON Export form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202505/Changes%20to%20the%20Quarterly%20Tax%20JSON%20Export%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202505/Changes to the Quarterly Tax JSON Export form.htm

Changes to the Quarterly Tax JSON Export form

Now on the Quarterly Tax JSON Export form:

[Image: screenshot]

Note: Note: Development is already in progress after which this File History section noted above on the Quarterly Tax JSON Export form will have more reports added to it in future releases.

JIRA # CMP-6128

========================================================================

Changes to the State Garnishment Rules form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202505/Changes%20to%20the%20State%20Garnishment%20Rules%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202505/Changes to the State Garnishment Rules form.htm

Changes to the State Garnishment Rules form

On this form, under the Rules for Calculating Withholding for Creditor Garnishments section, a new field name Multiple Order Priority Method has been added. This field will help you to manage the varying rules for different states for creditor garnishments like child support.

[Image: screenshot]

Select one of the following options from the dropdown:

Note: Note: If a Creditor Garnishment has an override state, it will follow the rules for the override state.

JIRA # CMP-6425, CMP-6388

========================================================================

Changes to the Labor Unions form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202506/Changes%20to%20the%20Labor%20Unions%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202506/Changes to the Labor Unions form.htm

Changes to the Labor Unions form

On the Labor Unions form, on the Union Deduction Code table, after the Union Dues Table Rules column, there is a new column named Periods as shown in the screenshot below. The GLOBAL custom feature code UNIONDEDPERIOD must be turned on for this field to display and being editable. If the GLOBAL custom feature code UNIONDEDPERIOD is turned off the Periods column will still display, but you cannot edit it.

[Image: screenshot]

Period here refers to the deduction period which references the week of the month for the payroll. For instance, if your weekly Pay Date was 02-28-2025 which was a Friday and 02-28-2025 was the 4th Friday of February, so Deduction Period will be 4. The Periods column indicates this Deduction Period for the corresponding Union Deduction Code.

JIRA # CMP-6488

========================================================================

Changes to the MasterTax Interface Parameters form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202506/Changes%20to%20the%20MasterTax%20Interface%20Parameters%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202506/Changes to the MasterTax Interface Parameters form.htm

Changes to the MasterTax Interface Parameters form

On the MasterTax Interface Parameters form, a new field named Include Pennsylvania Work State Flag (Y/N) is introduced as shown in the screenshot below.

[Image: screenshot]

This field is optional.

This field is a checkbox. It is selected by default.

This will apply for:

JIRA # CMP-6533, CMP-6537, CMP-6538

========================================================================

Changes to the PrismHR Tax Processing Work Center

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202506/Changes%20to%20the%20PrismHR%20Tax%20Processing%20Work%20Center.htm Path: CMP/Release-Notes/Enhancements/2025/R_202506/Changes to the PrismHR Tax Processing Work Center.htm

Changes to the PrismHR Tax Processing Work Center

The PrismHR Tax Processing Work Center (BETA) has been renamed PrismHR Tax Processing.

[Image: screenshot]

JIRA # CMP-6474

========================================================================

Changes to the Weighted Average form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202506/Changes%20to%20the%20Weighted%20Average%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202506/Changes to the Weighted Average form.htm

Changes to the Weighted Average form

On the Weighted Average form, a new field named Exclude FLSA Exempt Employees is introduced as shown in the screenshot below.

[Image: screenshot]

This field will help you to use the same pay codes for both Exempt and Non-Exempt employees.

This field is a checkbox. This field is un-checked by default. You can check it and click Accept to enable this option.

JIRA # CMP-6569

========================================================================

MasterTax PTS update for West Virginia local employees

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202506/MasterTax%20PTS%20update%20for%20West%20Virginia%20local%20employees.htm Path: CMP/Release-Notes/Enhancements/2025/R_202506/MasterTax PTS update for West Virginia local employees.htm

MasterTax PTS update for West Virginia local employees

The MasterTax PTS 500 record for West Virginia locals (tax code 49XXXXXXX-32) will now include the payroll frequency indicator in position 184 for the following payroll frequencies:

If there is more than one frequency, it will default to the most frequently used frequency in the record. For example, if the PTS 500 record represents 100 vouchers, and 99 of those vouchers are on a monthly pay schedule while one voucher is on a weekly schedule, then the frequency code in position 184 will contain “M” for monthly. This is because monthly is more frequent than weekly.

Also, if a voucher has a Daily frequency, then the system will ignore those. This is because for any frequency other than W/B/S/M, we should leave position 184 blank. Thus, if 99 vouchers have a daily frequency while one voucher has bi-weekly, then the system will set the MasterTax PTS code to “B” for bi-weekly. Similarly, if all the vouchers are on a daily schedule, then position 184 will be blank.

JIRA # CMP-6463

========================================================================

MasterTax RTS update on Worksite ID

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202506/MasterTax%20RTS%20update%20on%20Worksite%20ID.htm Path: CMP/Release-Notes/Enhancements/2025/R_202506/MasterTax RTS update on Worksite ID.htm

MasterTax RTS update on Worksite ID

When a Worksite Location has a Worksite ID, then on the MasterTax RTS file:

JIRA # CMP-6550

========================================================================

Railroad Unemployment Insurance Act Tax

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202506/Railroad%20Unemployment%20Insurance%20Act%20Tax.htm Path: CMP/Release-Notes/Enhancements/2025/R_202506/Railroad Unemployment Insurance Act Tax.htm

Railroad Unemployment Insurance Act Tax

The Tax tab of the Client Details form now has a new field named RUIA Rate as shown in the screenshot below.

[Image: screenshot]

RUIA Rate is Railroad Unemployment Insurance Act Tax rate. When a client is set up as a Railroad Employer, payrolls processed under the client will not include employer FUTA or FICA withholding and will instead implement RUIA withholding at the rate entered in the RUIA Rate field under the Tax Parameters section under the Tax tab on the Client Details form. The taxes withheld for RUIA will be reported on the MasterTax RTS, PTS, and PrismHR Periodic and Quarterly Files. The existing translation for core FICA tax codes to the Railroad equivalent will remain the same:

Employee Tax Employer Tax
00-60 RAILROAD TIER 1 SOC SEC EE 00-61 RAILROAD TIER 1 SOC SEC ER
00-62 RAILROAD TIER 2 SOC SEC EE 00-63 RAILROAD TIER 2 SOC SEC ER
00-64 RAILROAD TIER 1 MEDICARE EE 00-65 RAILROAD TIER 1 MEDICARE ER

JIRA # WSP-1746, WSP-1747

========================================================================

Changes to the Employee Details form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202507/Changes%20to%20the%20Employee%20Details%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202507/Changes to the Employee Details form.htm

Changes to the Employee Details form

To support 2026 Secure 2.0 requirements, on the Employee Details form in PrismHR, under the Other Tab, we have introduced the Retirement HPE Status grid. This will be further supported later this year.

For a Highly Paid Employee (HPE), the Retirement HPE Status panel tracks if the employee met or exceeded the HPE threshold in the prior tax year. For example, for tax year 2024, if the employee met this threshold, then the record would be entered as 2025 with the option selected as Yes.

[Image: screenshot]

This grid has field level security as it contains salary information. This field therefore will be hidden by default. You will need to enable it using the User Roles form.

JIRA # CMP-6541

========================================================================

Changes to the New York Quarterly Combined Wage Report

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202507/Changes%20to%20the%20New%20York%20Quarterly%20Combined%20Wage%20Report.htm Path: CMP/Release-Notes/Enhancements/2025/R_202507/Changes to the New York Quarterly Combined Wage Report.htm

Changes to the New York Quarterly Combined Wage Report

The state of New York has updated their combined reporting file specifications as of 01/01/2025. Click this link to visit the official website of New York State for the changes to withholding tax and wage reporting.

As this report can be created in Report Center in CSV format as per the updated specifications, you will need to use the Report Center only to generate this report for Q1 2025 and beyond. However, you can still generate this report in PrismHR for Q4 2024 and prior for past filings and verification of data.

Note: For information on how to generate this report in Report Center, consult the Report Center help documentation located on the Report Center sidebar. If this report is not available for your User ID in Report Center, contact your Report Center Administrator for assistance.

[Image: screenshot]

If you try to generate a report for any quarter for tax year 2025 and beyond by clicking the Generate Report button as shown above, you will receive the following notification. No report will be generated.

[Image: screenshot]

JIRA # CMP-6335

========================================================================

Changes to the Periodic Tax JSON Export

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202507/Changes%20to%20the%20Periodic%20Tax%20JSON%20Export.htm Path: CMP/Release-Notes/Enhancements/2025/R_202507/Changes to the Periodic Tax JSON Export.htm

Changes to the Periodic Tax JSON Export

The following changes have been made to the Periodic Tax JSON Export form as indicated in the screenshot below.

[Image: screenshot]

Report Period - Include All - Select this option to run the periodic tax export for all new TAX.JOURNAL records. - Pay Date Range - Select this option if you want to build the PrismHR Tax Export file for a specific pay date range. Complete the following fields: - Tax Date Start - Select the start date of the pay date range for the PrismHR Tax Export file that you want to generate. - Tax Date End - Select the end date of the pay date range for the PrismHR Tax Export file that you want to generate. Note: Once a file is generated, unless the Run in Test Mode option is set to Yes, the records included will be cleared from the TAX.JOURNAL file to prevent duplicated data.

========================================================================

Changes to the PrismHR Tax Parameters form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202507/Changes%20to%20the%20PrismHR%20Tax%20Parameters%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202507/Changes to the PrismHR Tax Parameters form.htm

Changes to the PrismHR Tax Parameters form

On the PrismHR Tax Parameters form, a new section named PrismHRTax Override Parameters has been added.

[Image: screenshot]

PrismHRTax Override Parameters For PrismHR Tax customers, the PrismHR Tax Parameters include this option to override the default banking information in the Client Setup files. The banking information entered here will be used for future debits and payments.
Override Employer Suffix Code (this field is not new - it has been included in this section from above) This code will append to any employer record with an identifier override. All other records will not include a suffix code. - If there is a PTM Identifier Number (for example ABC) entered on the Employer Details form (Emp ID 6485), and an Override Employer Suffix Code (for example XYZ) is entered on this form, then this suffix code will append to the client code (for example E6485XYX) for any employer record with an override identifier. - If no PTM Identifier Number is entered on the Employer Details form, then the client code will not add the Override Employer Suffix Code and will remain as is (from the above example E6485). Any employer that does not have the employer override will continue to use the System PTM code as the Processor ID. - This will also apply to the Daily Tax Export JSON output and to both the stand-alone file and the Include PTM Tax Agency Export file output using the Daily Tax Export form.

========================================================================

Remove remaining dependency on GLOBAL.PTO CFC

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202507/Remove%20remaining%20dependency%20on%20GLOBAL.PTO%20%20CFC.htm Path: CMP/Release-Notes/Enhancements/2025/R_202507/Remove remaining dependency on GLOBAL.PTO CFC.htm

Remove remaining dependency on GLOBAL.PTO CFC

We are retiring the custom feature code GLOBAL.PTO. Previously, many GLOBAL PTO features were not available without the custom feature code. After the custom feature code GLOBAL.PTO is removed from the System Parameters form, now:

JIRA # CMP-6484

========================================================================

Changes to the EEO Ethnic Codes form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202508/Changes%20to%20the%20EEO%20Ethnic%20Codes%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202508/Changes to the EEO Ethnic Codes form.htm

Changes to the EEO Ethnic Codes form

The EEO Report Code field in this form now has a new option in the drop-down named Middle Eastern / North African as shown in the screenshot below:

[Image: screenshot]

This EEO Report Code will be incorporated into required reports in a future release.

JIRA # CMP-6562

========================================================================

Changes to the Employee Details form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202508/Changes%20to%20the%20Employee%20Details%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202508/Changes to the Employee Details form.htm

Changes to the Employee Details form

On this form, under the Skills & Education tab, a new section named WH347 Skilled Trade Classification has been added as shown in the screenshot below:

[Image: screenshot]

The Journeyworker/Apprentice field has the following dropdowns:

The Apprentice Program Approval field has the following dropdowns:

The Level of Progression field indicates the level of apprenticeship of the registered apprentice and has the following dropdowns:

The Comments field - You can fill in any comments that you may like to add.

This information will be used to populate the corresponding information on the new Form WH-347.

JIRA # CMP-6414

========================================================================

Changes to the Pay Codes form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202508/Changes%20to%20the%20Pay%20Codes%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202508/Changes to the Pay Codes form.htm

Changes to the Pay Codes form

Under the Processing Options section on this form, a new field is introduced named Include in Check Stub Gross Wage calculation as shown in the screenshot below:

[Image: screenshot]

This field is a checkbox. On the Print Service Global Check Parameters form, under the Check Options, the Always Display Gross Wages option needs to be selected for this Include in Check Stub Gross Wage calculation field on the Pay Codes form to function.

JIRA # CMP-6643

========================================================================

Changes to the Recalculate Alabama Income Tax Exempt Wages form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202508/Changes%20to%20the%20Recalculate%20Alabama%20Income%20Tax%20Exempt%20Wages%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202508/Changes to the Recalculate Alabama Income Tax Exempt Wages form.htm

Changes to the Recalculate Alabama Income Tax Exempt Wages form

Previously, for any Overtime wages earned in June 2025 but paid in July 2025, the Alabama Overtime exemption was not honored. The recalculation utility did not recalculate on pay dates in July with June charge dates.

Now, for any wages earned in June 2025 but paid in July 2025, the Alabama Overtime exemption will be honored. Exempt overtime wages earned on or before June 30 but not paid until July 2025 may be reported on the July 2025 Form A-6 or the September Form A-1 if quarterly filing. The Alabama income tax exemption applicable to overtime wages ended on June 30, 2025.

When recalculating the exempt overtime amounts for Alabama wages earned in June but paid in July, you may also need to process corresponding tax adjustments. The Recalculate AL Overtime utility will be applied to the employees W2 and quarterly tax reports. The Recalculate utility will not adjust an employee’s taxable wages or tax amounts. After running the Recalculate AL Overtime utility, you can leverage Report Center to review the employees taxable wages with the exempt overtime amounts. This report can be created using the Employee Payroll Voucher data set with the field exempt_ot.

[Image: screenshot]

[Image: screenshot]

JIRA # CMP-6657

========================================================================

Recalculate Global PTO Vouchers

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202508/Recalculate%20Global%20PTO%20Vouchers.htm Path: CMP/Release-Notes/Enhancements/2025/R_202508/Recalculate Global PTO Vouchers.htm

Recalculate Global PTO Vouchers

A new form named Recalculate Global PTO Vouchers is introduced as shown in the screenshot below.

[Image: screenshot]

Use this form to update any existing vouchers that need to be included in the Flat Amount by Hours Worked Global PTO accrual calculations when enabling Global PTO functionality mid-year for a client. This process will not calculate accruals or create PTO registers. You should use this process when you enable Global PTO mid-year and need to account for accruals in the past. So, when you enable Global PTO mid-year, this process allows the look-back calculation method the ability to pick up the vouchers in the past to accurately represent the YTD accrued balances for Global PTO.

Note: Note: Client Access Group security is enabled on this form. PrismHR

To access this form, click the Payroll menu. Under Action, click Recalculate Global PTO Vouchers.

To recalculate Global PTO vouchers in PrismHR:

  1. Complete the following field:

Field Name — Description

Start PAY Date — Enter the starting date of the pay date range from when you want to recalculate Global PTO for payroll vouchers.

  1. Click Preview. A job progress window opens and shows the total number of records to be updated. Click Close. You will see a preview consisting of the following columns:

  1. Click the Download hyperlink to download the above information in a .CSV format.

  2. Click Update to update the Global PTO information on the required payroll vouchers. You will receive a warning message stating You are going to apply these changes to these vouchers. Do you wish to proceed?

  1. Click Cancel to cancel the above operation. You can enter a different Start PAY Date and redo the process.

JIRA # CMP-4287

========================================================================

Changes to Garnishment calculation Details Report

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202509/Changes%20to%20Garnishment%20calculation.htm Path: CMP/Release-Notes/Enhancements/2025/R_202509/Changes to Garnishment calculation.htm

Changes to Garnishment calculation Details Report

Previously, you could view the garnishment calculation report on initialized vouchers when a garnishment amount was deducted; however, the report was not available if the garnishment amount was reduced to zero.

Now, the garnishment calculation report is available when gross wages are greater than zero, but the garnishment deduction cannot be applied. It details the calculation details of the garnishment and its reduction to zero and is available on initialized and posted vouchers. The garnishment report is available for all types of garnishments (Child Support, Creditor garnishments, Levies, etc.) when the garnishment amount has been reduced to zero due to limits defined in the State Garnishment Rules.

[Image: screenshot]

JIRA # CMP-4468

========================================================================

Changes to the Clear New Hire Reporting Dates form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202509/Changes%20to%20the%20Clear%20New%20Hire%20Reporting%20Dates%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202509/Changes to the Clear New Hire Reporting Dates form.htm

Changes to the Clear New Hire Reporting Dates form

You can now also use this form to clear the New Hire Reporting Date for one or more employees for a client. For example, if you are supporting international employees, they initially use a temporary SSN during the application period. When the permanent SSN is issued, the New Hire Reporting Date may need to be cleared so that those employees are included in the next reporting cycle. This enhancement allows you to do this.

On the Clear New Hire Reporting Dates form, after you enter the date range and a Client ID a grid now appears as shown in the screenshot below.

[Image: screenshot]

Here you can select one or more employees for whom you want to clear the New Hire Reporting Date for the selected date range. A confirmation message displays when complete. Clearing this date will cause this employee’s data to be included on the file when the next New Hire Reporting Process is run.

JIRA # CMP-6578

========================================================================

Garnishment Calculation Available After Posting Payroll

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202509/Garnishment%20Calculation%20Available%20After%20Posting%20Payroll.htm Path: CMP/Release-Notes/Enhancements/2025/R_202509/Garnishment Calculation Available After Posting Payroll.htm

Garnishment Calculation Available After Posting Payroll

From now on, the garnishment calculation report will be available for all initialized, posted and finalized payroll vouchers for Service Providers and Worksite Managers.

JIRA # CMP-5618

========================================================================

JSON Client Setup File updates

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202509/JSON%20Client%20Setup%20File%20updates.htm Path: CMP/Release-Notes/Enhancements/2025/R_202509/JSON Client Setup File updates.htm

JSON Client Setup File updates

From Q3 2025 and beyond, please note the updates for the following forms:

NOTE:

JIRA # CMP-6735

========================================================================

New York Form MTA-305 Tax Reporting rate update

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202509/New%20York%20Form%20MTA-305%20Tax%20Reporting%20rate%20update.htm Path: CMP/Release-Notes/Enhancements/2025/R_202509/New York Form MTA-305 Tax Reporting rate update.htm

New York Form MTA-305 Tax Reporting rate update

Effective Q3 2025 and beyond, the NY MTA-305 download been updated based on new requirements. Please note that the report will continue to calculate the payroll expense and included detail records with no change - the following changes to New York Form MTA-305 Tax Reporting rate are applicable to the Rate tier by zone:

Payroll Expense attributable to Zone 1 Metropolitan Commuter Transportation Mobility Rate
Over $0 but not over $375,000 0.055% (0.00055)
Over $375,000 but not over $437,500 0.115% (0.00115)
Over $437,500 but not over $2,500,000 0.60% (0.0060)
Over $2,500,000 0.895% (0.00895)
Payroll Expense attributable to Zone 2 Metropolitan Commuter Transportation Mobility Rate
Over $0 but not over $375,000 0.055% (0.00055)
Over $375,000 but not over $437,500 0.115% (0.00115)
Over $437,500 but not over $2,500,000 0.34% (0.0034)
Over $2,500,000 0.635% (0.00635)

Note: Note: To be subject to the MCTMT for the quarter, the employer must have payroll expense in the entire MCTD greater than $312,500. For PEO reporting, this is assessed on the client level. This means Zone 1 + Zone 2 must exceed US$312,500. BUT the rate is determined by the payroll expense by zone.

JIRA # CMP-6640

========================================================================

Overtime Recalculation for a Batch Report

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202509/Overtime%20Recalculation%20for%20a%20Batch%20Report.htm Path: CMP/Release-Notes/Enhancements/2025/R_202509/Overtime Recalculation for a Batch Report.htm

Overtime Recalculation for a Batch Report

Use this new report to view the data that determined the overtime recalculation adjustment amount. This is an informational report that explains how the overtime recalculation reached the adjustment amount. You can run this report on both initialized and posted payroll batches.

To generate the overtime recalculation for batch report:

  1. Complete the following:

Field Name — Description

Payroll Number — Enter the payroll number here or click the Payroll Number hyperlink and select it from the Select Payroll Batches dialog box.

Report Filters

Employee Id — This field is optional. If you want to run the report for selected employees, enter them here or click the Employee Id hyperlink and select the employees from the Employee for Report Filter dialog box.

Other Options

Employee Totals Only — This field is optional. Check this box if you only want to see the Overtime Report with Employee Totals only - see the second screenshot below. > Note: Note: This is the recommended format for large payroll batches.

  1. Click Run to generate the report and display it on screen.

  2. Click Close to close this form.

The following is a sample Overtime Report (without Employee Totals Only)

[Image: screenshot]

The following is a sample Overtime Report (Employee Totals Only)

[Image: screenshot]

Note: Note: The detail report may potentially present a variation in the calculation by week due to rounding. The total OTADJ amount found on the original voucher will be the full amount.

JIRA # CMP-4624

========================================================================

Changes to the Positions form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202510/Changes%20to%20the%20Positions%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202510/Changes to the Positions form.htm

Changes to the Positions form

PrismHR now helps you to define which positions are considered eligible for tipped positions to comply with the tip’s requirements of the One Big Beautiful Bill Act. A new field named TTO Code (Tipped Taxable Occupation Code) has been added to this form as you can see from the screenshot below. Eligible tipped positions are determined by a TTOC.

[Image: screenshot]

You can enter the TTO Code manually, or you can click the TTO Code hyperlink and select it from the TTO Codes dialog box. The TTO Description displays upon entering a valid TTO Code. If you manually enter an incorrect TTO Code, you will receive an error stating is not a valid TTO Code.

JIRA # CMP-6813

========================================================================

Changes to the PrismHR Tax Parameters form

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202510/Changes%20to%20the%20PrismHR%20Tax%20Parameters%20form.htm Path: CMP/Release-Notes/Enhancements/2025/R_202510/Changes to the PrismHR Tax Parameters form.htm

Changes to the PrismHR Tax Parameters form

On this form, under the PrismHR Tax Override Parameters section, a new field named Include PrismHR Tax ID in Override Client ID is introduced as you can see from the screenshot below.

[Image: screenshot]

This field is a checkbox and is unchecked by default.

JIRA # CMP-6874

========================================================================

PrismHR now supports the production of a Form W-2 for railroad employees

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Enhancements/2025/R_202510/Railroad%20Reporting%20Update.htm Path: CMP/Release-Notes/Enhancements/2025/R_202510/Railroad Reporting Update.htm

PrismHR now supports the production of a Form W-2 for railroad employees

Railroad employers use Form W-2 to report wage payments to employees and to SSA. RRTA taxes are shown on the employee Form W-2 in Box 14, Boxes 3, 4, 5, 6 and 7, relating to FICA and Medicare, should be blank. When an employee is covered under the RRTA and has payroll processed in PrismHR as a railraod employee, the FormW-2 created for the employee will now include the required information in Box 14. To support the required W-3 reporting requirements for Railroad employers, an employee cannot be both an employee covered under the RRTA AND FICA within the same employer. Additionally, we suggest a railroad employer should not have both FICA and RRTA employees.

If your employer has both types of employees, you will need to manually review and adjust the Form W-3 which will by default combine these types of employees. If an employee who has both FICA tax codes (00-11 or 00-15) and Railroad tax codes (00-60, 00-62 or 00-64) for the same tax year:

JIRA # CMP-6749

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202401/CMP-Fixes%20Jan-2024%20MR.htm Path: CMP/Release-Notes/Fixes/2024/MR202401/CMP-Fixes Jan-2024 MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the January 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-5374 Previously, the overtime exemption for the state of Alabama in PrismHR was based on charge date. Now, the overtime exemption for the state of Alabama in PrismHR is based on pay date regardless of when the hours were worked.
CMP-5361 Previously, when an employee working in the state of Alabama had sheltered and exempt earnings that were greater than their taxable earnings, in some scenarios we saw the exempt and sheltered earnings exceeding the total wages on the voucher. When this happened, we also saw negative taxable wages and negative over-limit wages. The calculated tax amount remained 0.00. Now, when an employee working in the state of Alabama has taxable earnings that are less than the exempt overtime amount, the exempt amount is capped at the taxable wages. PrismHR will not display negative taxable wages or negative overlimit wages.
CMP-5329 Previously, for an employee who lives and works only in the state of Ohio, and the Form W-2 reported only Ohio wages, the EES (CIC) download incorrectly displayed PA in positions 1084-1085. Now, for an employee who lives and works only in the state of Ohio, and the Form W-2 reports only Ohio wages, the EES (CIC) download correctly displays OH in positions 1084-1085.
CMP-5253 Previously, the matching 401(k) contribution from the employer was not included in the taxable earnings listed on the employee’s voucher and was not included in the tax calculation for employees working in Oregon Tri-Met district and Lane County mass transit district. This is fixed. The matching 401(k) contribution from the employer is included in the taxable earnings listed on the employee’s voucher and is included in the tax calculation for employees working in Oregon Tri-Met district and Lane County mass transit district.
CMP-4746 Previously, for the Colorado Occupational Privilege Tax, the system incorrectly reported the gross taxable over the limit in box 18-20 on Form W-2 for SBEA clients. Now, for the Colorado Occupational Privilege Tax, the system correctly reports the gross taxable up to the wage limit in box 18-20 on Form W-2 for SBEA clients.
CMP-4733 Previously, on the local EFW2 download report in PrismHR, the report was generating a tax type R instead of C for Philadelphia local tax codes even when the tax type was set to local tax authority, a EFW2 code was entered, and a city code was set on the tax authority ID. The download file also generated 00 instead of 42 in positions 3 and 4 on the RS line. This is resolved. Now, for Philadelphia, PrismHR now generates a tax type C for all local tax codes on the local EFW2 download report. The download file also generates 42 instead of 00 in positions 3 and 4 on the RS line.
CMP-3278 Previously, when a memo pay code was set to a Labor Union, the memo pay code displayed as part of Gross Earnings which could imply the memo pay code is taxable. > Note: Note: This did not affect taxation of the pay, only the display of the gross earnings amount. Now, memo pay codes tied to labor unions are not included in the display for Gross Earnings.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202402/CMP-Fixes%20Feb-2024%20MR.htm Path: CMP/Release-Notes/Fixes/2024/MR202402/CMP-Fixes Feb-2024 MR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the February 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-5418 Previously, for a non-resident employee working in the state of Alabama, when using FLSA Ruleset, Overtime reported separately and hours worked in Alabama are over 40, the premium pay was not being flagged as exempt. Now, for any employee working over 40 hours in the state of Alabama, when using FLSA Ruleset, Overtime reported separately, the premium pay for Alabama overtime hours will also be exempt from Alabama state income tax regardless of the employee’s resident state.
CMP-5409 Previously, when printing multipage Form W-2s from the Employee Portal, the last page of the Form W-2s did not print the employer’s name and address in Box C. Now, when printing multipage Form W-2s from the Employee Portal, all pages of the Form W-2s correctly print the employer’s name and address in Box C.
CMP-5397 Previously, in some scenarios PrismHR faced a rounding issue when calculating overtime exemption for the state of Alabama. It also displayed a negative value in the Taxable Over Limit column on the employee voucher which also flowed into PTS. Now, PrismHR correctly calculates the new attributes for overtime calculation for the state of Alabama.
CMP-5389 Previously, if an employee had work week hours in the state of Alabama and lived in a non-taxing state such as Florida, PrismHR incorrectly combined the hours worked in those non-taxing states calculate the total work week hours for the state of Alabama. Now, if an employee has work week hours in the state of Alabama and is a resident of a non-taxing state that does not impose state withholding for example Florida, then PrismHR will not include any hours worked in those non-taxing states to calculate the total work week hours for the state of Alabama.
CMP-5386 Previously, payroll calculation failed in PrismHR if an ASO client redirected employee to employee or employer to employer taxes. Now, PrismHR allows an ASO client to redirect employee to employee or employer to employer taxes.
CMP-5384 Previously, when building W2 data on the Client Federal Entity Register for SBEA Employers, if an employee had worked under more than one employer in the state of New York for the tax year, PrismHR incorrectly added all Box 1 wages across each of the employer’s W-2s and reported them as NY wages on the Form W-2 in Box 16, which could overstate Box 6 NY state wages. Now, when building W2 data on the Client Federal Entity Register for SBEA Employers, when an employee has worked under more than one employer in the state of New York for the tax year, PrismHR displays the box 16 wage amount for the reporting employer which matches the Box 1 wage amount on the Form W-2.
CMP-5073 Previously, when completing a tax adjustment, with the flag “Adjust Client Tax Register” checked, Tax Identifier code (-37) did not update in the client tax register. It still displayed on the employer tax register. Now, when completing a tax adjustment, if the flag “Adjust Client Tax Register” is checked for Tax Identifier code (-37), it correctly updates in the client tax register.
CMP-4763 Previously, the Local EFW2 file for Lancaster County, PA generated by PrismHR displayed the tax authority name in positions 338-343 of the RS record instead of the employee’s resident PSD code. Now, the Local EFW2 file for Lancaster County, PA generated by PrismHR displays the full 6 digit PSD code in positions 338-343 of the RS record.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202404/CMP-Fixes%20Apr-2024.htm Path: CMP/Release-Notes/Fixes/2024/MR202404/CMP-Fixes Apr-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the April 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-5417 Previously, MasterTax Chart of Account Code field on the MasterTax Interface Parameters form incorrectly allowed non-alphanumeric characters. Now, MasterTax Chart of Account Code field on the MasterTax Interface Parameters form will only allow 2 alphanumeric characters.
CMP-4892 Previously, when an expense was reimbursed to an employee living and working in the state of Kentucky that has local school district tax, the system incorrectly included it as taxable earnings for calculating KY Local SCH Tax. Now, when an expense is reimbursed to an employee living and working in the state of Kentucky that has local school district tax, the system excludes it from taxable earnings for calculating KY Local SCH Tax as this is exempt.
CMP-5553 Previously, when adding the 105 record to the PTS, the sub cost center was incorrectly populated in positions 136-175 (GL Payroll Code). This should have been reported as the Company Code (Positions 56-95). Additionally, the Payroll Trailer (899) total record did not include the Record Count in positions 36-45. Now, these have been resolved. - Positions 136-175 in PTS 105 record is blank filled. - Positions 56-95 in PTS 105 record is populated with Subcost Center. - The Payroll Trailer (899) total record includes 105 record in the Record Count in positions 36-45.

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202405/CMP-Fixes-May-2024.htm Path: CMP/Release-Notes/Fixes/2024/MR202405/CMP-Fixes-May-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the May 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-5673 Previously, the EEO-1 build was using the current location instead of the As-of-Date to determine the employee location which caused data integrity issues. Now, this is fixed.
CMP-5671 Previously, you were not able to submit the CA Pay Data files generated by the system for tax year 2023 reported in 2024 owing to a change in two headers. Now, this is resolved, and you can submit the CA Pay Data files generated by the system for tax year 2023 reported in 2024.
CMP-5655 Previously, CMP-5432 (in April MR) inadvertently affected the calculations for employees with a union assigned for pay codes with a calculation method of Rate x Hours Worked. Now, this is fixed.
CMP-5636 Previously, the EEO-1 build was not importing the newly added Remote Worker field. This caused any workers initially flagged as remote to no longer be considered a remote worker for reporting. Now, this is fixed.
CMP-5428 Previously, the Employer Quarterly SUTA Tax Export file for the state of North Carolina did not meet all the specifications for submission of quarterly wage files. Now, you can submit the Employer Quarterly SUTA Tax Export file for the state of North Carolina without any difficulty.
CMP-4880 Previously, when generating the EEO-1 and CA Labor Contractor Report using a Report As-of-Date in December of the reporting year, the hours reported were the following year’s hours. Now, when generating the EEO-1 and CA Labor Contractor Report using a Report As-of-Date in December of the reporting year, the hours reported are for the correct reporting year for example a reporting date of 12/12/2023 will generate hours worked in 2023 instead of hours worked in 2024.
CMP-3659 Previously, on the Labor Union form, in the Union Dues Table section, if you selected Fixed Amount by Pay Rate Tier, then after the first line, you could not add additional rule lines to add additional tiers to the Fixed Amount by Pay Rate Tier rule. Now, in the Union Dues Table section you can add additional rule lines to add additional tiers to the Fixed Amount by Pay Rate Tier rule in the Labor Unions form.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202407/CMP-Fixes%20Jul-2024.htm Path: CMP/Release-Notes/Fixes/2024/MR202407/CMP-Fixes Jul-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the July 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-5797 Previously, if a Certified Payroll Report was generated with the Allocate Deductions/Taxes by Project field unchecked on the Certified Payroll Report form for an employee who had wages and fringe payments allocated to multiple projects, the net pay amount could be incorrect and did not always match the net pay on the voucher. Now, if a Certified Payroll Report is generated with the Allocate Deductions/Taxes by Project field unchecked on the Certified Payroll Report form for an employee who has wages and fringe payments allocated to multiple projects, the net pay amount is correct and matches the net pay on the voucher.
CMP-5760 Previously, when using the position override (union), and an employee worked in two projects under the same union on the same charge date, the Percent of Gross fringe calculated on the wages associated with the first project only. Now, when using the position override (union), and an employee works in two projects under the same union on the same charge date, the Percent of Gross fringe will calculate on the wages associated with the project.
CMP-5750 Previously, when a PFML tax code for CO, OR or WA for an employee or an employer was redirected to a different tax code, the tax limit was not honored on subsequent payrolls for Client and Employer tax basis (C or P). Now, when a PFML tax code for CO, OR or WA for an employee or an employer is redirected to a different tax code, the tax limit will be honored on subsequent payrolls for Client and Employer tax basis (C or P).
CMP-5727 Previously, when the Labor Union is assigned to both the Employee Details and the Positions forms, the Fringe pay code with % of Gross Earning calculation method was being calculated twice. Now, when the Labor Union is assigned to both the Employee Details and the Positions forms, the Union pay codes will not double.
CMP-5703 Previously, the Employer Quarterly SUTA Tax Export for North Carolina was getting rejected due to incorrect reporting of the Employer ID for Positions 8 - 17 on the RE and RT records. Now, the Employer Quarterly SUTA Tax Export for North Carolina correctly reports the NC Taxpayer ID/UI Account for Positions 8 - 17 on the RE and RT records as per the EFW2 file format.
CMP-5682 Previously, the system was incorrectly calculating the tax amount for Colorado Income Tax. Now, this is fixed.
CMP-5675 Previously, the system did not exempt Group Term Life Insurance in excess of $50,000 from State Unemployment Insurance tax for tax codes ending in -32 for all localities in Pennsylvania. Now, the system will exempt Group Term Life Insurance in excess of $50,000 from State Unemployment Insurance tax for all tax codes starting with 39 and ending in -32 for all localities in Pennsylvania except Philadelphia (391013000-32).
CMP-5606 Previously, for SC SUTA (41-24) we were reporting Month 1, Month 2, and Month 3 employment data in positions 111, 112, and 113 on the 601 record which is not correct according to MasterTax V46 specification. Now this is fixed. For SC SUTA (41-24) we will report Month1, Month 2, and Month 3 employment data in positions 147, 148, and 149 respectively and positions 107-141 will be blank on the 601 record which is as per MasterTax V46 specification.
CMP-5541 Previously, when a non-cash fringe pay code had a calculation method of Rate X Hours Paid (Select Codes) the total amount was calculating for a single project even though the employee was paid in multiple certified projects. Now, when a non-cash fringe pay code has a calculation method of Rate X Hours Paid (Select Codes) the total amount is calculated by each individual certified projects that the employee was paid in.
CMP-5052 Previously, on the Certified Pay Roll Report pdf, the Rate of Pay and Fringe Rate were overlapping. Now, this is fixed.
CMP-2982 Previously, the Employer Quarterly SUTA Tax Export for the state of Mississippi incorrectly reported the month as the first month of the quarter, instead of the last month in positions 215-220 on the S record. Now, this is fixed.
CMP-1459 Previously, on the Tax Adjustments form when AdjustClientTax Register was checked, the system did not follow it for employee tax codes XX-51 and XX-52. The Tax Basis displayed P instead of C. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202408/CMP-Fixes%20Aug-2024.htm Path: CMP/Release-Notes/Fixes/2024/MR202408/CMP-Fixes Aug-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the August 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-4942 Previously, in some scenarios, the system was not calculating the Occupational Privilege Tax correctly for all employees in Denver, Colorado. Now, this is fixed.
CMP-4353 Previously, the system was not billing correctly the Oregon Tri-Met Transit Tax (38-52) in alignment with accrual when an employee had OR Tri-Met Worksite Location assigned on the Employee Details form with some timesheet hours in a non-OR Tri-Met location. Now, this is fixed. Oregon Tri-Met Transit Tax (38-52) bill amount will match accrual when an employee has OR Tri-Met Worksite Location assigned on the Employee Details form with partial timesheet hours in a non-OR Tri-Met location.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202410/CMP-Fixes%20Oct-2024.htm Path: CMP/Release-Notes/Fixes/2024/MR202410/CMP-Fixes Oct-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the October 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-6080 Previously, PrismHR ignored the selections made under the Special Rules section on the Tax tab of the Employee Details form while calculating the Multnomah County Tax and the Portland Metro Tax. Now, this is fixed.
CMP-5995 Previously, on the MasterTax RTS: - The 500 records for tax codes 38-40 and 38-41 incorrectly included the sheltered amounts in positions 123-136 and 137-150 respectively and - The 601 record for tax code 38-24 (OR PMFL) incorrectly included the exempt amount in positions 428 - 441. Now, on the MasterTax RTS: - The 500 records for tax codes 38-40 and 38-41 will report: - QTD Gross Taxable Wages in positions 123-136 and - YTD Gross Taxable wages in positions 137 - 150. - The 601 record for tax code 38-24 (OR PMFL) will report: - Gross Taxable Wages for OR PFML in positions 428 - 441.

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/MR202412/CMP-Fixes%20Dec-2024.htm Path: CMP/Release-Notes/Fixes/2024/MR202412/CMP-Fixes Dec-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the December 2024 monthly release.

JIRA Number Issue Summary Resolution
CMP-6225 Previously, if a W-2 employee had a line 2 in their Resident Address but no line 2 in their Mailing Address, then the EES W2 Export was incorrectly combining the line 2 in their Resident Address as line 2 in their Mailing Address. Now, this is fixed.
CMP-6211 Previously, when cash wages such as Fringe Vacation or Holiday were also reported in the Fringe Summary the Net Wages Paid for the pay period did not display correctly on the Certified Payroll Report. Now, when cash wages such as Fringe Vacation or Holiday are also reported in the Fringe Summary the Net Wages Paid for the pay period matches the Net Voucher Amount on the Certified Payroll Report unless the Allocate Deductions/Taxes by Project field is checked on the Certified Payroll Report Format Parameters form.
CMP-6198 Previously, the EES Puerto Rico W-2 Export file had the Carriage Return at position 1600. Now, the EES Puerto Rico W-2 Export file has 1600 positions for all records with the carriage return at position 1601.
CMP-5744 Previously, when a Labor Union Affiliation code was assigned to the Employee Details form but no Union Code Override existed for any of the positions set on the client on the Positions form, then a change to the Union Deduction Codes on the Labor Union form did not correctly update the details on the Recurring Deduction form without saving the Employee Details record. Now, when a Labor Union Affiliation code is assigned to the Employee Details form but no Union Code Override exists for any of the positions set on the client on the Positions form, then a change to the Union Deduction Codes on the Labor Union form will correctly update the details on the Recurring Deduction form without saving the Employee Details record.
CMP-5632 Previously, for both ASO and PEO clients, for tax code 22-20 when the tax basis was employer, the MasterTax RTS file incorrectly showed zero for the client 500 and 501 records. Now, for both ASO and PEO clients, for tax code 22-20 when the tax basis is employer, the MasterTax RTS file does not show zero for the client 500 and 501 records.
CMP-5314 Previously, when an employee had a worksite location which is a remote location and had hours worked in a separate location which is not remote through either pay allocations or detailed timesheet entry, the wages earned were incorrectly taxed in the resident location only. Now, when an employee has a worksite location which is a remote location and has hours worked in a separate location which is not remote through either pay allocations or detailed timesheet entry, the wages earned are incorrectly taxed in the respective locations.
CMP-4990 Previously, for both SBEA and non-SBEA clients, when a 1099 contractor had federal or state income tax withheld, the W2 build process was picking up this 1099 contractor and reported the federal and state wages on a Form W-2. This meant that the W-2 Detail Report and the Form W-3 Totals Report also included this 1099 contractor which was incorrect. Now, when custom feature code 1099WITHHOLDING is set for both SBEA and non-SBEA clients, when a 1099 contractor has federal or state income tax withheld, the W2 build process will not pick up this 1099 contractor. The W-2 Detail Report and the Form W-3 Totals Report will not have such 1099 contractors.
CMP-4809 Previously, when an employee lived in Oregon and worked in another state and the OR Transit Tax (tax code 38-27) or the Multnomah County Income Tax (tax code 38051-30), was set to Calculate/Report at the Client Level (PEOs Only), on the Tax Deductions form, then the tax deduction code on the voucher was reported to the ER (tax basis, P) instead of the Client (tax basis, C). Now, when an employee lives in Oregon and works in another state and the OR Transit Tax (tax code 38-27) or the Multnomah County Income Tax (tax code 38051-30), is set to Calculate/Report at the Client Level (PEOs Only), on the Tax Deductions form, then the tax deduction code on the voucher is reported to the Client (tax basis, C).

Other Fixes

The following are some other issues that we’ve fixed in the December 2024 monthly release.

Jira Number Issue Summary Resolution
WSP-939 Previously, for the state of Ohio, on the Employer Quarterly SUTA Tax Export for PEO reported taxes or an ASO and on the Quarterly Tax Processing / Government Exports / Ohio export for Client reported taxes, the Adjustment Reason Code in the S Records in positions 248 - 249 were missing. Now, for the state of Ohio, on the Employer Quarterly SUTA Tax Export for PEO reported taxes or an ASO and on the Quarterly Tax Processing / Government Exports / Ohio export for Client reported taxes, the Adjustment Reason Code in the S Records in positions 248 - 249 contain zeros.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/QR202403/CMP-Fixes%20Mar-2024%20QR.htm Path: CMP/Release-Notes/Fixes/2024/QR202403/CMP-Fixes Mar-2024 QR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the March 2024 quarterly release.

JIRA Number Issue Summary Resolution
CMP-4921 Previously, when generating the CA Pay Data using the Build EEO-1 & Pay Data form, if under the Build Options, the Employee Filter field is set to “Paid more than $0 during the reporting period”, the system incorrectly showed Y for California for employees who had CA SUTA in a previous reporting year also. Now, when generating the CA Pay Data using the Build EEO-1 & Pay Data form, if under the Build Options, the Employee Filter field is set to “Paid more than $0 during the reporting period”, the system correctly displays Y for California for the employee only if the employee has CA SUTA for the current reporting period.
CMP-3101 Previously, the Daily Tax Export download did not display the Subject Wages, QTD Wages, QTD Subject Wages, QTD Taxable Wages, QTD Tax Amount, YTD Wages, YTD Subject Wages, YTD Taxable Wages and YTD Tax Amount for school district tax. Now, the Daily Tax Export download correctly displays the Subject Wages, QTD Wages, QTD Subject Wages, QTD Taxable Wages, QTD Tax Amount, YTD Wages, YTD Subject Wages, YTD Taxable Wages and YTD Tax Amount for school district tax.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/QR202406/CMP-Fixes%20Jun-2024%20QR.htm Path: CMP/Release-Notes/Fixes/2024/QR202406/CMP-Fixes Jun-2024 QR.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the June 2024 quarterly release.

JIRA Number Issue Summary Resolution
CMP-5644 Previously, when the employee tax for the Paid Family and Medical Leave tax for the state of Colorado (tax code 06-40) or Oregon (tax code 38-40) or Washington (48-40) was redirected to a different tax code (say 06-22) for Colorado or (say 38-22) for Oregon or (say 48-22) for Washington, the taxable wage limit was not honored after the tax limit was met. Now, when the employee tax for the Paid Family and Medical Leave tax for the state of Colorado or Oregon or Washington is redirected to tax code ending with -22, the taxable wage limit is honored after the tax limit is met. > Note: Note: Resolution to support all redirect tax codes is currently in progress and will be released as soon as possible.
CMP-5638 Previously, the system did not always correctly calculated the Alabama overtime exempt earnings amount when an employee had worked over 40 hours and multiple pay codes were used. Now, when using multiple pay codes for regular rate over 40 hours, the exempt amounts will calculate a blended rate.
CMP-4939 Previously, if an employee was enrolled in a benefit plan having Medical class that was used for a plan that was not a medical plan such as accident, the system incorrectly calculated the taxable wages for Modified Business Tax (tax code 29-41) for the state of Nevada. Now, the system correctly calculates the NV MBT 29-41 taxable wages as gross wages less employer contributions to pretax deductions (medical, dental, vision). Any benefit plans with a class of medical that are not for a medical plan and flagged as “Do Not Include in ACA Reporting” will not be included in the calculation.
CMP-3387 CMP-5592 Previously, on the Tax tab of the Employee Details form, when an employee under the Federal Tax Filing section had a value in the Other Income field and a large Voluntary Deduction or Retirement Flat amount in the Recurring Deductions form, the system presented a payroll error and the payroll would not process. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/QR202409/CMP-Fixes%20Sep-2024.htm Path: CMP/Release-Notes/Fixes/2024/QR202409/CMP-Fixes Sep-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the September 2024 quarterly release.

JIRA Number Issue Summary Resolution
CMP-5908 Previously, for SC SUTA Quarterly Export, positions 320-321 in the RE record did not display the two-digit last month of the quarter. Now, this is fixed.
CMP-5866 Previously, when an employee was working for two clients with the same non-CPEO employer, and had additional medicare wages in one of the clients but not the other, the Quarterly Tax Summary displayed Additional Medicare wages and tax for the client without T2 Medicare. Additionally, a credit for the T2 Medicare tax was shown in the ‘Adjustment for fraction of cents’. Now, this is fixed.
CMP-5860 Previously, any change made to the Client Details form would uncheck the Enable Remote Verification for this Location field under Other Parameters section on the Worksite Locations form for the client. This is resolved. Now only if you uncheck the Enable E-Verification? field in the Process Controls section under the Control tab of the Client Details form, then it will uncheck the Enable Remote Verification for this Location field under the Other Parameters section on the Worksite Locations form for the client.
CMP-5270 Previously, when the Additional Medicare Calc Method field was checked on the MasterTax Interface Parameters form, if an employee had additional medicare wages and a negative tax adjustment was entered, the 941 Quarterly Report did not update line 5d (Taxable wages and tips subject to Additional Medicare Tax). Now, this is fixed.
CMP-5019 Previously, when and employee worked for two clients under the same employer with Additional Medicare Calc Method selected on the MasterTax Interface Parameters form, and had over $200k in taxable wages under only one client, the Quarterly Tax Export incorrectly showed a negative value for 00-11ADD that did not have T2 Mdicare. Now, this is fixed.
CMP-2964 Previously, on the Quarterly Tax Summary form, the additional Medicare Tier 2 tax amount incorrectly populated to the Adjustment for fraction of cents field instead of the Wages subject to additional Medicare tax or the Calculate additional Medicare tax due fields. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2024/QR202411/CMP-Fixes%20Nov-2024.htm Path: CMP/Release-Notes/Fixes/2024/QR202411/CMP-Fixes Nov-2024.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the November 2024 quarterly release.

JIRA Number Issue Summary Resolution
CMP-6099 Previously, the system incorrectly reported taxable wages entered for Third Party Sick Pay and Tax Adjustments in T2 Medicare for employees with less than $200K in taxable wages. Now, the system does not report taxable wages entered for Third Party Sick Pay and Tax Adjustments in T2 Medicare for employees with less than $200K in taxable wages.
CMP-5656 Previously, when a client did not have a client level PTO Benefit Plan, the Global PTO Auto Enroll Payroll Batch Report did not include the employees for the client even though the Global PTO Plan Auto Enroll & Accrue field is selected for that client under the Other tab on the Client Details form. Now, even if a client does not have any client level PTO Benefit Plan, the Global PTO Auto Enroll Payroll Batch Report will include the employees for the client when the Global PTO Plan Auto Enroll & Accrue field is selected for that client under the Other tab on the Client Details form.
CMP-5529 Previously, when all the report parameters like Gender, Ethnicity and Employee Address (two lines) were selected for inclusion on the Certified Payroll Report Format Parameters form, then the CSV version of the Certified Payroll Report did not display the check number for that payroll for the employee. Now, this is fixed.
CMP-5420 Previously, on the Create Employee W-2 Forms form, under the Options section, if Suppress Third Party Sick Pay field was selected for an employee, and any Taxable Sick Pay adjustment was entered for that employee, but no income tax was withheld on the Third Party Sick Pay Adjustment form, then the Taxable Sick Pay amount did not get suppressed on the employee Form W-2. Now, this is fixed.
CMP-5391 Previously, both for SBEA and non-SBEA clients, the Employee W-2 Box Report did not display the Box c Employer Name. Now, this is fixed.
CMP-5323 Previously, when an S-Corp employee changed employers within a selected benefit tax adjustment year, the system did not account for vouchers under the previous employers during that benefit tax adjustment year. Now, this is fixed, and the system will calculate adjustments based on all vouchers related to all employers for the employee during that benefit tax adjustment year.
CMP-5317 Previously, on the State Rules form, if SUTA is PEO Based and Client SUTA Report Only was selected, then the MasterTax PTS did not report the 210 CR record unless a Client SUTA rate was added. Now, on the State Rules form, if SUTA is PEO Based and Client SUTA Report Only is selected, then the MasterTax PTS will report the 210 CR record even if a Client SUTA rate was not added since the accrual rate follows the Employer Tax Rate.
CMP-5259 Previously, for both SBEA and non-SBEA employers in the state of Nevada, the MasterTax RTS file under 601 record did not report the tips under tax code 29-24 in position 100-113. Now, this is fixed.
CMP-5075 Previously, when running the 941 Quarterly Report for a client with multiple employers, the report did not produce results based on the employer ID entered. Now, this is fixed.
CMP-3506 Previously, when an employee had a Form W-2 that was created manually, then the physical Form W-2 did not print the employee name in Box E as required. Now, this is fixed.

Other Fixes

The following are some other issues that we’ve fixed in the November 2024 quarterly release.

Jira Number Issue Summary Resolution
WSP-945 WSP-849 Previously, the EES W-2 Export for any year incorrectly reported the Common Pay Agent set for the current year, instead of the Common Pay Agent set for the reporting year. Now, this is fixed.
WSP-941 Previously, on the 1094C Report Download form, when you hovered over the checkbox beside the Generate All Clients field, the screen incorrectly displayed a No symbol. Now, this is fixed.
WSP-867 Previously, on the Create Employee W-2 Forms form, PrismHR did not generate an error report if an employee had a negative OASDI tax (tax code 00-12) for that tax year. Now, this is fixed.
WSP-866 Previously, the BDS/SOLV W-2 Export for any year incorrectly reported the Common Pay Agent set for the current year, instead of the Common Pay Agent set for the reporting year. Now, this is fixed.
WSP-851 Previously, the EES Virgin Islands W-2 Export for any year incorrectly reported the Common Pay Agent set for the current year, instead of the Common Pay Agent set for the reporting year. Now, this is fixed.
WSP-850 Previously, the EES Puerto Rico W-2 Export for any year incorrectly reported the Common Pay Agent set for the current year, instead of the Common Pay Agent set for the reporting year. Now, this is fixed.
WSP-783 Previously, the W-2C Box Report in PrismHR did not populate any data if an employee had a Form W-2c in the system for that tax year. Now, this is fixed.
WSP-709 Previously, when the Custom Feature Code ALLOW999SSNS was not enabled, then on the New Hire Form and for the New Employee Imports form, if you entered an SSN or an ITIN having any number between 50-65 on the 4th and 5th positions, you received an error. Now, this is fixed.
WSP-622 Previously, when income tax withholding was enabled for a 1099 contractor both on the Client Details form under the Tax tab, and also on the State Rules form under the State Tax Parameters section, and taxes were suppressed on the Client Details form and/or on the Tax Calculation Overrides form for the 1099 contractor, PrismHR still did not suppress either the federal or the individual state income tax. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/MR202501/CMP-Fixes%20Jan-2025.htm Path: CMP/Release-Notes/Fixes/2025/MR202501/CMP-Fixes Jan-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the January 2025 monthly release.

JIRA Number Issue Summary Resolution
CMP-6258 Previously, when an employee had AL OT Exempt wages and a zero Exempt Pay for a different state income tax, then on the Form W-2 for the employee, Box 14 was blank. Now, this is fixed.
CMP-6232 Previously, the Work Out of State Flag for PA changed after a tax deduction was processed resulting in incorrect tax files for MasterTax RTS. Now, this is fixed.
CMP-6191 Previously, when a tax adjustment was created for an ASO client for an employee-paid tax code with the Calculate/Report at Client Level (PEO’s Only) field checked on the Tax Deductions form, the tax was incorrectly reported with a ‘C’ Tax Basis on the employee payroll voucher. Now, when a tax adjustment is created for an ASO client for an employee-paid tax code with the Calculate/Report at Client Level (PEO’s Only) field checked on the Tax Deductions form, the tax is correctly reported with a ‘P’ Tax Basis on the employee payroll voucher.
CMP-6181 Previously, if for an employee a large amount was entered on the Other Income field under the Tax tab on the Employee Details form, the payroll calculation for that employee failed with an incorrect error message stating Insufficient cash earnings to pay taxes. Now, if for an employee a large amount was entered on the Other Income field under the Tax tab on the Employee Details form, the payroll process reduces the federal income tax withholding on the payroll to the precise amount necessary to reduce the employee’s net pay to “0” and processes the payroll for that employee without error.
CMP-6173 Previously, the Employer Quarterly SUTA Tax Export file for Colorado was missing the 0 or 1 indicator in the S records, positions 212, 213, and 214 indicating if the employee worked in a pay period that included the 12th of the applicable month during the quarter. Now, the Employer Quarterly SUTA Tax Export file for Colorado will report a 0 or 1 in the S records, positions 212, 213, and 214 indicating if the employee worked in a pay period that included the 12th of the applicable month during the quarter.
CMP-6079 Previously, when a client had payrolls under more than one employer, and you had allowed a particular client access to the Quarterly Tax Summary form, then it only reported the wages under the Employer ID assigned to that particular client. Now, when a client has payrolls under more than one employer, the Quarterly Tax Summary form will display the totals for the client as a whole including all Employer IDs.
CMP-5674 Previously, the Record ID in the ACA transmission file for each transmission was not in sync with the corresponding Federal Transmission Information on the Edit Employee 1095 Form for that employee. Now, this is fixed.
CMP-4147 Previously, when the employee portion of WA PFML (tax code 48-40) was redirected to the employer, the MasterTax RTS file did not accurately report the Weeks Worked and Hours Worked. Now, this fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/MR202502/CMP-Fixes%20Feb-2025.htm Path: CMP/Release-Notes/Fixes/2025/MR202502/CMP-Fixes Feb-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the February 2025 monthly release.

JIRA Number Issue Summary Resolution
CMP-6357 Previously, for the state of Ohio, the EFW2 had multiple RS records per employee owing to SIT and others even when the employee did not reside in a taxing school district. Now, for the state of Ohio, the EFW2 will only include one RS record per employee unless multiple school districts are reported.
CMP-6325 Previously, when an employee had CO, OR, or WA PFML (tax codes 06-40, 38-40 or 48-40), redirected to tax codes 06-22, 38-22, or 48-22 for a private plan the tax amount was incorrectly populated in Box 14 on the Form W-2 for both SBEA or non-SBEA clients. Now, tax codes 06-22, 38-22, and 48-22 will not be reported in Box 14 on the Form W-2 for employees for both SBEA or non-SBEA clients.
CMP-6324 Previously, when using a Common Pay Agent, the RE record on the EFW2 files for federal and states was incorrect. The EIN in positions 8-16 was not omitting the hyphen and positions 17-25 was not blank. Now, when using a Common Pay Agent, the RE record on the EFW2 files for federal and states is incorrect. The EIN in positions 8-16 will omit the hyphen and positions 17-25 is blank.
CMP-6320 Previously, on the Form W-2 for employees from Campbell County in the state of Kentucky, the: - Campbell County General Occupational License Fee (Tax ID 503), tax code 18037-44 did not report in the Box 18-20 AND - Senior Citizen Occupational License Fee (Tax ID - 511) tax code 18037-32 reported the tax withheld amount only in Box 14 instead of Box 18-20 Now, on the Form W-2 for employees from Campbell County in the state of Kentucky, both the following correctly report in Box-18-20: - Campbell County General Occupational License Fee (Tax ID 503), tax code 18037-44 - Senior Citizen Occupational License Fee (Tax ID - 511) tax code 18037-32

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/QR202503/CMP-Fixes%20Mar-2025.htm Path: CMP/Release-Notes/Fixes/2025/QR202503/CMP-Fixes Mar-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the March 2025 quarterly release.

JIRA Number Issue Summary Resolution
CMP-6453 Previously, in some scenarios, for the state of Iowa, the system was not calculating the income tax correctly. Now, this is fixed.
CMP-6404 Previously, for the state of Maryland, the EFW2 RV record positions 197-208 from the second record onwards were overstated as it reported the running total of the employers’ tax due amount instead of the tax due amount for that employer only which that line corresponded to. Now, this is fixed.
CMP-6336 Previously, the EES W-2 Export did not apply the prior year record for reporting Common Pay Agent which resulted in the Form W-2 PDF not matching the EES download for current tax year if there was a change in the Common Pay Agent data for the current year. Now, this is fixed.
CMP-6270 Previously, when the employer paid NY SDI tax code 33-25 was suppressed using the Tax tab on Client Details form, the system incorrectly also suppressed the employee paid NY SDI tax code 33-21 even though it was set up to calculate. Now, this is fixed.
CMP-5822 Previously, the system did not allow local tax code 18037-44 to report at the client level (Tax Basis of C) with any current overrides. Now, this is fixed.
CMP-5669 Previously, in some scenarios the system was not reporting the New York Metropolitan Commuter Transportation Mobility Tax correctly. Now, this is fixed.
CMP-5421 Previously, the EEO-1 Export Data included transferred employees of the client who were not active for the client during the reporting period. Now, this is fixed. This fix will be applied when the custom feature code EEOENHANCE is added to the System Parameters form.
CMP-4727 Previously, when for the state of CO, DE, ME, OR or WA an override rate for PFML was entered either on the Employer Tax Rates (SUTA) or the State Tax Rates (SUTA) form, the State Misc3 Rate (Employer contribution) and State Misc 3 Employee Rate (employee contribution) did not populate correctly in the PTS file on the 210 records in positions 71-76. Now, this is fixed.
CMP-2014 Previously, a negative garnishment amount could occur when the Student Loan Type was selected as Apply Federal Limits Minus Medical with percentage was applied to a Student Loan Garnishment. Now, a Student Loan Garnishment will not have a negative deduction amount.
CMP-412 Previously, on the Employee Details form and the New Hire form, a Native American Tribal document required an expiration date. Now, it does not.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/R_202504/CMP-Fixes%20Apr-2025.htm Path: CMP/Release-Notes/Fixes/2025/R_202504/CMP-Fixes Apr-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the April 2025 release.

JIRA Number Issue Summary Resolution
CMP-6487 Previously, when a Union was associated with certified payroll, in the Form WH-347 and Certified Payroll Report, the system did not accurately calculate the Project Totals. Additionally, the Project Totals were miscalculated when multiple positions with unions were included on the same payroll voucher. Now, when using Position based Unions with certified payroll reporting, the Project Total reflects all cash pay codes and fringe benefit pay codes as part of the Project Total pay for that Project and Position combination. The Project Total separates out the pay based on the different Project and Position combinations.
CMP-6478 Previously, using the Create Employee W-2 Forms form, when you ran the build Form W-2 process for an employee, the Form W-2 build process deleted all existing Form W-2s built for all employees for that employer. Now, using the Create Employee W-2 Forms form, when you run the build Form W-2 process for selected employees, the Form W-2 build process will delete the existing Form W-2s which were built for only those selected employees for that employer. > Note: Note: This was released as a hotfix on March 19, 2025.
CMP-6405 Previously, when an employee completed their LA state tax form through Onboarding or Employee Portal, the elections were not displaying under the Tax tab on the Employee Details form for the employee. Now, this is resolved.
CMP-5960 Previously, the CSV output of the Certified Payroll Report displayed only four Fringe Pay Codes even if more than four Fringe Pay Codes were displayed on the PDF output. Now, the CSV output of the Certified Payroll Report displays the same number of Fringe Pay Codes as displayed on the PDF output.
CMP-5312 CMP-6477 Previously, when an employee had a child support garnishment and a pretax deduction exceeding the gross pay, the system did not follow the Maximum Percent of Disposable Pay calculation for that state as per the State Garnishment Rules form. Now, when an employee has a child support garnishment and a pretax deduction exceeding the gross pay, the system does not stop payroll but provides a soft warning stating Warning: has a garnishment that should be reviewed. There are insufficient cash earnings to calculate all deductions on Voucher# . An adjustment may be needed.
CMP-5031 Previously, when an employee had a state tax levy garnishment set as a flat amount, during payroll calculation, the system did not follow the limits set on the State Tax Levy Maximum Percent of Gross Pay/Disposable Pay field on the State Garnishment Rules form for that state. Now, this is fixed.
CMP-3507 Previously, for both SBEA and non-SBEA clients, the Form W-2c listed a correction to the locality when two localities with the same name appeared on the Form W-2 even if a change was not made to the locality. Now, for both SBEA and non-SBEA clients, the Form W-2c does not list a correction to the locality when two localities with the same name appear on the Form W-2 unless a change was made to the locality.

Other Fixes

The following are some other issues that we’ve fixed in the April 2025 release.

Jira Number Issue Summary Resolution
WSP-1687 Previously, you were able to access the Change Reason History form from the navigation menus, which did not allow them to indicate the client/state/employer record in the displayed form. Now, the Change Reason History form no longer displays on the navigation menus, so you can only access this form by selecting it on the Actions menu in the Client Details, Employer Details, and State Rules forms, where the client/employer/state record already displays.
WSP-1752 Previously, the Change Reason History form could be added to Favorites which was incorrect. Now, the Change Reason History form cannot be added to Favorites.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/R_202505/CMP-Fixes%20May-2025.htm Path: CMP/Release-Notes/Fixes/2025/R_202505/CMP-Fixes May-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the monthly release of May 2025.

JIRA Number Issue Summary Resolution
CMP-6593 Previously, if the Submitter ID did not include an employer exclusion, the EFW2C file would not create. Now, this is fixed. You can now run the EFW2C download using a submitter with no employer exclusion list.
CMP-6540 Previously, when the Form W2C only had a change relating to the state or local values, a blank record for that employee appeared on the EFW2C download. This caused the total record to be wrong and employer information to be repeated in the file. Now, this is fixed.
CMP-6472 Previously, when the Certified Payroll Report was generated for multiple projects, the Project OT rate did not display correctly for all the projects. Now, the Project OT rate displayed on the Certified Payroll Reports (both PDF and CSV formats) will reflect the correct Project OT rate from the corresponding Certified project, ensuring no Project OT rates from other projects are included.
CMP-6468 Previously, for the state of Iowa (tax code 61-24) that consider the Employer HSA match as taxable for SUTA, the taxable billing did not reflect the employer HSA contribution. Now, on employee payroll vouchers, when the employer HSA contributions are taxable, both the taxable accrued and the taxable billing sections reflect the employer HSA contributions in the taxable earnings and the tax amounts.
CMP-6454 Previously, when a pay group was deleted that had payroll activity in the same year, then the annual average number of employees in the OSHA300A report was inflated. Now, this has been fixed. However, clients should not remove the pay group as it would cause an invalid calculation for the total employees.
CMP-6434 Previously, the net wages on the XML version of the Certified Payroll Report did not match its PDF version when an employee was paid with a Fringe Pay Code across two projects. Now, this is fixed.
CMP-6384 Previously, when using a pay code with the weighted average setup to be used for a pay period, if there were no other payroll hours other than the regular hours of pay to include in the weighted average, then the system incorrectly calculated the pay rate as zero. Now, if an employee is paid with the weighted average calculation method for a pay code and has no other payroll hours, then the pay rate will default to the employee’s regular hourly pay rate.
CMP-6294 Previously, for an employee working in a location that triggers GLOBAL PTO accrual, when an FLSA ruleset calculated HALF time or blended overtime rates, the GLOBAL PTO accrual did not pick up those hours. Now, for an employee working in a location that triggers GLOBAL PTO accrual, all pay codes that exist on the GLOBAL PTO Benefit plan (Included pay codes) are included in the accrual calculation, with or without FLSA ruleset calculations.
CMP-6243 Previously, the MasterTax RTS 601 record for CT0000-040 (CT PFML) positions 100 - 113 reported the Year-To-Date (YTD) earnings subject to CT PFML for the employee (EE) including earnings from subsequent quarters which was incorrect. Now, the MasterTax RTS 601 record for CT0000-040 (CT PFML) positions 100 - 113 reports the Year-To-Date (YTD) earnings subject to CT PFML for the employee (EE) as of the conclusion of the reporting quarter. It is important to note that this record will not account for any earnings from subsequent quarters.
CMP-6195 Previously, for both SBEA and non-SBEA employers in the state of Nevada, the MasterTax RTS file under 601 record did not report the tips under tax code 29-24 in position 100-113 for an ASO or any company with ER-reported NV SUTA. Now, this is fixed.
CMP-5286 Previously, even for an employee living in the state of New York, the tax code XXXXX-37 for NY Metro Commuter tax did not have a C tax basis when the Tax Authority was set to report on the Client. Now, this is fixed.
STEP-258 Previously, when setting up a Worksite Location for either Eugene or Portland OR, the system did not automatically set the OR Transit Tax field to the respective district. The system did not update the OR Transit Tax field at all. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/R_202506/CMP-Fixes%20Jun-2025.htm Path: CMP/Release-Notes/Fixes/2025/R_202506/CMP-Fixes Jun-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the release of 2025 June.

JIRA Number Issue Summary Resolution
CMP-6587 Previously, in the RTS 500 records, for Maine PFML, the system was reporting Gross Wages instead of Gross Wages excluding sheltered amounts. Also, the system was not reporting any wages on the 601 record for ME0000-014. Now, this is fixed. Maine PFML records on the RTS have been updated to report: - 500 records, ME0000-014 and 20-41, positions 123 - 136 QTD Gross Taxable Wages (Gross - Sheltered) - 500 records, ME0000-014 and 20-41, positions 137 - 150 YTD Gross Taxable Wages (Gross - Sheltered) - 601 records, ME0000-014, positions 72 - 85 QTD Gross Taxable Wages (Gross - Sheltered)

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/R_202507/CMP-Fixes%20Jul-2025.htm Path: CMP/Release-Notes/Fixes/2025/R_202507/CMP-Fixes Jul-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the 2025 July release.

JIRA Number Issue Summary Resolution
CMP-6650 Previously, for both SBEA and non-SBEA clients, the Quarterly JSON PHR Tax files were missing the YTDtoDate object. Now, this is fixed. The YTDtoDate object will report the total for all employee records in the following attributes: - TotalGrossWages - Total Tax - Total Taxable - TotalSubjectWages

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/R_202508/CMP-Fixes%20Aug-2025.htm Path: CMP/Release-Notes/Fixes/2025/R_202508/CMP-Fixes Aug-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the 2025 August release.

JIRA Number Issue Summary Resolution
CMP-6486 Previously, in some scenarios, for an employee who is a resident of Pennsylvania and working in multiple locations, the system at times caused multiple City Withholding Tax records (tax code -31) for the employee resulting in negative taxable earnings. Now, this is fixed.
RRT-6458 Previously, 1099 contractors were incorrectly included in the ACA Large Employer Test Report. Now, 1099 contractors are excluded from the ACA Large Employer Test Report.
CMP-6483 Previously, for the state of Wyoming, when SUTA is PEO Based and marked as Client SUTA Report Only on the State Rules form, PrismHR incorrectly displayed N instead of Y for Client Reporting Only for the employer tax codes 51-26 (WY Employment Support Fund) and 51-28 (WY Workforce Development) when the tax deduction codes 51-26 and 51-28 are marked as SUTA components. Now, this is fixed.
CMP-6358 Previously, when creating W2-C forms, the system would not create a W2C if an employee record was included in an existing EFW2C export that was still in progress and did not provide any error. Now, an error will appear during the create w2c process if an employee record is included in an existing EFW2C export that is in progress.
CMP-5941 Previously, for an ASO client, on the Tax Deductions form if a redirected tax code was set to Calculate/Report at Client level (PEO’s Only), then that redirected tax code incorrectly displayed a Tax Basis of C instead of P on the employee payroll voucher. Now, this is fixed.
CMP-4626 Previously, when recalculating overtime on a special batch with commission and/or bonus payments, the system incorrectly calculated overtime payment on pay codes set up to be excluded from payroll overtime recalculation. Now, this is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/R_202509/CMP-Fixes%20Sep-2025.htm Path: CMP/Release-Notes/Fixes/2025/R_202509/CMP-Fixes Sep-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the 2025 September release.

JIRA Number Issue Summary Resolution
CMP-6679 Previously, for the state of Maine, the system was incorrectly reporting PFML records on the RTS as follows: - 500 records, ME0000-014 and 20-41, positions 123 - 136 QTD Gross Taxable Wages (Gross - Sheltered) - 500 records, ME0000-014 and 20-41, positions 137 - 150 YTD Gross Taxable Wages (Gross - Sheltered) - 601 records, ME0000-014, positions 72 - 85 QTD Gross Taxable Wages (Gross - Sheltered) Now, this is fixed. Maine PFML records on the RTS have been updated to report: - 500 records, ME0000-014 and 20-41, positions 123 - 136 QTD Gross Taxable wages, Gross Wages - Sheltered wages NOT excluding overlimit wages - 500 records, ME0000-014 and 20-41, positions 137 - 150 YTD Gross Taxable wages, Gross Wages - Sheltered wages NOT excluding overlimit wages - 601 record, ME0000-014, positions 72 - 85 QTD Gross Taxable wages, Gross Wages - Sheltered wages NOT excluding overlimit wages

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Fixes/2025/R_202510/CMP-Fixes%20Oct-2025.htm Path: CMP/Release-Notes/Fixes/2025/R_202510/CMP-Fixes Oct-2025.htm

Fixes

When technical difficulties surface, we try to resolve them right away. The following are recent known issues that we’ve fixed in the 2025 October release.

JIRA Number Issue Summary Resolution
CMP-6858 Previously, when there were no gross wages or taxable wages for the employee, the Periodic Tax JSON Export reported “SubjectWage”: “” which caused payload upload error. Now, when there are no gross wages or taxable wages for the employee, the Periodic Tax JSON Export reports “SubjectWage”: “0.00” instead of the earlier blank, which caused payload upload error.
CMP-6765 Previously, if for an employee a large amount was entered on the Other Income field under the Tax tab on the Employee Details form, the payroll calculation for that employee failed with an incorrect error message stating Insufficient cash earnings to pay taxes. Now, if for an employee a large amount was entered on the Other Income field under the Tax tab on the Employee Details form, the payroll process reduces the federal income tax withholding on the payroll to the precise amount necessary to reduce the employee’s net pay to “0” and processes the payroll for that employee without error.
CMP-6700 Previously, if the Include Pennsylvania Work State Flag (Y/N) field on the MasterTax Interface Parameters form was used, then in some cases, the Mastertax RTS over-reported the PA EIT wages for an employee when wages for the current quarter covered pay periods in prior quarters. Now, this is resolved. The MasterTax RTS will only report the PA EIT wages for the current quarter.
CMP-6280 Previously, if an employee worked in multiple worksite locations both in Eugene, Oregon, and outside, the system did not always calculate the Community Safety Payroll Tax (CSPT) for Eugene, Oregon for the employee and the employer. Now, this is resolved.
CMP-6015 Previously, when entering Payroll / Change / Transfer Tax Basis, some SUTA minor tax codes (XX-21/-26) set as a SUTA component on the Tax Deductions form were incorrectly written in the Employer Tax Register instead of the Client Tax Register when a Client report override was on the Client Details Tax form for that state. Now, when entering a Payroll / Change / Transfer Tax Basis for SUTA minor tax codes (XX-21/-26) set as a SUTA component on the Tax Deductions form will write to the tax register corresponding to the report basis for the corresponding State SUTA.
CMP-4455 Previously, when an employee was working in multiple locations in the state of Pennsylvania, the system incorrectly calculated half of the total Local Service Tax as provided in Vertex for the employee’s home location. Now, when an employee is working in multiple locations in the state of Pennsylvania, the system correctly calculates the total Local Service Tax as provided in Vertex for the employee’s home location.

========================================================================

Known Issue

Source: https://tech-docs.prismhr.com/SP_help/Content/CMP/Release-Notes/Known-Issues/2025/CMP-Known%20Issue%20Mar-2025.htm Path: CMP/Release-Notes/Known-Issues/2025/CMP-Known Issue Mar-2025.htm

Known Issue

The following is a known issue which will be addressed in the 2025 April release.

Change Reason History form

The Change Reason History form should only be accessed from the

[Image: screenshot]

menu of the individual form for which you want to view the reason for change. For example if you want to view the reason for change for the Client Details form, then use the

[Image: screenshot]

menu of the Client Details form.

If you access the form as shown below, no change reason history will display. This option will be removed in the 2025 April release.

[Image: screenshot]

JIRA # WSP-203

========================================================================

File Size Limit Increased to 25 Mb

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/MR_202401/Doc_File_Size.htm Path: DM/Release-Notes/Enhancements/2024/MR_202401/Doc_File_Size.htm

File Size Limit Increased to 25 Mb

The file size for an single document upload in Document Management has been increased to 25 Mb.

Users can now store longer forms and more complex records to their databases.

JIRA # DM-946

========================================================================

Advanced Search by Client ID

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/MR_202401/Search_By_Client_ID.htm Path: DM/Release-Notes/Enhancements/2024/MR_202401/Search_By_Client_ID.htm

Advanced Search by Client ID

When a user performs a search on the Advanced Search form using the Select Companies field, they can now enter a Client ID to display the company with that ID number. In addition, users can enter a partial ID number to display all companies with matching Client IDs.

JIRA # DM-925

========================================================================

Search for Employees by First Name

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/MR_202401/Search_for_Employees_by_Name.htm Path: DM/Release-Notes/Enhancements/2024/MR_202401/Search_for_Employees_by_Name.htm

Search for Employees by First Name

Managers can now search for employees by their first names on the Document Management form. The search field has been updated to Search Name to indicate the change.

In addition, names now display in alphabetical order in the Search Name field.

JIRA # DM-921

========================================================================

Upload Documents Using the Mastertax Bulk Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/QR_202403/MasterTaxBulkInput.htm Path: DM/Release-Notes/Enhancements/2024/QR_202403/MasterTaxBulkInput.htm

Upload Documents Using the Mastertax Bulk Import Tool

Users can now upload multiple Mastertax documents at once using the Bulk Import Tool. When documents are uploaded using this tool, formatted Mastertax Zip files can be processed in a batch, automatically inspected for errors, and reprocessed or rolled back from a single form.

What you Need

Before you begin, make sure you have:

Correct Zip File Format

For the Bulk Import tool to read the documents in the Zip file correctly, the files must conform to certain naming conventions. Mastertax should already deliver the Zip file in the format below.

The name of the Zip file does not affect the upload, but the name will be used for the Description field for all the documents imported in that upload. For best practices, you should give the Zip file a name that describes the documents, such as “Q1 2024 Mastertax Upload” for first-quarter 2024 tax documents.

The naming convention of the tax files is very important for the files to be read correctly. Mastertax files should be named according to the following rules:

For example, if the Client ID is 3245, the tax file should look like this: “Q12024_C3245_mastertax.pdf”.

How to Access the Bulk Import Tool

You can access the Bulk Import tool through Document Management.

To access the Bulk Import tool:

  1. Click [Image: screenshot] (Back Office).

  2. From Client|Change select Manage Documents. The Manage Documents form displays.

  3. Click the [Image: screenshot] (Bulk Import) icon. The Bulk Import form displays.

The Bulk Import Form

The Bulk Import form displays the status of past bulk imports, and can be used to add a new bulk import.

[Image: screenshot]

The following fields display on this form:

How to Perform a Bulk Import

To perform a bulk import:

  1. On the Bulk Import form, click Add Import. The New Bulk Import form displays.

  2. Enter a name for the import in the Bulk Import Name field. This name is used as a description for the import in the system.

  3. Select a category for the import in the Target Category field. The field only displays categories that you have permission to access.

  4. Click Select Zip File. A file selection form displays.

  5. Select the Zip file that has been prepared according to the formatting standards listed above.

  6. Click Start Bulk Import.

The bulk import begins processing, and the Bulk Import form displays, where you can review the status of the import.

How to Review and Reprocess Errors on a Bulk Import

When you run a bulk import, the system displays the total number of files to be imported, the number successfully processed, and the number of files that were not imported due to errors.

Note: Note: Errors due to mistakes in formatting, unsupported file types, or files that contain 0 bytes cannot be fixed directly using the reprocessing method. To fix these errors, you will need to make changes to the documents on the Zip file and redo the import.

To review errors on a bulk import:

  1. On the Bulk Import form, select the import that has processing errors.

  2. Select the link in the Errors field.

The Import Errors form displays.

Each file with a processing error displays on this form. The File Name field displays each file, and the Exception field displays the corresponding error message.

Bulk import errors can be fixed according to the type of error:

To reprocess a bulk import:

  1. On the Bulk Import form, select the import that has processing errors.

  2. Click Reprocess Errors.

The system attempts to reprocess files that returned errors. Any errors which remain after reprocessing are likely due to file formatting, file type, or permissions issues, and can be reviewed on the Import Errors form.

How to Roll Back a Bulk Import

If you need to undo a bulk import, you can roll back the documents.

To roll back a bulk import:

  1. On the Bulk Import form, select Rollback.

The Confirm Rollback button displays.

  1. Select Confirm Rollback.

The rollback commences, and all processed files from the import are removed from the system.

JIRA # DM-774, DM-776, DM-939, DM-940, DM-941, DM-942, DM-951, DM-972, DM-977

========================================================================

Full Support for Special Characters in Document Names

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/QR_202403/Special_Characters_In_Doc_Names.htm Path: DM/Release-Notes/Enhancements/2024/QR_202403/Special_Characters_In_Doc_Names.htm

Full Support for Special Characters in Document Names

The Document Management system now supports the full range of special characters in the UTF-8 standard for document names and descriptions. Document names and descriptions with special characters now display properly for both desktop and mobile devices.

JIRA # DM-993

========================================================================

Enhancements to Document Storage Dashboard Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/QR_202403/Storage_Enhancements.htm Path: DM/Release-Notes/Enhancements/2024/QR_202403/Storage_Enhancements.htm

Enhancements to Document Storage Dashboard Performance

Improvements have been applied to the Document Storage Dashboard to improve loading times, especially for clients with a large number of documents to review.

JIRA # DM-690

========================================================================

Enhancements to Document Storage Dashboard

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/QR_202406/2_TB_Storage_Limit.htm Path: DM/Release-Notes/Enhancements/2024/QR_202406/2_TB_Storage_Limit.htm

Enhancements to Document Storage Dashboard

The Document Storage Dashboard has been enhanced to properly display the 2 TB limit allotted to most clients. In addition, the dashboard will dynamically change if the client has purchased additional storage space.

JIRA # DM-1019

========================================================================

Enhancements to Advanced Search for Clients and Employees

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/QR_202406/Active_Companies_By_Default.htm Path: DM/Release-Notes/Enhancements/2024/QR_202406/Active_Companies_By_Default.htm

Enhancements to Advanced Search for Clients and Employees

When a manager uses the Advanced Search form to search for clients or employees can now toggle between active and inactive clients or employees. By default, searches only apply to active records, improving the performance of the search.

The new Active Companies field can be used to switch between active companies and inactive companies.

The new Active Employees field can be used to switch between active, terminated, and on-leave employees.

Using these new fields, managers can perform searches for active records more quickly while retaining the ability to search for inactive records when needed.

JIRA # DM-1018

========================================================================

Bulk Downloads in Document Management

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/QR_202409/Bulk_Download_Tool.htm Path: DM/Release-Notes/Enhancements/2024/QR_202409/Bulk_Download_Tool.htm

Bulk Downloads in Document Management

Managers and Service Providers can now download documents in bulk using the Bulk Download process in Document Management. To download a large number of files, users can perform a bulk download to compress selected documents into a ZIP file, which can then be downloaded at any time from the new Bulk Download form.

To access bulk downloads, access the Manage Documents form. Select multiple documents and click the

[Image: screenshot]

(Download) icon to display the Confirm Download prompt, which informs the user that this download may take a significant time and offers the option to run the process in the background. Click Run in Background to perform the download and exit the prompt. The download progress displays on the

[Image: screenshot]

(Bulk Download) icon, and the user can continue performing other duties while the download processes. Once the download is complete, the Bulk Download icon displays a checkmark.

[Image: screenshot]

Click the

[Image: screenshot]

(Bulk Download) icon at any time to display the Bulk Downloads form. This form lists all bulk downloads performed by the current user, as well as the status, timestamps, processing percentage, size, errors, and available actions. Users can cancel a download that is currently in progress or click the Download button to download documents. The download link can also be shared with other users. In addition, the user can return to the Bulk Documents form at any time to redownload files.

If any errors occur during the download process, the Errors column displays a number as a link. Click this link to download a TSV file with a list of errors that occurred during the download.

Using this new process, managers and service providers can save time downloading large quantities and file sizes of documents and continue with their other duties while the download is processed.

JIRA # DM-999, DM-1002, DM-1003, DM-1005

========================================================================

Documents In Use Cannot Be Deleted

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2024/QR_202409/Documents_In_Use.htm Path: DM/Release-Notes/Enhancements/2024/QR_202409/Documents_In_Use.htm

Documents In Use Cannot Be Deleted

Documents are now protected from deletion while in use by an Employee Portal alert. If a user attempts to delete a document on the Manage Documents form that is in use, an error message now displays to indicate the document cannot currently be deleted and a description of the process currently using the document.

JIRA # DM-1120, DM-1121, DM-1122, DM-1141, DM-1142, DM-1145, DM-1214

========================================================================

Enhancement to Bulk Download Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2025/R202505/Bulk_Download_Performance.htm Path: DM/Release-Notes/Enhancements/2025/R202505/Bulk_Download_Performance.htm

Enhancement to Bulk Download Performance

The Bulk Download process has been enhanced to improve the performance of the download, with specific improvements to the process of creating a ZIP file for a large number of documents. For downloads of significant size, multiple ZIP files will be created to improve download performance.

JIRA # DM-1551, DM-1611

========================================================================

Bulk Import for PrismHR Tax Now Available

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2025/R202505/Bulk_Import_Tax.htm Path: DM/Release-Notes/Enhancements/2025/R202505/Bulk_Import_Tax.htm

Bulk Import for PrismHR Tax Now Available

Employees can now upload PrismHR Tax documents in bulk using the Bulk Import tool in Document Management. To upload these documents, simply select Bulk Import - PrismHR Tax in the Bulk Import Type field.

JIRA # DM-1435

========================================================================

Search for Employees by First Name

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2025/R202507/Search_By_First_Name.htm Path: DM/Release-Notes/Enhancements/2025/R202507/Search_By_First_Name.htm

Search for Employees by First Name

Managers can now search for employees by their first names using Advanced Search in Document Management. When Employee is selected as the search criteria, the Employee Last Name and Employee First Name fields now display.

JIRA # DM-725

========================================================================

Download All From Folder for Worksite Manager

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Enhancements/2025/R202509/Manager_Download_All.htm Path: DM/Release-Notes/Enhancements/2025/R202509/Manager_Download_All.htm

Download All From Folder for Worksite Manager

Worksite Managers and Worksite Trusted Advisors can now select a folder in Document Management and perform a bulk download of all files within that folder. Simply select the checkbox next to the folder name to select the entire folder, then click the Download icon to download all items in the folder.

Note: Note: Security permissions and document permissions are properly enforced for this operation, just like downloading items individually.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2024/DM_Fixes_MR_202401.htm Path: DM/Release-Notes/Fixes/2024/DM_Fixes_MR_202401.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-834 When a user updated a document in Document Management, the Modified Date field did not update to reflect the change. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2024/DM_Fixes_MR_202402.htm Path: DM/Release-Notes/Fixes/2024/DM_Fixes_MR_202402.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-995 In Document Management, the Search Name option’s search capabilities were case sensitive, preventing proper search results. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2024/DM_Fixes_MR_202410.htm Path: DM/Release-Notes/Fixes/2024/DM_Fixes_MR_202410.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1286 When a Worksite Manager accessed the Manage Documents form and attempted to filter results for active or terminated employees, the results were not filtered correctly. The filter worked correctly for Service Providers and Worksite Trusted Advisors. This is fixed.
DM-1324 When a user attempted to upload a document to a form in the Form Library, the filter results in the search window only displayed results from the documents currently displayed on the screen. If more than 100 documents were included in the folder, the user needed to tab to additional pages for the filter to display those results. This is fixed.
DM-1341 On the Manage Documents form, the Employee Status dropdown selection did not display if the company had no active employees. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2024/DM_Fixes_QR_202406.htm Path: DM/Release-Notes/Fixes/2024/DM_Fixes_QR_202406.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-929 When certain forms with signatures were uploaded to Document Management, viewing the document in Document Management did not display the signature. If the employee downloaded the file as a pdf and viewed the file, the signature displayed properly. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2024/DM_Fixes_QR_202411.htm Path: DM/Release-Notes/Fixes/2024/DM_Fixes_QR_202411.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1030 When a user selected the Select All option on the Document Management form’s advanced search feature and downloaded the documents, only the documents currently displayed on the screen were downloaded. This is fixed. Using Select All and downloading the selection now downloads all documents that match the search criteria.
DM-1229 When a user performed an advanced search on the Manage Documents form with filters selected, performing any operation on the results other than uploading a document removed the search results and filter. This is fixed.
DM-1264 When certain Worksite Trusted Advisors with long usernames or working for PEOs with long client names attempted to access the Manage Documents form, an error occurred. This is fixed.
DM-1389 When a user viewed documents for an employee using the Documents action on the Employee Details form, the option to filter the documents did not display. Filtering documents did display if the user accessed documents through the Manage Documents form. This is fixed. Users can now filter documents on both of these forms.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2025/DM_Fixes_MR_202501.htm Path: DM/Release-Notes/Fixes/2025/DM_Fixes_MR_202501.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1412 When a user attempted a bulk download on the Manage Documents form, an error occurred, and the download would not complete successfully. This is fixed.
DM-1453 When a user attempted a bulk import on the Manage Documents form using a mapping file, the import remained stuck in the Processing phase and did not complete successfully. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2025/DM_Fixes_QR_202503.htm Path: DM/Release-Notes/Fixes/2025/DM_Fixes_QR_202503.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1241 When an employee used Advanced Search to locate documents, different versions of the documents displayed as separate items, and selecting one version of the document selected all versions. This is fixed. The Advanced Search now displays only the latest version of the document in the search results.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2025/DM_Fixes_R202507.htm Path: DM/Release-Notes/Fixes/2025/DM_Fixes_R202507.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1744 When users accessed a document in the Document Management system, they could upload new versions of the document even if they did not have the proper permissions. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2025/DM_Fixes_R202508.htm Path: DM/Release-Notes/Fixes/2025/DM_Fixes_R202508.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1803 When a user performed an Advanced Search with a global scope on the Manage Documents form and attempted to download all selected items, the download did not complete and remained in the Analyzing Documents status. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2025/DM_Fixes_R202509.htm Path: DM/Release-Notes/Fixes/2025/DM_Fixes_R202509.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1770 When a user attempted to export documents from a terminated client in Document Management, the download did not complete properly. This is fixed.
EP-9499 When a user accessed Document Management using a mobile device, interactions were restricted by the default size of the frame, preventing proper scrolling. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Fixes/2025/DM_Fixes_R_202505.htm Path: DM/Release-Notes/Fixes/2025/DM_Fixes_R_202505.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
DM-1190 When a Worksite Manager accessed the Bulk Upload tool in Document Management, the Worksite Manager could view upload activity and rollback documents for clients outside of their security permissions. This is fixed. Only the user who performed an upload can now access the Rollback and Reprocess buttons.
DM-1572 When a user included a blank folder in a Bulk Import and attempted to download the files, the download process would sometimes stall. This is fixed.
DM-1590 When a user placed the cursor over the Bulk Import icon on the Manage Document page, the text popup displayed Bulk Upload. This is fixed.
DM-1625 When a user selected one or more documents and a folder in Document Management and attempted a bulk download, the documents were downloaded properly, but the folder was not included. This is fixed.
DM-1630 When a Worksite Manager used Advanced Search in Document Management, used the Select All feature, and attempted to download all selected documents, the documents did not download properly. This is fixed.
DM-1644 When a user downloaded a single document from the Manage Documents form, the file was still downloaded in a ZIP file. This is fixed. Single files are now downloaded directly, without being stored in a ZIP file.
DM-1661 When an employee used Advanced Search to locate documents and attempted to delete all the results using the Select All button, the documents were not properly deleted. Using Select All and delete did work properly without Advanced Search, and documents could be deleted one at a time using Advanced Search. This is fixed. When Select All is used, all documents selected on the current page of results are deleted.

========================================================================

Single Documents Downloaded As ZIP File

Source: https://tech-docs.prismhr.com/SP_help/Content/DM/Release-Notes/Known-Issues/2025/Known_Issues_R202504.htm Path: DM/Release-Notes/Known-Issues/2025/Known_Issues_R202504.htm

Single Documents Downloaded As ZIP File

When a user downloaded a single document from the Manage Documents form, the file is still downloaded in a ZIP file.

This issue will be fixed in an upcoming release.

JIRA # DM-1644

========================================================================

New UEX Version Number

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202401/EP_Version_Number.htm Path: EP/Release-Notes/Enhancements/2024/MR_202401/EP_Version_Number.htm

New UEX Version Number

Users can now view the Employee Portal application version number in the new UEX. Simply click the

[Image: screenshot]

icon on the menu bar, below the Privacy Policy, to display the Application Version form. This form lists the current version of the Employee Portal application.

JIRA # EP-7268

========================================================================

New Hire in EP for Mobile Devices

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202401/New_Hire_Mobile_Device.htm Path: EP/Release-Notes/Enhancements/2024/MR_202401/New_Hire_Mobile_Device.htm

New Hire in EP for Mobile Devices

The New Hire form has been updated for mobile devices. The New Hire form for entering SSNs and DOBs now scales to the resolution of mobile screens, and performance has been improved on this form for mobile devices.

JIRA # EP-7106

========================================================================

Upgrade Terminated Templates to New UEX

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202402/Upgrade_Terminated_Template.htm Path: EP/Release-Notes/Enhancements/2024/MR_202402/Upgrade_Terminated_Template.htm

Upgrade Terminated Templates to New UEX

Service providers can now upgrade a terminated template to the new UEX. By upgrading a terminated template, terminated employees can view the new UEX.

JIRA # EP-7441

========================================================================

Payroll Approval Form in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202403/ADMP_Payroll_Approval.htm Path: EP/Release-Notes/Enhancements/2024/MR_202403/ADMP_Payroll_Approval.htm

Payroll Approval Form in Employee Portal

Managers can now use the Payroll Approval form to view, download, approve, or deny payrolls in Employee Portal. To access this form, select Payroll Approval from the menu while in Manager mode.

[Image: screenshot]

The Payroll Approval form displays a list of payrolls in Pending Client Approval status that are ready for review and approval. This form displays summary information for each payroll, including the number, description, pay date and type, and invoice amount. Using this form, the manager can view details on the payroll, approve it, or deny it.

Select Review Payroll to display the Payroll Summary form, where the manager can review more specific details for the payroll. The Payroll Summary section on this form shows additional information, such as the pay period and deduction period.

[Image: screenshot]

The Payroll Detail tab on the Payroll Summary form displays payment records for individual employees on the payroll. The Unpaid Employee Detail tab shows information about any employees who are marked as unpaid on the payroll. The Invoice tab shows a complete breakdown of payment amounts, taxes, and fees on the invoice. Information from each of these tabs can be downloaded as a CSV file by clicking the Download button.

Managers can approve a payroll by clicking the Approve button for the payroll on the Payroll Approval form, or by displaying the Payroll Summary form for a payroll and clicking the Approve button on the bottom of the screen. Managers can also deny the payroll using the same processes. If a manager denies a payroll, the Deny Payroll # form displays, where the manager must enter a reason to deny the payroll.

Note: Note: A manager only has access to approve or deny a payroll if they have access to all employees on the specific payroll. If the manager does not have access to one or more employees on a payroll, that payroll does not display on the manager’s Payroll Approval form. The employees a manager can access are determined by the Data Security settings for the client.

Note: Note: Invoices on the Invoice tab are sorted according to the sorting rules configured on the Billing tab of the Client Billing form in Prism.

JIRA # ADMP-39, ADMP-40, ADMP-161, ADMP-164, ADMP-170, ADMP-172, ADMP-177, ADMP-181, ADMP-182, ADMP-183, ADMP-195, ADMP-250, ADMP-252, ADMP-255, ADMP-264

========================================================================

Rehire Form in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202403/ADMP_Rehire.htm Path: EP/Release-Notes/Enhancements/2024/MR_202403/ADMP_Rehire.htm

Rehire Form in Employee Portal

Managers can now use the Rehire form to rehire a previously terminated employee and return the employee to a normal work status. To access this form, select an employee on the My Employees form who has the Terminated Status. On the Employee Details form that displays, select HR Actions > Return to Work.

[Image: screenshot]

The Details panel on this form shows the status and the employment type. The History panel displays the history of the employee’s statuses, including the status type, reasons for changes, and effective dates. To rehire an employee, click the Start Rehire Process button. The Proposed Change section displays, where a manager can enter information for an employee’s rehiring.

[Image: screenshot]

The form is divided into sections, much like hiring an employee. In the Proposed Change section, the manager fills in the employee’s new status, employment type, rehire date, and reason, as well as selecting whether to use previous information for deductions, direct deposits, and benefits. In the Employment Details section, the manager fills in the employee’s new location, position, benefit groups, and organizational information such as department, division, or shift. In the Pay Details section, the manager fills in the employee’s new pay group, method, rate, and standard hours. In the Personal Information section, the manager fills in a personal email address, work email address, and mobile phone number for the employee, as well as confirming whether to use previous information for E-Verification, Onboarding, and Benefits Enrollment. If the New Hire process includes custom questions, these questions also appear on the Rehire form.

Once these fields are completed, click Save to return the employee to a work status.> Note: Note: All security for the Rehire form, including viewing an employee’s current pay rate in the form, follows the security set for the Rehire process ID on the User Roles form in Prism.

Using this form, managers can carry out the rehire process completely from Employee Portal to rehire previously terminated employees.

JIRA # ADMP-114, ADMP-124, ADMP-125, ADMP-126, ADMP-128, ADMP-129, ADMP-130, ADMP-131, ADMP-153

========================================================================

Additional Forms Enhanced with New UEX Design

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202403/EP_Additional_UEX_Forms.htm Path: EP/Release-Notes/Enhancements/2024/MR_202403/EP_Additional_UEX_Forms.htm

Additional Forms Enhanced with New UEX Design

Forms already included in Employee Portal have been upgraded to the Unified Employee Experience (UEX). The following forms have been updated in the new UEX:

JIRA # EP-6975, EP-6981, EP-7000, EP-7001, EP-7086, EP-7087, EP-7282, EP-7285, EP-7291

========================================================================

Enhancements to Dependents & Beneficiaries

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202403/EP_Enhancements_To_Dependents.htm Path: EP/Release-Notes/Enhancements/2024/MR_202403/EP_Enhancements_To_Dependents.htm

Enhancements to Dependents & Beneficiaries

The Dependents & Beneficiaries form has been enhanced with new UEX styling and parity with the Onboarding and Benefits Enrollment forms.

This form now utilizes the mandatory fields configured on the New Hire and Dependent Required Fields form in Prism, which is used to configure global or client-level required fields for new hires and dependents.

JIRA # EP-7006

========================================================================

Configuration Option to Hide Estimate PTO Feature

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202403/EP_Estimate_PTO_Remove.htm Path: EP/Release-Notes/Enhancements/2024/MR_202403/EP_Estimate_PTO_Remove.htm

Configuration Option to Hide Estimate PTO Feature

Clients can now hide the Estimate PTO function on the Paid Time Off form using the Configuration Template and/or Client Override. Select the Hide PTO Estimator toggle on the Configuration Template form for a client to hide the Estimate PTO function.

The Estimate PTO function is designed to work for flat amount plans. Using this feature, clients with plans that accrue PTO over time can remove the estimator to prevent confusion.

JIRA # EP-6940

========================================================================

Total Compensation Form for Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202403/EP_Total_Compensation_Form.htm Path: EP/Release-Notes/Enhancements/2024/MR_202403/EP_Total_Compensation_Form.htm

Total Compensation Form for Employee Portal

The new Total Compensation form is now available for employees in Employee Portal. This form can be accessed by selecting Pay > Total Compensation. On this form, employees can select a year to view total compensation for that year and specify individual quarters to focus the results further.

[Image: screenshot]

The Overview tab contains an overview of all compensation, including the worth of the employee’s total compensation, their pay, their benefits contribution, and their taxes. The tab also includes a visualized breakdown of their compensation.

The Pay tab contains a breakdown of the employee’s pay. The visualization and table display the worth of the employee’s regular pay, as well as compensation such as holidays, PTO, and vacation. It also displays the total worth of any bonuses, such as incentives, referrals, or commissions.

The Benefits tab contains details on the employee’s benefit plans, displaying the contribution to each plan by both the employee and the company.

The Taxes tab contains details on taxes paid by both the employee and the company for the employee’s compensation. The visualization and tables show specific values for taxes paid, such as federal and state income, FICA, Medicare, etc.

Using this new form, employees can review detailed information about their total compensation from the employer for their financial records.

JIRA # EP-843, EP-7122, EP-7123, EP-7218, EP-7125, EP-7230

========================================================================

Improvements for Cross-Hired Employee Segments

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202404/EP_4993_Crosshire_Segments.htm Path: EP/Release-Notes/Enhancements/2024/MR_202404/EP_4993_Crosshire_Segments.htm

Improvements for Cross-Hired Employee Segments

The Segments form has been improved to better handle cross-hired employees and indicate their company affiliations. The Add Employees form on the Segments form now includes the Company Name field, which displays the name of each employee’s company. In addition, when the segment targets an employee in a specific client, only names from that client are shown, even if the employee is a cross hire with multiple companies.

JIRA # EP-4993

========================================================================

New Clients Use Default UEX Automatically

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202404/EP_7538_New_Client_UEX.htm Path: EP/Release-Notes/Enhancements/2024/MR_202404/EP_7538_New_Client_UEX.htm

New Clients Use Default UEX Automatically

When a service provider adds a new client in PrismHR, the client is now automatically set to use the Default UEX template. Previously, the client was defaulted to the legacy template, and needed to be upgraded to the new UEX manually.

JIRA # EP-7538

========================================================================

Year-End Tax Forms Now Available

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202412/1095%20PDF.htm Path: EP/Release-Notes/Enhancements/2024/MR_202412/1095 PDF.htm

Year-End Tax Forms Now Available

Year-end tax forms are now available to view in Employee Portal. These include the W-2, W-2C, 1099, and 1095C forms.

JIRA # EP-8072, EP-8073, EP-8074, EP-8075

========================================================================

Install Employee Portal Link as App

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/MR_202412/App_Install.htm Path: EP/Release-Notes/Enhancements/2024/MR_202412/App_Install.htm

Install Employee Portal Link as App

Employees can now add Employee Portal to the home screen of their phone as a Progressive Web App (PWA). To add the bookmark to the home screen, navigate to Employee Portal, then select Add to Home Screen in your phone’s options menu. The bookmark to Employee Portal is added to your home screen with the PrismHR icon.

JIRA # EP-8691

========================================================================

Time Sheet Entry in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202406/ADMP_TimeSheetEntry.htm Path: EP/Release-Notes/Enhancements/2024/QR_202406/ADMP_TimeSheetEntry.htm

Time Sheet Entry in Employee Portal

Managers can now review, edit, and approve time sheets directly from Employee Portal using the new Time Sheets form. To access this form, select Time Sheets from the menu while in Manager mode.

[Image: screenshot]

The Time Sheets form displays a list of time sheets which are in progress and ready for review and approval. This form displays summary information about each time sheet, including the pay date, pay group, payroll type and number, the cutoff date, and status. Using this form, managers can view details of the time sheet and apply manual edits.

Select Start or Edit to display the Time Sheet Summary form, which displays information for each employee on the time sheet. Select View to review time sheets which have been submitted for calculation.

Manually Editing a Time Sheet

Using the Time Entry tab, managers can view details for each employee, including their pay rate, regular pay hours, overtime, PTO, and other details on the Time Entry tab. Managers can use the Leave Requests tab to apply leave to the time sheet and view leave that has been applied to the time sheet.

A blue dot next to the employee’s name indicates that additional entries are on the Pay Details Time Entry form.

A yellow triangle icon next to an employee’s name on the Summary Time Sheet indicates that there is a Leave Request for this employee that needs to be applied to the time sheet.

The Search field can be used to search for a specific employee by name or identifier. The Filter button can be used to narrow the list of employees based on Pay Method, Employment Type, Pay Group, Location, Department, Division, or FLSA status. Filters can be used together. For example, to see all part time employees in a specific department search by Department and Employment Type.

[Image: screenshot]

Time sheets can be edited directly from the Time Entry tab by clicking on specific cells. In addition, a manager can edit a specific employee’s time sheet record by selecting the employee name on the Time Entry tab to display the Pay Details form, where the employee’s time sheet record can be edited directly.

The Pay Details form is used to add time using different allocations, for example, if an employee worked at a different location. It is also used to add an entry for a Pay Code not shown on the Summary form.

[Image: screenshot]

Managers can lock specific employees by clicking on the

[Image: screenshot]

(Lock) icon. In addition, managers can view the Employee Details form for a specific employee by clicking on the

[Image: screenshot]

(Employee Details) icon.

Note: Note: If the time sheet record for an employee is locked, editing a cell on the Summary saving changes on the Pay Details form will unlock the record.

Applying Approved Leave to the Time Sheet

The Leave Requests tab displays approved leave requests that must be applied to the time sheet.

Note: Note: The Leave Requests tab does not display if there are no employees with leave that needs to be applied to their time sheet.

[Image: screenshot]

Click Apply Leave to apply the approved leave to the time sheet. Click Details to display the Leave Details form, where leave can be applied to the employee’s time sheet record. Managers can review the leave on this form to verify that the PTO has been allocated properly, then apply the leave to the time sheet.

[Image: screenshot]

The Leave Details form lists the leave dates, approved hours, and leave balance. The Adjusted Hours field defaults to the approved hours but can be changed to apply a different amount to the time sheet. If the Adjusted Hours field is changed, a comment must be added.

The Hours section displays the Current Hours and Updated Hours. The Current Hours is the amount currently on the time sheet for that leave code, and the Updated Hours show what will be on the time sheet when the Apply Leave button is clicked. Current Hours will only show if leave is set up with a Leave Offset Pay Code.

Pay Rate Changes and Time Sheets

If the employee has a pay rate change during the pay period covered by the time sheet, a warning message displays indicating that the time sheet must be corrected. This process must be done in the PrismHR software, and is not available for managers through Employee Portal at this time. Applying pay rate changes to time sheets will be added to Employee Portal in a future release.

Reviewing Details of a Time Sheet

Once edits to a time sheet are complete, click Review to access the Review tab, which displays summary information for the time sheet. Using this form, managers can review the gross pay and hours of the time sheet, as well as charts that break down the time sheet into elements such as Pay Codes, Departments, Locations, or Employment Types.

[Image: screenshot]

Click the View By field to change the graph to display different variables. In addition, click the Download button to download the time sheet as a CSV file.

If any employees on the time sheet have not been allocated pay, they display in the Unpaid Employees section. Managers should review this section and click Return to Time Sheet to make any necessary corrections before submitting the time sheet.

Once the time sheet is finalized, click Submit for Calculation to submit the time sheet for processing.

Note: Note: Once Submit for Calculation has been clicked changes can no longer be made, although the time sheet can still be viewed. To make any changes to the time sheet once it has been submitted for calculation, contact your Service Provider.

========================================================================

Prevent Employees from Canceling PTO

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202406/EP_Cancel_PTO.htm Path: EP/Release-Notes/Enhancements/2024/QR_202406/EP_Cancel_PTO.htm

Prevent Employees from Canceling PTO

Clients can now restrict the ability for employees to cancel their PTO leave requests using the Configuration Template or the Client Override. Select the Employees Ability to Cancel PTO toggle on the Configuration Template form to prevent employees from canceling leave requests.

Note: Note: When the employee’s ability to cancel PTO is restricted, managers still retain their access to canceling PTO for assigned employees.

JIRA # EP-7113

========================================================================

Pay Widget Updated to New UEX

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202406/EP_Pay_Widget_UEX.htm Path: EP/Release-Notes/Enhancements/2024/QR_202406/EP_Pay_Widget_UEX.htm

Pay Widget Updated to New UEX

The Pay widget has been updated to the Unified Employee Experience (UEX). These updates include new stylistic elements and verbiage to match the UEX updated across the system.

JIRA # EP-6631

========================================================================

View Total Balance on PTO Summary

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202406/EP_PTO_Summary_Total_Balance.htm Path: EP/Release-Notes/Enhancements/2024/QR_202406/EP_PTO_Summary_Total_Balance.htm

View Total Balance on PTO Summary

The PTO Summary chart on the Paid Time Off form in Employee Portal now displays the total balance of all remaining PTO. In addition, it displays the Available value, which shows the total balance of all remaining PTO, taking into account any regulations that restrict the maximum PTO usage per year.

The Total Balance value is calculated according to Total Accrued + Carry Over – Planned – Taken.

The Available value is calculated according to Total Accrued + Carry Over – Planned – Taken, with a maximum cap according to regulations.

JIRA # EP-7359

========================================================================

Search for Both Legal and Preferred Names

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202406/EP_Search_Legal_Name.htm Path: EP/Release-Notes/Enhancements/2024/QR_202406/EP_Search_Legal_Name.htm

Search for Both Legal and Preferred Names

When a manager searches for an employee using the My Employees form or widget in Employee Portal, the search results now include employees with matching preferred names or legal first names. Previously, only preferred first names were included in the results.

JIRA # EP-7628

========================================================================

Employee Termination HR Action

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202406/EP_Termination_HR_Action.htm Path: EP/Release-Notes/Enhancements/2024/QR_202406/EP_Termination_HR_Action.htm

Employee Termination HR Action

Managers can now use the Termination form to terminate an employee’s position at the company. To access this form, select an employee on the My Employees form. On the Employee Details form that displays, select HR Actions > Termination.[Image: screenshot]

The Details panel on this form shows the status and type of the employee. The History panel displays the history of the employee’s status changes at the company.

[Image: screenshot]

To begin the termination process:

  1. On the Employee Details form for a selected employee, navigate to HR Actions > Termination.
  2. Click Terminate Employee. The Proposed Change section displays.
  3. Enter the Termination Status, Termination Date, Termination Reason, and Last Day Worked.
  4. In the Okay to Rehire? field, select if the employee is eligible for rehiring.
  5. Select whether to deactivate direct deposits in the Turn Off Direct Deposit (if Active) field.
  6. In the Reassign Pending Approvals field, select another employee. The terminated employee’s approvals queue will be reassigned to the selected employee.
  7. In the Termination Explanation field, add a reason for the employee’s termination to be added to the employee’s record.
  8. Review the Unpaid PTO section. This section displays any unpaid PTO for the employee, which is handled by state regulations.
  9. Click Save. The proposed change is added to the system to terminate the individual’s employment.

Using this new form, managers can conduct employee terminations directly through Employee Portal, as well as handle necessary steps to record the termination, deactivate direct deposits, and reassign approvals.

JIRA # EP-7398

========================================================================

Enhancements to Themes Form for UEX

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202406/Themes_Form_Enhancements.htm Path: EP/Release-Notes/Enhancements/2024/QR_202406/Themes_Form_Enhancements.htm

Enhancements to Themes Form for UEX

The Themes form in Employee Portal has been enhanced with tags to quickly identify themes available for the new UEX. All themes for the new UEX now feature the New Experience tag, allowing users to quickly identify UEX themes. In addition, the Version column displays the UI version of each theme.

Note: Note: If the new UEX is not enabled on the System Parameters form, this tag does not display.

JIRA # EP-6311

========================================================================

Account Dropdown Menu

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202409/Account_Dropdown_Menu.htm Path: EP/Release-Notes/Enhancements/2024/QR_202409/Account_Dropdown_Menu.htm

Account Dropdown Menu

Worksite managers and worksite trusted advisors who are assigned to multiple companies can now select the current Active Company using a new option in the Account dropdown menu. Click the company name in the dropdown menu to access a list of all assigned companies. When a manager or advisor selects a different company, Employee Portal displays information for only that company. Using this feature, managers and advisors who are assigned to multiple companies can easily switch between their duties at the various organizations.

Note: Note: When a manager who is an employee at one company switches to another company where they are a manager, but not an employee, the Employee/Manager toggle in Employee Portal no longer displays. To access their employee information, the manager must switch back to the initial company.

JIRA # EP-7816, EP-7829

========================================================================

Filtered Totals on Time Sheet

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202409/Filtered_Totals_Row.htm Path: EP/Release-Notes/Enhancements/2024/QR_202409/Filtered_Totals_Row.htm

Filtered Totals on Time Sheet

When a user filters the totals on the Time Sheet form in Employee Portal, a new Filtered Totals row displays totals for all items matching this filter. This new row displays directly above the Totals row, and users can compare the two values to verify the accuracy of time sheet information.

JIRA # ADMP-373

========================================================================

My Approvals in HR Actions

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202409/HR_Actions_My_Approvals.htm Path: EP/Release-Notes/Enhancements/2024/QR_202409/HR_Actions_My_Approvals.htm

My Approvals in HR Actions

Managers can now access HR Action approvals from the My Approvals form in Employee Portal. Managers can review details for each request by clicking the Down Arrow icon and accept or deny the request directly from this form. Using the selection menu, managers can refine results to display specific approvals or categories.

In addition, the Approvals widget on the dashboard has been enhanced to display HR Action approvals. Managers can click the Review button to view details for each approval, as well as accept or deny the request from the dashboard.

The following HR Actions now display on the My Approvals form and the Approvals widget:

• Leave of Absence

• Return to Work

• Position Change

• Pay Rate Change

• Status Type Change

• Termination

• Rehire

Using this enhanced form and widget, managers can quickly review and make decisions for HR Actions that require approval.

JIRA # EP-7296, EP-7297, EP-7298, EP-7299, EP-7301, EP-7302, EP-7303, EP-7305, EP-7369, EP-7370, EP-7371, EP-7481

========================================================================

Pay Rate Change on Time Sheet in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202409/Pay_Rate_Change_EP.htm Path: EP/Release-Notes/Enhancements/2024/QR_202409/Pay_Rate_Change_EP.htm

Pay Rate Change on Time Sheet in Employee Portal

Managers can now approve time sheets that include a pay rate change using the Time Sheet Entry form in Employee Portal. When a time sheet includes a pay rate change that was made during the pay period, the manager can allocate hours on the time sheet to the appropriate pay rates.

To allocate hours on a time sheet with a pay rate change, select the Time Sheet Entry tab. If an employee has a pay rate change during the pay period, a yellow warning icon displays next to the employee’s name. Select the Pay Rate Change tab to review a list of all employees with pay rate changes during the pay period.

[Image: screenshot]

To allocate hours for each pay rate, click Allocate Hours on the corresponding row. The Allocate Hours form displays. On this form, enter the total number of hours for each pay rate. Once the hours are split between the two pay rates, click Apply Change, and the summary entry converts into two entries, one for each pay rate.

Using this new method, managers can easily allocate hours to account for pay rate changes directly from Employee Portal to make time sheet entries more efficient.

JIRA # , ADMP-394, ADMP-395, ADMP-441, ADMP-442, ADMP-443, ADMP-446, ADMP-447, ADMP-460, ADMP-461, ADMP-530, ADMP-557, ADMP-574, ADMP-592

========================================================================

Access Next Gen Report Center from Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202409/Report_Center_Access.htm Path: EP/Release-Notes/Enhancements/2024/QR_202409/Report_Center_Access.htm

Access Next Gen Report Center from Employee Portal

Worksite managers can now use the single sign-on feature to access the Next Gen Report Center directly from Employee Portal. Managers with the appropriate access can select the Report Center (New) menu item to access Report Center.

Note: Note: Managers must have access to the Next Gen Report Center for their User Role for this menu option to display. If the manager’s user role does not include access to Report Center, the menu item does not display.

JIRA # EP-7876, EP-7877

========================================================================

Time Sheet Import

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202409/Time_Sheet_Import.htm Path: EP/Release-Notes/Enhancements/2024/QR_202409/Time_Sheet_Import.htm

Time Sheet Import

Managers can now import time sheets in Employee Portal on the Time Sheets form. This method can be used for external timekeeping services or other means of logging time. To import a time sheet, select Time Sheets, then select Import. The Import Time Sheet form displays.

[Image: screenshot]

On this form, select an import template from the dropdown menu. After a template is selected, a text box listing requirements and notes displays, and a file can be selected for import. Valid file types include TXT and CSV files, and the file must be no more than 10MB in size. Once the file is uploaded, click Next.

The system processes the imported file immediately, and the information displays on the Review and Apply step. Review the information on this step to verify that the time sheet information is correct.

[Image: screenshot]

The Summary tab displays each line of the time sheet. The Warnings tab displays any warnings from the import, with a description of any errors from the file. If one or more warnings prevented the file from being imported completely, click the Restart button to redo the import process.

Once the time sheet is verified, click Import to import the time sheet. The Import Results step displays a summary of the file and any messages from the import. Managers can download the summary, warnings, or messages from the import using the corresponding buttons for record keeping.

JIRA # ADMP-2, ADMP-320, ADMP-322, ADMP-581, ADMP-585, ADMP-590

========================================================================

Worksite Trusted Advisors in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202409/Worksite_Trusted_Advisors.htm Path: EP/Release-Notes/Enhancements/2024/QR_202409/Worksite_Trusted_Advisors.htm

Worksite Trusted Advisors in Employee Portal

The Worksite Trusted Advisor user role is now available in Employee Portal. Trusted advisors can access all the same functions as a manager in Employee Portal, including managing employees, viewing the PTO calendar and verifying PTO requests for employees, and managing documents. Trusted advisors do not have access to the Employee/Manager toggle, as they do not have access to the employee menus or widgets in Employee Portal.

JIRA # EP-7835

========================================================================

Configuration Template Audit

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Configuration_Template_Audit.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Configuration_Template_Audit.htm

Configuration Template Audit

Service providers can now review a history of changes made to configuration templates. On the Configuration Templates form or Client Overrides form, select a form and click Template History to access a form which lists all changes made to the template. This report includes which field was changed and in which section, as well as the type of change, who made the change, and the date.

[Image: screenshot]

Using this new form, service providers can track changes to configuration templates to correct errors and verify updates more efficiently.

JIRA # EP-8024

========================================================================

Hide Employee Portal Navigation

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Hide_EP_Features.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Hide_EP_Features.htm

Hide Employee Portal Navigation

Administrators can now hide the header, navigation menu, and breadcrumbs for Employee Portal, allowing them to embed the EP application into their own application.

Administrators can configure a single sign-on URL with the new “?hideNavHeader=true” parameter to display an Employee Portal form without headers, navigation, or breadcrumbs.

For example, to access the Pay History form without a header, menu or breadcrumb, you could use a URL like “https://abc-ep.prismhr.com/uex/#/ess/pay-history?hideNavHeader=True”.

JIRA # EP-7913

========================================================================

Payroll Approval Dashboard Update

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_Approval_Dashboard.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_Approval_Dashboard.htm

Payroll Approval Dashboard Update

Users can now select a payroll by clicking anywhere on the payroll row, with the exception of the Approve and Deny buttons. Selecting a payroll in this manner displays the Payroll Detail form, just like selecting Review Payroll.

In addition, the Payroll Approval dashboard has been updated to be consistent with the Time Sheet Entry dashboard. The panel order and fields now match those on the Time Sheet Entry dashboard to maintain a standard style across the dashboards.

This style update helps maintain consistency between the dashboards for HR approval actions in Employee Portal.

JIRA # ADMP-253, ADMP-654

========================================================================

Payroll Approval Form Update

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_Approval_Form_Update.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_Approval_Form_Update.htm

Payroll Approval Form Update

The Payroll Approval form has been updated to match the layout of the Time Sheet Entry form and Payroll Summary form. The form now displays the same information in the same format, including Pay Date, Description, Payroll Type, Payroll Status, Total Invoice, and Payroll Number.

JIRA # ADMP-652

========================================================================

Pay Details Lock Banner Update

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_Details_Lock.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_Details_Lock.htm

Pay Details Lock Banner Update

When an employee’s time sheet has been locked, the information banner that displays on the Pay Details form now displays a lock icon to emphasize that the time sheet status. This style update keeps the notification consistent with the Summary table.

JIRA # ADMP-558

========================================================================

Payroll History Form in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_History_Form.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Payroll_History_Form.htm

Payroll History Form in Employee Portal

Managers can now use the Payroll History form to view and download reports on completed payrolls in Employee Portal. To access this form, select Payroll History from the menu while in Manager mode.

[Image: screenshot]

The Payroll History form displays a list of payrolls by year. To filter the results, select a Year and a Payroll Type in the selection fields. Managers can review summary information for payrolls on this form. Select a pay date to display additional details for the payroll from that date.

On the Payroll Summary form accessed by selecting a pay date, managers can review an overview of the payroll, details for specific employees on the payroll, and a list of associated reports and files.

[Image: screenshot]

The Overview tab displays a chart of how pay was allocated for this payroll and a details breakdown of the payroll statistics. Select options in the View By field to view the pay distribution by different variables, including departments, pay codes, and positions. This information can be downloaded by selecting the Download button.

[Image: screenshot]

The Payroll Details tab displays information for each employee on the payroll. Managers can review specific information about the hours worked, gross pay, taxes, deductions, and other information. This information can be downloaded by selecting the Download button.

[Image: screenshot]

The Reports & Files tab displays reports or files associated with the payroll, including the title, classification, file type, and status. Finalized files can be viewed or downloaded by selecting the corresponding buttons in the Action column.

Note: Note: Managers must have full access to the Payroll History Process ID in Prism to access the Payroll History form in Employee Portal. Managers must have full access to Payroll Summary in Prism to access the Payroll Summary tab and access to Payroll Reports to access the Reports & Files tab.

JIRA # ADMP-629

========================================================================

Retirement Summary Form

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Retirement_Summary_Form.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Retirement_Summary_Form.htm

Retirement Summary Form

Employees can now view and update their retirement contributions using the new Retirement Summary form in Employee Portal. Using this form, employees can see their retirement contributions per year, view the contribution rate, and change their contribution rates.

To access this form, select Benefit > Retirement Summary. The Retirement form displays.

[Image: screenshot]

The contribution rate displays for both pre-tax and Roth retirement accounts. In addition, the Retirement Summary section displays statistics for their yearly contribution. Select the Year field to view previous years.

Employees can select the Update Rates button to display the Update Contributions form. On this form, employees can change their contribution rates to Pre-Tax and Roth retirement accounts.

[Image: screenshot]

To make a change, select Amount for a flat amount or Percentage for a percentage of the paycheck. In the Amount field, enter the flat contribution or percentage to be contributed to retirement.

Note: Note: This value is contributed per pay period. Employees contributing a flat amount should calculate the amount of each paycheck to contribute accordingly.

Important: Clients can enable this feature for specific clients using the Configuration Template or the Client Override. Deselect the Retirement Contributions Read Only toggle on the Configuration Template form to allow employees from updating their retirement contribution rates from this form.

Once the change is complete, click Review. An acknowledgment displays, where the employee can add a digital signature indicating that they intend to make this change. Check the box and select Submit to submit the change for processing to make the change on the next payroll.

JIRA # EP-7960

========================================================================

Termination Explanation Character Limit

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Termination_Explanation_Limit.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Termination_Explanation_Limit.htm

Termination Explanation Character Limit

To maintain consistency across forms, the Termination Explanation field on the Employee Termination form is now limited to 200 characters. This standard size makes the form consistent with other explanation fields in the system.

JIRA # ADMP-679

========================================================================

Time Sheet Review Form Update

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2024/QR_202411/Time_Sheet_Review_Update.htm Path: EP/Release-Notes/Enhancements/2024/QR_202411/Time_Sheet_Review_Update.htm

Time Sheet Review Form Update

The Unpaid Employees section on the Time Sheet Review form has been enhanced to provide managers with additional information.

Using these new fields, managers can determine the proper course of action for unpaid employees more easily.

JIRA # ADMP-708

========================================================================

Redirect After Logout for Session Timeouts

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/MR2025_01/Redirect_Login.htm Path: EP/Release-Notes/Enhancements/2025/MR2025_01/Redirect_Login.htm

Redirect After Logout for Session Timeouts

When a client enables the Redirect After Logout option on the General Settings tab of the Configuration Templates form, Employee Portal users are now redirected to the specified URL when the user is logged out via a session time out or other error. This update allows service providers to further control the login screen destination for companies with that setting enabled.

JIRA # EP-8737

========================================================================

Audit Details Now Uses Local Time

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Audit_Details_Time.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Audit_Details_Time.htm

Audit Details Now Uses Local Time

The timestamp on the Audit Details form now displays in the browser’s local time instead of the server time. When an employee accesses this form, they can view timestamps using their local time without having to worry about accounting for location differences.

JIRA # EP-8231

========================================================================

Download and Print Total Compensation Statements

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Download_Total_Comp_Statement.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Download_Total_Comp_Statement.htm

Download and Print Total Compensation Statements

Employees can now download and print their compensation information as a report from the Total Compensation Statement form in Employee Portal. Reports can be downloaded as both PDF and CSV files.

The PDF version of the report includes the company, employee name, year, and quarter, as well as the total compensation package, including pay, benefits, and taxes. The report also includes a graph of this information, and tables containing total values for each attribute.

The CSV version of the report includes categories for pay, benefits, and taxes, amounts, employee contributions, employer contributions, and descriptions.

This feature is available on both desktop and mobile devices.

JIRA # EP-7236

========================================================================

Enhancement to Employer Contribution of Benefits Card

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Employer_Comp_Card_Retirement.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Employer_Comp_Card_Retirement.htm

Enhancement to Employer Contribution of Benefits Card

When an employee views the Employer Contribution of Benefits card in Employee Portal, the form now displays more information regarding retirement contributions. The Overview tab on this form now displays the employer 401k contribution, as well as a section for the retirement contribution on the Compensation breakdown chart.

The Benefits tab on this form now displays employer contributions to the retirement plan and incorporates this information into the breakdown chart and Detailed Benefit Breakdown.

JIRA # EP-7665

========================================================================

Job Candidates in Employee Portal New Hire

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Job_Candidates_In_EP.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Job_Candidates_In_EP.htm

Job Candidates in Employee Portal New Hire

Managers can now view and select job candidates from the PrismHR system on the New Hire form in Employee Portal. By selecting a job candidate, the manager no longer needs to re-enter the candidate’s information during the new hire process.

The Candidates tab on the New Hire Dashboard now displays the name, candidate number, application date, and location of job candidates in the system. Managers can select candidates to hire directly from this tab. In addition, managers can search for candidates by name using the Search field.

To hire a candidate:

  1. Select New Hire Dashboard.

  2. Select the Candidates tab.

  3. Select the candidate to hire, or search for the client by name using the Search field.

  4. Click Hire Candidate. The New Hire Form displays, with the candidate’s information prepopulated in the appropriate fields.

  5. Continue the New Hire process with the candidate’s information to initiate the hiring process.

Using this new tab, managers can review candidates in Employee Portal and transfer their information directly to the New Hire process when they select a candidate.

JIRA # EP-5999, EP-8341, EP-8342, EP-8344, EP-8348, EP-8864, EP-8865, EP-8928

========================================================================

Limit PTO Requests to Maximum Hours in Block

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Limit_PTO_Requests_Max_Hours.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Limit_PTO_Requests_Max_Hours.htm

Limit PTO Requests to Maximum Hours in Block

When an employer sets a value for the Maximum hours for a detail time sheet entry field on the PTO Benefit Plan, that maximum is now applied to PTO requests made through Employee Portal. When an employee makes a PTO request or a manager makes the PTO request on behalf of the employee, and the request exceeds the limit, the user is notified that they cannot submit the request until the value is changed.

JIRA # EP-8604, EP-8605

========================================================================

Payroll Vouchers in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Payroll_Vouchers_In_EP.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Payroll_Vouchers_In_EP.htm

Payroll Vouchers in Employee Portal

Managers can now view Employee Payroll Vouchers from posted payrolls in Employee Portal. Using this new form, managers can review extensive information about payroll vouchers for individual employees to verify the payroll.

To access a Payroll Voucher:

  1. Select Payroll History.

  2. Select the Pay Date for the voucher. The Payroll form displays.

  3. Select the Payroll Details form to view the individual employees on the payroll.

  4. Select the Voucher number for the employee to review. The Payroll Voucher form displays.

[Image: screenshot]

This form displays the following information:

Using this new form, managers can verify payroll vouchers directly from Employee Portal, while retaining the same functionality and security from core Prism.

JIRA # EP-8305, EP-8306, EP-8308, EP-8401, EP-8402, EP-8403, EP-8404, EP-8405, EP-8406, EP-8407, EP-8408, EP-8409, EP-8410, EP-8411, EP-8414, EP-8415, EP-8416, EP-8417, EP-8418, EP-8419, EP-8420, EP-8421, EP-8422

========================================================================

Preferred Name On New Hire Entry

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Preferred_Name_New_Hire_Entry.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Preferred_Name_New_Hire_Entry.htm

Preferred Name On New Hire Entry

The Preferred Name field now displays on the New Hire entry form in the Additional Fields section. The employee can add their preferred name during Onboarding, or the manager can enter the name on the New Hire Entry form.

JIRA # EP-6602

========================================================================

Enhancement to Retirement Contributions Year Filter

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Retirement_Comp_Year_Filter.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Retirement_Comp_Year_Filter.htm

Enhancement to Retirement Contributions Year Filter

When an employee accesses the Year filter dropdown selection on the Retirement Summary form, only the years with available data now display. If no data is available, only the current year displays.

JIRA # EP-8285

========================================================================

Standardized Dependents and Beneficiaries

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Standardized_Dependents.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Standardized_Dependents.htm

Standardized Dependents and Beneficiaries

Forms used to add and review dependents and beneficiaries have been standardized between Employee Portal and Benefits Enrollment so that equivalent forms have the same forms and functionality.

The Dependencies form has been updated with several changes:

The Beneficiaries form has been updated with multiple changes:

JIRA # EP-8153

========================================================================

Update Navigation Trail for Embedded Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Update_Nav_Trail.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Update_Nav_Trail.htm

Update Navigation Trail for Embedded Employee Portal

When a client uses Employee Portal in an embedded iframe, the navigation trail in the header can now update based on user activity. For example, if a user clicks on Beneficiaries in the parent window, then navigates to Dependents via a link in the iframe, the parent window can update its navigation trail to display the Dependents path.

JIRA # EP-8781

========================================================================

Variable Salary Pay Option in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/QR2025_03/Variable_Salary_Pay_Option.htm Path: EP/Release-Notes/Enhancements/2025/QR2025_03/Variable_Salary_Pay_Option.htm

Variable Salary Pay Option in Employee Portal

Managers can now set employees to the Variable Salary pay method in forms throughout Employee Portal to support this employee payment method. Variable Salary is now available as a pay method on the New Hire and Rehire forms and as a filter on the Time Sheet Entry form.

JIRA # EP-8809

========================================================================

Breadcrumb Update for UEX

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/Breadcrumb_Update.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/Breadcrumb_Update.htm

Breadcrumb Update for UEX

The Breadcrumb links displayed across the UEX have been updated to a more modernized format. This includes the following changes:

JIRA # EP-9051

========================================================================

Update to Margin Constancy

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/Margin_Consistency.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/Margin_Consistency.htm

Update to Margin Constancy

Margin sizes for forms have been updated across the UEX to maintain a consistent style. This includes changes to prevent content from being cut off, obscured, or improperly framed for desktop and mobile devices.

JIRA # EP-8899

========================================================================

Enhancements to New Hire Dashboard Email Notifications

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/New_Hire_Notification.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/New_Hire_Notification.htm

Enhancements to New Hire Dashboard Email Notifications

Managers can now send copies of email notifications from the New Hire Dashboard to themselves or to other employees in the system. Managers can now select to be copied in the email using the Send a copy to me option. In addition, other email addresses can be added in the Additional Recipients field. These email addresses must use the user@domain.com format, and can be separated by commas.

The Personal Email check box on the Email Notification has been renamed New Hire to clarify that this is for the new hire’s email address.

In addition, if a manager selects the Resend option, all previous options for additional email addresses are applied to the resent email message.

JIRA # EP-6884, EP-7667, EP-8322, EP-8380

========================================================================

Onboarding Component Removed from Configuration Templates

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/Onboarding_Component_Removed.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/Onboarding_Component_Removed.htm

Onboarding Component Removed from Configuration Templates

The Onboarding component has been removed from the Component selection menu on configuration templates. This menu component used an outdated format which is no longer used by clients. This option has been removed from the Configuration Templates options and from existing templates.

JIRA # EP-8879

========================================================================

Update to Page Title Constancy

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/Page_Title_Consistency.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/Page_Title_Consistency.htm

Update to Page Title Constancy

Page titles for forms have been updated across the UEX to maintain a consistent style. This includes updates to fonts, character sizes, and margins to prevent cutoffs.

JIRA # EP-8900

========================================================================

PrismOne Mobile App Now Available

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/PTO_PrismOne_Mobile.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/PTO_PrismOne_Mobile.htm

PrismOne Mobile App Now Available

We are excited to announce the launch of the PrismONE mobile app, now available on Google Play and the Apple App Store! With the PrismONE mobile app, employees can access their payroll and HR information anytime, anywhere, on any device. Employees can easily view their pay stubs, check PTO balances, and review benefits right from their mobile devices. For more information, please review the Quick Start Guide.

Clients now have the option to show the PrismOne Mobile App Information via configuration templates and client overrides. To show the QR Code, select the Show PrismOne Mobile App Information option on the configuration template or client override.

JIRA # EP-8999

========================================================================

Enhancements to Segments Form

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/Segments_Form_Check.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/Segments_Form_Check.htm

Enhancements to Segments Form

The Segments has been enhanced with additional protections to prevent clients from accidentally creating segments that do not include any employees.

When an employee creates a segment, the Targeted Employees selector no longer has an option selected by default. Employees must specifically select whether to target everyone with the segment or to select specific recipients.

JIRA # EP-8875

========================================================================

Update to Table Standards

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_04/Table_Standards.htm Path: EP/Release-Notes/Enhancements/2025/R2025_04/Table_Standards.htm

Update to Table Standards

Tables for forms have been updated across the UEX to maintain a consistent style. Selection options have been improved to ensure that options are accessible even for long lists and short window sizes. In addition, tables on mobile devices now display if the results are filtered.

JIRA # EP-8378

========================================================================

Breadcrumb Update for UEX

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_05/Breadcrumb_Update.htm Path: EP/Release-Notes/Enhancements/2025/R2025_05/Breadcrumb_Update.htm

Breadcrumb Update for UEX

The Breadcrumb links displayed across the UEX have been updated to a more modernized format. This includes the following changes:

JIRA # EP-9100

========================================================================

Context-Sensitive Buttons for Tax Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_05/Context_Sensitive_Tax_Forms.htm Path: EP/Release-Notes/Enhancements/2025/R2025_05/Context_Sensitive_Tax_Forms.htm

Context-Sensitive Buttons for Tax Forms

On the Tax Withholding form, the button to advance to the next page has been changed so that the final button on a form now indicates the end of the document.

When the current page is not the last page of the form, the button displays as Continue.

When the current page is the last page of the form, the button displays as Submit Form.

With this change, it is much clearer to the user when they have completed a Federal or State tax form and are ready to submit the form and advance to the next stage in the process.

JIRA # EP-8990

========================================================================

Add Custom Support Team Titles to Contact Us Widget

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_05/Custom_Support_Teams.htm Path: EP/Release-Notes/Enhancements/2025/R2025_05/Custom_Support_Teams.htm

Add Custom Support Team Titles to Contact Us Widget

Service Providers can now add custom titles to the list of Contact Roles on a Configuration Template or Client Override. When a service provider sets up custom titles for their support team using the Customize My Support Team Dashboard, these roles can now be added as contact roles for a support contact widget.

To add custom roles to a widget, select the Support Team widget on the Dashboard tab of a Configuration Template or Client Override and select Edit. In the Contact Roles field, select the custom title from the dropdown menu to add it to the list of Contact Roles.

JIRA # EP-8377

========================================================================

Enhancement to Inbound SSO Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_05/Inbound_SSO_Performance.htm Path: EP/Release-Notes/Enhancements/2025/R2025_05/Inbound_SSO_Performance.htm

Enhancement to Inbound SSO Performance

Improvements have been applied to the Inbound SSO feature to significantly improve performance of Employee Portal forms within customer applications.

JIRA # EP-9183

========================================================================

Enhancements for the PTO Calendar

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_05/PTO_Calendar_Overhaul.htm Path: EP/Release-Notes/Enhancements/2025/R2025_05/PTO_Calendar_Overhaul.htm

Enhancements for the PTO Calendar

The PTO Calendar has undergone visual enhancements to improve search features, filters, and buttons across all viewport sizes and devices.

[Image: screenshot]

The revised calendar now displays at full width for all devices, including mobile. Filters and buttons have been rearranged to match the new UEX style, and elements such as the date range are offset on their own row to improve readability.

JIRA # EP-9138

========================================================================

Legacy Themes Removed From Themes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_05/Remove_Legacy_Themes.htm Path: EP/Release-Notes/Enhancements/2025/R2025_05/Remove_Legacy_Themes.htm

Legacy Themes Removed From Themes Form

As a final step of the UX sunsetting process, Legacy themes have been removed from client accounts in Prism. Since legacy themes are no longer necessary, the Theme form now displays only UEX themes.

In addition, references to the Legacy UX have been removed now that the sunsetting process is complete. The Themes form no longer displays a Version selection or field, and the New Experience icon has been removed from themes using the new UEX.

JIRA # EP-8387

========================================================================

View and Edit Retirement Catch-Up Contributions in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_05/Retirement_Catchup.htm Path: EP/Release-Notes/Enhancements/2025/R2025_05/Retirement_Catchup.htm

View and Edit Retirement Catch-Up Contributions in Employee Portal

Employees can now add Catch-up amounts to their retirement contributions directly in Employee Portal. The Update Contributions form on the Retirement Summary now contains a Catch-up section for annual catch-up contributions. Simply enter new contribution amounts in this section and select Review to display the new rates. Employees are then prompted to sign an acknowledgment of the new rates for future payrolls. After checking this acknowledgment, click Submit to submit the new Catch-up contribution rates for future payrolls.

JIRA # EP-8926

========================================================================

Enhancement to 1095-C Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/1095C_Enhancement.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/1095C_Enhancement.htm

Enhancement to 1095-C Forms

When an employee views their 1095-C forms on the Taxes form in Employee Portal, the selection menu now displays the forms in chronological order, with the most recent form at the top for easier navigation.

JIRA # EP-9029

========================================================================

Enhancement to the File Audit Form

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/Enhancement_File_Audit_Form.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/Enhancement_File_Audit_Form.htm

Enhancement to the File Audit Form

When a configuration template is assigned to or removed from a client, service providers can now view the change by the template’s name on the File Audit form. Previously, the change displayed the configuration template’s ID number. With this enhancement, it is easier for service providers to verify which template was assigned or unassigned.

JIRA # EP-8855

========================================================================

Hire Type for New Hires in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/Hire_Type_For_New.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/Hire_Type_For_New.htm

Hire Type for New Hires in Employee Portal

When a new hire is added in Employee Portal, users can set the Hire Type field to determine if the new hire is a W2 Employee or a 1099 Contractor. With this new field, the New Hire form in Employee Portal is now compatible with Onboarding forms that use rules regarding 1099 documentation.

The Hire Type field only displays if the Contractors (1099) Allowed option is enabled for the client. If this option is disabled, the New Hire record defaults to a W2 employee.

JIRA # EP-8869

========================================================================

Legacy Configuration Template Sunsetting

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/Legacy_Configuration_Sunset.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/Legacy_Configuration_Sunset.htm

Legacy Configuration Template Sunsetting

The June release marks the final step of transition from legacy configuration templates. As part of this process, several changes will occur:

Note: Note: Formally assigning these clients to the Default UEX template will cause an increased client count for that template. This is expected behavior, and does not indicate any changes in the end-user experience.

JIRA # EP-8385, EP-8388

========================================================================

My Employees Form Now Defaults to Active

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/My_Employees_DefaultActive.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/My_Employees_DefaultActive.htm

My Employees Form Now Defaults to Active

When managers view the My Employees form in Employee Portal, the form now defaults to Active employees. Managers can use the filter options to view Inactive, Terminated, or On Leave employees. With this enhancement, managers can view all active employees more efficiently.

JIRA # EP-8093

========================================================================

My Employees Form Now Saves Sorting Preferences

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/My_Employees_Sorting.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/My_Employees_Sorting.htm

My Employees Form Now Saves Sorting Preferences

When a manager accesses the My Employees form in Employee Portal, the system now saves the sorting preferences from the current session. If a manager navigates to an employee record and then returns to the My Employees form, the sorting is retained so that the manager does not need to reenter filters and resort the results.

JIRA # EP-8081

========================================================================

Onboarding Component Removed from Configuration Templates

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/Onboarding_Component.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/Onboarding_Component.htm

Onboarding Component Removed from Configuration Templates

The Onboarding component has been removed from the Component selection menu on configuration templates. This menu component used an outdated format which is no longer used by clients. This option has been removed from the Configuration Templates options and from existing templates.

JIRA # EP-9242

========================================================================

Work Email Address for New Hires

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_06/Work_Email_For_New_Hire.htm Path: EP/Release-Notes/Enhancements/2025/R2025_06/Work_Email_For_New_Hire.htm

Work Email Address for New Hires

Managers can now add a work email address for a new hire on the New Hire Form in Employee Portal. Entries in this field must be valid email addresses.

JIRA # EP-8360

========================================================================

Direct Deposit on My Approvals

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_07/Direct_Deposit_My_Approvals.htm Path: EP/Release-Notes/Enhancements/2025/R2025_07/Direct_Deposit_My_Approvals.htm

Direct Deposit on My Approvals

In response to rising incidents of fraud involving unauthorized changes to employee banking details, an additional layer of security is now available for direct deposit accounts being added or removed from an Employee record.

[Image: screenshot]

Service providers can add a Direct Deposit Approval policy on the Approval Policies form in Prism. When this policy is enabled and an employee adds or removes a direct deposit account, an approval process triggers. This new process mirrors existing HR approval workflows and offers flexibility in routing: approvals can be directed to an employee’s manager, service provider, or another designated approver based on organizational preferences.

Managers can now view Direct Deposit approval requests on the My Approvals form or the My Approvals widget in Employee Portal, review the employee’s information, and approve or deny the change.

Note: Note: Bank account numbers are masked by default on this form to protect user security.

Employees can view their pending direct deposit approval requests on the Direct Deposits form in Employee portal. A message displays on the direct deposit, indicating that the change is still awaiting manager approval. Employees can make changes on this form, which will overwrite the current approval request.

[Image: screenshot]

This enhancement helps ensure that any changes to sensitive financial data are reviewed and verified to protect the security of employees.

JIRA # EP-9381, EP-9383, EP-9384

========================================================================

Enhanced Support for Many Companies on Login

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_07/Login_Many_Companies.htm Path: EP/Release-Notes/Enhancements/2025/R2025_07/Login_Many_Companies.htm

Enhanced Support for Many Companies on Login

The Login screen and Account Dropdown Menu have been enhanced for Worksite Managers and Worksite Trusted Advisors with access to more than 10 companies. When one of these users logs in or accesses the Account Dropdown Menu, a search bar now displays instead of a complete company list. The user can enter search criteria to scroll through only the companies that match that criteria, saving time for those with access to a large list of companies. Users with access to 10 or fewer companies are unaffected by this change.

JIRA # EP-7874

========================================================================

Restrict Work Email Address Changes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_07/Restrict_Work_Email_Change.htm Path: EP/Release-Notes/Enhancements/2025/R2025_07/Restrict_Work_Email_Change.htm

Restrict Work Email Address Changes

Service providers can now set Work Email addresses to Read Only using a new option on Configuration Templates and Client Overrides forms.

Select Work Email Read Only to set the Work Email field on the My Contact Info form in Employee Portal to Read Only. This can be used to prevent users from accidentally changing their email addresses to an invalid address or to incorrectly set their email address to something other than their work email.

JIRA # EP-3915

========================================================================

Subscribe to PTO Calendar Option

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_07/Subscribe_To_Calendar.htm Path: EP/Release-Notes/Enhancements/2025/R2025_07/Subscribe_To_Calendar.htm

Subscribe to PTO Calendar Option

The PTO Calendar in Employee Portal now features a Subscribe to Team Calendar option, which can be used to generate a subscription link to the calendar. After copying the link, users can add the link into calendars such as Google or Outlook to monitor the PTO Calendar from those applications.

Note: Note: This feature must be enabled by Service Providers for Configuration Templates or Client Overrides.

Note: Note: The Subscribe to PTO Calendar feature is not currently available to On-Prem Clients.

To enable the Subscribe to Team Calendar feature:

  1. In PrismHR, navigate to Employee Experience Configuration > Employee Portal > Configuration Templates or Employee Experience Configuration > Employee Portal > Client Overrides.

  2. Click Edit.

  3. Select the Enable PTO Calendar Sharing option.

  4. Click Save.

To obtain the PTO Calendar link:

  1. In Employee Portal, select the PTO Team Calendar.

  2. Click Subscribe to Calendar. The Subscribe to Team Calendar window displays.

  3. Copy the link provided.

  4. Use the provided link in your calendar application of choice.

For more information about using this feature with different calendar options, refer to the Subscribing to the PTO Calendar article on the CRC.

JIRA # EP-8497

========================================================================

Clock Number Field on Employee Details

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_08/Clock_Number.htm Path: EP/Release-Notes/Enhancements/2025/R2025_08/Clock_Number.htm

Clock Number Field on Employee Details

Worksite managers can now enter an employee’s clock number on the Employee Details section of the New Hire form. The Clock Number field is synchronized with the field of the same name in core Prism.

JIRA # EP-8355

========================================================================

Additional Gender Options for Dependents

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_08/Gender_Options.htm Path: EP/Release-Notes/Enhancements/2025/R2025_08/Gender_Options.htm

Additional Gender Options for Dependents

Employees can now select additional gender options for the personal details of their listed dependents. Employees can now select Non-Binary or Decline To State as options for the Gender field.

Note: Note: These options must be enabled by a Service Provider on the System Parameters form.

JIRA # EP-9402

========================================================================

New Globe Icon Available for Menus

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_08/Globe_Icon.htm Path: EP/Release-Notes/Enhancements/2025/R2025_08/Globe_Icon.htm

New Globe Icon Available for Menus

Service Providers can now choose the

[Image: screenshot]

(Global Classic Light) icon for Menu items in Employee Portal on Configuration Templates.

JIRA # EP-9517

========================================================================

Salary Hour Reduction Calculation on Timesheet

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_08/Salary_Hour_Reduction.htm Path: EP/Release-Notes/Enhancements/2025/R2025_08/Salary_Hour_Reduction.htm

Salary Hour Reduction Calculation on Timesheet

When a salaried employee has default hours for a pay code, and a manager then adds hours on another pay code, a message now displays indicating these hours will affect the salary amount.

The message reads “These hours will affect the salary amount. Should the standard hours in column X be reduced by Y hours?” If the manager selects Yes, the hours in the previous pay code are automatically reduced so that the total hours matches the employee’s default amount.

JIRA # EP-9271

========================================================================

Configuration Template Option for Managers to Enter New Hire SSN/DoB

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_08/SSN%20DOB%20Toggle.htm Path: EP/Release-Notes/Enhancements/2025/R2025_08/SSN DOB Toggle.htm

Configuration Template Option for Managers to Enter New Hire SSN/DoB

Clients can now allow managers to proceed through the New Hire process more swiftly using a new option on the Configuration Template and Client Override forms. When the Manager SSN/DoB Entry on New Hire option is selected on these forms, managers can type in the new employee’s social security number and date of birth on the New Hire form in Employee Portal.

When the manager adds the SSN and DoB directly on the New Hire form, the new employee does not need to log in to Employee Portal and add in that information themselves. Instead, the employee Prehire record and Employee ID Number are generated immediately in the system, and the employee can proceed immediately with the Onboarding Workflow.

Once a manager enters the new hire’s SSN and DoB, both of these fields are set to read-only, and the SSN field is masked for security purposes. If these fields need to be changed, the New Hire record should be deleted and remade. In addition, this option does not impact existing records. If a new hire record was added without an SSN or DoB, the record should be deleted and recreated to access this feature.

In addition, when this option is selected, the Employee ID now displays on the New Hire Dashboard, and the Kiosk Code and Invite Link columns no longer display.

Note: Note: This option should only be selected when trusted managers have access to the new employee’s SSN and DoB.

JIRA # EP-9440, EP-9442, EP-9443, EP-9450, EP-9454, WSP-2378

========================================================================

Additional Gender Options for Dependents

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_09/Gender_Options_Dependents.htm Path: EP/Release-Notes/Enhancements/2025/R2025_09/Gender_Options_Dependents.htm

Additional Gender Options for Dependents

Employees can now select a Gender Designation for their dependents, just as they can for themselves. This update enhances personalization and supports inclusive data representation across the platform.

Note: Note: This feature is configurable. Service Providers can enable or disable it using the Hide Gender Designation setting in the Configuration Template.

JIRA # EP-9403

========================================================================

Additional Pronoun Options for Dependents

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_09/Pronoun_Options_Dependents.htm Path: EP/Release-Notes/Enhancements/2025/R2025_09/Pronoun_Options_Dependents.htm

Additional Pronoun Options for Dependents

Employees can now specify Preferred Pronouns for their dependents, just as they can for themselves. This enhancement supports more inclusive and personalized experiences across the employee experience.

Note: Note: This feature is configurable. Service Providers can enable or disable it using the Hide Pronoun setting within the Configuration Template.

JIRA # EP-9404

========================================================================

Display Report Center in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_09/Report_Center_In_EP.htm Path: EP/Release-Notes/Enhancements/2025/R2025_09/Report_Center_In_EP.htm

Display Report Center in Employee Portal

Service Providers can now embed reports and dashboards from Report Center into Employee Portal as menu items. The new Report Center (Embed) option now displays as a Menu Component option on the Configuration Templates form and the Client Override form. Select this option to display the Embed Code field and enter a URL to link a report from Report Center.

Using this option, Service Providers can embed a workbook or dashboard from the Next Gen Report Center directly into Employee Portal for managers. Managers can click the menu option to view the report. Managers can access the full range of Report Center’s features for selecting Views and utilizing Explore mode in the workbook if they have the appropriate permissions.

Using this feature, Service Providers can select specific workbooks and dashboards to grant to managers directly through Employee Portal, customize the available workbooks and dashboards for specific clients, and leverage the functionality of Report Center while controlling how much data is available to their customers.

JIRA # EP-9468, EP-9469, EP-9466, EP-9467, RC-6682, RC-6683, RC-6659

========================================================================

Employee Photo on My Employees Widget

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/My_Employees_Photo.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/My_Employees_Photo.htm

Employee Photo on My Employees Widget

Managers can now see employee photos next to their names on the My Employees widget. This enhancement mirrors the appearance of the My Approvals widget and the Birthday & Anniversary widget.

JIRA # EP-9495

========================================================================

Bulk Delete for New Hire Dashboard

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/New_Hire_Bulk_Delete.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/New_Hire_Bulk_Delete.htm

Bulk Delete for New Hire Dashboard

Managers can now delete records in bulk using the New Hire Dashboard. Checkboxes now display next to each new hire entry on the dashboard, and managers can click the Delete New Hires button with multiple entries selected to delete up to 10 entries at once. In addition, the Select All checkbox allows managers to select all entries currently displayed. With this enhancement, managers can clean out unnecessary new hire entries more swiftly.

JIRA # EP-8978

========================================================================

Editing Employee Record During Onboarding Disabled

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/New_Hire_Disable.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/New_Hire_Disable.htm

Editing Employee Record During Onboarding Disabled

When a new employee’s Onboarding Prehire record is created in the system, the fields on the Employee New Hire Form are now locked for the duration of the onboarding process. A banner now displays above the New Hire Dashboard entry for an employee indicating that the employee is undergoing the onboarding process. This change prevents conflicting edits to the employee record during the onboarding process.

JIRA # EP-9093

========================================================================

Enhancements to New Hire Form

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/New_Hire_Enhancements.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/New_Hire_Enhancements.htm

Enhancements to New Hire Form

The New Hire Dashboard in Employee Portal has been enhanced to ensure that fields and requirements on the form match the New Hire form in Prism.

The New Hire form in Employee Portal has been updated with a new layout. Fields are now grouped into four categories, which includes Employee Personal Info, Employment Details, Benefit Details, and Employee Pay Details. Fields have been repositioned as a result of this change, but no fields have been removed, and the page retains all existing functionality.

The Employee Type field has been renamed Employment Type, and the Pay Rate Basis field has been renamed Pay Rate Basis/Period. In addition, the SSN/DOB selector has been updated to use a button format.

JIRA # EP-9609

========================================================================

Enhancement to Direct Deposits Form

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/Payroll_Deduction_Improvement.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/Payroll_Deduction_Improvement.htm

Enhancement to Direct Deposits Form

The Direct Deposits form in Employee Portal now allows an employee to view and update their Checking and Savings accounts when other account types (such as Deductions) have been applied by a Service Provider. When the employee accesses the Direct Deposits form, account types other than checking and savings are hidden for security purposes.

Note: Note: This update covers direct deposit types other than Checking and Savings. The information for these deposit types are covered on the employee record on the Deposit tab of the Employee Details form in Prism Core.

JIRA # EP-4474

========================================================================

Payroll Approval Reports in Employee Portal

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/Payroll_Reports_Files.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/Payroll_Reports_Files.htm

Payroll Approval Reports in Employee Portal

Managers can now view certain reports on processed payrolls directly from Employee Portal. Select a payroll on the Payroll Approvals form and select the Reports & Files to display a list of the reports available to view or download.

The Payroll reports added to this form include the following:

These forms use the default parameters as established in the core Prism application. Select View to display the report in a new tab, or select Download to download the report.

JIRA # EP-9324

========================================================================

Customize Push Notifications

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/Push_Notifications.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/Push_Notifications.htm

Customize Push Notifications

Employees can now customize their push notification preferences for the PrismONE Mobile App. The new App Settings form includes the Notifications setting, which allows employees to opt in or out of specific types of notifications, including messages, time sheet notices, and PTO notices.

Note: Note: Push notifications are enabled by default, and employees are instructed on how they can opt in or out of notifications on their first login.

JIRA # APP-45, APP-128

========================================================================

PrismONE ID support for PrismONE Mobile App

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/Redirect_After_Logout.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/Redirect_After_Logout.htm

PrismONE ID support for PrismONE Mobile App

This release includes login support for employees with existing PrismONE ID accounts. The new login process includes full multi-factor authentication support for both authenticator apps and SMS/Text messages.

With PrismONE ID, employees no longer need to log in to Employee Portal or scan a QR code. Once authenticated, users can quickly and easily log in using a PIN or biometric data, and their credentials are retained until the standard expiration date.

In addition, employees who work for multiple companies can now easily switch between accounts during login or within the app using the new “Sign In to Another Account” option.

With these enhancements, employees can access Employee Portal more quickly and securely using the PrismONE Mobile App.

JIRA # APP-93

========================================================================

Present Resident and Worksite Location Tax Form Options

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Enhancements/2025/R2025_10/Tax_Form_Options.htm Path: EP/Release-Notes/Enhancements/2025/R2025_10/Tax_Form_Options.htm

Present Resident and Worksite Location Tax Form Options

Employees who live in one state and work in another can now select state tax forms for both states to comply with payroll regulations. When the employee goes to update their tax forms in Employee Portal, the option available now include both their home address and their worksite location.

JIRA # EP-9243

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202401.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202401.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-1960 When a manager viewed an employee’s I9 form for approval, the employee hire date displayed as “NaN/NaN/Nan”. This is fixed.
EERT-2119 Attempting to email a Benefits Confirmation Statement to an employee from the Employee Confirmation Statements form or the Other tab of the Employee Details form caused an error message to display. This is fixed.
EERT-2230 When an employee completed the Benefit Summary form during Benefits Enrollment, the form was not properly marked as completed, and the EP Benefit Enrollment Widget would continue to show that there were incomplete forms. This is fixed.
EERT-2232 When a user attempts to use special characters that are now permitted on the I9 Section 2 form, an error message displays to indicate this. However, the error message would overlap existing text on the screen, rendering both illegible. This is fixed.
EERT-2236 During the onboarding process, when a user enters a telephone number that begins with a 1 before the area code, the system interpreted the 1 as part of the area code and truncated the phone number, resulting in incorrect information. This is fixed. The system now accepts both 9-digit and 10-digit numbers. If the user types in more digits, an error displays so that they can fix the issue, rather than truncating the number.
EERT-2246 When a user selected to receive electronic W-2 forms during onboarding and accessed the W-2 form in Employee Portal, a message would display incorrectly informing the user that they had not enrolled in electronic W-2 forms. The employee was prompted to enroll in electronic W-2 forms, despite already being enrolled. This is fixed. Employee Portal now displays the employee’s electronic form enrollment status properly.
EERT-2249 When a user signed up for Voluntary Life or AD&D plans during Benefits Enrollment, the employee could enter 0 in the amount field and allocate zero dollars a month to a plan. This is fixed.
EERT-2277 When a user received an MFA code that started with 0 and entered the code to log in to Employee Portal, an error message displayed indicating an invalid code. The user could request a new code and still log in successfully. This is fixed. MFA codes beginning with 0 are now properly accepted.
EERT-2305 When a user attempted to save a change to an alert in Employee Portal, errors could occur which caused the system to stall or prevented the change from being saved. This is fixed.
EP-6530 When a user viewed the Messages form in the new UEX and only a single page of information displayed, the text displayed “Viewing 1 of NaN”. This is fixed. The text now properly displays “1 of 1” for a single page of Messages.
EP-6713 When an employee clicked the checkbox for Select All on the Messages form, messages would not be selected. However, clicking the text for Select All did select all messages. This is fixed. The checkbox now properly selects all messages, and the text no longer functions as a button.
EP-6807 When a worksite manager attempted to assign themselves as the PTO Approver for a New Hire employee on their team, they were unable to do so if any security restrictions were set. The manager could assign themselves as the PTO Approver if no security restrictions were set. This is fixed. Worksite managers can now assign themselves as PTO Approvers for their own teams.
EP-7059 When a user attempted to load the EP dashboard after login, when the Contact Us widget was enabled and the Photo option was not selected in the Display field, an error occurred. This is fixed.
EP-7279 When a user makes changes to a client override on the Client Overrides form, the changes were not immediately applied. Users needed to clear their caches before the changes displayed. This is fixed.
EP-7315 When a company using the new UEX set up a redirect on the login, and an employee logged in using the Legacy UEX, the redirect did not function properly, and the employee would be sent to the Employee Portal dashboard. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202402.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202402.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2309 The Employee Portal PTO Estimator did not properly account for Semi-Monthly pay schedule payrolls, causing the estimate to be incorrect. This is fixed.
EERT-2316 When a client with no rehire approval policy created a rehire approval in Employee Portal, the approval record would sometimes be left in the “P” (Pending) status, and the approval was not automatically cleared from the system. This is fixed.
EERT-2332 When an employee submits a PTO request and there were multiple pay groups in a payroll batch, an error message displayed, but the message did not include the proper text message. In addition, if there were multiple pay groups in a payroll batch with different pay period start dates, employees could incorrectly submit a PTO request for a date after the first pay period start date. This is fixed. Employees are now informed that the payroll period date requested has been closed. In addition, employees can no longer submit a PTO request for a date after the first pay period start date.
EERT-2339 When a user attempted to upload a document to or delete a document from the legacy version of the Document Repository, an error occurred, and the action could not be completed. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202404.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202404.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2298 For certain clients, notifications for enrollment workflows being submitted were not issued properly. When an employee submitted their enrollment, no notifications were generated. This is fixed.
EERT-2360 When an employee attempted to review their benefit confirmation statement on the Benefit Confirmation Statements form in Employee Portal, clicking the link displayed a blank page. This is fixed.
EERT-2368 The system used the wrong field to determine if an employee had enrolled in an Electronic W-2 form and eligibility for an early elect. As a result, the employee was incorrectly flagged as having already signed up for an early W-2. This is fixed.
EERT-2403 The Date Occurred field on the Life Event widget on the Employee Portal dashboard allowed the employee to indicate an event that a Life Event had or will occur. However, The Date Occurred field on the Life Event form displayed the date that the life event was submitted into the system. This is fixed. The field has been renamed Date of Event on both forms, and the field now properly indicates the date that the event had or will occur.
EERT-2409 When an employee’s address was changed in Employee Portal, and that address included a secondary Address line for elements such as an apartment number, the information was combined into a single line. In addition, when the address connected many words in a single line, an error message would occur. This is fixed.
EERT-2412 When a terminated employee attempted to access Employee Portal to review their W-2 information, the employee could access the Employee Portal dashboard, but attempting to access other forms resulted in an error message. This is fixed.
EP-6959 When a user attempted to search for a default template on the Configuration Templates form and only the original default template existed, the search would yield no results. This is fixed.
EP-7357 When a manager attempted to add a Position Code in the Employee Type field on the New Hire Entry form, position codes did not display properly if they had not been opened in PrismHR and saved. This occurred if the position codes were imported through the data import tool. This is fixed.
EP-7409 When a terminated employee attempted to log in to Employee Portal, and the Terminated UEX Template was in use, the terminated employee receive an error message. This is fixed.
EP-7431 When an employee attempted to select a PTO approver on the New Hire form in Employee Portal, the PTO Approval field displayed no employees, and the search function would time out. This is fixed.
EP-7476 On the Birthdays and Anniversaries widget on the Employee Portal Dashboard, the dates were one day prior to the actual date of the employees’ birthday or anniversary. This is fixed.
EP-7504 The Support Center option displayed in the mobile view of the new UEX in Employee Portal, even if the Support Center option was disabled in settings. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202405.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202405.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EP-7764 When a client used the Upgrade Additional Clients option on the Configuration Templates form to upgrade more than 512 clients, an error occurred. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202407.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202407.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
ADMP-595 When a worksite manager made changes on the Pay Details form, the Department, Project, Division, and Position dropdown selection menus would sometimes not display all possible entries. This is fixed.
EERT-2491 When an employee went through the Onboarding process in Employee Portal, and the New Hire Question for the State Rule of the Worksite Location was enabled, an error occurred. If the new hire question was removed, the employee could complete the Onboarding process successfully. This is fixed.
EP-7651 When a user displayed the Total Compensation form, and the employee and employer contributions were both $0.00, the value would still display on the graph. This is fixed. Values of $0.00 are now properly truncated from the Total Compensation form.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202408.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202408.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2456 When certain users attempted to change their mailing addresses in Employee Portal, the system would mistakenly correct the address to a different city based on the geocode. This is fixed.
EERT-2475 When a user added the Paid Time Off widget to the Employee Portal dashboard without adding the Paid Time Off menu, the Request Time Off and View All options did not display correctly. This is fixed.
EERT-2527 When a user reviewed the Alerts Activity form for certain employees, no information would display. The Alerts Activity report in Report Center could be used to display the correct information. This is fixed.
EERT-2538 When a user displayed the Paid Time Off widget on the Employee Portal dashboard, and the Time Off menu component was disabled on the configuration template, the widget incorrectly displayed a message indicating that the employee had no available PTO. This is fixed.
EERT-2540 When a user set the Multiple Jobs field on the Tax Withholding form to Yes, then added an additional state withholding form, the Multiple Jobs field incorrectly reset to No. This is fixed.
EERT-2556 When a user entered a Reason Code for a Position change or a Status Type change using the HR Action forms in Employee Portal, the reason codes did not properly match the rules determined by the Client Details form. This is fixed.
EERT-2572 When a user added the My Benefits Widget to their dashboard, the widget displayed the same plan multiple times and incorrectly displayed the Payee field as Not Needed. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202410.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_MR_202410.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2457 When the Onboarding process finished, the employee’s W4 did not properly display the first date of employment. This is fixed. The W4 now displays the Start Date of Employment that is present on the employee’s I-9 documentation.
EERT-2614 When a manager attempted to use the Manager Portal to terminate an employee with a benefits record, and the manager attempted to assign a COBRA qualifying event, the dropdown selection displayed benefit plan names instead of COBRA Qualifying Events. In addition, creating the COBRA record was not logged in the proper auditing format. This is fixed.
EERT-2626 When approved PTO was cancelled, and the employee was listed as reporting to a manager who had been terminated, the approved PTO cancellation notification was sent to the terminated manager’s personal email address. This is fixed.
EERT-2636 When a configuration template disabled the Spanish Language selection toggle, the language selection option still displayed in the account dropdown menu. This is fixed.
EERT-2644 When a user attempted to enter a position in the Position field on the New Hire Dashboard, significantly long position codes wrapped around to the next line and caused overlapping text. This is fixed.
EP-8032 When an employee viewed an upcoming paycheck in the Pay Widget in Employee Portal, and the pay date was changed or processed early, the pay date displayed incorrectly and did not account for the updated pay date. This is fixed.
EP-8068 When a manager accessed the Employee Termination form, a History tab displayed, despite the system not supporting a termination history. This is fixed. The History tab no longer displays on this form.
EP-8268 The Template History link displayed on the Client Override form, but the functionality for this link is not yet implemented and intended for the November 2024 release. This is fixed. The link has been removed temporarily from the form.
EP-8281 When a user attempted to upload an image for the Background Image on a Configuration Template, the file size was restricted below the standard 300KB. This is fixed. Background images now have the proper maximum file size of 300KB.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202403.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202403.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2284 When a manager processed Section 2 of the I9 form, the manager’s name was not properly added as the Approver on the Dashboard. This is fixed.
EERT-2335 When a hiring manager entered an employee’s Personal Email address as part of the New Hire process and the employee did not enter a Personal Email address on the I-9 or Employee Info forms, the Personal Email record did not update properly. In addition, if the employee entered a different Personal Email address than the hiring manager, the employee’s entry was not properly saved. This is fixed.
EERT-2337 When an employee entered a PO Box number in the Employee Portal W-2 Address field in Employee Portal, the city and state of the PO Box were not properly saved to the employee’s Prism record. This is fixed.
EERT-2356 The PEO_NAME substitution variable did not resolve to the client’s legal name in the W2 Elect Terms section on the W-2 Election Configuration form. This is fixed.
EP-4815 When a user selected a template on the Configuration Templates form, an error message displayed if a menu or widget was assigned to a missing/deleted segment. However, this error message showed a generic message instead of the proper description. This is fixed. The error message now displays information to help identify which segments are invalid and which menus or widgets are causing the issue.
EP-7074 If a user entered 225 characters in the Title field for a Dashboard widget in Employee Portal, the Edit window no longer functioned properly. In addition, if too many characters were entered in the Title, the Edit window did not scale properly on screen. This is fixed.
EP-7420 When a user with multiple PTO plans accessed the Paid Time Off form in the new UEX, the pagination buttons did not display, preventing the employee from viewing additional plans on the form. This is fixed.
EP-7590 When an employee accessed the Manager View in the New UEX in a Chrome browser with Responsive Design Mode enabled in their browser settings, an error message displayed. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202406.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202406.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2417 When a newly terminated employee unaware of the termination accessed Employee Portal to update their work email address, a message displayed indicating that work emails cannot be set for a terminated employee. This is fixed. Terminated employees are now informed that they cannot update their email at this time and instructed to contact their HR manager.
EERT-2424 When a user displayed taxes on the Tax Withholding form in Employee Portal, and Block Withholding is selected as an Override type on the Tax tab on the Client Details form, some states did not properly display the Exempt From State Withholding? Field. This is fixed.
EERT-2429 When an employee viewed a life event on the Life Events widget that was initiated by a service provider or manager, the event would incorrectly display as being initiated by the employee. In addition, the Completed By field displayed incorrect information when benefit rules were used to determine the completion date. This is fixed.
EERT-2445 When a manager attempted to edit an employee record using the New Hire Dashboard, and the manager security settings only included Full Access for a single entity, an error occurred. If the manager had Full Access to at least two entities in their security settings, they could edit employee records normally. This is fixed.
EERT-2454 When an employee attempted to cancel a leave request on the Paid Time Off form that had already been approved then clicked No on the confirmation message, an error occurred. This is fixed.
EERT-2459 When an employee navigated to the Tax Withholding form in Employee Portal, an error message displayed for certain employees. This is fixed.
EERT-2464 When an employee attempted to log in to Employee Portal in the new UEX using an iPhone and the employee’s browser version was from before 2022, an error message displayed. However, the error message did not provide sufficient information. The error message now specifies that the employee needs to update their browser to access Employee Portal.
EERT-2465 When a manager added an employee through the New Hire Dashboard and the employee began working through Onboarding, the Hire Status field did not properly update and continued showing the employee in Not Started status. This is fixed.
EP-7650 On the Benefits tab on the Total Compensation dashboard, the Description column did not properly display. This is fixed.
EP-7654 On the Taxes Breakdown tab on the Total Compensation form in Employee Portal, the company contributions to taxes were erroneously labeled “-employee”. This is fixed.
EP-7947 When a worksite manager attempted to review pending leave requests in Employee Portal, the Leave Date field did not properly display on the requests. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202409.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202409.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
ADMP-429 When a rehired employee went through the new hire process in Employee Portal, the new hire questions did not display in the proper format. This is fixed.
ADMP-545 When a manager applied a leave request for an employee in Employee Portal and a second leave request for that employee was approved, the Updated Hours field on the Leave Details form displayed incorrect information. This was only a display issue, and the information was applied correctly on the time sheet. This is fixed.
ADMP-556 When a user set the language in Employee Portal, the Leave Request Summary Table status column was not resized to accommodate the translated text. This is fixed.
ADMP-565 When a time sheet containing only a single employee was set to Ready for Time Entry status, and a user finalized the time sheet, the Payroll Status field incorrectly displayed as blank. Closing the form and returning to page caused the field to correctly display as Time Sheet Entry in Progress. This is fixed.
EERT-2554 When a PTO plan had a Usage Waiting period selected on the PTO Benefit Plan form, the waiting period was not applied properly to leave requests, and employees could request time off during the waiting period. This is fixed.
EERT-2559 When a new employee was hired through the New Hire Dashboard in Employee Portal, a prehire record was not created, and the employee could not begin the Onboarding process. This is fixed.
EERT-2596 For certain clients, employees were unable to update their residential address in Employee Portal, and the Verify Address button remained greyed out even when changes were applied to the Address form. This is fixed.
EP-8011 When an employee attempted to view their annual salary on the Employment Summary form in Employee Portal, the salary did not display if the employee did not have an assigned manager. This is fixed.
EP-8183 When a terminated employee logged in to Employee Portal to view exiting documents, the user could view documents as though they were still an active employee. This is fixed.
EP-8202 When a user attempted to preview a document included on an alert on the Alerts form, an error occurred. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202411.htm Path: EP/Release-Notes/Fixes/2024/EP_Fixes_QR_202411.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
ADMP-662 When a Pay Code was set in Prism to allow description overrides, several forms in Employee Portal did not properly display the override description, including the Time Sheet Summary form, Detail Time Sheet Entry form, and Time Sheet Review form. This is fixed.
ADMP-693 When a Service Provider imported a new hire record from Employee Portal into Prism, the Hired By field on the employee record in Employee Portal displayed as blank. This is fixed.
ADMP-694 When a Service Provider imported a new hire record from Employee Portal into Prism, and the PTO approver was a Worksite Trusted Advisor, the Welcome email sent to the new hire did not display the HR Supervisor’s name. This is fixed.
ADMP-713 When a Worksite Manager attempted to rehire an employee using the Rehire HR Action in Employee Portal, an error occurred. This is fixed.
EERT-2641 When an employee was enrolled in a benefit plan and calculated accrual amounts in Employee Portal on the Paid Time Off form, the Estimate PTO feature did not properly account for Seniority Level when calculating future PTO accrual amounts. This is fixed.
EERT-2655 When calculating accrual amounts in Employee Portal, the Estimate PTO feature on the Paid Time Off form did not properly account for the Benefit Start Date on the Employee PTO Registers form in PrismHR, resulting in incorrect calculations. This is fixed.
EERT-2681 When an employee in a PTO plan with a seniority tier greater than 82 months attempted to use the PTO Estimator feature to determine their PTO, the estimator did not calculate hours correctly. This is fixed.
EP-7754 When a user edited a menu for a template on the Configuration Templates form in the New UEX, the clock icon from the legacy UEX was not available as a menu icon. This is fixed.
EP-8326 When an employee was within the usage wait period for PTO and attempted to view their accrued PTO, no hours displayed. This is fixed. Employees can now view their accrued PTO while they are within the usage wait period.
EP-8467 When a Trusted Advisor selected SMS/Text as their MFA option and attempted to log in to Employee Portal, only the option to send an email for MFA displayed. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_MR_202501.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_MR_202501.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2625 When a user hired an employee via the New Hire Dashboard in Employee Portal, the Benefit Group field on the New Hire Form did not exclude retirement-only benefit groups. This is fixed. Users will no longer see retirement-only benefit groups in this field.
EERT-2635 When a worksite manager who works for two companies attempted to create a segment on the Segments form, the company name on the segment could switch or disappear, and an error message could display that prevented creating the segment. This is fixed.
EERT-2643 When an user searched for employees using the Add Employees form on the Segments form, the search results did not display a complete list of matching employees if the user searched by last name. This is fixed.
EERT-2645 When a Worksite Manager attempted to terminate an employee who never completed registration for Employee Portal, the termination failed. This is fixed. The employee is now terminated even if they have not completed their registration.
EERT-2653 When a manager approved a PTO request using Employee Portal, the manager’s name did not display as the PTO Approver on the record. This is fixed.
EERT-2671 When an employee had accrued the maximum amount of PTO allowed for their plan, the PTO estimator continued to display future accruals that exceeded the maximum. This is fixed.
EERT-2676 When an employee’s preferred language was set to English, text in the footer of an Alert displayed the Spanish version. This is fixed. When an employee’s preferred language is set to English, all sections of the Alert now display in English.
EERT-2698 When a manager attempted to send a password reset link to an employee using Employee Portal, an error message displayed. This occurred for both email and SMS reset links. This is fixed.
EERT-2732 When a manager changed employee summary information using Employee Portal, the employee’s last hire, original hire, and last review dates would increase by one day. This is fixed.
EERT-2757 When a user viewed upcoming paychecks in the Pay Widget in Employee Portal, the widget should only display the date of the next regularly scheduled payroll. However, if a manual payroll was processed, that date would display instead. This is fixed.
EP-5424 When a user attempted to sort the Activity tab on the Employee Portal Alert form, only the Company Name column sorted properly. This is fixed.
EP-7574 When a user attempted to switch their preferred language to Spanish, an error occurred if the Enable Additional Languages option was not enabled on the Global Configuration form, even though Employee Portal does not use this configuration option. This is fixed. Employee Portal now properly disregards the Enable Additional Languages option on the Global Configuration form.
EP-8478 When a user attempted to duplicate a segment on the Segments form, an error occurred for certain segments. This is fixed.
EP-8576 When a Worksite Trusted Advisor made changes to the Employment Summary form in Employee Portal and attempted to save the changes, an error occurred. This is fixed.
EP-8732 When a worksite manager who has access to a client but is not an employee of that client attempted to log in to Employee Portal via SSO, an error occurred. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_MR_202502.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_MR_202502.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2605 When a Worksite Manager initiated a leave request in Employee Portal on behalf of an employee, and the leave request was approved, the approval confirmation email was sent to the Worksite Manager instead of the employee. This is fixed.
EERT-2637 When new hire questions were marked as mandatory on the New Hire Questions form, this requirement was not properly enforced, and new hires could navigate through the process while leaving the questions blank. This is fixed.
EERT-2691 When records on the New Hire Entry form in Employee Portal contained fields with too many characters, the fields displayed incorrectly for certain screen settings. This is fixed.
EERT-2768 When a user views upcoming paychecks in the Pay Widget in Employee Portal, the widget should only display the date of the next regularly scheduled payroll. However, when a Manual or Special payroll batch was processed for an employee, that date displayed instead. This is fixed.
EERT-2777 When a manager edited the Last Hire Date, Last Review Date, or Next Review Date on the Employment Summary or Personal Info form in Employee Portal, the date saved as the day before what was entered. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_QR_202503.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_QR_202503.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2706 When a user selected Appy to Clients on the Configuration Template form, performed a search, then cleared the search, previous selections from the Apply to Clients feature were deselected. This is fixed.
EERT-2726 When the early W-2 election configuration was not set up on the W-2 Election Text form, the early W-2 election sections still displayed on the W-2 form in Employee Portal. This is fixed.
EERT-2776 When a manager made a change to the Employment Summary form in Employee Portal, the employee’s email address was deleted. In addition, accidental deletions prior to 2025 displayed the email address as being deleted by an unknown user. This is fixed.
EP-8810 When an employee displayed the Retirement Summary form in Employee Portal, the Contribution Rates fields displayed future-dated effective rates instead of the current effective rates. This is fixed. When future-dated rates are entered in the system, they do not display in Employee Portal until the date they are supposed to come into effect.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_R202505.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_R202505.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2667 When a client with a single Employer ID attempted to enter a new hire using the New Hire Dashboard in Employee Portal, an error message occurred indicating that the Employer ID was required, even though that field was automatically populated. This is fixed.
EERT-2742 When an employee had a direct deposit account using the Percentage method and switched to the Fixed method, the employee could still enter a Maximum amount and save the record. This is fixed. The Maximum field is now disabled when the employee switches to the Fixed method.
EERT-2766 In the Pay widget in Employee Portal, if the latest pay date displayed on the last day of the year, the pay date displayed as the following year. For example, 12/31/2024 would display as 12/31/2025. This is fixed.
EERT-2829 When a user created a segment on the Segments form and clicked Add Employees on the form, the search results displayed the list of employees correctly. However, clicking Add Employees again caused the search results to display incorrectly. This is fixed.
EERT-2853 When the system parameters were set on the Termination Parameters form to allow termination dates to be more than a set number of days in the future if the user confirms a message, when the user selected Yes on the termination message, an error occurred. This is fixed.
EERT-2861 When a Worksite Location had the Remote Location option enabled in Prism, tax forms in Employee Portal still used the worksite location geocode instead of the employee’s resident geocode for tax calculations. This is fixed.
EERT-2864 When an employee’s User Role was set to hide the Employee Portal username on the Employee Details form, the name did not display on the form in PrismHR, but worksite managers could see the name on the Employee Details form in Employee Portal. This is fixed.
EERT-2866 For some clients, documents displayed using the pre-UEX Default template instead of the Default UEX template, even if the company was assigned to use the Default UEX template. This is fixed.
EERT-2870 When an employee submitted a PTO request that was not a whole number the PTO Calendar list view in Employee Portal displayed the request as only a whole number with .00 in the decimal place. For example, a request of 1.5 hours displayed as 1.00 hours. This is fixed.
EERT-2882 When the Email Address, Mobile Phone, and Employee Number fields were marked as required fields on the New Hire and Dependent Field Overrides form in Prism, the New Hire Dashboard did not properly make these fields required. This is fixed.
EP-8493 When a user searched the Client Override form by Client Number, the Status filter did not properly filter results. This is fixed.
EP-8828 If a segment had more than 334 employees included, Service Providers were unable to open the segment on the Segments form and received an error message indicating that they did not have access to all clients on the segment. This is fixed.
EP-8966 When a manager attempted to navigate the My Employees form using the keyboard, the employee was unable to select employees from the list or view additional pages of employees. This is fixed.
EP-9072 When a client enabled the Redirect After Logout feature on a Configuration Template for Employee Portal to implement a Vanity URL, the system did not redirect users to the specified URL correctly. This is fixed.
EP-9177 When a Worksite Manager attempted to save a Segment that has the same name as another Segment in Employee Portal, an error occurred. This is fixed. The Worksite Manager now receives a message indicating that the segment name already exists.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_R202506.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_R202506.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2773 If a cross hire employee record existed on multiple clients, and the employee updated their Mailing Address through Employee Portal, the Mailing Address field was only updated for the client that the employee was currently logged in to. This is fixed. The Mailing Address field now updates for the employee record across all clients that they have access to.
EERT-2793 When an employee was going through the Onboarding process with a status of Onboarding in Progress - Payroll Suppressed (save is disabled), the manager could still make changes to the employee’s record through the My Employees form in Employee Portal. This is fixed. Editing the employee record is now disabled until the Onboarding process is complete or suspended with payroll active.
EERT-2817 When a manager attempted to filter results on the PTO Team Calendar form using the PTO Type field, the results were not filtered properly when the PTO Type field was changed multiple times. This is fixed.
EERT-2819 On the Total Compensation Report, when an employee has a negative amount for the Employer contribution, the text did not display properly and overlapped with the displayed chart. This is fixed.
EERT-2826 When a user removed the date of birth from an employee record on the Personal Info tab in Employee Portal and attempted to save the changes, an error occurred. This is fixed. The Date of Birth field is required, and a message now displays indicating that the required field must be filled out before the record can be saved.
EERT-2887 When a worksite manager did not have access to view pay rates and entered time values on the Detail Time Sheet Entry form in Employee Portal, the time sheet displayed a $0 pay rate until the manager tabbed through the details and saved the entry. This is fixed. Both the hours and associated pay rate now populate properly on the time sheet.
EERT-2901 When a manager used Employee Portal to enter a rehire record and did not have access to Employee Pay on their user role, a message displayed incorrectly indicating required fields were missing information, even though no such fields displayed. This is fixed. Managers no longer require Employee Pay permissions to enter a rehire through Employee Portal.
EERT-2905 On the Employee PTO Calendar in Employee Portal, PTO requests for partial days displayed a value rounded to the nearest fifteen minutes instead of the exact hour and minute value entered on the request. This is fixed.
EERT-2916 When a user attempted to delete clients from the Segments form, the form only displayed up to 10 clients. This is fixed.
EP-5296 When a user entered a date or partially filled out the Direct Deposit Acceptance Text form in Prism, then left the screen without clicking Save or Cancel, Employee Portal would display a blank Acceptance Text message when a user updated their Direct Deposit form. This is fixed.
EP-9300 When a user accessed an employee’s Employee Portal using the proxy login feature, the proxy user could view the employee’s PrismONE Mobile QR Code. This is fixed. Proxy users can no longer view the PrismONE Mobile QR Code, just like 3rd party widgets.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_R202507.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_R202507.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2834 When a user downloaded the Client Allocation Report as a CSV file from Employee Portal, the data did not match the values in the same report downloaded as a CSV file from Prism. This is fixed.
EERT-2918 When bank accounts were added or changed in Employee Portal, the accounts were not properly set to Pending status, and prenotes were not created properly. This is fixed.
EERT-3001 If a user added, removed, or updated Direct Deposit accounts in the Employee Portal when no approval policy was in place, any unchanged accounts were reverted to Prenote (Pending) status. This is fixed.
EP-9023 When a manager attempted to edit a new hire’s First or Last Name from the New Hire Dashboard while the new employee was in Onboarding, the manager’s edits were not properly saved. This is fixed. Managers can now make edits on the New Hire form to the First and Last Name while the employee is going through the Onboarding process. > Note: Note: If a manager changes the employee’s First Name and Last Name, the onboarding process must be restarted. A message prompt displays when a manager attempts to edit these fields to require confirmation before the edit is saved.
EP-9111 When a user made changes to information on the Direct Deposit form in Employee Portal, navigated to another menu, and selected Yes, I want to leave on the confirmation message, an error occurred. This is fixed.
EP-9322 When a manager added a new hire’s personal and work email addresses and saved the form, the work email was incorrectly saved with the personal email address. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_R202508.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_R202508.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2915 When a user entered emergency contact information onto the Emergency Contacts form in Employee Portal, the phone number was not properly formatted. This is fixed.
EERT-2948 When a worksite manager attempted to add a rehire through Employee Portal, the rehire process could not be completed if the manager did not have access to the Employee Pay on their User Role and if the Rehire User Role process has the Pay Rate Hidden option selected. This is fixed.
EERT-2954 Worksite Trusted Advisors were able to access Segments in Prism, however, they were not able to save any changes they made. This is fixed. Worksite Trusted Advisors now only have access to Segments in Employee Portal. Changes to Segments in Employee Portal can be saved normally.
EERT-2971 When an employee Status was set to Selectable by Service Provider Only, Worksite Managers and Worksite Trusted Advisors could still select that Status for a new hire on the New Hire Dashboard. This is fixed.
EERT-2984 When a Worksite Manager attempted to rehire an employee who had not yet registered in Employee Portal, an error occurred. This is fixed. Employees with or without an Employee Portal User ID can now be rehired.
EERT-2997 When a manager added a cross-hire employee on the New Hire Dashboard, and the cross-hire employee already had an Employee Portal username from another company, the prehire record was not generated properly, and the onboarding workflow did not initiate. This is fixed.
EP-8338 When an employee acknowledged an alert, the Proof of Signature section of the form cut off a portion of the text in the final, saved version of the document. This is fixed.
EP-9365 When a Service Provider used the Proxy Login feature to log in as an Employee, the Service Provider could edit rates on the Retirement Summary form. This is fixed. The Retirement Summary form is now set to read-only during a Proxy Login session.
EP-9374 When an employee was actively employed by two clients and completed their federal and state tax withholding forms, the employee record was not properly updated for both clients. This is fixed.
EP-9392 When a user viewed the Veteran Status form on a mobile device, portions of the text were cut off. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_R202509.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_R202509.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2923 When a user entered their last name with a space at the end in Employee Portal, the system did not properly truncate the extra end space, which could create errors due to the name not matching other content. This is fixed.
EERT-2939 When a user viewed the Direct Deposit Acceptance text on the Direct Deposit form in Employee Portal, the conditions section of the form displayed incorrectly as HTML code instead of the terms and conditions. This is fixed.
EERT-2951 When a manager used the Time Sheet Entry form in Employee Portal to enter hours with a non-productive pay code, the Hours Worked field was incorrectly filled in automatically with the amount. This is fixed. Non-productive pay codes do not add to the Hours Worked field.
EERT-2959 On the Add/Edit Dependent form in Benefits Enrollment, the Primary Phone, Work Phone, and Email forms did not use the standard formatting used throughout the rest of Employee Portal. This is fixed.
EERT-3003 When a Worksite Manager viewed the Approvals form in Employee Portal, client approvals did not display properly, even though those approvals did display in Prism. This is fixed.
EERT-3017 When a user attempted to add a Direct Deposit account through Employee Portal, and the method and amount were the same as an inactive Direct Deposit account on the employee record, the system displayed a message indicating the new account was saved but did not actually save the record correctly. This is fixed.
EP-8824 When a user who could only navigate via the keyboard attempted to complete the I-9 form, numerous options could not be reached via keyboard navigation, including scrolling, buttons to approve or deny forms, or the Electronic Signature. This is fixed. Accessibility has been improved to ensure that keyboard-only users navigate, fill in, close, approve, and deny I-9 forms.
APP-52 When a user clicked a link on a 3rd party widget in the PrismONE Mobile App on an Android device, the links did not function properly. This is fixed.
APP-62 When users logging in with the PrismONE Mobile App attempted to punch in using the TimeCo widget or menu item, an error occurred. This is fixed.
APP-71 When a user entered their PIN incorrectly, reauthenticated their User ID, and logged in from another device, attempting to log in from the first device triggered the reauthentication requirement again. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_R202510.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_R202510.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
APP-124 When users accessed the PrismONE mobile app with certain Android devices, the header menu bar overlapped with some native phone elements, such as the clock and battery life indicator. This is fixed.
EERT-2970 When a user viewed the Pay tab on the Total Compensation Report in Employee Portal, if the bar graph for a row was shorter than the dollar amount text, the dollar amount text overflowed on the graph and overlapped with the name of the row. This is fixed.
EERT-2995 When users viewed the Time Sheet Entry form in Employee Portal and attempted to view the next page, the pagination did not function properly, and the user could only view the first page on the form. This is fixed.
EP-9658 When a user’s session timed out in Employee Portal, the Redirect After Logout feature did not properly redirect the user. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Fixes/2025/EP_Fixes_R_202504.htm Path: EP/Release-Notes/Fixes/2025/EP_Fixes_R_202504.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2576 When an employee viewed tax information using Employee Portal, the Additional Withholding (per paycheck) override type would display for all options instead of the selected override type. This is fixed.
EERT-2583 When an employee was hired by a manager using the New Hire Dashboard in Employee Portal, and the employee attempted to register using a mobile device, the registration form did not display properly. This is fixed.
EERT-2599 If a Worksite Manager had full security access to at least one field on the Contact Info form in Employee Portal, but work email addresses were hidden for the worksite manager’s user role, the worksite manager was unable to edit contact information on an employee’s record. This is fixed.
EERT-2608 When a user set up a Direct Deposit account with the Remainder method, then added an additional Direct Deposit account with the 100% value, the 100% account was not saved properly. This is fixed. The user is now shown a message that indicates the issue, which reads “The sum of your accounts is more than 100%. Please make the amount values less or equal to 100%.”
EERT-2684 If the maximum number of direct deposit accounts allowed for an employee was reduced using the Direct Deposit Form Settings form, and an employee’s direct deposit accounts exceeded the new limit, attempting to access the employee’s Direct Deposits form resulted in an error. This is fixed.
EERT-2705 When a Worksite Manager attempted to access the My Approvals form to view an approval, an error occurred. This is fixed.
EERT-2750 If an Onboarding workflow is suspended and the option to allow the employee to access Employee Portal is selected, the employee status remains open on the New Hire Dashboard instead of being marked as Completed. This is fixed.
EERT-2756 If an Employee Status Code did not allow Termination as an Allowed Action Code on the Employee Statuses form, employees with that status code could still be terminated through Employee Portal. This is fixed. A message now displays indicating the HR action is not allowed for that employment status or type, and the Termination action is not performed.
EERT-2760 When a segment targeting active employees was assigned to a manager menu item in Employee Portal, worksite trusted advisors were unable to see the menu item since they lacked an employee record. This is fixed.
EERT-2788 When a user reviewed Benefit Groups on the New Hire Dashboard in Employee Portal, benefit groups past their stop dates still displayed. This is fixed.
EERT-2808 When a Service Provider enabled payday notifications on the Client Details form, notifications still displayed as disabled in Employee Portal. Employees could still enable the notifications by opting in on the Employee Portal form, but it could not be enabled by default. This is fixed.
EERT-2811 When an employee received PTO from two different plans, the PTO Estimator calculated upcoming PTO incorrectly. This is fixed.
EP-6833 On the PTO Approvals form, the Comments field did not have a character limit, and comments with too many characters would display as cut off mid-sentence on the Approvals Summary record. This is fixed. The field is now limited to 200 characters.
EP-7455 When a service provider edited the Birthdays & Anniversaries widget on a Configuration Template, the Widget Visibility field displayed options to have the widget display for employees, despite the widget being restricted to only display for managers in Employee Portal. This is fixed. The Widget Visibility field now properly reflects that this is a manager-only widget.
EP-7687 When a user viewed a dropdown list on the My Employees form, and the browser window height was low, the dropdown form was cropped improperly. This is fixed.
EP-8868 When a manager entered new standard hours or new default T/S hours on the Status/Type Change form in Employee Portal, the manager was required to enter hours in a decimal point format. This is fixed.
EP-8870 When an employee entered an address on forms in Prism and was given an option to select a city, only one city displayed, even if there were multiple cities with that name. The employee could not change the city if it was incorrect. This is fixed.

========================================================================

Estimate PTO Returns Error for Global PTO Plans

Source: https://tech-docs.prismhr.com/SP_help/Content/EP/Release-Notes/Known-Issues/2024/Known_Issues_QR_202403.htm Path: EP/Release-Notes/Known-Issues/2024/Known_Issues_QR_202403.htm

Estimate PTO Returns Error for Global PTO Plans

If an employee on a Global PTO plan selects Estimate PTO on the Paid Time Off form, an “NA” message occurs. Global PTO plans are not applicable to the PTO estimator. Service Providers using Global PTO plans for employees can hide the Estimate PTO feature using the enhancement in this release.

This issue will be fixed in an upcoming release.

JIRA # EP-7374

========================================================================

Account Selection on Login

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2024/QR_202409/Account_Selection_Login.htm Path: IAM/Release-Notes/Enhancements/2024/QR_202409/Account_Selection_Login.htm

Account Selection on Login

Employees who are assigned to multiple [ASO] companies can now select the current Active Company using a new option on the Employee Portal sign-on form. Click the company name in the dropdown menu to access a list of all assigned companies. When an employee selects a company, Employee Portal displays information for only that company. Employees can switch their current Active Company using an option on the Account dropdown menu in Employee Portal.

JIRA # IAM-936

========================================================================

PrismOne ID Feature Code

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2024/QR_202409/Feature_Code.htm Path: IAM/Release-Notes/Enhancements/2024/QR_202409/Feature_Code.htm

PrismOne ID Feature Code

A new client custom feature code, GLOBAL-ID-SIGN-IN-BUTTON-PHR, is now available on the Client Details form. Enabling this custom feature code adds a sign-on button to the PrismHR Login form which directs users to the PrismONE ID login feature.

JIRA # IAM-1314

========================================================================

PrismONE ID Now Available

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2024/QR_202409/PrismONE_Now_Available.htm Path: IAM/Release-Notes/Enhancements/2024/QR_202409/PrismONE_Now_Available.htm

PrismONE ID Now Available

PrismONE ID is a new cutting-edge Identity Management solution designed specifically for the PrismHR product suite that streamlines access across all PrismHR applications by enabling users to authenticate with a single, unified identity. From simplifying user management and enhancing security to ensuring integration and a consistent user experience across all PrismHR products, this next-generation solution will help users save time.

Existing PrismHR users already have PrismONE ID their activated.

Enabling PrismONE ID is accomplished by applying a series of feature codes that will either invite or require users to self-register, just after logging into PrismHR or Employee Portal (EP). For more information on PrismONE ID, consult the implementation guide on the CRC.

JIRA # IAM-1318

========================================================================

Require Mobile Number on Registration

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2024/QR_202409/Require_Mobile_Number.htm Path: IAM/Release-Notes/Enhancements/2024/QR_202409/Require_Mobile_Number.htm

Require Mobile Number on Registration

Employees are now required to enter a mobile number when registering through the PrismOne login form. After entering their first name, last name, mobile number, and password on registration screen, employees must verify their mobile number before proceeding with registration.

JIRA # IAM-1296

========================================================================

Enhancement to Block Email MFA Fallback Feature Code

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Apr/Block_Email_Fallback.htm Path: IAM/Release-Notes/Enhancements/2025/Apr/Block_Email_Fallback.htm

Enhancement to Block Email MFA Fallback Feature Code

The custom feature code BLOCK-EMAIL-MFA-FALLBACK will now check a worksite manager’s Employee Details form if the worksite manager does not have a mobile number on the Users form. If the worksite manager does have a mobile number on the Users form, this number is prioritized over the Employee Details information.

JIRA # IAM-1795

========================================================================

Disable Local Login Feature Code

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Apr/Disable_Local_Login.htm Path: IAM/Release-Notes/Enhancements/2025/Apr/Disable_Local_Login.htm

Disable Local Login Feature Code

A new client custom feature code, GLOBAL-ID-DISABLE-LOCAL-LOGIN, is now available on the Client Details form. Enabling this custom feature code blocks access to the legacy login screens for PrismHR Core and PrismHR Employee Portal (EP).

If a client has a custom Identity & Access Management (IAM) system configured, PrismHR and/or EP will redirect the user to that URL. If not, PrismHR and/or EP will redirect the user to PrismONE ID.

Note: Note: Clients should only apply this feature code once all known users have registered for PrismONE ID or the client is managing their own own IAM system.

JIRA # IAM-1697

========================================================================

Enhancement to PrismOne Login Indicating Disabled Accounts

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Apr/Disabled_Account_Indicator.htm Path: IAM/Release-Notes/Enhancements/2025/Apr/Disabled_Account_Indicator.htm

Enhancement to PrismOne Login Indicating Disabled Accounts

When a user had multiple Employee Portal users linked to a single PrismONE ID account, and one of the user accounts was disabled, the disabled account was not properly labeled on the PrismOne login form. The account is now greyed out and cannot be selected to indicate that it is disabled.

JIRA # IAM-1705

========================================================================

Enhancement to Forgot Password Process

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Apr/Forgot_Password_Enhancement.htm Path: IAM/Release-Notes/Enhancements/2025/Apr/Forgot_Password_Enhancement.htm

Enhancement to Forgot Password Process

When a user tries to reset a password, but has no multifactor authentication factors set up, a prompt now informs the user that the process is unavailable and instructs them to contact their manager.

JIRA # IAM-1352

========================================================================

Enhancement to MFA Option Selection

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Apr/MFA_Option_Enhancement.htm Path: IAM/Release-Notes/Enhancements/2025/Apr/MFA_Option_Enhancement.htm

Enhancement to MFA Option Selection

Users can now select which multifactor authentication method to use while logging in to PrismOne while registering in the system. During the Authentication Set Up (MFA) step, the user can now select to use an Authenticator App, a phone message, or both options as their MFA method.

JIRA # IAM-1805

========================================================================

Enhancement to Mobile Number Validation

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Apr/Mobile_Validation_Enhancement.htm Path: IAM/Release-Notes/Enhancements/2025/Apr/Mobile_Validation_Enhancement.htm

Enhancement to Mobile Number Validation

Mobile numbers used for PrismOne login verification now have stricter validation standards. The mobile number must now have a valid country code. If a country code is missing, +1 is added automatically to indicate the US.

JIRA # IAM-1788

========================================================================

Improved Error Message for Employees Already Registered

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Aug/Already_Registered_Message.htm Path: IAM/Release-Notes/Enhancements/2025/Aug/Already_Registered_Message.htm

Improved Error Message for Employees Already Registered

The error message that displays when a user who has already registered with PrismONE attempts to register again has been clarified with a reminder that they have already registered and instructions on where to go if they forgot their password.

JIRA # IAM-2250

========================================================================

Disable Timeout for Registration Reminder

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Aug/Disable_Timeout_For_Message.htm Path: IAM/Release-Notes/Enhancements/2025/Aug/Disable_Timeout_For_Message.htm

Disable Timeout for Registration Reminder

When Service Providers activate the feature code for the PrismONE ID registration reminder message, the message will now bypass the normal popup timeout in PrismHR and display for each login. The popup timeout in Employee Portal will still be enforced, so it will only display once per day in EP.

JIRA # IAM-2260

========================================================================

Improved Error Message for IP Restrictions

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Aug/IP_Message.htm Path: IAM/Release-Notes/Enhancements/2025/Aug/IP_Message.htm

Improved Error Message for IP Restrictions

The error message that displays when a user attempted to use a Business-to-Customer (B2C) login and encountered IP restrictions has been clarified to identify the IP restrictions as the cause of the error.

JIRA # IAM-1271

========================================================================

Self-Registration Feature Code

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Aug/SelfRegistration_Feature_Code.htm Path: IAM/Release-Notes/Enhancements/2025/Aug/SelfRegistration_Feature_Code.htm

Self-Registration Feature Code

A new client custom feature code, GLOBAL-ID-DIRECT-EE-REG, is now available on the System Parameters form. Enabling this custom feature code causes all new users registering through Employee Portal to use the PrismONE ID registration flow. The new users are no longer required to first log in with a local username and password when this custom feature code is enabled.

JIRA # IAM-2020

========================================================================

Owner Mismatch Notification

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Jan/Domain_Notification.htm Path: IAM/Release-Notes/Enhancements/2025/Jan/Domain_Notification.htm

Owner Mismatch Notification

When a user attempts to log in to an account with a different owner, the error message now informs the user of the error and instructs them to use a different account or return to the proper domain. For example, if the user’s email domain does not match the domain of the company, the error message displays.

JIRA # IAM-1451

========================================================================

MFA Signup Order

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Jan/MFA_Signup_Order.htm Path: IAM/Release-Notes/Enhancements/2025/Jan/MFA_Signup_Order.htm

MFA Signup Order

The order in which Multi-Factor Authentication sign ups are presented during registration has been changed for PrismOne. Time-Based One-Time Passwords (TOTP) MFA signup is now offered first, with Short Message Service (SMS) MFA signups offered second.

JIRA # IAM-1662

========================================================================

PrismOne Registration Feature Code

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/June/Custom_Feature_Code.htm Path: IAM/Release-Notes/Enhancements/2025/June/Custom_Feature_Code.htm

PrismOne Registration Feature Code

A new client custom feature code, GLOBAL-ID-DIRECT-PHR-USER, is now available on the System Parameters form. Enabling this custom feature code causes all new users created in PrismHR to use the PrismONE ID registration flow. The new users are no longer required to first log in with a local username and password when this custom feature code is enabled.

JIRA # IAM-1405

========================================================================

Managers Reset Passwords for PrismOne ID

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Mar/Manager_Reset_Password.htm Path: IAM/Release-Notes/Enhancements/2025/Mar/Manager_Reset_Password.htm

Managers Reset Passwords for PrismOne ID

Managers can now initiate password resets for users using the PrismONE ID login. When a manager initiates a password reset on the Employee Details form, a message displays to notify the manager that the employee uses PrismOne ID. Managers can then send a password reset link to the employee.

Note: Note: If the manager is not logged in with PrismOne ID and attempts to send a password reset link to a user who is using PrismOne ID, a message displays informing the manager that the action cannot be completed, and that the manager must log in with PrismONE ID first.

JIRA # IAM-1430

========================================================================

Multiple PrismOne IDs for Shared Workstation

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Mar/Multiple_IDs_for_Workstation.htm Path: IAM/Release-Notes/Enhancements/2025/Mar/Multiple_IDs_for_Workstation.htm

Multiple PrismOne IDs for Shared Workstation

Users who share a computer station can now create new PrismOne IDs from the same machine. When a user accesses the Link Accounts form for PrismOne, and the system already has saved login information, the user is given the option to link their account or to create a new PrismOne ID account. This allows multiple employees who share a single workstation to each have their own PrismOne ID.

JIRA # IAM-1731

========================================================================

Enhancement to New Users Linking Accounts

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/May/New_Users_Link_Accounts.htm Path: IAM/Release-Notes/Enhancements/2025/May/New_Users_Link_Accounts.htm

Enhancement to New Users Linking Accounts

When a user who is eligible for logging into Employee Portal but does not have an EP account attempts to log in using their PrismONE ID, the user is now prompted to log in locally to Employee Portal to link their account with PrismONE. In addition, users can select a link to see what applications are accessible with their PrismONE ID to verify that their account is properly linked.

JIRA # IAM-1711

========================================================================

Enhancement to Registration Form

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/May/Registration_Cancel.htm Path: IAM/Release-Notes/Enhancements/2025/May/Registration_Cancel.htm

Enhancement to Registration Form

The Cancel button has been removed from the password reset form to prevent users from mistakenly canceling the reset request.

JIRA # IAM-1816

========================================================================

Enhancement to Password Reset Process

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/May/SMS_Forgot_Password.htm Path: IAM/Release-Notes/Enhancements/2025/May/SMS_Forgot_Password.htm

Enhancement to Password Reset Process

When a user selects the link in a password reset email message and is prompted to enter their authentication, the user can now use an authenticator app or an SMS text message.

When the user registers their PrismONE ID account, they can choose to use an authentication app, SMS messages, or both. If only one method is selected, that method displays automatically when the user is prompted to authenticate their login. If both methods are selected, the user can choose which method to use when logging in.

JIRA # IAM-1818, IAM-1891, IAM-1928

========================================================================

Disable Portal Login Feature Code

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Sep/Feature_Code_Disable_Portal.htm Path: IAM/Release-Notes/Enhancements/2025/Sep/Feature_Code_Disable_Portal.htm

Disable Portal Login Feature Code

A new global custom feature code, GLOBAL-ID-DISABLE-PORTAL-LOGIN, is now available on the System Parameters form. Enabling this custom feature code blocks access to the legacy login screens for PrismHR Employee Portal. If a client has a logout URL configured, the PrismHR and EP login screens will redirect to the client URL. If a logout URL is not configured, the login screens redirect to the PrismONE ID login screen.

Note: Note: It is not recommended to apply this feature code unless all of your known users have registered for PrismONE ID or you are managing your own access with your own identity & access management system.

JIRA # IAM-1706

========================================================================

My Linked Applications Section for Account Settings

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Sep/My_Linked_Applications.htm Path: IAM/Release-Notes/Enhancements/2025/Sep/My_Linked_Applications.htm

My Linked Applications Section for Account Settings

The new My Linked Applications section has been added to the Account Settings form. Users can view applications linked to their PrismONE account in this section. This section is divided by organizations and by individual accounts, displaying the Application Username, Application, and User Type for each linked account, if available. If data is not available for an organization, it will still display with an indication of limited data.

Users can click the Link additional accounts link to add an additional account to an organization and follow the PrismONE login verification process.

JIRA # IAM-2289

========================================================================

Sign In Help Link on Login Error Message

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Enhancements/2025/Sep/Sign_In_Help.htm Path: IAM/Release-Notes/Enhancements/2025/Sep/Sign_In_Help.htm

Sign In Help Link on Login Error Message

The login error message that displays when a user fails to sign in to PrismONE now includes the Sign In help link. Users can click this link for additional information about the PrismONE login process and how it uses a different login than their previous credentials.

JIRA # IAM-2285

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Fixes/2025/Fixes_IAM_202501.htm Path: IAM/Release-Notes/Fixes/2025/Fixes_IAM_202501.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
IAM-1563 If multiple PrismHR user IDs are linked to a single PrismONE ID, and any of the user IDs are disabled, the disabled ID still displays as an option in PrismOne. If the disabled user ID was selected, an error displays, and the user needed to repeat the entire login process. This is fixed. Disabled user IDs now display with the (Disabled) label, and selecting the ID now displays an error message indicating the disabled user ID cannot be used and prompts the user to select a new ID.
IAM-1608 When a user entered a 6-digit number code with a space between the numbers, the code would was not accepted. This is fixed. Spaces are now automatically truncated for 6-digit authorization codes.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Fixes/2025/Fixes_IAM_202503.htm Path: IAM/Release-Notes/Fixes/2025/Fixes_IAM_202503.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
IAM-1627 When a user reset their PrismOne ID password, the new password was not held to the same password strength requirements as other PrismOne ID forms. This is fixed.
IAM-1827 When a worksite manager clicked the Send Password Reset link on the Reset Password form in Employee Portal to reset a password for an employee, an error occurred. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Fixes/2025/Fixes_IAM_202504.htm Path: IAM/Release-Notes/Fixes/2025/Fixes_IAM_202504.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
IAM-1685 When a user logged in and was show the Authentication Code form, the Cancel option was not aligned correctly. This is fixed.
IAM-1744 On the Account Settings form for the PrismOne login, email addresses with too many characters overlapped with adjacent fields. This is fixed.
IAM-1803 When a user access the Approve Sign In Request form in PrismOne and added an SMS code while logging in, attempting to proceed using the Enter key produced an error. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Fixes/2025/Fixes_IAM_202505.htm Path: IAM/Release-Notes/Fixes/2025/Fixes_IAM_202505.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
IAM-1607 When a user accessed the login and registration forms for PrismONE, the forms briefly displayed in the wrong format during the loading process. This is fixed.
IAM-1908 When a user’s email address included a space preceding or following an email address, and the user attempted to conduct a password reset, an error occurred indicating that the email used an invalid format. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Fixes/2025/Fixes_IAM_202509.htm Path: IAM/Release-Notes/Fixes/2025/Fixes_IAM_202509.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
IAM-2242 When users attempted to change their password or MFA settings from the My Login Settings screen, an intermittent error would occur. This is fixed.
IAM-2318 When users clicked the Login Settings link from the Users form or the My Login Settings menu item, a timeout error occurred. This is fixed.
IAM-2347 When a user viewed the mandatory sign-up modal for PrismONE, the user could bypass the modal using the Escape key. This is fixed.

========================================================================

“Leave This Site” Message

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Known-Issues/2025/April/Leave_This_Site_Message.htm Path: IAM/Release-Notes/Known-Issues/2025/April/Leave_This_Site_Message.htm

“Leave This Site” Message

When a user is completing registration steps for PrismOne, a “Leave site?” message displays intermittently, such as when entering a phone number or a verification code.

Note: Note: Users can click Leave on this message and proceed with registration without interrupting the process.

This issue will be fixed in an upcoming release.

JIRA # IAM-1914

========================================================================

Known Issue

Source: https://tech-docs.prismhr.com/SP_help/Content/IAM/Release-Notes/Known-Issues/2025/January/Password_Reset_Link.htm Path: IAM/Release-Notes/Known-Issues/2025/January/Password_Reset_Link.htm

Known Issue

When a user clicks the Reset My Password button in a password reset email message, an error occurs.

The temporary password option still works properly, and should be used as a workaround for this issue until it is fixed.

JIRA # IAM-1735

========================================================================

Workflow Form Library UEX Update

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/MR202404/BE_8025_Workflow_Library_UEX.htm Path: OBE/Release-Notes/Enhancements/2024/MR202404/BE_8025_Workflow_Library_UEX.htm

Workflow Form Library UEX Update

Default forms in the Form Library have been upgraded to the Unified Employee Experience (UEX), and these new versions replace the existing default forms. These updates include new stylistic elements and verbiage to max the UEX update across Onboarding, Benefits Enrollment, and Employee Portal.

JIRA # OBE-8025

========================================================================

Map California Wage Notice to PDF Fields

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/MR_202402/New_CA_Wage_Form.htm Path: OBE/Release-Notes/Enhancements/2024/MR_202402/New_CA_Wage_Form.htm

Map California Wage Notice to PDF Fields

You can now map the updated 2024 California Wage Notice form to PDF fields on a custom form. This can be used to write data to the new Emergency or Disaster Disclosure section of the California form. This data is populated based on the responses to the following new hire questions:

To add these questions to a form, access the PDF Fields Map tab after uploading a PDF and click Edit for the field to which you want to map the questions. The Edit PDF Fields Map window displays. On this window, select the following:

Map (Source) Function
disaster_question Check box for a state or federal emergency or disaster declaration.
emergency_or_disaster_declaration Text box to enter the state or federal emergency of disaster declaration.

After making a selection, click Apply Changes. The window closes, and the information from PrismHR that corresponds to the selected source is automatically entered in the field when the form is accessed in Onboarding.

JIRA # OBE-7933, CMP-5392

========================================================================

Evidence of Insurability in Spanish

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/MR_202410/Evidence_Insurability_Spanish.htm Path: OBE/Release-Notes/Enhancements/2024/MR_202410/Evidence_Insurability_Spanish.htm

Evidence of Insurability in Spanish

Service providers can now provide the Evidence of Insurability (EOI) form and Evidence of Insurability Message in Spanish for users whose preferred language is Spanish.

When a user with their preferred language set to Spanish goes through Benefits Enrollment, the Spanish version of the EOI form and message now displays, if one is provided. If the service provider only provides the form or message in English, the English version displays regardless of the user’s preferred language choice.

JIRA # OBE-8657

========================================================================

Updated Wording for Sending Benefit Confirmation Statement Emails

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Benefit_Confirmation_Statement_Wording.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Benefit_Confirmation_Statement_Wording.htm

Updated Wording for Sending Benefit Confirmation Statement Emails

Previously, the subject line of the Benefits Confirmation Statement email message template on the Email Services form required the word “Secure” at the end of the subject line. However, this created confusion regarding whether the email message was sent via a secure gateway, or if the email message was secured with encryption. The wording requirement on the subject line has been removed.

Email messages sent using this form use a secure SMTP gateway when sent. Prism email messages are not inherently encrypted.

JIRA # EERT-2279

========================================================================

Global Employee Dependent Required Fields Settings Enforcement

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Global_Dependent_Required_Fields.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Global_Dependent_Required_Fields.htm

Global Employee Dependent Required Fields Settings Enforcement

With this ticket, logic was applied to ensure that dependent fields flagged as required on the New Hire and Dependent Required Fields (Global) form are enforced on the Add Dependent form in Benefits Enrollment when you attempt to save the form. This change affects the following fields:

To achieve settings enforcement of required dependent fields on the Add Dependent form, the following changes were made:

[Image: screenshot]

JIRA # OBE-7786, OBE-7423, OBE-7735

========================================================================

New UI for Symmetry Payroll Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/New_UI_Symmetry.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/New_UI_Symmetry.htm

New UI for Symmetry Payroll Forms

The all-new Symmetry user interface for onboarding forms now includes additional features, including performance and security improvements, and language support.

The new UI features improved responsiveness for all screen dimensions, improving performance for employees completing forms on all devices. In addition, the new UI is updated to the latest JavaScript libraries to prevent security vulnerabilities and keep the onboarding form process secure.

Furthermore, the update includes additional language support for onboarding forms. Employees can translate forms into Spanish, French, or English, regardless of the original published language from the jurisdiction, improving the accessibility of all forms in the onboarding process.

JIRA # OBE-6425

========================================================================

New Notifications for Time-Based Hire Date

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Notification_Time_Based_Hire.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Notification_Time_Based_Hire.htm

New Notifications for Time-Based Hire Date

Service Providers can now configure a new trigger and notifications in Onboarding and Benefits Enrollment based on time-based conditions for the hiring date. Using this feature, service providers can set up triggers on the Notification Templates form so that new hires are sent notifications a certain number of days before or after the hiring date.

Hiring managers can use these conditions for situations where the employee should start onboarding before or after a specific hiring date. For example, an employee might be hired, but have to wait for equipment before they can start work, and the onboarding process can be delayed until they can obtain their equipment and begin working.

To add time-based triggers to an existing notification:

  1. Select Onboarding and Benefits > Notification Templates.

  2. Select the Template Id to modify.

  3. In the Notification Triggers section, select Time Based for the Trigger Type.

  4. In the Trigger Condition field, select X Days before hire date or X Days after hire date.

  5. In the Number of Days field, enter the number of days before or after the hire date to send the notification.

  6. Click Save.

Using these new trigger conditions, Service Providers can enter a new hire into the system prior to their hire date, but notify the new employee to begin onboarding or benefits enrollment on their actual hire date.

JIRA # OBE-7807, OBE-7813, OBE-7991

========================================================================

Preferred Name in Onboarding and Benefits Enrollment

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Preferred_Name_OBE_BE.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Preferred_Name_OBE_BE.htm

Preferred Name in Onboarding and Benefits Enrollment

A new hire’s preferred name now displays throughout Onboarding and Benefits enrollment, which the system uses in place of their legal first name in the user menu, header, and other forms. The electronic signature continues to use the new hire’s legal name.

When a manager enters a new hire’s preferred name in the Preferred Name field during the Onboarding process, that name now displays throughout the process. The new hire can now see the preferred name on the Employee Information form. In addition, the new hire can add a name if the field is blank, or change the name to update the record.

An additional substitution variable which can be used when building message templates is now available. The following variable and its formatting are now available:

Preferred Name <>

When generating a message, the system replaces the variable with data for the specified employee.

JIRA # OBE-6505, OBE-6508, OBE-6940, OBE-6941, OBE-6942, OBE-6974, OBE-7691

========================================================================

Remove Multiple Benefit Enrollments from a Batch

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Remove_Mass_Enrollments_202403.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Remove_Mass_Enrollments_202403.htm

Remove Multiple Benefit Enrollments from a Batch

Service Providers can now remove multiple benefit enrollments from a batch at once on the Post Benefit Enrollments form. Select multiple enrollments on this form and click Remove to remove multiple enrollments from the batch. A confirmation message displays, and if confirmed, the selected enrollments are removed from the batch and returned to the post benefits enrollment batch queue.

JIRA # OBE-6677, OBE-7697

========================================================================

Skip to Content Button During Onboarding and Benefits Enrollment

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Skip_Content_Button_202403.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Skip_Content_Button_202403.htm

Skip to Content Button During Onboarding and Benefits Enrollment

Employees can now tab immediately to a Skip to Content button on every page during the Onboarding and Benefits Enrollment processes. This element is always listed first on each form. Pressing tab once displays the button, and pressing tab again hides the button and moves to the next element.

When selected, the Skip to Content button moves the cursor to the main content on each form. This enhancement improves accessibility for individuals who may have difficulties navigating the form.

JIRA # OBE-6913

========================================================================

Upload Two-Sided Supporting Documents

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Two_Sided_Documents.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Two_Sided_Documents.htm

Upload Two-Sided Supporting Documents

This enhancement includes support for employers who are qualified to use the alternate procedure in E-Verify to submit two-sided supporting documentation. This procedure allows two-sided or multi-page documentation to be provided as proof of I-9 Employement Eligibility. For example, a new hire can submit scanned pages from their passport as proof of eligibility.

Note: Note: To be considered qualified, the employer must be in good standing with E-Verify. For more information about eligibility, refer to the Qualifications section below.

Submitting Two-Sided Documentation

When a new hire selects a two-sided document to upload in the Select a Document to Upload field on the I-9 Employment Eligibility form, the new hire can now upload separate files for the front and back of the document. This support is also provided when selecting a US passport as documentation, with separate uploads for the Passport ID page and the Passport Barcode page.

Reviewing Two-Sided Supporting Documents

Employers can now review two-sided documents to verify their authenticity on the Employment Eligibility Verification form, which is accessed through the My Approvals form in Employee Portal. If the employee submitted two-sided documents, the Employment Eligibility Verification form now displays individual tabs for each side of the document to be reviewed.

Note: Note: Employers can review two-sided documents on both desktop and mobile devices.

Declining to Upload and In-Person Documents

Employers can elect to decline to upload documents during the Onboarding process and choose to present their documentation to the employer in person. During the Onboarding process, the new hire can select the I will present documentation to my employer in person option on the I-9 Employment Eligibility form to decline the document upload.

Qualifications

To be considered qualified, the employer must be in good standing with E-Verify. According to the US Citizenship and Immigration Services (USCIS), good standing refers to an employer who is enrolled in E-Verify with respect to all hiring sites in the United States that use the alternative procedure, in compliance with all requirements, and continues to participate in good standing in E-Verify at any time they use the alternate procedure. For more information about the alternate procedure qualifications, refer to the USCIS documentation here.

JIRA # OBE-7273, OBE-7274, OBE-7726, OBE-7767, OBE-7768, OBE-7775, OBE-7795

========================================================================

Updated Wording for Voluntary Self-Identification of Disability

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202403/Update_SelfIdentify_Wording.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202403/Update_SelfIdentify_Wording.htm

Updated Wording for Voluntary Self-Identification of Disability

The wording of the Voluntary Self-Identification of Disability during the Onboarding process has been updated to match the wording of the official form used by the US Department of Labor.

JIRA # OBE-6952

========================================================================

Duplicate Forms and Workflows in the Form Library

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Clone_Forms_in_Library.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Clone_Forms_in_Library.htm

Duplicate Forms and Workflows in the Form Library

Clients can now duplicate forms and workflows to accelerate the process of creating new ones. The newly duplicated form or workflow contains all the original form data except for the ID, Name, Date of Creation, and Start Date. The Date of Creation and Start Date will be the date of duplication.To duplicate a form, select a form in the Form Library and click Duplicate. The Duplicate Form screen displays, which can be used to enter a new ID and name, as well as select which version of the form to duplicate.

[Image: screenshot]

After entering a new ID and name, click Duplicate. The Edit Custom Form screen displays, which can be used to configure the general information and specific layout of the form.

[Image: screenshot]

Workflows can also be duplicated in the Workflow Library using an identical procedure. Using this feature, clients can create similar workflows more quickly by using an existing workflow as a template and editing the copied workflow.

JIRA # OBE-4704

========================================================================

Edit Dependents in Enrollment Workflow

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Edit_Dependents_Workflow.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Edit_Dependents_Workflow.htm

Edit Dependents in Enrollment Workflow

Clients can now enable employees to make changes to their dependents during the benefit enrollment process. Previously, employees could only add dependents during benefit election, but had to navigate to the Employee Portal to make changes to dependents. Using this option, clients can allow employees to make changes directly to save time.

Note: Note: When the employee edits a dependent and changes the relationship, date of birth, gender, full-time student flag, tobacco user flag, or disabled flag, the employee’s workflow is reset, and the employee receives a notification indicating that they must recomplete their elections.

To enable editing dependents during the workflow at a global level, navigate to Workflow Setup / Benefits Specific / Enrollment Options and select the Allow Edit Dependents in Enrollment Workflow field.

To enable editing dependents during the workflow at a client level, navigate to Client / Change / Client Details, navigate to the Benefits tab, and select the Allow Edit Dependents in Enrollment Workflow? field.

Note: Note: These fields are disabled by default and must be enabled at the global or client level to allow employees to edit their dependents during the workflow.

When this field is checked, the Edit button is available on the Dependents form in the benefits enrollment workflow. When the field is not checked, the Edit button does not display on the Dependents form in the UI.

JIRA # OBE-7781

========================================================================

Gender Designation in Spanish

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Gender_Designation_Spanish.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Gender_Designation_Spanish.htm

Gender Designation in Spanish

Employees can now view the options in the Gender Designation form in Spanish as well as English, based on their preferred language. The description that displays is based on the Designation Description (Spanish) field on the Self Identity Codes form, which is available on the System|Change menu.

JIRA # OBE-6866

========================================================================

My Dependents UEX Updates

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/My_Dependents_UEX.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/My_Dependents_UEX.htm

My Dependents UEX Updates

The Dependents form has been updated in the new UEX to display dependent data as cards to quickly review dependent information. The Dependents cards organize automatically depending on screen size, improving readability on smaller screens or windows.

Employees can add a dependent by clicking Add Dependent. The Add Dependent form displays, where the employee can fill in information about the dependent’s name, relationship, address, and other details. If the option to edit dependents during benefits enrollment is enabled on the global or client level, the employee can also edit the dependent from this form.

JIRA # OBE-7787

========================================================================

Notification for Creating Batches of Enrollments

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Notification_Batch_Enrollments.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Notification_Batch_Enrollments.htm

Notification for Creating Batches of Enrollments

Users creating a batch on the Post Benefit Enrollments form now receive a confirmation message if they create a batch that includes multiple enrollments. The message displays the number of items that are included in the batch to help employees avoid accidentally including too many items.

[Image: screenshot]

The employee must confirm that the items in the batch are correct before naming and processing the batch.

JIRA # OBE-7879

========================================================================

Enhancement to Proxy Login Form

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Proxy_Login_Form_Enhancement_QR202406.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Proxy_Login_Form_Enhancement_QR202406.htm

Enhancement to Proxy Login Form

Service providers who have enabled the Worksite Manager Proxy role (which now displays as Worksite Manager/Trusted Advisor Proxy, see below) in the Account Management Roles panel on the Users form can now access the Worksite Manager Proxy role on the Proxy Login form.

To do this, select the new Worksite Manager/Truster Advisor option in the Activity field. After selecting Worksite Manager/Truster Advisor, the Employee ID field displays as User ID, so service providers can enter or select the worksite manager or worksite trusted advisor’s user ID. For example:

[Image: screenshot]

Note: Service providers can continue to access the Worksite Manager Proxy option on the Actions menu in the Users form to proxy into the system as a worksite manager or worksite trusted advisor. However, the Worksite Manager Activity option is no longer available on the Actions menu for employees who display on the Enhanced Dashboard after selecting the Benefit Enrollment Workflows and Benefit Enrollment Only views in the At a Glance panel.

In addition to the enhancement described above, the Worksite Manager Proxy role in the Account Management Roles panel on the Users form now displays as Worksite Manager/Trusted Advisor Proxy. For example:

[Image: screenshot]

For more information about the Proxy Login form, see the in-product help or PrismHROnboarding User Guide.

JIRA # WSP-51

========================================================================

Onboarding Support for Remote Location

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Remote_Location_Field.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Remote_Location_Field.htm

Onboarding Support for Remote Location

Onboarding now leverages the existing Remote Location field for remote employees. The Onboarding process now uses the resident address for tax form processing if the employee worksite location is set to remote.

JIRA # OBE-7794

========================================================================

Enhancements to Remote Verification for Form I-9

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Remote_Verification_Enhancements.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Remote_Verification_Enhancements.htm

Enhancements to Remote Verification for Form I-9

The Remote Verification section of Form I-9 Section 2 has been enhanced with additional logic to determine that it displays under specific, proper circumstances. The section displays based on the combination of the Enable I-9 Remote Verification field on the Client Details form and the worksite location using the following logic:

JIRA # OBE-7946

========================================================================

Session Timeout Notification

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Session_Timeout_Notification.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Session_Timeout_Notification.htm

Session Timeout Notification

Users are now notified when their active session time in Onboarding or Benefits Enrollment has expired and given the option to return to the Employee Portal login URL. The user is automatically logged out of the system when the timeout occurs for security reasons, while the prompt remains on-screen to inform the user that the session has timed out.

[Image: screenshot]

Users can click the Return to Employee Portal button on the timeout prompt to return to the Employee Portal login URL.

JIRA # OBE-5810, OBE-7902, OBE-8019

========================================================================

Skip to Content Button for Additional Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202406/Skip_To_Content_Additional.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202406/Skip_To_Content_Additional.htm

Skip to Content Button for Additional Forms

Employees can now tab immediately to a Skip to Content button on additional forms in the Onboarding process. When selected, this button moves the cursor to the main content on each form.

The Skip to Content button is now available on the following forms:

This enhancement improves accessibility for individuals who may have difficulties navigating these forms.

JIRA # OBE-6998

========================================================================

ACA Life Event

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202409/ACA_Life_Event.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202409/ACA_Life_Event.htm

ACA Life Event

Service providers can now use the new ACA life event to provide eligible employees with ACA benefits elections. By initiating this life event for an employee, the employee can enroll in selected ACA coverage options.

If an employee qualifies for ACA benefits based on their hours worked within a certain time period, the employees are added to a list of qualifying individuals. Service providers can view this list on the ACA Offered Employees form.

If the employee is not eligible for on-line benefits enrollment due to their employee type, service providers can still initiate the ACA life event for the employee as long as the employee is listed on the ACA Offered Employees table. This override is only available for the ACA life event.

Service providers can customize which coverage options appear on the ACA life event using the Life Event Maintenance form.

JIRA # OBE-8172, OBE-8174, OBE-8477

========================================================================

Benefits Enrollment In Spanish

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202409/Benefits_Enrollment_In_Spanish.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202409/Benefits_Enrollment_In_Spanish.htm

Benefits Enrollment In Spanish

Employees can now view the Benefits Enrollment workflow in Spanish as well as English, based on their preferred language. Employees can switch their preferred language using a new option on their account dropdown menu. When an employee selects Spanish as their preferred language, this choice is respected throughout the enrollment process.

Service providers can customize the Spanish text of the Benefits Enrollment workflow using the Workflow Library form. Selecting the Edit icon on the Process tab or the Forms and Documents tab displays an option to edit both the English label and the Spanish label.

Note: Note: All configuration options require an English text version, with the exception of supporting documents. Users can add supporting documents specifically for the Spanish language.

Note: Note: Employees only see the documents available for their preferred language. If a service provider has multiple supporting documents in English but only one in Spanish, Spanish users only see the single document. Service providers can upload the additional documents in the Spanish section as well as English to make them available to everyone, if necessary.

JIRA # OBE-4091, OBE-5844, OBE-5846, OBE-8179, OBE-8180, OBE-8181, OBE-8219, OBE-8220, OBE-8268, OBE-8278, OBE-8279, OBE-8280, OBE-8300, OBE-8301, OBE-8302, OBE-8303, OBE-8435, OBE-8436, OBE-8446, OBE-8463

========================================================================

Enhancement to Bulk Change Benefit Plan Form

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202409/Enhanced_Bulk_Change.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202409/Enhanced_Bulk_Change.htm

Enhancement to Bulk Change Benefit Plan Form

When a user searches for a benefit plan on the Bulk Change Benefit Plan form, the search results now display as a selector instead of a dropdown menu. In addition, the search results display both the Benefit Plan ID field and the Benefit Plan Name field. This enhancement allows users to differentiate between benefit plans that use the same benefit plan name.

JIRA # EERT-2585

========================================================================

Form Library Preview Updated to New UEX

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202409/Form_Library_Preview.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202409/Form_Library_Preview.htm

Form Library Preview Updated to New UEX

The preview feature in the Form Library when creating a new form has been upgraded to the Unified Employee Experience (UEX). When a user previews a form during the creation process, the form style and interface now display using the updated UEX elements. Using this feature, service providers can see exactly how the new forms display to users in the new UEX.

JIRA # OBE-8027, OBE-8349, OBE-8368, OBE-8369, OBE-8370, OBE-8371

========================================================================

New Benefit Enrollment Notification for Time-Based Hire Date

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202409/New_BE_Notification.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202409/New_BE_Notification.htm

New Benefit Enrollment Notification for Time-Based Hire Date

Service Providers can now configure a new trigger and notifications in Benefits Enrollment based on time-based conditions for the hiring date. Using this feature, service providers can set up triggers on the Notification Templates form so that new hires are sent notifications a certain number of days before or after the hiring date.

JIRA # EERT-2588

========================================================================

Enhancements to Pet and Legal Insurance Benefits

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202409/Pet_Legal_Insurance.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202409/Pet_Legal_Insurance.htm

Enhancements to Pet and Legal Insurance Benefits

When a user selects Pet or Legal insurance during Benefits Enrollment, the user is no longer presented with an option to enroll dependents. Since neither Pet nor Legal Insurance require dependents to be enrolled, this update helps prevent confusion while enrolling for these benefits.

Note: Note: This will only take effect on newly created Web Enrollment Configurations. Any current workflows that were created before this release will need to be deleted and re-created in order to see this change.

JIRA # OBE-8375

========================================================================

Trace Log Timestamp Enhancement

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202409/Trace_Logs.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202409/Trace_Logs.htm

Trace Log Timestamp Enhancement

Trace logs on the Onboarding Trace Log form and the Benefits Enrollment Trace form now display a timestamp with milliseconds. This matches the style used by audit log entries, making it easier for users to compare the two logs.

JIRA # EERT-2586

========================================================================

Enhancement to Other Tab on Employee Form

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2024/QR_202411/Employee_Form_Other_Tab.htm Path: OBE/Release-Notes/Enhancements/2024/QR_202411/Employee_Form_Other_Tab.htm

Enhancement to Other Tab on Employee Form

The Onboarding In Progress field on the Other tab on the Employee Form is now a read-only field. Previously, selecting this field manually could cause issues with the onboarding workflow. If a manager needs to suspend an employee’s onboarding status, they can use the Suspend Workflow action on the Workflow Maintenance form.

JIRA # OBE-8207

========================================================================

Change Notification for Client Workflow Grid

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/MR202402/Client_Workflow_Grid_Notification.htm Path: OBE/Release-Notes/Enhancements/2025/MR202402/Client_Workflow_Grid_Notification.htm

Change Notification for Client Workflow Grid

When a user updates the End Date field for a Client ID on the Client Workflow Grid, a notification now appears to confirm that the workflow end date has been successfully modified. Additionally, the user is given the option to navigate to the Web Enrollments Date Update bulk tool, allowing them to update all active workflows efficiently.

JIRA # OBE-8698

========================================================================

Payroll Specialists as Notification Recipients

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/MR202402/Payroll_Spec_Notification.htm Path: OBE/Release-Notes/Enhancements/2025/MR202402/Payroll_Spec_Notification.htm

Payroll Specialists as Notification Recipients

Service Providers can now select a Payroll Specialist as the recipient of onboarding and benefits notifications using the Notification Recipients form. While editing a notification, select Payroll Specialist in the To Generic field to designate that roll as the recipient.

JIRA # OBE-4938, OBE-8774

========================================================================

Ancillary Brief Description in Spanish

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/MR2025_01/Ancillary_Spanish.htm Path: OBE/Release-Notes/Enhancements/2025/MR2025_01/Ancillary_Spanish.htm

Ancillary Brief Description in Spanish

Service providers can now provide the Ancillary Brief Description on the ANC cards in Spanish for users whose preferred language is Spanish.

When a user with their preferred language set to Spanish goes through Benefits Enrollment, the Spanish version of the ANC cards now display, if one is provided. If the service provider only provides the form in English, the English version displays regardless of the user’s preferred language choice.

JIRA # OBE-8847

========================================================================

Invalid Launch Restriction

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/MR2025_01/Invalid_Launch_Restriction.htm Path: OBE/Release-Notes/Enhancements/2025/MR2025_01/Invalid_Launch_Restriction.htm

Invalid Launch Restriction

Employees are now prevented from starting an Onboarding workflow if no workflow has been assigned. If a user selects the This employee will be completing the onboarding process on the web option on the New Hire form, and no workflow is assigned, an error message now displays indicating the situation. In addition, no prehire record is created in this situation.

If a future-dated workflow is assigned when the employee selects this option, a prehire record is created, and the Onboarding workflow proceeds as normal.

JIRA # OBE-8534

========================================================================

Custom Form Setup Validation

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/MR2025_01/Setup_Conflict_Validation.htm Path: OBE/Release-Notes/Enhancements/2025/MR2025_01/Setup_Conflict_Validation.htm

Custom Form Setup Validation

When a service provider creates a custom form in the Form Library, the options to add a File Hyperlink field and an attached fillable PDF form are now mutually exclusive. Including both items on a custom form is unnecessary, and could create issues with saving information during the Onboarding workflow.

When a service provider adds an attached fillable PDF to a custom form, the File Hyperlink option is now disabled, and vice versa.

JIRA # OBE-8540

========================================================================

Aggregate Spouse Maximum Life Benefits

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Aggregate_Spouse_Max_Benefits.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Aggregate_Spouse_Max_Benefits.htm

Aggregate Spouse Maximum Life Benefits

The system now takes into account the Employer Paid Life coverage amount for the employee and the Voluntary Life coverage amount to combine the amounts when the Use Aggregate Spouse Maximum box is checked to limit the spouse from electing more than 50% of the employee’s total coverage, rounded down to the nearest 10,000.

The employee is not required to enroll in Voluntary Life in order for the Spouse to enroll in Voluntary Life, however the Spouse’s election is limited to 50% of the employee’s Employer Paid Life election.

JIRA # OBE-8663

========================================================================

Beneficiary Phone and Address Fields Standardized

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Beneficiary_Phone_Standardized.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Beneficiary_Phone_Standardized.htm

Beneficiary Phone and Address Fields Standardized

Phone and Address fields for multiple sections of Benefits Enrollment have been standardized to appear with the same names as Prism and Employee Portal.

JIRA # OBE-8499, OBE-8500

========================================================================

Benefit Summary Updated to UEX

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Benefit_Summary_UEX.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Benefit_Summary_UEX.htm

Benefit Summary Updated to UEX

The Benefit Summary form has been upgraded to the Unified Employee Experience (UEX). This update helps unify the user experience with the other aspects of the system.

The UEX upgrade applies to tiles, icons, and messages across the Benefit Summary form. In addition, tiles now include a Download Plan Summary link to allow users to download a summary of each benefit for their records.

JIRA # OBE-7910, OBE-8723, OBE-8724, OBE-8725, OBE-8726, OBE-8727, OBE-8728, OBE-8734, OBE-8735, OBE-8809, OBE-8811, OBE-8823, OBE-8824, OBE-8935, OBE-8938

========================================================================

Enhancement to Bulk Change Benefit Plan Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Bulk_Change_Enhancement.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Bulk_Change_Enhancement.htm

Enhancement to Bulk Change Benefit Plan Tool

Improvements have been added to the Bulk Change Benefit Plan form to increase performance of the process. Filtering and searching for data is now more responsive to prevent this screen from timing out, and the form only loads the data as needed for the search.

JIRA # OBE-8339

========================================================================

Calculate Life Event Benefits Window From Life Event Date

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Calculate_Life_Event.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Calculate_Life_Event.htm

Calculate Life Event Benefits Window From Life Event Date

When a Life Event is launched, there is now an option to calculate the End Date of the Workflow from the Life Event Date instead of the date the Life Event workflow is created.

Previously, the system applied the 60-day window length from the Start Date of the Life Event Workflow. For example, if an employee had a baby on 10/11/2024 and the Life Event Workflow was created on 10/25/2024, the system allowed the employee to complete their enrollment until 12/24/2024.

With this update, the 60-day window will now be calculated from the Life Event Date (i.e. 10/11/2024), ensuring the employee has until 12/10/2024 to complete their enrollment. This change ensures timely recording of elections to gain coverage.

JIRA # OBE-6105

========================================================================

Clone a Life Event

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Clone_Life_Event.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Clone_Life_Event.htm

Clone a Life Event

Clients can now clone existing life events while editing events on the Life Event Maintenance form. Cloning a life event copies all items in the event, including the General, Offer Type Rules, Process, Notifications, Client List, and Employee Portal Components tabs.

Note: Note: The

[Image: screenshot]

(Edit) and

[Image: screenshot]

(Remove) actions now display as icons on this form for formatting purposes.

To clone a life event:

  1. Access the Life Events Maintenance form.

  2. Under the Action column, select the [Image: screenshot] (Clone) icon. The Duplicate Life Event form displays.

  3. Enter an ID for the new Life Event in the New ID field.

  4. Enter a code for the new Life Event in the New Code field.

  5. Click Duplicate. A copy of the life event is created with the new name and code

JIRA # OBE-8717

========================================================================

Warning Message for Inactive Dependents or Beneficiaries

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Inactive_Dependent_Message.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Inactive_Dependent_Message.htm

Warning Message for Inactive Dependents or Beneficiaries

If an employee submits a benefits enrollment with an active dependent or beneficiary, and the dependent or beneficiary is marked as inactive prior to the enrollment being posted, the review process now flags an error for the discrepancy.

After receiving an error message indicating an inactive dependent or beneficiary, the user performing the enrollment posting is now given an option to move the enrollments that failed review to a new batch. The user can then continue posting the items which passed review.

JIRA # OBE-3874

========================================================================

Life Coverage Dependent Reduction Provision Message

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Life_Dependent_Reduction.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Life_Dependent_Reduction.htm

Life Coverage Dependent Reduction Provision Message

Employers can now add a Dependent Reduction Provision for Life coverage on the Group Benefit Plan Setup form.

When an employee views Life coverage for their dependents, the Dependent Reduction Provision message now displays under the Life tile during Benefits Enrollment. This message can be added for both English and Spanish language options.

JIRA # OBE-8818

========================================================================

Life Event End Date Warning Message

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Life_Event_End_Date_Message.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Life_Event_End_Date_Message.htm

Life Event End Date Warning Message

When a Life Event is launched for an employee, the user is now notified if the calculated End Date would fall before the Start Date for the Life Event. An error message is presented to the user, and the workflow will not launch if the End Date falls before the Life Event Start Date.

JIRA # OBE-8877

========================================================================

Post Benefit Enrollment Warning for Terminated Employees

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Post_Warning_For_Terminated.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Post_Warning_For_Terminated.htm

Post Benefit Enrollment Warning for Terminated Employees

If the posting for the Benefits Enrollment process includes a terminated or future terminated employee, the user now receives a warning message indicating that a terminated employee is included in the batch. This does not prevent the user from completing the processing, however they are able to remove the terminated employee(s) from the posting batch if necessary.

JIRA # OBE-6366

========================================================================

Preferred Name Throughout Benefits Enrollment

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Preferred_Name_BE.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Preferred_Name_BE.htm

Preferred Name Throughout Benefits Enrollment

When an employee has a preferred name on their record, several fields in the Benefit Enrollment workflow displayed their legal first name instead.

The preferred name now displays throughout the Benefits Enrollment workflow, including the Who Needs Coverage? area of the Medical form and the user login dropdown menu.

Note: Note: This does not change the display of the employee’s name on the Confirmation Statement.

JIRA # OBE-8189

========================================================================

Redirect After Logout

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Redirect_After_Logout.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Redirect_After_Logout.htm

Redirect After Logout

If the Redirect After Logout field is enabled on the Configuration Templates form, an employee who logs out of Benefits Enrollment or Onboarding is now redirected to the URL specified on the template. This feature shares the same functionality as the Employee Portal Redirect On Logout.

Note: Note: A client can disable the redirect specifically for Onboarding by selecting the Disable Onboarding Redirect toggle on the configuration template.

JIRA # OBE-8817

========================================================================

SSN Applied For Field for Dependents

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/SSN_Applied_For.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/SSN_Applied_For.htm

SSN Applied For Field for Dependents

Employees can now add a dependent or beneficiary during Benefits Enrollment who is currently applying for a Social Security Number. To indicate that the dependent or beneficiary has applied for a SSN, simply check the SSN applied for field. This will satisfy the SSN requirements for these forms.

JIRA # OBE-8701

========================================================================

Enhancement to Edit New Hire Form

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/QR202503/Variable_Salary_Option.htm Path: OBE/Release-Notes/Enhancements/2025/QR202503/Variable_Salary_Option.htm

Enhancement to Edit New Hire Form

Service providers can now select the Variable Salary option in the Pay Method field on the Edit New Hire form to accurately track the hours that employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

Note: The Variable Salary option in the Pay Method field only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

To set the Variable Salary option as the Pay Method:

  1. Enable the VARSALMETHOD custom feature code on the System Parameters form.

  2. Set the Workflow Type on the Workflow Maintenance form to Onboarding and the Action to Edit New Hire.

  3. After filtering by Client ID and selecting Search, select a new hire employee to edit in the Search Results list. The Edit New Hire form displays.

  4. Select the Variable Salary option in the Pay Method field. For example:

[Image: screenshot]

  1. Click Save.

For more information, see the in-product help or PrismHROnboarding User Guide.

JIRA # PD-18651

========================================================================

Dependent Provision on Life Benefit Summary

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/Dependent_Provision.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/Dependent_Provision.htm

Dependent Provision on Life Benefit Summary

Service providers can now have the Dependent Age Reduction Provision message from the Group Benefit Plan form display for Life benefit plans during Benefits Enrollment.

The text of the Dependent Age Reduction Provision message now displays on the Life tile of the Benefit Summary form. In addition, the text displays on the Change Coverage Amounts form when an employee makes a change to coverage amounts.

JIRA # OBE-8968

========================================================================

Flex Benefit Summary Contribution Limits

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/Flex_Benefit_Summary.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/Flex_Benefit_Summary.htm

Flex Benefit Summary Contribution Limits

The Flexible Spending Account tile on the Benefit Summary form now features the Contribution Limits dropdown section. This section displays the Minimum Contribution, Max Individual Amount, and Max Household Amount fields to provide additional information about contributions for the FSA.

JIRA # OBE-9054

========================================================================

New Global Business Rule for Worksite Location

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/Global_Business_Rule.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/Global_Business_Rule.htm

New Global Business Rule for Worksite Location

Service providers can now create a global business rule that uses worksite locations on the Business Rules Library form. When the Rule Type field is set to Global, the Employee Worksite Location Field now allows service providers to select one or more worksite locations to use the global rule.

For example, if a city ordinance in New York City has a certain requirement, service providers can create a global rule to comply with the requirement and enter all NYC worksite locations in the Employee Worksite Location Code field.

JIRA # OBE-9076

========================================================================

HSA Match Calculation During Enrollment

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/HSA_Match_Calculation.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/HSA_Match_Calculation.htm

HSA Match Calculation During Enrollment

When a client has a standard or fixed HSA Match defined for their employee benefits, employees can now see a projected calculation of that match during the Benefits Enrollment process.

The Heath Savings Account tile now displays a banner of the projected match and the annual limit that the employee can contribute. Using this feature, employees can make decisions about how much to contribute to an HSA to meet employer matching more easily.

JIRA # OBE-3835, OBE-8993

========================================================================

Enhancement to HSA Requests for Benefits Workflow

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/HSA_Requests_Enhancement.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/HSA_Requests_Enhancement.htm

Enhancement to HSA Requests for Benefits Workflow

Clients can now activate a message to inform employees that they must complete certain forms when selecting a high deductible plan and provide a link to download the forms.

To activate this option, select HSA Request on the Process tab of a workflow in the Workflow Library. Once this option is selected, service providers can enter a message in English and Spanish, as well as attach documents to be distributed to employees who select high deductible plans.

JIRA # OBE-9185, OBE-9186

========================================================================

Formatting Update for Money in Benefits Enrollment

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/Money_Formatting.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/Money_Formatting.htm

Formatting Update for Money in Benefits Enrollment

Large dollar amounts displayed during Benefits Enrollment now have commas separating the thousandth digit to improve legibility. For example, 100000 now displays as 100,000.

JIRA # OBE-8842

========================================================================

Return to Employee Portal Without Logout

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/Return_To_EP.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/Return_To_EP.htm

Return to Employee Portal Without Logout

When an employee navigates away from Benefits Enrollment, they can now go directly to Employee Portal without logging out and logging back in again.

Employees can select the logo in the top left of the application. A prompt displays to indicate that there progress has been saved and they are about to return to Employee Portal. Accepting this prompt allows the employee to navigate to the Portal directly.

JIRA # OBE-6408

========================================================================

Enhancements to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202504/System_Parameters_Enhancement.htm Path: OBE/Release-Notes/Enhancements/2025/R202504/System_Parameters_Enhancement.htm

Enhancements to System Parameters Form

The new Enable Decision Support option is now available on the System Parameters form. This option can be accessed by selecting System | Change and then Enrollment Options in the Actions menu. We are excited to announce that this feature will activate Decision Support tools in an upcoming release; however, it is not yet operational.

JIRA # OBE-9160

========================================================================

Enhancement to the Bulk Change Benefit Plan Form

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202505/Bulk_Change_Benefit_Enhance.htm Path: OBE/Release-Notes/Enhancements/2025/R202505/Bulk_Change_Benefit_Enhance.htm

Enhancement to the Bulk Change Benefit Plan Form

The filter options on the Bulk Change Benefit Plan form are now located on the main form. Users can make selections immediately in the Control Groups, Clients, and Benefits Plans fields, then select Apply Pre-Filter to view results.

In addition, users can make multiple selections in one or more filters to apply bulk changes to more benefit plans at once.

JIRA # OBE-9030

========================================================================

Enhancement to Benefit Plan Selection

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202506/Benefit_Plan_Selection.htm Path: OBE/Release-Notes/Enhancements/2025/R202506/Benefit_Plan_Selection.htm

Enhancement to Benefit Plan Selection

When an employee views benefit plan options during Benefits Enrollment, their current plan now displays as the Current Enrollment Plan.

[Image: screenshot]

This enhancement makes it easier to compare plans at a glance to their current selection.

JIRA # OBE-9371

========================================================================

Enhancement to Dependent Age Limits by State Override

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202506/Dependent_Age_State_Limit.htm Path: OBE/Release-Notes/Enhancements/2025/R202506/Dependent_Age_State_Limit.htm

Enhancement to Dependent Age Limits by State Override

When using the Override Dependent Age Limits By State option on the Group Benefit Plan Setup form, the state’s dependent age limits now override the client’s Dependent Age Limit values during Benefits Enrollment. When employees make selections during Benefits Enrollment and this option is selected, the Dependent’s resident state is used to determine the age limit for dependents. If the dependent does not have a listed resident state, the Employee’s resident state is used instead.

JIRA # OBE-9124

========================================================================

Enhancement to Missing State EIN Message

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202506/Missing_State_EIN_Message.htm Path: OBE/Release-Notes/Enhancements/2025/R202506/Missing_State_EIN_Message.htm

Enhancement to Missing State EIN Message

When an employee is working on their Onboarding workflow and does not add a State EIN on the Employer Details panel, the message that displays no longer restricts the employee from continuing the Onboarding process if the State EIN is recommended, but not required.

JIRA # OBE-9414

========================================================================

Disability Guarantee Issue and Late Entry Amounts on Benefit Summary

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202507/Disability_Guarantee_Issue.htm Path: OBE/Release-Notes/Enhancements/2025/R202507/Disability_Guarantee_Issue.htm

Disability Guarantee Issue and Late Entry Amounts on Benefit Summary

When an employee elects an amount greater than the Guarantee Issue or Late Entry amounts defined on the Enrollment Details for Disability plans, the Benefits Summary form now displays the relevant information. Under these conditions, the Guarantee Issue Coverage Amount displays, as well as a link to the Evidence of Insurability (EOI) form for the plan. This information is available in both English and Spanish.

JIRA # OBE-9113

========================================================================

Disability Guarantee Issue and Late Entry Amounts on Benefit Plans

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202507/Disability_Guarantee_Plans.htm Path: OBE/Release-Notes/Enhancements/2025/R202507/Disability_Guarantee_Plans.htm

Disability Guarantee Issue and Late Entry Amounts on Benefit Plans

The Disability Plan tile now displays the coverage amount and deductions per pay period for both the Guaranteed Issue and the Coverage Requiring Evidence of Insurability. Employees can use this information to make more informed decisions about disability plans during Benefits Enrollment.

JIRA # OBE-7003

========================================================================

Voluntary Disability Coverage in Benefits Summary

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202507/Voluntary_Benefits_Summary.htm Path: OBE/Release-Notes/Enhancements/2025/R202507/Voluntary_Benefits_Summary.htm

Voluntary Disability Coverage in Benefits Summary

Employees can now view their Voluntary Disability coverage amounts on the Benefits Summary Form and the Confirmation Statement during Benefits Enrollment. This coverage amount displays for both Short Term and Long Term disability coverage. Currently, the Coverage Amount only displays when Employer Cost is shown. In a future release, we will update this logic so that the Coverage Amount will also display when Employer Cost is hidden, ensuring more consistent visibility for employees.

JIRA # OBE-9207, OBE-9208

========================================================================

Gender Selection Dropdown for Dependents

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202508/Gender_Selection.htm Path: OBE/Release-Notes/Enhancements/2025/R202508/Gender_Selection.htm

Gender Selection Dropdown for Dependents

When employees enter information for dependents on the Dependents form in Benefits Enrollment, the Gender field now displays as a dropdown list instead of a toggle. Employees can also now select Non-Binary or Decline To State as Gender options for their dependents.

Note: Note: These options must be enabled by a Service Provider on the System Parameters form.

JIRA # OBE-9483

========================================================================

Enhancement to Onboarding Forms with Required Information

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202508/Required_Information.htm Path: OBE/Release-Notes/Enhancements/2025/R202508/Required_Information.htm

Enhancement to Onboarding Forms with Required Information

During the onboarding process, if any required Employer Details are missing, an error message now displays on the tax form, and the form will remain open and incomplete. Previously, employees were redirected to the Onboarding Summary, regardless of whether other forms were still unfinished in the workflow.

Now, navigation has been enhanced. Employees will be directed to the next incomplete form or to the Onboarding Summary if no other forms are pending. The employee cannot submit their onboarding workflow until all required information have been entered and the tax forms have been completed.

JIRA # OBE-9485

========================================================================

Care Advocacy Offer Type

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Enhancements/2025/R202510/Care_Advocacy_Offer_Type.htm Path: OBE/Release-Notes/Enhancements/2025/R202510/Care_Advocacy_Offer_Type.htm

Care Advocacy Offer Type

A new offer type, Care Advocacy (CAD), is now available for use with Marketplace partner care advocacy benefits. This offer type allows Service Providers to group CAD benefits under one form. Employees can only select one plan for this offer type. A prebuilt Care Advocacy form is now available in the Workflow Library, which can be copied into a Benefits Enrollment workflow to provide CAD benefits.

OBE-9646

========================================================================

Changes to I-9 Forms for Non-Applicable Fields

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202401/Changes_to_I9_Forms.htm Path: OBE/Release-Notes/Fixes/2024/MR202401/Changes_to_I9_Forms.htm

Changes to I-9 Forms for Non-Applicable Fields

I-9 Forms have been updated to comply with new regulations regarding fields which are not applicable to the employee. I-9 Forms no longer accept N/A as an entry, and must either include information or be left blank.

To comply with this change, I-9 Forms are no longer populated with “N/A” for fields where neither the employer or employee have any input. Fields that are not applicable are now left blank on the form.

JIRA # OBE-7741, OBE-7751

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202401/OB_Fixes_MR_202401.htm Path: OBE/Release-Notes/Fixes/2024/MR202401/OB_Fixes_MR_202401.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2256 When new users are required to enter a personal email address and a new employee is going through the onboarding using the new UEX, the Personal Email field did not display as a required field. In addition, if the field was left blank and the employee attempted to submit their details, they could not complete the process. This is fixed.
EERT-2272 When a user selected a form in the Form Library and attempted to open a pdf in the PDF Integration section of the General tab, the pdf form did not open properly. This is fixed.
EERT-2283 When a new employee in the Onboarding in Progress status attempted to exit the Benefits Enrollment, a 404 error occurred. This is fixed. The employee is now directed to the Employee Portal login form.
EERT-2288 When a user created a business rule in the Business Rules Library and saved the rule without selecting an operator in the Choose Operator field, that rule became a global rule for the client. Any custom form created with the same business rule would be visible to all employees. This is fixed. Users can no longer save a business rule without selecting an operator.
EERT-2289 When a user added a new custom form to the Onboarding process, the form did not display during the onboarding workflow. This is fixed.
EERT-2318 When a user attempted to upload a PDF document to the Document Repository, an error message displayed, and the action could not be completed. This is fixed.
OBE-7215 When a user reviewed Disability cards during Benefits Enrollment, the “Enter Coverage Amount” text on cards with editable amounts could be clicked, which caused the card to be selected. This is fixed.
OBE-7302 When a user accessed Benefits Enrollment using the Proxy Login feature, attempting to email the Benefits Confirmation Statement PDF caused the PDF to display with missing data and incorrect formatting. This issue only occurred in the Unified Employee Experience (UEX). This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202402/OB_Fixes_MR_202402.htm Path: OBE/Release-Notes/Fixes/2024/MR202402/OB_Fixes_MR_202402.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2169 When an employee displayed the Enrollment Statement for benefits and a custom form was included at the end of the benefit enrollment workflow, the enrollment statement would include a duplicate offer type. This is fixed. Custom forms no longer cause a duplicate offer type in the enrollment statement.
EERT-2299 When an employee during onboarding had Download PDFs selected in their Chrome browser settings, the preview of the I-9 Section 1 document did not display properly and could not be downloaded. This is fixed.
EERT-2316 When a client with no rehire approval policy created a rehire approval in Employee Portal, the approval record would sometimes be left in the “P” (Pending) status, and the approval was not automatically cleared from the system. This is fixed.
EERT-2336 After an employee submits a benefits enrollment workflow, the confirmation statements could not be properly sent to the employee via email on the Employee Last Confirmation form or the Employee Confirmation Statements form. This is fixed.
EERT-2344 When a user previews forms in the Form Library or goes through the Onboarding process, the names of the form hyperlinks could change, disappear, or appear on the incorrect form. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202404/BE_Fixes_202404_MR.htm Path: OBE/Release-Notes/Fixes/2024/MR202404/BE_Fixes_202404_MR.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2313 If an employee was previously assigned a Benefit Group with no Benefit Rules and the employee was then assigned to a future-dated Benefit Group, network information was not properly pulled into the new group. This is fixed.
EERT-2360 When an employee attempted to review their benefit confirmation statement on the Benefit Confirmation Statements form in Employee Portal, clicking the link displayed a blank page. This is fixed.
EERT-2369 If an employee refreshed a form during Benefits Enrollment, the name of the form reverted to the most recent form name, regardless of the form name assigned during workflow creation. This is fixed.
EERT-2389 When a user enrolling in benefits attempted to waive benefits on the Gap Insurance form in the new UEX, and all plans were unavailable due to dependencies, the waive selection was not properly saved. In addition, on certain benefits enrollment forms in the new UEX, if the employee waived benefits, clicked Next, and then clicked Back, the Waived status on plans was changed to Not Available. This is fixed. When no benefit plans are available due to dependencies, no waive selection is available, and the form is automatically counted as complete. This behavior mirrors the behavior of the Legacy user interface.
EERT-2399 When a new employee during Onboarding attempted to add a personal email address that had more than five characters in the top-level domain, the email address could not be saved. For example, name@company.design would return as an invalid email address, despite being a valid address. This is fixed. The Onboarding email address field now supports top-level domain addresses of any length.
EERT-2419 When an employee unchecked the Approve every employee enrollment field on the Edit Workflow form in the Workflow Library, the employee could not save the form. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202404/OB_Fixes_MR_202404.htm Path: OBE/Release-Notes/Fixes/2024/MR202404/OB_Fixes_MR_202404.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2334 When a user completed Section 1 of the I-9 Form in the new UEX, sent it for approval, and started Section 2, the user could continue to edit Section 1. This is fixed. Section 1 is now properly locked after it is completed and sent for approval.
EERT-2367 When a new employee attempted to use a foreign passport and I-94 form as documentation on the I-9 form during Onboarding, the system would require them to submit an I-20 form or DS-2019 form. Neither the I-20 form, nor DS-2019 form are specifically required for a new employee with a foreign passport. This is fixed. Employees submitting a foreign passport and I-94 form are no longer required to submit a third document for verification.
EERT-2381 The new UEX did not properly display markdown formatting and fonts on certain forms. As a result, certain customer forms that used the markdown formatting did not display correctly. This is fixed. The new UEX now features full support for the markdown formatting used by customer forms.
EERT-2386 When an employee using the Direct Deposit form during Onboarding attempted to clear the form by selecting the Cancel button, the Cancel and Save options would become grayed out, and nothing would happen. This is fixed. When the user cancels their direct deposit, they are returned to the main Direct Deposit form.
EERT-2394 When an Onboarding Complete Notification included the Hire Date substitution variable, the notification displayed an incorrect date instead of the actual hire date. This is fixed.
EERT-2399 When a new employee during Onboarding attempted to add a personal email address that had more than five characters in the top-level domain, the email address could not be saved. For example, name@company.design would return as an invalid email address, despite being a valid address. This is fixed. The Onboarding email address field now supports top-level domain addresses of any length.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202405/BE_Fixes_202405_MR.htm Path: OBE/Release-Notes/Fixes/2024/MR202405/BE_Fixes_202405_MR.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2398 When an employee accessed a form associated with the Voluntary (VOL) offer type during benefits enrollment, the running total was not calculated while accessing these forms or making selections. Navigating to other benefits enrollment forms would update the running total. This is fixed.
EERT-2405 After an employee submits a benefits enrollment workflow, the confirmation statements could not be properly sent to the employee via email on the Employee Last Confirmation form or the Employee Confirmation Statements form if the sender was a Worksite Manager. Service Providers and Trusted Advisors could still send the confirmation statements normally. This is fixed.
EERT-2437 When an employee completed signing their onboarding forms or benefit confirmation statements, the IP address was not properly saved in the record. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202405/OB_Fixes_MR_202405.htm Path: OBE/Release-Notes/Fixes/2024/MR202405/OB_Fixes_MR_202405.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2437 When an employee completed signing their onboarding forms or benefit confirmation statements, the IP address was not properly saved in the record. This is fixed.
OBE-8140 When an I9 Approver attempted to review an I9 form uploaded by an employee, the zoom on the form could not be changed. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202407/BE_Fixes_202407_MR.htm Path: OBE/Release-Notes/Fixes/2024/MR202407/BE_Fixes_202407_MR.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2366 When an employee proceeded through Benefits Enrollment for a New Hire Flexible-only plan, the workflow displayed the current year contribution options, but not the contribution options for the next year. Dual-plan years did display properly for other benefits types. This is fixed.
EERT-2427 When a user completed Benefits Enrollment for a plan set to auto-enroll with required beneficiaries, the beneficiary data was not properly saved to the Prism record. This is fixed.
EERT-2435 When an employee completed their benefits enrollment, records for beneficiaries who were also dependents were saved properly, but beneficiary-only records were not properly saved. This is fixed.
EERT-2482 When a proxy user completed an employee’s benefits enrollment, the Confirmation Statements form properly displayed the Proxy User details on the initial form, but did not save the details to the stored Confirmation Statements. This is fixed.
OBE-8390 When a user attempted to save a dependent as a spouse during Benefits Enrollment and already had a dependent marked as their spouse, a warning message displayed properly. However, the user could not edit the dependent to remove the second spouse label. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202407/OB_Fixes_MR_202407.htm Path: OBE/Release-Notes/Fixes/2024/MR202407/OB_Fixes_MR_202407.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2362 When an employee entered their address during the Onboarding process, the country was not properly populated automatically on the form. This is fixed.
EERT-2452 When an employee saved a form during the Onboarding process that was not a tax form but had “Tax” in the form name, the form was saved to the Tax Form folder, even if it should have been saved to the Signed Employee Documents or Other Documents folder. This is fixed.
EERT-2466 When an employee went through the Onboarding process for a Minnesota worksite location and filled out the state form, the field for number of days in a pay period was populated with incorrect information. This is fixed.
EERT-2525 When a user added a Tax Identification number during the Onboarding process, the number was added to the pdf during the workflow, but was not added properly to the W4 form in Prism. This is fixed. The Tax Identification number is now added properly on both forms.
EERT-2526 When a user entered direct deposit information that contained an extra ‘%’ character during Onboarding, the information was not properly transferred to the Employee Details form. This is fixed.
EERT-2531 When a user displayed the New Hampshire Wage Form in Onboarding, the pdf was not properly mapped. This is fixed.
OBE-8426 When a user duplicated a form in the Workflow Library and entered a new ID, the last character entered in the ID field was incorrectly omitted. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202408/OB_Fixes_MR_202408.htm Path: OBE/Release-Notes/Fixes/2024/MR202408/OB_Fixes_MR_202408.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2390 The Elect W-2 form’s acknowledgment did not display in the new UEX electronic signature format, and it displayed differently than other custom forms with an e-signature acknowledgment. This is fixed.
EERT-2397 When a user approved an I-9 Section 2 document using the same browser that was used to complete the onboarding process, the worksite employee’s name displayed on the I9 audit instead of the approver’s name. This is fixed.
EERT-2489 When employees went through the benefits enrollment process for certain providers, the FSA election section did not display properly. This is fixed.
EERT-2512 When a Service Provider or Worksite Manager submitted a Life Event workflow that has a documentation requirement via proxy, the Confirmation Statement was sent to the email address on the employee record rather than the recipient email address entered. This is fixed.
EERT-2545 When an employee enrolled in a Flexible Spending plan through Benefits Enrollment, the employee could continue after entering an Annual Election amount greater than the Plan Year Limit. This is fixed.
EERT-2550 When an employee’s Onboarding process is suspended from the Workflow Maintenance form, and the option to allow access to Employee Portal is selected, the Onboarding in Process flag was not properly cleared from the employee record. This is fixed.
EERT-2552 When an employee going through Benefits Enrollment made selections for Life and Critical Illness costs, the calculation experienced latency, causing the form to display $0 premiums on the confirmation statement and Benefits Enrollment forms. This is fixed.
EERT-2567 When a user entered information for the I-9 Section 2 form, the user could enter spaces into the First Supporting Document field, which could create errors in the system. This is fixed.
EERT-2580 When a user duplicated a form in the Form Library and removed an attached PDF from the copied form, the PDF file was deleted from the client’s documents and would no longer display on the original version of the form. This is fixed.
EERT-2594 When a user duplicated a workflow with a version number of 2.0 or greater, the new workflow was not saved as version 1, and an error occurred when the new workflow was assigned to an employee. Workflows with a version number starting with 1 could still be duplicated and saved without error. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202410/OB_Fixes_MR_202410.htm Path: OBE/Release-Notes/Fixes/2024/MR202410/OB_Fixes_MR_202410.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2537 The Substitute Variable <> in Benefits Enrollment notification templates did not pull data properly to display the employee’s personal email address. This substitute variable did work properly in Onboarding notification templates. This is fixed.
EERT-2557 When an employee completing the I-9 workflow provided Supporting Documents and uploaded files, then changed their answer to indicate they would provide documents to employer in person, the uploaded documents were not all properly removed. The first supporting document was removed, but the second was not, and the uploaded document was saved to the employee’s I-9 Documents folder. This is fixed. When an employee changes their selection, all previously uploaded files are now removed.
EERT-2597 Users with Inquiry access to the Web Enrollment Configuration form could delete and archive an employee’s Benefit Enrollment Workflow. This is fixed. Users with Inquiry access are now properly restricted from making changes on this form.
EERT-2639 If errors occurred during the Rehire Approval process, the Rehire Approval was not properly removed when a new approval record was created. This resulted in unnecessary approval records remaining in the system. This is fixed. When a new Rehire Approval record is created, any additional Rehire Approval records for that same user are removed from the system.
EERT-2648 When a user going through Benefits Enrollment selected both Limited FSA and Dependent Care FSA, and at lease one option had Terms and Conditions, those Terms and Conditions did not display properly on the Summary page. As a result, the user could not complete their Benefits Enrollment. This is fixed.
OBE-8656 When a user filled out underwriting questions during Benefits Enrollment and then switched their preferred language, their selected responses were not properly saved on the form. This is fixed.
OBE-8677 In a previous release, the Pet and Legal offer types were changed to no longer display an option to select Dependents, as neither plan included them. However, if an employee had added dependents to a Pet or Legal plan previously, the dependents were incorrectly retained on the plan during the Benefits Enrollment posting process. This is fixed. If any unnecessary dependent data exists on a Pet or Legal benefit plan, the dependent data is removed during the Benefit Enrollment posting process.
OBE-8680 When a Spanish version of the plan summary and additional documents were added to a benefits plan on the Benefits Enrollment Plan Details form, these documents did not display properly when a user set their preferred language to Spanish and went through Benefits Enrollment. This is fixed. The Spanish versions of the plan summary and additional documents now display properly when the preferred language is set to Spanish.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/MR202412/OB_Fixes_MR_202412.htm Path: OBE/Release-Notes/Fixes/2024/MR202412/OB_Fixes_MR_202412.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2564 During the Onboarding workflow, the I-9 Section 2 Approval was sometimes not created properly, which prevented the employee from finishing the Onboarding process. This is fixed. Additional logging has been added to attempt to prevent this issue from occurring in the future.
EERT-2702 In the Benefit Enrollment workflow, documents linked to a benefits plan using the Benefit Enrollment Plan Detail form displayed the document category instead of the document name and description. This is fixed.
OBE-8850 On the Benefit Enrollment Plan Details form, the English and Spanish text boxes for Evidence of Insurability were not independent, and editing one text box would change the other. This is fixed.
OBE-8856 Spanish characters in the text for the Onboarding and Benefits Enrollment workflows displayed incorrectly as a ? symbol. This is fixed. Please note that some invalid ? characters may still exist in the Form Library and Benefit Enrollment Plan Details forms which will be addressed in a future release.
OBE-8911 On the Benefit Enrollment Plan Details form, the Spanish Underwriting Questions Yes/No response displays as S? instead of Si’. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/QR202403/BE_Fixes_202403_QR.htm Path: OBE/Release-Notes/Fixes/2024/QR202403/BE_Fixes_202403_QR.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2297 When the Electronic Enrollment flag was disabled on the Control tab of the Client Details form, open enrollment workflows were still generated electronically. These workflows would display on the dashboard and result in notifications being sent to employees about their open enrollment in the system. This is fixed.
EERT-2324 When a user selected Benefits Enrollment for an employee on the Web Enrollment Configuration form, the Next Open Enrollment Effective Date field displayed ‘N’ instead of the appropriate date. This is fixed.
EERT-2329 When a user generated an Enrollment Status by Workflow/Client report, two u-umlauts (üü) were added to the entries in the Enrollment Status field. This is fixed.
EERT-2330 When a user attempted to enter an election amount on the Health Savings Account Form Name form during Benefits Enrollment, the form would refresh after the user typed each individual character. This is fixed. A message now displays indicating that the plan cost is being updated when changes are made to the election amount.
EERT-2333 When a user created a new form in the Form Library and uploaded a mapped pdf file, the pdf-mapped fields did not display on the Layout tab unless the user returned to the General tab and reopened the Layout tab. This is fixed.
EERT-2359 When a user accessed the Life Event Maintenance form, the form header and the Add Life Event button did not display properly. This is fixed.
EERT-2413 When an employee previously enrolled in $0 Employee Life Insurance Coverage, the employee coverage was updated to a salary multiplier or maximum coverage during the posting process. This is fixed. When an employee is enrolled at $0 Employee Life Coverage, the posting process keeps the employee coverage at $0 accordingly.
OBE-7643 During Benefits Enrollment, switching between forms and comparing statements on each form could result in the Compare bar becoming stuck. If the user compared planned on the Whole Life Prebuilt form, then compared plans on the Basic Life form, then returned to the Whole Life Prebuilt form and compared plans, they would be unable to remove selected plans or close the comparison. This is fixed.
OBE-7913 When an employee had a non-conforming dependent enrolled on their medical, dental, or vision benefits plans, the employee needed to complete required documentation. However, the documentation link did not display in the standard style for URLs, which could create confusion. This is fixed. The table has been restyled, and the URL now looks like a standard link.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/QR202403/OB_Fixes_QR_202403.htm Path: OBE/Release-Notes/Fixes/2024/QR202403/OB_Fixes_QR_202403.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2323 When a user added a conditional field to a custom form in the Form Library, the custom form could not be previewed. This is fixed.
EERT-2333 When a user created a new form in the Form Library and uploaded a mapped pdf file, the pdf-mapped fields did not display on the Layout tab unless the user returned to the General tab and reopened the Layout tab. This is fixed.
EERT-2335 When a hiring manager entered an employee’s Personal Email address as part of the New Hire process and the employee did not enter a Personal Email address on the I-9 or Employee Info forms, the Personal Email record did not update properly. In addition, if the employee entered a different Personal Email address than the hiring manager, the employee’s entry was not properly saved. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/QR202406/OB_Fixes_QR_202406.htm Path: OBE/Release-Notes/Fixes/2024/QR202406/OB_Fixes_QR_202406.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2363 When an employee added a spouse to their Voluntary Life coverage in the Benefits Enrollment Workflow, the Running Total field included the spouse contribution twice. The Running Total field on other forms in the Benefits Enrollment Workflow calculated the contribution amounts properly. This is fixed.
EERT-2375 When an employee added dependents to the Group Term Life plan in the Benefits Enrollment Workflow, the Running Total field did not properly update to include the dependents. This is fixed.
EERT-2429 When an employee viewed a life event on the Life Events widget that was initiated by a service provider or manager, the event would incorrectly display as being initiated by the employee. In addition, the Completed By field displayed incorrect information when benefit rules were used to determine the completion date. This is fixed.
EERT-2438 When a new employee entered pay card information on the Direct Deposits form during the onboarding process and attempted to delete the entry they just added, the Add Account option did not display. The employee had to refresh the screen to get the Add Account option to reappear. This is fixed.
EERT-2480 When the recipient of an email notification from Onboarding or Benefits Enrollment workflows is inactive, the notification would still be sent to the email address in the system. This is fixed. Inactive users no longer receive notifications.
EERT-2485 When an employee was enrolled in a benefits plan with Cafeteria Contributions the prior year and went through the open enrollment workflow, the Cafeteria Contribution from the prior year incorrectly displayed as applying to the new plan instead of the contribution from the current year. The correct deduction amounts were still applied during the payroll calculation process. This is fixed.
OBE-7370 When an employee first attempted to download the electronic Signed Consent Form during the Onboarding process, the download would fail. Attempting to download the form a second time worked correctly. This is fixed.
OBE-7665 During the I-9 documentation step of the Onboarding process, selecting certain options in the Type of Number field displayed an erroneous character. This is fixed.
OBE-8044 When an employee attempted to remove uploaded documents during the Onboarding process, the warning message text referred to the button incorrectly. This is fixed.
OBE-8193 When a worksite manager denied an I-9 approval on the My Approvals form or the My Approvals widget, the I-9 approval form remained open after the denial was confirmed. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/QR202409/OB_Fixes_QR_202409.htm Path: OBE/Release-Notes/Fixes/2024/QR202409/OB_Fixes_QR_202409.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2621 When an employee going through the Benefits Enrollment process attempted to select an HSA amount higher than the Max Individual value, they were unable to do so, even if their spouse or children qualified them for the higher Max Household value. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2024/QR202411/OB_Fixes_QR_202411.htm Path: OBE/Release-Notes/Fixes/2024/QR202411/OB_Fixes_QR_202411.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2504 When there was no Open Enrollment workflow assigned to the Client Workflow Grid form, but a workflow was assigned to the System Workflow Grid form, the dashboard for Benefits Enrollment workflows incorrectly displayed the client’s employees as eligible for open enrollment. This issue only impacted how the dashboard displayed, and employees were restricted from accessing benefits enrollment when enrollment was not open. This is fixed.
EERT-2579 When the I-9 Section 2 content was denied, and an employee completed their Onboarding workflow again to correct the issue, the Onboarding status bar did not update to show that all steps were complete. This is fixed.
EERT-2670 When a user filled out the second supporting document section on Section 2 of the I-9 Form and selected option C - Employment Auth. Document (DHS), the issuing authority of the document was mistakenly updated to display the U.S. Department of State instead of the Department of Homeland Security. This is fixed.
EERT-2679 When an employee chooses to waive a new benefit plan during Benefits Enrollment and did not have a previous election, the employee was still presented with a notification to remove their previous selection. This is fixed. Employees are no longer given a warning message about removing previous choices when waiving a new benefit plan.
OBE-8467 When a user attempted to edit forms in the Form Library, multiple display issues could occur with distorted, miscolored, or missing text. This is fixed.
OBE-8672 When a user displayed the Review I-9 Section 1 form or the I-9 Section 2 form, the text would be cut off along one side of each page. This is fixed.
OBE-8744 When a user built a form in the Form Library using the default ANCILLARY_PREBUILT form, text entered in the English section of the custom form did not display. Text entered in the Spanish section did display properly, but would display even if the user’s Preferred Language was set to English. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_MR_202501.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_MR_202501.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2497 When a crosshire employee required I9 Section 2 Approval, the email notification was not properly sent to the Worksite Manager assigned to the employee. This is fixed.
EERT-2503 If a user double clicked the link to Direct Deposit or Tax during the onboarding process, a blank page displayed. This is fixed.
EERT-2584 When an employee completes the Employee Information section of the I9, the address is corrected in the system to ZIP+4 digits. However, if the I9 is denied by a manager and resubmitted by the employee, the address was not corrected to ZIP+4 a second time. This is fixed.
EERT-2606 Sometimes, after submitting Employee Information in Onboarding, the system fails to create necessary employee records due to network issues or browser refreshes which would cause the workflow to fail upon submission. This is fixed.
EERT-2622 When an employee changed their address during the onboarding process, the employee’s geocode failed to update. This is fixed.
EERT-2682 When an employee selected certain offer types during Benefits Enrollment, a different offer was incorrectly saved, which caused Invalid Offer Type for Benefit Plan during the Posting process. This is fixed.
EERT-2692 When a user clicked the Continue button twice while entering a new hire on the New Hire form, duplicate entries were created which prevented the onboarding process from being completed. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_MR_202502.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_MR_202502.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2430 When a user attempted to enter a coverage amount on a disability plan during Benefits Enrollment using a mobile device, an error prevented the keyboard from displaying properly, preventing the user from completing the form. This form functioned properly for desktop devices. This is fixed.
EERT-2462 When a user entered an FSA/HSA election amount during Benefits Enrollment in the new UEX, if the user did not delete the default $0.00 amount before typing in a number, the system omitted the first digit entered in the field. This is fixed.
EERT-2522 When a user accessed the Approvals Pending Queue, the same employee could display as multiple pending approvals and confirmation statements. Approving any one record would remove the others from the Pending Queue, but the multiple confirmation statements would remain. This is fixed.
EERT-2549 If an employee was terminated and rehired on the same date, the employee information did not display properly in the Employee Details File Audit form. This is fixed.
EERT-2704 When a user accessed an employee’s benefit Confirmation Statement using the Employee Details form or the Employee Confirmation Statements form, the employee’s beneficiary information did not display. This is fixed.
EERT-2714 When a user entered an FSA or HSA election amount that used a decimal point during Benefits Enrollment, only the first digit after the decimal was saved in the system. This is fixed.
EERT-2720 When a user did not select coverage for overage dependents and listed them as beneficiaries only, the system incorrectly added coverage to these dependents. This is fixed.
EERT-2725 When a user attempted to submit an Employee Confirmation Statement using the Other tab on the Employee Details form, an error occurred. This is fixed.
EERT-2753 When an employee completed the I-9 section of the Onboarding process, in some instances Section 2 of the I-9 was unable to be located, preventing the employee from completing their onboarding properly. This is fixed. Additional trace logs have been added to assist in identifying the issue.
EERT-2775 Occasionally, when an employee received their Employee Confirmation Statement, incorrect wording from a different form appeared on the statement. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_QR_202503.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_QR_202503.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2370 When a user accessed the Benefit Summary and Confirmation forms, the text on the screen displayed incorrectly. In addition, the text in the Benefit Confirmation email message also displayed incorrectly. This is fixed.
EERT-2498 When a user selected the View Detail during Benefits Enrollment, the second digit after the decimal in values did not display if that digit was zero. This is fixed.
EERT-2717 For customers using Client Specific Custom Fields for New Hampshire, the fields on the New Hampshire Wage Form did not automatically populate properly. This is fixed.
EERT-2740 When a user selected the Employee Statuses search field on the Bulk Launch Benefit Workflow form, the prefilter did not work properly, resulted in long loading times while only displaying a limited number of results. This is fixed.
OBE-6181 On the Health Savings Account form in Benefits Enrollment, the estimated deductions warning made reference to ‘Flexible Spending’ contributions. This is fixed. The warning message now properly references Health Savings Accounts.
OBE-7938 When a user displayed batches of forms on the Post Benefit Enrollments form, the name in the Batch Name field could overlap the Batch Number field for very long batch names. This is fixed.
OBE-8199 The updated Default Forms for Confirm and Welcome included fields that were left blank, and users were unable to remove these empty fields. This is fixed. The empty fields have been removed from the default forms.
OBE-8639 When a Spanish language version was added for the Category Titles and Field Labels for an Onboarding and Benefits Workflow, the text still displayed the English version. This is fixed.
OBE-8899 If the Spanish Comparison Fields were left blank on the Define Offer Type Level Setup form, the Compare Benefits tool did not display properly during Benefits Enrollment, even if the Spanish language was not enabled. This is fixed.
OBE-8922 When a user added or updated a Spanish description for a benefit plan offer type such as FSA, HSA, or DEPFSA, the Spanish description of the plan did not display properly. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_R202504.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_R202504.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2617 The Web Enrollment Configuration can be manually created with a future Start Date; however, employees were able to access the workflow before this date. This is fixed.
EERT-2669 In some cases, after the I-9 approval process, the I-9 documents were not saved to Employee Documents. This is fixed.
EERT-2779 During the Onboarding process, the I-9 Section 2 Approval record would sometimes not be properly generated, preventing the I-9 process from being completed. This is fixed.
EERT-2785 In the Life Event workflow, employees could remove spouse and dependents from CRL plans even if the Allow Unenrollment option was not enabled. This is fixed.
EERT-2798 On the Bulk Launch Benefit Workflow form, the Return To The Pre-Filter Selections Page button did not function properly. This is fixed.
EERT-2818 When an employee’s preferred language was set to Spanish, the employee’s beneficiaries did not display on the Employee Confirmation Statement. This is fixed.
EERT-2844 When a user configured pay methods in the Business Rules Library form, Variable Salary was not available as a payment method. This is fixed.
EERT-2865 When a client used the Rules Engine, the Non-Conforming Dependent Benefit acknowledgment message did not display during Benefits Enrollment. This is fixed.
OBE-9139 When an employee displayed the Benefits Summary, and the language was set to Spanish, the English description for FSA/HSA plan types displayed instead. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_R202505.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_R202505.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2771 When a user selected the Define Plan Level Setup option on the Benefits Enrollment Plan Details form and attempted to save a record with attached documents, an error occurred. This is fixed.
EERT-2778 When an employee was enrolled in multiple voluntary benefit plans and viewed all options during Benefits Enrollment, options the employee was not enrolled in did not display properly. This is fixed.
EERT-2821 When an employee submitted Employee Information during the Onboarding process, employee records were sometimes not generated properly, resulting in an error message. This is fixed.
EERT-2839 When a user made edits to a workflow in the Workflow Library by removing forms from a category and deleting that category, the category was not properly deleted unless the removed forms were added to a different category. This is fixed.
EERT-2840 When a user made a change to a form which had a Business Rule attached to it in the Form Library, the Business Rule was removed from the form. This is fixed.
EERT-2845 When a user attempted to download a batch of enrollment statements using the Download Enrollment Statements form, an error occurred. This is fixed.
EERT-2846 When an employee submitted a Benefit Enrollment workflow, then made changes to their state of residence that made them ineligible for those benefits, the employee was prompted properly to redo their enrollment. However, the employee’s original benefit selection remained active in the system. This is fixed.
EERT-2847 When an employee selected the Child Only plan for life insurance coverage, the option to make their spouse a dependent could still be selected. This is fixed.
EERT-2852 When a user attempted to set up a new plan on the Benefit Plan Details form or make changes to an existing plan, an error occurred when the employee attempted to save the record. This is fixed.
EERT-2855 When a user had multiple VOL enrollments on the Life Events form, and Allow Un-Enrollment was not enabled, the user could still unenroll from all but one VOL offer. This is fixed.
EERT-2879 When the Onboarding process was initiated for a new hire, the Onboarding email message was sent to inactive Service Provider email addresses. This is fixed. Inactive Service Provider users are now excluded from the Onboarding email messages.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_R202506.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_R202506.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2863 For certain clients, the substitution variable for email messages did not work properly, and the Onboarding message did not contain the proper link for the new employee to start the Onboarding process. This is fixed.
EERT-2869 When an employee attempted to run the Enrollment Status by Workflow/Client report, the report did not process and display properly. This is fixed.
EERT-2878 When a Benefit Group was future-dated on an employee record, Network benefit plans did not take this new group into consideration. This is fixed.
EERT-2896 For certain clients, the electronic consent form did not display properly during the Onboarding process. This is fixed.
EERT-2900 When a user with an apostrophe in their name attempted to complete their I9 form using an Apple device, an error occurred. This is fixed.
EERT-2929 When an employee completed the Symmetry Tax forms, the document ID was not properly stored in the Prehires record. As a result, when the workflow was submitted, the workflow data review process reopened the Tax form. This is fixed.
OBE-9474 Employees were able to proceed through the tax form in the Onboarding workflow even when required fields on the Employer Details record (e.g., telephone number) were missing. This resulted in the tax forms reopening during the final submission of the workflow. This is fixed. Employees can no longer continue past the tax form until all required fields are completed. Important Note: After acknowledging the error message, employees will currently be redirected to the Onboarding Summary page instead of the next incomplete form in the workflow. If there is an unfinished form prior to the tax form, they will be taken to that form instead. We are actively working on a future update to ensure employees are directed to the next incomplete form in the workflow as intended.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_R202507.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_R202507.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2752 The Enrollment Status by Workflow/Client Report was not displaying correctly based on the workflow assigned on the System and Client Workflow Grid. This is fixed. Data will now display correctly based on what is on the System and Client Workflow Grids. If there is data on the Workflow Grid for an Open Enrollment with relevant dates, the report will display the employees as eligible.
EERT-2888 When an employee filled out their I9 form during the Onboarding process, Foreign Passport was missing from the dropdown menu when selecting options for a Lawful Permanent Resident. This is fixed.
EERT-2894 During the Onboarding process, the Birth Certificate Document C item did not properly mark the Issuing Authority field as a required field. This is fixed.
EERT-2917 When a position was added on the Positions form, the new position did not display properly on in the Business Rules Library. This is fixed.
EERT-2919 When a manager viewed the My Employees form in Employee Portal, the PTO Approver field did not display a name properly even if one was assigned. The PTO Approver did display properly on the Employee Details form. This is fixed.
EERT-2921 When a Dependent adult was added as a Beneficiary to certain plans within the Benefits Enrollment workflow and the workflow was saved, the Beneficiary was also added as a Covered Dependent on the plans, despite being over the age limit. This is fixed.
EERT-2927 When a manager without permissions to access Employee Details viewed the My Employees form in Employee Portal, Employee IDs displayed without the corresponding Employee Name. This is fixed.
EERT-2931 When the year was changed on the Total Compensation Statement form in Employee Portal, other values on the form were not properly updated and remained the same. This is fixed.
EERT-2944 When the Electronic Enrollment option on the Client Controls form was disabled, Onboarding and Benefits Enrollment notifications were still sent out. This is fixed.
OBE-9433 When an employee viewed the Language Survey during the Onboarding Process, the Confirm button did not always display properly, forcing the employee to start the form again. This is fixed.
OBE-9434 When an employee enters their middle name or middle initial during Onboarding, the information was not displaying tax forms. This is fixed. The middle initial will now display on the completed tax form when a middle name or initial is entered during onboarding.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_R202508.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_R202508.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2803 When a user entered a new hire on the New Hire form and obtained the prehire ID for the new employee, then resized their browser screen, a duplicate prehire record was created. This is fixed.
EERT-2962 When an employee edited a dependent on the Life Event form during Benefits Enrollment, the workflow would refresh but display different forms than those assigned to that Life Event. This is fixed. The Life Event now only displays formed assigned to that event on the Life Event Maintenance form.
EERT-2972 When an employee entered Direct Deposit information during the Onboarding process and entered the same routing number and account number for their Fixed account and Remaining account, the system erroneously displayed an error message about Health Savings Accounts. This is fixed. The error message now only displays when an employee enters the same routing and account number as their existing HSA.
EERT-2975 When no coverage amount was elected by the employee for Group Term Life Coverage, the employee coverage incorrectly posted based on the salary multiplier. This is fixed.
EERT-2986 When an employee’s form I-9 Section 1 was edited or denied, the employee was unable to submit their tax forms to complete Onboarding. This is fixed.
EERT-2992 When a new employee going through Onboarding attempted to enter Emergency Contact information, an error occurred with a message indicating that an employee record could not be created. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_R202509.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_R202509.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2945 When an employee attempted to submit a Birth Certificate as one of their ID documents during the I-9 Approval process, but left the Document Number field blank, an error message displayed incorrectly stating that the Expiration Date field was required. This is fixed. The message now correctly indicates that the Document Number field is blank and requires an entry.
EERT-2947 When a user ran the Enrollment Status Workflow/Client Report, and no results were returned, the report did not display at all. This is fixed. The report header now displays properly on a report that returns no results to indicate a successful report with no items returned.
EERT-3008 When a user accessed the Current Benefits form, and their language was set to Spanish, the Group Benefit Plan Type Description field did not display the Spanish text. This is fixed.
EERT-3042 When a user entered an override for the Employee Information menu name, this name did not display on the Submit Confirmation message. This is fixed.

========================================================================

Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/OBE/Release-Notes/Fixes/2025/OB_Fixes_R202510.htm Path: OBE/Release-Notes/Fixes/2025/OB_Fixes_R202510.htm

Fixes

When technical difficulties surface, we strive to resolve them right away. The following are recent known issues that we’ve fixed.

Jira # Issue Summary Resolution
EERT-2968 When an employee submitted the Benefits Enrollment workflow from Employee Portal or via proxy, the Total cost per period field did not display on the Confirmation Statement. This field did display properly on the Confirmation Statement when viewed from the Employee Details form or the Benefit Enrollment Maintenance form. This is fixed.
EERT-3050 When a Service Provider overrode the Employee Information menu names on the Configuration Templates or Client Overrides forms, the override did not display in the Browser URL or the Submit Confirmation window. This is fixed.
EERT-3051 When an employee made selections for their HSA or FSA plan during Benefits Enrollment, the employee could click the Next button and proceed to the next form before the plan had finished calculating or saving. This is fixed. Employees can only proceed to the next form once the plan has finished calculating, and the information has been saved.
EERT-3052 Employees could add non-numeric characters to the HSA Annual Contribution and FSA Annual Contribution fields during Benefits Enrollment, which resulted in a posting error. This is fixed.
EERT-3058 Multiple users could initiate the Post Benefits Enrollment process at the same time, potentially creating errors. This is fixed. Initiating the process now properly locks the process for other users.
EERT-3060 When a user filled out the I-9 form, the Section 2 approval message did not display properly. This is fixed.
EERT-3076 When the system attempted to send the Benefits Enrollment Confirmation Statement as an email message, an error occurred. This is fixed.
EERT-3086 When a user attempted to delete a document after a document upload, an error occurred. This is fixed.

========================================================================

Alternate ID for Independent Contractors

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2023/MR202302/CPR-3847_Alternate_1099_ID.htm Path: PD/Release-Notes/Enhancements/2023/MR202302/CPR-3847_Alternate_1099_ID.htm

Alternate ID for Independent Contractors

You can use the new Alternate ID field to assign an alternative identifier to independent contractors (1099 employees).

This new field is located on the Employee Details > Work tab, under the Miscellaneous panel.

This is intended for any service provider that needs to store a second identification number for independent contractors. For example, you might be required to associate contractors with their Social Security number and their business FEIN. Any value entered is masked automatically.

[Image: Alternate ID field on the Miscellaneous tab of Employee Work]

Note: Note: The field displays even if the employee is not a contractor (in other words, if the 1099 Contractor field is not selected). You can also hide this option from users by enabling field-level security on the User Roles form.

JIRA # CPR-3847

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202401/Documentation/New_Task_Sheets_MR202401.htm Path: PD/Release-Notes/Enhancements/2024/MR202401/Documentation/New_Task_Sheets_MR202401.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following task sheet was created:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202401/HumanResources/Employee_Details_Form_Enhancement_MR202401.htm Path: PD/Release-Notes/Enhancements/2024/MR202401/HumanResources/Employee_Details_Form_Enhancement_MR202401.htm

Enhancement to Employee Details Form

Previously, only service providers could add a manager from another client as a PTO approver.

Now, users logged in as worksite managers can enter a manager’s employee ID from a different client as a PTO approver.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16114

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202405/Documentation/New_Task_Sheets_MR202405.htm Path: PD/Release-Notes/Enhancements/2024/MR202405/Documentation/New_Task_Sheets_MR202405.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheet was updated:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Completed Payroll Notes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202405/Payroll/Completed_Payroll_Notes_Form_Enhancement_MR202405.htm Path: PD/Release-Notes/Enhancements/2024/MR202405/Payroll/Completed_Payroll_Notes_Form_Enhancement_MR202405.htm

Enhancement to Completed Payroll Notes Form

All payroll notes that are past their expiration date now automatically move to the Completed Payroll Notes form and display “Expired” in the Completed By column instead of the user who completed the payroll note. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-17122

========================================================================

Enhancement to SuperBatch Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202405/Payroll/SuperBatch_Form_Enhancement_MR202405.htm Path: PD/Release-Notes/Enhancements/2024/MR202405/Payroll/SuperBatch_Form_Enhancement_MR202405.htm

Enhancement to SuperBatch Form

The Pay Date Up To field on the SuperBatch form now displays as Cutoff Date Up To. In addition, the Cut Off Date column now displays as Cutoff Date. For example:

[Image: screenshot]

The system now defaults to displaying payrolls where the cutoff date is on or prior to the Friday of the current week. (Therefore, the system no longer uses pay dates to determine which payrolls to display.) For example, a payroll with a cutoff date of Monday, 4/1/2024, displays all payrolls with a cutoff date on or before 4/5/2024.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-17076

========================================================================

Enhancement to Tax Register Audit Inquiry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202407/Employer%20Administration/Tax_Register_Audit_Inquiry_Form_Enhancement_MR202407.htm Path: PD/Release-Notes/Enhancements/2024/MR202407/Employer Administration/Tax_Register_Audit_Inquiry_Form_Enhancement_MR202407.htm

Enhancement to Tax Register Audit Inquiry Form

The tax register audit process has been reconfigured, so it now automatically runs every day instead of once per week. (Previously, this process ran weekly.)

As part of this enhancement, the last run date now displays a weekday instead of a Sunday. For example:

[Image: screenshot]

Note: This form is only available for service providers. Also, you should only provide access to this form to users who are allowed to view all clients.

For more information, see the in-product help or PrismHREmployer Administration Guide.

JIRA # WSP-513

========================================================================

Enhancement to Global Employee Garnishment Setup Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202407/Global_Employee_Garnishment_Setup_Report_Form_Enhancement_MR202407.htm Path: PD/Release-Notes/Enhancements/2024/MR202407/Global_Employee_Garnishment_Setup_Report_Form_Enhancement_MR202407.htm

Enhancement to Global Employee Garnishment Setup Report Form

Previously, incorrect garnishment docket numbers displayed in the Global Employee Garnishment Setup Report, which has been fixed.

In addition, the Employee Id column now displays in this report. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRBenefits Enrollment User Guide.

JIRA # RRT-5849

========================================================================

Enhancement to New Hire Reporting Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202407/HumanResources/New_Hire_Reporting_Form_Enhancement_MR202407.htm Path: PD/Release-Notes/Enhancements/2024/MR202407/HumanResources/New_Hire_Reporting_Form_Enhancement_MR202407.htm

Enhancement to New Hire Reporting Form

To accommodate the state of Indiana now requiring electronic new hire reporting as of 7/1/2024, the downloaded file generated by selecting Indiana in the Report to State field on the New Hire Reporting form now includes the following additional information required to meet their file submission layout requirements:

Your organization uses the New Hire Reporting form to preview and build the file to send to states and report any new employees. For more information and instructions, refer to the PrismHR Human Resources User Guide or the in‑product help.

JIRA # RRT-5895

========================================================================

Enhancement to Bank Accounts Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202407/Payroll/Bank_Accounts_Form_Enhancement_MR202407.htm Path: PD/Release-Notes/Enhancements/2024/MR202407/Payroll/Bank_Accounts_Form_Enhancement_MR202407.htm

Enhancement to Bank Accounts Form

A new field, Same Day Processing, and its associated field, Cutoff Time, now reside on the Bank Accounts form, which is available on the System|Change menu. For example:

[Image: screenshot]

You can enable the Same Day Processing field if the bank account is used for same day processing. (If you enable this field, this information gets translated to the ACH file.)

After enabling the Same Day Processing field, the Cutoff Time field displays. You can select 1300 (default) or 1700 as the processing cutoff time.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # WSP-473

========================================================================

Enhancement to ACH Batch Control Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202407/System/ACH_Batch_Control_Form_Enhancement_MR202407.htm Path: PD/Release-Notes/Enhancements/2024/MR202407/System/ACH_Batch_Control_Form_Enhancement_MR202407.htm

Enhancement to ACH Batch Control Form

After a batch posts, the ACH Batch Control form now displays the total number of detail lines in the ACH file, along with the total number of debits and credits. For example:

[Image: screenshot]

Note: You can access the ACH Batch Control form by selecting a transaction in the ACH Processing form.

These new fields are helpful in determining the total count because they might be different from the totals that display in the Summary Information panel due to:

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # WSP-474

========================================================================

Enhancement to External Third Party Checks Journal Post Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202410/Payroll/External_Third_Party_Checks_Journal_Post_Form_Enhancement_MR202410.htm Path: PD/Release-Notes/Enhancements/2024/MR202410/Payroll/External_Third_Party_Checks_Journal_Post_Form_Enhancement_MR202410.htm

Enhancement to External Third Party Checks Journal Post Form

A new field, Days Back, now resides on the External Third Party Checks Journal Post form, which is available on the Operations|Action menu. For example:

[Image: screenshot]

You can use the Days Back field to display only the journal data pertaining to that selection, such as 1 Month (default), 2 Months, 3 Months, or 1 Year, or Show All data.

Note: If more than 1000 rows of data display, then paging controls are available to help you quickly move through the results.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # RRT-5906

========================================================================

Enhancement to SuperBatch Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202410/Payroll/SuperBatch_Form_Enhancement_MR202410.htm Path: PD/Release-Notes/Enhancements/2024/MR202410/Payroll/SuperBatch_Form_Enhancement_MR202410.htm

Enhancement to SuperBatch Form

You can now review reports for payroll batches in Wire Transfer Pending status (WT.PEND) in the SuperBatch form by selecting the

[Image: screenshot]

icon. (Previously, this icon was dimmed for these payroll batches.)

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-18131

========================================================================

Direct Logins From Informer

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202410/System/PP_Direct_Logins_Informer_MR202410.htm Path: PD/Release-Notes/Enhancements/2024/MR202410/System/PP_Direct_Logins_Informer_MR202410.htm

Direct Logins From Informer

A new configuration setting has been added to client databases to disable direct login from Informer. By default, this option is set to false and permits direct logins.

Note: Note: In the November release, this setting will be changed to disable direct logins from Informer by default.

Important! To configure this option, the PrismHR team must perform the change on your system. Contact your PrismHR representative for help with this setting.

JIRA # PP-1671

========================================================================

Enhancements to Retirement Export Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/MR202412/System/PP_Performance_Retirement_Export_MR12.htm Path: PD/Release-Notes/Enhancements/2024/MR202412/System/PP_Performance_Retirement_Export_MR12.htm

Enhancements to Retirement Export Form

Improvements have been applied to the Retirement Export form to increase performance and reduce exporting times.

JIRA # PP-1701

========================================================================

Enhancement to Billing Formats Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Billing/Billing_Formats_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Billing/Billing_Formats_Form_Enhancement_QR202403.htm

Enhancement to Billing Formats Form

A new tool tip now displays next to the Invoice Print Format field on the Billing Formats form, which is available on the System|Change menu. For example:

[Image: screenshot]

You can select a format for printing invoices in the Invoice Print Format field. For example, STACK Print 3Col by Break Stacked Version (WCSort on Template!).

For more information, see the in-product help or the PrismHRBilling User Guide.

JIRA # PD-16205

========================================================================

Enhancements to Client Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/Client_Details_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/Client_Details_Form_Enhancements_QR202403.htm

Enhancements to Client Details Form

The following enhancements now reside on the Client Details form, which is available on the Client|Change menu:

[Image: screenshot]

Note: If you enable One Payroll per Pay Group, the system creates separate payroll control batches when multiple pay groups have the same pay date.

[Image: screenshot]

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16406 and PD-16424

========================================================================

Enhancements to Commission Maintenance and Commission Plan Maintenance Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/Comm_Maint_CommPlan_Maint_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/Comm_Maint_CommPlan_Maint_Enhancements_QR202403.htm

Enhancements to Commission Maintenance and Commission Plan Maintenance Forms

To help standardize the commission Based On options, the following enhancements were made:

[Image: screenshot]

In addition, the Average Number Lives option now displays as Average Active Employee Count. For example:

[Image: screenshot]

[Image: screenshot]

In addition, the Average Employee Lives for CommCycle option now displays as Average Active Employee Count. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16319 and PD-16320

========================================================================

Enhancements to Commission Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/Commission_Maintenance_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/Commission_Maintenance_Form_Enhancements_QR202403.htm

Enhancements to Commission Maintenance Form

The following enhancements now reside on the Commission Maintenance form, which is available on the Client|Change menu:

[Image: screenshot]

Note: You can access the Commission Maintenance form by selecting Commissions on the Action menu in the Client Details form.

When setting up commissions on the client level, users are no longer allowed to set up both client and system-level plans on the same line. If they attempt this setup and click Accept, an error message now displays. For example:

[Image: screenshot]

Note: After clicking OK, the system returns to the form without saving the line.

[Image: screenshot]

You can use this column to apply additional based-on types to commission rules at the client level, such as Percent of Bill Code, Profits on Admin, Workers’ Comp Profit, Benefit Commission Type, and Benefit Commission Percentage.

[Image: screenshot]

These options do the following:

Note: If both a client-level and a system-level plan are applied, then the system calculates the commissions based on the system-level plan.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16372, PD-16373, PD-16438, and PD-16441

========================================================================

Enhancements to Commission Plan Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/Commission_Plan_Maintenance_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/Commission_Plan_Maintenance_Form_Enhancements_QR202403.htm

Enhancements to Commission Plan Maintenance Form

The following enhancements now reside on the Commission Plan Maintenance form, which is available on the Operations|Change menu:

After saving a commission plan, the system no longer applies any updates to the plan if it is already in use at the client level. For example, if you create commission plan A and apply it to client 123, then update commission plan A and save the updates the system displays an error message:

[Image: screenshot]

Note: You can make updates to any plans at the system level that are not applied to clients. After you apply the plan to a client, it cannot be updated.

[Image: screenshot]

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16321 and PD-16322

========================================================================

Enhancements to Compute Commissions Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/Compute_Commissions_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/Compute_Commissions_Form_Enhancements_QR202403.htm

Enhancements to Compute Commissions Form

The following enhancements now reside on the Compute Commissions form, which is available on the Operations|Action menu:

[Image: screenshot]

These new columns can help assist you in understanding the information produced in this report. For example, there could be several salespeople for one client in an invoice, so each salesperson now has their own line item associated with their calculated commission.

[Image: screenshot]

Click the Download Pay File link to download a .csv file that contains the commission data that was just calculated. For example:

[Image: screenshot]

Note: Note the following:

Note: The system calculates these options using the same process at the client level that is currently done at the system level in conjunction with the Based On Item option.

For more information, see the in-product help, PrismHRClient Administration Guide, and PrismHR System Administration Guide.

JIRA # PD-16323, PD-16377, PD-16512, and PD-16532

========================================================================

Enhancement to Enhanced Dashboard

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/Enhanced_Dashboard_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/Enhanced_Dashboard_Enhancement_QR202403.htm

Enhancement to Enhanced Dashboard

Selecting the Terminated option when Status Classification is selected in the Enhanced Dashboard now populates the Terminated Date field instead of the Hire Date field. For example:

[Image: screenshot]

Note: Employee termination dates are found in the employee’s record in the Employment panel on the Employee Details form, including the status date. (You can access the Employee Details form by selecting an employee in the Employee Name column.)

For more information, see the in‑product help.

JIRA # PD-13429

========================================================================

Enhancement to Invoices Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/Invoices_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/Invoices_Form_Enhancement_QR202403.htm

Enhancement to Invoices Form

A new mass download button

[Image: Mass Download icon]

was added to the Invoices form, which is available on the Client|View menu.

[Image: Invoice form with mass download button highlighted]

Click the icon to download a zip file containing all invoices for the selected year. The zip file is saved to your Downloads folder.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-15321 and 16531

========================================================================

Enhancement to New Client Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Client/New_Client_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Client/New_Client_Form_Enhancement_QR202403.htm

Enhancement to New Client Form

Previously, the system did not display an error message when users entered more than nine digits in the Federal ID Number field on the New Client form, which is available on the Operations|Action menu. The system now displays the following error message if you enter an EIN or a FEIN that is more than nine digits:

[Image: screenshot]

Click OK to continue. When you return to the New Client form, enter a nine-digit EIN or FEIN in the Federal ID Number field.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16035

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Documentation/New_Task_Sheets_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Documentation/New_Task_Sheets_QR202403.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following new task sheets are now available:

The following existing task sheets were updated:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancements to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Employee_Details_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Employee_Details_Form_Enhancements_QR202403.htm

Enhancements to Employee Details Form

The following enhancements now reside on the Employee Details form, which is available on the HR|Change menu:

[Image: screenshot]

If you do not set up both accounts on the Deposit tab, the following warning displays:

[Image: screenshot]

This warning is useful to remind users that if the company makes HSA contributions to employee accounts but they did not set up the company’s HSA deposit account associated with the employee’s record, then funds become lost.

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

Note: Clicking the Save button saves the current employee changes, but does not close the employee record.

Note: Note the following about the save banner:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-15248, PD-15490, PD-15498, PD-15500, PD-15502, PD-15532, PD-16314, and PD-16763

========================================================================

Enhancements to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Employee_Fields_Import_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Employee_Fields_Import_Form_Enhancements_QR202403.htm

Enhancements to Employee Fields Import Form

The following enhancements now reside on the Employee Fields Import form, which is available on the Operations|Action menu:

[Image: screenshot]

[Image: screenshot]

You can use these field codes to perform a mass update of the tax information for employees in their Employee Details record.

Observe the following guidelines when importing values for these field codes:

Field Code Description
Deductions You must enter a dollar amount.
Federal Claim Dependents You must enter a dollar amount.
FICA Exempt This is a Yes/No option. > Note: Note the following: - Yes, No, Y, and N are acceptable. - A blank field is equal to No.

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

You can use these field codes to perform a mass update of information for employees in their Employee Details record.

Observe the following guidelines when importing values for these field codes:

Field Code Description
1099 Contractor This is a Yes/No option. > Note: Note the following: - Yes, No, Y, and N are acceptable. - A blank field is equal to No.

[Image: screenshot]

To delete a template:

  1. Select the template you want to delete in the Use template field. The template displays in the Save Selected Fields as a Template (optional) section.

  2. Click Delete Template.

  3. A message displays, “Are you sure you want to delete this template?” Select Yes to remove the template from the list of available templates.

Note: After you delete a template, you can reuse the template name and ID to create a new template.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-15771, PD-16199, and PD-16200

========================================================================

Enhancement to Employee PTO Detail Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Employee_PTO_Detail_Report_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Employee_PTO_Detail_Report_Form_Enhancement_QR202403.htm

Enhancement to Employee PTO Detail Report Form

Previously, the system displayed the employee’s Hourly Rate on the Employee PTO Detail Report (both on-screen and when exported) for worksite managers and worksite trusted advisors with the Time Sheet Entry (w/o Pay Rates) Human Resources role set on the Users form and the PTO Absence Summary Report with Buyback option set on the Employee PTO Detail Report form.

To prevent this from happening, the system now validates that the employee’s Hourly Rate no longer displays in the report in this scenario.

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-16605

========================================================================

Removal of Event Categories Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Event_Categories_Form_Removed_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Event_Categories_Form_Removed_QR202403.htm

Removal of Event Categories Form

Due to event categories not being used in PrismHR, the Event Categories form and its functionality has been removed from the system.

JIRA # PD-15377

========================================================================

Enhancement to Rehire Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Rehire_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Rehire_Form_Enhancement_QR202403.htm

Enhancement to Rehire Form

Previously, the New Hire Questions form for work locations that required questions during an employee rehire did not display if the worksite location did not change. (This form only displayed if you entered or selected a new worksite location or re-selected the same location.)

Now, when an employee assigned to a worksite location associated with new hire questions is rehired, the New Hire Questions form automatically displays in the Rehire form, which is helpful because the questions might have changed since the employee was last hired. For example:

[Image: screenshot]

Note: You can set new hire questions on the State Rules form. The state listed in the worksite location determines the questions that are asked.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-15348

========================================================================

Enhancement to Self Identity Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Self_Identity_Codes_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Self_Identity_Codes_Form_Enhancement_QR202403.htm

Enhancement to Self Identity Codes Form

A new field, Gender Designation Description (Spanish), now resides on the Self Identity Codes form, which is available on the System|Change menu. For example:

[Image: screenshot]

You can use the Gender Designation Description (Spanish) field to designate a Spanish gender designation that the Onboarding workflow uses during Spanish onboarding.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-15212

========================================================================

Enhancement to Status Type History Adjustment Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Status_Type_History_Adjustment_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/HumanResources/Status_Type_History_Adjustment_Form_Enhancement_QR202403.htm

Enhancement to Status Type History Adjustment Form

Previously, users could only change an employee’s original hire date in the Status Type History Adjustment form if there were no other history records. When there were more records than the original hire date, users had to submit a request with PrismHR Customer Support to make this update on the back end.

You can now update the following dates for any history record using an enhanced method now available in the Status Type History Adjustment form:

To update these dates when there are more records than the original hire date:

  1. Click the link in the Date Effective column for the effective date you want to update. The system highlights the line you selected.

  2. Click the Change Date button that displays. A warning displays:

[Image: screenshot]

  1. Click OK to continue.

  2. The dates available for updating display on the right side of the form. For example:

[Image: screenshot]

  1. Select the dates you want to change.

  2. Click Submit.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16142

========================================================================

Enhancements to Approvals Pending Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Approvals_Pending_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Approvals_Pending_Form_Enhancements_QR202403.htm

Enhancements to Approvals Pending Form

The following enhancements now reside on the Approvals Pending form, which is available on the Client|Action menu:

The system now displays the approver’s user name in the Generated By column for users logged in as worksite managers for the following approval types:

When you select a Pay Rate Change approval link in the Approvals Pending form, the Approval form displays where you can “grab” an approval. The Detail section in this window now displays the New Standard Hours and Auto Pay Time Card data rows. For example:

[Image: screenshot]

These new data rows display the following information entered on the Pay Rate Change form:

For more information, see the in-product help or PrismHR Approvals Guide.

JIRA # PD-8747 and PD-15920

========================================================================

Enhancement to Bill Pending Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Bill_Pending_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Bill_Pending_Form_Enhancement_QR202403.htm

Enhancement to Bill Pending Form

The system now applies an E-Verify fee in the Bill Pending form for each new hire when the Submit for E-Verification field is enabled on the New Hire form. After saving the new hire, the system automatically creates a bill pending fee using the new EV-FEES bill code. For example:

[Image: screenshot]

Note: Note the following:

For more information, see the in-product help or PrismHR Payroll Processing Guide.

JIRA # PD-15247

========================================================================

Enhancements to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Data_Import_Tool_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Data_Import_Tool_Enhancements_QR202403.htm

Enhancements to Data Import Tool

The following enhancements now reside in the Data Import Tool, which is available on the Operations|Import Processing menu:

[Image: screenshot]

Note: The Backup Account Assignment import template is only available for service providers.

To import this data, select Backup Account Assignment from the Import Template menu, and then click Find File to upload the file.

Note: Note the following:

[Image: screenshot]

Note: The Client Benefits import template is only available for service providers.

To import this data, select Client Benefits from the Import Template menu, and then click Find File to upload the file.

Note: Note the following:

[Image: screenshot]

Note: The Client Commissions import template is only available for service providers.

To import this data, select Client Commissions from the Import Template menu, and then click Find File to upload the file.

Note: Note the following:

[Image: screenshot]

You can use this new field to define the client’s work category, such as CON for Construction.

Note: Note the following:

[Image: screenshot]

Note: The Employer Tax Rates (SUTA) import template is only available for service providers.

To import this data, select Employer Tax Rates (SUTA) from the Import Template menu, and then click Find File to upload the file.

You can also access this new import template by clicking the Import icon that now displays on the Employer Tax Rates (SUTA) form, accessible from the Employer|Change menu. For example:

[Image: screenshot]

Note: Note the following:

[Image: screenshot]

Note: The Pay Code Total Compensation Category import template is only available for service providers.

To import this data, select Pay Code Total Compensation Category from the Import Template menu, and then click Find File to upload the file.

You can also access this new import template by clicking the Import icon that now displays on the Pay Codes form, accessible from the System|Change menu. For example:

[Image: screenshot]

Note: Note the following:

[Image: screenshot]

You can use this new field to define whether the worksite geocode will be ignored and taxes will be based on the employee’s resident geocode. (Workers Compensation will also follow the resident geocode when enabled on the Benefit tab in the Client Details form.)

For more information, see the in-product help, PrismHREmployer Administration Guide, PrismHR Payroll Administration Guide, or PrismHRPayroll Setup Guide.

JIRA # PD-15195, PD-15604, PD-15807, PD-15871, PD-16196, PD-16375, and PD-16427

========================================================================

Enhancement to Pay Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Pay_Codes_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Pay_Codes_Form_Enhancement_QR202403.htm

Enhancement to Pay Codes Form

A new field, Total Compensation Category, now displays in the Processing Options panel on the Pay Codes form, which you can access on the System|Change menu. For example:

[Image: screenshot]

You can select the Direct or Indirect category in the Total Compensation Category field to designate where the compensation displays in the total compensation statement in the Total Compensation dashboard in Employee Portal (EP).

Note: This enhancement is useful because you can simply set the category in the Pay Codes form instead of updating every pay code in the Total Compensation Report Setup form.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-15806

========================================================================

Enhancement to Pay/Deduction Register Adjustments Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Pay_Deduction_Register_Adjustments_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Pay_Deduction_Register_Adjustments_Form_Enhancement_QR202403.htm

Enhancement to Pay/Deduction Register Adjustments Form

The original error message that displayed during processing when using the Pay/Deduction Register Adjustments form, “Could not client 14254 on the Employee,” now displays as “Could not find client XXX on the Employee Record,” to help alleviate confusion when this error occurs.

For more information, see the in-product help or PrismHR Adjustment Processing Guide.

JIRA # PD-16734

========================================================================

Enhancement to Payday Notifications

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payday_Notifications_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payday_Notifications_Enhancement_QR202403.htm

Enhancement to Payday Notifications

The process of sending payday notifications has been enhanced to help inhibit these notifications from going directly to spam.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-16743

========================================================================

Enhancement to Payroll Calculation Error Message

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Calculation_Error_Message_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Calculation_Error_Message_Enhancement_QR202403.htm

Enhancement to Payroll Calculation Error Message

Previously, when an employee received pay less than zero ($0), the system displayed a payroll calculation error message that did not specify the employee ID or the data tested, “Employee BENEFIT TESTING has a total pay < zero. Not Allowed!”

During this situation the following message now displays providing the information you need to identify the affected employee, “Employee <Employee ID> <Employee Name> has a total pay of less than zero. This is not allowed.”

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-14214

========================================================================

Enhancements to Payroll Notes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Notes_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Notes_Form_Enhancements_QR202403.htm

Enhancements to Payroll Notes Form

The following enhancements now reside on the Payroll Notes form, which you can access on the Client|View menu or by selecting Payroll Notes on the Actions menu in the Client Details form.

New Filters Section

A new section, Filters, now displays. For example:

[Image: screenshot]

You can use the new filters and Find Payroll Notes button to narrow an employee search for the current client.

To narrow an employee search, use the following methods:

Note: Note the following when using the filters:

Reordered Columns

For easier review, the columns on this form were reordered and now display as follows:

Update to Display Mode and Urgent Columns

To make the list of payroll notes easier to review, the Display Mode and Urgent columns now display the data’s description, not the code. For example:

[Image: screenshot]

These columns now display the following descriptions:

Column Description (Code)
Display Mode One Time (Y) All Payrolls (N) Scheduled Payrolls (S)
Urgent Yes (Y) No (N)

New Cancel Button

A new button, Cancel, now displays. For example:

[Image: screenshot]

Click Cancel to clear any filters that you set, which resets them to the default setting.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-16001, PD-16006, PD-16008, and PD-16014

========================================================================

Enhancement to Payroll Status Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Status_Report_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Status_Report_Form_Enhancement_QR202403.htm

Enhancement to Payroll Status Report Form

The report parameters on the Payroll Status Report form and the Payroll Status Report output, which is available on the Operations Payroll|Report menu, have been updated to allow for better monitoring of payrolls and their progress. For example:

[Image: screenshot]

The report parameters were updated as follows:

Note: The values must be entered in date format. In addition, the start date cannot occur after the end date and the end date cannot occur before the start date.

Note: Selected steps do not display in the report header.

The following column updates now reside in the output on the Payroll Status Report:

For example:

[Image: screenshot]

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-16125 and PD-16546

========================================================================

Enhancement to Payroll Variance Reports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Variance_Reports_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Variance_Reports_Form_Enhancement_QR202403.htm

Enhancement to Payroll Variance Reports Form

A new column, Type, now displays in the Payroll (Benefits, Deduction, Pay, or Tax) Variance Report, which you can generate using the Payroll Variance Reports form. For example:

[Image: screenshot]

The Type column displays the option selected in the Variance Report Type field on the Payroll Variance Reports form. For example, if the report type is Benefits then the Type column displays “Benefit” on every line.

Note: If you select All as the Variance Report Type (as displayed in the screenshot above), then each line displays the report type for that payroll.

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-15419

========================================================================

Enhancement to Payroll Voucher Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Voucher_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Payroll_Voucher_Form_Enhancement_QR202403.htm

Enhancement to Payroll Voucher Form

Previously, after payroll processed, the system listed multiple retirement loans for an employee as one line item on the voucher on the Deductions tab in the Payroll Voucher form.

Now, each retirement loan displays as their own line item on the voucher after payroll processes. For example:

[Image: screenshot]

Note: Associated payroll reports now display multiple employee retirement loans on separate lines.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-16160

========================================================================

Enhancement to PEO Client Accounting Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/PEO_Client_Accounting_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/PEO_Client_Accounting_Form_Enhancement_QR202403.htm

Enhancement to PEO Client Accounting Form

When the Use Non-Bill Accounting field is enabled on the PEO Client Accounting form, the system now displays a warning if you do not enter a value in the EE Tax Account field and click Save. (This warning helps prevent payroll failure.) For example:

[Image: screenshot]

Click OK to continue.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-16381

========================================================================

Enhancement to Recurring Deductions and Scheduled Deductions Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Recurring_Deds_Sched_Deds_Enh_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Recurring_Deds_Sched_Deds_Enh_QR202403.htm

Enhancement to Recurring Deductions and Scheduled Deductions Forms

Previously, users were able to manually enter deduction codes and save the record in the Recurring Deductions and Scheduled Deductions forms if the codes existed at the global level even though they did not display on the Deduction Codes list in the Control tab on the Client Details form.

To prevent users from manually entering restricted deduction codes in the Recurring Deductions and Scheduled Deductions forms a warning now displays when users click Save, “Warning - <deduction code> is not a deduction code defined on the <client> Client Detail Control tab.” Click OK to continue.

Note: Note the following:

For more information, see the in-product help, PrismHRPayroll Overrides Guide or PrismHRPayroll Administration Guide.

JIRA # PD-15099

========================================================================

Enhancement to Reprinting Payroll Checks

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Reprinting_Payroll_Checks_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Reprinting_Payroll_Checks_Enhancement_QR202403.htm

Enhancement to Reprinting Payroll Checks

Previously, worksite managers and worksite trusted advisors who were assigned the Payroll - Prints Checks HR Role in the Users form had to click the question mark icon in the Payroll Reports form and then click the Rebuild field in the Reprint Payroll Checks form to reprint payroll checks.

To make printing and rebuilding payroll checks more user-friendly for worksite managers and worksite trusted advisors, these users can now simply select the Reprint Payroll Checks link in the Payroll Reports form.

Note: The Reprint Payroll Checks link is disabled for worksite managers and worksite trusted advisors who are not assigned the Payroll - Prints Checks HR Role.

For more information, see the in-product help, PrismHR Payroll Administration Guide, or PrismHR Payroll Reports guide.

JIRA # PD-15921

========================================================================

Enhancement to Scheduled Payments Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Scheduled_Payments_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Scheduled_Payments_Form_Enhancement_QR202403.htm

Enhancement to Scheduled Payments Form

The system now prevents users from entering or selecting client-restricted pay codes (those codes not assigned to the client) in the Pay Code field on the Scheduled Payments form, which is available on the Payroll|Change menu. (These restricted pay codes include those restricted at the client level on the Control tab in the Client Details form in the Pay Code field. If deduction codes are set, then only those codes are available for that client.)

Note: Note the following:

For more information, see the in-product help or PrismHR Payroll Overrides Guide.

JIRA # PD-15261

========================================================================

Enhancement to Tax Adjustment Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Tax_Adjustment_Import_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Tax_Adjustment_Import_Form_Enhancement_QR202403.htm

Enhancement to Tax Adjustment Import Form

Three new fields, Location, Special Options Code, and Residential Geocode Override, which display at the end of the import, can now be imported using the Tax Adjustment Import form, which is available on the Payroll|Change menu.

Note: You can configure the settings for these fields on the Tax Adjustments form, which is available on the Payroll|Change form.

Note: Note the following about these fields:

For more information, see the in-product help or PrismHR Adjustment Processing Guide.

JIRA # PD-16242

========================================================================

Enhancement to Third Party Check Advice Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Third_Party_Check_Advice_Report_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Third_Party_Check_Advice_Report_Form_Enhancement_QR202403.htm

Enhancement to Third Party Check Advice Report Form

A new field, Check Date, now resides on the Third Party Check Advice Report form, which is available on the Payroll|Report menu. For example:

[Image: screenshot]

The Third Party Check Advice Report retrieves garnishment or non-garnishment third party check information that details employees and component amounts included in the third party check.

You can select the Check Date field instead of the Batch Number to display to and from date fields, where you can enter a date range for the Check Type.

Note: You can only enter or select valid dates in the to and from date fields. Once you enter the to date, you must enter the from date to proceed. Also, when you select Check Date, the Third Party Batch field name changes to Batch Number.

In addition, the report output now displays the date range in the report header that you entered or selected. For example:

[Image: screenshot]

Note: All check dates from the date range you entered or selected are included in the report output, regardless of batch.

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-15844

========================================================================

Enhancements to Time Sheet Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Time_Sheet_Entry_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Time_Sheet_Entry_Form_Enhancements_QR202403.htm

Enhancements to Time Sheet Entry Form

The following enhancements now reside on the Time Sheet Entry form on the Payroll|Action menu:

Accepting Leave Requests

As an extension to working with Global PTO Plans, leave requests made in the Employee Portal that the system pulls into timesheets using the red dot can now be accepted there. For example:

[Image: screenshot]

Note: The Global PTO Plans feature allows you to set up PTO plans on the system level and automatically assign those plans to employees based on work location.

Entering a Payroll Note

You can now enter a payroll note directly from the Time Sheet Entry form by clicking the

[Image: screenshot]

icon. Clicking this icon opens the Payroll Notes form, where you can click New Note to add a note. For example:

[Image: screenshot]

In addition, you can now narrow an employee search for the current client using the options and selecting Find Payroll Notes in the new Filters section, as shown above. (See Enhancements to Payroll Notes Form.)

Clicking New Note opens the Payroll Notes form, where you can add the note. For example:

[Image: screenshot]

Enhanced Payroll Notes

To improve consistency across all payroll notes, the column headers and information that display on the Payroll Notes form have been enhanced, so the information is easier to review. For example:

[Image: screenshot]

Note: Note the following:

Filtering by Pay Method

Service providers, worksite managers, and worksite trusted advisors can now filter a timesheet by pay method, which is useful when entering employee hours.

In association with this enhancement a new column, Pay Method, now displays when you select the Filter

[Image: screenshot]

icon. For example:

[Image: screenshot]

To filter the timesheet by pay method, select an option in the Pay Method column, then click Close. (A blue checkmark displays next to each selected option.)

Note: The No. column displays the number of employees for each status.

For more information, see the in-product help, PrismHR Payroll Administration Guide, PrismHR Payroll Processing Guide, or PrismHR Paid Time Off User Guide.

JIRA # PD-14613, PD-15834, PD-16004, PD-16015, PD-16016, PD-16017, and PD-16748

========================================================================

Enhancement to Unbundled Billing Additional Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Unbundled_Billing_Additional_Details_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Unbundled_Billing_Additional_Details_Form_Enhancement_QR202403.htm

Enhancement to Unbundled Billing Additional Details Form

To suppress the billing (delivery fee) for a manual check that occurs when a billing rule is processing live checks, a new field, Exclude From Manual Check, now displays on the Unbundled Billing Additional Details form when the Use If Any Check field is selected. For example:

[Image: screenshot]

Note: You can access the Unbundled Billing Additional Details form by selecting Additional Conditions from the Actions menu on the Billing Rules (Unbundled) form.

To suppress the billing (delivery fee) for a manual check:

  1. Select one of the following rules in the Based On field in the Billing Rules (Unbundled) form:

  1. Select Use If Any Check in the Unbundled Billing Additional Details form.

  2. Select Exclude From Manual Check to prevent the system from processing billing on a manual check.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-11084

========================================================================

Enhancements to Update Payroll Notes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Update_Payroll_Notes_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/Payroll/Update_Payroll_Notes_Form_Enhancements_QR202403.htm

Enhancements to Update Payroll Notes Form

The following enhancements now reside on the Update Payroll Notes form that make it easier to enter a payroll note:

[Image: screenshot]

Note: To access the Update Payroll Notes form, select New Note in the Payroll Notes form, which displays on the Client|View menu.

[Image: screenshot]

Note: You must disable the Worksite User Viewable field to prevent worksite managers and worksite trusted advisors from viewing the note.

[Image: screenshot]

Previously, users were unable to complete a note without deleting it. Now users can click Complete, which closes the note and removes it from the current payroll note list on the main Payroll Notes form, but allows users to review the note history at a later date.

Note: After clicking Complete, you can only review the completed note on the Completed Payroll Notes form. (The information pertaining to who completed the note displays on that form.)

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-16007 and PD-16019

========================================================================

Enhancement to Employee PTO Register Adjustment Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/PTO/Employee_PTO_Register_Adjustment_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/PTO/Employee_PTO_Register_Adjustment_Form_Enhancement_QR202403.htm

Enhancement to Employee PTO Register Adjustment Form

When you archive a register, you cannot adjust it. Therefore, to prevent users from making an adjustment to an archived register, these register types do not display as an option in the Register Type field on the Employee PTO Register Adjustment form.

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-16104

========================================================================

Enhancements to Employee PTO Register Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/PTO/Employee_PTO_Register_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/PTO/Employee_PTO_Register_Form_Enhancements_QR202403.htm

Enhancements to Employee PTO Register Form

You can now archive a PTO register for an employee using the Employee PTO Register form, which is available on the Work Centers|PTO Adjustments and Maintenance|Maintenance menu.

Archiving a PTO Register for an Employee

You can now archive a PTO register for an employee using the new Archive button. For example:

[Image: screenshot]

Clicking Archive terminates a PTO register for an employee while keeping an historical record of that register so you can refer to this information when seeking answers about what was done in the past.

Note: You must select an Employee and Register Type to enable the Archive button.

When you click Archive a warning displays describing what happens to pending PTO requests. For example:

[Image: screenshot]

After clicking OK, the following message displays:

[Image: screenshot]

Clicking Yes clears the fields on the form. (Click No to return to the form to make updates.)

Note: After archiving a PTO register, the plan no longer displays in Employee Portal (EP) and the system no longer makes additional accruals.

After Archiving a PTO Register for an Employee

After archiving a PTO register, the system places it into an Archived folder as a read-only record. You can review the archived register’s historical information, including the Benefit End Date. However, you cannot make any adjustments to the archived register. (At this time, the Save and Delete buttons are disabled.)

When you select the Register Type field for an archived record, the list displays “Archived” at the end of the register type. For example:

[Image: screenshot]

Note: Note the following:

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-15934, PD-16090, PD-16091, PD-16092, PD-16105, and PD-16220

========================================================================

Enhancement to PTO Absence Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/PTO/PTO_Absence_Codes_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/PTO/PTO_Absence_Codes_Form_Enhancement_QR202403.htm

Enhancement to PTO Absence Codes Form

Previously, users were able to select pay codes that were not assigned to the client in the Control tab on the Client Details form and save the record in the PTO Absence Codes form.

To prevent users from entering or selecting unassigned pay codes in the PTO Absence Codes form, the system now validates that only restricted pay codes for the client display in the Search Pay Codes list.

Note: Note the following:

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-15279

========================================================================

Enhancements to PTO Benefit Plans Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/PTO/PTO_Benefit_Plans_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/PTO/PTO_Benefit_Plans_Form_Enhancements_QR202403.htm

Enhancements to PTO Benefit Plans Form

The following enhancements now reside on the PTO Benefit Plans form, which is available on the Work Centers|PTO|PTO Plan Setup and Enrollment menu:

[Image: screenshot]

Note: The First Year Prorated Amounts panel only displays if you select Flat Amount in the Calculation Basis field.

You can use the First Year Prorated Amounts panel to change the number of hours employees will receive in their first year of employment, which helps handle numerous PTO changes to ensure employee records are correctly maintained. For example, if a client allows five hours of PTO to accrue per pay period, they might only allow three hours to accrue per pay period for the employee’s first year, if they were hired from July to December.

Note: Note the following when using the First Year Prorated Amounts panel:

In addition, a new tool tip now displays next to the Add To Balance On First Accrual field when you click the question mark (

[Image: screenshot]

). For example:

[Image: screenshot]

Note: Note the following:

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-16121, PD-16157, and PD-16158

========================================================================

Enhancement to PTO Register Enrollment Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/PTO/PTO_Register_Enrollment_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/PTO/PTO_Register_Enrollment_Form_Enhancement_QR202403.htm

Enhancement to PTO Register Enrollment Form

Previously, you could not create a new enrollment for the same register/benefit plan in the PTO Register Enrollment form.

To enhance this process, you can now create a new enrollment even if an employee has an archived record.

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-16106

========================================================================

Enhancement to ACH Journal Edit/Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/ACH_Journal_Edit_Entry_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/ACH_Journal_Edit_Entry_Form_Enhancement_QR202403.htm

Enhancement to ACH Journal Edit/Entry Form

The warning that displays when you delete an ACH journal entry record has been enhanced to clearly explain the consequences when making this type of deletion. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # PD-16514

========================================================================

Enhancement to Change Password Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/Change_Password_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/Change_Password_Form_Enhancement_QR202403.htm

Enhancement to Change Password Form

A new field, Requires New Password, now displays on the Change Password form, which is available by selecting Change User Password on the Actions menu in the Employee Details form. For example:

[Image: screenshot]

Note: The Change User Password option only displays on the Actions menu for employees who already have a username.

The read-only Requires New Password field, which is enabled by default and cannot be disabled for security purposes, prompts employees to create a new password the next time they log into the system.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-15253

========================================================================

Enhancement to Global Configuration Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/Global_Configuration_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/Global_Configuration_Form_Enhancement_QR202403.htm

Enhancement to Global Configuration Form

To prevent users from unintentionally changing the product configuration, a new warning now displays if you change the Product Version in the Global Configuration form, which is available on the System|Change menu. For example:

[Image: screenshot]

Click OK to continue. (If you did not intend to change the Product Version, you can reset it to the original version.)

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-16395

========================================================================

Audit Log Formatting

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Audit_Log_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Audit_Log_QR202403.htm

Audit Log Formatting

The Before Value and After Value fields on the File Audit form have been improved with text wrapping when the fields contain several entries.

JIRA # PP-860

========================================================================

Data Security Restrictions for Terminated Clients

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Deny_WTA_Access_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Deny_WTA_Access_QR202403.htm

Data Security Restrictions for Terminated Clients

When a client is terminated in Prism, access to that client is now removed from Data Security.

In addition, if a Worksite Trusted Advisor (WTA) only had access to the terminated client, the WTA User is deactivated. If the client is set to be terminated in the future, the WTA is set to deactivate at the same time.

Note: Note: If a client is reactivated in the system, WTAs who were deactivated as part of the same process are not automatically reactivated. After reactivating the client, the administrator must also reactivate the corresponding WTA records.

JIRA # PP-1236

========================================================================

Enhancements to Payroll Posting Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Enhancements_Payroll_Posting_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Enhancements_Payroll_Posting_QR202403.htm

Enhancements to Payroll Posting Performance

Improvements have been applied to increase the loading speed when leave requests must be updated as part of payroll processing.

JIRA # PP-1204

========================================================================

Juvod User Role Removed

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Juvod_User_Role_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Juvod_User_Role_QR202403.htm

Juvod User Role Removed

The Juvod company services are no longer available, therefore the corresponding Juvod user role has been removed from the User Role Maintenance form.

JIRA # PP-1243

========================================================================

Masking I-9 Details

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Masking_I9_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Masking_I9_QR202403.htm

Masking I-9 Details

Sensitive information about employee I-9 forms can now be masked on forms throughout the Prism application. Users with proper permissions can click the masked field to display the information as necessary.

JIRA # PP-1202

========================================================================

Enhancements to Payroll Search Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Payroll_Batch_Search_Time_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Payroll_Batch_Search_Time_QR202403.htm

Enhancements to Payroll Search Performance

Improvements have been applied to the Payroll Search forms found on multiple payroll reports and processes to improve the loading speed, especially for clients with access to a large number of records included in the payroll search results.

JIRA # PP-1249

========================================================================

Register Rebuilds Percentage Display

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Register_Rebuild_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Register_Rebuild_QR202403.htm

Register Rebuilds Percentage Display

The Register Rebuilds form has been improved to show timestamps for each percent of completion during the process. Previously, the form only showed a timestamp at every 10% of completion.

JIRA # PP-1244

========================================================================

Improved Register Rebuilds Email Message

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Register_Rebuilds_Message_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/PP_Register_Rebuilds_Message_QR202403.htm

Improved Register Rebuilds Email Message

The Email generated by the Register Rebuilds form when a rebuild is completed has been enhanced with additional information, including the year and the Client ID.

JIRA # PP-1250

========================================================================

Enhancement to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/System_Parameters_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/System_Parameters_Form_Enhancement_QR202403.htm

Enhancement to System Parameters Form

To help prevent confusion since HRPyramid has been retired, the Use HRPyramid Accounts Receivable field in the Global Accounting panel in the System Parameters form now displays as Use PrismHR Accounts Receivable. For example:

[Image: screenshot]

Note: If your organization is using PrismHR Accounts Receivable and you want it to be the primary accounts receivable, enable the Use PrismHR Accounts Receivable field. (If you select this option, the system will not track accounts receivable information in your accounting software.)

For more information, see the in-product help, PrismHR Accounting User Guide, or PrismHR System Administration Guide.

JIRA # PD-16405

========================================================================

Enhancements to User Roles Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/User_Roles_Form_Enhancements_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/User_Roles_Form_Enhancements_QR202403.htm

Enhancements to User Roles Form

The following enhancements now reside on the User Roles form, which is available on the System|Change menu:

[Image: screenshot]

You can use the CLIENT.PROCESS.NOTES*DISPLAY process ID to set user roles to Inquiry or Deny, which affects how they can work with payroll notes when accessed by clicking the Payroll Notes icon on the Time Sheet Entry form. For example, this user role is set to Inquiry, which prohibits them from using the filters, Find Payroll Notes, and New Note (these options are dimmed):

[Image: screenshot]

[Image: screenshot]

Enabling the HRPY.WORK*UPDATE.ROLE.DESC process ID displays the Role Description option on the Actions menu. For example:

[Image: screenshot]

Selecting the Role Description option displays a form where you can update the description for a user role. Simply enter or select a user from the Role ID field and the current description displays. Enter a New Description and click Save. For example:

[Image: screenshot]

Note: Updates to role descriptions are noted in the audit log.

For more information, see the in-product help, PrismHR Payroll Administration Guide, or PrismHR System Administration Guide.

JIRA # PD-10053 and PD-16497

========================================================================

Enhancement to Users Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202403/System/Users_Form_Enhancement_QR202403.htm Path: PD/Release-Notes/Enhancements/2024/QR202403/System/Users_Form_Enhancement_QR202403.htm

Enhancement to Users Form

A new option, Commission Details, now displays on the Actions menu in the Users form for service providers with the Sales Representative Account Management role. For example:

[Image: screenshot]

Selecting Commission Details opens a new form where you can record the Client ID and Employee Identifier. This information helps the system capture additional salesperson details to create an import pay file. For example:

[Image: screenshot]

Adding the Commission Details Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Commission Details from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRP.USERS*COMMISSION.DETAILS from the Search Processes list. (To quickly find this item, enter Commission Details in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-16376

========================================================================

Enhancements to Auto Holiday Pay Days Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Client/Auto_Holiday_Pay_Days_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Client/Auto_Holiday_Pay_Days_Form_Enhancements_QR202406.htm

Enhancements to Auto Holiday Pay Days Form

The following enhancements now reside on Auto Holiday Pay Days form, which you can access by selecting Days on the Auto Holiday Pay form:

[Image: screenshot]

Note: If you enter a year that is more than 10 years in the past or greater than 10 years in the future from the current year an error message displays, “Year <year> is outside of the date range that can be displayed.” Click OK to continue.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16477

========================================================================

Enhancements to Client Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Client/Client_Details_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Client/Client_Details_Form_Enhancements_QR202406.htm

Enhancements to Client Details Form

The following enhancements now reside on the Client Details form, which is available on the Client|Change menu.

New Business Entity Type Option

A new option, B-Corporation, is now available as a classification option in the Business Entity Type field on the Classifications panel. For example:

[Image: screenshot]

You can use the B-Corporation option when classifying a for-profit corporation that has been certified by B Lab, which is a non-profit company that measures a company’s social and environmental performance against the standards in the online B Impact Assessment.

New Payroll Tab Fields

Two new fields, Days Until Prenote Auto-Activate and Prenote On Next Pay Date, now reside on the Payroll tab in the Client Details form. For example:

[Image: screenshot]

You can use these fields to override the system-level parameters at the client level:

Note: Note the following:

Setting Field Security for Three Account Tab Fields

You can now set field security for the Payroll Check Account, Garnishment Check Account, and Receipts Account fields on the Account tab, so these fields that are normally required can be hidden for specific users.

To set field security for these fields:

  1. Access the User Roles form on the System|Change menu and select a Role ID.

  2. Locate the COMPANY.MASTER*MAINT.ACCOUNT process and select Field in the Security column. The Field Security Maintenance form displays.

  3. Click Add. The Field Security Selection form displays.

  4. Select the CHECK.ACCT, CHECK.ACCT.GARN, and INV.RECPT.ACCT fields checkboxes in the list and click Accept. The Field Security Maintenance form redisplays.

  5. Change the permissions for the fields to Hidden and the Required field to N. For example:

[Image: screenshot]

Note: Updating the permissions to Hidden and the Required field to N displays a message, “Warning: This is a required field. Hiding could prevent user from saving form.” Click OK to continue.

  1. Click Save. The User Roles form redisplays.

  2. Click Save.

New Time Sheet Tab Tool Tip

To help users understand how data is stored for projects with phases, a new tool tip now displays in the Detail Time Entry Parameters panel on the Time Sheet tab. For example:

[Image: screenshot]

This tool tip summarizes that the Detail Time Entry form in Employee Portal (EP) does not include the Project with phase field due to how the system stores data for phases, where the same phase code can be used with different projects or no project. Therefore, a “project with phase” is only available in the PrismHR core product.

New Contractors 1099 DOB Required Field

A new field, Contractors 1099 DOB Required, now resides on the Other tab. For example:

[Image: screenshot]

You can enable the Contractors 1099 DOB Required field to override an enabled Do not require DOB field (located on the System Parameters form). This is helpful if you require 1099 contractors to perform the onboarding process using Employee Portal (EP), which requires an employee’s date of birth.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-14912, PD-17023, WSP-49, WSP-281, and WSP-303

========================================================================

Enhancement to Divisions Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Client/Divisions_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Client/Divisions_Form_Enhancement_QR202406.htm

Enhancement to Divisions Form

A new panel, Misc GL, now resides on the Divisions form, which is available on the Client|Change menu. For example:

[Image: screenshot]

You can use the Misc GL panel to replace predefined wildcards with miscellaneous GL segments for divisions using the following columns:

Important! Any changes made to the descriptions affect all divisions in the active client.

Note: During payroll processing, the system substitutes the GL segments for wildcards in GL account codes. These wildcards must also be included in the following setups:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-42

========================================================================

Name Changes for Find Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Client/Name_Changes_for_Find_Forms_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Client/Name_Changes_for_Find_Forms_QR202406.htm

Name Changes for Find Forms

To improve naming consistency in PrismHR forms, the following “find” forms have name changes:

[Image: screenshot]

[Image: screenshot]

For more information, see the in-product help, PrismHRClient Administration Guide, or PrismHRPayroll Reports guide.

JIRA # PD-16543

========================================================================

Enhancements to Print Service Options Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Client/Print_Service_Options_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Client/Print_Service_Options_Form_Enhancements_QR202406.htm

Enhancements to Print Service Options Form

The following enhancements now reside on the Print Service Options form, which you can access from the Actions menu on the Client Details form:

[Image: screenshot]

Note: You can access the Print Service Options form by selecting Print Service Options on the Actions menu in the Client Details form.

Note: Note the following about this enhancement:

Now when users set the Client Print Service Option parameters (or Global parameters) for the project with its prevailing wage on the Pay Detail panel, if the prevailing wage for the project is greater than the prevailing wage for the position, the check stub displays the prevailing wage from the project.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16577 and PD-17273

========================================================================

Enhancement to Projects Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Client/Projects_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Client/Projects_Form_Enhancement_QR202406.htm

Enhancement to Projects Form

Three new fields, Misc GL Count, Misc GL Description, and Misc GL Segment, now reside on the Projects form, which is available on the Client|Change menu. For example:

[Image: screenshot]

You can use these fields to replace predefined wildcards with miscellaneous GL segments for projects in payroll accounting and PEO client accounting using the following columns:

Important! Any changes made to the descriptions affect all projects in the active client.

Note: During payroll processing, the system substitutes the GL segments for wildcards in GL account codes. These wildcards must also be included in the following setups:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-110

========================================================================

Enhancement to Worksite Locations Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Client/Worksite_Locations_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Client/Worksite_Locations_Form_Enhancement_QR202406.htm

Enhancement to Worksite Locations Form

A new panel, Misc GL, now resides on the Worksite Locations form, which is available on the Client|Change menu. For example:

[Image: screenshot]

You can use the Misc GL panel to replace predefined wildcards with miscellaneous GL segments for worksite locations using the following columns:

Important! Any changes made to the descriptions affect all worksite locations in the active client.

Note: This column’s values are for reference only. (These descriptions are stored in the client’s record.) The system automatically loads these values each time a worksite location record displays.

Note: During payroll processing, the system substitutes the GL segments for wildcards in GL account codes. These wildcards must also be included in the following setups:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-44 and WSP-326

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Documentation/New_Task_Sheets_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Documentation/New_Task_Sheets_QR202406.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheets were updated:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Retirement Exports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Employer%20Administration/Retirement_Exports_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Employer Administration/Retirement_Exports_Form_Enhancement_QR202406.htm

Enhancement to Retirement Exports Form

The headers that display in the downloaded Pinnacle template in .xls format, which you can run using the Retirement Exports form, have been improved, so they now display meaningful headers instead of generic code headers. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHREmployer Administration Guide.

JIRA # PD-16056

========================================================================

Enhancement to Transfer Employee to New Client Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Employer%20Administration/Transfer_EEtoNewClient_Enh_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Employer Administration/Transfer_EEtoNewClient_Enh_QR202406.htm

Enhancement to Transfer Employee to New Client Form

Selecting the To Location field in the Transfer Employee to New Client form now provides search capability. For example:

[Image: screenshot]

To find a particular location amongst a large list of client locations, simply enter the location code, location name, state, or city in the search box.

Note: Worksite managers do not have access to the Transfer Employee to New Client form.

For more information, see the in-product help or PrismHREmployer Administration Guide.

JIRA # PD-17095

========================================================================

Enhancements to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Details_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Details_Form_Enhancements_QR202406.htm

Enhancements to Employee Details Form

The following enhancements now reside on the Employee Details form, which is available on the HR|Change menu.

Using a Worksite Trusted Advisor’s User ID as PTO Approver or Manager

Service providers can now enter a worksite trusted advisor’s user ID (who has access to the client) as the PTO Approver or Manager for the selected employee on the Work tab. (Previously, you could only enter an employee ID in these fields.)

Note: Note the following:

Using New Deduction Options

Selecting the new Deduction 1, Deduction 2, or Deduction 3 option in the Type field on the Deposit tab automatically populates the Method field as Fixed and the Amount field as 0.00. For example:

[Image: screenshot]

Service providers, worksite managers, and worksite trusted advisors can select one of these options to associate the deduction code with the direct deposit information.

Note: Note the following when using the Deduction 1, Deduction 2, or Deduction 3 option type:

Setting Field Security for Employee SSN and Benefits Thru Date Fields

You can now set field security for the Employee SSN field on the Personal tab and the Benefits Thru Date field on the Work tab, so these fields that are normally required can be hidden for specific users.

To set field security for these fields:

  1. Access the User Roles form on the System|Change menu and select a Role ID.

  2. Locate the EMPLOYEE.PER*MAINT.PERSONAL process and select Field in the Security column. The Field Security Maintenance form displays.

  3. Click Add. The Field Security Selection form displays.

  4. Select the EMPLOYEE.SSN and UNMASKED.SSN fields checkboxes in the list and click Accept. The Field Security Maintenance form redisplays.

  5. Change the permissions for both fields to Hidden and the Required field to N. For example:

[Image: screenshot]

  1. Click Save. The User Roles form redisplays.

  2. Locate the EMPLOYEE.PER*MAINT.WORK process and select Field in the Security column. The Field Security Maintenance form displays.

  3. Click Add. The Field Security Selection form displays.

  4. Select the PAID.THRU field checkbox in the list and click Accept. The Field Security Maintenance form redisplays.

  5. Change the permissions for the field to Hidden and the Required field to N. For example:

[Image: screenshot]

  1. Click Save. The User Roles form redisplays.

  2. Click Save.

A new Tax Calculation Override link now displays in the Federal Tax Filing panel on the Tax tab when an employee has a tax override, such as an active tax override, a one-time record, or a miscellaneous tax override. (This enhancement applies to all tax overrides.) For example:

[Image: screenshot]

When you select the Tax Calculation Override link, the Tax Calculation Overrides form opens, displaying the employee’s income tax overrides.

Note: The Tax Calculation Override link displays for service providers, worksite managers, and worksite trusted advisors who have Full access to both the Employee Details form and the Tax Calculation Overrides form. (This link also displays for users who have Inquiry access to these forms, but does not display if their access is set to Deny.)

Working with Termination Explanation After Employee Termination

You can now add, update, or delete a Termination Explanation on the Other tab after an employee has been terminated.

Note: This enhancement is only available for service providers.

Before adding, editing, or deleting a Termination Explanation for a terminated employee, you must first enable the new EDITTERM custom feature code in the System Parameters form. For example:

[Image: screenshot]

Required School District Error Message Updated on Tax Tab

The error message that displays when you save information on the Tax tab without entering a School District when this field is required has been updated. The error message now displays as follows:

[Image: screenshot]

New Worksite Manager Proxy Option on Actions Menu

You can now directly login as a worksite manager/worksite trusted advisor by selecting the new Worksite Manager Proxy option on the Actions menu. For example:

[Image: screenshot]

Selecting Worksite Manager Proxy opens the Proxy Login form, where the Worksite Manager/Trusted Advisor option displays in the Activity field and the selected employee’s username displays in the User ID field. For example:

[Image: screenshot]

For more information, see the in-product help, PrismHR Client Administration Guide, PrismHRHuman Resources User Guide, PrismHR Onboarding User Guide, or PrismHR System Administration Guide.

JIRA # PD-15590, PD-16369, PD-16707, PD-16772, PD-16774, PD-16853, WSP-277, WSP-293, and WSP-294, WSP-420

========================================================================

Enhancements to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Fields_Import_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Fields_Import_Form_Enhancements_QR202406.htm

Enhancements to Employee Fields Import Form

The following enhancements now reside on the Employee Fields Import form, which is available on the Operations|Action menu:

Note: Note the following:

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-12848, PD-16782, and WSP-66

========================================================================

Enhancement to Employee Organizational Structure Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Organizational_Structure_Report_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Organizational_Structure_Report_Enhancement_QR202406.htm

Enhancement to Employee Organizational Structure Report

In association with the enhancement that allows service providers to enter a worksite trusted advisor’s user ID (who has access to the client) as the PTO Approver or Manager for the selected employee on the Work tab in the Employee Details form, those individuals who are designated as a “manager” or “PTO approver” now display in the Employee Organizational Structure Report in the PTO Approver Name and PTO Approver Position columns or the Manager Name column, where their position is “Worksite Trusted Advisor.” For example:

[Image: screenshot]

Note: Since worksite trusted advisors do not have a position code, their job title displays as “Worksite Trusted Advisor,” and their name displays as listed in their Users record.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17046

========================================================================

Enhancements to Employee Termination Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Termination_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Employee_Termination_Form_Enhancements_QR202406.htm

Enhancements to Employee Termination Form

The following enhancements now reside on the Employee Termination form, which is available on the HR|Action menu:

[Image: screenshot]

Note: This read-only field displays the employee’s position after you enter or select an Employee.

[Image: screenshot]

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17001 and PD-17058

========================================================================

Enhancement to Future Dated Changes Reflected in Audit Logs

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Future_Changes_Reflected_in_Audit_Logs_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Future_Changes_Reflected_in_Audit_Logs_Enhancement_QR202406.htm

Enhancement to Future Dated Changes Reflected in Audit Logs

To ensure the system now displays the correct user ID of those individuals who make future dated changes in audit logs, all utility programs now assign that user ID for changes made in the following forms:

JIRA # PD-16855

========================================================================

Enhancement to Global Search Results

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Global_Search_Results_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Global_Search_Results_Enhancement_QR202406.htm

Enhancement to Global Search Results

Previously, when performing a global search for an employee the system displayed the preferred name instead of the legal first name.

The system now displays an employee’s legal first name in parentheses if there is a preferred name for the employee, which displays first. After the legal first name the middle initial displays, then the last name. For example:

[Image: screenshot]

In this example, the employee’s preferred name (Ty), legal first name (Ted), middle initial (A.), and last name (Mullens) displays.

For more information about this enhancement, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16835

========================================================================

Enhancement to Leave Request Approval Process

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Leave_Request_Approval_Process_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Leave_Request_Approval_Process_Enhancement_QR202406.htm

Enhancement to Leave Request Approval Process

Previously, only employee IDs could be entered when approving leave requests. Now, service providers can enter a worksite trusted advisor’s user ID in the PTO Approver and Manager fields as part of the leave request approval process.

Note: You must enter user IDs in lowercase.

For more information about this enhancement, see Enhancements to Employee Details Form and Enhancement to New Hire Form.

JIRA # PD-16713

========================================================================

Enhancement to New Hire Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/New_Hire_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/New_Hire_Form_Enhancement_QR202406.htm

Enhancement to New Hire Form

Service providers can now enter a worksite trusted advisor’s user ID (who has access to the client) as the PTO Approver or Manager for the selected employee on the New Hire form, which is available on the HR|Action menu. (Previously, you could only enter an employee ID in these fields.)

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16708

========================================================================

Enhancement to Organization Chart Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Organization_Chart_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Organization_Chart_Form_Enhancement_QR202406.htm

Enhancement to Organization Chart Form

In association with the enhancement that allows service providers to enter a worksite trusted advisor’s user ID (who has access to the client) as the PTO Approver or Manager for the selected employee on the Work tab in the Employee Details form, those individuals who are designated as a “manager” now display on the Organization Chart form at the top of the chart. (Worksite trusted advisors always display at the top of the chart because they are not assigned a manager.) For example:

[Image: screenshot]

Note: Since worksite trusted advisors do not have a position code, their job title displays as “Worksite Trusted Advisor,” and their name displays as listed in their Users record.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16849

========================================================================

Enhancement to Positions Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Positions_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Positions_Form_Enhancement_QR202406.htm

Enhancement to Positions Form

A new panel, Misc GL, now resides on the Positions form, which is available on the Client|Change menu. For example:

[Image: screenshot]

You can use the Misc GL panel to replace predefined wildcards with miscellaneous GL segments for positions using the following columns:

Important! Any changes made to the descriptions affect all positions in the active client.

Note: When the system evaluates the Misc GL Segments, they are always based on the “home” job, which is different from the way segments are evaluated for departments (that is, for account codes for payment, the system uses the timesheet “worked-for” department).

Note: During payroll processing, the system substitutes the GL segments for wildcards in GL account codes. These wildcards must also be included in the following setups:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # WSP-109

========================================================================

Enhancement to PTO Approver Reassignment Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/PTO_Approver_Reassignment_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/PTO_Approver_Reassignment_Form_Enhancement_QR202406.htm

Enhancement to PTO Approver Reassignment Form

Service providers can now enter a worksite trusted advisor’s user ID (who has access to the client) as the PTO Approver for the selected employee in the Reassign To field on the PTO Approver Reassignment form, which is available on the HR|Action menu. (Previously, you could only enter an employee ID in this field.)

In addition, when you select the PTO Approver field the two columns in the Select Employee list now display as Current PTO Approver ID and Current PTO Approver. For example:

[Image: screenshot]

Note: You can select current worksite trusted advisors assigned as a PTO Approver from the Select Employee list.

Note: Note the following about this enhancement:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16710

========================================================================

Enhancements to Rehire Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Rehire_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/HumanResources/Rehire_Form_Enhancements_QR202406.htm

Enhancements to Rehire Form

The following enhancements now reside on the Rehire form, which is available on the HR|Action menu:

Note: Note the following:

[Image: screenshot]

[Image: screenshot]

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16709, PD-17059, and PD-17060

========================================================================

Enhancement to New Employee Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/New-Employee-Import/New_Employee_Import_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/New-Employee-Import/New_Employee_Import_Form_Enhancement_QR202406.htm

Enhancement to New Employee Import Form

Service providers can now import a PTO Approver and Manager as a worksite trusted advisor (who has access to the client), using user IDs, on the New Employee Import form. (Previously, you could only use employee IDs.)

Note: Note the following:

For more information, see the in-product help or PrismHRNew Employee Import Guide.

JIRA # PD-16714

========================================================================

Enhancement to Bill Pending Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Bill_Pending_Details_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Bill_Pending_Details_Form_Enhancement_QR202406.htm

Enhancement to Bill Pending Details Form

You can now place a bill-pending item on hold (taking it out of “in-progress” status and returning it to “time-entry” status) by editing its Bill Date, Event, and Bill Rate in the Bill Pending Details form.

Important! This process is not available for restartable payrolls.

To edit a bill-pending item to place it on hold:

  1. Reset the Payroll Calculation: Complete status to Payroll Calculation: Ready on the calculated payroll by finalizing the timesheets again in the Process Payroll form. (This step deletes any initialized vouchers, so the payroll is no longer initialized.)

  2. Select the bill-pending item on the Bill Pending form. The Bill Pending Details form displays.

  3. Update the Bill Date and other pertinent information, which places the bill-pending item on hold.

  4. Click Save. After initializing the payroll again, the edited bill-pending item no longer displays in the initialized invoice.

Note: Note the following:

For more information, see the in-product help or PrismHR Payroll Processing Guide.

JIRA # WSP-245

========================================================================

Enhancements to Check History Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Check_History_Import_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Check_History_Import_Form_Enhancement_QR202406.htm

Enhancements to Check History Import Form

The following enhancements now reside on the Check History Import form, which is available on the Operations|Import Processing menu:

[Image: screenshot]

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-14146 and WSP-188

========================================================================

Enhancements to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Data_Import_Tool_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Data_Import_Tool_Enhancements_QR202406.htm

Enhancements to Data Import Tool

The following enhancements now reside in the Data Import Tool, which is available on the Operations|Import Processing menu:

[Image: screenshot]

Note: The Employer W/C Accrual Modifiers import template is only available for service providers.

To import this data, select Employer W/C Accrual Modifiers from the Import Template menu, and then click Find File to upload the file.

Note: Note the following:

[Image: screenshot]

You can use these fields as follows:

[Image: screenshot]

You can use the Client Details (Benefits) import template to import NAICS codes for the client to reduce the amount of manual work required.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-16762, PD-16942, PD-16943, and PD-17110

========================================================================

Enhancements to Employee Deduction Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Deduction_Details_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Deduction_Details_Form_Enhancements_QR202406.htm

Enhancements to Employee Deduction Details Form

The following enhancements now reside on the Employee Deduction Details form.

Note: You can access this form by selecting the Edit Detail icon (

[Image: screenshot]

) for an employee in the Recurring Deductions form.

[Image: screenshot]

You can use the ACH Options field to associate a deduction with a direct deposit account.

Note: Note the following:

Processing Deductions for ACH Account

When you select a deduction option in the ACH Options field and run a payroll the deduction process works as it always has, where the system recognizes the deduction code setup. However, instead of just recognizing the deduction, the system now routes the deduction amount to a direct deposit account.

After running the payroll process, the deduction amount displays on the Employee Voucher Deductions form in the voucher on the Deductions tab, where the status is DD1, DD2, or D*D3 on the Banking tab, according to the option selected on the Employee Deduction Details form. For example:

[Image: screenshot]

Note: The deduction’s taxation is determined by the deduction code details set on the Deduction Codes form. For example:

[Image: screenshot]

To view changes made to this form, select the Audit option on the Actions menu. The Audit Log Display form opens. For example:

[Image: screenshot]

Note: You must add access to the Employee Deduction Details form in your user role to access the Audit option on the Actions menu in this form.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-16732, PD-16733, PD-16771, and PD-17022

========================================================================

Enhancement to Employee Direct Deposit Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Direct_Deposit_Report_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Direct_Deposit_Report_Form_Enhancement_QR202406.htm

Enhancement to Employee Direct Deposit Report Form

The deduction to ACH information for the new Deduction 1, Deduction 2, or Deduction 3 options displays in the Employee Direct Deposit Report when run using the Employee Direct Deposit Report form.

Note: For information about the new deduction options, see Enhancements to Employee Details Form.

Note: Note the following about this enhancement:

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-16735

========================================================================

Enhancement to Employee Loans Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Loans_Report_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Loans_Report_Form_Enhancement_QR202406.htm

Enhancement to Employee Loans Report Form

A new panel, Selection Criteria, now displays on the Employee Loans Report form, which is available on the Payroll|Report menu. For example:

[Image: screenshot]

You can use the options in the Selection Criteria panel to only display specific Employee IDs and display loans with a Balance Greater than Zero in the report output.

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-13904

========================================================================

Enhancement to Employee Payroll Voucher Reversal Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Payroll_Voucher_Reversal_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Employee_Payroll_Voucher_Reversal_Form_Enhancement_QR202406.htm

Enhancement to Employee Payroll Voucher Reversal Form

The system traditionally treats reversals (voids) done in the Employee Payroll Voucher Reversal form as if they are a regular checking or savings account.

To accommodate the new ACH deduction codes, Deduction 1, Deduction 2, and Deduction 3, the system processes them as it does for all other ACH types. Selecting Yes to the prompt that displays during ACH reversals ensures that the bank file includes a debit to the account, which takes the funds from the employee’s account. (Selecting No displays the ACH amount as the usual credit in the bank file.)

Note: See Enhancements to Employee Details Form for more information about the new ACH deduction codes.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-16773

========================================================================

Enhancement to Invoice Sales Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Invoice_Sales_Report_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Invoice_Sales_Report_Enhancement_QR202406.htm

Enhancement to Invoice Sales Report

Two new columns, Period Start Date and Period End Date, now display in the output after running the Invoice Sales Report, whose form is available on the Payroll|Report menu. For example:

[Image: screenshot]

In addition, the Date column header now displays as Invoice Date.

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-16987

========================================================================

Enhancement to Payees Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payees_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payees_Form_Enhancement_QR202406.htm

Enhancement to Payees Form

Previously, users could only enter numeric characters (0-9) and the dash (-) character in the Bank Account Number field for the Garnishing Authority payee type in the EFT Parameters panel and the State Disbursement Unit payee type in the State Disbursement Unit Parameters panel on the Payees form. (The system displayed an error message when users entered an alphabetic character in the Bank Account Number field.)

To accommodate users who need to use alphabetic characters in their account numbers, the system now allows these characters in addition to numeric characters and a dash, which can be combined. For example, CSP-87654 is now an allowed bank account number.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17232

========================================================================

Enhancement to Payroll Reversal Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Reversal_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Reversal_Form_Enhancement_QR202406.htm

Enhancement to Payroll Reversal Form

The system traditionally treats reversals (voids) done in the Payroll Reversal form as if they are a regular checking or savings account.

To accommodate the new ACH deduction codes, Deduction 1, Deduction 2, and Deduction 3, the system processes them as it does for all other ACH types. (See Enhancements to Employee Details Form for more information about the new ACH deduction codes.)

During the payroll reversal process, the system now automatically reverses all ACH postings.

Note: This process does not reverse HSA ACH transactions.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-17090

========================================================================

Enhancements to Payroll Schedules Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Schedules_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Schedules_Form_Enhancements_QR202406.htm

Enhancements to Payroll Schedules Form

To ensure names are consistent across the PrismHR platform, “Payroll Schedules” now displays as “Pay Schedules” in the following instances:

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-13206

========================================================================

Enhancements to Payroll Validation Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Validation_Report_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Validation_Report_Form_Enhancements_QR202406.htm

Enhancements to Payroll Validation Report

The Payroll Validation Report, which is accessible on the Payroll|Reports menu, has been enhanced as follows:

In addition, when you run the Payroll Validation Report the first time, the system now captures more errors for SUTA and workers’ compensation. (Previously, you had to run the report multiple times after fixing individual issues.) For example, the system now captures the following issues:

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # WSP-305 and WSP-327

========================================================================

Enhancement to Payroll Voucher Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Voucher_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Payroll_Voucher_Form_Enhancement_QR202406.htm

Enhancement to Payroll Voucher Form

To improve consistency, the Absence Description column that displayed on the PTO tab in the Payroll Voucher form now displays as “Leave Reason.” For example:

[Image: screenshot]

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-15302

========================================================================

Enhancements to Process Payroll Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Process_Payroll_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Process_Payroll_Form_Enhancements_QR202406.htm

Enhancements to Process Payroll Form

The following enhancements now reside on the Process Payroll form, which is available on the Payroll|Action menu:

The following message now displays, “You cannot make any changes once you submit payroll for processing. Are you sure you want to submit?”

To help users understand this situation in a timelier fashion, the program that calculates workers’ compensation premiums now displays both errors on the first pass.

For more information about the Process Payroll form, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-15760, WSP-187, and WSP-311

========================================================================

Enhancements to SuperBatch Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/SuperBatch_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/SuperBatch_Form_Enhancements_QR202406.htm

Enhancements to SuperBatch Form

The following enhancements now reside on the SuperBatch form, which is available on the Operations|Action menu:

[Image: screenshot]

Note: Note the following when using the Cost Center filter option:

Note: For more information, see Enhancements to System Parameters Form.

[Image: screenshot]

Note: The payroll must be in the Payroll is ready for review state (

[Image: screenshot]

) for this report option to display.

Clicking Unpaid Employees Report opens the report parameters form, where you can display payroll information for employees who received no earnings in a specific payroll or during a payroll period.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-16721, PD-17006, PD-17107, PD-17111, and PD-17125

========================================================================

Enhancement to Payroll Register Report and Parameters Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Suppress_NonCash_Fringe_PayCodes_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Suppress_NonCash_Fringe_PayCodes_QR202406.htm

Enhancement to Payroll Register Report and Parameters Forms

You can now exclude non-cash fringe pay codes from the Compact version of the Payroll Register Report and the Payroll Register Report Parameters forms, which helps differentiate between pay and non-cash fringe pay codes.

To exclude these pay codes, enable the Suppress Non-Cash Fringe Pay Codes field in the Compact Format Parameters panel on the Payroll Register Report and the Payroll Register Report Parameters forms. For example:

[Image: screenshot]

[Image: screenshot]

Note: The Payroll Register Report and the Payroll Register Report Parameters forms run the same report.

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-16913 and PD-16924

========================================================================

Enhancement to Tax Calculation Overrides Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Tax_Calculation_Overrides_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Tax_Calculation_Overrides_Form_Enhancement_QR202406.htm

Enhancement to Tax Calculation Overrides Form

Two new fields, Status and Voucher, now reside on the Tax Calculation Overrides form, which you can access on the Payroll|Action menu. For example:

[Image: screenshot]

You can use the Status field to control how the system handles overrides during payroll processing using one of the following options:

Note: After a payroll processes with the Status set to Onetime, the override status changes to Inactive and the voucher number displays in the Voucher field. (You cannot edit or reactivate a onetime override after it is used. However, you can enter a new override for the same tax authority.)

For more information, see the in-product help or PrismHRPayroll Overrides Guide.

JIRA # WSP-184

========================================================================

Enhancement to Unbundled Billing Additional Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Unbundled_Billing_Additional_Details_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Unbundled_Billing_Additional_Details_Form_Enhancement_QR202406.htm

Enhancement to Unbundled Billing Additional Details Form

You can now use the Flat Amount / Invoice option in the Based On field on the Billing Rules (Unbundled) form to suppress the billing (delivery fee) for a manual check that occurs when a billing rule is processing live checks by enabling the Exclude From Manual Check field on the Unbundled Billing Additional Details form. (Previously, the Exclude From Manual Check field only displayed when the Amt per Check (One Per Voucher will Fire), Flat Amount, or Flat Amount / Paid EE (only once per EE) option was enabled.) For example:

[Image: screenshot]

Note: Note the following:

To suppress the billing (delivery fee) for a manual check:

  1. Select one of the following rules in the Based On field in the Billing Rules (Unbundled) form:

  1. Select Use If Any Check in the Unbundled Billing Additional Details form.

  2. Select Exclude From Manual Check to prevent the system from processing billing on a manual check.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-16941

========================================================================

Enhancement to Unpaid Employees Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Unpaid_Employees_Report_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/Payroll/Unpaid_Employees_Report_Form_Enhancement_QR202406.htm

Enhancement to Unpaid Employees Report Form

The Type Class field on the Unpaid Employees Report form now displays as Employee Type. For example:

[Image: screenshot]

Options for the Employee Type field now include all employee types, not just employee classes, including All Full-Time and All Part-Time.

Note: The system displays settings from the Client Controls form as options in the Employee Type field. If there are no settings in the Client Controls form, then all employee types display.

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # PD-16989

========================================================================

Enhancement to Employee PTO Register Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/PTO/Employee_PTO_Register_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/PTO/Employee_PTO_Register_Form_Enhancement_QR202406.htm

Enhancement to Employee PTO Register Form

To improve consistency, the Reason column that displayed in the Paid Hours Absent Detail panel on the Employee PTO Register form now displays as “Leave Reason.” For example:

[Image: screenshot]

For more information, see the in-product help or PrismHR Paid Time Off User Guide.

JIRA # PD-15302

========================================================================

Enhancement to Leave of Absence Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/PTO/Leave_of_Absence_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/PTO/Leave_of_Absence_Form_Enhancement_QR202406.htm

Enhancement to Leave of Absence Form

To help you select the correct Leave Employment Status on the Leave of Absence form when there is a status code that shares the same abbreviated description, all status codes in this field now display their full description, separated by a dash (-) in front of the status code. For example:

[Image: screenshot]

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-17055

========================================================================

Enhancement to PTO Auto Enroll Rules Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/PTO/PTO_Auto_Enroll_Rules_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/PTO/PTO_Auto_Enroll_Rules_Form_Enhancement_QR202406.htm

Enhancement to PTO Auto Enroll Rules Form

A new column, Work Group, now displays on the PTO Auto Enroll Rules form, where you can auto-enroll employees in specific PTO plans/registers based on their assigned work group. For example:

[Image: screenshot]

In addition, you can sort the form by Work Group in the Sort By field.

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-13425

========================================================================

Enhancement to PTO Auto-Enrollment Rules Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/PTO/PTO_Auto_Enrollment_Rules_Maintenance_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/PTO/PTO_Auto_Enrollment_Rules_Maintenance_Form_Enhancement_QR202406.htm

Enhancement to PTO Auto-Enrollment Rules Maintenance Form

A new field, Work Group, now displays on the PTO Auto-Enrollment Rule Maintenance form, so you can auto-enroll employees in specific PTO plans/registers based on their work group. For example:

[Image: screenshot]

Note: You can access this form by clicking New Rule on the PTO Auto Enroll Rules form.

To create a new rule that includes a work group, enter or select the Employee Type, Work Group, PTO Register Type, and PTO Benefit Plan and click Save. The new rule displays in the PTO Auto Enroll Rules form.

Note: After running the PTO Auto Register Enrollment process, only employees who meet the criteria in the auto-enroll rule are auto-enrolled in the identified PTO Register Type and PTO Benefit Plan.

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-16465 and PD-16498

========================================================================

Enhancement to PTO Benefit Plans Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/PTO/PTO_Benefit_Plans_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/PTO/PTO_Benefit_Plans_Form_Enhancement_QR202406.htm

Enhancement to PTO Benefit Plans Form

A new field, Max Per Year, now resides in the First Year Prorated Amounts panel on the PTO Benefit Plans form. For example:

[Image: screenshot]

Enter the employee’s Max Per Year PTO hours for their first year of employment, so that employee no longer accrues PTO once they reach their maximum PTO hours. For example, this enhancement is helpful when you hire employees from January to March who will receive 24 hours of PTO, but employees hired in April would only receive 12 hours of PTO. Therefore, those employees hired in April will accrue 12 hours of PTO on their first payroll and then stop at 12 hours and will not receive the full 24 hours of PTO that the earlier-hired employees will receive.

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-17246 and PD-17266

========================================================================

Enhancements to Reactivation Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/PTO/Reactivation_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/PTO/Reactivation_Form_Enhancements_QR202406.htm

Enhancements to Reactivation Form

The following enhancements now reside on the Reactivation form, which is available on the HR|Action menu:

[Image: screenshot]

[Image: screenshot]

For more information, see the in-product help or PrismHRPaid Time Off User Guide.

JIRA # PD-17056 and PD-17061

========================================================================

Enhancement to ACH Hold Management Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/ACH_Hold_Management_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/ACH_Hold_Management_Form_Enhancement_QR202406.htm

Enhancement to ACH Hold Management Form

A new button, Find Journals, now displays on the ACH Hold Management form, which is available on the Operations|Action menu. For example:

[Image: screenshot]

Previously, the system automatically loaded the entire list of holds when accessing the ACH Hold Management form, which could cause a delay. Now you can select the filter settings and then select Find Journals to display all holds that only pertain to the selected criteria, which provides faster processing. (To display all holds, do not select any parameters before selecting Find Journals.)

Note: This form no longer displays the Refresh button.

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # PD-17149 and PD-17225

========================================================================

Enhancement to ACH Hold Management (Internal Payroll) Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/ACH_Hold_Management_Internal_Payroll_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/ACH_Hold_Management_Internal_Payroll_Form_Enhancement_QR202406.htm

Enhancement to ACH Hold Management (Internal Payroll) Form

A new button, Find Journals, now displays on the ACH Hold Management (Internal Payroll) form, which is available on the Operations|Action menu. For example:

[Image: screenshot]

Previously, the system automatically loaded the entire list of holds when accessing the ACH Hold Management (Internal Payroll) form, which could cause a delay. Now you can select the filter settings and then select Find Journals to display all holds that only pertain to the selected criteria, which provides faster processing. (To display all holds, do not select any parameters before selecting Find Journals.)

Note: This form no longer displays the Refresh button.

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # PD-17149 and PD-17225

========================================================================

Enhancements to ACH Journal Edit/Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/ACH_Journal_Edit_Entry_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/ACH_Journal_Edit_Entry_Form_Enhancements_QR202406.htm

Enhancements to ACH Journal Edit/Entry Form

The following enhancements now reside on the ACH Journal Edit/Entry form, which is available on the Operations|Action menu:

[Image: screenshot]

After entering or selecting the Company and Journal, select Audit Logs to view the Audit Log Display, which lists any changes made to a form. (Click Log ID to view the details.)

[Image: screenshot]

Selecting Field in the Security column opens the Field Security Maintenance form, where you can click Add to set security permissions for fields in the ACH Journal Edit/Entry form.

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # WSP-186 and WSP-250

========================================================================

Enhancement to Cost Centers Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/Cost_Centers_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/Cost_Centers_Form_Enhancement_QR202406.htm

Enhancement to Cost Centers Form

You can now review an audit log for a cost center by selecting the Audit option on the Actions menu in the Cost Centers form.

To view changes made to a cost center, enter or select the Cost Center ID on the Cost Centers form, then select the Audit option. The Audit Log Display form opens. For example:

[Image: screenshot]

Note: The system only displays audits from this release forward (no past transactions can be reviewed from the Cost Centers form).

JIRA # WSP-23

========================================================================

Enhancement to G/L Setup Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/GL_Setup_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/GL_Setup_Form_Enhancement_QR202406.htm

Enhancement to G/L Setup Form

Previously, an issue sometimes occurred where the system was prevented from populating wildcards in account numbers for external invoices. (You can set up wildcards on the “GL” template using the “AR” Miscellaneous Item in the G/L Setup - Miscellaneous Accounts panel.)

The system now populates the Employer Cost Center (EMCC) and Employer Sub-Cost Center (EMSCC) wildcard options on the G/L setup for the “AR” Miscellaneous Item.

For more information, see the in-product help or PrismHRAccounting User Guide.

JIRA # WSP-317

========================================================================

Enhancement to Message Templates Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/Message_Templates_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/Message_Templates_Form_Enhancement_QR202406.htm

Enhancement to Message Templates Form

To help track payroll completions, two new message templates, PAYROLL_APPROVED and PAYROLL_DENIED, are now available on the Message Templates form. For example:

[Image: screenshot]

[Image: screenshot]

You can use these new message templates to send a notification to internal service provider users, noted as the Payroll representative listed on the Account tab in the Client Details form (or listed in Backup Assignments), after payroll has either been approved or denied.

Note: The message templates can include the following substitution variables:

In addition, you must also select the PAYROLL_APPROVED and PAYROLL_DENIED template types in the Email Services form to complete the notification setup. For example:

[Image: screenshot]

Note: To access the Email Services form, select Email Services on the Actions menu in the System Parameters form.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-36

========================================================================

Modern Button Style

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/Modernized_Buttons_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/Modernized_Buttons_Enhancement_QR202406.htm

Modern Button Style

To improve consistency, the buttons on many forms throughout PrismHR now display a modern button style, which improves visibility. For example, the primary and secondary buttons in the Time Sheet Entry form now display using this modern style:

[Image: screenshot]

In addition, hovering over a button that displays in a highlighted color indicates that the button is clickable and will perform an action.

JIRA # PD-17004, PD-17017, PD-17030, and PD-17104

========================================================================

Enhancement to New Hire and Dependent Required Fields and Dependent Field Overrides Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/NewHire_Dep_Req_Fields_Global_Overrides_Forms_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/NewHire_Dep_Req_Fields_Global_Overrides_Forms_QR202406.htm

Enhancement to New Hire and Dependent Required Fields and Dependent Field Overrides Forms

A new field, Union Code, now resides on the New Hire and Dependent Required Fields (Global) and New Hire and Dependent Field Overrides forms, which you can access on the System|Change and Client|Action menus, respectively. For example:

[Image: screenshot]

[Image: screenshot]

You can use these forms to indicate that the Union Code field is a required field on the New Hire form for a standard or onboarded new hire.

For more information about the New Hire and Dependent Required Fields (Global) and New Hire and Dependent Field Overrides forms, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-16407

========================================================================

Enhancement to Notification Control Panel Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/Notification_Control_Panel_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/Notification_Control_Panel_Form_Enhancement_QR202406.htm

Enhancement to Notification Control Panel Form

A new panel, ACH Processing, now resides on the Notification Control Panel form. For example:

[Image: screenshot]

You can use the ACH Processing panel to schedule this time-based process and produce the ACH files.

Note: You must use the options in the ACH Processing panel in conjunction with multiple ACH processing.

To specify the daily start time for ACH processing, simply enter the User ID and the start time in the Daily ACH Start Time field (this field defaults to 05:00:00). Valid entries for this field must be entered in military time. For example, to start ACH processing at 1:00AM, enter 01:00:00.

To the right of the Daily ACH Start Time field a display-only process status displays, which matches the same control number that displays in the BE Notify panel.

In addition, the display-only Last Run Date/Time field displays the last date and time the process ran.

Note: Note the following:

For more information about this enhancement, see the in-product help and the PrismHR ACH User Guide.

JIRA # PD-16123 and PD-16124

========================================================================

Enhancements for Data Build Notifications

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Data_Build_Email_202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Data_Build_Email_202406.htm

Enhancements for Data Build Notifications

Email notifications for certain ACA functions have been enhanced with additional information. When a client completes a build on the Rebuild ACA Data form or the Build ACA 1095 Registers form, the email notification now notifies the client when the process was completed and whether there were any errors in the process.

JIRA # PP-1431

========================================================================

Enhancements to Employee Change Report Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Improve_Employee_Change_202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Improve_Employee_Change_202406.htm

Enhancements to Employee Change Report Performance

Improvements have been applied to increase the loading speed for the Employee Change Report. These improvements apply to all three modes of this report selected in the Report Type field.

JIRA # PP-1330

========================================================================

Enhancements to Purge Clients Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Purge_Client_Form_202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Purge_Client_Form_202406.htm

Enhancements to Purge Clients Form

The Purge Clients form has been enhanced with additional features and usability improvements. These enhancements make it easier and more intuitive for service providers to comply with laws regarding how long they can retain client and employee data, and allows clients to easily search for inactive clients, remove records, and download reports of purged records.

The Years of Inactivity field is used to select the number of years since the Client Status Date and the last employee voucher pay date. Selecting a value in this field populates the table with matching records.

Click Clear List to remove all items from the list.

Select the Rebuild Registers option to have tax registers rebuilt during the purge process with the purged employee voucher data removed.

Select Purge Clients to display a confirmation message. Select yes to begin the purge process, which removes the clients from the system.

Note: Note: This process cannot be reversed.

Once a purge is complete, the Download Purge Reports button can be used to download a report of clients removed from the system.

JIRA # PP-1299

========================================================================

New Tax Register Audit Inquiry Utility

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Tax_Register_Inquiry_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/PP_Tax_Register_Inquiry_QR202406.htm

New Tax Register Audit Inquiry Utility

Service providers can access a new utility to review tax amounts in registers and compare them to the total tax in payroll vouchers and check for any discrepancies. This utility automatically processes an audit once a week.

Note: This feature is only available for service providers.

Service providers can review the audit by accessing the Tax Register Audit Inquiry form by clicking System > View > Tax Register Audit Inquiry. This form displays a report including the number of registers that did not match the voucher tax totals, as well as all relevant clients, employees, and tax codes.

[Image: tax]

Note: Note: To have access to this form, the HRPY.WORK*REG.AUDIT.INQUIRY process ID must be added to the user role.

Click a link in the Register Type column to display a detailed report of all registers for the selected client or employee.

Using this form, service providers can verify if any registers have discrepancies with payroll vouchers and determine which registers need to be rebuilt.

JIRA # WSP-336

========================================================================

Removal of Max Amt Before Override Field on System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/Removal_of_Max_Amt_Before_Override_Field_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/Removal_of_Max_Amt_Before_Override_Field_QR202406.htm

Removal of Max Amt Before Override Field on System Parameters Form

Due to lack of functionality, the Max Amt Before Override field on the System Parameters form has been removed.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-16889

========================================================================

Enhancements to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/System_Parameters_Form_Enhancements_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/System_Parameters_Form_Enhancements_QR202406.htm

Enhancements to System Parameters Form

The following enhancements now reside on the System Parameters form, which you can access on the System|Change menu.

New Custom Feature Codes

Two new custom feature codes are now available:

[Image: screenshot]

Note: Note the following:

[Image: screenshot]

Note: The VOLUNTARYDEDACH custom feature code can only be set at the system level and is only available for service providers.

Select Feature Code List Updates

In addition to sorting the Feature Code column in the Select Feature Code list, you can now sort the Feature Description column. (Select Custom Feature Codes to access this list.) Also, you can now search for custom feature codes using the new Refine Search section. For example:

[Image: screenshot]

New Independent Contractors Section

A new section, Independent Contractors, is now available. For example:

[Image: screenshot]

The fields in the Independent Contractors section indicate how to pay 1099 contractors, so you can easily manage large groups of these employee types:

Note: Note the following about the Independent Contractors section:

For more information, see the in-product help, PrismHR Payroll Processing Guide, or PrismHR System Administration Guide.

JIRA # PD-16775, PD-17040, 17111, and WSP-281

========================================================================

Enhancement to Web Service User Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202406/System/Web_Service_User_Form_Enhancement_QR202406.htm Path: PD/Release-Notes/Enhancements/2024/QR202406/System/Web_Service_User_Form_Enhancement_QR202406.htm

Enhancement to Web Service User Form

A warning message now displays after selecting a User ID and clicking Delete in the Web Service User form, so you can confirm this action to prevent deleting the wrong user. For example:

[Image: screenshot]

Note: You can access this form by selecting the Web Service Users option on the Actions menu in the System Parameters form.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-16464

========================================================================

Enhancements to Client Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Client/Client_Details_Form_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Client/Client_Details_Form_Enhancements_QR202409.htm

Enhancements to Client Details Form

The following enhancements now reside on the Client Details form, which is available on the Client|Change menu:

[Image: screenshot]

To better automate any billing that is processed through the Bill Pending form, you can now enter or select the billing location in the new Bill Pending Location field.

Note: Users whose role is set to INQUIRY for the Client Details form displays this field in read-only format and cannot enter or select a billing location.

[Image: screenshot]

Note: This panel consists of a new Payroll Reminder Notifications field and the existing Payday Notifications and Payroll Submission Notifications fields that previously resided in the Other Options panel.

Service providers can now set payroll reminders at the client level using the Payroll Reminder Notifications field to send payroll reminders to worksite advisors and worksite trusted advisors if the payroll is still in timesheet entry status as the payroll’s completion date gets closer to the cutoff date. For example, if the payroll will no longer be available to worksite advisors and worksite trusted advisors as of 4/15/2024 and it is not completed, the system sends a reminder to those users on 4/13/2024 that payroll is almost due.

Note: When setting up payroll reminders, to enable notifications at the system level, you must select the Enable payroll reminder notifications field on the System Parameters form. (See Enhancements to System Parameters Form.)

However, if you enable Enable payroll reminder notifications on the System Parameters form, the system sends payroll reminders for all clients, except those that have the client-level Payroll Reminder Notifications field disabled.

[Image: screenshot]

Assigning a numeric value in the Benefit Parent Client field allows you to group clients together for benefit purposes.

[Image: screenshot]

Note: You can only enter service providers in these employee representative account type fields.

[Image: screenshot]

You can enter a checking account in the Reverse Wire Account field that is associated with a reverse wire transfer.

Important! The reverse wire process does not work for internal processing. (You cannot make an entry in the Reverse Wire Account field if the active client is set up for internal ACH processing on the System Parameters form.)

Note: The system validates this checking account, so you cannot enter an account that is linked to an ACH originator set up for a reverse wire transfer in any other bank account fields, except for the reverse wire transfer account.

After entering the checking account number, the following warning displays:

[Image: screenshot]

Click OK to continue, then perform the tasks listed in the warning.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16094, PD-17511, WSP-459, WSP-476, and WSP-572

========================================================================

Enhancement to Commission Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Client/Commission_Maintenance_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Client/Commission_Maintenance_Form_Enhancement_QR202409.htm

Enhancement to Commission Maintenance Form

Previously, users were able to select a Based On option in the Commission Maintenance form that did not work with the selected Flat or Percent option, which resulted in the system calculating the gross wages flat commission as a percentage in the report output. (For example, the system calculated the commission as 50% of gross wages instead of a flat $50.)

Note: To access the Commission Maintenance form, select Commissions on the Actions menu in the Client Details form.

The system now validates that the following Based On options do not work with the selected Flat or Percent option:

Note: If you make these types of selections, an error message displays and you cannot save the record.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-17053

========================================================================

Enhancement to Report Print Options Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Client/Report_Print_Options_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Client/Report_Print_Options_Form_Enhancement_QR202409.htm

Enhancement to Report Print Options Form

The breadcrumbs for the Report Print Options form, which is accessible from the Actions menu on the Client Details form, now displays the correct form name in its breadcrumbs. For example:

[Image: screenshot]

In addition, the description for the Report Print Options form in the User Roles form now displays the correct description. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-17348

========================================================================

Modernized Button Style on Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Client/Updated_Button_Style_on_Forms_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Client/Updated_Button_Style_on_Forms_Enhancement_QR202409.htm

Modernized Button Style on Forms

Buttons that display on some of the PrismHR forms have been modernized, which helps you accomplish tasks more quickly and efficiently. For example:

[Image: screenshot]

Buttons on the following forms now display the modern style:

Note: You can access this form by selecting User Fields on the Actions menu in the Client Details form.

JIRA # PD-17345, PD-17346, and PD-17347

========================================================================

Enhancement to Work Groups Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Client/Work_Groups_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Client/Work_Groups_Form_Enhancement_QR202409.htm

Enhancement to Work Groups Form

A new field, Obsolete, now displays on the Work Groups form, which is available on the Client|Change menu. For example:

[Image: screenshot]

To obsolete an existing work group:

  1. Enter or select a Work Group.

  2. Select Obsolete.

  3. Click Save.

Obsolete work groups will display Yes in the new Obsolete Code column on the Work Group with User Security list, which you can access by selecting Work Group. For example:

[Image: screenshot]

Note: After a work group is made obsolete, the following occurs:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-17419 and PD-17420

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Documentation/New_Task_Sheets_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Documentation/New_Task_Sheets_QR202409.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheet was updated:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Client Tax Register Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Employer%20Administration/Client_Tax_Register_Report_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Employer Administration/Client_Tax_Register_Report_Form_Enhancement_QR202409.htm

Enhancement to Client Tax Register Report Form

You can now control the display of Social Security Numbers (SSNs) in the Client Tax Register Report form by enabling the new SHOWSSNFORTAX custom feature code in the System Parameters form. For example:

[Image: screenshot]

In addition to enabling the SHOWSSNFORTAX custom feature code, you must also set up a Conversion User in the Account Management Roles panel on the Users form. After making these updates, SSNs will display in the Client Tax Register Report when you set the Report Type field to Detail. (This enhancement is helpful when tax departments need to generate reports with the full SSN on their conversion accounts to test/reconcile data when converting from other systems.) For example:

[Image: screenshot]

For more information, see the in-product help, PrismHREmployer Administration Guide, and PrismHR System Administration Guide.

JIRA # WSP-490

========================================================================

Enhancement to Worker’s Compensation Exports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Employer%20Administration/WC_Exports_Form_Enh_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Employer Administration/WC_Exports_Form_Enh_QR202409.htm

Enhancement to Worker’s Compensation Exports Form

The Check Date column that displays in the Worker’s Compensation Exports form’s preview and report output now displays as “Last Check Date.” For example:

[Image: screenshot]

Note: This enhancement only affects the SUNZ Worker’s Compensation and Generic (Non Third Party) vendors. (The Cedar Hill Within Pay Dates vendor’s report does not include the pay date or column headers.)

The former Check Date column title was confusing because dates in this column represent the last check date for the pay date range entered. Therefore, the system creates a file that only displays the last check date for each employee in that pay period.

For more information, see the in-product help or PrismHREmployer Administration Guide.

JIRA # PD-17140

========================================================================

Enhancements to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/HumanResources/Employee_Details_Form_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/HumanResources/Employee_Details_Form_Enhancements_QR202409.htm

Enhancements to Employee Details Form

The following enhancements now reside on the Employee Details form, which is available on the HR|Change menu.

[Image: screenshot]

Selecting the Works for <X> other company(s) link displays a list of other companies where the employee works, so you can quickly access that company by selecting it. (After making a selection, the Employee Details form reopens to that company.)

[Image: screenshot]

Note: International addresses are not yet compatible with check formats.

Enabling the International Address field displays the new Country field in the panel, so you can add the employee’s country to their mailing address. For example:

[Image: screenshot]

In addition, three field names have been updated to accommodate international addresses:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-10079 and WSP-570

========================================================================

Removal of OnHRP Onboarding (ON) Menu Option

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/ONHRP/OnHRP_Onboarding_ON_Menu_Option_Removed_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/ONHRP/OnHRP_Onboarding_ON_Menu_Option_Removed_QR202409.htm

Removal of OnHRP Onboarding (ON) Menu Option

The Onboarding (ON) menu option, which was created for the retired OnHRP product, has been disabled in the system. (Previously, a blank screen displayed when users selected this option.)

Note: You cannot search for the Onboarding (ON) menu option and its process ID does not display in the User Roles form.

JIRA # PD-17317

========================================================================

Enhancement to ACH Originators Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/ACH_Originators_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/ACH_Originators_Form_Enhancement_QR202409.htm

Enhancement to ACH Originators Form

To help automate the reverse wire process, a new option, Reverse Wire Transfer, now displays in the Third Party Format field. For example:

[Image: screenshot]

Performing a reverse wire transfer allows clients to determine the payment amount prior to posting payrolls, so the system places those funds into a file that is sent before payroll is completed/posted. (This ensures that the client has the funds before payroll is posted.)

Important! The reverse wire process does not work for internal processing. (System validation on the Reverse Wire Account field on the Account tab in the Client Details form will not allow users to make an entry in this field if the active client is set up for internal ACH processing on the System Parameters form.)

In addition, after you save a reverse wire transfer, you cannot use the ACH originator for employee direct deposits.

Note: You cannot make changes to a reverse wire payroll whose payment has been marked as received because the funds were already sent. (These payrolls display with green checkmarks, marking them as lockedPayment Received payrolls when viewing them in the SuperBatch and Process Payroll forms.)

After selecting Reverse Wire Transfer, the following new fields display:

Note: The client is responsible for setting up the title of the output file, which should include the file’s creation date and timestamp.

If you select the Wells Fargo option, the following new fields display:

Note: If you enter a positive number a message displays, “Are you sure? Usually, this process is run before the invoice date.” Click OK to continue.

Note: Note the following:

[Image: screenshot]

Click OK to continue, then perform the tasks listed in the warning.

[Image: screenshot]

[Image: screenshot]

Click OK to continue.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # WSP-241, WSP-242, WSP-243, WSP-475, and WSP-550

========================================================================

Removal of Auto Clear Offsetting Balances Menu Option

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Auto_Clear_Offsetting_Balances_Form_Retirement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Auto_Clear_Offsetting_Balances_Form_Retirement_QR202409.htm

Removal of Auto Clear Offsetting Balances Menu Option

The Auto Clear Offsetting Balances menu option, which resided on the Accounts Receivable|Action menu, has been disabled in the system, so it is no longer available on that menu or by using the global search.

Note: New enhancements to Cash Receipts processing will be available in late 2024, which will alleviate the need for this programming.

For instructions on how to manually clear offsetting balances, refer to the “[Where is the Accounts Receivable / Action / Auto Clear Offsetting Balances Menu?](https://prismhr.my.site.com/CSC/s/article/Where-is-the-Accounts-Receivable-Action-Auto-Clear-Offsetting-Balances-Menu)” article on the CRC.

JIRA # PD-16209

========================================================================

Enhancement to Billing Rules (Unbundled) Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Billing_Rules_Unbundled_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Billing_Rules_Unbundled_Form_Enhancement_QR202409.htm

Enhancement to Billing Rules (Unbundled) Form

A new option, Per Active Employee Per Month, is now available in the Based On field on the Billing Rules (Unbundled) form. For example:

[Image: screenshot]

The Per Active Employee Per Month option calculates the admin fee based on the client’s employee count on the first regular payroll of the month, using a tiered charge format. (The second payroll captures any new employees.)

Enabling the Per Active Employee Per Month option bills active employees for the month. For example, if the first payroll of the month has 100 active employees, they will be billed for 100 employees. On the second payroll if there is a new hire and a termination, they will still be billed for one employee on that payroll, since the new hire needs to be billed and the termination was active for part of the month.

Note: An edge case could occur that is currently not supported. When you calculate a payroll, the system determines the number of employees that are active at that time and once the payroll is posted, it commits counts to the employee records. If you calculate the payroll and add several employees or terminate employees and then post without recalculating, the system misses the new employees added/removed in the billing cycle.

Selecting the Per Active Employee Per Month option automatically initiates the following field updates that cannot be changed:

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17390 and PD-17391

========================================================================

Enhancements to Cash Posting Reports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Cash_Posting_Reports_Form_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Cash_Posting_Reports_Form_Enhancements_QR202409.htm

Enhancements to Cash Posting Reports Form

The following enhancements now reside on the Cash Posting Reports form, which is available on the Accounts Receivable|Report menu:

[Image: screenshot]

Using this list, you can easily locate the bank using the sorting or search features. Simply click the Account ID or Reference columns to quickly locate your bank, or search for a bank using the Refine Search section.

[Image: screenshot]

In addition, the Posting Deposit # column in the report’s output now displays as Posting Batch # because this column represents the system-generated batch number. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRAccounting User Guide.

JIRA # PD-17224 and PD-17594

========================================================================

Enhancement to Cash Receipts Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Cash_Receipts_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Cash_Receipts_Form_Enhancement_QR202409.htm

Enhancement to Cash Receipts Form

A new icon,

[Image: screenshot]

, now displays on the Cash Receipts form, which is available on the Accounts Receivable|Action menu. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

Selecting the Import icon (

[Image: screenshot]

) opens the new Cash Receipts Import form, where you can upload a file for import and view errors that occurred during cash receipts imports or view successfully imported rows. (See New Cash Receipts Import Form.)

Note: Note the following:

For more information, see the in-product help or PrismHRAccounting User Guide.

JIRA # PD-17284

========================================================================

Enhancements to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Data_Import_Tool_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Data_Import_Tool_Enhancements_QR202409.htm

Enhancements to Data Import Tool

The following enhancements now reside on the Data Import Tool:

[Image: screenshot]

You can use these new fields to do the following:

[Image: screenshot]

Note: Previously, you could only access this import template from the W/C Classification Rates form.

You can use the Global W/C Classification Rates import template to import changes to W/C rates at the system level.

[Image: screenshot]

You can use these new fields to do the following:

[Image: screenshot]

You can use these new fields to do the following:

Note: Only applies if the worksite location of the client is an EEO Federal Contractor.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-15289, PD-17418, PD-17580, and PD-17586

========================================================================

Enhancements to Delivery Methods and Special Delivery Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Delivery_Methods_and_Special_Delivery_Forms_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Delivery_Methods_and_Special_Delivery_Forms_Enhancements_QR202409.htm

Enhancements to Delivery Methods and Special Delivery Forms

The following enhancements now reside on the Delivery Methods and Special Delivery forms:

[Image: screenshot]

Note: You can access this form by selecting Delivery Methods on the System|Change menu.

[Image: screenshot]

Note: You can access this form by selecting Special Delivery on the Actions menu in the Client Details form.

[Image: screenshot]

For more information, see the in-product help, PrismHRClient Administration Guide, or PrismHR Payroll Setup Guide.

JIRA # PD-17292

========================================================================

Enhancement to Detail Time Sheet Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Detail_Time_Sheet_Entry_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Detail_Time_Sheet_Entry_Form_Enhancement_QR202409.htm

Enhancement to Detail Time Sheet Entry Form

Previously, when a salaried employee’s pay was split between two or more pay codes and the pay codes were marked to round to the period pay so the total amount of the salaried employee’s pay equals their standard pay, the system displayed the last detail time entry as a paid amount that was a few cents off the other detail entries.

Now, the system adjusts the last detail time entry so the time entry’s total matches the salaried employees’ actual salary amount. Therefore, the last detail time entry might be different due to rounding to ensure the total matches the employee’s salary. For example, when the system adds them and calculates to three cents more than the salary, it subtracts three cents from that last entry.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-17435

========================================================================

Enhancement to Employee Payroll Vouchers Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Employee_Payroll_Vouchers_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Employee_Payroll_Vouchers_Form_Enhancement_QR202409.htm

Enhancement to Employee Payroll Vouchers Form

Worksite managers and worksite trusted advisors can now reprint multiple vouchers at once that have an associated check in the Employee Payroll Vouchers form, which is available on the Payroll|View menu.

Note: To use this feature, worksite managers and worksite trusted advisors must also have user role access to the Reprint Payroll Checks form (MVQ.CONTROL*REPRINT.CHECK.MAINT process ID).

These users can now either individually select vouchers for reprinting or click Select All to choose all vouchers. For example:

[Image: screenshot]

Note: If they click Select All, the following message displays regarding any vouchers that cannot be reprinted, “Voucher(s) that do not have a check associated have been excluded from the selection.” Therefore, you cannot select the following voucher types for reprint: A, J, void, check import, or any vouchers without an associated check.

To reprint multiple vouchers, do the following:

  1. Enter or select an employee, then select the year. The associated employee vouchers display.

  2. Click Select All or individually select the vouchers you want to reprint.

  3. Click Reprint. A PDF displays that contains all selected vouchers, which you can download or print.

Note: Users whose role is set to INQUIRY for the Employee Payroll Vouchers form can view the Reprint button, but cannot click it.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-17210

========================================================================

Enhancement to Employee Voucher Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Employee_Voucher_Report_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Employee_Voucher_Report_Enhancement_QR202409.htm

Enhancement to Employee Voucher Report

The employee ID now displays next to the employee name in the on-screen and .xls output in the Employee Voucher Report. For example:

[Image: screenshot]

.

In addition, the “Totals For” label that displayed next to the employee name was removed.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-16988

========================================================================

Enhancement to Payroll Control Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Payroll_Control_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Payroll_Control_Form_Enhancement_QR202409.htm

Enhancement to Payroll Control Form

In association with the enhanced the reverse wire process, if you try to delete a payroll in the Payroll Control form where a reverse wire transfer journal exists an error displays, “Payroll <XXX> can not be deleted as the ACH journals have already been created.”

For more information, see the in-product help or PrismHR Payroll Processing Guide.

JIRA # WSP-545

========================================================================

Enhancement to Process Payroll Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Process_Payroll_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Process_Payroll_Form_Enhancement_QR202409.htm

Enhancement to Process Payroll Form

A new link, Payroll Approval, now displays in the Selected Payroll panel on the Process Payroll form, which is available on the Payroll|Action menu. For example:

[Image: screenshot]

Selecting Payroll Approval in the Payroll Maintenance field allows quick access to the Payroll Approval form, where you can review and approve the selected payroll.

Note: Users whose role is set to INQUIRY for the Payroll Approval form can select the Payroll Approval link, but the Payroll Approval form will display in read-only format.

For more information about the Process Payroll form, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # WSP-431

========================================================================

Enhancements to SuperBatch Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/SuperBatch_Form_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/SuperBatch_Form_Enhancements_QR202409.htm

Enhancements to SuperBatch Form

The following enhancements now reside on the SuperBatch form, which is available on the Operations|Action menu:

Ribbon Updates

The following updates were made to the ribbon:

[Image: screenshot]

[Image: screenshot]

Note: Clicking a highlighted checkmark deselects it, so the system no longer displays payrolls with that status.

[Image: screenshot]

Payroll Process Updates

Payroll process information now displays differently:

For example:

[Image: screenshot]

Self-Service Filter Update

The system now denotes whether a payroll is self-service in the Client Level Actions area by displaying “SS” next to Employees Finalized when you select All Payrolls in the Self-Service filter. For example:

[Image: screenshot]

Note: Note the following about this enhancement:

New Process Payroll Option

You can now directly access the Process Payroll form for self-service clients by clicking the payroll’s checkbox and selecting Process Payroll on the Actions menu. For example:

[Image: screenshot]

Note: Note the following about this enhancement:

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-17574, PD-17575, PD-17576, WSP-38, and WSP-432

========================================================================

Enhancement to Tax Register Detail Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Tax_Register_Detail_Report_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Tax_Register_Detail_Report_Form_Enhancement_QR202409.htm

Enhancement to Tax Register Detail Report Form

You can now control the display of Social Security Numbers (SSNs) in the Tax Register Detail Report form by enabling the new SHOWSSNFORTAX custom feature code in the System Parameters form. For example:

[Image: screenshot]

In addition to enabling the SHOWSSNFORTAX custom feature code, you must also set up a Conversion User in the Account Management Roles panel on the Users form. After making these updates, SSNs will display in the Tax Register Detail Report. (This enhancement is helpful when tax departments need to generate reports with the full SSN on their conversion accounts to test/reconcile data when converting from other systems.) For example:

[Image: screenshot]

Note: The SSN column only displays the last four digits if you do not enable SHOWSSNFORTAX custom feature code and set up a Conversion User in the Account Management Roles panel on the Users form.

For more information, see the in-product help, PrismHRPayroll Reports guide, and PrismHR System Administration Guide.

JIRA # WSP-490

========================================================================

Enhancement to Time Sheet Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Time_Sheet_Entry_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Time_Sheet_Entry_Form_Enhancement_QR202409.htm

Enhancement to Time Sheet Entry Form

Previously, if an employee had a pay rate change pending for a current pay period, which displayed as a red dot on the timesheet, and then users deleted that pay rate change in the Pay History Adjustment form, the system still displayed that pay rate change in the timesheet’s Pay rate column.

This enhancement ensures that the pay rate change and its red dot no longer display in the timesheet when users delete that pay rate change and instead displays the existing rate in the Pay rate column.

For more information, see the in-product help or PrismHR Payroll Processing Guide.

JIRA # PD-17581

========================================================================

Enhancement to Time Sheet Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Time_Sheet_Import_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Time_Sheet_Import_Form_Enhancement_QR202409.htm

Enhancement to Time Sheet Import Form

The Import Hours Worked and Standard Hours to Time Sheet field now displays as Use Import for Hours Worked and Employee Default Hours for Hours Paid on the Time Sheet Import form when you enable the TS-LOAD.HRS.WORKED (Global) or TS-LOAD.HRS.WORKED-C (Client) custom feature code on the System Parameters form. For example:

[Image: screenshot]

Note: Enabling the Use Import for Hours Worked and Employee Default Hours for Hours Paid field populates the employee’s default hours (not standard hours) on the timesheet.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-17611

========================================================================

Enhancement to Unbundled Billing Rules Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Unbundled_Billing_Rules_Import_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Payroll/Unbundled_Billing_Rules_Import_Form_Enhancement_QR202409.htm

Enhancement to Unbundled Billing Rules Import Form

You can now import a new Based On rule, Per Active Employee Per Month, when you select Download Spreadsheet in the Unbundled Billing Rules Import form.

The Per Active Employee Per Month option calculates the admin fee based on the client’s employee count on the first regular payroll of the month, using a tiered charge format. (The second payroll captures any new employees.) (See Enhancement to Billing Rules (Unbundled) Form.)

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17397

========================================================================

Enhancement to Employee PTO Register and Employee PTO Register Inquiry Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/PTO/EE_PTO_Reg_and_Inquiry_Forms_Enh_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/PTO/EE_PTO_Reg_and_Inquiry_Forms_Enh_QR202409.htm

Enhancement to Employee PTO Register and Employee PTO Register Inquiry Forms

The system now notes if an employee is auto-enrolled in a PTO plan by displaying “Employee Auto Enrolled” on the Employee PTO Register and Employee PTO Register Inquiry forms. For example:

[Image: screenshot]

[Image: screenshot]

The system displays the “Employee Auto Enrolled” notification during the following auto-enrollments:

Note: The system will not adjust current (existing) records. (Auto-enrollments will be captured going forward. All other records will be blank.)

For more information, see the in-product help or PrismHR Paid Time Off User Guide.

JIRA # WSP-183

========================================================================

Enhancement to PTO Benefit Plans Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/PTO/PTO_Benefit_Plans_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/PTO/PTO_Benefit_Plans_Form_Enhancement_QR202409.htm

Enhancement to PTO Benefit Plans Form

A new field, Apply Carryover toward Maximum Accrual Per Year, now resides on the PTO Benefit Plans form. For example:

[Image: screenshot]

Note: The Calculation Basis must be Flat Amount by Hours Worked to view the Apply Carryover toward Maximum Accrual Per Year field in the Flat Amount per Hours Worked panel.

You can enable the Apply Carryover toward Maximum Accrual Per Year field to implement Colorado and Maine paid leave.

Note: Note the following:

For more information, see the in‑product help or PrismHR Paid Time Off User Guide.

JIRA # PD-17295 and PD-17297

========================================================================

Enhancement to ACH Batch Control History Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/System/ACH_Batch_Control_History_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/System/ACH_Batch_Control_History_Form_Enhancement_QR202409.htm

Enhancement to ACH Batch Control History Form

A new panel, ACH File Build Reports, now resides on the ACH Batch Control History form. For example:

[Image: screenshot]

Note: To access the ACH Batch Control History form, select Completed ACH Transactions on the ACH Processing form or the ACH Processing (Internal Payroll) form and then select a batch.

Previously, users were directed to use ACH reporting in the Report Center when they clicked Build Review Reports for a completed ACH batch. (This message no longer displays.)

You can now run the original ACH reports without reopening the ACH process by clicking Build Review Reports, which displays the new ACH File Build Reports panel. (These are the same reports that the system creates when you complete the ACH process for the first time, which display in the ACH Batch Control form by selecting Build Review Reports.)

To view the original ACH reports, select the following options on the ACH File Build Reports panel:

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # PD-17400

========================================================================

Enhancement to Email Services Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/System/Email_Services_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/System/Email_Services_Form_Enhancement_QR202409.htm

Enhancement to Email Services Form

A new email template type, Payroll Reminder Email, is now available on the Email Services form. For example:

[Image: screenshot]

Note: To access the Email Services form, select Email Services on the Actions menu in the System Parameters form.

Selecting the Payroll Reminder Email template type sets up an automated email for payroll reminders.

For more information, see the in-product help or PrismHR System Administration Guide.

JIRA # PD-17314

========================================================================

Enhancements to Message Templates Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/System/Message_Templates_Form_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/System/Message_Templates_Form_Enhancements_QR202409.htm

Enhancements to Message Templates Form

The following enhancements now reside on the Message Templates form, which is available on the System|Change menu:

[Image: screenshot]

Note: You can also use the existing <<COMPANY.NO>>, <<COMPANY.NAME>>, <<PAYROLL.NO>>, and <<PAYROLL.PAY.DATE>> substitution variables in payroll reminders.

The <<CUTOFF.DATE>> substitution variable represents the date when payroll is due. You can use this substitution variable to remind worksite managers and worksite trusted advisors to submit their time if the payroll is still in timesheet entry status. For example, if the payroll will no longer be available to worksite advisors and worksite trusted advisors as of 4/15/2024 and it is not completed, the system sends a reminder to those users on 4/13/2024 that payroll is almost due.

Note: This feature is only available for service providers.

[Image: screenshot]

The <> and <> substitution variables represent the name of the employee’s PTO benefit plan and their PTO balance in HR Action Approval email notifications.

Note: The available PTO hours are based on the time when the approval request was submitted.

The email notification delivered to the approver displays the information from these substitution variables. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-17313 and WSP-189

========================================================================

General System Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/System/PP_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/System/PP_Enhancements_QR202409.htm

General System Enhancements

The following enhancements have been added to the core Prism platform.

Enhancements to Building State Tax Solution

Improvements have been applied to increase the loading speed for the Building State Tax Solution Report, especially for users with a large number of clients.

JIRA # PP-1423

You can now perform a global search by entering an employee’s phone number in the Search field, the same way that you would search for their first or last name.

For more information about using the Search field, see the in-product help.

JIRA # PP-1503

Enhancements to Pending Benefit Self‑Billing Report Performance

Improvements have been applied to increase the loading speed for the Pending Benefit Self‑Billing Report, especially for clients with a large number of active employees.

JIRA # PP-1608

Find Changes Made By Webservice User

The Find Changes Made by a User form has been enhanced to included Webservice users. With this improvement, users can run an audit report to see all changes made by a specific user by API as well as through Prism directly.

In addition, this form has been renamed from Find All Changes for a User to Find Changes Made by a User to better convey the purpose of this audit report.

JIRA # PP-1505

Symmetry Address Verification Updated

The Symmetry address verification which validates address information has been updated to the latest interface.

JIRA # PP-1587

========================================================================

Enhancements to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/System/System_Parameters_Form_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/System/System_Parameters_Form_Enhancements_QR202409.htm

Enhancements to System Parameters Form

The following enhancements now reside on the System Parameters form, which is available on the System|Change menu:

[Image: screenshot]

You can notify users prior to the payroll’s cutoff date if the payroll has not been completed by selecting the Enable payroll reminder notifications field.

Note: If you already set up the RESTART-PAYROLL-GLOBAL and RESTART-PAYROLL-CLIENT custom feature codes, they will be automatically removed.

For more information, see the in-product help or PrismHR System Administration Guide.

JIRA # PD-14499, PD-15168, PD-15170, and PD-15295

========================================================================

Enhancements to Users Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/System/Users_Form_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/System/Users_Form_Enhancements_QR202409.htm

Enhancements to Users Form

The following enhancements now reside on the Users form, which is available on the System|Change menu:

[Image: screenshot]

Note: This feature is only available for service providers.

Enabling this role allows users with this level of access to view the full Social Security Number (SSN) on the Personal tab in the Employee Details form even if they only have Inquiry access to this form. However, they cannot edit the SSN on the Employee Details form.

Note: The Access to Full SSN role supersedes the SSN Mask Override setting on the Report Print Options form at the client level and the SSN Mask Option setting on the System Parameters form.

Now when you select these options the sMFA Device Expiration setting remains at Use Global Settings, which is the default.

Note: You can still manually change the sMFA Device Expiration setting.

[Image: screenshot]

Note: Note the following:

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-17579, WSP-393, and WSP-503

========================================================================

Enhancement to Web Service User Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/System/Web_Service_User_Form_Enhancement_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/System/Web_Service_User_Form_Enhancement_QR202409.htm

Enhancement to Web Service User Form

A new field, Marketplace Integration, now displays on the Web Service User form, along with a tool tip (

[Image: screenshot]

) that describes this field. For example:

[Image: screenshot]

Note: You can access this form by selecting the Web Service Users option on the Actions menu in the System Parameters form.

Enabling the Marketplace Integration field displays a second field where you can select the Marketplace Integration vendor’s description. (After making a selection, if this is a new user the vendor’s name displays in the User ID field.)

Note: If the user record already exists but the Marketplace Integration field is not enabled, you can enable this field and select a vendor’s description, which does not overwrite the existing User ID. After saving this update, you cannot change the User ID, the Marketplace Integration field, or the vendor description field.

In addition, the Minimum API Version and Contact Information fields were moved to the right side of the Web Service User form to accommodate the new Marketplace Integration field.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-17707

========================================================================

Enhancements to Notification Control Panel

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202409/Work-Centers/Notification_Control_Panel_Enhancements_QR202409.htm Path: PD/Release-Notes/Enhancements/2024/QR202409/Work-Centers/Notification_Control_Panel_Enhancements_QR202409.htm

Enhancements to Notification Control Panel

The layout/processing of the Notification Control Panel, which is available on the Work Centers|Onboarding & Benefits|Workflow Setup menu, has been updated to make it more user-friendly and efficient. In addition, the labels and buttons that display in this form have been relocated in the sections, so you can easily identify if a process is running and enabled or disabled. For example:

[Image: screenshot]

New Notification Control Panel Layout

To process the notifications more efficiently, OB Notify and BE Notify now run as separate processes, so you can run them independently. As an outcome of this separation, the form layout and buttons more clearly show how the form functions:

Note: As part of this update, you can now run the BE Notify, Payday Notifications, and ACH Processing processes independently.

As part of the form layout, the background process now automatically runs BE Notify, Payday Notify, ACH Processing, and Payroll Reminders.

Note: If BE Notify is turned off, the other processes continue to run.

Note: After clicking Start the system starts the processes and the button re-displays as Stop.

Updated Labels

To easily identify the state of processes and the location of their Stop/Start buttons in the Notification Control Panel, labels and their respective buttons now display as follows:

Note: When you click Start and then Save, the RUNNING label displays next to it.

Note: When you click Stop, the SHUTDOWN REQUESTED label displays next to the RUNNING label. After clicking Save, the NOT RUNNING label displays.

New Payroll Reminders Process

You can now use the Payroll Reminders panel to schedule payroll reminders for worksite advisors and worksite trusted advisors if the payroll is still in timesheet entry status as the payroll’s completion date gets closer to the cutoff date. For example, if the payroll will no longer be available to worksite advisors and worksite trusted advisors as of 4/15/2024 and it is not completed, the system sends a reminder to those users on 4/13/2024 that payroll is almost due.

Note: This feature is only available for service providers.

To schedule a payroll reminder:

  1. Click Back Office. Select Notification Control Panel on the Operations|Action menu.

  2. In the Payroll Reminders panel, enter the number of hours before the payroll cutoff date and time to send the reminder in the Payroll Reminder Timing field.

  3. Click Save.

For more information about the Notification Control Panel, see the in-product help, PrismHR Onboarding User Guide, or PrismHR Benefits Enrollment User Guide.

JIRA # PD-17247, PD-17249, PD-17250, PD-17031, PD-17249, PD-17312, and PD-17411

========================================================================

Enhancement to Client Notes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Client/Client_Notes_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Client/Client_Notes_Form_Enhancement_QR202411.htm

Enhancement to Client Notes Form

A new field, Category, now resides on the Client Notes form. For example:

[Image: screenshot]

Note: You can access this form by selecting the Notes tab in the Client Details form.

Select a Category to associate a note at the client level with a category. (The OV - Overview option in this field is the default.)

Note: Due to the existing client notes moving to a new format, the system made a change to the audit log.

Note: Note the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-17830, PD-17831, PD-17946, PD-18240, and PD-18241

========================================================================

Enhancement to Client Security Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Client/Client_Security_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Client/Client_Security_Form_Enhancement_QR202411.htm

Enhancement to Client Security Form

Two new panels, User Roles and Human Resource Roles, and a new field, Payroll Suppress, now reside on the Client Security form. For example:

[Image: screenshot]

Note: You can access this form by selecting Security on the Actions menu in the Client Details form.

Use these new features to perform the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-34

========================================================================

Enhancement to Divisions Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Client/Divisions_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Client/Divisions_Form_Enhancement_QR202411.htm

Enhancement to Divisions Form

A new field, Reverse Wire Account, now displays in the Division ACH panel on the Divisions form when the client is set up as Reverse Wire in the Client Details form. For example:

[Image: screenshot]

In addition, the ACH Details panel name changes to Reverse Wire Details in this scenario.

Note: The client must be set up with the Break Field set to Division and Create REAL Invoice Break enabled on the Billing tab in the Client Details form to invoice correctly by division.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-791

========================================================================

Enhancement to Worksite Locations Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Client/Worksite_Locations_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Client/Worksite_Locations_Form_Enhancement_QR202411.htm

Enhancement to Worksite Locations Form

A new field, Reverse Wire Check Acct, now displays in the ACH / Account Setup panel on the Worksite Locations form when the client is set up as Reverse Wire in the Client Details form. For example:

[Image: screenshot]

In addition, the ACH Details panel name changes to Reverse Wire Details in this scenario.

Note: The client must be set up with the Break Field set to Location and Create REAL Invoice Break enabled on the Billing tab in the Client Details form to invoice correctly by location.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-792

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Documentation/New_Task_Sheets_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Documentation/New_Task_Sheets_QR202411.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheet was updated:

Note: This article was previously titled Transfer Employee in PrismHR.

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Employee Address Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Address_Report_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Address_Report_Enhancement_QR202411.htm

Enhancement to Employee Address Report

International mailing addresses for employees now display in the Mailing Address column on the Employee Address Report. In addition, a new column, Country, now displays. For example:

[Image: screenshot]

Note: You can add an employee’s international mailing address on the Address tab in the Employee Details form.

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # WSP-741

========================================================================

Enhancements to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Details_Form_Enhancements_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Details_Form_Enhancements_QR202411.htm

Enhancements to Employee Details Form

The following enhancements are now available on the Employee Details form, which you can access on the HR|Change menu:

[Image: screenshot]

You can apply an FLSA exemption category code by selecting an option in the FLSA Exemption Category field.

Note: Note the following:

For example:

[Image: screenshot]

You can enable a future effective date to change an employee’s work shift, project, or work group by selecting the Future Date link, which opens a new form where you can do the following:

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-15772, PD-17630, PD-17642, PD-17643, PD-17647, PD-17648, PD-18077, and PD-18079

========================================================================

Enhancement to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Fields_Import_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Fields_Import_Form_Enhancement_QR202411.htm

Enhancement to Employee Fields Import Form

A new field, FLSA Exemption Category, is now available to use during imports on the Employee Fields Import form, which is available on the Operations|Action menu. For example:

[Image: screenshot]

You can use the FLSA Exemption Category field to import an FLSA Exemption Category Code in the Employee Details record of FLSA Exempt employees.

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18078

========================================================================

Enhancement to Employee Termination Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Termination_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/HumanResources/Employee_Termination_Form_Enhancement_QR202411.htm

Enhancement to Employee Termination Form

A new field, Last Pay Period Hours, now resides on the Employee Termination form, which is available on the HR|Action menu. For example:

[Image: screenshot]

You can use the Last Pay Period Hours field to automate the last payout to the terminated employee. (Entering an amount here populates the timesheet for this terminated employee’s last pay period, which is the pay period where their termination date is entered.)

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # WSP-870

========================================================================

Enhancement to Billing Rules (Unbundled) Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Billing_Rules_Unbundled_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Billing_Rules_Unbundled_Form_Enhancement_QR202411.htm

Enhancement to Billing Rules (Unbundled) Form

If a Per Active Employee Per Month (PAEPM) rule is already active for a client, you cannot create another PAEPM rule for that client using the same rule dates.

Creating another PAEPM rule in the Billing Rules (Unbundled) form using the same rule dates, which would make them active at the same time, displays the following warning after clicking Save:

[Image: screenshot]

Note: You can create multiple PAEPM rules if they have different dates, which makes them active at different times.

In addition, if you click Delete with a PAEPM rule displayed, the following warning displays:

[Image: screenshot]

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17904

========================================================================

Enhancements to Check History Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Check_History_Import_Enhancements_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Check_History_Import_Enhancements_QR202411.htm

Enhancements to Check History Import Form

The following enhancements are now available on the Check History Import form:

[Image: screenshot]

Click OK to continue.

[Image: screenshot]

[Image: screenshot]

Note: After selecting Add Check a message displays, “Client <ID> is not in the import batch client list. Do you wish to continue?” Click Yes to continue.

[Image: screenshot]

[Image: screenshot]

Note: If there is only one client, the Client Selection field defaults to that specific client.

[Image: screenshot]

In addition, the reports that display after clicking Download Reports in the Reports (CSV) column automatically default to all clients in the check import batch for completed imports when you view them in the downloaded output.

[Image: screenshot]

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # WSP-599, WSP-600, WSP-601, WSP-602, WSP-603, WSP-604, WSP-605, and WSP-698

========================================================================

Enhancement to Check Import Batch Status Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Check_Import_Batch_Status_Report_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Check_Import_Batch_Status_Report_Enhancement_QR202411.htm

Enhancement to Check Import Batch Status Report

The Client ID column in the Check Import Batch Status Report, which you can generate in the Check History Import Batch Status Report form, now displays multiple client IDs included in a batch. For example:

[Image: screenshot]

Note: The space limitations in this column truncate multiple IDs. Download this report to ensure you can view all IDs included in this column.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # WSP-711

========================================================================

Enhancements to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Data_Import_Tool_Enhancements_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Data_Import_Tool_Enhancements_QR202411.htm

Enhancements to Data Import Tool

The following enhancements now reside in the Data Import Tool, which is available on the Operations|Import Processing menu:

[Image: screenshot]

Note: The Employee Resident Address import template is only available for service providers.

To import this data, select Employee Resident Address from the Import Template menu, and then click Find File to upload the file.

Note: Note the following:

Note: A prompt displays in this instance, “Click Replace to use the suggested address or Skip to not import the employee’s address.”

[Image: screenshot]

You can use this new field to define an offer of coverage for eligible employees.

Note: Valid values for this required field are N, Y, YES, NO, No, Yes, yes, no, n, and y.

Note: The valid code for the Bill on Wages or Hours field must be either W to represent wages or H to represent hours.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-17725, PD-17777, PD-17811, and PD-18253

========================================================================

Enhancement to Mass Change Pay Group Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Mass_Change_Pay_Group_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Mass_Change_Pay_Group_Form_Enhancement_QR202411.htm

Enhancement to Mass Change Pay Group Form

Previously, if you specified New Default T/S Hours on the Mass Change Pay Group form, the system only changed the hours for employees who had default time sheet hours defined in the Default T/S Hours field on the Pay tab in the Employee Details form. Therefore, it did not add default hours for employees who did not have any set up.

Now when you enter New Default T/S Hours for employees on the Mass Change Pay Group form, the system automatically updates these hours in the Default T/S Hours field on the Pay tab in the Employee Details form.

Note: This update occurs even if the Auto Accept T/S field is not enabled.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17562

========================================================================

Enhancement to Offset Impound Accounts Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Offset_Impound_Accounts_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Offset_Impound_Accounts_Form_Enhancement_QR202411.htm

Enhancement to Offset Impound Accounts Form

A new Fund Type impound option, Benefits, now resides on the Offset Impound Accounts form. For example:

[Image: screenshot]

Note: You must enable the ACHBREAKONPRBATCH custom feature code on the System Parameters form to access the Offset Impound Accounts form on the Actions menu for the Bank Accounts form.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17693

========================================================================

Enhancement to Payroll Review Process

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Payroll_Allocation_Report_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Payroll_Allocation_Report_Enhancement_QR202411.htm

Enhancement to Payroll Review Process

You can now access the Payroll Allocation Report from the following forms as part of the payroll review process:

For example, you can easily access this report by selecting Payroll Allocation Report in the Review field on the Process Payroll form:

[Image: screenshot]

JIRA # WSP-872

========================================================================

Enhancement to Payroll Options Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Payroll_Options_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Payroll_Options_Form_Enhancement_QR202411.htm

Enhancement to Payroll Options Form

A new field, Delivery Message Override, now displays on the Payroll Options form. For example:

[Image: screenshot]

Note: You can access the Payroll Options form by selecting Options on the Actions menu in the Payroll Control form after entering or selecting a Payroll Number.

Selecting the Delivery Message Override field displays the Special Message field, where you can enter a message that will display on the payroll’s delivery sheet after payroll completes.

For more information, see the in-product help or PrismHR Payroll Processing Guide.

JIRA # WSP-919

========================================================================

Enhancement to SuperBatch Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/SuperBatch_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/SuperBatch_Form_Enhancement_QR202411.htm

Enhancement to SuperBatch Form

To help shorten the list of payroll processors who display in the Payroll Processor field so you can quickly find a processor, only processors who have open payrolls assigned to them now display in this list.

Note: Payroll processors who are assigned to a payroll in the Completed state or not currently assigned a payroll no longer display in the Payroll Processor field.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # WSP-874

========================================================================

Enhancement to Unbundled Billing Rules Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Unbundled_Billing_Rules_Import_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/Unbundled_Billing_Rules_Import_Form_Enhancement_QR202411.htm

Enhancement to Unbundled Billing Rules Import Form

If a Per Active Employee Per Month (PAEPM) rule is already active for a client, you cannot import another active PAEPM rule for that client.

Importing another PAEPM rule in the Billing Rules (Unbundled) form that has the same rule dates, which would make them active at the same time, displays the following warning:

[Image: screenshot]

Note: You can import multiple PAEPM rules if they have different dates, which makes them active at different times.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17949

========================================================================

Enhancements to W/C Billing Modifiers Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/Payroll/WC_Billing_Modifiers_Form_Enhancements_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/Payroll/WC_Billing_Modifiers_Form_Enhancements_QR202411.htm

Enhancements to W/C Billing Modifiers Form

The following enhancements now reside on the W/C Billing Modifiers form, which is available on the Client|Change menu.

[Image: screenshot]

[Image: screenshot]

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # WSP-733 and WSP-734

========================================================================

Enhancement to Group Benefit Plans Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/PD-17690%20(Epic).htm Path: PD/Release-Notes/Enhancements/2024/QR202411/PD-17690 (Epic).htm

Enhancement to Group Benefit Plans Form

A new field, Apply Impounding, now displays in the Special Options panel on the Group Benefit Plans form when the ACHBREAKONPRBATCH custom feature code is enabled on the System Parameters form. For example:

[Image: screenshot]

Enabling Apply Impounding allows you to choose the plans that use impound functionality. This functionality ensures that when employees are paid with a benefit plan that is included in the Offset Impounding Accounts, the system separates it out in the ACH file, as is currently done for net pay, taxes, or retirement.

Note: When you enable the Apply Impounding field, the system automatically updates the audit log.

For more information, see the in-product help or PrismHRBenefits Administration User Guide.

JIRA # PD-17691 and PD-17692

========================================================================

Enhancement to Planned Time Off Requests Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/PTO/Planned_Time_Off_Requests_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/PTO/Planned_Time_Off_Requests_Form_Enhancement_QR202411.htm

Enhancement to Planned Time Off Requests Form

The message that displays when you cancel a leave request by selecting Cancelled in the Planned Time Off Requests form has been updated, indicating that the system does not remove the leave from the current timesheet. This message now displays as follows:

[Image: screenshot]

Note: If you select No a message displays, “Change not made per user request.” Click OK.

For more information, see the in-product help or PrismHRPTO User Guide.

JIRA # PD-18111

========================================================================

Enhancement to Client Status Change Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/System/Client_Status_Change_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/System/Client_Status_Change_Form_Enhancement_QR202411.htm

Enhancement to Client Status Change Form

A new section, Termination Details, is now available on the Client Status Change form. For example:

[Image: screenshot]

You can now capture information in the Termination Details section that describes important details about the client termination, such as whether their taxes are complete for the year, are their W2s complete, or is the client moving to another PEO.

Note: You must select Terminated in the New Status field to display the Termination Details section.

Note: Note the following about the Termination Details section:

For more information, see the in-product help or PrismHR System Administration Guide.

JIRA # WSP-996

========================================================================

Enhancements to Accounting G/L Detail Download

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Accounting_GL_Download.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Accounting_GL_Download.htm

Enhancements to Accounting G/L Detail Download

Improvements have been applied to the Accounting G/L Detail Download form to increase performance and reduce downloading times.

JIRA # PP-1442

========================================================================

Enhancements to Change SUTA Flag on Vouchers

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Change_SUTA_Flag.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Change_SUTA_Flag.htm

Enhancements to Change SUTA Flag on Vouchers

Improvements have been applied to increase the speed of the Confirm Change SUTA Flag on Vouchers process.

JIRA # PP-1690

========================================================================

Direct Informer Login Setting Update

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Direct_Logins_Update_QR11.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Direct_Logins_Update_QR11.htm

Direct Informer Login Setting Update

In a previous enhancement, a new setting as added to disable direct logins from Informer. This option was marked as false by default, allowing direct logins. For security purposes, this setting is now enabled by default, preventing direct logins from Informer.

Important! To configure this option, the PrismHR team must perform the change on your system. Contact your PrismHR representative for help with this setting.

JIRA # PP-1672

========================================================================

Enhancements to Federal Report Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Federal_Report_Performance.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/System/PP_Federal_Report_Performance.htm

Enhancements to Federal Report Performance

Improvements have been applied to the Federal Tax Entity Report and the Federal 940 Report to improve performance and decrease loading times.

JIRA # PP-1547

========================================================================

Enhancements to New York Tax Reporting Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/System/PP_New_York_Tax_Performance.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/System/PP_New_York_Tax_Performance.htm

Enhancements to New York Tax Reporting Performance

Improvements have been applied to the New York Form MTA-305 Tax Reporting performance form to reduce loading times.

JIRA # PP-1686

========================================================================

Enhancement to Users Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2024/QR202411/System/Users_Form_Enhancement_QR202411.htm Path: PD/Release-Notes/Enhancements/2024/QR202411/System/Users_Form_Enhancement_QR202411.htm

Enhancement to Users Form

A new Human Resources Role, Manager User Setup, is now available in the Human Resource Roles panel. For example:

[Image: screenshot]

Enabling this role allows worksite managers to set up other worksite managers.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-557

========================================================================

Enhancement to PTO Classes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/MR_202501/Client/PTO_Classes_Form_Enhancement_MR202501.htm Path: PD/Release-Notes/Enhancements/2025/MR_202501/Client/PTO_Classes_Form_Enhancement_MR202501.htm

Enhancement to PTO Classes Form

Two new fields, Linked Accrual and Transfer To, now reside on the PTO Classes form. For example:

[Image: screenshot]

Note: This enhancement is part of the new Linked Accrual Plans Feature.

These new fields perform as follows:

For example, if class A is linked/transferred to class B, class A does not display on the Transfer To list for other classes to transfer to (effectively preventing anything from transferring to it).

Note: Note the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18270 and PD-18272

========================================================================

Enhancement to PTO Register Types Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/MR_202501/Client/PTO_Register_Types_Enhancement_MR202501.htm Path: PD/Release-Notes/Enhancements/2025/MR_202501/Client/PTO_Register_Types_Enhancement_MR202501.htm

Enhancement to PTO Register Types Form

A new option, Prior Year Accrual, is now available in the Trigger Method field on the PTO Register Types form. For example:

[Image: screenshot]

The Prior Year Accrual method triggers the balance register to move the accrued PTO hours from the accrual plan to the balance plan. The system initializes the trigger date when the pay period crosses over into the year’s end. The plan is triggered at year end from the accrual plan to the balance plan, which could be an anniversary date or a fiscal date, and uses the option set in the Year-End Basis field. (Either way, the transfer of hours happens during the pay period in which that year-end date occurs.)

Note: This enhancement is part of the new Linked Accrual Plans Feature. The system will transfer the prior year accrued hours from the accrual register to the balance register for employees enrolled in a Linked Accrual PTO Register when the plan year is triggered.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18271 and PD-18272

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/MR_202501/Documentation/New_Task_Sheets_MR202501.htm Path: PD/Release-Notes/Enhancements/2025/MR_202501/Documentation/New_Task_Sheets_MR202501.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following new task sheet was created:

You can use the Linked Accrual Plans Feature to accrue employee PTO hours for transfer once the plan year ends. This feature consists of two PTO plans that you must set up so employees can accrue time for a plan year in one register that they cannot use until the plan year ends. After the plan year ends, the accrued hours move to a new register where employees can use their PTO hours. (Employees can have several different linked accrual plans, one for sick time, one for vacation time, and so on.)

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/MR_202501/HumanResources/Employee_Details_Form_Enhancement_MR202501.htm Path: PD/Release-Notes/Enhancements/2025/MR_202501/HumanResources/Employee_Details_Form_Enhancement_MR202501.htm

Enhancement to Employee Details Form

Service providers can now enter a worksite manager’s user ID (who has access to the client) as the PTO Approver or Manager for the selected employee on the Work tab in the Employee Details form.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18654

========================================================================

Enhancement to Pay History Adjustment Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/MR_202501/HumanResources/Pay_History_Adjustment_Form_Enhancement_MR202501.htm Path: PD/Release-Notes/Enhancements/2025/MR_202501/HumanResources/Pay_History_Adjustment_Form_Enhancement_MR202501.htm

Enhancement to Pay History Adjustment Form

A warning message now displays when you select a Date Effective and click Delete Date on the Pay History Adjustment form. For example:

[Image: screenshot]

This warning message was created to inform users that deleting a pay rate change for the current timesheet may not update the current timesheet.

Important! Deleting a pay rate change that is effective on the first day of the current timesheet does not automatically update the pay rate on that timesheet.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18245

========================================================================

Enhancement to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/MR_202501/Payroll/Data_Import_Tool_Enhancement_MR202501.htm Path: PD/Release-Notes/Enhancements/2025/MR_202501/Payroll/Data_Import_Tool_Enhancement_MR202501.htm

Enhancement to Data Import Tool

The Remove Existing Data field on the Backup Account Assignment import template in the Data Import Tool now displays as Remove existing backup account assignments for all clients in the import file. For example:

[Image: screenshot]

Previously, selecting Remove Existing Data for all clients in the import file did not behave as expected when the import file contained a user who was already a backup assignment for the role in the import file.

Now when you select Remove existing backup account assignments for all clients in the import file, the system deletes backup assignments for all clients in the import file and adds user account assignments in the import file.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-18324

========================================================================

Enhancement to Updating Employee’s Location

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/MR_202501/System/PP_Performance_Employee_Location_MR202501.htm Path: PD/Release-Notes/Enhancements/2025/MR_202501/System/PP_Performance_Employee_Location_MR202501.htm

Enhancement to Updating Employee’s Location

Improvements have been applied to increase the loading speed while updating an employee’s worksite location, division, or department on the Employee Details form.

JIRA # PP-1718

========================================================================

Enhancements to Billing Rules (Unbundled) Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Billing/Billing_Rules_Unbundled_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Billing/Billing_Rules_Unbundled_Form_Enhancements_QR202503.htm

Enhancements to Billing Rules (Unbundled) Form

The following enhancements now reside on the Billing Rules (Unbundled) form, which is available on the Client|Change menu:

[Image: screenshot]

The updated Select Billing Rules selector provides a more efficient way to search for a billing rule, allowing you to search by rule number or description, and filter obsolete billing rules (the default is No).

[Image: screenshot]

You can use these fields as follows:

Note: The system tracks changes made in these fields in the audit log.

In addition, the system no longer displays the fees on payrolls for rules that are marked as Obsolete and does not calculate it through payroll.

The system now allows a credit for unbundled billing rules set to Per Employee Per Month, so these billing rules can now handle a negative amount.

For more information, see the in-product help, PrismHRBilling User Guide, or the PrismHR Payroll Setup Guide.

JIRA # PD-16181, PD-18260, PD-18297, and PD-18339

========================================================================

Enhancement to Auto Holiday Pay Days Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Days_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Days_Form_Enhancement_QR202503.htm

Enhancement to Auto Holiday Pay Days Form

Due to the new functionality that allows you to override hours on an existing Auto Holiday Pay Rule (see Enhancements to Auto Holiday Pay Rule Maintenance Form), a warning now displays when you try to delete one of those override dates in the Auto Holiday Pay Days form by clicking the X next to the date in the Holiday Dates panel. For example:

[Image: screenshot]

Note: Click Yes to continue.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18040

========================================================================

Enhancement to Auto Holiday Pay Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Form_Enhancement_QR202503.htm

Enhancement to Auto Holiday Pay Form

A new column, Override Date, now displays in the Auto Holiday Pay form. For example:

[Image: screenshot]

The Override Date column indicates when the Auto Holiday Pay Rules for that Line # has at least one entry in the Holiday Dates panel in the Auto Holiday Pay Days form.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18036

========================================================================

Enhancement to Auto Holiday Pay Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Report_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Report_Form_Enhancement_QR202503.htm

Enhancement to Auto Holiday Pay Report Form

In association with the new functionality that allows you to override hours on an existing Auto Holiday Pay Rule (see Enhancements to Auto Holiday Pay Rule Maintenance Form), a new column, Override Date, now displays on the Auto Holiday Pay Rules Report, which you can run from the Auto Holiday Pay Report form using the Rules or Days report type. For example:

[Image: screenshot]

[Image: screenshot]

Note: A Y in the Override Date column indicates that override dates exist for this rule or date.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18039 and PD-18043

========================================================================

Enhancements to Auto Holiday Pay Rule Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Rule_Maintenance_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Auto_Holiday_Pay_Rule_Maintenance_Form_Enhancements_QR202503.htm

Enhancements to Auto Holiday Pay Rule Maintenance Form

The following enhancements now reside on the Auto Holiday Pay Rule Maintenance form, which you can access by selecting New Rule or by selecting an existing rule in the Line # column on the Auto Holiday Pay form:

[Image: screenshot]

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

[Image: screenshot]

To allow employees to leave early and thus override hours on their Auto Holiday Pay, enter or select the Override Dates based on information that exists on the Auto Holiday Pay Days form, then enter their Override Hours. (You cannot duplicate override dates.)

Note: Note the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18037, PD-18038, and PD-18629

========================================================================

Enhancement to Client Acknowledgement Report Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Client_Acknowledgement_Report_Parameters_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Client_Acknowledgement_Report_Parameters_Form_Enhancement_QR202503.htm

Enhancement to Client Acknowledgement Report Parameters Form

The following enhancements were made to the Sort By options on the Client Acknowledgement Report Parameters form:

For example:

[Image: screenshot]

Note: Running the file using the Employee First Name Sort option sorts the employees on the report by their first name in alphabetical order.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18269

========================================================================

Enhancements to Client Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Client_Details_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Client_Details_Form_Enhancements_QR202503.htm

Enhancements to Client Details Form

The following enhancements now reside on the Client Details form:

[Image: screenshot]

You can use the new Multi-Entity Groups form to organize similar clients. (See New Multi-Entity Groups Form.)

Note: Note the following:

[Image: screenshot]

Note: This new Account Management Role is only available for service providers.

You can enter or select the user who has the Payroll Processor (Print/Mail) account management role in the Print/Mail User field. (If you select any other user an error message displays, “User <XXX> is not set up to be a Print/Mail User.”)

[Image: screenshot]

If users make a change to any of the fields in the Workers’ Compensation Insurance panel, that change is reflected in the audit history that displays on the W/C Policy History form.

Note: Note the following:

[Image: screenshot]

Note: To open the Select Payroll Reports list, select Report Code in the Payroll Reports panel. (Including or excluding this report is reflected in the audit log.)

[Image: screenshot]

Selecting the Enabled option in the Payroll live check calculation warning field displays a warning message during payroll calculation to indicate that the system will create a live check. (This field is helpful in case the client never wants to create a live check during payroll processing.)

Note: You can enable/disable the Payroll live check calculation warning field at the client level. Also, this field can be set to Enable, Disable, or Hidden in the user role’s Field Level Security.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18263, PD-18319, PD-18387, WSP-760, WSP-761, and WSP-989

========================================================================

Enhancement to Departments Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Departments_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Departments_Form_Enhancement_QR202503.htm

Enhancement to Departments Form

An updated selector now displays when you select Department Code in the Departments form. For example:

[Image: screenshot]

The updated Department selector provides a more efficient way to search for a department, allowing you to search by department name or description, and filter obsolete departments (the default is No).

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18508

========================================================================

Enhancement to PTO Absence Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/PTO_Absence_Codes_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/PTO_Absence_Codes_Form_Enhancement_QR202503.htm

Enhancement to PTO Absence Codes Form

A new option, Variable Salary, now displays in the Pay Method field on the PTO Absence Codes form. For example:

[Image: screenshot]

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18634

========================================================================

Enhancements to PTO Auto-Enrollment Rules Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/PTO_Auto_Enrollment_Rules_Maintenance_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/PTO_Auto_Enrollment_Rules_Maintenance_Form_Enhancements_QR202503.htm

Enhancements to PTO Auto-Enrollment Rules Maintenance Form

The following enhancements now reside on the PTO Auto-Enrollment Rules Maintenance form:

[Image: screenshot]

Note: The system includes the panel values in the rule when the Include option is enabled.

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18627 and WSP-1003

========================================================================

Enhancement to PTO Benefit Plans Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/PTO_Benefit_Plans_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/PTO_Benefit_Plans_Form_Enhancement_QR202503.htm

Enhancement to PTO Benefit Plans Form

To help prevent confusion, the Maximum Hours That Can Be Used in a Block field name in the Flat Amount per Hours Worked panel on the PTO Benefit Plans form now displays as Maximum hours for a detail time sheet entry. For example:

[Image: screenshot]

Note: You can use the Maximum hours for a detail time sheet entry field to set the maximum number of hours that can be entered in the Hours Paid field on the summary or detail time sheet.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18284

========================================================================

Enhancement to Time Sheet Defaults Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Time_Sheet_Defaults_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Time_Sheet_Defaults_Form_Enhancement_QR202503.htm

Enhancement to Time Sheet Defaults Form

A new option, Variable Salary, now displays in the Pay Method field on the Time Sheet Defaults form. For example:

[Image: screenshot]

Note: The Time Sheet Defaults form is accessible by clicking Time Sheet Defaults on the Actions menu in the Pay Groups form.

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

Note: Note the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18633

========================================================================

Enhancement to Work Groups Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Client/Work_Groups_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Client/Work_Groups_Form_Enhancement_QR202503.htm

Enhancement to Work Groups Form

The Employees Assigned to Work Group form, which is accessible by selecting Employees Assigned To on the Actions menu in the Work Groups form with a Work Group selected, now displays in the standard format used throughout the product. For example:

[Image: screenshot]

The Employees Assigned to Work Group form displays all employees assigned to the selected work group for the client, but only the employees you have access to display. (If you do not enter or select a work group and try to select the Employees Assigned To option an error message displays, “You must enter a Work Group first!”)

Note: The Employee ID links to the employee’s record on the Employee Details form.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-15207

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Documentation/New_Task_Sheets_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Documentation/New_Task_Sheets_QR202503.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheets were updated:

You can rehire an employee who was previously terminated using the Rehire form.

You can set up general parameters on the System Parameters panel.

PTO benefit plans support a flat amount per hours worked PTO accrual calculation basis that complies with state-mandated paid sick leave laws.

SuperBatch, a payroll processing hub, helps payroll processors oversee each payroll assignment without adding extra work or time. Using a streamlined workflow, you can accomplish all your payroll tasks—entering time data, checking for errors, finalizing and printing—directly from the SuperBatch.

The Enhanced Dashboard provides quick access to company information, favorite forms, and work centers from a central location.

Use the Deduction Codes form to maintain global deduction codes.

Use the Pay Codes form to establish pay code information and processing parameters required to process pay information in PrismHR.

The following task sheet was removed:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancements to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Details_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Details_Form_Enhancements_QR202503.htm

Enhancements to Employee Details Form

The following enhancements now reside on the Employee Details form:

[Image: screenshot]

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes.

Note: Employees whose Pay Method is set to Variable Salary will always be paid their per pay period amount regardless of the number of hours worked.

The following example explains the difference between standard salary pay and variable salary pay:

An employee makes $2,000 per pay period, with a standard hours of 80 hours, so their hourly rate is $25. They will work a variable amount of time, which should be reflected for allocation purposes, but they will always need to be paid $2,000 per pay period.

For the bi-weekly pay period, if they worked 80 hours they would receive $25 per hour or their standard pay of $2000. However, this employee might work RegA 40 hours and RegB 60 hours, so the company needs to track those hours but still pay the employee $2000. If they are listed as variable salary pay, I would expect the following to happen:

Standard salary pay:

Pay Code Hours Wages
Reg 80 25
Total 80 2000

Variable salary pay:

Pay Code Hours Wages
RegA 40 800 (40/100)*200
RegB 60 1200 (60/100)*200
Total 100 2000

Note: This enhancement does not apply when using a Future Date.

When you enter or select a new Work Shift value, a message now displays to confirm whether you want this value to display on the current timesheet after clicking Save. For example:

[Image: screenshot]

Updates to the current payroll timesheet are effective for:

Note: This enhancement does not apply when using a Future Date.

When you enter or select a new Project value, a message now displays to confirm whether you want this value to display on the current timesheet after clicking Save. For example:

[Image: screenshot]

Updates to the current payroll timesheet are effective for:

[Image: screenshot]

Note: This feature is only available for service providers.

After enabling the FAMILY_RELATIONSHIP custom feature code on the System Parameters form, you can use the Related section to track employees who are related to each other. (If you select a user who does not exist in the database an error message displays, “Employee ID <XXX> doesn’t exist.”)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18381, PD-18384, WSP-1015, WSP-1160, and WSP-1161

========================================================================

Enhancements to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Fields_Import_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Fields_Import_Form_Enhancements_QR202503.htm

Enhancements to Employee Fields Import Form

The following enhancements now reside on the Employee Fields Import form, which is available on the Operations|Action menu:

For example:

[Image: screenshot]

[Image: screenshot]

Note: Note the following when importing these fields:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17779, PD-18393, and PD-18655

========================================================================

Enhancement to Employee Hours By Active Weeks Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Hours_By_Active_Weeks_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Hours_By_Active_Weeks_Report_Enhancement_QR202503.htm

Enhancement to Employee Hours By Active Weeks Report

The system now displays the new Variable Salary option as “VSalary” in the Employee Hours By Active Weeks Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-18662

========================================================================

Enhancement to Employee Master Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Master_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Master_Report_Enhancement_QR202503.htm

Enhancement to Employee Master Report

The system now displays the new Variable Salary option as “V - VSalary” in the Employee Master Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-18664

========================================================================

Enhancement to Employee New Hire Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_New_Hire_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_New_Hire_Report_Enhancement_QR202503.htm

Enhancement to Employee New Hire Report

The system now displays the new Variable Salary option as “V - VSalary” in the Employee New Hire Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-18665

========================================================================

Enhancement to Employee Pay Rate Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Pay_Rate_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Pay_Rate_Report_Enhancement_QR202503.htm

Enhancement to Employee Pay Rate Report

The system now displays the new Variable Salary option as “VSalary” in the Employee Pay Rate Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-18666

========================================================================

Enhancement to Employee Termination Explanation

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Termination_Explanation_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Employee_Termination_Explanation_Enhancement_QR202503.htm

Enhancement to Employee Termination Explanation

To maintain consistency across the PrismHR forms, you can now only enter up to 200 characters in the Termination Explanation field on the Employee Termination form.

Note: If you enter more than 200 characters in the Termination Explanation field an error message displays when you click Save, “Termination Explanation is <xxx> characters. Termination Explanation can not exceed 200 characters.”

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18088

========================================================================

Enhancement to Mass Pay Rate Change Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Mass_Pay_Rate_Change_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Mass_Pay_Rate_Change_Form_Enhancement_QR202503.htm

Enhancement to Mass Pay Rate Change Form

A new option, Variable Salary, now displays in the Pay Method field on the Mass Pay Rate Change form. For example:

[Image: screenshot]

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18632

========================================================================

Enhancement to New Hire Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/New_Hire_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/New_Hire_Form_Enhancement_QR202503.htm

Enhancement to New Hire Form

A new option, Variable Salary, now displays in the Pay Method field on the New Hire form. For example:

[Image: screenshot]

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18631

========================================================================

Enhancement to New Hire Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/New_Hire_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/New_Hire_Report_Enhancement_QR202503.htm

Enhancement to New Hire Report

In association with the new Variable Salary pay method option that you can set on the Employee Details form, the system now recognizes employees assigned this pay method as “Salary” when you generate the New Hire Report from the New Hire Reporting form.

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-18949

========================================================================

Enhancement to Other Employee Information Termination Explanation

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Other_EE_Info_TermExpl_Enh_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Other_EE_Info_TermExpl_Enh_QR202503.htm

Enhancement to Other Employee Information Termination Explanation

To maintain consistency across the PrismHR forms, you can now only add or update up to 200 characters in the Termination Explanation on the Other tab in the Employee Details form.

Note: With the EDITTERM custom feature code enabled in the System Parameters form, if you add or update more than 200 characters in the Termination Explanation field an error message displays when you click Save, “Termination Explanation is <xxx> characters. Termination Explanation can not exceed 200 characters.”

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18089

========================================================================

Enhancement to Pay Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Pay_Codes_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Pay_Codes_Form_Enhancement_QR202503.htm

Enhancement to Pay Codes Form

A new field, Include in Variable Salary Pay, now displays in the Processing Options panel on the Pay Codes form. For example:

[Image: screenshot]

Note: The Include in Variable Salary Pay field only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)You can enable the Include in Variable Salary Pay field to include the selected pay code in the employee’s Variable Salary pay.

You can enable the Include in Variable Salary Pay field to include the selected pay code in the employee’s Variable Salary pay.

The Variable Salary pay method accurately tracks the hours that employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Setup Guide.

JIRA # PD-18914

========================================================================

Enhancement to Pay Rate Change Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Pay_Rate_Change_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Pay_Rate_Change_Form_Enhancement_QR202503.htm

Enhancement to Pay Rate Change Form

Previously, the entry box for the Hours Paid field on the Pay Rate Change form displayed a red border, indicating that this entry was required. If you make a pay rate change in the current pay period you can allocate hours, but since this entry is not required the red border around the entry box no longer displays. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18197

========================================================================

Enhancements to Rehire Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Rehire_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Rehire_Form_Enhancements_QR202503.htm

Enhancements to Rehire Form

The following enhancements now reside on the Rehire form:

[Image: screenshot]

You can use the Manager field to add or update the employee’s manager.

Note: Service providers, worksite managers, and worksite trusted advisors can do the following when working with the Manager field:

Important! Only service providers can enter the user ID of a worksite trusted advisor who they are allowed access.

[Image: screenshot]

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17146 and PD-18630

========================================================================

Enhancement to Reviews Due By Month Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Reviews_Due_By_Month_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/HumanResources/Reviews_Due_By_Month_Report_Enhancement_QR202503.htm

Enhancement to Reviews Due By Month Report

The system now displays the new Variable Salary option as “V - VSalary” in the Reviews Due By Month Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-18677

========================================================================

Enhancement to New Employee Import Process

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/New%20Employee%20Import/New_Employee_Import_Process_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/New Employee Import/New_Employee_Import_Process_Enhancement_QR202503.htm

Enhancement to New Employee Import Process

The system now allows the new Variable Salary option as a valid Pay Method when using the New Employee Import process. When you use the Pay Method field code in an import, the Variable Salary option displays in the downloaded file as “V.”

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRNew Employee Import User Guide.

JIRA # PD-18656

========================================================================

Enhancement to Approval Summary Termination Explanation

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Approval_Summary_Termination_Explanation_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Approval_Summary_Termination_Explanation_Enhancement_QR202503.htm

Enhancement to Approval Summary Termination Explanation

Previously, the system interpreted carriage returns entered in the Termination Explanation field on the Employee Termination form as the end of the explanation and only displayed the first line in the Termination Explanation description on the termination’s Approval Summary.

The system now ignores carriage returns entered in the Termination Explanation field and displays the entire explanation (up to 200 characters) in the termination approval.

Note: You can view a termination explanation in an Approval Summary by selecting a Termination Approval in the Approvals Pending form.

For more information, see the in-product help or PrismHRApprovals Guide.

JIRA # PD-17968

========================================================================

Updates to Backdated Leave Request Feature

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Backdated_Leave_Request_Updates_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Backdated_Leave_Request_Updates_QR202503.htm

Updates to Backdated Leave Request Feature

To ensure that backdated leave requests are processed in a timely manner, the following updates now reside on the system:

[Image: screenshot]

[Image: screenshot]

To view pending backdated leave requests for all employees in the payroll who have backdated leave requests that display on the Backdated Leave Request Processing form, click the yellow indicator or the Outstanding Approval icon. A form now displays the Pending Backdated Leave Requests section, which provides more details. For example:

[Image: screenshot]

Note: Worksite managers who do not have access to an employee due to data entity security can still view that employee on the Approvals Pending form. However, they cannot view that employee on the Backdated Leave Request Processing form.

Note: Note that backdated leave requests only display on the Backdated Leave Request Processing form in the following conditions:

[Image: screenshot]

Note: The notes listed above for the Time Sheet Entry and SuperBatch forms also apply to this Process Payroll form update.

[Image: screenshot]

Note: This enhancement is helpful in determining whether a manual check entry is for a backdated leave request or was entered manually by a user, so you can suppress administrative fees for manual checks created by Backdated Leave Request processing.

For more information, see the in-product help, PrismHR Human Resources User Guide, PrismHR Payroll Administration Guide, or PrismHR Payroll Processing Guide.

JIRA # PD-18354, PD-18355, PD-18356, PD-18357, and PD-18358

========================================================================

Enhancement to Cash Receipts Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Cash_Receipts_Import_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Cash_Receipts_Import_Form_Enhancement_QR202503.htm

Enhancement to Cash Receipts Import Form

Previously, clicking OK in the “File content successfully imported” message after a successful import in the Cash Receipts Import form left the Import Cash Receipts button enabled and the import data still displayed on-screen, which made it appear as if the import did not occur.

To resolve this confusion, now when users click OK in the “File content successfully imported” message the form clears and returns to its original state.

For more information, see the in-product help or PrismHR Accounting User Guide.

JIRA # PD-17945

========================================================================

Enhancement to Confirm Pending Reversal Global Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Confirm_Pending_Reversal_Global_Form_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Confirm_Pending_Reversal_Global_Form_QR202503.htm

Enhancement to Confirm Pending Reversal Global Form

A new link, Download Report, now displays on the Confirm Pending Reversal Global form. For example:

[Image: screenshot]

After selecting Find Employees, you can select the Download Report link to open the displayed information in CSV format.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # WSP-1077

========================================================================

Enhancements to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Data_Import_Tool_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Data_Import_Tool_Enhancements_QR202503.htm

Enhancements to Data Import Tool

The following enhancements now reside on the Data Import Tool:

[Image: screenshot]

You can use this new field to enter a check stub description for the employee’s Scheduled Deduction.

Note: By default, the system populates this field with the deduction code’s description.

[Image: screenshot]

Note: This import template is only available for service providers.

You can use this new field to enter users who have the Payroll Processor (Print/Mail) account management role assigned on the Account tab in the Client Details form. (If you select any other user an error displays, “User <XXX> is not set up to be a Payroll Processor (Print/Mail).”)

Note: See Enhancements to Client Details Form for more details about the new Print/Mail User field.

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-12936, PD-18658, and WSP-1150

========================================================================

Enhancement to Deduction Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Deduction_Codes_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Deduction_Codes_Form_Enhancement_QR202503.htm

Enhancement to Deduction Codes Form

A warning now displays when you try to update the Deduction Type for an existing Deduction Code on the Deduction Codes form. For example, changing Voluntary to Wage Garnishment displays the following warning:

[Image: screenshot]

Note: Note the following that occurs after you click OK and save the record, and the system processes the updated Deduction Code through a complete payroll process:

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # WSP-446

========================================================================

Enhancement to Employee Payroll Vouchers Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Employee_Payroll_Vouchers_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Employee_Payroll_Vouchers_Form_Enhancement_QR202503.htm

Enhancement to Employee Payroll Vouchers Form

A new column, Payroll Number, now displays in the Employee Payroll Vouchers form after entering or selecting an Employee. For example:

[Image: screenshot]

To quickly navigate to a payroll voucher’s details, simply select a link in the Payroll Number column. The Payroll Summary form opens to that selected payroll voucher’s details.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # WSP-1154

========================================================================

Enhancement to Employee Period Pay and Hours Audit Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Employee_Period_Pay_and_Hours_Audit_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Employee_Period_Pay_and_Hours_Audit_Report_Enhancement_QR202503.htm

Enhancement to Employee Period Pay and Hours Audit Report

The system now displays the new Variable Salary option as “VSalary” in the Employee Period Pay and Hours Audit Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18667

========================================================================

Enhancement to Employee Voucher Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Employee_Voucher_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Employee_Voucher_Report_Enhancement_QR202503.htm

Enhancement to Employee Voucher Report

The system now displays the new Variable Salary option as “V - VSalary” in the Employee Voucher Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18668

========================================================================

Enhancement to Fax Back Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Fax_Back_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Fax_Back_Report_Enhancement_QR202503.htm

Enhancement to Fax Back Report

The system now displays the new Variable Salary option as “VSalary” in the Fax Back Report on-screen and .xls report output for those employees assigned this option as their Pay Method. For example:

[Image: screenshot]

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that salary-exempt employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18669

========================================================================

Enhancement to FLSA Classification Analysis Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/FLSA_Classification_Analysis_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/FLSA_Classification_Analysis_Report_Enhancement_QR202503.htm

Enhancement to FLSA Classification Analysis Report

In association with the new Pay Method option, Variable Salary, “Y” now displays in the Salary column in the FLSA Classification Analysis Report on-screen or .xls output for employees assigned this pay method.

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18671

========================================================================

Enhancement to Gross-to-Net Register Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Gross_to_Net_Register_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Gross_to_Net_Register_Report_Enhancement_QR202503.htm

Enhancement to Gross-to-Net Register Report

In association with the new Variable Salary pay method option that you can set on the Employee Details form, the system now recognizes employees assigned this pay method as “Salary” when you generate the Gross-to-Net Register Report.

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18934

========================================================================

Enhancement to Manual Check Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Manual_Check_Entry_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Manual_Check_Entry_Form_Enhancement_QR202503.htm

Enhancement to Manual Check Entry Form

Previously, users could not create a zero pay stub when creating a manual check entry. To resolve this issue, you can now create a zero-dollar, non-negotiable pay stub after completing a manual check entry, which the system records. (You can print the pay stub by accessing the voucher from either the Process Payroll form or the Employee Voucher form.)

Note: This feature is only available for new payrolls, not previously processed payrolls.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # WSP-1055

========================================================================

Enhancements to Pay Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Pay_Codes_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Pay_Codes_Form_Enhancements_QR202503.htm

Enhancements to Pay Codes Form

The following enhancements now reside on the Pay Codes form:

[Image: screenshot]

Note: The Include in Variable Salary Pay field only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can enable the Include in Variable Salary Pay field to include the selected pay code in the employee’s Variable Salary pay.

The Variable Salary pay method accurately tracks the hours that employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

Note: Entering a negative value now displays the following error message:

[Image: screenshot]

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-18446 and PD-18914

========================================================================

Enhancement to Payroll Check Journal Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Check_Journal_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Check_Journal_Report_Enhancement_QR202503.htm

Enhancement to Payroll Check Journal Report

In association with the new Pay Method option, Variable Salary, the system recognizes employees assigned this pay method by displaying “Salaried” in the Payroll Check Journal Report on-screen or .xls output.

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18935

========================================================================

Enhancement to Payroll Control Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Control_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Control_Form_Enhancement_QR202503.htm

Enhancement to Payroll Control Form

A new field, Reason, now resides on the Payroll Control form. For example:

[Image: screenshot]

Note: The Reason field only displays when the Payroll Type is set to Manual.

You can use the Reason field to track the reason why the client is processing manual payrolls.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # WSP-972

========================================================================

Enhancements to Payroll Deduction Custom Export Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Deduction_Custom_Export_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Deduction_Custom_Export_Form_Enhancements_QR202503.htm

Enhancements to Payroll Deduction Custom Export Form

The following enhancements now reside on the Payroll Deduction Custom Export form when you select Essential Staff Care in the Output Format field:

[Image: screenshot]

You can use the new fields to filter the report by benefit group for the Essential Staff Care carrier:

[Image: screenshot]

Enabling the Only include MED, DEN, VIS Offer Types for the listed Benefit Groups field allows you to only include this type of information for the Payroll Number or the pay date range for the Benefit Groups listed in the panel. (If you do not enable this field, the system includes all offer types for the listed Benefit Groups.)

Note: This field setting cannot be saved and if needed, it must be enabled each time you run the report.

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18367, PD-18369, and PD-18455

========================================================================

Enhancement to Payroll History Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_History_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_History_Form_Enhancement_QR202503.htm

Enhancement to Payroll History Form

Previously, users who had Deny access to the Payroll Summary form and Full access to the Payroll History form were able to access the Payroll Summary form from the Payroll History form.

When users are set to Deny access to the Payroll Summary form and Full access to the Payroll History form, they can no longer access the Payroll Summary form by selecting a payroll listed in the Payroll History form.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-17815

========================================================================

Enhancement to Payroll Register Report

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Register_Report_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Register_Report_Enhancement_QR202503.htm

Enhancement to Payroll Register Report

In association with the new Variable Salary pay method option that you can set on the Employee Details form, the system now recognizes employees assigned this pay method as “Salary” when you generate the Payroll Register Report.

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

You can use the Variable Salary option to accurately track the hours that salary-exempt employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-18936

========================================================================

Enhancements to Payroll Reports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Reports_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Payroll_Reports_Form_Enhancements_QR202503.htm

Enhancements to Payroll Reports Form

The following enhancements now reside on the Payroll Reports form:

[Image: screenshot]

Note: The Payroll Reports form is accessible by clicking the Reports icon (

[Image: screenshot]

) in the Payroll Summary form after selecting a Payroll Number.

You can download or view details by doing the following:

[Image: screenshot]

Note: For more information, see Enhancement to Global Payroll Reports Form.

For more information, see the in-product help or PrismHRPayroll Reports guide.

JIRA # PD-17967 and PD-18265

========================================================================

Enhancement to PEO Client Accounting Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/PEO_Client_Accounting_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/PEO_Client_Accounting_Form_Enhancement_QR202503.htm

Enhancement to PEO Client Accounting Form

A new preset code, HRSWKED, is now available on the Lookup Items list when you select the Data field in the Custom Layout panel on the PEO Client Accounting form. For example:

[Image: screenshot]

Selecting the HRSWKED preset code pulls the Hours Worked from the Earning Detail panel on the Billing Voucher Detail form into the PEO Client Accounting file.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-18638

========================================================================

Enhancements to Process Payroll Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Process_Payroll_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Process_Payroll_Form_Enhancements_QR202503.htm

Enhancements to Process Payroll Form

The following enhancements now reside on the Process Payroll form:

This functionality works as follows:

System Level Setting Client Level Setting Behavior
Disabled –Select– No warning
Disabled Enabled Warning functionality triggered
Disabled Disabled No warning
Enabled –Select– Warning functionality triggered
Enabled Enabled Warning functionality triggered
Enabled Disabled No warning

[Image: screenshot]

To quickly identify employees and access their information simply select an Employee ID, which opens the Employee Details form where their data displays.

[Image: screenshot]

Note: The Variable Salary option only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary option accurately tracks the hours that employees actually work. For example, non-profit companies could use this option to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes. (See Enhancements to Employee Details Form.)

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-18320, PD-18650, WSP-1157, and WSP-1158

========================================================================

Security Report Name Change

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Security_Report_Name_Change_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Security_Report_Name_Change_QR202503.htm

Security Report Name Change

To ensure security report naming consistency, the report, warning, and path associated with Security Notifications that users receive during payroll calculations have been renamed Security Changes Report. For example:

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

For more information, see the in-product help, PrismHRPayroll Reports guide, or PrismHR Payroll Processing Guide.

JIRA # PD-17377

========================================================================

Enhancement to SuperBatch Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/SuperBatch_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/SuperBatch_Form_Enhancement_QR202503.htm

Enhancement to SuperBatch Form

Previously, all payrolls that were set to Separate Print/Ship Functions on the Global Configuration form displayed for anyPrint/Mail User on the SuperBatch form.

To help users filter the payrolls they need to print, when a Print/Mail User is assigned to a client who has a payroll that is in the POSTCOMP state (

[Image: screenshot]

) or beyond that user only sees their clients on the SuperBatch form.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # WSP-991

========================================================================

Removal of SuperBatch Legacy

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/SuperBatch_Legacy_Removal_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/SuperBatch_Legacy_Removal_QR202503.htm

Removal of SuperBatch Legacy

SuperBatch Legacy, the original version of SuperBatch, has been removed from the system. Instead, you must use SuperBatch, the enhanced payroll processing hub, which was introduced in 2024.

Note: SuperBatch Legacy will no longer be searchable in PrismHR and you cannot add the SuperBatch Legacy form to any user roles. In addition, SuperBatch Legacy will no longer display in existing user roles or in menus.

For more information about using SuperBatch, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-18061

========================================================================

Enhancement to Unbundled Billing Rules Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Unbundled_Billing_Rules_Import_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Payroll/Unbundled_Billing_Rules_Import_Form_Enhancement_QR202503.htm

Enhancement to Unbundled Billing Rules Import Form

Two new fields, Obsolete and Obsolete Date, now display in the downloadable spreadsheet in columns BD and BE, respectively, on the Unbundled Billing Rules Import form. For example:

[Image: screenshot]

Field Details Description
Obsolete Allowed values: - Y: Yes - y: Yes - YES: Yes - yes: Yes - Yes: Yes - N: No - n: No - NO: No - no: No - No: No Indicate whether the billing rule is Obsolete. (The system reads a blank value as “No.”)

JIRA # PD-18261

========================================================================

Enhancement to ACH Hold Management and ACH Hold Management (Internal Payroll) Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/ACH_Hold_Management_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/ACH_Hold_Management_Form_Enhancement_QR202503.htm

Enhancement to ACH Hold Management and ACH Hold Management (Internal Payroll) Forms

A new button, Delete, now displays on the ACH Hold Management and ACH Hold Management (Internal Payroll) forms, which are available on the Operations|Change menu. For example:

[Image: screenshot]

[Image: screenshot]

Note: The Delete button only displays when the On Hold Status is set to Yes.

Simply click Delete to remove a hold from the system.

After clicking Delete a warning displays:

[Image: screenshot]

Select Yes to remove the hold on the selected journals.

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # WSP-963

========================================================================

Enhancement to ACH Originators Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/ACH_Originators_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/ACH_Originators_Form_Enhancement_QR202503.htm

Enhancement to ACH Originators Form

Three new options, South State/Union Bank of MI, Fifth Third Bank, and Tristate, now display in the Bank Name field on the ACH Originators form when you select the Reverse Wire Transfer option as the Third Party Format. For example:

[Image: screenshot]

Selecting one of these options generates a .csv output file for reverse wire transfers with South State/Union Bank of MI, Fifth Third Bank, or Tristate during the ACH process.

Note: The South State/Union Bank of MI, Fifth Third Bank, and Tristate options are only available for service providers.

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # WSP-1195, WSP-1196, and WSP-1197

========================================================================

Enhancement to ACH Processing Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/ACH_Processing_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/ACH_Processing_Form_Enhancement_QR202503.htm

Enhancement to ACH Processing Form

The Value Date field used in Chase Reverse Wire output, which is downloadable on the ACH Processing form, is now a required field in column 13 with an eight-character date format, YYYYMMDD.

Note: The system retrieves the date information for the Value Date field from the payroll and the associated ACH Originator.

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # WSP-1316

========================================================================

Enhancement to Build State Tax Solution Files Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/Build_State_Tax_Solution_Files_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/Build_State_Tax_Solution_Files_Form_Enhancement_QR202503.htm

Enhancement to Build State Tax Solution Files Form

The system now treats an employee with the new Pay Method of Variable Salary as if it has a Pay Method of Salary in the Build State Tax Solution Files form. (See Enhancements to Employee Details Form.)

JIRA # PD-18724

========================================================================

Enhancement to Favorites Template Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/Favorites_Template_Import_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/Favorites_Template_Import_Form_Enhancement_QR202503.htm

Enhancement to Favorites Template Import Form

Previously, the system displayed process IDs in the Select User Process list (accessible by selecting Process in the Favorites Template Import form) that could not be added to a user role in the User Roles form.

To prevent users from selecting unavailable process IDs, the system only displays process IDs that can be added to a user role in the User Role Maintenance list in the User Roles form.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-18513

========================================================================

Enhancement to Global Payroll Reports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/Global_Payroll_Reports_Form_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/Global_Payroll_Reports_Form_Enhancement_QR202503.htm

Enhancement to Global Payroll Reports Form

You can now add the Payroll Retirement Contributions Report to the Report Name list in the Global Payroll Reports form, so it will print after payroll processing finishes. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-18264

========================================================================

Enhancement to Employee Benefit Rule Override Form Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Employee_Benefit_Performance_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Employee_Benefit_Performance_QR202503.htm

Enhancement to Employee Benefit Rule Override Form Performance

The Employee Benefit Rule Override form has been enhanced to improve the performance of the form.

JIRA # PP-1303

========================================================================

New Pay Groups User Field

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Pay_Groups_User_Field_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Pay_Groups_User_Field_QR202503.htm

New Pay Groups User Field

Clients can now store user-defined fields using the newly added action, User Fields, on the Pay Groups form.

To access User Fields:

  1. Open the Pay Groups form.

  2. Click the Actions icon to display the list of action items available for the form.

  3. Click User Fields to view the custom fields defined by your organization.

JIRA # PP-1782

========================================================================

New Payroll Control User Field

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Payroll_Control_User_Field_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Payroll_Control_User_Field_QR202503.htm

New Payroll Control User Field

Clients can now store user-defined fields using the newly added action, User Fields, on the Payroll Control form.

To access User Fields:

  1. Open the Payroll Control form.

  2. Click the Actions icon to display the list of action items available for the form.

  3. Click User Fields to view the custom fields defined by your organization.

JIRA # PP-1721

========================================================================

Enhancement to Retirement Export Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Retirement_Export_Performance_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Retirement_Export_Performance_QR202503.htm

Enhancement to Retirement Export Form

Improvements have been applied to the Retirement Export form to increase performance and reduce exporting times.

JIRA # PP-1701

========================================================================

Enhancement to SBEA Rebuild Client Federal Tax Register Form Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_SBEA_Rebuild_Performance_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_SBEA_Rebuild_Performance_QR202503.htm

Enhancement to SBEA Rebuild Client Federal Tax Register Form Performance

Improvements have been applied to the SBEA Rebuild Client Federal Tax Register form to improve the loading times and performance of this form.

JIRA # PP-1786

========================================================================

Enhancement to Superbatch Form Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Superbatch_Performance_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Superbatch_Performance_QR202503.htm

Enhancement to Superbatch Form Performance

Improvements have been applied to the Superbatch form to improve loading times while processing all the payrolls available by selecting All Payroll Processors from the Payroll Processor dropdown. In addition, performance of the form has been improved when the feature code ALLOWWTREQLOC is added to a client.

JIRA # PP-1729, PP-1730, PP-1759

========================================================================

Enhancement to SUTA Tax Rebuild Form Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_SUTA_Tax_Performance_R202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_SUTA_Tax_Performance_R202503.htm

Enhancement to SUTA Tax Rebuild Form Performance

Improvements have been applied to the SUTA Tax Liability Report form to improve the performance of the report.

JIRA # PP-1794

========================================================================

Enhancement to Workers Comp Report Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Workers_Comp_Performance_R202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Workers_Comp_Performance_R202503.htm

Enhancement to Workers Comp Report Performance

The Workers Comp Analysis by Client/Class Report form has been enhanced to improve the performance of running the report.

JIRA # PP-1765

========================================================================

Enhancement to the Worksite User Data Security Download Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Worksite_User_Data_Performance_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/PP_Worksite_User_Data_Performance_QR202503.htm

Enhancement to the Worksite User Data Security Download Form

The Worksite User Data Security Download form has been enhanced to improve the performance of the download.

JIRA # PP-1422

========================================================================

Enhancements to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/System/System_Pararmeters_Form_Enhancements_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/System/System_Pararmeters_Form_Enhancements_QR202503.htm

Enhancements to System Parameters Form

The following enhancements now reside on the System Parameters form:

[Image: screenshot]

Selecting the Enable payroll live check calculation warning field displays a warning message during payroll calculation to indicate that the system will create a live check. (This field is helpful in case the client never wants to create a live check during payroll processing.)

Note: The Enable payroll live check calculation warning field is disabled by default at the system level, but can be overridden at the client level.

[Image: screenshot]

When you enable the Require Manual Payroll Reason field (default is disabled), the system sets the payroll Reason field as required on the Payroll Control form for manual payrolls.

[Image: screenshot]

Note: This option is only available for service providers.

Selecting Clear All Backup Account Assignments opens a form where you can clear all backup account assignments regardless of which clients are listed in the import file. For example:

[Image: screenshot]

Clicking Process and then selecting Yes removes all backup account assignments, so they no longer display when you select Backup Assignments on the Account tab in the Client Details form. Use the Data Import Tool to import new backup account assignments.

Important! This process cannot be reverted.

Note: Note the following:

For more information, see the in-product help, PrismHR Payroll Processing Guide, or PrismHRSystem Administration Guide.

JIRA # PD-18346, PD-18353, PD-18503, and WSP-974

========================================================================

Enhancement to Notification Control Panel

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/QR_202503/Work%20Centers/Notification_Control_Panel_Enhancement_QR202503.htm Path: PD/Release-Notes/Enhancements/2025/QR_202503/Work Centers/Notification_Control_Panel_Enhancement_QR202503.htm

Enhancement to Notification Control Panel

You can now set a user’s field-level security for the Start and Stop buttons on the Notification Control Panel using the Field option on the User Roles form. For example, you could hide these buttons to prevent users from starting or stopping the notifications engine during enrollments.

[Image: screenshot]

To set field-level security for the Start and Stop buttons on the Notification Control Panel:

  1. Go to the User Roles form on the System|Change menu.

  2. Enter or select the Role ID. (Note: If the user’s role is set to Inquiry for the Notification Control Panel, you cannot set field-level security even if the field security is set to grant access. If the user’s role is set to Full, you can only access the fields set in the field security settings.)

  3. Select Field for the Notification Control Panel (see screenshot above). The Field Security Maintenance form displays.

  4. Click Add. The Field Security Selection form displays.

  5. To enable field-level security for the Start and Stop buttons, click the following checkboxes:

[Image: screenshot]

  1. Click Accept. The selected fields display in the Field Security Maintenance form.

  2. Select Enable in the Permissions column for each field. The permissions for these fields changes to Disable.

  3. Click Save. The User Roles form re-displays.

  4. Click Save.

For more information about the Notification Control Panel, see the in-product help.

JIRA # PD-18273

========================================================================

Enhancement to Billing Templates Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Billing/Billing_Templates_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Billing/Billing_Templates_Form_Enhancement_R202504.htm

Enhancement to Billing Templates Form

Previously, users could successfully save the Limit or Discount Shelter for an ASO billing Template Type to Yes in the Other Tax Code Billing Options panel on the Billing Templates form.

When you try to save an ASO billing template’s Limit or Discount Shelter setting to Yes the following error message now displays:

[Image: screenshot]

In addition, the system now displays the Limit and Discount Shelter options for FICA and Federal or State Unemployment when setting up ASO billing templates.

For more information, see the in-product help or PrismHRBilling User Guide.

JIRA # PD-17970

========================================================================

Enhancements to Client Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Client/Client_Details_Form_Enhancements_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Client/Client_Details_Form_Enhancements_R202504.htm

Enhancements to Client Details Form

The following enhancements are now available on the Client Details form:

[Image: screenshot]

[Image: screenshot]

[Image: screenshot]

Note: Note: Click OK to continue, then enter the required information mentioned in the option’s warning message.

[Image: screenshot]

Important! The Maximum ACH Amount field is a placeholder for future development. At the time of this release, the field’s functionality is not working.

[Image: screenshot]

Enabling these new fields sends a notification for the client to emails listed in the additional notification emails for Payroll Finalization Notifications on the Control tab and to worksite managers/worksite trusted advisors who have the Payroll Approver H/R Role when the system creates a Miscellaneous Invoice Notification or an Employee Payroll Voucher Reversal Notification.

Note: Note the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-19001, PD-19230, and WSP-1406

========================================================================

Enhancement to PTO Register Types Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Client/PTO_Register_Types_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Client/PTO_Register_Types_Form_Enhancement_R202504.htm

Enhancement to PTO Register Types Form

A new option, First of Quarter, is now available in the Trigger Method field on the PTO Register Types form. For example:

[Image: screenshot]

Selecting the First of Quarter method triggers when the pay period includes the first day of a new quarter for employees enrolled in a PTO Benefit Plan that has a calculation basis of Flat Amount. For example, if the first pay date in Q4 occurs on 10/7/2024, PTO accrual occurs during that payroll. (Quarters are typically calendar quarters: Q1 = January - March, Q2 = April - June, Q3 = July - September, and Q4 = October - December.)

Note: Note the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18980 and PD-18981

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Documentation/New_Task_Sheets_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Documentation/New_Task_Sheets_R202504.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheet was updated:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Approval Policies and Global Approval Policies Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Appr_Policies_and_Global_Enh_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Appr_Policies_and_Global_Enh_R202504.htm

Enhancement to Approval Policies and Global Approval Policies Forms

A new option, ACH Maximum, now displays in the Approval Type field on the Approval Policies and Global Approval Policies forms. For example:

[Image: screenshot]

[Image: screenshot]

Important! The ACH Maximum option is a placeholder for future development. At the time of this release, the option’s functionality is not working.

For more information, see the in-product help, PrismHRApprovals Guide, or PrismHRHuman Resources User Guide.

JIRA # WSP-1408

========================================================================

Enhancement to Employee Details and Employee Termination Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Employee_Details_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Employee_Details_Form_Enhancement_R202504.htm

Enhancement to Employee Details and Employee Termination Forms

You can now enter a Termination Explanation on the Other tab in the Employee Details form or in the Employee Termination form that exceeds 200 characters when you enable the new TERMEXPLAIN custom feature code on the System Parameters form. (Previously, an error message displayed after entering more than 200 characters and clicking Save, “Termination Explanation is <xxx> characters. Termination Explanation can not exceed 200 characters.”)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-19241

========================================================================

Enhancement to Portal New Hire Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Portal_New_Hire_Import_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Portal_New_Hire_Import_Form_Enhancement_R202504.htm

Enhancement to Portal New Hire Import Form

The system now imports the Variable Salary option as a valid Pay Method during imports in the Portal New Hire Import form. When you use the Pay Method field code in an import, the Variable Salary option displays in the downloaded spreadsheet as “V.”

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

The Variable Salary pay method accurately tracks the hours that employees actually work. For example, non-profit companies could use this pay method to track the work hours of their employees who are paid a standard salaried amount, so they can use these hours and their allocations for grant purposes.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18657

========================================================================

Enhancement to Status Type History Adjustment Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Status_Type_History_Adjustment_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/HumanResources/Status_Type_History_Adjustment_Form_Enhancement_R202504.htm

Enhancement to Status Type History Adjustment Form

You can now perform an alternate global search for status type changes, which display on the Status Type History Adjustment form, by entering the following terms in the Search box:

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # PD-18793

========================================================================

Enhancement to New Employee Import Process

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/New%20Employee%20Import/New_Employee_Import_Process_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/New Employee Import/New_Employee_Import_Process_Enhancement_R202504.htm

Enhancement to New Employee Import Process

The system now recognizes new employees who have all zero Social Security Numbers (000-00-0000) during imports using the New Employee Import process when the ALLOWZEROSSSNS custom feature code is enabled.

For more information about the New Employee Import process, see the in-product help or PrismHRNew Employee Import User Guide.

JIRA # WSP-1539

========================================================================

Enhancement to Cash Receipts Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Cash_Receipts_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Cash_Receipts_Form_Enhancement_R202504.htm

Enhancement to Cash Receipts Form

Previously, a warning message displayed in the Cash Receipts form when users entered several deposits for the same invoice. This message stated that the invoice number had already been used. (Users were required to click OK to continue and then manually enter the invoice number.) Users can now select duplicate invoice numbers, so this warning message no longer displays.

In addition, when users tried to enter an additional row by selecting the invoice number from the Outstanding Invoices list for the same invoice number, the system removed the cash receipt row that was entered. Users can now select an invoice number in this scenario without deleting the row.

For more information, see the in-product help or PrismHRAccounting User Guide.

JIRA # PD-19118

========================================================================

Corresponding SFTP ACH File Now Written for SFTP Directory

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Corresponding_SFTP_ACH_File_Now_Written_for%20SFTP_Directory_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Corresponding_SFTP_ACH_File_Now_Written_for SFTP_Directory_R202504.htm

Corresponding SFTP ACH File Now Written for SFTP Directory

After the system writes an ACH file to the SFTP Directory during multiple file ACH processing, it creates a new corresponding SFTP ACH file with a suffix, _STFP_COMPLETE, which it writes to the STFP Directory to ensure that the ACH file is complete.

Note: During multiple file ACH processing the system now displays “STFP complete,” indicating this process runs as expected for multiple ACH files.

JIRA # PD-18921

========================================================================

Enhancements to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Data_Import_Tool_Enhancements_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Data_Import_Tool_Enhancements_R202504.htm

Enhancements to Data Import Tool

The following enhancements now reside in the Data Import Tool:

[Image: screenshot]

Note: This feature is only available for service providers.

When you enable the Keep existing data for fields not in the import file field, optional fields in the Worksite Locations import template will keep their existing data during imports. (If you do not enable this field, the system overwrites optional fields with no data during imports.)

Important! When you enable Keep existing data for fields not in the import file in the Worksite Locations import template, the Address entry validation dialog and the File Content tab display blank information for fields not included in the import file, but the import keeps the original information entered on the Worksite Locations form.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-19069 and PD-19194

========================================================================

Enhancement to Employee Payroll Voucher Reversal Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Employee_Payroll_Voucher_Revsersal_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Employee_Payroll_Voucher_Revsersal_Form_Enhancement_R202504.htm

Enhancement to Employee Payroll Voucher Reversal Form

After an Employee Payroll Voucher Reversal is complete and the Client Control for Payroll Finalization Notification is set to Email, the system now notifies the user at the email address indicated in the Payroll Finalization email and for worksite managers/worksite trusted advisors with the Payroll Approver H/R Role that the reversal is complete and displays the invoice from the reversal.

Note: The system sends the Payroll Finalization email to worksite managers and worksite trusted advisors designated with the Payroll Approver Human Resource Role on the Users form, including any email addresses listed in the Additional Notification Emails panel on the Control tab in the Client Details form (the Additional Notification Emails panel displays when you select the Email option).

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-16979 and PD-19193

========================================================================

Enhancement to Miscellaneous Invoice Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Miscellaneous_Invoice_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Miscellaneous_Invoice_Form_Enhancement_R202504.htm

Enhancement to Miscellaneous Invoice Form

After you create a Miscellaneous Invoice and the Client Control for Payroll Finalization Notification is set to Email, the system now notifies the user at the email address indicated in the Payroll Finalization email that the invoice was created.

Note: The system sends the Payroll Finalization email to worksite managers and worksite trusted advisors designated with the Payroll Approver Human Resource Role on the Users form, including any email addresses listed in the Additional Notification Emails panel on the Control tab in the Client Details form (the Additional Notification Emails panel displays when you select the Email option).

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-14310

========================================================================

Enhancement to Payroll Approval Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Payroll_Approval_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Payroll_Approval_Form_Enhancement_R202504.htm

Enhancement to Payroll Approval Form

A new option, Approval Payroll Reports, is now available in the View Report/Analytic field on the Payroll Approval form. For example:

[Image: screenshot]

Selecting Approval Payroll Reports opens the new Approval Payroll Reports form, which lists all the available payroll approval reports and downloadable files. Click the Open File icon (

[Image: screenshot]

) in the Job column to view the report or downloadable file listed in the Report Title column. For example:

[Image: screenshot]

Note: Moving your cursor over the Open File icon displays “Open File.”

For example, clicking the Open File icon in the Gross-To-Net Report row opens that report:

[Image: screenshot]

For more information, see the in-product help, PrismHR Payroll Processing Guide, or PrismHRPayroll Reports guide.

JIRA # PD-18862, PD-18863, PD-18864, PD-18866, PD-18867, and PD-18874

========================================================================

Enhancement to Payroll Reports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Payroll_Reports_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Payroll_Reports_Form_Enhancement_R202504.htm

Enhancement to Payroll Reports Form

Third-party checks now display on the Payroll Reports form only when the user’s Human Resource Role on the Users form is set to Payroll - Print Garnishment Checks. (Previously, third-party checks displayed when the user’s Human Resource Role was set to Payroll - Print Checks.)

Note: The Payroll Reports form is accessible by clicking the Reports icon (

[Image: screenshot]

) in the Payroll Summary form after selecting a Payroll Number.

For more information, see the in-product help, PrismHRPayroll Reports guide, or PrismHR Third Party Check Processing guide.

JIRA # PD-19188

========================================================================

Enhancement to PEO Client Accounting Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/PEO_Client_Accounting_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/PEO_Client_Accounting_Form_Enhancement_R202504.htm

Enhancement to PEO Client Accounting Form

A new Pay Period End Date preset code, PPENDDATE, now displays when you select Data in the Custom Layout panel on the PEO Client Accounting form. For example:

[Image: screenshot]

When you select Data and then select the PPENDDATE preset code from the PEO Client Accounting Custom Codes list that displays, the General Ledger (GL) file displays the Pay Period End Date for that payroll.

Note: If there are multiple Pay Period End Dates for a payroll, the PPENDDATE preset code displays the earliest Pay Period End Date for that payroll.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-17917

========================================================================

Enhancement to Summary Time Sheet Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Summary_Time_Sheet_Entry_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/Payroll/Summary_Time_Sheet_Entry_Form_Enhancement_R202504.htm

Enhancement to Summary Time Sheet Entry Form

The system now displays employees assigned the Variable Salary option as their Pay Method in the Employee Details form as “salaried” employees in summary timesheets. This assignment is indicated by displaying a green dot in the Salary column in summary timesheets.

Note: The Variable Salary option in the Pay Method field on the Employee Details form only displays if the VARSALMETHOD custom feature code is enabled on the System Parameters form. (Custom feature codes are only available for service providers.)

In addition, if you enter time in a pay code that is not the default pay code on the Summary Time Sheet form for variable salaried exempt employees who are also FLSA Exempt a message displays, “These hours will affect the salary amount. Should the standard hours in column <number> be reduced by <number> hours?” Select Yes to reduce the default hours.

Note: If you change the default hours, the green dot changes to an orange dot. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHR Payroll Processing Guide.

JIRA # PD-18967

========================================================================

Enhancement to Message Templates Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/System/Message_Templates_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/System/Message_Templates_Form_Enhancement_R202504.htm

Enhancement to Message Templates Form

To enable a standard message notification to accompany your Maximum ACH Approval requests, a new message template, ACHMAXAPPROVAL, is now available in the Message Templates form. For example:

[Image: screenshot]

Important! The ACHMAXAPPROVAL message template is a placeholder for future development. At the time of this release, the template’s functionality is not working.

For information about configuring message templates, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-1440

========================================================================

Enhancement to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/System/System_Parameters_Form_Enhancement_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/System/System_Parameters_Form_Enhancement_R202504.htm

Enhancement to System Parameters Form

A new field, Disable Marketplace Icon for Service Providers, now displays on the System Parameters form. For example:

[Image: screenshot]

When you enable the Disable Marketplace Icon for Service Providers field (disabled by default), the Marketplace link on the PrismHR menu bar will not display for service providers.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-19250

========================================================================

Enhancements to Users Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202504/System/Users_Form_Enhancements_R202504.htm Path: PD/Release-Notes/Enhancements/2025/R_202504/System/Users_Form_Enhancements_R202504.htm

Enhancements to Users Form

The following enhancements are now available on the Users form:

[Image: screenshot]

Previously, if the H/R Role for a worksite manager or worksite trusted advisor was set to Payroll - Prints Checks and that user had access to the Payroll Reports form, they could print both regular paychecks and garnishment paychecks.

To prevent worksite managers and worksite trusted advisors from printing regular paychecks and only allow them to print garnishment paychecks, you can now set their role to Payroll - Print Garnishment Checks. In association with this update, those users only assigned the Payroll - Prints Checks H/R Role can no longer print garnishment checks.

Note: After setting the Payroll - Print Garnishment Checks role assignment, it displays when you open the Payroll Reports form, which is only accessible from the Payroll Summary form or by selecting the Recent Payrolls view on the Enhanced Dashboard.

[Image: screenshot]

Important! The Billing Representative option is a placeholder for future development. At the time of this release, the option’s functionality is not working.

The Billing Representative is the user who can approve ACH Billing threshold approvals for global-level and client-level approval policies.

Users can set the Billing Representative Account Management Role as follows:

For information, see the in-product help, PrismHR Human Resources User Guide, or PrismHR System Administration Guide.

JIRA # PD-18918 and WSP-1407

========================================================================

Enhancement to Client Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Client/Client_Details_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Client/Client_Details_Form_Enhancement_R202505.htm

Enhancement to Client Details Form

A new field, Maximum ACH Amount, is now available on the Control tab in the Client Details form. For example:

[Image: screenshot]

Note: The Maximum ACH Amount field is only available for service providers.

You can enter the maximum allowable ACH amount in the Maximum ACH Amount field to enforce a threshold amount requiring ACH approval.

Note: You can only enter positive numeric values in this field, which are limited to two decimal places. If you enter more than two decimal places, the system truncates them. For example, the system truncates 5000.7890 to 5000.78.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-1406

========================================================================

Increased Range for Misc G/L EEM Wildcards

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Client/Increased_Range_for_Misc_GL_EEM_Wildcards_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Client/Increased_Range_for_Misc_GL_EEM_Wildcards_R202505.htm

Increased Range for Misc G/L EEM Wildcards

The system now accepts an increased range of 01-99 Misc G/L EEM wildcards used with PEO Client Accounting and Regeneration on the following forms:

Note: Previously, the system only allowed a range of 01-09 Misc G/L EEM wildcards.

For example, you can use up to EEMLC99 wildcards in the Misc GL panel on the Worksite Locations form:

[Image: screenshot]

For more information about using wildcards for PEO Client Accounting, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-18929, PD-18930, PD-18931, PD-18932, and PD-18933

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Documentation/New_Task_Sheets_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Documentation/New_Task_Sheets_R202505.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheets were updated:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Transfer Employee to New Client Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Employer%20Administration/Transfer_EE_NewClient_Enh_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Employer Administration/Transfer_EE_NewClient_Enh_R202505.htm

Enhancement to Transfer Employee to New Client Form

A new field, Term Reason Code, now displays in the Transfer Employee to New Client form when you enable Terminate Employee in Original Client. For example:

[Image: screenshot]

You can use this field to select a valid termination reason code (only those codes with “Termination” included in their Valid Actions on the Employee Termination form display) for the original client when transferring and terminating an employee in one action.

Note: The system displays the default value for the Term Reason Code based on the Transfer Term Reason Code selection in the System Parameters form.

For more information, see the in-product help or PrismHREmployer Administration Guide.

JIRA # WSP-1522

========================================================================

Enhancement to Approval Policies and Global Approval Policies Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Appr_Policies_and_Global_Enh_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Appr_Policies_and_Global_Enh_R202505.htm

Enhancement to Approval Policies and Global Approval Policies Forms

A new option, ACH Maximum, is now available in the Approval Type field on the Approval Policies and Global Approval Policies forms. For example:

[Image: screenshot]

[Image: screenshot]

Note: The ACH Maximum option is only available for service providers.

You can use the new ACH Maximum option to create or update an ACH Maximum Approval policy at the client or global level.

Note: Service providers who have Inquiry access to the Approval Policies and Global Approval Policies forms can view existing ACH Maximum Approval policies in read-only format and cannot make updates to the policy setup.

For more information, see the in-product help, PrismHRApprovals Guide, or PrismHRHuman Resources User Guide.

JIRA # WSP-1408

========================================================================

Enhancement to Approvals Pending Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Approvals_Pending_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Approvals_Pending_Form_Enhancement_R202505.htm

Enhancement to Approvals Pending Form

You can now approve or deny approvals for the Maximum ACH Approval Policy, whose approvals display on the Approvals Pending form.

Note: The Maximum ACH Approval Policy is only available for service providers.

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # WSP-1411

========================================================================

Enhancement to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Employee_Fields_Import_Form_Enhancement_R_202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Employee_Fields_Import_Form_Enhancement_R_202505.htm

Enhancement to Employee Fields Import Form

A new field, Termination Reason Code, is now available to use during imports on the Employee Fields Import form, which is available on the Operations|Action menu. For example:

[Image: screenshot]

You can use the Termination Reason Code field to import the Termination Reason Code in the Employee Work record to update an employee’s termination reason.

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # WSP-1524

========================================================================

Enhancement to Find Changes to an Employee Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Find_Changes_to_an_Employee_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/HumanResources/Find_Changes_to_an_Employee_Form_Enhancement_R202505.htm

Enhancement to Find Changes to an Employee Form

Previously, the system was not returning audits on file without an associated Company ID.

To associate the Employee ID relationship with the audits, the Start Date field in the Find Changes to an Employee form is now a required field. For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRHuman Resources Reports Guide.

JIRA # RRT-6272

========================================================================

Enhancement to Bank Accounts Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Bank_Accounts_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Bank_Accounts_Form_Enhancement_R202505.htm

Enhancement to Bank Accounts Form

To prevent clients from posting a same-day payroll after the defined time/pay date, you can use the new custom feature code, SAMEDAYSTOP, at the global level, in conjunction with the Same Day Processing field in the Bank Accounts form, so the system executes appropriate same-day handling. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

When users attempt to finalize a same-day payroll after the defined time/pay date, the following payroll finalization error message displays when the SAMEDAYSTOP custom feature code is enabled at the global level, “Payroll posting after the Same Day Processing cutoff is prohibited. Correct the pay date to continue.”

For more information, see the in-product help, PrismHRPayroll Setup Guide, or PrismHR System Administration Guide.

JIRA # WSP-1442

========================================================================

Enhancement to Pay Import Definition Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Pay_Import_Definition_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Pay_Import_Definition_Form_Enhancement_R202505.htm

Enhancement to Pay Import Definition Form

A new option, Clients Assigned To, now displays on the Actions menu in the Pay Import Definition form. Selecting this option displays the Clients Assigned to Pay Import Definition form for the selected Definition ID. For example:

[Image: screenshot]

Note: If you do not select a Definition ID in the Pay Import Definition form and then select the Clients Assigned To option an error message displays, “You must enter a Definition ID first.” Click OK to continue.

The Clients Assigned to Pay Import Definition form displays all active, pending, inactive, terminated, and client-canceling clients assigned to the selected pay import definition ID.

Note: You can filter the client list by selecting an option from the Status field. In addition, only the clients you are allowed to view will display.

For more information, see the in-product help or PrismHRPayroll Setup Guide.

JIRA # PD-10616

========================================================================

Enhancements to Process Payroll and SuperBatch Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Process_Payroll_and_SuperBatch_Forms_Enhancements_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Process_Payroll_and_SuperBatch_Forms_Enhancements_R202505.htm

Enhancements to Process Payroll and SuperBatch Forms

The following enhancements now reside on the Process Payroll and SuperBatchforms:

[Image: screenshot]

The list of errors does not display. Instead, a warning message displays, which you can download to an Excel spreadsheet by clicking the Errors and Warnings Download icon (

[Image: screenshot]

).

[Image: screenshot]

[Image: screenshot]

Selecting Payroll Variance Analysis opens a dashboard where you can review relevant payroll information and compare two payrolls on a single dashboard to simplify the review process. For example:

[Image: screenshot]

Note: When you select a category and view individual employees, select the Voucher link to display the employee’s Variance Voucher, which shows the difference between the finalized and initialized payroll. You can also select the Detail link to display a file audit of the change to the employee’s payroll.

Also, you can download this dashboard by selecting Download Variance Detail. Clients can select which variance percentage displays as a warning on this dashboard using the Payroll Variance Percentage Warning field.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-18228 and PD-19242

========================================================================

Enhancement to Process Payroll Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Process_Payroll_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/Payroll/Process_Payroll_Form_Enhancement_R202505.htm

Enhancement to Process Payroll Form

The Restartable Payroll and Legacy Payroll features now prevent submitted payrolls (those whose status is set to INITPEND), that exceed a set ACH amount, from processing until they are approved by a Billing Representative. These submitted payrolls are those where the payroll processor clicks Yes when the “You cannot make any changes once you submit payroll for processing. Are you sure you want to submit?” message displays. (Note that this message does not display when payrolls are submitted in SuperBatch.)

Note: This enhancement is only available for service providers. In addition, existing Payroll Calculation Maximum check approval policies and Worksite approval steps still function as expected in conjunction with the ACH Maximum Approval Policy.

The following preconditions must be met to enforce a threshold amount requiring ACH approval from Billing Representatives:

Note: For more information about the Maximum ACH Amount field, see Enhancement to Client Details Form.

Note: Note the following that occurs when the system triggers Maximum ACH Approval for a submitted payroll:

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # WSP-1409 and WSP-1410

========================================================================

Enhancement to Message Templates Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/System/Message_Templates_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/System/Message_Templates_Form_Enhancement_R202505.htm

Enhancement to Message Templates Form

To enable a standard message notification to accompany your Maximum ACH Approval requests, a new message template, ACHMAXAPPROVAL, is now available in the Message Templates form. For example:

[Image: screenshot]

Note: The ACHMAXAPPROVAL message template is only available for service providers.

The message template can include the following substitution variables:

To use the new message template, select ACH Maximum Approval in the Template Type field on the Email Services form. For example:

[Image: screenshot]

Note: To access this form, select Email Services on the Actions menu in the System Parameters form.

For information about configuring message templates, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-1440

========================================================================

Enhancement to Delete Unused Employee Form Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Delete_Unused_Boost_R05.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Delete_Unused_Boost_R05.htm

Enhancement to Delete Unused Employee Form Performance

The Delete Unused Employee form has been enhanced to improve the performance of the form.

JIRA # PP-1835

========================================================================

Enhancement to Payroll Variance Form Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Payroll_Variance_Boost_R05.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Payroll_Variance_Boost_R05.htm

Enhancement to Payroll Variance Form Performance

The Payroll Variance form has been enhanced to improve the performance of the form.

JIRA # PP-1763

========================================================================

New Payroll Variance Analysis Dashboard

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Payroll_Variance_R05.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Payroll_Variance_R05.htm

New Payroll Variance Analysis Dashboard

The Payroll Variance Analysis dashboard is now available. Using this dashboard, employees can review relevant payroll information and compare two payrolls on a single dashboard to simplify the review process.

[Image: screenshot]

When the Payroll Variance Analysis dashboard is displayed, current payrolls in Calculated status display as tabs. Select a calculated payroll to compare it to payrolls in Finalized status using the Compare to Payroll field.

After selecting the two payrolls to compare, statistics for each payroll and the variance between them displays in the first section of the dashboard. In addition, a second section of the dashboard displays changes in employee records between the two payrolls, such as new hires, pay rate changes, and employment status changes. Select any category to display individual employees with a change between the two payrolls and the resulting variance in payroll totals.

Note: Note: When you select a category and view individual employees, select the Voucher link to display the employee’s Variance Voucher, which shows the difference between the finalized and initialized payroll. You can also select the Detail link to display a file audit of the change to the employee’s payroll.

This dashboard can also be downloaded by selecting Download Variance Detail. Clients can select what variance percentage displays as a warning on this dashboard using the Payroll Variance Percentage Warning field.

JIRA # PP-1550

========================================================================

Select Previous Quarters on Tax Register Audit Inquiry

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Select_Previous_Quarters_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/System/PP_Select_Previous_Quarters_R202505.htm

Select Previous Quarters on Tax Register Audit Inquiry

Service providers can now review tax amounts in registers for previous quarters using the Tax Register Audit Inquiry form. Select a quarter in the Audit Year and Quarter field to display the audit inquiry for that quarter.

Note: Note: Audit results for the current year and quarter are ordinarily built each day. To apply corrections to registers made since the last daily audit, select Refresh Audit. The audit inquiry process is restarted, and the user can navigate to other forms and perform other tasks while the rebuild finishes.

JIRA # PP-1860

========================================================================

Enhancement to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/System/System_Parameters_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/System/System_Parameters_Form_Enhancement_R202505.htm

Enhancement to System Parameters Form

A new custom feature code, BNKACCTCUTOFFENFORCE, is now available in the Custom Feature Codes column. Enabling this feature code sets a cutoff time at the Bank Account level to override the system-level cutoff time configured in the Same Day Check Cut Off field on the System Parameters form. For example:

[Image: screenshot]

Note: Note the following:

For more information, see the in-product help, PrismHR Payroll Processing Guide, PrismHR System Administration Guide, or PrismHRClient Administration Guide.

JIRA # WSP-1449

========================================================================

Enhancement to Users Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202505/System/Users_Form_Enhancement_R202505.htm Path: PD/Release-Notes/Enhancements/2025/R_202505/System/Users_Form_Enhancement_R202505.htm

Enhancement to Users Form

A new Account Management Role, Billing Representative, is now available on the Users form. For example:

[Image: screenshot]

The Billing Representative is the user who can approve ACH Billing threshold approvals for global-level and client-level approval policies.

Users can set the Billing Representative Account Management Role as follows:

For information, see the in-product help or PrismHR System Administration Guide.

JIRA # WSP-1407

========================================================================

Purge Clients Form Replaced

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Client/Purge_Clients_Form_Replaced_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Client/Purge_Clients_Form_Replaced_R202506.htm

Purge Clients Form Replaced

A new form, Inactive Data Deletion, has replaced the Purge Clients form. This enhanced form lets you delete customer data for clients who have been inactive for a certain number of years. For example:

[Image: screenshot]

The Inactive Data Deletion form consists of two panels:

Note: Note the following:

To delete files for an inactive client:

  1. In the Years of Inactivity field, select the minimum number of years a client must be inactive to display. The clients matching this criteria display.

  2. Select the clients to delete in the Clients table. (Click Client ID to select all clients that display.)

  3. Select Rebuild Employer Registers to allow employee voucher data to be removed from the tax registers. Disable this field to prevent employee voucher data from being removed.

  4. Once all settings have been verified, click Delete Client Data. A warning displays, “Permanently delete all data for the <number> selected clients?” Confirm the action to remove data for the displayed clients by clicking Yes. (Clicking No returns to the form.)

Note: This action cannot be undone.

  1. After a deletion is complete, click a link in the Clients Deleted column in the History panel to download a report of all clients removed from the system.

To search for data deletions within a date range:

  1. Open the History panel by clicking the plus sign ( [Image: screenshot] ).

  2. Enter or select the From and To date range. The system adjusts the display of data deletions to match the criteria.

Note: Note the following:

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-19129, PD-19130, PD-19132, PD-19137, PD-19138, PD-19139, and PD-19564

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Documentation/New_Task_Sheets_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Documentation/New_Task_Sheets_R202506.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guides) to display a list of the most current task sheets. For example:

[Image: screenshot]

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Data_Import_Tool_Enhancement_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Data_Import_Tool_Enhancement_R202506.htm

Enhancement to Data Import Tool

The Data Import Tool on the Operations|Import Processing menu has been enhanced, so you can now import property for the employee details record using the new Employee Property import template. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

After selecting the Employee Property import template, the following message displays: “Employee Property imported through this process will add to existing records. Updates to existing employee property must be updated manually on the Employee Property form.” Click OK to continue.

To import employee property, select Employee Property from the Import Template menu, and then click Find File to upload the file.

Note: Note the following when using the Employee Property import template:

For more information, see the in-product help, PrismHRHuman Resources User Guide, PrismHRPayroll Administration Guide, PrismHRPayroll Setup Guide, or the PrismHRPayroll Overrides Guide.

JIRA # PD-18717

========================================================================

Enhancement to Payroll Validation Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Payroll_Validation_Report_Form_Enhancement_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Payroll_Validation_Report_Form_Enhancement_R202506.htm

Enhancement to Payroll Validation Report Form

When running the Payroll Validation Report on a payroll, the system now sends a notification if a time sheet entry contains hours/units greater than 0 and a 0.0000 unit rate, and then pays $0.00 for the time sheet entry. In this scenario, the following message displays: “Warning: Employee <employee name> (<employee id>) had 8.00 time sheet detail hours of REG pay at unit rate of $0.0000 resulting in $0.00 paid. Processing continued.” For example:

[Image: screenshot]

For more information, see the in-product help, PrismHRPayroll Administration Guide, or PrismHRPayroll Reports Guide.

JIRA # WSP-1878

========================================================================

Enhancement to Payroll Voucher Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Payroll_Voucher_Form_Enhancement_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Payroll_Voucher_Form_Enhancement_R202506.htm

Enhancement to Payroll Voucher Form

A new field, Confirm Pending Reversal, now resides on the Banking tab in the Payroll Voucher form. For example:

[Image: screenshot]

The Confirm Pending Reversal field clearly identifies the state of the payroll voucher reversal as Pending, Successful, or Unsuccessful:

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # WSP-1832

========================================================================

Enhancement to Process Payroll and SuperBatch Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Process_Payroll_and_SuperBatch_Forms_Enhancements_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Process_Payroll_and_SuperBatch_Forms_Enhancements_R202506.htm

Enhancement to Process Payroll and SuperBatch Forms

A new calculation warning now displays on the Process Payroll and SuperBatch forms when a timesheet entry contains hours greater than zero (0) and a 0.0000 unit rate, resulting in $0.00 being paid for the time sheet entry. For example:

[Image: screenshot]

Note: Note the following:

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # WSP-1691

========================================================================

Enhancement to Redirect Direct Deposit Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Redirect_Direct_Deposit_Form_Enhancement_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Redirect_Direct_Deposit_Form_Enhancement_R202506.htm

Enhancement to Redirect Direct Deposit Form

A new field, Redirect Deposit Date, is now available on the Redirect Direct Deposit form. For example:

[Image: screenshot]

You must enter or select a date in the Redirect Deposit Date field to accurately date Redirect Direct Deposit vouchers and ACH Journals. (Clicking in this field automatically defaults to the current date.)

In addition, when you update the Send to Account field to initiate a redirect of any existing deposits in the voucher and you save this information, the system now uses the date from the Redirect Deposit Date field for creating both the adjustment vouchers and ACH Journal entries.

In association with this enhancement, the existing functionality that prompted users with a message after clicking Save when the original voucher date occurred in the future, “The pay date for the deposit was <date>. Do you want to use that date instead of today’s date on the check?,” no longer displays. Instead, the system now prompts you to select the date prior to clicking Save. (This functionality is the same for vouchers with original pay dates in the past, present, or future.)

Note: Note the following when working in the Redirect Deposit Date field:

For more information, see the in-product help or PrismHRPayroll Adjustment Processing Guide.

JIRA # WSP-1964 and PD-1965

========================================================================

Enhancement to Reprint Payroll Checks and Employee Payroll Vouchers Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Reprint_Payroll_Checks_Form_Enhancement_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/Payroll/Reprint_Payroll_Checks_Form_Enhancement_R202506.htm

Enhancement to Reprint Payroll Checks and Employee Payroll Vouchers Forms

Service providers, worksite managers, and worksite trusted advisors must now have Full access to the Reprint Payroll Checks and Employee Payroll Vouchers forms to use the Reprint Payroll Checks link and the question mark (

[Image: screenshot]

) on the Payroll Reports form, and the Reprint option on the Employee Payroll Vouchers form, to reprint payroll checks or payroll vouchers, respectively.

To set up a user’s access for these forms, access the User Roles form and set the following process IDs to Full:

[Image: screenshot]

For example, if a user has Full access to the Reprint Payroll Checks form, the Reprint Payroll Checks link and the question mark (

[Image: screenshot]

) are enabled:

[Image: screenshot]

Note: Note the following:

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-18919

========================================================================

Enhancement to Employer Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Employer_Details_Enhance_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Employer_Details_Enhance_R202506.htm

Enhancement to Employer Details Form

The Employer Details form has been enhanced to improve performance. The Initialization History section now displays events from the past year, and the Local Tax Identifiers section now includes pagination.

JIRA # PP-1851

========================================================================

Enhancement to Employee Fields Import

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Performance_EmployeeFieldsImport_06.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Performance_EmployeeFieldsImport_06.htm

Enhancement to Employee Fields Import

The Employee Fields Import process has been enhanced to improve performance, especially for clients with a large number of employee records.

JIRA # PP-1864

========================================================================

Enhancement to Employee Status Type History Adjustment Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Performance_ESTH_06.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Performance_ESTH_06.htm

Enhancement to Employee Status Type History Adjustment Performance

The Employee Status Type History Adjustment form has been enhanced to improve the performance of the form, especially for clients with a large number of employee records.

JIRA # PP-1872

========================================================================

Enhancement to Superbatch Form Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Superbatch_Performance_Shipping_R202506.htm Path: PD/Release-Notes/Enhancements/2025/R_202506/System/PP_Superbatch_Performance_Shipping_R202506.htm

Enhancement to Superbatch Form Performance

The Superbatch form has been enhanced to improve the performance of the form, especially for printing and shipping payrolls.

JIRA # PP-1899

========================================================================

Enhancement to Projects Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/Client/Projects_Form_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/Client/Projects_Form_Enhancement_R202507.htm

Enhancement to Projects Form

The Project G/L Segments have been expanded on the Projects form, so you can now add up to three codes per project. For example:

[Image: screenshot]

You can use G/L Segment 1, 2, and 3 for internal/employer accounting using wild cards EEPR, EEPR2, and EEPR3.

Note: Only G/L Segment 1 is available for ASO Client Accounting using wild card EEPR.

For more information about this enhancement, see the in‑product help or PrismHRClient Administration User Guide.

JIRA # PD-14509

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/Documentation/New_Task_Sheets_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/Documentation/New_Task_Sheets_R202507.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following existing task sheet was updated:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancements to Approval Policies and Global Approval Policies Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Appr_Policies_and_Global_Enh_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Appr_Policies_and_Global_Enh_R202507.htm

Enhancements to Approval Policies and Global Approval Policies Forms

The following enhancements now reside on the Approval Policies and Global Approval Policies forms:

[Image: screenshot]

[Image: screenshot]

You can use the new Direct Deposit Change option to require approval at the client or global level to store direct deposit information in the employee details record.

Important! There must be a client-level or global-level approval policy in place to use this feature. (Without an approval policy, the system immediately records any changes and applies them to the employee record, which is the current method.) In addition, the approval policy only applies when an employee changes, adds, or removes the Transit Number or Account Number in the direct deposit information.

When an approval policy is defined for a client using the Direct Deposit Change option and an employee, worksite manager, or worksite trusted advisor submits a new or updated direct deposit or deletes a direct deposit, the system sets the update to Pending status and an approval is required. (After approval, the direct deposit follows the regular prenote process, if one is in place.) However, if a service provider makes an update, the change does not go through an approval process and is immediately applied to the employee record.

Note: The approval is submitted either from an employee making an update in Employee Portal or from a worksite manager or worksite trusted advisor making an update in Employee Portal or in the Prism Core application.

When an approval is pending and a worksite manager or worksite trusted advisor tries to make a change, the following occurs on the Deposit tab in the Employee Details form:

[Image: screenshot]

[Image: screenshot]

You can set the Direct Deposit Approver A/M Role for global-level and client-level approval policies, so the user with this role can approve updates to direct deposits.

For more information, see the in-product help, PrismHRApprovals Guide, or PrismHRHuman Resources User Guide.

JIRA # PD-19669, PD-19670, PD-19674, PD-19678, and PD-19679

========================================================================

Enhancement to Approvals Pending Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Approvals_Pending_Form_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Approvals_Pending_Form_Enhancement_R202507.htm

Enhancement to Approvals Pending Form

In association with the new Direct Deposit Change approval type (see Enhancements to Approval Policies and Global Approval Policies Forms), the Approval form, accessed by selecting a pending approval on the Approvals Pending form, now displays this approval type when worksite managers or worksite trusted advisors make a direct deposit change, which requires an approval. For example:

[Image: screenshot]

For more information about working with pending approvals, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-19673

========================================================================

Enhancement to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Employee_Fields_Import_Form_Enhancement_R_202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Employee_Fields_Import_Form_Enhancement_R_202507.htm

Enhancement to Employee Fields Import Form

Two new fields, Last Performance Rating and Last Performance Review, are now available to use during imports on the Employee Fields Import form, which is available on the Operations|Action menu. For example:

[Image: screenshot]

You can use the new fields to do the following:

Note: These fields relate to the same fields that display in the Performance panel on the Pay tab in the Employee Details form.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-19265

========================================================================

Enhancement to Portal New Hire Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Portal_New_Hire_Import_Form_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/HumanResources/Portal_New_Hire_Import_Form_Enhancement_R202507.htm

Enhancement to Portal New Hire Import Form

The system now allows service providers to use Alternate Employer IDs during imports in the Portal New Hire Import form when the following setup is configured in the Alternate Employers panel on the Other tab in the Client Details form:

Note: You can use an Alternate Employer ID in the Employer ID column in the import file. If the Employer ID does not meet the criteria listed above an error message displays during the import, “Employer ID is not valid for the Client ID.”

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-19005

========================================================================

Enhancement to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/Payroll/Data_Import_Tool_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/Payroll/Data_Import_Tool_Enhancement_R202507.htm

Enhancement to Data Import Tool

Two new fields, G/L Segment 2 and G/L Segment 3, now display on the Projects/Cost Codes import template in columns 6 and 7, and in the downloadable sample header file. For example:

[Image: screenshot]

Note: The original field, G/L Segment Code, now displays as G/L Segment 1 for consistency purposes.

You can use the G/L Segment 1, G/L Segment 2, and G/L Segment 3 fields to import up to three codes per project.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-19426

========================================================================

Enhancement to Pay Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/Payroll/Pay_Codes_Form_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/Payroll/Pay_Codes_Form_Enhancement_R202507.htm

Enhancement to Pay Codes Form

A new field, Unpaid Variable Salary Time, now displays in the Processing Options panel on the Pay Codes form when you enable the Include in Variable Salary Pay field. For example:

[Image: screenshot]

You can select the Unpaid Variable Salary Time field to reduce an employee’s Variable Salary pay by the percentage of unpaid hours assigned to the Unpaid Pay Code (default is disabled). For example, if an employee makes $3000 per pay period and they submit 100 hours, where 90 hours are worked and 10 hours are unpaid. This indicates that the employee’s wages should be reduced by 10 hours, so the system reduces the wages for the pay period from $3000 to $2700. This calculation works as follows: $3000/10 hours of unpaid time is $300, so $300 is subtracted from the gross pay. (On the voucher, the Unpaid Time hours display as the number of hours in the time sheet entry for the unpaid pay code, but the unit rate and amount display as zero (0).)

Note: The system still allocates wages for the reduced amount, except the pay is reduced by the unpaid hours.

For more information, see the in-product help or PrismHR Payroll Setup Guide.

JIRA # PD-19541 and PD-19542

========================================================================

Enhancement to Email Services Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/System/Email_Services_Form_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/System/Email_Services_Form_Enhancement_R202507.htm

Enhancement to Email Services Form

Two new email template types, Direct Deposit Change and ACH Maximum Resolution, now display on the Email Services form. For example:

[Image: screenshot]

[Image: screenshot]

Note: To access the Email Services form, select Email Services on the Actions menu in the System Parameters form.

The new template types do the following:

Note: Previously, worksite managers incorrectly received the HR Actions Resolution message when an ACH Maximum Approval policy was in place and the corresponding approval item was approved or denied.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-19672 and WSP-2221

========================================================================

Enhancement to Message Templates Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/System/Message_Templates_Form_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/System/Message_Templates_Form_Enhancement_R202507.htm

Enhancement to Message Templates Form

In association with the new Direct Deposit Change approval type on the Approval Policies and Global Approval Policies forms, a standard notification message is now available to accompany approval requests for direct deposit changes. To customize the message, use the Message Template form. For example:

[Image: screenshot]

For information about configuring message templates, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-19671

========================================================================

Enhancements to Users Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202507/System/Users_Form_Enhancement_R202507.htm Path: PD/Release-Notes/Enhancements/2025/R_202507/System/Users_Form_Enhancement_R202507.htm

Enhancements to Users Form

The following enhancements are now available on the Users form:

[Image: screenshot]

Note: You can only assign this role to service providers.

The Direct Deposit Approver is the user who can approve direct deposit updates stored in the employee details record.

[Image: screenshot]

Note: The Security by field is available for service providers with access to configure a worksite manager’s (WSM) Data Security.

You can use the Security by field to configure a user’s Data Security access hierarchy, so you can easily manage which employees the user can access.

The following chart displays a high-level overview of the Data Security access hierarchy used in association with the new Security by field:

[Image: screenshot]

The Security by field provides the following options:

Note: Note the following:

For information, see the in-product help or PrismHR System Administration Guide.

JIRA # PD-19670 and WSP-1230

========================================================================

Enhancement to Billing Rules (Bundled) Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Billing/Billing_Rules_Bundled_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Billing/Billing_Rules_Bundled_Form_Enhancement_R202508.htm

Enhancement to Billing Rules (Bundled) Form

Two new fields, Rule Start Date and Rule End Date, now display on the Billing Rules (Bundled) form. For example:

[Image: screenshot]

You can enter or select the Rule Start Date and Rule End Date to ensure the rule only applies during a specific date range.

For more information, see the in-product help or PrismHRBilling User Guide.

JIRA # PD-10014

========================================================================

Enhancement to Client Details and G/L Setup Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Client/Client_Details_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Client/Client_Details_Form_Enhancement_R202508.htm

Enhancement to Client Details and G/L Setup Forms

The system now displays the following error message when you enter or select an obsoleteG/L Template in either the Control tab on the Client Details form or the G/L Setup form, where the name of the obsolete G/L template displays within single quote marks:

[Image: screenshot]

An error message displays and the system will not process the payroll when a client assigned with an obsolete G/L template does the following:

Note: The payroll process ceases regardless of the payroll type (regular, manual, or special) or the payroll engine (legacy or restartable).

For more information, see the in-product help, PrismHR Accounting User Guide, or PrismHRClient Administration Guide.

JIRA # WSP-2246

========================================================================

Enhancement to Commission Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Client/Commission_Maintenance_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Client/Commission_Maintenance_Form_Enhancement_R202508.htm

Enhancement to Commission Maintenance Form

A new Based On field option, Percent of Target Amount, and a new field, Target Amount, now display on the Commission Maintenance form. For example:

[Image: screenshot]

Note: You can access the Commission Maintenance form by selecting Commissions from the Actions menu on the Client Details form.

You can now configure commissions to do the following:

The Target Amount field value is an overall dollar figure the system multiplies by the Amount Percent value to calculate the salesperson’s commission payout amount. For example, a Target Amount set to 100,000 for a 30% of Target Amount Commission setup would pay out $30,000 as the Commission amount for the defined commission period.

Note: Note the following:

Note: If the commission cannot be split evenly across all invoices, then the sum of all commission amounts across all invoices will still total the exact commission amount.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # WSP-2520 and WSP-2521

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Documentation/New_Task_Sheets_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Documentation/New_Task_Sheets_R202508.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Approvals Pending Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/HumanResources/Approvals_Pending_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/HumanResources/Approvals_Pending_Form_Enhancement_R202508.htm

Enhancement to Approvals Pending Form

A confirmation message now displays when you select a pending approval in the Approve column on the Approvals Pending form. (Previously, the system would automatically approve the change after users selected a pending approval.) For example:

[Image: screenshot]

Note: This confirmation message displays when you approve a pending approval in either the Assigned to You or the Available to You panels.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18775

========================================================================

Enhancement to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/HumanResources/Employee_Details_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/HumanResources/Employee_Details_Form_Enhancement_R202508.htm

Enhancement to Employee Details Form

A new field, Universal Employee ID, now displays on the Name tab in the Employee Details form. For example:

[Image: screenshot]

The Universal Employee ID field displays an employee’s qualified employee ID (System ID|organization ID|employee ID), so you can help them register and set up their PrismONE Mobile application.

Note: The PrismONE Mobile application is part of the PrismONE ID platform, a new cutting-edge Identity Management solution designed specifically for the PrismHR product suite that streamlines access across all PrismHR applications by enabling users to authenticate with a single, unified identity. (For more information about PrismONE Mobile, consult the Enabling PrismONE For Mobile article on the Customer Resource Center.)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-19795

========================================================================

Enhancement to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/HumanResources/Employee_Fields_Import_Form_Enhancement_R_202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/HumanResources/Employee_Fields_Import_Form_Enhancement_R_202508.htm

Enhancement to Employee Fields Import Form

Two new fields, HPE Prior Year and HPE Retirement Year, are now available to use during imports on the Employee Fields Import form, which is available on the Operations|Action menu. For example:

[Image: screenshot]

You can use the new fields to do the following:

Note: Note the following:

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-15787

========================================================================

Enhancements to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Data_Import_Tool_Enhancements_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Data_Import_Tool_Enhancements_R202508.htm

Enhancements to Data Import Tool

The following enhancements now reside on the Client Commissions import template in the Data Import Tool:

[Image: screenshot]

Enabling these fields does the following:

[Image: screenshot]

You can use the Target Amount field to indicate the commission’s target amount, which is used in conjunction with the new Based On field option, Percent of Target Amount. (You can enter up to two decimals in this field. The system truncates values with more than two decimals.)

The Target Amount field value is an overall dollar figure the system multiplies by the Amount Percent value to calculate the salesperson’s commission payout amount. For example, a Target Amount set to 100,000 for a 30% of Target Amount Commission setup would pay out $30,000 as the Commission amount for the defined commission period.

Note: See Enhancement to Commission Maintenance Form for more information about the new Target Amount field and Percent of Target Amount Based On option.

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # WSP-2235, WSP-2522, and WSP-2523

========================================================================

Enhancement to Payees Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Payees_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Payees_Form_Enhancement_R202508.htm

Enhancement to Payees Form

A new option, Colorado, now displays in the Eft Addenda Format field on the Payees form. For example:

[Image: screenshot]

You can select the Colorado option to include a Colorado employer’s full FEIN or Colorado Account Number (nine-digit Tp Identifier) in a Colorado EFT file (positions 12-20), which the system uses when sending electronic payments to a garnishing authority.

For more information, see the in-product help or PrismHRPayroll Setup Guide.

JIRA # PD-18695

========================================================================

Enhancement to Payroll Voucher Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Payroll_Voucher_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Payroll_Voucher_Form_Enhancement_R202508.htm

Enhancement to Payroll Voucher Form

A new field, Void Initiated, now displays on the Banking tab in the Payroll Voucher form after voiding a voucher. For example:

[Image: screenshot]

The Void Initiated field displays the date/time of the voucher void, which matches the time stamp when users enter or select a Voucher Number on the Employee Payroll Voucher Reversal form and click Accept in the Voucher Reversal Parameters form that displays, after which the system then displays the Processing Voucher Reversal process window.

Note: Note the following:

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # WSP-2266

========================================================================

Enhancement to Process Payroll and SuperBatch Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Process_Payroll_and_SuperBatch_Forms_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Process_Payroll_and_SuperBatch_Forms_Enhancement_R202508.htm

Enhancement to Process Payroll and SuperBatch Forms

A new option, Benefit Billing Detail Report, now displays in the Review field on the Process Payroll form and in the list of reports for the SuperBatch form. For example:

[Image: screenshot]

[Image: screenshot]

Selecting this option opens the Benefits Billing Detail Report form, which you can use to determine what information prints on the Benefits Billing Detail Report and in what order.

Note: Note the following:

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # WSP-2186

========================================================================

Enhancement to Process Payroll Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Process_Payroll_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/Payroll/Process_Payroll_Form_Enhancement_R202508.htm

Enhancement to Process Payroll Form

A new warning message now displays when calculating payroll in the Process Payroll form if an employee has a gross pay greater than zero but has zero net pay. For example:

[Image: screenshot]

Note: This feature is available for both the Restartable and Legacy Payroll processes.

This new warning message is helpful before finalizing payrolls in identifying employees with large deduction arrears that are using their entire check or employees who have completed their tax forms incorrectly.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-19280

========================================================================

Enhancement to G/L Template Maintenance Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/System/GL_Template_Maintenance_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/System/GL_Template_Maintenance_Form_Enhancement_R202508.htm

Enhancement to G/L Template Maintenance Form

A new field, Obsolete, is now available on the G/L Template Maintenance form. For example:

[Image: screenshot]

You can enable the Obsolete field for a Template ID to prevent it from being used.

In association with this update, a new column, Obsolete, now displays in the Select GL Template list when you select Template ID. For example:

[Image: screenshot]

Note: Obsolete G/L template IDs display Y in the Obsolete column.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-2245

========================================================================

Enhancement to Manager User Setup Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202508/System/Manager_User_Setup_Form_Enhancement_R202508.htm Path: PD/Release-Notes/Enhancements/2025/R_202508/System/Manager_User_Setup_Form_Enhancement_R202508.htm

Enhancement to Manager User Setup Form

A new field, Security by, is now available in the Data Entity Security panel on the Manager User Setup form. For example:

[Image: screenshot]

Note: The Security by field is available for service providers with access to configure a worksite manager’s (WSM) Data Security.

You can use the Security by field to configure a user’s Data Security access hierarchy, so you can easily manage which employees the user can access.

The following chart displays a high-level overview of the Data Security access hierarchy used in association with the new Security by field:

[Image: screenshot]

The Security by field provides the following options:

Note: Note the following:

Note: A message displays in place of the list of employees for new users who have direct reports where the user record and user ID have not yet been saved, “User must be saved before we can display employee access.” (The employee list displays after you save the record and the form refreshes.)

For information, see the in-product help or PrismHR System Administration Guide.

JIRA # WSP-2372

========================================================================

Enhancement to Inactive Data Deletion Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/Client/Inactive_Data_Deletion_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/Client/Inactive_Data_Deletion_Form_Enhancement_R202509.htm

Enhancement to Inactive Data Deletion Form

The Inactive Data Deletion form has been enhanced, so service providers can now quickly search for inactive Employees to deidentify their customer data. For example:

[Image: screenshot]

You can use the new Data Type field to quickly search for Clients or Employees who have been inactive for a certain number of years to potentially delete or deidentify inactive customer data. (Previously, you could only delete files for inactive clients.)

Note: To preserve data integrity, the system deidentifies employee data and removes any Personally Identifiable Information (PII). (The tool tip (

[Image: screenshot]

) displays this information.)

If you enable Employees in the Data Type field, three fields display, Years Terminated, Client ID, and Search, to help enhance your inactive data search. Note the following about these fields:

Note: After you select a number from the Years Terminated field, the following message displays:

[Image: screenshot]

Click OK to continue.

Note: Employee IDs associated with more than one Client ID display. For example:

[Image: screenshot]

Note: To narrow down the list of employees that displays, enter the employee ID or the employee’s first or last name in the Search box. After clicking the magnifying glass icon (

[Image: screenshot]

) or pressing Enter, the employee list redisplays that criteria. (Searches can return up to 1,000 employees at a time since only 1,000 employees can be deidentified at a time.)

To deidentify files for an inactive employee:

  1. Select Employees in the Data Type field.

  2. In the Years Terminated field, select the minimum number of years an employee must be inactive to display. The employees matching this criteria display. In addition, a message displays, “Employee Inactive Data Deletion limited to 1000 employees per run.”

  3. To narrow the search, enter or select the employee’s Client ID. After entering or selecting an ID and moving your cursor off the field, the search immediately displays all inactive employee data for that ID.

  4. Select the employees to deidentify in the Employees table. (Click Employee ID to select all employees that display.)

  5. After verifying the settings, click Deidentify Employee Data. A confirmation message displays, “Deidentify all data for the <number> selected employees?” Confirm the action to remove data for the displayed employees. (The system replaces the attribute values in Column F.)

Note: This action deidentifies employee data (that is, it removes the data instead of deleting it) and cannot be undone.

  1. Once the deidentify process is complete, click a link in the Employees column in the History panel to download a report of all employees removed from the system.

Note: This downloadable report lists the company ID and the employee ID for all employees who were deidentified. However, no PII is shared.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-19133, PD-19134, PD-19525, and PD-19803

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/Documentation/New_Task_Sheets_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/Documentation/New_Task_Sheets_R202509.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following new task sheet was created:

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancement to Employee Fields Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/HumanResources/Employee_Fields_Import_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/HumanResources/Employee_Fields_Import_Form_Enhancement_R202509.htm

Enhancement to Employee Fields Import Form

Ten new Alternate Pay Rate fields now display on the Select Field list in the Employee Fields Import form when you select Field Code in the Fields to Update panel. For example:

[Image: screenshot]

Note: These new Alternate Pay Rate fields replace the Alternate Pay Rates field.

You can use the new Alternate Pay Rate fields to import up to 10 alternate pay rates into a specific sequence number. (Previously, you could only import one alternate pay rate for an employee even though an employee could have more than one alternate pay rate.)

Note: Alternate pay rates are used in conjunction with pay codes that have a Standard calculation method. (You can enter the Alt. Pay Rate# number in the Standard Method Rules panel on the Pay Codes form.)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-18506

========================================================================

Enhancement to Bank Accounts Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Bank_Accounts_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Bank_Accounts_Form_Enhancement_R202509.htm

Enhancement to Bank Accounts Form

You can now enter alphanumeric characters, or a combination of both alphanumeric and numeric characters, in the bank Account ID field in the Bank Accounts form. (Previously, only numeric characters were allowed.) For example:

[Image: screenshot]

For more information, see the in-product help or PrismHRPayroll Setup Guide.

JIRA # WSP-2194

========================================================================

Enhancement to Change Employer IDs for a Voucher Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Change_Employer_IDs_for_a_Voucher_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Change_Employer_IDs_for_a_Voucher_Form_Enhancement_R202509.htm

Enhancement to Change Employer IDs for a Voucher Form

Two different warning messages now display after clicking Update in the Change Employer IDs for a Voucher form to help prevent accidental mass updates of employer IDs for vouchers:

[Image: screenshot]

Clicking Yes proceeds with the update.

[Image: screenshot]

Clicking Yes proceeds with the update.

For more information, see the in-product help or PrismHR Payroll Processing Guide.

JIRA # PD-19405

========================================================================

Enhancement to Data Import Tool

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Data_Import_Tool_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Data_Import_Tool_Enhancement_R202509.htm

Enhancement to Data Import Tool

Three new fields, Remove existing assignments, Replace existing assignments, and Keep Existing Assignments now display on the Client Account Assignments import template in the Data Import Tool. For example:

[Image: screenshot]

These new fields allow you to update existing records or add new records without including the entire list of users.

Enabling these fields during imports does the following:

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # WSP-2359

========================================================================

Enhancement to Employee Pay Summary Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Employee_Pay_Summary_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/Payroll/Employee_Pay_Summary_Form_Enhancement_R202509.htm

Enhancement to Employee Pay Summary Form

Two new fields, FSA Match and HSA PEO Match, now reside on the Employee Pay Summary form. For example:

[Image: screenshot]

These new fields display the following information from vouchers for the selected year and quarter:

For more information, see the in-product help or PrismHR Payroll Administration Guide.

JIRA # PD-14302

========================================================================

Enhancement to Manager User Setup Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/System/Manager_User_Setup_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/System/Manager_User_Setup_Form_Enhancement_R202509.htm

Enhancement to Manager User Setup Form

To control access to the Manager User Setup form for worksite managers and worksite trusted advisors, service providers can now add field-level security for sMFA device expiration using the Field option on the User Roles form. For example:

[Image: screenshot]

Note: Note the following:

To set field-level security on the Manager User Setup form:

  1. Go to the User Roles form on the System|Change menu.

  2. Enter or select the Role ID. (Note: If the user’s role is set to Inquiry for the Manager User Setup form, you cannot set field-level security even if the field security is set to grant access. If the user’s role is set to Full, you can only access the fields set in the field security settings.)

  3. Select Field for the Manager User Setup form (see screenshot above). The Field Security Maintenance form displays.

  4. Click Add. The Field Security Selection form displays.

  5. To enable field-level security for sMFA device expiration, select the Manager User Setup checkbox. For example:

[Image: screenshot]

  1. Click Accept. The selected field displays in the Field Security Maintenance form.

  2. To change field permissions and requirements:

  1. Click Save. The User Roles form re-displays.

  2. Click Save.

For information, see the in-product help or PrismHR System Administration Guide.

JIRA # PD-19622

========================================================================

Enhancement to Billing Rules Performance

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/System/PP_Performance_Billing_Rules_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/System/PP_Performance_Billing_Rules_R202509.htm

Enhancement to Billing Rules Performance

The search function on the Billing Rules form has been enhanced to improve the performance of the search, especially for clients with a large number of billing rules.

JIRA # PP-1967

========================================================================

Audit Available for SSO Services

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/System/PP_SSO_Audit_Log_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/System/PP_SSO_Audit_Log_R202509.htm

Audit Available for SSO Services

When any change is made to SSO Services, the changes will now display on the File Audit form.

JIRA # PP-1991

========================================================================

Enhancement to System Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/System/System_Parameters_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/System/System_Parameters_Form_Enhancement_R202509.htm

Enhancement to System Parameters Form

A new custom feature code, ADDRESSAUTOCOMP, is now available on the System Parameters form. For example:

[Image: screenshot]

IMPORTANT! THIS CUSTOM FEATURE CODE IS SCHEDULED FOR FUTURE DEVELOPMENT AND SHOULD NOT BE USED AT THIS TIME.

Enabling this custom feature code auto-completes an employee’s resident address in the Address field on the Address tab in the Employee Details form, the Worksite Locations form, the New Hire form, the Client Details form, and the New Client form, based on the Smarty address validation service.

For more information, see the in-product help or PrismHR System Administration Guide.

JIRA # PD-19948

========================================================================

Enhancement to User Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202509/System/User_Report_Form_Enhancement_R202509.htm Path: PD/Release-Notes/Enhancements/2025/R_202509/System/User_Report_Form_Enhancement_R202509.htm

Enhancement to User Report Form

A new field, User Role, now displays on the User Report form. For example:

[Image: screenshot]

You can use the User Role field to filter existing user roles by selecting a role from the list that displays.

In addition, the User Role displays in the report header. For example:

[Image: screenshot]

For information, see the in-product help or PrismHR System Administration Guide.

JIRA # WSP-1925

========================================================================

Enhancement to Billing Formats Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/Billing/Billing_Formats_Form_Enhancement_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/Billing/Billing_Formats_Form_Enhancement_R202510.htm

Enhancement to Billing Formats Form

A new option, STDNOBANK Standard Invoice with suppressed banking info, is now available in the Invoice Print Format field on the Billing Formats form. For example:

[Image: screenshot]

You can use the STDNOBANK Standard Invoice with suppressed banking info option to hide ACH/banking account information (that is, the system removes the bank account and all ACH Payment record data from the on-screen invoice display and the invoice’s PDF output) when the client is using any of the Electronic Billing options on the Billing tab in the Client Details form.

Note: This option affects standard ACH configurations, ACH by location or divisions, and wire transfers.

For more information, see the in-product help or PrismHRBilling User Guide.

JIRA # WSP-2660

========================================================================

Enhancement to Multi-Entity Group Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/Client/Multi_Entity_Group_Details_Form_Enhancement_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/Client/Multi_Entity_Group_Details_Form_Enhancement_R202510.htm

Enhancement to Multi-Entity Group Details Form

A new field, Common Law Employer Group, now displays on the Multi-Entity Group Details form. For example:

[Image: screenshot]

You can select Common Law Employer Group to define the multi-entity group as that type.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-20060

========================================================================

New and Improved Task Sheets

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/Documentation/New_Task_Sheets_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/Documentation/New_Task_Sheets_R202510.htm

New and Improved Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

To print any task sheet, right-click on the topic and select Print. You can also find PDFs of these task sheets on the Customer Resource Center.

========================================================================

Enhancements to Employee Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/HumanResources/Employee_Details_Form_Enhancements_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/HumanResources/Employee_Details_Form_Enhancements_R202510.htm

Enhancements to Employee Details Form

The enhancements described in this release note are available on the Employee Details form.

Enhancements for Deidentified Employees

The following enhancements are associated with deidentified employees:

[Image: screenshot]

Click OK to continue.

Note: To deidentify employees, select Employees in the Data Type field on the Inactive Data Deletion form. (For more information, refer to the “Removing Inactive Customer Data” topic in the PrismHR Client Administration Guide, which displays when you select the help (

[Image: screenshot]

) icon in the Inactive Data Deletion form.)

Enhancements for Gender Designation and Preferred Pronouns

The following enhancements now reside on the Other tab:

Note: You can no longer create, update, or delete a Gender Designation Code or Preferred Pronoun Code. Instead, you must select a standard code from the list that displays in the Gender Designation and Preferred Pronoun fields. (See Enhancements to Self Identity Codes Form for a list of available standardized codes.)

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-19768, PD-19771, PD-20061, PD-20062, and PD-20063

========================================================================

Enhancements to Self Identity Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/HumanResources/Self_Identity_Codes_Form_Enhancements_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/HumanResources/Self_Identity_Codes_Form_Enhancements_R202510.htm

Enhancements to Self Identity Codes Form

The following enhancements now reside on the on the Self Identity Codes form:

Code Description
A Agender
AP Apathetic
BI Bigender
DN Do Not Disclose
F Female
G Genderfluid
GQ Genderqueer
M Male
MA Maverique
NB Non-Binary
NL Not Listed
T Transgender
TF Transgender Female
TM Transgender Male
TRI Trigender
TWO Two-Spirit

Note: If a gender designation code in this table already exists, the system overwrites the description with the one used in this table. For example, if the code G already exists with the description “Genderqueer,” the system overwrites it as “Genderfluid.”

Code Description
AE ae/aer/aers
CO co/coself
EV ey/em/eirs
FAE fae/faer
H he/him/his
IT it/its
MER mer/mers
NE ne/nem/nirs
NONE I don’t have pronouns
PER per/pers
S she/her/hers
TH they/them/theirs
VE ve/ver/vers
VIR ve/vir/vis
XE xe/xem/xyrs
ZE ze/hir/hirs
ZIR ze/zir/zirs

Note: You can continue to select the employee’s Gender Designation or Preferred Pronoun by selecting from the standardized list that displays on the Other tab in the Employee Details form.

For more information, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-19746, PD-19747, and PD-19770

========================================================================

Enhancement to Pay Schedules Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Pay_Schedules_Form_Enhancement_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Pay_Schedules_Form_Enhancement_R202510.htm

Enhancement to Pay Schedules Form

Currently, the system sets the period end date the same as the pay date when a pay schedule is set up as Monthly, the Pay Day is set as End Of Month, and the Pay Period Ends is set to end on this day of the month after/before the pay date (as configured in the On this Day of Month After the Pay Date field).

This process has been enhanced, so you can now create a pay schedule for a monthly payment where the pay date occurs before the pay period. For example, a schedule can be set up with a pay period of 8/1/2025-8/31/2025 for a pay date of 7/31/2025, so the Pay Period Ends date is the same date as the Pay Day date.

For more information, see the in-product help or PrismHRPayroll Setup Guide.

JIRA # PD-19157

========================================================================

Enhancement to Payroll Approval Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Payroll_Approval_Form_Enhancement_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Payroll_Approval_Form_Enhancement_R202510.htm

Enhancement to Payroll Approval Form

The system no longer incorrectly prints Approval Payroll Reports when accessed in the View/Report Analytic field on the Payroll Approval Form. (You can also view Approval Payroll Reports in Employee Portal (EP).)

For more information, see the in-product help, PrismHR Payroll Processing Guide, or PrismHRPayroll Reports guide.

JIRA # PD-19950

========================================================================

Enhancements to Payroll Variance Analysis Dashboard

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Payroll_Variance_Analysis_Dashboard_Enhancements_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Payroll_Variance_Analysis_Dashboard_Enhancements_R202510.htm

Enhancements to Payroll Variance Analysis Dashboard

The following enhancements now reside on the Payroll Variance Analysis dashboard:

For example:

[Image: screenshot]

[Image: screenshot]

You can now select one of the following variance options in the Payroll Variance Warning field:

Note: A text box displays next to the Payroll Variance Warning field where you can change the amount or percentage number. (This number defaults to 10.) If you enter a number for Amounts that is greater than 100 and then select Percentages, the number reverts to 10 (default).

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-19638 and PD-19982

========================================================================

Enhancement to Process Payroll Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Process_Payroll_Form_Enhancement_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/Payroll/Process_Payroll_Form_Enhancement_R202510.htm

Enhancement to Process Payroll Form

An error message now displays when you process a payroll that contains a deidentified employee. For example:

[Image: screenshot]

Note: This error message displays in both restartable and legacy payrolls.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-20064

========================================================================

Enhancement to Confirmation Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2025/R_202510/PTO/Confirmation_Form_Enhancement_R202510.htm Path: PD/Release-Notes/Enhancements/2025/R_202510/PTO/Confirmation_Form_Enhancement_R202510.htm

Enhancement to Confirmation Form

A new button,

[Image: screenshot]

, now displays in the panels on the Confirmation form, which is step 3 in the Time Off Setup Workflow process. For example:

[Image: screenshot]

Note: To access the Confirmation form, open a plan in the Time Off Setup Workflow form and click

[Image: screenshot]

, then click

[Image: screenshot]

in the Set Up Plans form (step 2 in the Time Off Setup Workflow process), which displays if you have completed all the required fields on that form.

You can click the

[Image: screenshot]

button in the panels to return to the previous panels in the Set Up Plans form to update plan information. Make your updates and click

[Image: screenshot]

to proceed to the Confirmation form.

For more information about the Confirmation form, see the in-product help or the PrismHR Paid Time Off User Guide.

JIRA # PD-20028

========================================================================

Enhancement to Positions Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Enhancements/2026/R_202603/Client/Positions_Form_Enhancement_R202603.htm Path: PD/Release-Notes/Enhancements/2026/R_202603/Client/Positions_Form_Enhancement_R202603.htm

Enhancement to Positions Form

A new field, Remote Position Classification, now displays on the Positions form.

You can use the Remote Position Classification field to designate an alternative position classification for remote employees of the same position.

Note: Note the following:

For more information, see Defining Positions.

JIRA # WSP-3195

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202401/General/Fixes_General_PrismHRP_MR202401.htm Path: PD/Release-Notes/Fixes/2024/MR202401/General/Fixes_General_PrismHRP_MR202401.htm

General Fixes

Jira # Issue Summary Resolution
PD-16140 Users were able to apply an exported timesheet template to the import definitions in the Time Sheet tab on the Client Details form. This is fixed.
RRT-5589 The system sometimes did not remove the employee details in full from open payroll batches after users deleted an employee using the Delete Unused Employee form. This is fixed.
RRT-5593 This customer-specific issue occurred because the key structure they used prevented the system from creating a zip file. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202401/Payroll/Fixes_Payroll_PrismHRP_MR202401.htm Path: PD/Release-Notes/Fixes/2024/MR202401/Payroll/Fixes_Payroll_PrismHRP_MR202401.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-16315 The system allowed users to remove a non-voluntary deduction code by clearing the value in the Recurring Deductions form. The system now reverts non-voluntary deduction codes back to their original code when users clear them in the Recurring Deductions form.
RRT-5575 The system did not update the GL.DETAIL file when adjustments were created during the Tax Adjustments process. This is fixed going forward for new adjustments.
RRT-5592 The system sometimes produced blank output and displayed a message, “No items to print on this report,” after running the Payroll Check Printing Report. This is fixed.
RRT-5643 The system did not accept zero (0) deduction amounts during payroll calculations when users processed payrolls. (The data validation only allowed numbers larger than $0.) This is fixed.
RRT-5668 The system displayed an error message when users tried to calculate a new manual check in the Manual Check Entry form. This is fixed.
RRT-5671 The system did not allow users to enter special characters, such as the underscore symbol, in the PC File Name field in the ACH Originators form. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202402/Payroll/Fixes_Payroll_PrismHRP_MR202402.htm Path: PD/Release-Notes/Fixes/2024/MR202402/Payroll/Fixes_Payroll_PrismHRP_MR202402.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-16029 The system did not recognize memo codes that had a Percent of Gross Earnings calculation basis when users generated the Memo Pay Code Report. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202404/General/Fixes_General_PrismHRP_MR202404.htm Path: PD/Release-Notes/Fixes/2024/MR202404/General/Fixes_General_PrismHRP_MR202404.htm

General Fixes

Jira # Issue Summary Resolution
API-6926 An internal issue caused the Employee Details form to not display the Applicant ID and Clock Number of newly hired employees. These fields are located in the Other and Work tabs of Employee Details. This is fixed. Going forward, these values are now saved correctly. > Note: Note: Any employee records affected by this issue must be corrected. Incorrectly saved Clock Number values can be corrected manually. If the issue affects the Applicant ID, contact PrismHR Customer Support for assistance.
PD-15030 The system displayed a prompt to set a new password when a service provider proxied in as a worksite manager from the Users form who had Requires New Password enabled. Service providers no longer receive a prompt to set a new password in this scenario.
PD-16810 The system did not display a warning when users imported a new employee with a home, work, or cell phone number that contained an alpha character using the New Employee Import form. This is fixed.
PD-16830 The Save and Save & Close buttons on all tabs in the Employee Details form remained active (although they did not work) even though they were set to Inquiry mode. This is fixed.
PD-16999 The system imported the FICA Exempt Thru date into the Thru Date field when users ran imports using the Employee Fields Import form. The system now imports the FICA Exempt Thru date to the Employee Details record.
PP-1320 When an employee entered a Position Title on the Positions form that contained special characters, the title would display incorrectly on the Org Chart form. This is fixed. The Org Chart form now displays special characters properly.
PP-1401 When a user selected the a valid state in the State Code field on the State Tax Rates (SUTA) form, then reselected the State Code field and clicked Select, an error message displayed. This is fixed.
RRT-5328 The system displayed a service provider instead of the actual user who processed the approval in the PTO Approval Report. This is fixed.
RRT-5627 The system displayed an error message when users attempted to save an existing record whose name was “NEW” on the New Hire Questions form. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202404/Payroll/Fixes_Payroll_PrismHRP_MR202404.htm Path: PD/Release-Notes/Fixes/2024/MR202404/Payroll/Fixes_Payroll_PrismHRP_MR202404.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-17012 The system created an incorrect Period End Date for the monthly payroll schedule that displayed on the Pay Groups form. This is fixed.
PD-17038 The system displayed gray text instead of black text on the SuperBatch form. This is fixed.
RRT-5318 The system did not return any results (even though there were audit entries) when users filtered changes using the Find Changes to a File Report form by selecting the CLIENT.MASTER Audited File Name and the ACHStatus Audited Field Name (attribute 109). This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202405/General/Fixes_General_PrismHRP_MR202405.htm Path: PD/Release-Notes/Fixes/2024/MR202405/General/Fixes_General_PrismHRP_MR202405.htm

General Fixes

Jira # Issue Summary Resolution
PD-17068 The system cut off the Deny Reason in the email when the HR Resolutions message template in the Message Templates form included blank lines between sentences and the Deny Reason included a carriage return. This is fixed.
PP-1467 When an address for a newly hired employee had multiple geocodes, the Geocode field on the Address tab of the Employee Details form defaulted to a value of 1. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202405/Payroll/Fixes_Payroll_PrismHRP_MR202405.htm Path: PD/Release-Notes/Fixes/2024/MR202405/Payroll/Fixes_Payroll_PrismHRP_MR202405.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-17116 The Payroll is ready to calculate icon did not display in the SuperBatch form after a manager approved the maximum check amount. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202407/General/Fixes_General_PrismHRP_MR202407.htm Path: PD/Release-Notes/Fixes/2024/MR202407/General/Fixes_General_PrismHRP_MR202407.htm

General Fixes

Jira # Issue Summary Resolution
PD-17525 The system displayed a worksite trusted advisor’s user ID in Data Retriever instead of their first and last name when they were assigned as a PTO approver. This is fixed.
PP-1474, PP-1487 When a worksite manager with access to multiple companies displayed the Organization Chart, the chart would display incorrectly if the manager was assigned employees from a different company than the current session. This is fixed.
PP-1540 When a user selected the Look Back filter on the External Journal Post form, future-dated journals would incorrectly display. This is fixed.
WSP-467 A warning message displayed on the Tax tab in the Employee Details form when the state tax was not set up for a 1099 contractor, which was confusing because the state tax is not required. This is fixed.
WSP-472 On the Tax Register Audit Inquiry form, the header displayed incorrectly. This is fixed.
WSP-551 The system encountered an issue with the CLIENTBATCH field in external invoice files with custom accounting layout. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202407/Payroll/Fixes_Payroll_PrismHRP_MR202407.htm Path: PD/Release-Notes/Fixes/2024/MR202407/Payroll/Fixes_Payroll_PrismHRP_MR202407.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-17426 The buttons on the Earnings Maximum, Tax Exemptions, and Weighted Average forms, accessed from the Pay Codes form, did not display in the modernized style. This is fixed.
PD-17427 The buttons on the Show employees and Time Sheet Defaults forms, accessed from the Actions menu in the Pay Groups form, did not display in the modernized style. This is fixed.
WSP-539 If a client-bill-pending record contained hidden line items for COVID charges, then when other line items were edited in the Bill Pending form the system lost track of where they belonged. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202408/General/Fixes_General_PrismHRP_MR202408.htm Path: PD/Release-Notes/Fixes/2024/MR202408/General/Fixes_General_PrismHRP_MR202408.htm

General Fixes

Jira # Issue Summary Resolution
RRT-5898 A previous update to the program caused the filtering based on the G/L Company Number on the Employer Details form to fail, which resulted in the system placing all the requested data in one file. This is fixed.
RRT-5920 If users entered an Employee Number on the Work tab in the Employee Details form earlier and then changed it, the system did not use the new number for timesheet imports. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202408/Payroll/Fixes_Payroll_PrismHRP_MR202408.htm Path: PD/Release-Notes/Fixes/2024/MR202408/Payroll/Fixes_Payroll_PrismHRP_MR202408.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-17582 Users could not import a service provider as a backup account assignment to a client using the Backup Account Assignment import template in the Data Import Tool when the service provider did not have access to that client through Client Access Groups, and the import was set to Keep Existing Data or Remove Existing Data. This is fixed.
PD-17628 The system did not display the same rounded totals from the Deductions column on the Payroll Summary form in its output report. This is fixed.
RRT-5899 The system displayed bill code accounting errors during the Regenerate Client Accounting process. This process now regenerates data when a bill code or account changes in the G/L.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202410/General/Fixes_General_PrismHRP_MR202410.htm Path: PD/Release-Notes/Fixes/2024/MR202410/General/Fixes_General_PrismHRP_MR202410.htm

General Fixes

Jira # Issue Summary Resolution
PD-17896 Worksite managers were unable to assign a cross-hired worksite manager (an employee who was not hired by the client) as a PTO Approver or Manager on the Employee Details form. This is fixed.
PD-18202 The system did not apply the change when users enabled Apply Current Hours Taken before applying Stop-Balance limits in the PTO Benefit Plans form and saved the record. This is fixed.
PD-18233 The system displayed a fatal error message during payroll calculation when an employee had the federal tax Override Type set to Add to Withholding on the Tax tab in the Employee Details form and that employee had zero hours (that is, 0.00) listed on a voucher. This is fixed.
PD-18236 The system displayed a fatal error message during payroll calculation when an employee had a value entered in the Other Income field on the Tax tab in the Employee Details form and a large Voluntary Deduction or Retirement Flat amount. This is fixed.
PP-1607 When a user added a new position classification, the classification displayed on the Client Details Audit form, despite never having been used. This is fixed.
PP-1616 When a user tabbed through the Group Benefit Plans form and there was no data in certain sections of the form as the user tabbed through, data would be incorrectly cleared from the form. This is fixed.
PP-1617 When a user viewed the New Hire form and resized the browser window, data could be deleted from the form. This is fixed.
PP-1624 When a multi-value grid such as the Custom Code Translation Table form had a blank row as a separator, users could navigate to the blank row with tab and make entries. In addition, blank rows were sometimes added to the last page of a multi-value grid. This is fixed.
PP-1626 When a user selected Manual in the Payroll Type field on the Payroll Control form, the user could only add a maximum of six employees to the batch. This is fixed.
PP-1646 When a user attempted to add a User Field for the Delivery Methods feature, the form for a client-level change displayed. This is fixed. Changes to the Delivery Methods feature now display the proper system-level change form.
PP-1655 When a Worksite Manager user selected the Support Team tab on the Enhanced Dashboard, the tab immediately closed after the user selected it. This is fixed.
PP-1658 When a user set the PEO Client Accounting template to Custom and selected Tab as the delimiter, the data opened as a web page instead of a .txt file. This is fixed.
PP-1676 When a user attempted to display the Org Chart form, the form incorrectly displayed a message that there was no available data. This is fixed.
PP-1677 When a new hire was added to a client, the Enhanced Dashboard and My Home forms did not display an updated employee total on charts. This is fixed.
RRT-5867 When users either entered a company ID after entering an employer ID or entered an employer ID after entering a company ID in the Quarterly Tax Export form, the system displayed messages that referenced the “employee ID” when it should have referenced the “employer ID.” This is fixed.
WSP-765 Clicking Cancel in the Global User Defined Fields form did not clear the selected information from the screen. In addition, clicking Cancel after clicking Save displayed the multi-value grid data from the previously selected Page Title, but did not actually select the Page Title or display any saved updates. This is fixed.
WSP-769 The Save and Delete buttons and the selector field links sometimes appeared active (although they did not function) for users whose role was set to Inquiry on the PTO Auto Enroll Rules form. In addition, the Line # links were not available for viewing purposes. This is fixed.
WSP-771 Users whose role was set to Inquiry on the Employee Work form were able to select some of the links in the Employment Verification panel and select a value, then access a different tab and save that update. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202410/Payroll/Fixes_Payroll_PrismHRP_MR202410.htm Path: PD/Release-Notes/Fixes/2024/MR202410/Payroll/Fixes_Payroll_PrismHRP_MR202410.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-18151 The Restartable Payroll engine sometimes displayed an error message, “Cannot read employee payroll voucher,” when the system was calculating payrolls. This is fixed.
PD-18153 The Restartable Payroll engine did not reorder charge dates chronologically for Detail Time entries on the voucher when an employee was subject to Alabama State Income Tax and the later charge date was entered in the detailed time entry first, which incorrectly calculated the Alabama Overtime exempt amount. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled, the system correctly reordered detail time entries and the taxes were calculated correctly. This is fixed.
PD-18156 The premium overtime pay code did not honor the pay period end date when the Restartable Payroll engine was used with the FLSA ruleset that included a premium pay code for overtime. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled, the Legacy Payroll engine honored the work weekday override on the pay group. The Restartable Payroll engine now uses the Work Week Ends On date override on the employee’s pay group to charge the premium overtime pay code.
PD-18218 The Restartable Payroll engine did not suppress benefits when the Suppress Benefits Calculation field was enabled on the Payroll Option Templates form. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled in this scenario, the system suppressed benefits. This is fixed.
PD-18238 The Restartable Payroll engine did not generate the correct results when the Adjust Taxes to Cover Cash Shortfall field on the Payroll tab in the Client Details form was set to Adjust taxes before deductions. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled in this scenario, this issue did not occur. This is fixed.
RRT-5852 The system did not accurately track employees with multiple pay codes in the Payroll Allocation Report if one of the departments was null in the Allocations table. This is fixed.
WSP-770 The Delete button was active for users whose role was set to Inquiry on the Check Acknowledgement Report Parameters form. > Note: Note: Clicking Delete and selecting Yes in the prompt did not actually delete the record. This is fixed.
WSP-830 The system sometimes generated false errors in client accounting when users ran the Payroll Validation Report. This is fixed.
WSP-842 When running a payroll, the system did not correctly calculate the withholding based on the Ending Pay date and calculation Status on the Tax Calculation Overrides form. This is fixed.
WSP-988 Users were unable to access the timesheet and restart the payroll process after a wire transfer was marked as received. Users can now access timesheet-entry and initialization again for a payroll with wire-pending status and is marked as payment received on the Payments Pending form.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202412/General/Fixes_General_PrismHRP_MR202412.htm Path: PD/Release-Notes/Fixes/2024/MR202412/General/Fixes_General_PrismHRP_MR202412.htm

General Fixes

Jira # Issue Summary Resolution
PD-18590 The system did not correctly format the email produced when users imported new hires in the Portal New Hire Import form. > Note: Note: New hires entered manually were not affected by this scenario. This is fixed.
RRT-6023 The system did not recognize the ALLOWZEROSSNS custom feature code that was enabled when users tried to save the new 000 Employee SSN number on the Employee Details form and displayed an error message. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/MR202412/Payroll/Fixes_Payroll_PrismHRP_MR202412.htm Path: PD/Release-Notes/Fixes/2024/MR202412/Payroll/Fixes_Payroll_PrismHRP_MR202412.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-18246 The system did not display an error message for an unapproved payroll with an initialized voucher that exceeded the maximum check amount when users tried to recalculate it using the Restartable Payroll feature in the Process Payroll or SuperBatch form. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled in this scenario, this issue did not occur. This is fixed.
PD-18247 The system generated a negative deduction (credits/refunds) as an A voucher when users tried to generate a live check using Restartable Payroll for a manual payroll that contained a .01 timesheet detail entry and a negative one-time deduction. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled in this scenario, this issue did not occur. The system now generates an R voucher where the check number displays on the Banking tab in the Payroll Voucher form.
PD-18280 The system did not display benefit adjustments on the Deductions tab in the Payroll Voucher form after users calculated a regularly scheduled payroll using the Restartable Payroll feature. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled in this scenario, this issue did not occur. This is fixed.
PD-18321 The system did not create a voucher when users calculated a payroll using the Restartable Payroll feature that contained one employee who had two detail entries that overwrote each other. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled in this scenario, this issue did not occur. This is fixed.
PD-18509 The system displayed employees who had zero pay vouchers when users calculated a special payroll using the Restartable Payroll feature. > Note: Note: When the LEGACY-PAYROLL-GLOBAL custom feature code was enabled in this scenario, this issue did not occur. This is fixed.
WSP-1215 Users were unable to download reports, except for the Voucher Summary Report, before posting results when they accessed step 5, Calculate Taxes, in the Check History Import process after the voucher information displayed. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202403/General/Fixes_General_PrismHRP_QR202403.htm Path: PD/Release-Notes/Fixes/2024/QR202403/General/Fixes_General_PrismHRP_QR202403.htm

General Fixes

Jira # Issue Summary Resolution
PD-14807 The system did not match the bulk role descriptions to the user role in the Bulk Role Update form. This is fixed.
PD-15636 The system did not delete pending payrolls when users changed the client’s status in the Client Status Change form. This is fixed.
PD-15955 A phantom checkbox displayed at the bottom of the list in the Messages form if there were less than 99 messages. This is fixed.
PD-16176 Users who proxied in as managers were unable to view planned time off requests if they were logged in directly as a manager. This is fixed.
PD-16325 The system did not display an error message during an employee fields import if the employee’s record did not have the FICA Exempt field enabled on the Tax tab in the Employee Details form and users tried to enter a thru date. In this scenario the following error message now displays, “The FICA Exempt field must be Yes to add a thru date.”
PD-16326 The system allowed users to save a blank user record in the User Roles panel in the Users form. The system now removes any blank user roles in the Users form when users save the record.
PD-16578 The system did not calculate union deductions correctly when users updated an employee’s Labor Union Affiliation in the Employee Fields Import form. This is fixed.
PP-767 When a user accesses the Client Benefits Overview form with more than 500 benefit groups available, severe performance delays would occur. This is fixed. Plans terminated over a year ago will now be skipped on this form to improve performance.
PP-936 The column headers on the Enhanced Dashboard were misaligned after an update to the form. This is fixed.
PP-1131 When a user attempted to search for an employee with an invalid record due to modifications or deletion, the search process would sometimes lag out and cause processing delays. This is fixed.
PP-1177 When a user attempted to export the Employee Master Report or the Emergency Contact Report as an XLS file, an error occurred. This is fixed.
PP-1205 When a user reviewed records on the SuperBatch form, records could not be properly sorted by Pay Date. This is fixed.
PP-1208 The Billing Zip Code field on the COBRA Participant Record form was not listed as a required field. If a user left the field blank, an invalid entry was saved on the record. This is fixed.
PP-1214 Multi-factor authentication would sometimes send two separate authentication emails to the user’s email account. This is fixed.
PP-1246 When a user received a warning message while attempting to archive a PTO Register that had already been archived, the warning message displayed incorrect text. This is fixed.
PP-1247 Users could assign roles to individuals who lacked the proper permissions by manually entering the user name on the Backup Account Assignments form. This is fixed. The Backup Account Assignments form now restricts users from being assigned to roles when they lack the proper security permissions.
PP-1261 When printing a report or converting a report to a PDF format, a user could enter special characters into the Print From Page and Print To Page fields, which created an error. This is fixed.
PP-1267 When an employee clicked the Select Geocode button on the Employee Address form to locate a geocode, the selection window did not properly display. This is fixed.
RRT-5610 When there were multiple unbundled billing rules that specified the same Position Code, Pay Class, and Pay Code, but different Location Codes, the system did not follow the sales tax setup in the Sales Tax Codes form and incorrectly calculated the sales tax. In this scenario, after users applied an unbundled billing rule and the system calculated the sales tax, other unbundled billing rules matching the description above had incorrectly calculated sales tax, which was added to the sales tax total even though those later billing rules specified a Location Code that was different from the Location Code in the timesheet earnings. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202403/Payroll/Fixes_Payroll_PrismHRP_QR202403.htm Path: PD/Release-Notes/Fixes/2024/QR202403/Payroll/Fixes_Payroll_PrismHRP_QR202403.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-15516 When a check import was processed with an HSA deduction where the type was set as a Flexible Spending Account, the system created a record for the year in which the check import was dated. (This was incorrect because a client might have both a Section 125 plan and an HSA plan.) When using a check import to record HSA deductions, the process now creates and updates the employee flexible spending record. In addition, this process now validates whether the deduction code in the import is linked to a Section 125 plan on the client or to the HSA plan listed on the Benefits tab in the Client Details form. Therefore: - When using the HSA plan, the system creates a record with the plan year HS21, HS22, HS23. - When using the Section 125 plan, the record remains 2021, 2022, 2023.

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202406/General/Fixes_General_PrismHRP_QR202406.htm Path: PD/Release-Notes/Fixes/2024/QR202406/General/Fixes_General_PrismHRP_QR202406.htm

General Fixes

Jira # Issue Summary Resolution
PD-16526 The system displayed an error message in the Delete Pending Client form when users added a client to a segment, moved that client to Pending status, and then deleted it, so they could no longer open the segment. This is fixed.
PD-16573 The system displayed a warning that didn’t apply when users enrolled an employee in a PTO Benefit Plan with YTD Hours Calculated in the Employee PTO Register Enrollment form. The system now validates against the correct seniority level when users enroll employees.
PD-16854 The default MFA message that displayed in the Message Templates form when no custom MFA message had been configured was grammatically incorrect. This is fixed.
PD-16858 After users selected an Employee and Register Type on the Employee PTO Register, they had to click the Actions menu twice to open it. This is fixed.
PD-16863 The list of options in the Leave Employment Status field on the Leave of Absence form did not display in alphabetical order. This is fixed.
PD-16864 The system did not display the Reason column in the Status Type History form after users reactivated an employee. This is fixed.
PD-16997 The Employee Details option did not display on the Actions menu in the Employee Benefits Enrollment form for users whose role was set to Inquiry access for the Employee Details form. This is fixed.
PD-17003 Users were unable to delete a Client Acct Template from a worksite location in the Worksite Locations form after processing a payroll. This is fixed.
PD-17026 The system did not display the net amount of earnings when it calculated the salary amount for an employee with the Calc Salary by Date Range field enabled on the Retirement Exports form for the Pinnacle template. This is fixed.
PD-17073 The text box for the Rebate Bill Code field on the Deduction Codes form did not line up with the field. This is fixed.
PD-17109 The system did not update the PTO register’s Benefit Start Date on the Employee PTO Register form when users switched between Register Types. This is fixed.
PD-17130 The system included the December accrual amount in the PTO Register Types form for the First of Following Month Trigger Method in the carryover for a year’s YTD PTO accrual that was not the current year, which effectively doubled the last month of the year’s PTO accrual. This is fixed.
PD-17218 An error message did not display when users entered a new hire with direct deposit set to Active and then saved the record with missing information, such as the account number. The appropriate error message now displays in this scenario.
PD-17233 The system allowed users to save information in the EEO Ethnic Codes form without selecting the EEO Report code, which is a required field. This is fixed.
PD-17234 After users processed the W-2 Box Report successfully and clicked Report in the Job Progress window, clicked Report to view the report output results and closed that window, then clicked Close in the Job Progress window, the report output redisplayed with no results (the output was blank). This is fixed.
PD-17241 The system displayed the wrong error message, “Please raise a Custom Programming Request,” when users tried to delete a new hire on the Delete Unused Employee form after entering a transfer in the Transfer Tax Basis form. The correct error message now displays in this scenario, “Please submit a Professional Services Engagement Request.”
PD-17242 The system displayed the School District Number in the Registration Number field on the Property tab in the Employee Details form, which overrode any existing value for that field. This is fixed.
PD-17254 The system did not display audit record updates in the File Audit form when users created W-2s and changed the W2C web access to No for the employer. This is fixed.
PD-17260 The system did not include all required fields for the state of Maine in the New Hire Reporting form’s downloadable output file. This is fixed.
PP-605 When a user searched for an employee on the Find Changes to an Employee form, the search resulted in slowed performance. This is fixed.
PP-1084 In some cases, the External Journal Post form resulted in slow performance when search results returned a large number of records. This is fixed.
PP-1157 When a client attempted to add a large number of employees to the Payroll Control Quick Load form, an error occurred. This is fixed.
PP-1314 When a user reviewed the File Audit form, mass pay rate changes displayed “Background Process” instead of the user who made the change. This is fixed. The audit log now shows the User ID.
PP-1328 When a user added a phone number with too many digits to the Emergency Contact section of an employee record, the system saved the improper number and did not inform the user of the error. This is fixed. The user is now notified that the phone number has too many digits and must be corrected.
PP-1374 When a user made changes on the Client Benefit form to the ACA table, the File Audit form displayed incorrect information for changes to the Year and ACA Large Employer fields. This is fixed.
PP-1379 When a user selected Add All on a selection form which displayed items 100 at a time, only the first 100 items would be added. For example, on the Select Pay Code form, clicking Add All would add the first hundred pay codes displayed. This is fixed.
PP-1387 When a user selects multiple clients using the Client ID selector on the Unbundled Billing Rules Import form, then uses the selector to remove some of the selected clients, the clients were not properly removed from the list and an error message displayed. This is fixed.
PP-1479 When a user entered a ZIP code on the New Hire form and selected a GeoCode from the dropdown menu, the City, State, and Country fields did not automatically populate. In addition, state forms based on these fields were not properly flagged as required. This is fixed. Selecting a geocode now populates the corresponding fields properly and flags the required forms.
WSP-342 The system evaluated Misc GL segments for departments, divisions, locations, positions, and projects on payroll invoices. The system now suppresses evaluation of the wildcards when building account codes for payroll invoices.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202406/Payroll/Fixes_Payroll_PrismHRP_QR202406.htm Path: PD/Release-Notes/Fixes/2024/QR202406/Payroll/Fixes_Payroll_PrismHRP_QR202406.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-16034 The system incorrectly pointed to the Employee Master, an HRPyramid term, instead of the Employer Details form, in the error message that displayed when users tried to process a payroll that contained a state tax number that was not listed in the State Tax panel for the state where the employee works and resides. The correct error message now displays, “State income tax is being calculated for but a State Tax Number has not been setup on the Employer Details record for Employer ID . State tax number must be setup for this employer before this payroll can proceed.” > Note: Note: This update includes restartable payrolls.
PD-16572 The system did not round per pay periods as expected for a salaried employee in the Time Sheet Entry form when their pay was split between two or more pay codes. When pay codes are marked to round to the pay period, the system now forces the total amount of the salaried employee’s pay to round this way, as long as the total hours equal their standard pay.
PD-16806 The system doubled Workers’ Compensation Basis Pay when users created an on-demand check using the On Demand Check Processing form. The Workers’ Compensation Basis Pay now equals the Pay Amount of an on-demand check.
PD-16914 The values in the Description columns overlapped into the Amount column in the output for the Payroll Variance Reports form, which made it difficult to read. The values in the Description columns were truncated, so they no longer overlap into the next column.
PD-16991 User were unable to edit the Leave to Timesheet and Notes fields in the Leave request assignment form when a new leave request for the pay period of a current payroll was approved after an approved leave request was already accepted into a timesheet. This is fixed.
PD-17033 The Commission pay method that displayed in the Pay Method column after selecting the Filter icon in the Time Sheet Entry form was spelled incorrectly. This is fixed.
PD-17064 The system displayed a form, Tax Override, when users selected Add To Favorites in the Actions menu on the Manual Check Entry form. (This favorite was still saved.) The system now only displays a banner, “Form added to favorites,” when users select Add To Favorites in the Manual Check Entry form.
PD-17237 The system allowed worksite managers to save information in the Payroll Control form without setting a date in the required Remote Cutoff Date field. This is fixed.
PD-17255 When users paid using a pay code set to Pay Code is Exempt from All Taxes on the Tax Exemptions form, the system calculated the Employer NM Assessment Fee even though there were no taxable wages. This is fixed.
PD-17311 The system displayed a blank payday notification when the Current Type in the Message Templates form was set to TEXT. The system now displays payday notifications that match the email template, with the pay details.
RRT-5794 The system did not display the pay rates for some commissioned employees in the timesheet and for the employee’s pay in the Time Sheet Entry form. (The system calculated the payroll without errors and created a zero voucher.) This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202409/General/Fixes_General_PrismHRP_QR202409.htm Path: PD/Release-Notes/Fixes/2024/QR202409/General/Fixes_General_PrismHRP_QR202409.htm

General Fixes

Jira # Issue Summary Resolution
PD-14382 The system displayed the Add to Favorites option on the Actions menu in the Commission Maintenance form even though the current user already set the form as a favorite. This is fixed. Only the Remove from Favorites option now displays in this scenario.
PD-16457 Worksite trusted advisors were unable to access the same Data Retriever Benefits and Salary History as a worksite manager with the same user role. This is fixed.
PD-16471 Worksite managers were unable to view leave requests in the Planned Time Off Requests form when they were logged in at the same time a service provider proxied in as that worksite manager. This is fixed.
PD-16994 Worksite managers and worksite trusted advisors were allowed to enter a Work Group, Location, Department, or Division in the PTO Auto-Enrollment Rule Maintenance form that they were not allowed to access. This is fixed.
PD-17085 An error message displayed when users selected the User Fields option on the Actions menu in the Employee Details form. This is fixed.
PD-17091 Only one status code displayed in the Termination Status field even though more than one status code shared the same full description and abbreviated description. This is fixed.
PD-17115 The Delete button was enabled for users whose user role was set to Inquiry mode for the Employer Details form. (Note: The system did not delete the record in this scenario.) The Delete button is now disabled in this scenario.
PD-17227 The system did not display a scroll bar in the User Fields form, so users were unable to access all available user-defined fields. The appropriate error message now displays in this scenario.
PD-17243 The values in the ZIP Code, City, County, and Geocode fields on the Address tab in the Employee Details form reverted to their previous values after users clicked Close in the Select Geocode window. (Note: This also occurred in the Latitude and Longitude fields on the Worksite Locations form.) This is fixed.
PD-17272 The system displayed an error message when users processed backdated leave requests if the Other Income field on the Tax tab in the Employee Details form listed an amount. This is fixed.
PD-17299 The system added default timesheet hours to an employee’s record when a future pay rate history adjustment was made in the Pay History Adjustment form. This is fixed.
PD-17339 Error messages in the Employer W/C Accrual Modifiers form did not display in a consistent format. The error message now includes the line number, column number, and error message details.
PD-17350 After users deleted a client in the Delete Pending Client form, worksite managers and worksite trusted advisors with access to that client could still view it in the Current Access panel on the Users form. This is fixed.
PD-17433 The Employee Fields Import form did not retain decimal points in the spreadsheet when it pulled data from the Default T/S Hours field on the Pay tab in the Employee Details form. This is fixed.
PD-17523 The system displayed the original total on the invoice after recalculating payroll for users who selected the Create REAL Invoice Breaks option on the Billing tab in the Client Details form. This is fixed.
PD-17552 The system did not display an error message when users did not have access to the client based on Client Access Group security settings when they either entered or selected a client in the Cash Receipts form. An error message now displays in this scenario on the Cash Receipts form and during the import process.
PD-17610 The system displayed an error message, “User is already assigned as a primary,” only for the Payroll and Human Resources Account Assignment Roles when users entered the same service provider user ID for the same role as a Backup Account Assignment role. The system now displays that error message for the following Account Assignment Roles: - Benefits - Risk - Sales - Coordinator - Broker - I-9 Approver

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202409/Payroll/Fixes_Payroll_PrismHRP_QR202409.htm Path: PD/Release-Notes/Fixes/2024/QR202409/Payroll/Fixes_Payroll_PrismHRP_QR202409.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-13566 The Restartable Payroll process did not clear initialized vouchers when it returned to the timesheet entry, which created a deadlock condition when an employee existed in two payrolls, particularly if that employee switched to a new pay group. The system now displays an error during the Restartable Payroll process when an employee is already being paid by the company while in a payroll with a status other than TS.ENTRY, TSOKCOMP, TS.READY, or COMP.
PD-14846 A duplicate Okay to Rehire field labeled as “New Type” displayed for approval-pending employee terminations on the Approval form, when accessed from the Approvals Pending form. The New Type field no longer displays in this scenario.
PD-15269 The XLS output in the confirmation report for imports using the Data Import Tool did not match the on-screen output. This is fixed.
PD-17135 The system assigned an incorrect pay period from the Pay Period field on the Pay tab in the Employee Details form when changing an employee to a different pay group on the Mass Change Pay Group form. This is fixed.
PD-17278 Users were able to reprint a voided third party check in the Third Party Check Posted Batch form. The Show Batch Accounting, Reprint Checks, and Remit Advice Report buttons are now disabled for voided batches.
PD-17325 When users imported changes to an existing rule in the Unbundled Billing Rules Import form, blank fields indicated “Value Removed” regardless of whether or not the field was already blank. “Value Removed” only displays if the system actually removes/clears the field in the transaction report.
PD-17360 The system displayed blank pages in the middle of data when users printed the Fax Back Report or converted it to PDF format for printing. This is fixed.
PD-17384 Users were able to exit the Payroll Reversal process before it finished by clicking the Close (X) button, so they did not answer all the void questions as part of this process and did not view any errors or warnings that might have displayed. The Payroll Reversal form no longer displays a Close (X) button, so users can only close this form after the process is complete.
PD-17403 A blank green bar displayed on the SuperBatch form when a service provider or worksite manager approved a payroll. The following now occurs: - When a worksite manager or worksite trusted advisor approves a payroll from the Approvals Pending form, a blank green bar no longer displays. - When a service provider approves a payroll in the SuperBatch form by clicking the Ellipsis icon and selects Payroll Approval, a blank green bar no longer displays.

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202411/General/Fixes_General_PrismHRP_QR202411.htm Path: PD/Release-Notes/Fixes/2024/QR202411/General/Fixes_General_PrismHRP_QR202411.htm

General Fixes

Jira # Issue Summary Resolution
PD-14919 The system did not validate the Ethnic Code description on the EEO Ethnic Codes form, which displayed an error message on the Personal Info page in Employee Portal when no Ethic Code description was saved. The Ethnic Code field is now a required field.
PD-17522 The system displayed an extra period in the HOME.PHONE2 field for the Prism-Expanded Field Mapping ID when it was imported using the New Employee Import form. This is fixed.
PD-17795 PTO approvers who are worksite managers displayed as Last Name First Name in the PTO Approver column in the Data Retriever output report. These PTO approvers now display as First Name Last Name in the PTO Approver column.
PD-17800 The system did not redisplay unposted payrolls in the Cash Receipts form when users clicked Clear. This is fixed.
PD-17869 The system displayed an error in the Total Compensation Dashboard when users accessed an employee who was enrolled in an ancillary plan, even after they added the missing Benefit Plan ID. This is fixed.
PD-17976 The system did not clear the Last Billed Date in the new client when an employee was transferred using the Transfer Employee to New Client form. Instead, the system copied the date from the previous client. This is fixed.
PP-1532 When two users ran the ACA Third Party 1095 Export process at the same time for different clients, the process could mix the data and include results for both clients in a single download. This is fixed.
PP-1656 If an employee’s preferred first name included special characters, an error occurred when attempting to access the employee’s Time Sheet. This is fixed.
PP-1678 When an incorrect client number was added to an employee record, the employee no longer displayed in search results. This is fixed.
PP-1694 When a user attempted to view a voucher on the Employee Payroll Vouchers selection form for the Employee Details form, the first time the user selected the voucher, it did not display. Selecting the voucher a second time displayed the voucher successfully. This is fixed.
RRT-5944 If users had more than one user role, Custom Field Security Settings sometimes did not work correctly. This is fixed.
RRT-5953 The Informer row filter prevented users from viewing reports that listed closed/approved payroll calculations made by service providers even though they had access to the associated forms. This is fixed.
WSP-546 The background process updated several deduction codes even though users didn’t initiate the changes. The audit log no longer displays these updates.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2024/QR202411/Payroll/Fixes_Payroll_PrismHRP_QR202411.htm Path: PD/Release-Notes/Fixes/2024/QR202411/Payroll/Fixes_Payroll_PrismHRP_QR202411.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-17065 The system disabled the Save button on the Manual Check Entry form when users zoomed in or out of the browser window after selecting Calculate Totals. This is fixed.
PD-17442 After filtering the Unpaid Employees Report by Employee Type, that type did not stay in place after running and then closing the on-screen report. This is fixed.
PD-17543 The system successfully imported an event code that was attached to a bill code that did not exist in the Account Template in the PEO Client Accounting form when using the Miscellaneous Invoices import template. The system now displays an error message if the import cannot succeed because the event code is attached to a bill code that does not exist in the Account Template.
RRT-5881 The system did not create an invoice for a credit when a voucher was reversed. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/MR202501/General/Fixes_General_PrismHRP_MR202501.htm Path: PD/Release-Notes/Fixes/2025/MR202501/General/Fixes_General_PrismHRP_MR202501.htm

General Fixes

Jira # Issue Summary Resolution
PD-17719 An approved leave request displayed as paid in the Planned Time Off Requests form in the following scenario: - PTO Absence Code had Auto Accept enabled or disabled. - Employee in the payroll had an approved leave accepted in the timesheet before calculation. - After payroll calculation, the same employee then had another leave submitted and approved for the same pay period. - The payroll was finalized. - The leave that was requested and approved after the payroll calculation displayed as paid in the Planned Time Off Requests form, but it was not paid to the employee. (The timesheet and voucher did not display that the PTO was paid.) The approved leave request does not display as paid in the Planned Time Off Requests form in this scenario.

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/MR202501/Payroll/Fixes_Payroll_PrismHRP_MR202501.htm Path: PD/Release-Notes/Fixes/2025/MR202501/Payroll/Fixes_Payroll_PrismHRP_MR202501.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-16299 The system displayed a warning that there was a duplicate holiday date when users clicked Tab in the Holiday Date field on the Payroll Holidays form to add a new date. This is fixed.
PD-17620 The system did not display a warning when users entered Hours Paid in a Detail or Summary Time Sheet Entry for an absence pay code that exceeded the value entered in the Maximum Hours That Can Be Used in a Block field on the PTO Benefit Plans form. The following warning now displays and the system removes the entered hours if you exceed the maximum hours, “Maximum number of hours for this leave cannot be greater than .”
PD-18104 The system did not use the higher overtime rate calculation based on the employee’s prevailing wage or the employee’s rate when importing pay with the OTPREVAILINGWAGE custom feature code enabled. > Note: Note: This scenario did not apply during manual pay imports. This is fixed.
PD-18278 The system did not allow users to assign deduction codes to a percent of earnings calculation method in the Deduction Codes form. A new option, % of Earnings, now displays in the Calculation Method field so users can apply deductions codes to this calculation method.
PD-18340 When users deleted a column from the Unbundled Billing Rules Import file and subsequent columns in the file did not contain any data, the system did not import the billing rule (as expected) but no error report displayed and the Transaction Report recorded that it was saved. The Transaction Report records that the billing rule was skipped and creates an error report.
PD-18343 When pay codes included the Round to Period Pay if Salaried Employee option set in the Pay Codes form, the Time Sheet Report did not include the rounded values during payroll processing. This is fixed.
PD-18519 When users set up suppression on an Employer FUTA while importing in the Check History Import form, the system incorrectly generated vouchers with pre-tax deductions for Employer FUTA for employees with pre-tax deductions. When suppressing Employer FUTA during an import in the Check History Import form and the import file includes employee pre-tax deductions, the system prevents the calculation of any employee 00-17 tax entries for all employees, including those with pre-tax deductions.
PD-18628 The system displayed an error message when users ran the Pay Schedule Report for a 2025 pay schedule set to the pay period of Monthly (find last occurrence of day of week in month). (No error message displayed when users ran the report for a 2024 pay schedule set to Monthly.) This is fixed.
RRT-5810 The system changed an employee’s default hours to zero (0) on the timesheet after users updated an employee’s tax withholding form in the Employee Portal when the payroll was in the Payroll Calculation Ready state. This is fixed.
RRT-6092 Users were unable to void a converted check while reversing an employee voucher in the Employee Payroll Voucher Reversal form even though they acknowledged it as a converted check and that no billing would be generated. This is fixed.
WSP-772 The Pay Group fields remained on the Payroll Approval form after users submitted an approval. This is fixed.
WSP-1070 The system displayed validation errors in the Payroll Validation Report for benefit plans that had the One Month Prepay field selected on the Benefit Plan Setup form, but the Require Prepay Benefit Account No. field was not set on the System Parameters form. This is fixed.
WSP-1108 The system updated the Last Pay Period Hours field on a timesheet even though the employee termination process failed for an employee with a type that did not allow for termination. This is fixed.
WSP-1124 Users could not close the Recalculate Tax on Vouchers History form by clicking the Close button. Instead, they had to click the “X” button in the form to close it. Additionally, after closing the Recalculate Tax on Vouchers History form the Reporting Entity field no longer displayed any options, so users were unable to use this form until they cleared it by clicking Cancel. This is fixed.
WSP-1149 The system did not display a message in the table on the Confirm Pending Reversal Global form after the process finished running but there were no records to display when users entered dates and selected Find Employees. A message now displays, “No records found.”
WSP-1294 The system was previously updated to prohibit adjusting more than one school district at a time on the Tax Adjustment Import form, but this validation was never implemented. The system now validates that users can only adjust one school district at a time and displays an error message if they try to adjust more than one at a time.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/MR202502/General/Fixes_General_PrismHRP_MR202502.htm Path: PD/Release-Notes/Fixes/2025/MR202502/General/Fixes_General_PrismHRP_MR202502.htm

General Fixes

Jira # Issue Summary Resolution
PD-18836 The system did not display a warning message when users selected the Prior Year Accrual option in the Trigger Method field on the PTO Register Types form and saved the record. In this scenario a warning message now displays, “Warning: This trigger method will only work with linked accruals.”
RRT-6114 When users selected External W-2 Benefit Import from the W-2 Processing\ W-2 Processes menu an error message displayed, “Cannot find the data file in the IMPORT.DATA directory. This is fixed.
RRT-6128 When users made a future-dated position change for employees, the system pulled the change into the timesheet when processing a pay import. This is fixed.
RRT-6142 The system displayed the “Please wait” message when users tried to generate the PEO Client Accounting G/L Detail Report, which prevented them from running this report. This is fixed.
RRT-6168 The system did not populate the Prenote Date on the Deposit tab in the Employee Details form after users added a Direct Deposit in Employee Portal. This is fixed.
WSP-1076 Users were unable to view employee details after selecting the Employees Assigned To option on the Actions menu in several forms because the links that displayed in the Employee ID column were not accessible. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/MR202502/Payroll/Fixes_Payroll_PrismHRP_MR202502.htm Path: PD/Release-Notes/Fixes/2025/MR202502/Payroll/Fixes_Payroll_PrismHRP_MR202502.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-15126 When users entered a negative tax adjustment for an Employer Paid tax in the Tax Adjustments form with the Corporate option selected as the Product Version, the Accounting tab on the adjustment voucher displayed two debits instead of a debit and a credit. This is fixed.
PD-18944 When users enabled the Round to Period Pay If Salaried Employee field on the Pay Codes form for the pay code listed on the timesheet, the system displayed negative or incorrect amounts in the Time Sheet Report for some of the salaried employees listed under the flagged codes. > Note: Note: The vouchers displayed the correct amounts. This is fixed.
WSP-1189 Users who were logged in as a service provider with Full access to the SuperBatch form but were not the assigned payroll processor were unable access the user ID/name of users with the Payroll Processor (Print/Mail) Account Management Role who had active payrolls to print when using the Payroll Processor option on the Superbatch form. This is fixed.
WSP-1340 The system validated the Client Accounting template setup for Deduction Codes that did not have a Rebate Bill Code configured on the Deduction Codes form when users ran the Payroll Validation Report, which produced false errors. If there is no Rebate Bill Code for the Deduction Code, the system now skips validating the accounting in the client template when users run the Payroll Validation Report.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/QR202503/General/Fixes_General_PrismHRP_QR202503.htm Path: PD/Release-Notes/Fixes/2025/QR202503/General/Fixes_General_PrismHRP_QR202503.htm

General Fixes

Jira # Issue Summary Resolution
PD-17700 An error message displayed asking users to save changes when they accessed the Benefits or Payroll tab on the Client Details form and then clicked the Client Status icon on the Detail tab, but no changes were made. The error message now displays as “Updates have been made to Client Details which can include system default values for new fields added to the form.” Users must save updates in the Client Details form before they are allowed to change the Client Status.
PD-18065 When an employee record had an associated Manager listed on the Work tab in the Employee Details form, the system displayed information from the Manager’s employee record in the Local Tax Filings panel on the non-manager’s Tax tab. (This continued occurring even when users attempted to clear the rows in the Local Tax Filings panel.) This is fixed.
PD-18067 When users clicked the edit icon for the line description in the Billing Formats form that did not already have an associated bill code, the system displayed a dialog box, “There are no bill codes for this item. Please select a bill code.” However, after they tried to sort by the bill code or description, the system displayed an error. This is fixed.
PD-18108 Selecting the Division Code field in the Divisions form displayed obsolete codes in the selector list when the Obsolete field was set to No and users sorted that list. This is fixed.
PD-18113 When users ran ACH processing for a payroll where the ACH Originator Third Party Download was set to Wells Fargo and the PC File Name field contained an entry, the system produced an ACH file for download that still reflected the naming convention that used the PRISM placeholder value of the configured PC filename value (that is, PRISM_….txt). The system now produces an ACH file for download that contains the PC filename used in the ACH Originator configuration.
PD-18444 When configuring a user in the Users form, if users entered an employee ID prior to selecting the User Type as a Worksite Trusted Advisor, the system changed the Employee ID field to a read-only field. However, the employee ID remained in the field and the user record was saved with the employee linked to the worksite trusted advisor. After selecting the Worksite Trusted Advisor as the User Type, the system clears any value entered in the Employee ID field and changes that field to a read-only (non-selectable) field.
PD-18457 When users posted cash receipts in the Cash Receipts Import form, the system ignored the Bank ID values on each row and only read the first Bank ID in the import file, which resulted in inaccurate cash postings as well as downstream impacts on the G/L related to using the incorrect bank account used for postings. When posting cash receipts using the Cash Receipts Import form, the system posts all rows to the bank account identified in the Bank ID column of the first row in the import. In addition, text now displays on the Cash Receipts Import form, “This import does not support multiple Bank IDs. The Bank ID in the first row of the import file will be used for all cash receipts in the import file.”
PD-18492 Users were able to enter more than the maximum number of bank accounts allowed for an employee’s direct deposit on the Deposits tab in the Employee Details form. An error now displays in this scenario, “Employee has Active Bank Accounts, the Maximum Allowed is .”
PD-18556 The system accrued PTO for an employee on an Arrearage voucher when the Accrue on Arrears field was disabled and the Calculation Basis field was set to Flat Amount on the PTO Benefit Plans form. This is fixed.
PD-18637 When the Mobile Phone field on the New Hire form was set to required for Standard New Hires and the HOME.PHONE2 column in the import file was empty, the system populated the HOME.PHONE.2 column with the Employer ID. If users then tried to manually update the mobile phone number, the system displayed an error message during a New Employee Import. The result was that the column header in the Import Corrections Step displayed HOME.PHONE.2, but the Prism-Expanded template used for the import displayed HOME.PHONE2 (no second decimal point). In this scenario, users can now enter a valid mobile phone number. In addition, the system now displays HOME.PHONE2 in the column header in the Import Corrections Step.
PD-18644 The system displayed an error message when users ran the Employee Total Compensation Report for Benefit Plans that were added to the Total Compensation Report Setup form in the seventh or eighth columns in the Benefit Plan Allocation panel. The Employee Total Compensation Report now displays the code information added in the seventh or eighth columns.
PD-18744 The Number of Hours values on the File Audit form, which are accessed by selecting Audit on the Actions menu in the Auto Holiday Pay Rule Maintenance form, did not display a decimal point. This is fixed.
PD-18788 The wrong selector displayed when users selected the Candidates option on the Actions menu in the New Hire form. This is fixed.
PD-19074 When a backdated leave request was submitted for multiple days, the system created the voucher as expected but only the first date of the date range displayed as Paid. (The other dates did display the backdated leave requests and the planned time off requests did display the leave request as Approved, but not Paid.) When users submit a backdated leave request for multiple days, the following now occurs: - The planned time off requests display the date range as Paid and the system applies the voucher to all dates in the range. - The system does not display the dates that were processed for backdated leave requests.

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/QR202503/Payroll/Fixes_Payroll_PrismHRP_QR202503.htm Path: PD/Release-Notes/Fixes/2025/QR202503/Payroll/Fixes_Payroll_PrismHRP_QR202503.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-17124 When the Payroll Allocation Report was sorted by Division and the Group by Employee ID field was enabled, the report output only included the hours and wages allocated to the employee’s home division. In addition, when the Group by Employee ID field was disabled, the report output included a column for the allocated divisions, and reported all divisions where the employee had allocated hours. When the Group by Employee ID field is enabled, all Primary Sort options now include all hours and wages for the employee in the report output, not just the ones allocated to their home department, division, and so on.
PD-17888 When users set the Status to One Time on a Scheduled Payment and the system calculated the payroll, the Gross Earnings, Taxes, Deductions, Net Pay, Check Amount, and Deposit Amount on the Payroll Summary form all displayed as 0.00, which was an incorrect amount. However, the Payroll Summary Report run from the Payroll Summary form displayed the correct amounts. This is fixed.
PD-17900 The system displayed the end of the timesheet incorrectly when columns were hidden on the timesheet and users moved between pages. This is fixed.
PD-17906 The system did not display the most current Minimum Wage rate on the State Rules in the Payroll Validation Report. This is fixed.
PD-17909 When users changed an employee’s employer and then attempted a tax adjustment import for their previous employer, the system generated an error message that the employee did not work for that employer. > Note: Note: This scenario does not apply to adjustments made using the Tax Adjustments form. This is fixed.
PD-17983 When users accessed the New Pay Rate Assignment form from the Time Sheet Entry form for an employee with a pending pay rate change and clicked the menu headers, the system incorrectly changed the value that displayed in the Hours column. > Note: Note: This was only a display issue because the correct REG and O/T hours displayed in the initialized voucher. This is fixed.
PD-17993 An extra column without any detail displayed in the XLS output for any Compact Report format in the Payroll Register Report. This is fixed.
PD-18106 Users had difficulty making timesheet entries using the Pivot By function and the Return button in the Detail Time Sheet Entry form. This is fixed.
PD-18124 Users whose user role was set to DENY access on the Voucher tab on the Payroll Voucher form (process ID EMPLOYEE.PAYROLL.VOUCHERS*INQ.VOUCHER) were able to select a voucher to access employee vouchers from the following forms: - Payroll Summary - Employee Payroll Vouchers - Payroll Summary With Paging This is fixed.

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202504/General/Fixes_General_PrismHRP_R_202504.htm Path: PD/Release-Notes/Fixes/2025/R202504/General/Fixes_General_PrismHRP_R_202504.htm

General Fixes

Jira # Issue Summary Resolution
PD-18796 If the Maximum Number of Bank Accounts Allowed field was set to blank/null in the Direct Deposit Form Settings form and users tried to save an employee record in the Employee Details form when the employee had no direct deposit information listed in the Deposit tab and they made an update or clicked Save, the system displayed an error message. This is fixed.
PD-18821 The system used the payroll’s Period End Date as the “date” for the transfer of hours on the Employee PTO Register instead of using the Year End Date to match the date for the Carryover hours. This is fixed. In addition, the following now occurs: - The “annotation” on the accrual Employee PTO Register for the transfer of hours now includes the Year End Date. - During the transfer/carryover process, a “0.00” Hours Calculated entry does not display on the Balance register. - The system now displays the transfer of hours as the Hours Accrued on the voucher for the balance register.

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202504/Payroll/Fixes_Payroll_PrismHRP_R202504.htm Path: PD/Release-Notes/Fixes/2025/R202504/Payroll/Fixes_Payroll_PrismHRP_R202504.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-18442 The system did not update Third Party Sick Pay voided adjustments in the Payroll Adjustments file when they were voided using the Employee Payroll Voucher Reversal form, so those voids were not included in the Third Party Sick Pay Report. These voided adjustments now display as a negative amount in the Third Party Sick Pay Report.
PD-18612 The system display ed an error and then terminated the session when users entered certain special characters, such as the left angle bracket (<), when they created a payroll note in the Payroll Notes form. > Note: Note: New hires entered manually were not affected by this scenario. The system now accepts all special characters when creating a payroll note in the Payroll Notes form.
PD-18859 When users updated the units in a detail timesheet using a unit pay code, the system incorrectly updated the entry in the Hours Worked field. This is fixed.
PD-19006 The system did not allow users to import stand-alone, miscellaneous charges using the Miscellaneous Invoices import template in the Data Import Tool when the bill code was not set up on a PEO Client accounting template even though it was set up on a related Global PEO accounting template. This is fixed.
PD-19223 The system displayed Admin Fees for ASO clients in the Payroll Check Journal Report. This is fixed.
PD-19255 The system did not save the second and subsequent entries in the Detail Time Sheet Entry form when an employee’s Pay Method was set to Variable Salary on the Pay tab in the Employee Details form. > Note: Note: This issue occurred when users entered a Pay Code that was marked as Variable Salary and another Pay Code that was not marked as Variable Salary. This is fixed.
RRT-6178 When there were multiple Flex account deductions on the voucher and the HSA deduction was not listed first, the system assigned the wrong G/L account to the HSA deduction. This is fixed.
RRT-6201 The system did not capture Employee Direct Deposit updates when the status changed during payroll calculation. This is fixed.
WSP-1326 The Payroll Delivery Sheet that had a Delivery Method override set up for the payroll on the Payroll Options form, which is accessible by selecting Options on the Payroll Control form, did not display the correct delivery message. Instead, the delivery message displayed the delivery Method selected on the Company Delivery Methods form, which is accessible by selecting Special Delivery on the Actions menu from the Payroll tab on the Client Details form. The system now displays the delivery message specified on the Payroll Options form.
WSP-1400 The system did not display the most current list of Payroll Processors with open payrolls in the SuperBatch form when users with an open session clicked the Refresh Batch Report and Filters/Settings icon, even when another user assigned a payroll to a Payroll Processor not previously listed in the filter list of Payroll Processors. If there is no Rebate Bill Code for the Deduction Code, the system now skips validating the accounting in the client template when users run the Payroll Validation Report.
WSP-1527 The system displayed an error message about a missing post-tax deduction code when users ran a payroll for an employee with post-tax deductions related to benefits enrollment, even though the configuration correctly reflected the post-tax deduction code. This is fixed.
WSP-1785 The system did not display check counts correctly on the Payroll Delivery Page for payrolls that included a manual check. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202505/General/Fixes_General_PrismHRP_R_202505.htm Path: PD/Release-Notes/Fixes/2025/R202505/General/Fixes_General_PrismHRP_R_202505.htm

General Fixes

Jira # Issue Summary Resolution
PD-18822 The system included multiple checks for the same pay date into one value in the Summary and Detail versions of the Global Payroll Deduction by Date Report, but listed both checks. (This created issues with the XMLS download, which displayed one row per check with the total from the pay date.) The system now displays the amount associated with each check number in the Summary and Detail versions of the Global Payroll Deduction by Date Report, and its Excel version, regardless of the pay date.
PD-19219 When cash earnings were insufficient for all tax amounts, the system did not prioritize Federal Income Tax (FIT) over State Income Tax (SIT) when the Adjust Taxes to Cover Cash Shortfall field was set to Adjust taxes after deductions on the Payroll tab in the Client Details form. The system now prioritizes Federal Income Tax (FIT) over State Income Tax (SIT) when cash earnings are insufficient for all tax amounts, regardless of the Adjust Taxes to Cover Cash Shortfall setting.
PD-19404 The system did not complete the Direct Deposit Prenote in ACH text file or ACH detail report when the account was deactivated and then reactivated. This is fixed.
PD-19414 The system displayed an incorrect amount of Approved leave for the Leave Type in the Leave Approval form. This is fixed.
PP-1837 When a user attempted to save edits on the User Roles form, and the Role ID field was blank, an incorrect record with a User ID of ROLE was created. This is fixed. If the Role ID field is not valid, the record is not saved, and the system displays a message instructing the user to add a Role ID.
PP-1865 When a Service Provider performed a register rebuild for the Tax Register or Federal Tax Register on the Register Rebuilds form, the form experienced significant performance issues, and the rebuild ran for an extended period of time. This is fixed.
PP-1871 When a user deleted existing payroll batches and created a new batch, the Processing History form displayed the wrong User ID for the record of that action. This is fixed.
PP-1873 When a Service Provider used the Quarterly Tax Summary form with a large number of records, the form experienced significant performance issues. This is fixed.
PP-1874 When a user resized the browser on the Employer Details form in Prism, the entries listed in the State Tax ID Numbers section of the form disappeared. This is fixed.
PP-1877 When a user attempted to run the Worksite User Data Security Download, and at least one user record on the report had a large number of roles, the report did not run successfully. This is fixed.
PP-1881 When a user resized the browser with the Action menu displayed in Prism, the Action menu items disappeared and left a blank menu box. This is fixed.
RRT-6268 The system displayed an incorrect warning message when users saved an employee record in a specific way after making a change. This is fixed.
WSP-1727 The system did not calculate the Pending Adjustment Balances as expected when users made an update to a PTO Benefit Plan and ran the PTO Accrual Recalculation process. This is fixed.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202505/Payroll/Fixes_Payroll_PrismHRP_R202505.htm Path: PD/Release-Notes/Fixes/2025/R202505/Payroll/Fixes_Payroll_PrismHRP_R202505.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-18809 When there were multiple payrolls to approve on the Payroll Approval form and users entered a different Payroll Number than the default payroll number that displayed, accessing the Gross-to-Net Register Report from this form displayed the default payroll number instead of the number they entered. The payroll number users enter on the Payroll Approval form now displays when they access the Gross-to-Net Register Report.
PD-19023 The system changed the MEMO-OFFSET Bill Code in the PEO Client Accounting form to an incorrect value when users regenerated PEO Client Accounting in the Regenerate Client Accounting form. This is fixed.
PD-19189 Users were able to add the Payroll Reports form as a favorite even though the Payroll Reports form cannot be directly accessed. The Add to Favorites option no longer displays on the Actions menu for the Payroll Reports form. In addition, you cannot add the HRPY.WORK*PAYROLL.REPORTS process ID to a user’s favorites or to the Template ID field on the Favorites Template Import form.
PD-19220 The system did not display the Charge Date on a voucher accessed on the Pay tab in the Payroll Voucher form when the Pay Code was set to the Per Diem calculation method. This is fixed.
PD-19412 The system did not display Employer Contribution amounts for employer taxes on the Payroll Check Journal Report when ASO clients were set up to not bill employer taxes. This is fixed.
PD-19427 The system did not display all initialized payrolls in the Payroll Variance Analysis form. Users can now review payrolls in the Payroll Variance Analysis form once they have been initialized and before they are sent for approval from SuperBatch.
WSP-1804 The system incorrectly displayed a penny ($0.01) variance in the Net Pay value in the Payroll Summary Report and the Payroll Summary form. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202506/General/Fixes_General_PrismHRP_R_202506.htm Path: PD/Release-Notes/Fixes/2025/R202506/General/Fixes_General_PrismHRP_R_202506.htm

General Fixes

Jira # Issue Summary Resolution
PD-18699 The system automatically enrolled rehires with a future dated rehire date into a leave plan using their last hire date as the benefit start date instead of their future dated rehire date when the Auto Enroll rules were set up to use the Rehire Date on the Rehire form. The system now automatically enrolls rehires with a future dated rehire date in a leave plan using their future rehire date as the benefit start date when the Auto Enroll rules are set up to use the Rehire Date on the Rehire form.
PD-18922 The system displayed employee amounts in the Employee Total Compensation Report for worksite managers and worksite trusted advisors who did not have access to employees due to data entity security restrictions. > Note: Note: They were unable to view employee information in this scenario. This is fixed.
PD-19416 The system did not recognize the Linked Accrual plan year for PTO taken by an employee when the plan year was set to Anniversary and the time off was taken during the Anniversary pay period. The system now follows these steps: 1. Deducts hours used in the plan year 2. Applies Carryover 3. Transfers Hours between plans 4. Accrues 5. Deducts hours used in the NEW plan year
  1. Deducts hours used in the plan year
  2. Applies Carryover
  3. Transfers Hours between plans
  4. Accrues
  5. Deducts hours used in the NEW plan year | PD-19544 | The system did not create a prenote in the ACH file when users inactivated a direct deposit account that had a remaining balance and added another account that was set to prenote and the Remaining Balance account was set to Inactive before saving. | This is fixed. | | PP-1110 | When viewing the 1099 and W2 forms, if fields with the same name on each form featured a dropdown box selection, the options from the first form displayed on the second form. | This is fixed. | | PP-1223 | When a user accessed the Direct Deposit form, fields that should have been hidden due to their field-level security still displayed. | This is fixed. | | PP-1545 | When an invoice was processed with External Invoice Posting, the Process Control Dashboard did not change the job to a completed status. | This is fixed. | | PP-1762 | When a user ran the Department Codes report from within the Client Details form, the report ran properly, but attempting to exit the Client Details form resulted in an error message. | This is fixed. | | PP-1855 | When a user collapsed certain elements on pages throughout Prism, the collapsed sections did not align properly. | This is fixed. | | PP-1905 | When a user accessed the Delete Unused Employee form and switched to a different client, the current client number displayed differently than the client number the user was actually accessing. | This is fixed. | | PP-1912 | When a user attempted to run the Find Changes to a File Report for a client with many faulty file audit records, the process ran extremely slowly. | This is fixed. | | PP-1916 | When a user was designated as a backup assignment for a client access group, that user was not immediately granted access to the proper client assignments. | This is fixed. | ========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202506/Payroll/Fixes_Payroll_PrismHRP_R202506.htm Path: PD/Release-Notes/Fixes/2025/R202506/Payroll/Fixes_Payroll_PrismHRP_R202506.htm

Payroll Fixes

Jira # Issue Summary Resolution
WSP-2081 The system continued suppressing tax on payrolls after the indicated stop date when an employee was configured with a tax suppression on tax code 33-25. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202507/General/Fixes_General_PrismHRP_R_202507.htm Path: PD/Release-Notes/Fixes/2025/R202507/General/Fixes_General_PrismHRP_R_202507.htm

General Fixes

Jira # Issue Summary Resolution
PD-18915 When the payroll pay date occurred on a holiday on the first payroll of the year and the pay date was reverted to the prior year, if the payroll was recreated the deduction period changed to the new date instead of staying the same. This is fixed.
PD-19125 When users posted a payment to an invoice in the Cash Receipts form, the Amount and Total Allocated amounts changed to zero (0). This is fixed.
PD-19200 A few fields on the System Parameters form overlapped when some custom feature codes were enabled. This is fixed.
PD-19571 The system deleted an entire multi-entity group when users deleted a client in the Inactive Data Deletion form that was part of a multi-entity group. This is fixed.
PD-19609 The system did not automatically enroll rehires with a future dated rehire date in a leave plan if the PTO Auto Enroll Rule used an Employment Type that matched the future Employment Type instead of their current Employment Type. Rehires with a future dated rehire date are now automatically enrolled in a leave plan if the PTO Auto Enroll Rule uses an Employment Type that matches the future Employment Type.
PP-1223 When a user accessed the Direct Deposit form, fields that should have been hidden due to their field-level security still displayed. This is fixed.
PP-1949 When a user made a change to the Tax forms in Employee Portal, the File Audit for the change displayed erroneous information. This is fixed.
WSP-1904 A confusing error message displayed during PTO accrual recalculation for the current PTO Plan Year in the PTO Accrual Recalculate form when an employee’s PTO Register Year End Date preceded the Year End Date for the current year. An updated error message now displays in this scenario, “Date of recalculation adjustment is beyond current PTO Register Year End Date. skipped.”

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202507/Payroll/Fixes_Payroll_PrismHRP_R202507.htm Path: PD/Release-Notes/Fixes/2025/R202507/Payroll/Fixes_Payroll_PrismHRP_R202507.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-19513 Selecting the Compare to Payroll link on the Payroll Variance Analysis dashboard displayed the status of each completed payroll in the Batch Selection form as the status of the initialized payroll instead of the status for the payrolls shown. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202508/General/Fixes_General_PrismHRP_R_202508.htm Path: PD/Release-Notes/Fixes/2025/R202508/General/Fixes_General_PrismHRP_R_202508.htm

General Fixes

Jira # Issue Summary Resolution
PD-19032 Users were able to save information on the following tabs in the Employee Details form when they accessed it as a modal form and the selected employee had a status of “Onboarding in progress - Payroll suppress (save is disabled)”: - Personal - Address - Work - Pay - Tax - Deposit - Skills & Education - Property The Save button is no longer enabled in this scenario. Users must make employee updates in the Workflow Maintenance form when the employee’s status is set to “Onboarding in progress - Payroll suppress (save is disabled)”.

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202508/Payroll/Fixes_Payroll_PrismHRP_R202508.htm Path: PD/Release-Notes/Fixes/2025/R202508/Payroll/Fixes_Payroll_PrismHRP_R202508.htm

Payroll Fixes

Jira # Issue Summary Resolution
PD-19548 The system displayed a variance between Other Deductions on the Payroll Variance Analysis dashboard when there was no difference. The Deduction Variance in the Payroll Variance Analysis dashboard now displays differences in the initialized and posted vouchers in the Other and Third Party Deductions section.
PD-19611 Users who had Inquiry or Deny access to the Reprint Payroll Checks form but had Full access to the Payroll Reports form were unable to use the question mark (?) icon for all payroll reports instead of just reprint payroll reports. This is fixed.
WSP-1260 The system incorrectly handled time entries dated beyond the current regularly scheduled payroll in the Direct Pay Entry form, which created multiple manual payrolls with incorrect or missing period dates for future pay periods. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202509/General/Fixes_General_PrismHRP_R_202509.htm Path: PD/Release-Notes/Fixes/2025/R202509/General/Fixes_General_PrismHRP_R_202509.htm

General Fixes

Jira # Issue Summary Resolution
PP-1464 When a user ran the Company Register Rebuild, the VOUCHER.XREF data was not properly cleared. This is fixed.
PP-1884 When a user created a new department with the an ID ending in “e” followed by a number, ran the Department Codes report, and exported the report as an XLS file, the spreadsheet interpreted the code as an exponential number and produced an error. For example, “123e73” was interpreted as “123^73”. This is fixed.
PP-1890 When a user ran the Find Changes to an Employee report and exported the report as an XLS file, the Record ID column on the exported report dropped leading and trailing zeroes if the line didn’t contain alphanumeric characters. For example, “001234.567890 displayed as “1234.56789.” This is fixed.
PP-1996 When a user entered a number on certain fields on the Group Benefit Plans form, such as the Non-Taxable Limit field, then pressed Enter, the value was cleared. This is fixed.
RRT-6528 The system reported an incorrect Gross Wage amount for NC in the RT record in the NC SUTA tax export file when using the Employer Quarterly SUTA Tax Export form, which resulted in filing errors. The file now reports the gross taxable, net taxable, and excess wages correctly to allow filers to submit the NC SUTA export without error. > Note: Note: The Employer Quarterly SUTA Tax Export form for NC now correctly reports the RT record according to the specifications to include: - Positions 34-53, Total Gross Taxable Wages (Gross wages - sheltered wages) - Positions 54-73, Total Net Taxable Wages (currently correct) - Positions 74-93, zero fill (or gross taxable overlimit) - RF record positions 17 - 36 = Total of all RT records, positions 34 - 53, Gross Taxable Wages

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202509/Payroll/Fixes_Payroll_PrismHRP_R202509.htm Path: PD/Release-Notes/Fixes/2025/R202509/Payroll/Fixes_Payroll_PrismHRP_R202509.htm

Payroll Fixes

Jira # Issue Summary Resolution
RRT-6424 The system calculated the sales tax incorrectly when an unbundled billing rule was set to Flat Amount/Invoice in the Based On field on the Billing Rules (Unbundled) form. This is fixed.
RRT-6473 The system displayed an error message that did not clearly explain how to resolve the issue when users processed a payroll, “State income tax is being calculated for ST but a State Tax Number has not been setup on the Employer Details record for Employer ID XXX. State tax number must be setup for this employer before this payroll can proceed.” An updated error message now clearly explains how to resolve the issue, “State income tax is being calculated for ST but a State Tax Number has not been setup on the Employer Details record for Employer ID XXX. State tax number must be setup for this employer or income tax suppressed for employee AXXXX before this payroll can proceed.”
RRT-6475 The system still displayed voluntary deductions on the voucher that were entered on the Summary Time Sheet form after the deduction was deleted from the timesheet and the payroll was recalculated. > Note: Note: This issue did not apply when the deduction was mandatory and only occurred when using Restartable Payroll. This is fixed.
RRT-6503 The system failed validation during a Miscellaneous Invoice Import in the Data Import Tool if a bill code was used and either the bill code or an asterisk (*) was not found in the Other Bill Code field on the PEO Client Accounting form. This is fixed.

========================================================================

General Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202510/General/Fixes_General_PrismHRP_R_202510.htm Path: PD/Release-Notes/Fixes/2025/R202510/General/Fixes_General_PrismHRP_R_202510.htm

General Fixes

Jira # Issue Summary Resolution
PP-1654, PP-1659 When a user entered a New Transaction on the Retirement Plan Enrollment form for an employee using the Retirement Register Adjustment window, after selecting the Loan link, the Loan selector opened, however, the Retirement Register Adjustment window moved out of sight to the bottom of the screen. This is fixed.
PP-2016 When a user made changes to individual records on the Timesheet Detail form, pressing the Enter key did not save the changes. This is fixed.
PP-2025 When a user exported a Prism report, fields with a 0 were not properly exported in a Number format. This is fixed.
RRT-6507 The system populated OR PFML employee statistics with OR SUTA employee monthly counts, which sent invalid data to Mastertax RTS and created inaccurate reporting for customers. The system now zero-fills Mastertax RTS 501 record for tax code 38-40 (EE paid OR PFML) positions 67-80 and positions 81-94, whether Client or ER is reported.

========================================================================

Payroll Fixes

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Fixes/2025/R202510/Payroll/Fixes_Payroll_PrismHRP_R202510.htm Path: PD/Release-Notes/Fixes/2025/R202510/Payroll/Fixes_Payroll_PrismHRP_R202510.htm

Payroll Fixes

Jira # Issue Summary Resolution
WSP-2643 When an obsolete G/L template in a payroll was processed, the system displayed an additional error message in the Process Payroll form that there were no timesheets found in the payroll even though there were multiple employee timesheets entered. This is fixed.

========================================================================

New Completed Payroll Notes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202403/Client/New_Completed_Payroll_Notes_Form_QR202403.htm Path: PD/Release-Notes/New-Features/2024/QR202403/Client/New_Completed_Payroll_Notes_Form_QR202403.htm

New Completed Payroll Notes Form

A new form, Completed Payroll Notes, is now available on the Client|Action menu. For example:

[Image: screenshot]

You can use the Completed Payroll Notes form to review or track previously entered notes that are marked as completed using a date range that occurs within one year.

To search for completed notes by the date they were entered, simply enter or select the Start Date and End Date, then click Submit. (If you are searching for completed notes using a date range greater than one day, it must be within one year.) For example, the following completed payroll notes display for the date range 11/28/2022 through 11/27/2023:

[Image: screenshot]

After the list displays, you can view an existing completed note by clicking the Ref #.

Note: Note the following when working with the Start Date and End Date:

Adding the Completed Payroll Notes Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Completed Payroll Notes from the list. (To quickly find this item, select Company in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*COMPLETED.PAYROLL.NOTES from the Search Processes list. (To quickly find this item, enter Completed Payroll Notes in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHR Payroll Administration Guide.

JIRA # PD-16002

========================================================================

New Finalized Payroll Notes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202403/Client/New_Finalized_Payroll_Notes_Form_QR202403.htm Path: PD/Release-Notes/New-Features/2024/QR202403/Client/New_Finalized_Payroll_Notes_Form_QR202403.htm

New Finalized Payroll Notes Form

A new form, Finalized Payroll Notes, is now available by selecting a Ref # that displays in the Completed Payroll Notes form. (See New Completed Payroll Notes Form.)

You can use the read-only Finalized Payroll Notes form to view the details of a payroll note that is marked as completed, including who viewed the note. (The last line in the Viewed By section displays the person who completed the note.) For example:

[Image: screenshot]

For more information, see the in‑product help or PrismHR Payroll Administration Guide.

JIRA # PD-16059

========================================================================

New SuperBatch Process

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202403/Payroll/New_SuperBatch_Process_QR202403.htm Path: PD/Release-Notes/New-Features/2024/QR202403/Payroll/New_SuperBatch_Process_QR202403.htm

New SuperBatch Process

The enhanced version of the SuperBatch form/process is now available. This new interface includes updated icons, fonts, a payroll description, and filters. For example:

[Image: screenshot]

To distinguish between the original version and the enhanced SuperBatch form, which resides on the Operations|Action menu, the original SuperBatch form name now displays as “SuperBatch Legacy” in the system.

Note: Note the following:

[Image: screenshot]

Using the Filtering Options

You can use the filtering options in the enhanced version of SuperBatch to limit the payrolls that display:

Note: Note the following:

The icons in the top-right corner of the SuperBatch form help you perform the following actions:

Icon — Description

Payroll Transfer [Image: screenshot] — Displays the SuperBatch Payroll Transfer form, where you can transfer all currently viewed payrolls or selected payrolls to another payroll processor. (Select the payroll processor and click Update.) Note: If you select multiple payrolls and then click this icon to change to a new payroll processor, only the payrolls you selected are updated, not those in the entire view.

Filter Selection [Image: screenshot] — Displays a search form, where you can enter information to narrow the payroll assignments that display. (Enter the search information and click Apply.)

Refresh Existing Filter [Image: screenshot] — Refreshes payrolls that display based on the existing user and selected filters/settings. Note: This filter can also act as a “reset” for payrolls.

Reset Filters [Image: screenshot] — If you filtered the payrolls to only display payrolls associated with a particular step, select this icon to refresh the display so all payrolls associated with the selected filters redisplay.

Working with the Ribbon

A ribbon displays the steps for the payrolls in-progress. For example:

[Image: screenshot]

Note: Each step displays the number of payrolls associated with it.

To further filter the payroll display, click a step in the ribbon to display all the payrolls in that step. (Some of these filters can include several statuses, which you can select as a group or individually.) For example, clicking Ready for Time Entry in the example above displays the payrolls matching that criteria:

[Image: screenshot]

Note: A right-angle arrow displays next to a step when you click it, so you can easily determine which step is selected in the ribbon.

Working in the Client Level Actions Area

You can easily access actions and reports, client and payroll details, and notes in the Client Level Actions area. For example:

[Image: screenshot]

To do this: Select this:
Access additional actions for selected client or payroll Ellipsis ( [Image: screenshot] ) icon
Access Client Details form displaying selected client’s details Client name or client ID
Access Payroll Control form displaying selected payroll’s details Payroll number
Access Payroll Notes form for selected payroll or create a new note Notes ( [Image: screenshot] ) icon

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-15857, PD-15858, PD-15859, PD-15861, PD-15863, PD-16287, PD-16288, PD-16301, PD-16302, PD-16423, PD-16525, PD-16726, and PD-16760

========================================================================

New Delete Imported Vouchers Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202403/System/New_Delete_Imported_Vouchers_Form_QR202403.htm Path: PD/Release-Notes/New-Features/2024/QR202403/System/New_Delete_Imported_Vouchers_Form_QR202403.htm

New Delete Imported Vouchers Form

A new form, Delete Imported Vouchers, now exists on the Operations|Utility Processing menu, so you can quickly delete vouchers that you imported using the Check History Import process. (Previously, users had to reach out to PrismHR Customer Support to complete this task.) For example:

[Image: screenshot]

Note: This feature is only available for service providers who have access to the payrolls that contain the voucher for deletion.

To delete imported vouchers, enter the Batch ID and click Delete. A warning displays:

[Image: screenshot]

Select Yes to delete the vouchers from the selected payroll.

Note: Only vouchers in completed payrolls can be deleted. If the voucher resides in a payroll that is not complete the following error displays, “Batch ID must be for a completed batch.”

Adding the Delete Imported Vouchers Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Delete Imported Vouchers from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select EMPLOYEE.PAYROLL.VOUCHERS*DELETE.VOUCHER from the Search Processes list. (To quickly find this item, enter Delete Imported Vouchers in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # PD-15872 and PD-16462

========================================================================

New Copy Client Settings Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202406/Client/New_Copy_Client_Settings_Form_QR202406.htm Path: PD/Release-Notes/New-Features/2024/QR202406/Client/New_Copy_Client_Settings_Form_QR202406.htm

New Copy Client Settings Form

A new form, Copy Client Settings, is now available on the Operations|Utility Processing menu. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

You can use the new Copy Client Settings form to copy client settings from one client to another.

To copy client settings:

  1. Enter or select the Copy From Client. The client’s name displays.

  2. Enter or select the Client ID in the Copy to Client panel. The Client Name displays.

  3. Deselect or select the attributes for this client in the What to Copy panel.

  4. Click Copy. The Existing Data panel displays existing client settings.

  5. Select the client settings to copy by selecting individual checkboxes or select the checkbox next to the File Copy column to select all settings.

  6. Click Update Existing. A warning message displays, “This process will override any existing records in the client. Are you sure you want to continue?” Click Yes to continue.

Note: Note the following:

Adding the Copy Client Settings Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The Copy Client Settings form displays.

  4. Select Copy Client Settings from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select COMPANY.MASTER*COPY.SETTINGS from the Search Processes list. (To quickly find this item, enter Copy Client Settings in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHR Client Administration Guide.

JIRA # WSP-304

========================================================================

New Employee Details Loans Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202406/HumanResources/New_Employee_Details_Loans_Form_QR202406.htm Path: PD/Release-Notes/New-Features/2024/QR202406/HumanResources/New_Employee_Details_Loans_Form_QR202406.htm

New Employee Details Loans Form

A new form, Employee Details Loans, is now available by selecting Loans on the Actions menu in the Employee Details form. For example:

[Image: screenshot]

Note: Previously, selecting Loans displayed the Employee Loans form, which did not display the loans for the selected employee.

Now you can easily view all the loans currently active for the selected employee by accessing the Employee Details Loans form. In addition, you can quickly set up a new loan by selecting the Loan Maintenance link on this form, which displays a blankEmployee Loans form where you can select Set up new loan and complete the loan details.

Note: Note the following:

Adding the Employee Details Loans Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Employee Details Loans from the list. (To quickly find this item, select HR in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select EMPLOYEE.LOANS*SHOW.ALL from the Search Processes list. (To quickly find this item, enter Employee Details Loans in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Employee Details Loans form, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-16507, PD-16528, and PD-16529

========================================================================

New Unbundled Billing Rules Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202406/System/New_Unbundled_Billing_Rules_Import_Export_QR202406.htm Path: PD/Release-Notes/New-Features/2024/QR202406/System/New_Unbundled_Billing_Rules_Import_Export_QR202406.htm

New Unbundled Billing Rules Import Form

A new form, Unbundled Billing Rules Import form, now resides on the Operations|Action menu. For example:

[Image: screenshot]

Note: This form is only available for service providers.

You can use the Unbundled Billing Rules Import form to import multiple unbundled billing rules for clients associated with a specific bill code.

Note: Client Access Group security is enabled on this form.

To import unbundled billing rules:

  1. Enter or select the Client IDs. (You can select multiple clients from the Select Clients list at once.) The Client Name displays next to each client. (If left blank, the system selects all clients.)

  2. Enter or select the Bill Codes. The Bill Description displays next to each client. (If left blank, the system selects all bill codes.)

  3. Select Download Spreadsheet. A progress dialog displays the processing steps.

  4. Click Close. A separate Downloads window displays the name of the .csv file that the system created. (Click Open file to view the downloaded file.)

Note: The first row in the downloaded file displays information about the first rule and the multi-value fields, which are separated by a pipe delimiter (|).

  1. If necessary, update the information in this spreadsheet before proceeding.

  2. Enter the Import Name.

  3. Select Upload File. Click Add Files and select the file to upload, then click Start Upload.

Note: The file must be in .csv format.

  1. Click Close. The uploaded filename displays.

  2. Click Import. A progress dialog displays the processing steps.

  3. Click Close.

  4. Click Transaction Report to display a link to a report that contains the unbundled billing rules transactions.

Note: The Transaction Report displays “Skipped” for any column in a row that has valid data but was not imported because a required row contained invalid data. (All invalid data displays in the Transaction Report.)

  1. Click Error Report to display a link to a .csv file that details the errors that occurred during the import. (The system does not import any rows listed in the error file and only imports rows where all data in the row is valid.)

Note: The Error Report link only displays if errors occurred during the import, which confirms that the system is unable to perform the import.

Note: Note the following:

Adding New Rules to an Import

Using the import process, you can define new rules that the system adds to the Billing Rules (Unbundled) form. To do this, you must enter the rule as NEW. For example:

Note: Note the following:

Define the following information for the import:

Field Details Description
Client ID Unique identifier for the client.
Rule This field is pre-defined. Note: If you create a NEW rule, the next sequential value is selected. Existing Billing Rule ID, or New Rule to create a new unbundled billing rule. The system automatically assigns an ID.
Rule Description This is a free-form field where you can enter the description. Describes the rule. (This description cannot exceed 40 characters.)
Rate Allows numeric value up to 4 decimal places. Billing Rate. The system uses this in conjunction with the Based On value.
Based On Codes used as basis for calculating unbundled billing rules. Based On value, which represents the logic to use when calculating the rate.
Rule Start Date Date format MM/DD/YYYY. Rule Start Date when this rule begins.
Rule End Date Date format MM/DD/YYYY. Rule End Date when this rule ends.
Voucher Types Allowed types: - R: Regular - V: Vacation - S: Supplemental - A: Arrearage - H: Adjustment > Note: Note: - If only Regular applies, use R. - If all types apply, use RVSHA. Voucher Types to which a billing rule applies.

When you update an existing rule in the Unbundled Billing Rules Import form, the import must identify the rule number being updated and include details that for the updated rule. For example, Rule 1 defines Pay Group A. If the updated rule then lists Rule 1 as Pay Group B, after the import finishes Rule 1 now uses Pay Group B.

After you import the updated rule, you can view the Transaction Report to determine which values were imported. (You can view errors by clicking Error Report.)

Note: Note the following:

Adding the Unbundled Billing Rules Import Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Unbundled Billing Rules Import from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*UPDATE.UNBUNDLED.BILLING.RULES from the Search Processes list. (To quickly find this item, enter Unbundled Billing Rules Import in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRPayroll Setup Guide.

JIRA # PD-16538, PD-16550, PD-16551, PD-16553, PD-16555, PD-16556, PD-16557, PD-16558, PD-16574, PD-16717, PD-16718, PD-16719, PD-16720, PD-17087, PD-17088, and PD-17098

========================================================================

New W/C Policy Update Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202406/System/WC_Policy_Update_Form_QR202406.htm Path: PD/Release-Notes/New-Features/2024/QR202406/System/WC_Policy_Update_Form_QR202406.htm

New W/C Policy Update Form

A new form, W/C Policy Update, now exists on the Operations|Utility Processing menu, so you can quickly change a W/C policy listed on the Benefits tab in the Client Details record. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

To make a W/C policy change, enter or select the Policy ID and select Find Clients, which populates the table with the clients associated with the selected policies. Select the clients and policy change information, then click Process Policy Changes.

Note: Note the following:

Adding the W/C Policy Update Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select W/C Policy Update from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*WC.POLICY.UPDATE from the Search Processes list. (To quickly find this item, enter W/C Policy Update in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRClient Administration Guide.

JIRA # PD-16499, PD-16500, and PD-16501

========================================================================

New G/L Import Entry Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202409/Accounting/New_GL_Import_Entry_Form_QR202409.htm Path: PD/Release-Notes/New-Features/2024/QR202409/Accounting/New_GL_Import_Entry_Form_QR202409.htm

New G/L Import Entry Form

A new form, G/L Import Entry, is now available on the System|Change menu. For example:

[Image: screenshot]

You can use the G/L Import Entry form to quickly import account codes to the G/L setup by uploading a file for import and then viewing any errors that occurred during the import or viewing successfully imported rows.

To import G/L account codes:

  1. Enter or select the GL Template. The template name displays.

  2. Select the GL Type.

  3. Enable Overwrite Existing Account Codes to replace previously imported account codes. Otherwise, leave this field blank and the system will only import new codes.

  4. Select Download Template File to download a .txt file to your computer that contains the headings that match the selected GL Type. A separate window displays the downloaded file link.

  5. Click Open File. The spreadsheet template displays, where you can enter the G/L account codes information.

  6. Select Find File. Click Add Files and select the file to upload, then click Start Upload.

  7. Click Close. A progress window displays.

Note: If an error occurs a message displays, “It may be possible to recover from this error. Do you want to repeat your last action?” Click OK.

  1. Click Close. The import process extracts account codes from the external file.

Note: Note the following:

  1. A preview of imported G/L account codes displays in the G/L Import Data panel.

Note: You can download a .csv version of this information by clicking Preview Report.

  1. If the import process encounters errors, you can select one of the following:

Adding the G/L Import Entry Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select G/L Import Entry from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select GL.DISTRIB.DEFN*GL.IMPORT.ENTRY from the Search Processes list. (To quickly find this item, enter G/L Import Entry in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRAccounting User Guide.

JIRA # WSP-497

========================================================================

New Portal New Hire Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202409/HumanResources/New_Portal_New_Hire_Import_Form_QR202409.htm Path: PD/Release-Notes/New-Features/2024/QR202409/HumanResources/New_Portal_New_Hire_Import_Form_QR202409.htm

New Portal New Hire Import Form

A new form, Portal New Hire Import, now resides on the Operations|Action menu. For example:

[Image: screenshot]

Note: This feature is only available for service providers. In addition, users whose role is set to INQUIRY for the Portal New Hire Import form displays the form in read-only format.

Clients sometimes do not have all the required new hire information, such as a Social Security Number, when they enter a new hire. Therefore, they must enter new hires in Employee Portal (EP), which requires less information. Because some clients must enter up to 500 new hires per day manually, service providers can now use the Portal New Hire Import form to quickly import new hires all at once from several clients who were registered in Employee Portal (EP). After uploading a file for import, you can view any errors that occurred during the import or view successfully imported rows.

Important! This new process applies as follows:

To import new hires from Employee Portal:

  1. Select Download Spreadsheet Template to download a .csv file to your computer that contains the new hires import headings in row 1. A separate window displays the downloaded file link.

Important! The first row of the import file must contain all the columns in the downloaded spreadsheet template in the same order. (Optional fields with no data can be included, but must be left blank.)

  1. Click Open File. The spreadsheet template displays, where you can enter the new hires information.

The spreadsheet template contains the following columns:

Column Description
Employer ID Employer ID associated with the new hire (required). Note: If the Employer ID or Client ID is not valid, the system does not validate the remaining data in that row. In addition, this Employer ID must be associated with the Client ID.
Client ID Client ID associated with the new hire (required). Note: You must set Electronic On-Boarding to Prompt or Always in the client-level settings on the Control tab in the Client Details form. Otherwise, the entire import will fail and an error message displays, “Client does not use Electronic On-Boarding. New Hires cannot be imported.”
First Name First name of new hire (required).
Last Name Last name of new hire (required).
Middle Name Middle name of new hire (optional).
Employment Status Current employment status associated with the new hire (required). Note: If there are restrictions on the Control tab in the Client Details form, only those employee statuses listed in the form can be used.
Employee Type Employment type associated with the new hire (required). Note: If there are restrictions on the Control tab in the Client Details form, only those employee types listed in the form can be used.
Work Location Work location associated with the new hire (required).
Position Position of new hire (required).
Start Date Date when new hire began employment (required).
Pay Method Pay method associated with the new hire (required): - S = Salary - H = Hourly - D = Driver - C = Commission

  1. Select Upload File. Click Add Files and select the file to upload, then click Start Upload.

  2. Click Close. The uploaded filename displays.

  3. Select Preview Data. (If you select Preview Data before uploading the file, no information displays.) Information displays on the following tabs:

Note: If any field in a row fails, the entire row is not imported.

Note: If no successful rows display in the file and you select File Content a message displays, “No New Hires to import.”

  1. Click Import Data to import new hires that display on the File Content tab. The “File content successfully imported” message displays. Click OK. The imported new hires display on the New Hire Dashboard in Employee Portal (EP) where the system generates a welcome code, so these new hires can obtain that code in the New Hire Dashboard.

Note: Any additional errors that occur during the import display in the existing errors list on the Errors tab.

  1. Click Confirmation Report to download a .csv report that contains the successfully imported new hires information.

Note: Columns that are blank indicate an unsuccessful data import.

Adding the Portal New Hire Import Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Portal New Hire Import from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*PORTAL.NEW.HIRE.IMPORT from the Search Processes list. (To quickly find this item, enter Portal New Hire Import in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Portal New Hire Import form, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17212, PD-17214, PD-17217, PD-17219, PD-17220, and PD-17341

========================================================================

New Cash Receipts Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202409/Payroll/New_Cash_Receipts_Import_Form_QR202409.htm Path: PD/Release-Notes/New-Features/2024/QR202409/Payroll/New_Cash_Receipts_Import_Form_QR202409.htm

New Cash Receipts Import Form

A new form, Cash Receipts Import, is now available on the Accounts Receivable|Action menu. For example:

[Image: screenshot]

You can use the Cash Receipts Import form to quickly import and post cash receipts into the system by uploading a file for import and then viewing any errors that occurred during the import or viewing successfully imported rows.

Note: Note the following:

To import cash receipts:

  1. Select Download Spreadsheet Template to download a .csv file to your computer that contains the cash receipts import headings in row 1. A separate window displays the downloaded file link.

  2. Click Open File. The spreadsheet template displays, where you can enter the cash receipts information.

Note: All columns in this spreadsheet are required except for the Description 1 and Description 2 columns.

The spreadsheet template contains the following columns:

Column — Description

Client Number — The client number associated with the deposit.

Bank ID — The bank ID associated with the deposit.

Deposit Date — The deposit date associated with the deposit.

Description 1 — The description associated with the deposit (optional).

Description 2 — The description associated with the deposit (optional).

Deposit Number — The deposit number associated with the deposit.

Line Type — The line type associated with the deposit.

Deposit Type — The type of deposit.

Deposit Amount — The total amount that was deposited.

Deposit Reference — The unique reference ID associated with the deposit, which can include alphanumeric characters, but not spaces.

Posting Type — The posting type associated with the deposit. (Posting types are established on the Cash Receipt Rules form.)

Invoice Number — The invoice number associated with the deposit.

Amount — The amount that is applied to the deposit.

  1. Select Upload File. Click Add Files and select the file to upload, then click Start Upload.

  2. Click Close. The uploaded filename displays.

  3. Select Preview Data. Information displays on the following tabs:

Note: If you select Preview Data before uploading the file, no information displays.

  1. Click Import Cash Receipts to post the cash receipts that display on the File Content tab. The “File content successfully imported” message displays. Click OK.

Note: Any additional errors that occur during the posting display in the existing errors list on the Errors tab.

Adding the Cash Receipts Import Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Cash Receipts Imports from the list. (To quickly find this item, select Accounts Receivable in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*CASH.RECEIPTS.IMPORT from the Search Processes list. (To quickly find this item, enter Cash Receipts Imports in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRAccounting User Guide.

JIRA # PD-17280, PD-17282, PD-17283, PD-17300, and PD-17388

========================================================================

New Restartable Payroll Feature

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202409/Payroll/New_Restartable_Payroll_Feature_QR202409.htm Path: PD/Release-Notes/New-Features/2024/QR202409/Payroll/New_Restartable_Payroll_Feature_QR202409.htm

New Restartable Payroll Feature

A new payroll calculation process, Restartable Payroll, is now the default payroll process, which has replaced the Legacy Payroll process. The Restartable Payroll process picks up the calculation process when the last successful employee is calculated. (The Legacy Payroll process is still available, if you need to resolve payroll issues.)

Note: The Restartable Payroll process does not require any custom feature codes. However, if you need to use the Legacy Payroll process, you must enable the LEGACY-PAYROLL-GLOBAL custom feature code on the System Parameters form. (See Enhancements to System Parameters Form.)

When you calculate a payroll using the Restartable Payroll process, the previously used progress bar now displays more information in a job progress window. This window displays the calculation progress in stages, so you can easily track how much payroll has been calculated during this process. For example:

[Image: screenshot]

.

Note: During this process, if you calculate payroll and the system encounters an error and then the payroll is recalculated, after you fix the issue the system displays the following message:

[Image: screenshot]

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # PD-15167 and PD-17357

========================================================================

New PTO Accrual Recalculation Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202409/PTO/New_PTO_Accrual_Recalculation_Form_QR202409.htm Path: PD/Release-Notes/New-Features/2024/QR202409/PTO/New_PTO_Accrual_Recalculation_Form_QR202409.htm

New PTO Accrual Recalculation Form

A new form, PTO Accrual Recalculation, now resides on the PTO Adjustments and Maintenance|Adjustments menu. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

You can use this form to recalculate PTO accruals for the selected PTO Class, Register Type, and PTO Benefit Plan for the current plan year. (The date range automatically adjusts for each employee based on the year-end date in their register.) This form is helpful in case the initial setup was incorrect or you need to make a bulk adjustment.

Note: You must first update the PTO benefit plan/register for a PTO recalculation to appear.

To recalculate PTO accruals:

  1. Enter or select the PTO Class.

  2. Select the Register Type.

  3. Enter or select the Benefit Plan.

  4. Select Preview. The system processes the PTO registers for that client, register type, and PTO benefit plan for the current plan year. (The date range automatically adjusts for each employee based on the year-end date in their register.) For example:

[Image: screenshot]

  1. Enter a Comment on Adjustment that will display on the PTO adjustment.

  2. Click Process Recalculation. A window opens that displays the processing steps.

  3. Click Close. A message displays, “Update Completed.” Click OK to continue.

  4. Click Download Report to view the PTO accrual recalculation details on-screen. (You can save the file by clicking XLS.) The report displays on-screen. (You can also select Download Report to save this report.)

Note: Note the following:

Adding the PTO Accrual Recalculation Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select PTO Accrual Recalculation from the list. (To quickly find this item, select PTO Adjustments and Maintenance in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*PTO.ACCRUAL.RECALC from the Search Processes list. (To quickly find this item, enter PTO Accrual Recalculation in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHRPTO User Guide.

JIRA # WSP-306

========================================================================

New Client Notes Category Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/Client/New_Client_Notes_Category_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/Client/New_Client_Notes_Category_Form_QR202411.htm

New Client Notes Category Form

A new form, Client Notes Category, now resides on the System|Change menu. For example:

[Image: screenshot]

Note: This form is only available for service providers.

You can use the Client Notes Category form to create different types of notes templates, which will be associated with the categories on the Notes tab in the Client Details form.

To create notes templates:

  1. Enter or select the Category ID. The Category Description displays.

  2. Click Save.

Note: If you select Delete a message displays, “Are you sure you want to delete? This will delete any client notes you have associated with this category.” Click Yes to continue.

Adding the Client Notes Category Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The Client Notes Category form displays.

  4. Select Client Notes Category from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select CLIENT.NOTES.CATEGORY*MAINT from the Search Processes list. (To quickly find this item, enter Client Notes Category in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHR Client Administration Guide.

JIRA # PD-17829

========================================================================

New Manager User Setup Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/Client/New_Manager_User_Setup_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/Client/New_Manager_User_Setup_Form_QR202411.htm

New Manager User Setup Form

A new form, Manager User Setup, now resides on the Client|Change menu. For example:

[Image: screenshot]

Worksite managers can use this form to set up other worksite managers within their organization, who will be accessed in the Manager User Setup form.

Note: Note the following:

To set up worksite manager users:

  1. Perform the following setups:
  1. — On the Client Security form select User Roles and Human Resources Roles that will be allowed for the current client. (These will be the only roles that are available on the Manager User Setup form for worksite managers to assign to worksite managers they are creating.)
b. On the Users form, enable the Manager User Setup Human Resources Role.
  1. Do one of the following on the Manager User Setup form:

  1. — Select the User ID of an existing worksite manager or worksite employee to set up as a worksite manager user. The form populates the user’s information.

  2. — Enter a newUser ID, which automatically sets the User Type to Worksite Manager. (Continue entering information pertaining to the new user.)

Note: Note the following:

  1. Select Requires New Password to set a new password for an existing user or for a new user.

  2. Select an MFA option in the sMFA Device Expiration field.

  3. Define the User Role ID and the Human Resources Role to indicate which roles the worksite manager user is allowed to access.

Note: You must assign at least one user role to save the record.

  1. Select Add Client to define the Data Security entities for the client. The entities display in the Data Entity Security panel.

Note: Only the clients where you have access display. If you have access to multiple clients, you must select Add Company to manage the list of clients. (You must have access to at least one client to save the record.) Also, you can delete a client by selecting the icon in the Delete column.

  1. Select an entity In the Data Entity Security panel to change the access. For example, if Full Access displays, selecting it changes the access to No Access.

  2. Click Save.

Using the Actions Menu Options

The Manager User Setup form provides additional options on the Actions menu:

Adding the Manager User Setup Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The Manager User Setup form displays.

  4. Select Manager User Setup from the list. (To quickly find this item, select Company in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRP.USERS*MANAGER.USER.SETUP from the Search Processes list. (To quickly find this item, enter Manager User Setup in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHR Client Administration Guide.

JIRA # WSP-33 and WSP-556

========================================================================

New Project History and Project History Adjustment Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/HumanResources/New_Project_History_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/HumanResources/New_Project_History_Form_QR202411.htm

New Project History and Project History Adjustment Forms

Two new forms, Project History and Project History Adjustment, now reside on the HR|View and HR|Change menus, respectively. For example:

[Image: screenshot]

[Image: screenshot]

Use these forms to do the following:

Note: If an adjustment for the selected record has already been posted, you cannot delete or change the date.

Adding the Project History and Project History Adjustment Forms to User Roles

To begin using these new forms, you must first add them to the user role(s). (Note: If you have more than one user role to add to these new forms, use the Bulk Role Update instructions.)

To add these menu items to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Project History and Project History Adjustment from the list. (To quickly find these items, select HR in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for these items (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add these menu items to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HISTORY.XREFPROJECT.INQUIRY and HISTORY.XREFPROJECT.HISTORY.ADJUST from the Search Processes list. (To quickly find these items, enter Project History and Project History Adjustment in the Form Description field and click Refine, then select the forms that display.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Project History and Project History Adjustment forms, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17641

========================================================================

New Shift History and Shift History Adjustment Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/HumanResources/New_Shift_History_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/HumanResources/New_Shift_History_Form_QR202411.htm

New Shift History and Shift History Adjustment Forms

Two new forms, Shift History and Shift History Adjustment, now reside on the HR|View and HR|Change menus, respectively. For example:

[Image: screenshot]

[Image: screenshot]

Use these forms to do the following:

Note: If an adjustment for the selected record has already been posted, you cannot delete or change the date.

Adding the Shift History and Shift History Adjustment Forms to User Roles

To begin using these new forms, you must first add them to the user role(s). (Note: If you have more than one user role to add to these new forms, use the Bulk Role Update instructions.)

To add these menu items to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Shift History and Shift History Adjustment from the list. (To quickly find these items, select HR in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for these items (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add these menu items to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HISTORY.XREFSHIFT.INQUIRY and HISTORY.XREFSHIFT.HISTORY.ADJUST from the Search Processes list. (To quickly find these items, enter Shift History and Shift History Adjustment in the Form Description field and click Refine, then select the forms that display.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Shift History and Shift History Adjustment forms, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17631

========================================================================

New Work Group History and Work Group History Adjustment Forms

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/HumanResources/New_Work_Group_History_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/HumanResources/New_Work_Group_History_Form_QR202411.htm

New Work Group History and Work Group History Adjustment Forms

Two new forms, Work Group History and Work Group History Adjustment, now reside on the HR|View and HR|Change menus, respectively. For example:

[Image: screenshot]

[Image: screenshot]

Use these forms to do the following:

Note: If an adjustment for the selected record has already been posted, you cannot delete or change the date.

Adding the Work Group History and Work Group History Adjustment Forms to User Roles

To begin using these new forms, you must first add them to the user role(s). (Note: If you have more than one user role to add to these new forms, use the Bulk Role Update instructions.)

To add these menu items to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Work Group History and Work Group History Adjustment from the list. (To quickly find these items, select HR in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for these items (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add these menu items to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HISTORY.XREFWORK.GROUP.INQUIRY and HISTORY.XREFWORK.GROUP.HISTORY.ADJUST from the Search Processes list. (To quickly find these items, enter Work Group History and Work Group History Adjustment in the Form Description field and click Refine, then select the forms that display.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Work Group History and Work Group History Adjustment forms, see the in-product help or PrismHRHuman Resources User Guide.

JIRA # PD-17646

========================================================================

New Benefits Per Hour Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/Payroll/New_Benefits_Per_Hour_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/Payroll/New_Benefits_Per_Hour_Form_QR202411.htm

New Benefits Per Hour Form

A new form, Benefits Per Hour, is now accessible by selecting this option on the Actions menu in the Employee Details form. For example:

[Image: screenshot]

You can use the Benefits Per Hour form to store the employee’s benefits per hour pay code using the memo class of pay codes.

Note: The benefits per hour record created here has no impact on payroll, which continues to use the benefit per hour rate stored in the Employee Details form.

To access this form and store an employee’s benefits per hour:

  1. Access the Employee Details form on the HR|Change menu.

  2. Enter or select an employee and then select the Benefits Per Hour option on the Actions menu. The Benefits Per Hour form displays the selected employee’s ID in the Employee field.

  3. Enter or select the Pay Code. The Description displays.

Note: If you enter a Pay Code that is not a memo pay code the following warning displays, “Pay code must have a pay class of memo.”

  1. Select the Status as Active or Inactive.

  2. Enter the benefits per hour Amount.

  3. Click Save.

Adding the Benefits Per Hour Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Benefits Per Hour from the list. (To quickly find this item, select Payroll in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select BENEFIT.PER.HOUR*MAINT from the Search Processes list. (To quickly find this item, enter Benefits Per Hour in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Benefits Per Hour form, see the in-product help or PrismHRBenefits Administration User Guide.

JIRA # PD-17316

========================================================================

New Confirm Pending Reversal Global Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/Payroll/New_Confirm_Pending_Reversal_Global_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/Payroll/New_Confirm_Pending_Reversal_Global_Form_QR202411.htm

New Confirm Pending Reversal Global Form

A new form, Confirm Pending Reversal Global, is now available on the System|Action menu. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

You can use the Confirm Pending Reversal Global form to globally review pending payroll voucher reversals for multiple employees using a range of start and end dates. In the list that displays after selecting Find Employees, you can then confirm each pending reversal.

To globally review and then individually confirm payroll voucher reversals:

  1. Click Back Office. Select Confirm Pending Reversal Global under System|Action.

  2. Obtain a list of employees with a pending voucher reversal by date range:

a. Enter or select the start date in the Date Submitted Start field.
b. Enter or select the end date in the Date Submitted End field.
— —
  1. Select Find Employees. A list of those employees with a pending voucher reversal for that date range displays.

Note: You can sort the results by clicking the column headers in the list of pending reversals.

  1. Select the Process ID link. The Employee Payroll Voucher Reversal form displays.

  2. A message displays, “Confirm processing of Reversal?” Click Yes to process the reversal.

  3. Click Save.

Adding the Confirm Pending Reversal Global Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Confirm Pending Reversal Global from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select CHECK.REVERSALS.PEND*CONFIRM.REVERSAL.GLOBAL from the Search Processes list. (To quickly find this item, enter Confirm Pending Reversal Global in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRPayroll Administration Guide.

JIRA # WSP-878

========================================================================

New Overtime Report Parameters Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/Payroll/New_Overtime_Report_Parameters_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/Payroll/New_Overtime_Report_Parameters_Form_QR202411.htm

New Overtime Report Parameters Form

A new form, Overtime Report Parameters, is now available on the System|Change menu. For example:

[Image: screenshot]

You can use the Overtime Report Parameters form to determine the data to be included in the Overtime Report, including specific pay codes.

Note: Note the following:

To set up overtime report parameters:

  1. Click Back Office. Select Overtime Report Parameters on the System|Change menu.

  2. Enable Include Expense Reimbursements in Regular Earnings to include expense reimbursements in the YTD Regular column in the report.

  3. Enable Include Fringe Benefits in Regular Earnings to include fringe benefit pay amounts in the YTD Regular column in the report.

  4. Enable Include Salaried Employees on Report to include salaried employees in the report.

  5. If necessary, enter each pay code in the Overtime Pay Codes (Optional) field to include in the Batch Overtime column amount in the report. The pay code description displays.

  6. If necessary, enter each earnings pay code in the Earnings Pay Codes (Optional) field to determine what pay and hours will be included in the report. The earnings pay code description displays.

  7. Click Save.

Adding the Overtime Report Parameters Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Overtime Report Parameters from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select REPORT.PARAMS*BATCH.OT.MAINT from the Search Processes list. (To quickly find this item, enter Overtime Report Parameters in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHR Payroll Reports guide.

JIRA # 17008

========================================================================

New Mass Archive Employee PTO Registers Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/PTO/New_Mass_Archive_Employee_PTO_Registers_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/PTO/New_Mass_Archive_Employee_PTO_Registers_Form_QR202411.htm

New Mass Archive Employee PTO Registers Form

A new form, Mass Archive Employee PTO Registers, now displays on the PTO Adjustments and Maintenance|Maintenance menu. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

You can use the Mass Archive Employee PTO Registers form to archive PTO registers for multiple employees at once.

Note: Note the following:

Adding the Mass Archive Employee PTO Registers Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Mass Archive Employee PTO Registers from the list. (To quickly find this item, select PTO Adjustments and Maintenance in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*MASS.PTO.ARCHIVE.ENTRY from the Search Processes list. (To quickly find this item, enter Mass Archive Employee PTO Registers in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHRPTO User Guide.

JIRA # WSP-877

========================================================================

New Favorites Template Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/System/New_Favorites_Template_Import_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/System/New_Favorites_Template_Import_Form_QR202411.htm

New Favorites Template Import Form

A new form, Favorites Template Import, now resides on the System|Change menu. For example:

[Image: screenshot]

You can use the Favorites Template Import form to pre-populate user favorites by importing the forms identified in the Template Process IDs panel, with the flexibility to add or remove those favorites templates in the future.

Note: You can identify the forms to import by entering or selecting their process ID in the Process field. After the import finishes, the system adds the identified forms to your existing favorites list.

Note: Note the following when using this feature:

To create and import a favorites template:

  1. Expand the Favorites Template panel.

  2. Enter a new Template ID, or enter or select an existing template. Do the following:

  1. — For a new template ID, enter the Template Description (must be one word and only contain alpha-characters).
b. For an existing template ID, the Template Description and Template Process IDs display.

Note: You can update the Template Description, but not the Template ID.

  1. Enter or select the process IDs for the forms to associate with the template in the Process field. (You must select at least one process ID.) If you select the process IDs from the Select User Process list, click Done to add them. The Name displays.

Note: The Select User Process list displays the available Process IDs and their Process Description.

  1. Click Save. A message displays, “Saving an existing Favorites Template will not update Users Favorites. Do you wish to continue?” Click Yes to continue.

  2. To use the sample import file template, select Download Sample Header File and download the template.

  3. Select Upload File in the Import User Favorites panel to upload a new or existing template.

  4. Select Add Files, select the template, then select Start Upload. Click Close. The uploaded template name displays.

  5. Click Import. After the import finishes, the system adds the identified forms to the user’s existing favorites list.

  6. Click View Transaction Report to download the import details. (This report lists whether the update was successful for each User ID and the Template ID.)

Note: If both the User ID and the Template ID in a row are invalid, the report lists the error on a separate line in the report.

Note: To delete an existing favorites template, simply enter or select the template and click Delete in the Favorites Template panel. A message displays, “This will delete the Favorites Template. Do you wish to continue?” Click Yes.

Adding the Favorites Template Import Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Favorites Template Import from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select FAVORITES.TEMPLATE*IMPORT from the Search Processes list. (To quickly find this item, enter Favorites Template Import in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-17818, PD-17820, PD-17821, PD-17822, PD-17823, PD-17871, PD-17905, and PD-18134

========================================================================

New FLSA Exemption Category Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2024/QR202411/System/New_FLSA_Exemption_Category_Form_QR202411.htm Path: PD/Release-Notes/New-Features/2024/QR202411/System/New_FLSA_Exemption_Category_Form_QR202411.htm

New FLSA Exemption Category Form

A new form, FLSA Exemption Category, now resides on the System|Change menu. For example:

[Image: screenshot]

Note: This feature is only available for service providers who have FULL access to the FLSA Exemption Category form.

You can use the FLSA Exemption Category form to create FLSA exemption category codes.

To create a new FLSA exemption category code:

  1. Click Back Office. Select FLSA Exemption Category under System|Change.

  2. Enter an FLSA Exemption Category Code that represents that represents an FLSA exemption category. For example, ADMIN or Q1.

  3. Enter an FLSA Exemption Category Description.

  4. Click Save.

Note: Note the following:

Adding the FLSA Exemption Category Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select FLSA Exemption Category from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select FLSA.EXEMPTION.CATEGORY*MAINT from the Search Processes list. (To quickly find this item, enter FLSA Exemption Category in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # PD-18074 and PD-18075

========================================================================

Linked Accrual Plans Feature

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/MR202501/Client/Linked_Accrual_Plans_Feature_MR202501.htm Path: PD/Release-Notes/New-Features/2025/MR202501/Client/Linked_Accrual_Plans_Feature_MR202501.htm

Linked Accrual Plans Feature

A new feature, Linked Accrual Plans, consists of two PTO plans that you must set up so employees can accrue time for a plan year in one register that they cannot use until the plan year ends. After the plan year ends, the accrued hours move to a new register where employees can use their PTO hours. (Employees can have several different linked accrual plans, one for sick time, one for vacation time, and so on.)

Note: Note the following:

Using Linked Accrual Plans Feature

To use the Linked Accrual Plans feature, you must set up two PTO plans in the PTO Benefit Plans form:

The following diagram demonstrates the setup for Linked Accrual Plans:

[Image: screenshot]

Note: Note the following:

Setting Up the Linked Accrual Plans Feature

Set up the following:

  1. PTO Class: Use the PTO Classes form to define which PTO classes will be used in conjunction with each other, consisting of a PTO class for the accrual and a PTO class for the balance.

For example:

a. Create a PTO Class Code for the Balance plan. For example, VACBAL.

Note: Do not enable Linked Accrual.

b. Create a PTO Class Code for the Accrual plan. For example, VACACCR.
c. Enable Linked Accrual.
— —
d. In the Transfer To field, select VACBAL.
— —

Note: These PTO classes are now linked and cannot be linked to other classes.

  1. PTO Register: Enable the Prior Year Accrual trigger method on the PTO Register Types form to trigger the balance register to move the accrued PTO hours from the accrual plan to the balance plan.

For example:

a. Create a PTO Type Code register for the Balance plan. For example, VACBAL.
b. Create a PTO Type Code register for the Accrual plan. For example, VACACCR.
  1. PTO Benefit Plan: Enroll employees in an Accrual plan and a Balance plan on the PTO Benefit Plans form. The Accrual plan determines the PTO time accrued. The system does not use the Balance plan to determine the accruals, but employees must be enrolled in both plans for the transfer to work correctly.

  1. — Create a PTO Benefit Plan for the Balance plan. For example, VACBAL. (You must select a calculation basis, but the system does not use it to calculate accruals.)

  2. — Create a PTO Benefit Plan for the Accrual plan. For example, VACACCR. (This will hold the settings for the accruals.)

  1. PTO Absence Codes: Set up an Absence Code on the PTO Absence Codes form for employees to use the Balance plan. (No special settings are needed for this plan. The Accrual plan does not require an absence code.)

Transfer Process

When the system transfers accrued PTO hours, the employee register displays the accrued amount in the calculated column in the Balance register and displays an annotation, “Accrual Transfer MM/DD/YY,” in the details. The system then zeroes out the year-to-date accrual amounts in the employee Accrual register and displays an annotation, “XX number of hours moved to linked plan.”

System Enhancements

The following enhancements were made to accommodate the Linked Accrual Plans feature:

Enhancement Description
Enhancement to PTO Classes Form (PD-18270) Two new fields, Linked Accrual and Transfer To, now reside on the PTO Classes form: - Linked Accrual (default is disabled): Enable this field to mark the selected PTO Class Code as a linked accrual. - Transfer To: Transfers the selected PTO Class Code to another PTO class. (This field only displays if Linked Accrual is enabled.) > Note: Note the following: - Once a PTO class is identified as a linked accrual, you can define where the accruals are transferred. - After defining a PTO class as a linked accrual, it cannot be used as the Transfer To option. - Once the PTO balance class is linked to an accrual, it cannot be linked again. (The linking of accruals is a 1:1 relationship. Each accrual class can only be linked to one balance class and only one accrual class.)

New Multi-Entity Group Details Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/QR202503/Client/New_Multi_Entity_Group_Details_Form_QR202503.htm Path: PD/Release-Notes/New-Features/2025/QR202503/Client/New_Multi_Entity_Group_Details_Form_QR202503.htm

New Multi-Entity Group Details Form

A new form, Multi-Entity Group Details, is now available by selecting Create New Group in the Multi-Entity Groups form. For example:

[Image: screenshot]

You can use the Multi-Entity Group Details form to create a new multi-entity group.

Adding the Multi-Entity Group Details Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The Client Notes Category form displays.

  4. Select Multi-Entity Group Details from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select MULTI.ENTITY.GROUPS*NEW.MAINT from the Search Processes list. (To quickly find this item, enter Multi-Entity Group Details in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHR Client Administration Guide.

JIRA # PD-18680 and PD-18681

========================================================================

New Multi-Entity Groups Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/QR202503/Client/New_Multi_Entity_Groups_Form_QR202503.htm Path: PD/Release-Notes/New-Features/2025/QR202503/Client/New_Multi_Entity_Groups_Form_QR202503.htm

New Multi-Entity Groups Form

A new form, Multi-Entity Groups, is now available on the System|Change menu. For example:

[Image: screenshot]

You can use the Multi-Entity Groups form to organize similar clients.

Note: This form is only available for service providers.

Adding the Multi-Entity Groups Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The Client Notes Category form displays.

  4. Select Multi-Entity Groups from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select MULTI.ENTITY.GROUPS*MAINT from the Search Processes list. (To quickly find this item, enter Multi-Entity Groups in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in‑product help or PrismHR Client Administration Guide.

JIRA # PD-18679

========================================================================

New Payroll Reason Codes Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/QR202503/Payroll/New_Payroll_Reason_Codes_Form_QR202503.htm Path: PD/Release-Notes/New-Features/2025/QR202503/Payroll/New_Payroll_Reason_Codes_Form_QR202503.htm

New Payroll Reason Codes Form

A new form, Payroll Reason Codes, now resides on the System|Change menu. For example:

[Image: screenshot]

Note: This form is only available for service providers.

You can use the Payroll Reason Codes form to group and sort payroll reason codes. If you need to obsolete a payroll reason code, simply click Obsolete Reason Code. (The obsolete payroll reason code will no longer display on the Payroll Control form.)

Note: The INT (Internal) and CNT (Client) payroll reason codes are pre-loaded in the Payroll Reason Code list. (These can be deleted by the client. However, once a payroll reason code is used, it cannot be deleted.)

Adding the Payroll Reason Codes Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Payroll Reason Codes from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select PAYROLL.REASON.CODES*MAINT from the Search Processes list. (To quickly find this item, enter Payroll Reason Codes in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRPayroll Processing Guide.

JIRA # WSP-973

========================================================================

New Employee Carryover Loss Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/QR202503/PTO/New_Employee_Carryover_Loss_QR202503.htm Path: PD/Release-Notes/New-Features/2025/QR202503/PTO/New_Employee_Carryover_Loss_QR202503.htm

New Employee Carryover Loss Form

A new form, Employee Carryover Loss, now resides on the Reports menu. For example:

[Image: screenshot]

You can use the Employee Carryover Loss form to produce a report that displays PTO carryover lost for each employee from the previous year. For example, if employees can carryover up to 40 hours of PTO and an employee has 60 hours available at the end of the year, the report would display 20 hours of lost PTO carryover.

Note: The report that the Employee Carryover Loss form produces does not apply to global PTO.

To access this form and obtain PTO carryover lost for each employee:

  1. On the Reports menu, select Employee Loss Carryover under Payroll|Reports.

  2. Select the Register Type.

  3. Select the PTO Benefit Plan.

  4. Enter or select the As Of Date.

  5. Click Run. The PTO Carryover Loss Report displays. For example:

[Image: screenshot]

Adding the Employee Carryover Loss Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Employee Carryover Loss from the list. (To quickly find this item, select Payroll in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*PTO.CARRYOVER.LOSS.REPORT from the Search Processes list. (To quickly find this item, enter Employee Carryover Loss in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Employee Carryover Loss form, see the in-product help, the PrismHR Payroll Reports guide, or the PrismHR Paid Time Off User Guide.

JIRA # WSP-924

========================================================================

New PTO Auto-Enrollment Rules Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/QR202503/PTO/New_PTO_Auto_Enrollment_Rules_Import_Form_QR202503.htm Path: PD/Release-Notes/New-Features/2025/QR202503/PTO/New_PTO_Auto_Enrollment_Rules_Import_Form_QR202503.htm

New PTO Auto-Enrollment Rules Import Form

A new form, PTO Auto-Enrollment Rules Import, now resides on the Operations|Action menu. For example:

[Image: screenshot]

You can use the PTO Auto-Enrollment Rules Import form to import multiple PTO auto-enrollment rules or update existing rules.

To import PTO auto-enrollment rules:

  1. In the Generate Import Spreadsheet section, create an import spreadsheet by entering or selecting the Client IDs. (You can select multiple clients from the Select Clients list at once.) The Client Name displays next to each client. (If left blank, the system selects all clients and bill codes.)

  2. Select Download Spreadsheet. The system creates a spreadsheet that displays in a separate window, which is suitable for editing.

  3. In the Import Data section, enter an Import Name. (This is a required field; you cannot import a file without this information.)

  4. Select Upload File. Click Add Files and select the file to upload, then click Start Upload. (This file must be in .csv format.)

  5. Click Close. A separate Downloads window displays the name of the .csv file that the system created. (Click Open file to view the downloaded file.)

Note: The first row in the downloaded file displays information about the first rule and the multi-value fields, which are separated by a pipe delimiter (|).

  1. Click Import. Processing steps describe the information saved and include a date and time stamp. You can view this as a report or download in PDF or XLS format by clicking Report.

  2. Click Close.

  3. Click Transaction Report to display a link to a report that contains the PTO auto-enrollment rules transactions.

Note: The Transaction Report displays “Skipped” for any column in a row that has valid data but was not imported because a required row contained invalid data. (All invalid data displays in the Transaction Report.)

  1. Click Error Report to display a link to a .csv file that details the errors that occurred during the import. (The system does not import any rows listed in the error file and only imports rows where all data in the row is valid.)

Note: The Error Report link only displays if errors occurred during the import, which confirms that the system is unable to perform the import.

Note: Note the following:

Adding the PTO Auto-Enrollment Rules Import Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select PTO Auto-Enrollment Rules Import from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*UPDATE.PTO.ENROLL.RULES from the Search Processes list. (To quickly find this item, enter PTO Auto-Enrollment Rules Import in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the PTO Auto-Enrollment Rules Import form, see the in-product help, the PrismHR Client Administration Guide, or the PrismHR Paid Time Off User Guide.

JIRA # WSP-1005

========================================================================

New Marketplace Link

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/QR202503/System/New_Marketplace_Link_QR202503.htm Path: PD/Release-Notes/New-Features/2025/QR202503/System/New_Marketplace_Link_QR202503.htm

New Marketplace Link

A new link, Marketplace, now displays on the PrismHR menu bar. For example:

[Image: screenshot]

Selecting Marketplace provides quick access to the PrismHR Marketing|Expanded Services web site, where you can connect with vendors. For example:

[Image: screenshot]

Note: Only service providers can access the PrismHR Marketing|Expanded Services web site.

In the PrismHR Marketing Portal, you can access customizable email templates and run campaigns designed to help increase awareness and adoption at the employer and employee levels. The Marketing Portal is a complimentary program for all PrismHR PEO and staffing customers.

JIRA # PD-18314

========================================================================

New Transfer ACH File to PC Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/QR202503/System/New_Transfer_ACH_File_to_PC_Form_QR202503.htm Path: PD/Release-Notes/New-Features/2025/QR202503/System/New_Transfer_ACH_File_to_PC_Form_QR202503.htm

New Transfer ACH File to PC Form

A new form, Transfer ACH File to PC, now exists on the Operations|Action menu, so you can download ACH files to your PC. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

After entering or selecting an ACH file to download, the File View displays the first 15 lines of the selected ACH File. For example:

[Image: screenshot]

Adding the Transfer ACH File to PC Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Transfer ACH File to PC from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*DOWNLOAD.ACH.FILES.DIR.XREF from the Search Processes list. (To quickly find this item, enter Transfer ACH File to PC in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRACH User Guide.

JIRA # PD-18983

========================================================================

New Approval Payroll Reports Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202504/Payroll/New_Approval_Payroll_Reports_Form_R202504.htm Path: PD/Release-Notes/New-Features/2025/R202504/Payroll/New_Approval_Payroll_Reports_Form_R202504.htm

New Approval Payroll Reports Form

A new form, Approval Payroll Reports, is now accessible by selecting the new option, Approval Payroll Reports, in the View Report/Analytic field on the Payroll Approval form. For example:

[Image: screenshot]

Selecting Approval Payroll Reports opens the new Approval Payroll Reports form, which lists all the available payroll approval reports and downloadable output files. Click the Open File icon (

[Image: screenshot]

) in the Job column to view the report or downloadable file listed in the Report Title column. For example:

[Image: screenshot]

Note: Note the following:

For more information, see the in-product help, PrismHR Payroll Processing Guide, or PrismHRPayroll Reports guide.

JIRA # PD-18870

========================================================================

New Redirect Direct Deposit Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202504/Payroll/New_Redirect_Direct_Deposit_Form_R202504.htm Path: PD/Release-Notes/New-Features/2025/R202504/Payroll/New_Redirect_Direct_Deposit_Form_R202504.htm

New Redirect Direct Deposit Form

A new form, Redirect Direct Deposit, now resides on the Payroll|Change menu. For example:

[Image: screenshot]

You can use the Redirect Direct Deposit form to redirect a direct deposit (DD) to a different DD account after the ACH has already been processed for the voucher’s original direct deposit transaction.

After you make the redirects and click Save, the system:

Note: Note the following:

[Image: screenshot]

However, if there is only one currently active checking or savings account and the only currently active checking or savings account has a transit and routing number that matches the transit and account number, then only the –Select– option displays. In this case a warning displays, “There are no valid alternative Direct Deposit Accounts for this voucher.”

Adding the Redirect Direct Deposit Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Redirect Direct Deposit from the list. (To quickly find this item, select Payroll in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select EMPLOYEE.PAYROLL.VOUCHERS*REDIRECT.DIRECT.DEPOSIT from the Search Processes list. (To quickly find this item, enter Redirect Direct Deposit in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRPayroll Adjustment Processing Guide.

JIRA # WSP-1261, WSP-1266, WSP-1322, and WSP-1667

========================================================================

New Report Print Options Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202505/System/New_Report_Print_Options_Form_R202505.htm Path: PD/Release-Notes/New-Features/2025/R202505/System/New_Report_Print_Options_Form_R202505.htm

New Report Print Options Form

A new form, Report Print Options, is now available by selecting Report Print Options on the Actions menu in the Cost Centers form. For example:

[Image: screenshot]

Note: This feature is only available for service providers.

You can use the Report Print Options form to add an Invoice Logo override to the Print Service Report Logo Filepath when configuring a sub-cost center, which helps manage branding for all clients within the same cost center. (Previously, there were only two options available to display the invoice and report logos, either at the global or client level.)

Note: Note the following:

Adding the Report Print Options Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Report Print Options from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select COST.CENTERS*REPORT.PRINT.OPTIONS from the Search Processes list. (To quickly find this item, enter Report Print Options in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-1520

========================================================================

New Mass Employee Transfer Import Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202506/HumanResources/New_Mass_Employee_Transfer_Import_Form_R202506.htm Path: PD/Release-Notes/New-Features/2025/R202506/HumanResources/New_Mass_Employee_Transfer_Import_Form_R202506.htm

New Mass Employee Transfer Import Form

A new form, Mass Employee Transfer Import, is now available on the Operations|Import Processing menu. For example:

[Image: screenshot]

You can use the Mass Employee Transfer Import form to quickly import a list of employees for transfer to new clients.

Note: Note the following:

To perform a mass employee transfer import:

  1. Click Back Office.

  2. From the Operations|Import Processing menu, select Mass Employee Transfer Import.

  3. Select Download Spreadsheet Template to download a sample (.csv) template file to your computer to use for creating the list of employees to transfer to new clients. A separate window displays the downloaded file link. (The file downloads to the Downloads folder on your system.)

The spreadsheet template contains the following columns:

Column — Description

From Client — The client ID for the client that the employee is transferring from (required).

Employee ID — The ID of the employee whose information requires a transfer (required).

To Client — The client ID for the client where the employee is transferring (required).

To Employer — The employer ID assigned to the new client where the employee is being transferred (required).

To Pay Group — The pay group for the destination client (required).

To Retire Plan — The retirement plan where the employee is being transferred (optional).

To Position — A valid position for the destination client (required).

To Location — A valid location for the destination client (required).

To Client Hire Date — The hire date to use for the company where the employee is being transferred (required). Note: After entering or selecting a date, a message containing that date displays. Select Yes to confirm that date should be used to update the Status, Type, Status Type History, Position History, and Pay History. If you select No, the system updates that information using the most recent date for that record in the From Client employee record after the transfer finishes.

Update historical dates? — Indicates whether to keep status, type, status type history, position history, and pay history dates (required).

Transfer YTD Check Stubs — The year-to-date check stub details to the company where the employee is transferring (required).

Terminate Employee in Original Client — Indicate whether to terminate the employee and their benefits in the original client (required).

Termination Date — The date when the transferring employee will be terminated in their old client (optional).

Termination Reason — A valid termination reason code (optional).

Terminate Benefit Coverage Today — The terminated group benefits for the employee ends coverage today (required).

  1. Click Find File to open the File Upload dialog box.

  2. Click Add Files in the File Upload dialog box.

  3. Select the specified Import File from your system that you have created. Once selected, the Import File will display in the File Upload dialog box.

  4. Click Start Upload to upload the file.

  5. Click Close on the File Upload dialog box.

  6. The uploaded Import File name will display under the File Name field on the form. The content of the file will display under File Content tab. Errors, if any, will display in the Messages tab. Correct the errors and redo the process.

While processing the uploaded file, the following validation occurs:

  1. Click Import to import the content into PrismHR. After the import finishes, the following occurs:
  1. Click Report to view the transaction report. This report contains the following information:

Adding the Mass Employee Transfer Import Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Mass Employee Transfer Import from the list. (To quickly find this item, select Operations in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*MASS.EMP.TRANS.IMPORT from the Search Processes list. (To quickly find this item, enter Mass Employee Transfer Import in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help, PrismHRClient Administration Guide, PrismHR Employer Administration Guide, or PrismHR Payroll Administration Guide.

JIRA # WSP-1523, WSP-1772, and WSP-1798

========================================================================

New ACH Journal Edits Audit Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202507/System/New_ACH_Journal_Edits_Audit_Report_Form_R202507.htm Path: PD/Release-Notes/New-Features/2025/R202507/System/New_ACH_Journal_Edits_Audit_Report_Form_R202507.htm

New ACH Journal Edits Audit Report Form

A new form, ACH Journal Edits Audit Report, is now available on the System|Report menu. For example:

[Image: screenshot]

Note: Note the following:

You can enter criteria in the ACH Journal Edits Audit Report form to produce a report that captures ACH updated or manually created records. After entering the criteria, click Generate Report to produce the ACH Journal Edits Audit Report.

Adding the ACH Journal Edits Audit Report Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select ACH Journal Edits Audit Report from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*ACH.JOURNAL.AUDIT.RPT.ENTRY from the Search Processes list. (To quickly find this item, enter ACH Journal Edits Audit Report in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-1920 and WSP-1921

========================================================================

New ACH Journal Hold/Release Audit Report Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202507/System/New_ACH_Journal_Hold_Release_Audit_Report_Form_R202507.htm Path: PD/Release-Notes/New-Features/2025/R202507/System/New_ACH_Journal_Hold_Release_Audit_Report_Form_R202507.htm

New ACH Journal Hold/Release Audit Report Form

A new form, ACH Journal Hold/Release Audit Report, is now available on the System|Report menu. For example:

[Image: screenshot]

Note: Note the following:

You can enter criteria in the ACH Journal Hold/Release Audit Report form to produce a report that captures ACH hold and release activity. After entering the criteria, click Generate Report to produce the ACH Journal Hold/Release Audit Report.

Adding the ACH Journal Hold/Release Audit Report Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select ACH Journal Hold/Release Audit Report from the list. (To quickly find this item, select System in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select HRPY.WORK*ACH.HOLD.REL.AUDIT.RPT from the Search Processes list. (To quickly find this item, enter ACH Journal Hold/Release Audit Report in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information, see the in-product help or PrismHRSystem Administration Guide.

JIRA # WSP-1923 and WSP-1924

========================================================================

New Confirmation Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202509/PTO/New_Confirmation_Form_R202509.htm Path: PD/Release-Notes/New-Features/2025/R202509/PTO/New_Confirmation_Form_R202509.htm

New Confirmation Form

As step 3 in the new Time Off Setup Workflow process (see New Time Off Setup Workflow Process), a new form, Confirmation, displays when you click

[Image: screenshot]

in the Set Up Plans form, if you completed all required fields on that form (see New Set Up Plans Form). For example:

[Image: screenshot]

You can review and then submit the saved time off plan details from steps 1 and 2 in each panel on the Confirmation form.

Note: If you need to make a change to the plan information, click

[Image: screenshot]

to return to the panels in the Set Up Plans form and make that update. Then proceed to the Confirmation form by clicking

[Image: screenshot]

.

Note: Note the following when working in the Confirmation form:

Finishing the Plan Setup

To complete step 3, review the information in each panel and click Finish Setup to commit the saved plan to the system. A message displays:

[Image: screenshot]

Important! Clicking Finish Setup finalizes the time off plan information that you made in this workflow. If you need to make more updates, you must now make them in the legacy PTO Work Center.

Click Yes to commit the saved plan to the system. A progress window displays. For example:

[Image: screenshot]

Click Close to return to the Time Off Setup Workflow form.

Note: Note the following:

Use the buttons in the Confirmation form to do the following:

Click — Action

[Image: screenshot] — Opens a panel.

[Image: screenshot] — Collapses an open panel.

[Image: screenshot] — Collapses the panel details.

[Image: screenshot] — Opens each panel and displays their details.

[Image: screenshot] — Returns to the Set Up Plans form, where you can make changes to plan information.

[Image: screenshot] — Proceeds to the Confirmation form, if you returned to the Set Up Plans form to make a change.

[Image: screenshot] — Completes step 3 by committing the saved plan to the system.

[Image: screenshot] — Saves your information and returns to the Time Off Setup Workflow form.

For more information about the Time Off Type form, see the in-product help or the PrismHR Paid Time Off User Guide.

JIRA # PD-19056, PD-19057, PD-19224, PD-19257, and PD-19258

========================================================================

New Set Up Plans Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202509/PTO/New_Set_Up_Plans_Form_R202509.htm Path: PD/Release-Notes/New-Features/2025/R202509/PTO/New_Set_Up_Plans_Form_R202509.htm

New Set Up Plans Form

As step 2 in the new Time Off Setup Workflow process (see New Time Off Setup Workflow Process), a new form, Set Up Plans, displays when you select a time off type in the Time Off Type form and click

[Image: screenshot]

(see New Time Off Type Form).

The Set Up Plans form displays four panels where you can create or update the employee time off accrual schedule, plan, pay, and portal configuration. The side stepper panel on the left side displays your position in this process. For example:

[Image: screenshot]

Note: Note the following about the Set Up Plans form:

Using the Setup Panels

You can use the panels in the Set Up Plans form to do the following:

[Image: screenshot]

Note: Note the following when working in the Accrual Schedule panel:

[Image: screenshot]

Use the buttons in the Plans panel to do the following:

Click — Action

[Image: screenshot] — To create a new plan. A blank plan opens below the current open plan. (This button is located at the bottom of the panel, so you can easily add another plan without scrolling up to the [Image: screenshot] button at the top of the panel if you have many plans open.)

[Image: screenshot] — To create a duplicate plan of the current open plan (displays beneath it), so you can use that plan’s selections to quickly set up another plan.

[Image: screenshot] — To create a new plan, which displays as a blank plan below the current open plan. (This button is located at the top of the panel.)

[Image: screenshot] — To delete the current plan. After clicking [Image: screenshot] a warning message displays, “Are you sure you want to delete this plan?” Click Yes to continue.

[Image: screenshot]

Note: The system automatically populates the Accrual Schedule field with the following data from the Schedule Code field on the Accrual Schedule panel:

Note: The system re-populates the Accrual Schedule field anytime you update the Schedule Code on the Accrual Schedule panel.

[Image: screenshot]

Note: These settings control how the absence code behaves in Employee Portal (EP). (Absence codes are specialized reason codes that describe the reason for employee absences.)

Use the buttons in the Set Up Plans form to do the following:

Click — Action

[Image: screenshot] — Opens a panel.

[Image: screenshot] — Collapses an open panel.

[Image: screenshot] — Saves the information in the current open panel, then closes that panel and returns to the panel above.

[Image: screenshot] — Saves the information in the current open panel, then closes that panel and advances to the next panel in the form. For example, if you click [Image: screenshot] in the Accrual Schedule panel, the Plans panel opens. (You can advance to the next panel even if all the fields in the open panel are not complete.)

[Image: screenshot] — Returns to the Time Off Type form.

[Image: screenshot] — Advances to the Confirmation form, which is step 3 in the Time Off Setup Workflow process. Note: You must complete all the required fields in the panels before moving on to step 3, the Confirmation form. (This button is disabled until you complete those fields.)

[Image: screenshot] — Saves your information and returns to the Time Off Setup Workflow form.

For more information about the Time Off Type form, see the in-product help or the PrismHR Paid Time Off User Guide.

JIRA # PD-19047, PD-19048, PD-19049, PD-19050, PD-19051, PD-19052, PD-19053, PD-19054, PD-19055, PD-19221, PD-19351, PD-19537, PD-19798, PD-19987, and PD-20076

========================================================================

New Time Off Setup Workflow Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202509/PTO/New_Time_Off_Setup_Workflow_Form_R202509.htm Path: PD/Release-Notes/New-Features/2025/R202509/PTO/New_Time_Off_Setup_Workflow_Form_R202509.htm

New Time Off Setup Workflow Form

When you use the new Time Off Setup Workflow process (see New Time Off Setup Workflow Process), a new form, Time Off Setup Workflow, now resides on the Client|Change menu. For example:

[Image: screenshot]

Note: Note the following:

[Image: screenshot]

Note: The legacy PTO Work Center Plan Setup steps now display in the new Maintenance column.

You can use the Time Off Setup Workflow form to continue setting up in-progress time off plans or create new time off plans. (See New Time Off Setup Workflow Process.)

Important! You cannot update existing plans created in the legacy PTO Work Center using the new Time Off Setup Workflow process. Instead, you must edit existing plans in the legacy PTO Work Center. (Click

[Image: screenshot]

in the header area of the Time Off Setup Workflow form to access the legacy PTO Work Center.)

Using the Time Off Setup Workflow Form

The Time Off Setup Workflow form contains two panels:

Column — Description

Batch ID — Displays the batch number that was assigned to the time off plan. (Clicking the time off plan in this column displays the Time Off Type form, which opens the workflow to the last step the user completed.)

Name — Displays the name of the time off plan.

Status — Displays the last step the user completed for the time off plan.

Time Off Type — Displays the time off plan type that was selected in the batch.

Last Modified Date — Displays the date, in MM/DD/YYYY format, when the time off plan was last modified.

Last Modified User — Displays the user ID of the last user who modified the time off plan.

Actions — Select Delete ( [Image: screenshot] ) to delete an in-progress time off plan.

You can create a new time off plan by selecting New Setup. The Add Time Off Setup Batch form displays, where you can name the time off plan.

Note: Note the following:

Selecting the Time Off Type

To start the Time Off Setup Workflow process, make a selection from the Batch ID column in the Client Time Off Setups in Progress panel. The Time Off Type form (step 1 in the Time Off Setup Workflow process) displays the last step the user completed. However, if the type for a time off plan has not been set, you can set it here. (See New Time Off Type Form.)

Note: Click

[Image: screenshot]

in the Time Off Type form to save your time off plan type and return to the Time Off Setup Workflow form.

Understanding the Side Stepper

Each form in the Time Off Setup Workflow process consists of a “side stepper” on the left side of the window and setup panels on the right side of the window.

The side stepper displays your position in this process. As you move through the process, each completed step displays in green. For example, the step shown in green below, Time Off Type, confirms that the time off type was selected (step 1), so you need to complete step 2, Set Up Plans, the next step in the process, which is highlighted in black:

[Image: screenshot]

Note: Steps that display in gray are not complete.

Adding the Time Off Setup Workflow Form to User Roles

To begin using this new form, you must first add it to the user role(s). (Note: If you have more than one user role to add to this new form, use the Bulk Role Update instructions.)

To add this menu item to a user role, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select or enter the Role ID.

  3. Click Add. The User Role Maintenance form displays.

  4. Select Time Off Setup Workflow from the list. (To quickly find this item, select Company in the Type Filter box.)

  5. Click Accept.

  6. Click Save.

To change the role’s access to Inquiry or Deny for this item (the default is Full), click the Access item (the access changes to Inquiry, click it again to change the access to Deny). Click Save.

To add this menu item to multiple user roles, do the following:

  1. Click Back Office. Select User Roles from the System|Change menu.

  2. Select Bulk Role Update from the Actions menu. The Bulk Role Update form opens.

  3. Click Form and then select PTO.WORKFLOW.WORK*DASHBOARD from the Search Processes list. (To quickly find this item, enter Time Off Setup Workflow in the Form Description field and click Refine, then select the form that displays.)

  4. A list of user roles displays.

  5. Grant access to each user role in the Access column. You can grant full access (Full) or read-only access (Inquiry). To deny access, click Deny.

  6. Click Accept. The User Roles form displays.

  7. Click Save.

For more information about the Time Off Setup Workflow form, see the in-product help, the PrismHRClient Administration Guide, or the PrismHRPaid Time Off User Guide.

JIRA # PD-19036, PD-19037, PD-19038, PD-19039, PD-19040, PD-19060, PD-19221, PD-19351, and PD-19987

========================================================================

New Time Off Setup Workflow Process

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202509/PTO/New_Time_Off_Setup_Workflow_Process_R202509.htm Path: PD/Release-Notes/New-Features/2025/R202509/PTO/New_Time_Off_Setup_Workflow_Process_R202509.htm

New Time Off Setup Workflow Process

The original PTO Setup Workflow process has been redesigned as the “Time Off Setup Workflow” process, which provides more user-friendly forms to create employee time off plans for your clients.

Note: Note the following:

Important! This process only applies to setting up new time off plans, not editing existing plans. (You can only edit existing plans in the legacy PTO Work Center. Click

[Image: screenshot]

in the header area of the Time Off Setup Workflow form to access the legacy PTO Work Center.)

Getting Started

You can use the new Time Off Setup Workflow form to continue setting up in-progress time off plans or create new time off plans. (See New Time Off Setup Workflow Form.)

Note: To set up a new time off plan, click New Setup, which displays the Add Time Off Setup Batch form, where you can name the batch.

Understanding the Process Steps

Setting up new time off plans now involves using the following workflow:

Step/Form Description
Step 1, Time Off Type form After selecting a time off plan in the Time Off Setup Workflow form, the Time Off Type form displays (see New Time Off Type Form). Select one of the standard time off types for the time off plan or add a new time off type. Note: You must select a time off type to proceed to step 2, Set Up Plans form. (The [Image: screenshot] button is disabled until you complete this step.) Selecting Add Type displays the Add Time Off Type form, where you can create a new time off type instead of selecting one of the standard types that display in the Time Off Type form. For example, you can create a new “Personal Holiday” time off type. After selecting the time off type and clicking [Image: screenshot] , the system enables the Time Off Type step on the left side by displaying the step number in green, confirming that this step is complete.
Step 2, Set Up Plans form Clicking [Image: screenshot] in the Time Off Type form displays the Set Up Plans form (see New Set Up Plans Form), where you can set up the following items: - Accrual Schedule: Set when employees accrue time off. (The [Image: screenshot] button is disabled until you set the accrual schedule.) - Plans: Set how much time off employees accrue. (You can set up multiple plans, such as a full-time plan and a part-time plan.) Note: Select Duplicate Plan to copy an existing plan, so you can use that plan’s selections to quickly set up another plan. - Pay: Set the pay information for the time off type, which includes the Pay Code and Accrual Schedule. - Portal Configuration (Optional): Enable the Can Request This Time Off Type in Portal field to allow employees to request time off using Employee Portal (EP). After making these selections and clicking [Image: screenshot] , the system enables the Set Up Plans step on the left side by displaying the step number in green, confirming that this step is complete. Note: You cannot continue to the next step in the process until you complete all panels in step 2. (The [Image: screenshot] button is disabled until you complete this step.)

========================================================================

New Time Off Type Form

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/New-Features/2025/R202509/PTO/New_Time_Off_Type_Form_R202509.htm Path: PD/Release-Notes/New-Features/2025/R202509/PTO/New_Time_Off_Type_Form_R202509.htm

New Time Off Type Form

As step 1 in the new Time Off Setup Workflow process (see New Time Off Setup Workflow Process), a new form, Time Off Type, displays when you select a time off plan in the Batch ID column in the Time Off Setup Workflow form (see New Time Off Setup Workflow Form).

Note: Note the following:

Setting the Time Off Plan Type

You can use the Time Off Type form to set the type for a time off plan by either selecting a standard time off type in the list that displays (the type description displays in highlighted text with the type name displaying underneath) or creating a new type. For example:

[Image: screenshot]

In addition, you can create a new type in the Time Off Type form by selecting Add Type. For example, you can create a new “Personal Holiday” time off type in the Add Time Off Type form that displays (both fields are required):

[Image: screenshot]

After selecting the time off type or saving a new type and clicking

[Image: screenshot]

, the system enables the Time Off Type step on the left side by displaying the step number in green, confirming that this step is complete.

Note: Note the following:

For more information about the Time Off Type form, see the in-product help or the PrismHR Paid Time Off User Guide.

JIRA # PD-19043, PD-19044, PD-19045, PD-19046, PD-19221, and PD-19351

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202403.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202403.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

Reprinting Payroll Checks — To make printing and rebuilding payroll checks more user-friendly for worksite managers and worksite trusted advisors, these users can now simply select the Reprint Payroll Checks link in the Payroll Reports form. (See Enhancement to Reprinting Payroll Checks.)

Validating Employee’s Hourly Rate — The system now validates that the employee’s Hourly Rate no longer displays in the Employee PTO Detail Report for worksite managers and worksite trusted advisors who have the Time Sheet Entry (w/o Pay Rates) Human Resources role set on the Users form and the PTO Absence Summary Report with Buyback option set on the Employee PTO Detail Report form. (See Enhancement to Employee PTO Detail Report Form.)

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202406.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202406.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

Working with Termination Explanation After Employee Termination (PD-15590) — You can now add, update, or delete a Termination Explanation on the Other tab after an employee has been terminated. Note: This enhancement is only available for service providers.

Using a Worksite Trusted Advisor’s User ID as PTO Approver or Manager (PD-16707) — Service providers can now enter a worksite trusted advisor’s user ID (who has access to the client) as the PTO Approver or Manager for the selected employee on the Work tab. (Previously, you could only enter an employee ID in these fields.)

Enhancement to Global Search Results (PD-16835) — Previously, when performing a global search for an employee the system displayed the preferred name instead of the legal first name. The system now displays an employee’s legal first name in parentheses if there is a preferred name for the employee, which displays first. After the legal first name the middle initial displays, then the last name.

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202409.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202409.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

Enhancements to System Parameters Form (PD-15168) — A new custom feature code, LEGACY-PAYROLL-GLOBAL, is now available on the Custom Feature Codes list, which you can enable to revert to the Legacy Payroll process. (You can use this payroll process instead of the default Restartable Payroll process.)

Enhancement to Employee Payroll Vouchers Form (PD-17210) — Worksite managers and worksite trusted advisors can now reprint multiple vouchers at once that have an associated check in the Employee Payroll Vouchers form, which is available on the Payroll|View menu. Note: To use this feature, worksite managers and worksite trusted advisors must also have user role access to the Reprint Payroll Checks form (MVQ.CONTROL*REPRINT.CHECK.MAINT process ID).

Enhancement to PTO Benefit Plans Form (PD-17295) — You can enable the new Apply Carryover toward Maximum Accrual Per Year field to implement Colorado and Maine paid leave.

Enhancement to Work Groups Form (PD-17419) — A new field, Obsolete, now displays on the Work Groups form, which is available on the Client|Change menu.

Enhancements to Data Import Tool (PD-17580) — The existing Global W/C Classification Rates import template is now available on the Import Template field in the Data Import Tool. Note: Previously, you could only access this import template from the W/C Classification Rates form.

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202503.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_QR202503.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

= Enhancement to Work Groups Form (PD-15207) — The Employees Assigned to Work Group form, which is accessible by selecting Employees Assigned To on the Actions menu in the Work Groups form with a Work Group selected, now displays in the standard format used throughout the product.

Enhancement to Payroll History Form (PD-17815) — Previously, users who had Deny access to the Payroll Summary form and Full access to the Payroll History form were able to access the Payroll Summary form from the Payroll History form. When users are set to Deny access to the Payroll Summary form and Full access to the Payroll History form, they can no longer access the Payroll Summary form by selecting a payroll listed in the Payroll History form.

Removal of SuperBatch Legacy (PD-18061) — SuperBatch Legacy, the original version of SuperBatch, has been removed from the system. Instead, you must use SuperBatch, the enhanced payroll processing hub, which was introduced in 2024.

New Marketplace Link (PD-18314) — A new link, Marketplace, now displays on the PrismHR menu bar. Selecting Marketplace provides quick access to the PrismHR Marketing|Expanded Services web site, where you can connect with vendors.

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202504.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202504.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

Enhancement to Pay Import Definition Form (PD-10616) — A new option, Clients Assigned To, now displays on the Actions menu in the Pay Import Definition form. Selecting this option displays the Clients Assigned to Pay Import Definition form for the selected Definition ID.

Enhancement to PEO Client Accounting Form (PD-17917) — A new Pay Period End Date element, PPENDDATE, now displays when you select Data in the Custom Layout panel on the PEO Client Accounting form.

Enhancements to Users Form (PD-18918) — A new Human Resources Role, Payroll - Print Garnishment Checks, now displays for worksite managers and worksite trusted advisors.

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202506.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202506.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

Enhancement to Reprint Payroll Checks and Employee Payroll Vouchers Forms (PD-18919) — Service providers, worksite managers, and worksite trusted advisors must now have Full access to the Reprint Payroll Checks and Employee Payroll Vouchers forms to use the Reprint Payroll Checks link and the question mark ( [Image: screenshot] ) on the Payroll Reports form, and the Reprint option on the Employee Payroll Vouchers form, to reprint payroll checks or payroll vouchers, respectively.

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202507.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202507.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

Enhancements to Users Form (WSP-1230) — A new field, Security by, is now available on the Users form. You can use the Security by field to configure a user’s Data Security access hierarchy, so you can easily manage which employees the user can access. Note: The Security by field is available for service providers with access to configure a worksite manager’s (WSM) Data Security.

========================================================================

PrismHR Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202509.htm Path: PD/Release-Notes/Release-Highlights/2025/Prism_Release_Highlights_R202509.htm

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Highlight — Description

Enhancement to Manager User Setup Form (PD-19622) — To control access to the Manager User Setup form for worksite managers and worksite trusted advisors, service providers can now add field-level security for sMFA device expiration using the Field option on the User Roles form.

========================================================================

Revision_MR_202401

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202401.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202401.htm

Revision 01

========================================================================

Revision_MR_202402

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202402.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202402.htm

Revision 01

========================================================================

Revision_MR_202404

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202404.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202404.htm

Revision 01

========================================================================

Revision_MR_202405

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202405.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202405.htm

Revision 01

========================================================================

Revision_MR_202407

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202407.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202407.htm

Revision 01

========================================================================

Revision_MR_202408

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202408.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202408.htm

Revision 01

========================================================================

Revision_MR_202409

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202409.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202409.htm

Revision 02

========================================================================

Revision_MR_202410

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202410.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202410.htm

Revision 01

========================================================================

Revision_MR_202412

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_MR_202412.htm Path: PD/Release-Notes/Revisions/2024/Revision_MR_202412.htm

Revision 01

========================================================================

Revision_QR_202403

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_QR_202403.htm Path: PD/Release-Notes/Revisions/2024/Revision_QR_202403.htm

Revision 02

========================================================================

Revision_QR_202406

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_QR_202406.htm Path: PD/Release-Notes/Revisions/2024/Revision_QR_202406.htm

Revision 01

========================================================================

Revision_QR_202411

Source: https://tech-docs.prismhr.com/SP_help/Content/PD/Release-Notes/Revisions/2024/Revision_QR_202411.htm Path: PD/Release-Notes/Revisions/2024/Revision_QR_202411.htm

Revision 01

========================================================================

Release Notes R_202511

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2025/11/Release-Notes-R_202511.htm Path: Release-Notes/2025/11/Release-Notes-R_202511.htm

Release Notes R_202511

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202511 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday November 20, 2025
Wave 2 Friday November 21, 2025
On-Premise Monday November 24, 2025

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-1819 Group Benefit Plans form Redesign On the Group Benefit Plans form, the paycheck and taxes related fields from different sections have been moved to the newly created Paycheck & Taxes section. This section is displayed for all the insurance classes. [Image: screenshot] The Paycheck & Taxes section has now the following fields which were earlier under different sections: - Pay Stub Name - Suppress Print On Check - Suppress All Processing On Arrears Vouchers - Report On Form W2 - Report Premium Cost On W2 Note: There is no change in the existing functionality.
WSP-2883, WSP-2890 New Plan Anniversary Month and Plan Anniversary Override Month fields On the Retirement Plans form, a new drop-down field named Plan Anniversary Month has been introduced to add new anniversary date to calculate the Next Auto Escalation Date. [Image: screenshot] On the Benefit Plan Setup form, when you select Plan Class as Retirement, then a new field named Plan Anniversary Override Month has been added to allow users to override Plan Anniversary Month selection made on the Retirement Plans form. Additionally, the selection that you make in the Plan Anniversary Month field on the Retirement Plans form is displayed as read-only next to the Plan Anniversary Override Month field. [Image: screenshot] Note: While using Plan Anniversary in the calculation of the Next Auto Escalation Date, the system uses the value defined in the Plan Anniversary Override Month and Day field on the Benefit Plan Setup form. If the plan anniversary override value is not defined, then the system uses the value defined in the Plan Anniversary Month and Day field on the Retirement Plans form. If both the above mentioned fields are left blank, then the system uses the value defined in the Start Date field on the Benefit Plan Setup form as the plan anniversary date.
WSP-2861 Changes to the Retirement Plan Enrollment form On the Retirement Plan Enrollment form, under the Election Details section, a new read-only table named Retirement HPE Status has been added to assist users in identifying why a contribution was redirected. The table is displayed only when you select a plan and provide an effective date. [Image: screenshot]
WSP-2913 New Deemed ROTH and Deemed ROTH Override fields According to the Secure 2.0 Act, employees who meet the HPE Threshold for prior year and make a catchup contribution to a 401k, 403b or 457b plan, must make that contribution on a ROTH basis. This Act is effective starting January 1, 2026. On the Retirement Plans form, a new drop-down field named Deemed ROTH has been added for users to allow plans elect a provision to force Pre-tax contributions to ROTH contributions AND/OR Pre-tax Catchup contributions to ROTH Catchup contributions regardless of whether the 402G limit has been met. [Image: screenshot] The Deemed ROTH drop-down field has the following options: - -Select- - This option uses the same logic as the No (Default) option. - No (default) - Pre-tax Catchup contributions is taken as pre-tax until total pre-tax contributions equals the 402G limit. Once the 402G limit is reached, no further Pre-tax or Pre-tax Catchup will be taken for contributions. Note: For example, if an employee meets the HPE threshold for the prior year (Example: 2025), then the pre-tax contribution is limited to $23,500. Any elected ROTH and ROTH Catchup contributions will continue up to the limits. Any remaining pre-tax Catchup contributions will not be forced to ROTH Catchup contribution. - Pre-tax Catchup to ROTH Catchup after 402(g) limit - Pre-tax Catchup contributions may be taken up to the point when total pre-tax contributions equal the 402G limit. Any further catchup contributions will be taken as a ROTH catchup contribution. Note: For example, if an employee meets the HPE threshold for the prior year (Example: 2025), then the pre-tax contribution is limited to $23,500 with any remaining Catchup contributions taken as ROTH Catchup contribution for the following year (Example: 2026). - Pre-tax Catchup to ROTH Catchup before 402(g) limit - Pre-tax Catchup contributions will be taken as a ROTH Catchup regardless of whether the total pre-tax contributions equal the 402G limit. Note: For example, if an employee meets the HPE threshold for the prior year (Example: 2025), then the pre-tax contribution is limited to $23,500. However, all the pre-tax Catchup contributions are taken as ROTH Catchup contribution regardless of whether the total pre-tax contributions equals the 402G limit. - Pre-tax to ROTH and Pre-tax Catchup to ROTH Catchup after 402(g) limit - Pre-tax and Pre-tax Catchup contributions may be taken up to the point when total pre-tax contributions equal the 402G limit. At this point, all pre-tax elections will be taken as ROTH and all Pre-tax Catchup will be taken as ROTH Catchup contributions. Note: For example, if an employee meets the HPE threshold for the prior year (Example: 2025), then the pre-tax contribution is limited to $23,500 with any remaining pre-tax contributions taken as ROTH and pre-tax Catchup contributions taken as ROTH Catchup for the following year (Example: 2026). Please note that currently, the 402(G) limit is equal to the Contribution Limit defined on the Tax Year Limits Maintenance form. The Catch Up Limit is also defined on this form. Additionally, the 402(G) limit and the Catch Up limit can be overridden by defining limits under the Plan Year Deferral Limits section on the Retirement Plans form. On the Benefit Plan Setup form, when you select Plan Class as Retirement, then a new field named Deemed ROTH Override has been added to allow users to override Deemed ROTH selection made on the Retirement Plans form. Additionally, the selection that you make in the Deemed ROTH field on the Retirement Plans form is displayed as read-only next to the Deemed ROTH Override field. [Image: screenshot] Note: When you check Prohibit Deductions for either of the following on the Retirement Plans form: - Roth Post-Tax Deduction Code - Roth Catch-Up Deduction Code then, the following options are not displayed in the Deemed ROTH drop-down options: - Pre-tax Catchup to ROTH Catchup after 402(g) limit - Pre-tax Catchup to ROTH Catchup before 402(g) limit - Pre-tax to ROTH and Pre-tax Catchup to ROTH Catchup after 402(g) limit
WSP-2348 Changes to the Benefit Plan Setup form On the Benefit Plan Setup form, when you select Plan Class as Group Benefit, then under the Group Benefits Setup section, a new field named Max Days Back Dating has been added which allows users to override the Max Days Back Dating value defined on the Group Benefit Plans form for the selected Benefit Plan. [Image: screenshot] - This newly added field is an editable field. Additionally, you can only enter numbers between 1 and 999999. - The value assigned to the Max Days Back Dating field on the Group Benefit Plans form is displayed as read-only to the right of the input field on this form. Note: If the Max Days Back Dating field does not have a value defined on the Benefit Plan Setup form, but has a value defined for this field on the Group Benefit Plans form, then the system uses the value defined on the Group Benefit Plans form as default.
WSP-2569, WSP-2571, WSP-2572 Changes to the Employee Benefits Enrollment form On the Employee Benefits Enrollment form, when you manually create a benefit enrollment and in the Coverage Starts field, if you enter a date that is prior to the Current Date minus the value defined for that benefit plan in the Max Days Back Dating field on the Group Benefit Plans form, then an error message is displayed. However, if a client level override value is set for Max Days Back Dating field on the Benefit Plan Setup form, then the input in the Coverage Starts field takes the value setup on client level into consideration. [Image: screenshot] When an Employee Benefits Enrollment record is terminated, the Max Days Back Dating value is used to validate a benefit plan that is to be terminated. The Coverage Ends date now accepts the value which equal to or greater than the current date minus the Max Days Back Dating value assigned at the client level. Additionally, on the Benefits Import form, while importing a benefit plan, the Max Days Back Dating value is used to validate a benefit plan that is to be terminated.
WSP-2812 Changes on the COBRA Participant Record form On the COBRA Participant Record form, when you select a dependent Participant ID, and then click the Edit Cobra Participant Record hyperlink, the Social Security Number field on the Edit COBRA Participant Record modal form is masked based on the option that you choose to mask SSN from the SSN Mask Option field on the System Parameters form. The Social Security Number field is displayed as a read-only field. However, you can edit the SSN by clicking the Edit SSN hyperlink. For example, on the System Parameters form, if you choose Show Last Four (###-##-6789) as the option from the SSN Mask Option field, then on the COBRA Participant Record form, when you select a dependent Participant ID and click the Edit Cobra Participant Record hyperlink, the value in the Social Security Number field will be masked to display only the last four digits as shown in the image below: [Image: screenshot]
WSP-2747, WSP-2749, WSP-2754, WSP-2813, WSP-2814 Changes to the Benefit Utilities form Under the Benefit Utilities section, a new utility named Auto Escalation has been added to identify enrollments that are not flagged as Auto Escalation?. [Image: screenshot] When you select the Auto Escalation utility, the Report Filters section is displayed. Under the Reports Filters section: - Select the Employment Status Class. This filter has the following options: - All Classes - Active - On Leave - Terminated - Select the Enrollment History from the drop-down options. This filter has the following options: - All Enrollments (Default) - Only enrollments without contribution changes - Only enrollments with contribution changes - 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 their Client IDs here or click the Client ID link and select them from the Select Clients dialog box. - Retirement Plan ID - This field is required. Enter the Retirement Plan ID or click the Retirement Plan ID hyperlink to select from the Select Plan dialog box. Now, click Search. A job control runs. Once the job control process is completed, click Close to view the list of employee with retirement plan enrollments that are not flagged as Auto Escalation?. The Results section displays the following columns: - Search Employee Name - This input field allows you to search for a specific employee name. Additionally, when you search for an employee, the results are displayed only within the batch selected. - Batch No. - It represents the threshold for the returned records. For example, if the threshold is to display 1000 records in one batch and the total results returned are 2500, then it will be divided into 3 batch, where Batch 1 will have 1000 records, Batch 2 will display the next 1000 records, and Batch 3 will display the remaining 500 records. You can select the batch number from the drop-down list. Note: If you make any changes to any of the records in a certain batch and select a different Batch Number, then the system displays a warning message stating, There are unsaved changes that will be lost. Are you sure you want to change batches? - Click Yes to close the warning message and jump to the selected batch number. Any unsaved changes to the original batch will be lost. - Click No to remain on the original selected batch number. - Client ID - Unique ID of the client with which the employee is associated. - Employee Name - Name of the employee. It is displayed as a hyperlink. Clicking this opens the Employee Details form with the information of the selected employee. - Employment Status Class - Current status of the employee’s employment. - Retirement Plan ID - The retirement plans to which the employees are enrolled. - Status - Status of the retirement plan. - Status Date - The status date. - Retirement Benefit Group - The retirement benefit group in which the employee is enrolled in. - Election Changes Exist - - Last Effective Date - The last effective date from which the retirement plan was active. Select the record(s) that you want to update the Auto Escalation? checkbox with the most recent Effective Date listed within the Election Details of the retirement enrollment record and click Update. Based on the number of records you have selected, a confirmation message stating, Auto Escalation Enrollments will be updated. Are you sure? is displayed. - Click Yes to update the selected records. - Click No to remain on the form.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
WSP-2910 Changes to the Employee Details Form On the Employee Details form, under the Other tab, under the Miscellaneous section, the following two new fields have been introduced: - Qualified OT Exempt - As of [Image: screenshot] Field Name — Description Qualified OT Exempt — This field is optional. This field is a check box. This field currently has no functionality, but it can be leveraged to determine which employees should not be included in future qualified OT imports for 2025. In 2026 and beyond, this field will be used to exclude employees from any future development to automate or recalculate these amounts. As of — This field only displays once the Qualified OT Exempt field is selected. If you have selected the Qualified OT Exempt field, this field is required. Provide the date from when you want to block the system from accumulating qualified OT for any employee. For more information, see the in-product help or PrismHRHuman Resources User Guide.
Field Name Description
Qualified OT Exempt This field is optional. This field is a check box. This field currently has no functionality, but it can be leveraged to determine which employees should not be included in future qualified OT imports for 2025. In 2026 and beyond, this field will be used to exclude employees from any future development to automate or recalculate these amounts.
As of This field only displays once the Qualified OT Exempt field is selected. If you have selected the Qualified OT Exempt field, this field is required. Provide the date from when you want to block the system from accumulating qualified OT for any employee.
WSP-2923 Changes to the Pay Codes Form On the Pay Codes form, under the Processing Options section, the following two new fields have been introduced: - Qualified OT Factor - Pay Code is used to pay daily OT [Image: screenshot] Field Name — Description Qualified OT Factor — This field is optional. Define the percentage of overtime pay that should be included in qualified overtime calculations by selecting the appropriate factor from the following options to ensure only eligible overtime amounts are reported in compliance with OBBBA’s rules. - – Select– (default) - 100% : Half time - Calculates at the standard 0.5 of the employee’s hourly rate. - 50% : Double Time (1x) - Calculates at the standard employee’s standard full hourly rate. - 33% : Time & A Half - Calculates at 1.5x of the employees standard hourly rate. - 25% : Double time (2x) - Calculates at 2x of the employees standard hourly rate. Pay Code is used to pay daily OT — This field is optional. This is an informational setting that will be used in future reports to flag employees who may be receiving daily OT and require additional review for FG overtime. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
Field Name Description
Qualified OT Factor This field is optional. Define the percentage of overtime pay that should be included in qualified overtime calculations by selecting the appropriate factor from the following options to ensure only eligible overtime amounts are reported in compliance with OBBBA’s rules. - – Select– (default) - 100% : Half time - Calculates at the standard 0.5 of the employee’s hourly rate. - 50% : Double Time (1x) - Calculates at the standard employee’s standard full hourly rate. - 33% : Time & A Half - Calculates at 1.5x of the employees standard hourly rate. - 25% : Double time (2x) - Calculates at 2x of the employees standard hourly rate.
Pay Code is used to pay daily OT This field is optional. This is an informational setting that will be used in future reports to flag employees who may be receiving daily OT and require additional review for FG overtime.
WSP-2718, WSP-2724 Changes to the Print Service Global Check Parameters Form On the Print Service Global Check Parameters form, under the Global Check Configuration section, a new field named Exclude suppressed Pay Codes in Gross Pay on Checks? has been introduced. [Image: screenshot] When on the Pay Codes form, the Print on Paystub field is set to NO, Suppress Printing on Pay Stub, the following grid illustrates the functionality of this field: [Image: screenshot] For more information, see the in-product help or PrismHR System Administration User Guide.
WSP-2723, WSP-2724 Changes to the Print Service Options Form On the Print Service Options form, a new field named Exclude suppressed Pay Codes in Gross Pay on Checks? has been introduced. [Image: screenshot] When on the Pay Codes form, the Print on Paystub field is set to NO, Suppress Printing on Pay Stub, the following grid illustrates the functionality of this field: [Image: screenshot] For more information, see the in-product help or PrismHR Client Administration User Guide.
CMP-336 Changes to the State Garnishment Rules Form On the State Garnishment Rules form, under the Rules for Calculating Withholding for Child-Support Payments section, a new field named Include Charged Tips In Base Pay? has been introduced. [Image: screenshot] This field indicates whether charged tips are included in base pay when calculating the maximum amount to garnish for child support for the selected state. This field is a drop-down. Select of the following options: - Yes (Default) - Charged tips (a pay code with class of earnings flagged for used to pay for charged tips) will be included in the base pay. This option retains the existing functionality to calculate the child support garnishment. - No - Charged tips will not be included in the base pay. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
CMP-6793 CMP-6795 Changes to the State Rules Form On the State Rules form, only for the state of Oregon, a new field named SIT Combined Reporting is introduced. This field does not appear for any other state. This field will be used during payroll processing to force the tax basis for specific state taxes to be assigned the same tax entity (PEO or Client) as is assigned for SUTA. [Image: screenshot] Oregon is a combined reporting state that has historically always been PEO report only. To support Oregon HB 2236(Permits professional employer organizations (PEOs) to report payroll information in aggregate on behalf of their clients) this new option has been added. For combined reporting, all state taxes must report on the same level including SIT. While we support this today for SUTA and SUTA Components, SIT could previously only be set to an override on the employer level. With this option, for pay dates starting 1/1/2026, Oregon employers now can change the PEO/Client reporting designation for additional Oregon state taxes that do not naturally follow the client reporting dates within the client detail tax tab. - This is not a required field. - Unchecked - This field is unchecked by default. When this field is not set on Oregon, AND for all client types other than PEO, AND for all states other than Oregon, there will be no change in tax basis. - Checked - When this field is checked for OREGON PEO CLIENT TYPES, all of the following taxes will report using the same tax basis P or C for PEO Clients: - 38-23 (WBF) - Employee - 38-24 (SUTA) - Employer - 38-26 (WBF) - Employer - 38-27 (State transit) - Employee - 38-28 (SUTA offset) - Employer - 38-20 (SIT) - Employee - 38-40 (PFML) - Employee - 38-41 (PFML) - Employer - 38-51 (Lane Transit) - Employer - 38-52 (TRI COUNTY TRANSIT) - Employer - When you select this field, you will receive a warning stating Warning, payroll processing will use the SUTA tax entity for other state taxes with the tax IDs 20,23,26,27,28,40,41,51,52. Are you sure? You can click Yes or No. - The existing tax basis designation hierarchy Tax Deduction → State Rule → Employer Detail → Client Detail is extended to the State Tax Deduction codes that are currently excluded such that: - If SUTA is configured to be PEO or Client, all of the above tax codes follow the SUTA Reporting designation. - Not all Oregon tax codes will follow the new SIT setting. For example, the following state and local tax codes are excluded from this logic: - 38-46 (Portland Metro SHS). - Any County or Local tax codes. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
WSP-2310, WSP-2313, WSP-2369, WSP-2708 Client Global PTO Maintenance form (NEW) Use this new form to view and configure client specific Global PTO parameters. [Image: screenshot] To access this form, click Client. Under Client\ Change, click Client Global PTO Maintenance. To configure client specific Global PTO parameters: - 1. Complete the following fields: Field Name — Description Excluded Plans by State — This field is optional. This form provides the ability to exclude full states from the Global PTO enrollment and accrual process. This option is intended for clients who may be required to provide State Sick Leave in certain states but not all. If you want to, you can now exclude certain Global PTO Benefit Plans from the enrollment and accrual once the client is enabled for Global PTO. - State - You can enter the two digit state codes manually or you can click the State hyperlink and select them from the Select States (permitted list of States Code records configured on the State Rules form) dialog box. You cannot select a state here that is already listed in the Global PTO Plan Overrides section below. - Description - This field automatically populates the state name once the State field is populated. Excluded Plans by ID — This field is optional. If multiple Global PTO Benefit plans exist on the State Rules form for a state, and you need to prevent enrollment and accrual in one or more plans for that state for the client, you can enter the specific Global PTO Benefit Plan IDs here. If client has Global PTO Benefit Plan IDs configured under this field, then creation and/or accrual of any Global PTO plan(s) identified in this field will be ignored. - Exclude Plans by ID - You can enter the Global PTO Benefit Plan IDs manually or you can click the Exclude Plans by ID hyperlink and select them from the Select Global PTO Benefit Plans dialog box. You cannot select a state here that has already listed having Global PTO Plan Overrides. - Description - This field automatically populates the Global PTO Benefit Plan description once the Exclude Plans by ID field is populated. Global PTO Plan Overrides — When Global PTO Plan Override rules are configured, this section will display all existing Global PTO override rules for the client. You can click on the number hyperlink under the “Line #” column to open the Global PTO Client Override form to view the override rules for that state. You can make changes to the override rules on that form and save the changes which will reflect here upon editing. The following columns display for this section: - Line # - State - Plan ID - I/E - Employee Type - I/E - Pay Method - Override Plan ID Sort By — This field is drop-down. You can select the sort order for the list above by any one of the following options: - Order Applied (Default) - State - Plan ID - Employee Type - Pay Method - Override Plan ID 2. Click Save to save the changes. 3. Click Delete to delete all records of Global PTO exclusions for this client. 4. Click New Rule to open the Global PTO Client Override. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
Field Name Description
Excluded Plans by State This field is optional. This form provides the ability to exclude full states from the Global PTO enrollment and accrual process. This option is intended for clients who may be required to provide State Sick Leave in certain states but not all. If you want to, you can now exclude certain Global PTO Benefit Plans from the enrollment and accrual once the client is enabled for Global PTO. - State - You can enter the two digit state codes manually or you can click the State hyperlink and select them from the Select States (permitted list of States Code records configured on the State Rules form) dialog box. You cannot select a state here that is already listed in the Global PTO Plan Overrides section below. - Description - This field automatically populates the state name once the State field is populated.
Excluded Plans by ID This field is optional. If multiple Global PTO Benefit plans exist on the State Rules form for a state, and you need to prevent enrollment and accrual in one or more plans for that state for the client, you can enter the specific Global PTO Benefit Plan IDs here. If client has Global PTO Benefit Plan IDs configured under this field, then creation and/or accrual of any Global PTO plan(s) identified in this field will be ignored. - Exclude Plans by ID - You can enter the Global PTO Benefit Plan IDs manually or you can click the Exclude Plans by ID hyperlink and select them from the Select Global PTO Benefit Plans dialog box. You cannot select a state here that has already listed having Global PTO Plan Overrides. - Description - This field automatically populates the Global PTO Benefit Plan description once the Exclude Plans by ID field is populated.
Global PTO Plan Overrides When Global PTO Plan Override rules are configured, this section will display all existing Global PTO override rules for the client. You can click on the number hyperlink under the “Line #” column to open the Global PTO Client Override form to view the override rules for that state. You can make changes to the override rules on that form and save the changes which will reflect here upon editing. The following columns display for this section: - Line # - State - Plan ID - I/E - Employee Type - I/E - Pay Method - Override Plan ID
Sort By This field is drop-down. You can select the sort order for the list above by any one of the following options: - Order Applied (Default) - State - Plan ID - Employee Type - Pay Method - Override Plan ID
WSP-2311, WSP-2370, WSP-2877 Global PTO Client Override Form (NEW) Use this new form to view and configure client specific Global PTO override rules. [Image: screenshot] You can only access form using the Client Global PTO Maintenance form. Click the New Rule button on this form to open the Global PTO Client Override form. You will not find this form from the search bar. To configure client specific Global PTO override rules: - 1. Complete the following fields: Field Name — Description Employee Type — Select groups of employees based on their Employee Type to override the existing global pto enroll and accrual logic. Select either Include or Exclude from the drop-down for one more Employee Type. You can manually enter them here. Click the Employee Type hyperlink and select them from the Select Employee Type Codes dialog box. Pay Method — Select groups of employees based on their pay method to override the existing global pto enroll and accrual logic. Select either Include or Exclude from the drop-down for one or more of the following pay methods: - Hourly - Salary - Variable Salary - Commission - Driver State Code — Enter the state for which the override rule applies. Enter a two-digit State code that has NOT already been added to the Excluded Plans By State grid on the Client Global PTO Maintenance form. PTO Benefit Plan — Select the PTO Benefit Plan that the override rule applies to. Select a Global PTO Benefit Plan ID available for the selected state from the drop-down. Override PTO Plan ID — Select an existing Global PTO Benefit Plan to replace the Global PTO Benefit Plan set in the PTO Benefit Plan field. This is a required field unless the Exempt employees from accruals in this PTO Benefit Plan field is checked. Exempt employees from accruals in this PTO Benefit Plan — Check this field to exempt employees from accruals in this PTO Benefit Plan for the client. Note: When you check this field, the Override PTO Plan ID field will be cleared. 2. Click Save to save the changes for the client-specific Global PTO override rule. You cannot save this form if: - both the Employee Type and Pay Method fields and blank for a Global PTO override rule, OR, - for a specified state, the Override PTO Plan ID field is blank and also the Exempt employees from accruals in this PTO Benefit Plan field is not checked. 3. Click Delete to delete the override PTO plan for the state. 4. Click Cancel to clear this form. 5. Click Close to close this form and return to the Client Global PTO Maintenance form. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
Field Name Description
Employee Type Select groups of employees based on their Employee Type to override the existing global pto enroll and accrual logic. Select either Include or Exclude from the drop-down for one more Employee Type. You can manually enter them here. Click the Employee Type hyperlink and select them from the Select Employee Type Codes dialog box.
Pay Method Select groups of employees based on their pay method to override the existing global pto enroll and accrual logic. Select either Include or Exclude from the drop-down for one or more of the following pay methods: - Hourly - Salary - Variable Salary - Commission - Driver
State Code Enter the state for which the override rule applies. Enter a two-digit State code that has NOT already been added to the Excluded Plans By State grid on the Client Global PTO Maintenance form.
PTO Benefit Plan Select the PTO Benefit Plan that the override rule applies to. Select a Global PTO Benefit Plan ID available for the selected state from the drop-down.
Override PTO Plan ID Select an existing Global PTO Benefit Plan to replace the Global PTO Benefit Plan set in the PTO Benefit Plan field. This is a required field unless the Exempt employees from accruals in this PTO Benefit Plan field is checked.
Exempt employees from accruals in this PTO Benefit Plan Check this field to exempt employees from accruals in this PTO Benefit Plan for the client. Note: When you check this field, the Override PTO Plan ID field will be cleared.
CMP-6811 Validation of SOC to TTOC relationship On the Positions form, from now on, the system will validate when you enter a TTO Code against the SOC Code during the creation of or updating a Position. [Image: screenshot] - Invalid TTO/SOC combinations result in an error message: TTO code [] and SOC code [] are not related. - Invalid TTO code results in an error message: TTO Code [] does not exist. - Invalid entries cannot be saved. - Valid TTO code entry is allowed when the SOC code is blank. For more information, see the in-product help or PrismHR Client Administration User Guide.
CMP-6821 W-2 Delaware PFML update Beginning Tax Year 2025, for the state of Delaware, the YTD Employee PFML contribution (tax Code 08-40) will be added to the Form W-2 build for both SBEA and non-SBEA clients to report on the employee’s Form W-2 and Form W-2c in Box 14 with the description DEPFML. The amount reported is the total employee PFML contributions withheld for the year.
CMP-6820 W-2 Maine PFML update Beginning Tax Year 2025, for the state of Maine, the YTD Employee PFML contribution (tax Code 20-40) will be added to the Form W-2 build for both SBEA and non-SBEA clients to report on the employee’s Form W-2 and Form W-2c in Box 14 with the description MEPFML. The amount reported is the total employee PFML contributions withheld for the year.
CMP-6590 W-2 Oregon PFML update Beginning Tax Year 2025, for the state of Oregon, the YTD Employee PFML contribution (tax Code 38-40) will be added to the Form W-2 build for both SBEA and non-SBEA clients to report on the employee’s Form W-2 and Form W-2c in Box 14 with the description PFMLI. The amount reported is the total employee PFML contributions withheld for the year.
CMP-6837 Employer Tax for Paid Family and Medical Leave To support the new Minnesota PFML tax deductions, significant changes will be effective 1.1.26; State Misc 3 ER (-41), which has historically also been used to support the employer PFML portion, but is currently being used for the Minnesota Additional Assessment Fee. To support the separation of the Minnesota Admin Assessment fee from the employer PFML tax logic, we have introduced a new State Misc 4 Employer Tax Identifier, -54. For pay dates on or after 1.1.26, tax code 24-41will be used for employer contributions to Minnesota PFML. The Minnesota Additional Assessment tax will be reassigned to tax code 24-54. To prepare for this transition, the following updates will be required: - 1. Tax Code & Report Settings - Update the description of the existing tax code 24-41 and add the description to tax code 26-54. - Tax Code 24-41 : Minnesota Paid Family Medical Leave (Employer) - Tax Code 24-54 : Minnesota Admin Assessment Fee - Ensure the tax code 26-41 PEO\ Client report setting is configured to Client before 1/1/2026 payrolls. 2. PrismHR Tax & MasterTax Mapping - Update the tax code mapping for PrismHR Tax & MasterTax imports to reflect the new identifier. 3. Rate Overrides - Migrate any existing rate overrides for the Minnesota Admin Assessment fee to State Misc4. - Use State Misc3 for Minnesota Employer PFML rate overrides. 4. Tax Suppression Review - Remove any suppressions that may interfere with the new tax code functionality.
CMP-6840 New State Misc4 Rate field introduced For each of the following forms, a new field named State Misc4 Rate has been introduced. Enter the state miscellaneous 4 rate here, for example for tax code 24-54 (Minnesota). Employer Tax Rate (SUTA) [Image: screenshot] State Tax Rates (SUTA) [Image: screenshot] State Tax Bill Rates (SUTA) [Image: screenshot] For more information, see the in-product help or PrismHR Employer Administration User Guide or PrismHR Billing User Guide

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-9410 Universal Employee ID on Employee Details The Employee Details form in Manager Portal now displays an employee’s Universal Employee ID for the PrismONE application. Managers can use this information to verify that employees have connected their accounts to the PrismONE Mobile App or other PrismONE ID integrations. For more information, see the in-product help.
EP-9571 Retirement Plan Setup Option to Prohibit 401k Deductions Clients can now prohibit employees from editing or enrolling in retirement plans that include deduction types marked as Prohibited. If this option is selected, when an employee views the Employee Contributions form, the following rules apply: - If the employee does not have an Employee Contributions amount toward the Prohibited deduction type, the deduction type is hidden. - If the employee does have an amount on the Prohibited deduction type, the employee must enter a null value for that deduction type to save their updates. With this configuration option, clients can restrict employees from making updates to deductions that are prohibited by their employer or plan administrator. For more information, see the in-product help.
EP-9631, EP-9632, EP-9633, EP-9634, EP-9635, EP-9636, EP-9639, EP-9640, EP-9641, EP-9642 Enhanced Employee Details Enhanced Employee Details The Employee Details form in Employee Portal has been enhanced with an updated user interface designed to provide more visibility and ease of navigation while retaining all current functionality. The new form design has more available space, making it easier to view more of the employee’s information at once. For example: [Image: screenshot] Menu options are now arranged as a horizontal bar, providing more screen space for employee information below. Information is now arranged in columns which are sized to the current screen, providing full support for mobile devices and desktop displays of various sizes. HR Actions are now accessed via a menu on the right. Select HR Actions to display a menu with all available options. When a HR Action is selected, the HR Action options remain displayed as a menu, allowing managers to quickly navigate through and perform several actions. To return to the employee information, simply select one of the menu tabs. For example: [Image: screenshot] Using this new configuration, managers can view employee information more easily by viewing more details at a time and navigating quickly through menu tabs and HR Actions. For more information, see the in-product help.
EP-9668 Taxable Wages on Payroll Inquiry Form Employees can now view taxable wage information on the Taxes Withheld tab on the Payroll Inquiry form. This form displays a breakdown of all taxes withheld from their pay, such as Medicare and Social Security. Employees can use this form to verify that their taxes are being withheld correctly based on their pre-tax savings. For more information, see the in-product help.

Onboarding / Benefits Enrollment (OBE) Enhancements

Ticket Description Summary Help Content
OBE-6813 Warning Message for Same Effective Date as Posting If the system detects that an existing Benefit Coverage Detail record has the same effective date as the Benefit Enrollment posting process, a warning message now informs the service provider conducting the process. This warning displays the company, employee ID, employee name, and offer type of the posting to make it easier to determine the discrepancy. The batch can still be posted successfully by disregarding this warning message, if necessary. For more information, see the in-product help.
OBE-9711 Enhancement to Decision Recommendation Tool Wording Plans suggested by a Decision Recommendation Tool during Benefits Enrollment now display the Save plan button, which is used to save the plan details as the recommended plan for later steps. The previous wording, Select plan, implied that only the recommended plans could be selected, and has been changed. When a user saves a recommended plan, the plan displays with a label indicating that it was saved on that recommendation tool. In addition, users can select the menu item for their decision recommendation tool to compare saved plans. For more information, see the in-product help.
WSP-2740 Enhancement to Unarchive Benefits Web Enrollment To improve visibility, the Unarchive Benefits Web Enrollment form no longer displays the Batch Number, Batch Status, and Completed Batch fields. These fields almost never displayed relevant information for this form, and thus have been removed. For more information, see the in-product help.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
PD-20003 Billing Enhancement to Billing Rules (Unbundled) Form The Select Billing Rules list, which is accessible by selecting Billing Rule on the Billing Rules (Unbundled) form, now displays values for the following fields: - Rule Number - Rule Description - Rate - Rule Based On - Rule End Date - Voucher Type - Batch Type - Obsolete - Obsolete Date - Billing Code - Benefit Plan For example: [Image: screenshot] For more information, see the in-product help or PrismHR Billing User Guide.
PD-19722 and PD-19749 Client Enhancement to PTO Benefit Plans and Time Off Setup Workflow Forms In association with the Nebraska Healthy Families and Workplaces Act in effect as of October 1, 2025, which allows employees to begin accruing leave after they have worked 80 hours, a new field, Begin accruing hours AFTER ___ hours worked, now displays in the Flat Amount per Hours Worked panel on the legacyPTO Benefit Plans form and the Time Off Setup Workflow form. For example: PTO Benefit Plans form [Image: screenshot] Time Off Setup Workflow form [Image: screenshot] > Note: Note the following: - You must select the Flat Amount by Hours Worked option in the following fields to display the Begin accruing hours AFTER ___ hours worked field: - Calculation Basis field on the PTO Benefit Plans form - Accrual Method field in the Plans panel on the Time Off Setup Workflow form - Employees do not begin accruing hours until they reach the number of hours worked as entered in the Begin accruing hours AFTER ___ hours worked field. - Accruals differ depending on whether you enable If the actual hours worked are not an even multiple of the hours worked then accrue a fraction of the accrual hours. For more information, see the in-product help, PrismHR Client Administration Guide, or PrismHR PTO User Guide.
RRT-6601 Client Enhancement to PTO Register Types Form The warning that displays when you select End of Quarter in the Trigger Method field on the PTO Register Types form was updated to provide more clarity when using this setting. For example: [Image: screenshot] For more information, see the in-product help or PrismHR Client Administration Guide.
WSP-2628 Client Enhancement to Client Details Form The Classifications panel in the Client Details form now provides the following: - A truncated version of the SIC Code and NAICS Code names using ellipses (…) now displays. (Cursor over the SIC Code and NAICS Code descriptions to display their full name.) For example: [Image: screenshot] - The first three multi-entity groups associated with a client now display in alphabetical order, which replaced the original Multi-Entity Group field. (You can scroll down to view other multi-entity groups.) For example: [Image: screenshot] In addition, you can select a multi-entity group to display its details in the Multi-Entity Group Details form. > Note: Note the following: - Users whose user role is set to FULL or INQUIRY for the Multi-Entity Group Details form have enabled access to the links that display in the Multi-Entity Group column. - Users whose user role is set to DENY for the Multi-Entity Group Details form can only view the client details (no links display in the Multi-Entity Group column). For more information, see the in-product help or PrismHR Client Administration Guide.
WSP-2780 Client Enhancement to Compute Commissions Form The system now computes the Commission Basis Amount for PTG Commission Base in the Compute Commissions form using the calculation logic of the Target Amount divided by the number of invoices. For example, if there are four invoices in the commission period, the Target amount (10000) would be divided by the four invoices in the period, which would set the Commission Basis Amount = 2500. (This is logically consistent with Net commission = Commission Basis Amount * Percent rate; 2500 * 30% = 750.) For more information, see the in-product help or PrismHR Client Administration Guide.
API-7687, PD-19029, PD-20208, and PD-20210 Human Resources Enhancements to Employee Details Form The following enhancements are now available on the Employee Details form: - The system now updates an employee’s mailing address across clients for employees who have the same Employee ID for multiple clients. - Information for the following fields no longer displays after an employee is deidentified using the Inactive Data Deletion form: - Work Email - Work Phone - The audit entry for deidentified employees that displays on the File Audit form now displays the user ID and the IP address of the user who ran the deidentification process. (Previously, the User ID field displayed “Background Process” and the Client IP Address field displayed “N/A.”) For example: [Image: screenshot] For more information, see the in-product help or PrismHR Human Resources User Guide.
PD-19191 Human Resources Enhancement to Approvals Pending Form Previously, the PTO amounts in the Approvals Pending form did not match the amounts in Employee Portal (EP). To resolve this issue, leave approvals now display the hours from the employee’s PTO register in the Detail Description column in the Approval Summary section: - Register YTD Accrued - Register YTD Taken - Register YTD Available For more information, see the in-product help or PrismHR Human Resources User Guide.
PD-19952 Human Resources Enhancement to Employee Fields Import Form Four new WH347 fields now display on the Select Field list in the Employee Fields Import form when you select Field Code in the Fields to Update panel. For example: [Image: screenshot] > Note: Note the following: - These fields reside in the WH347 Skilled Trade Classification panel on the Skills & Education tab in the Employee Details form. - All WH347 fields are required as part of the import, but fields other than the Journeyworker/Apprentice field can have a blank value for the data. - The WH347 Apprentice Program Approval and WH347 Level of Progression fields are only allowed if you enter Apprentice (RA) in the Journeyworker/Apprentice field. For more information, see the in-product help or PrismHRHuman Resources User Guide.
PD-20206 Human Resources Enhancement to Employee Dependents Form The system now removes the following field information in the Employee Dependents form from employee records when an employee is deidentified: Dependent Details panel: - Last Name - First Name - Social Security Number Address Details panel: - Address - Address Line 2 - ZIP Code - City - State - Primary Phone - Work Phone - Email Note: To deidentify employees, select Employees in the Data Type field on the Inactive Data Deletion form. (For more information, refer to the “Removing Inactive Customer Data” topic in the PrismHR Client Administration Guide, which displays when you select the help ( [Image: screenshot] ) icon in the Inactive Data Deletion form.) For more information, see the in-product help or PrismHR Human Resources User Guide.
WSP-1731 and WSP-1732 Human Resources Enhancement to Mass Employee H/R Actions Form A new field, Employee Selection Method, now displays on the Mass Employee H/R Actions form. For example: [Image: screenshot] You can use the Employee Selection Method field to select employees from a generated list or import a list of employees for a mass H/R action using the following options: - Generate List: Selecting this option and completing the required fields generates a list of employees who meet the selected criteria. - Import List: Selecting this option and completing the required fields displays the Upload Employees button, which you can select to import your list of employees who meet the selected criteria. > Note: Note the following when working with Import List: - The system only accepts uploaded files as a single-column list of employee IDs in either .txt or .csv format. - Employees listed in the import file who do not exist in the selected client are automatically excluded from the import. - The system validates the contents of the imported employee list and if any employee does not pass validation, they are not included in the on-screen report. In addition, if “Fail” displays in the Import Status column in the report, this indicates that the employee does not match the selected criteria. (You can access this report by selecting Download Report.) - If no employees pass validation a message displays, “There were no employees with selected.” > Note: Note the following: - Users whose user role is set to FULL for the Mass Employee H/R Actions form have enabled access to the fields on this form. - Users whose user role is set to INQUIRY for the Mass Employee H/R Actions form only have view access to the fields on this form. - A message displays when you select one of the options listed above. (This message originally displayed when making a selection from the H/R Action field.) For example: [Image: screenshot] Click OK to continue. - You cannot edit the H/R Action or Employee Selection Method after making a selection in these fields. (Click Cancel to clear the form.) For more information, see the in-product help or PrismHR Human Resources User Guide.
WSP-2836, WSP-2837, and WSP-2838 New Employee Import Enhancement to New Employee Import Dashboard Three new options, Division, Department, and Project Codes, are now available in the Table field on the Employee Import Code Translation Tables form, which you can access by selecting Code Translation Tables on the New Employee Import dashboard. For example: [Image: screenshot] You can use the Division, Department, and Project Codes options to set up a translation table for division, department, and project codes, so you can use this translation table to change the import file code to an accepted PrismHR code. For more information, see the in-product help or PrismHR New Employee Import User Guide.
PD-19174 Payroll Enhancement to Employee PTO Accruals Report A new column, Current Balance, now displays in the Employee PTO Accruals Report. For example: [Image: screenshot] The Current Balance column displays the YTD hours available for each employee from the Employee PTO Register for each register type. For more information, see the in-product help or PrismHR Payroll Reports guide.
PD-19549 Payroll Enhancement to Eligible PTO Report Form The system did not display the correct column headers in the XLS report output of the Eligible PTO Hours Report that you can generate using the Eligible PTO Report form. All columns now display the correct header in the XLS report output. In addition, the following columns now display in the XLS output of the Eligible PTO Hours Report: - Calc Hours: The weekly average of the hours the employee worked. - Balance: Subtracts the hours used from the eligibility hours. - 5+: Indicates if the employee was hired more than five years ago. For example: [Image: screenshot] For more information, see the in-product help or PrismHR Payroll Reports guide.
PD-19968 Payroll Enhancement to Summary Time Sheet Entry Form A new column, Status Type, now displays on the Summary Time Sheet Entry form. For example: [Image: screenshot] The Status Type column displays the employee’s classification status (first part of status type) and employee type (second part of status type, separated by a dash (-); for example, A-FT): - Classification status: A for active, L for on leave, or T for terminated. - Employee Type: FT for full-time and PT for part-time. For more information, see the in-product help or PrismHR Payroll Processing Guide.
PD-20035 Payroll Enhancement to Batch Payments Form A new column, Edit Employee Details, now displays when you select Yes in the Suppress Allocation column in the Batch Payments form. For example: [Image: screenshot] Selecting the Edit Employee Details ( [Image: screenshot] ) icon in this column displays the Time Sheet Allocation form, where you can assign the Department, Division, Location, Shift, Position, Project, and Phase allocations. For example: [Image: screenshot] After entering the allocation types, click Accept to apply the values to the batch payment. Note: If you override the home data fields in the Time Sheet Allocation form, a checkmark displays in the Edit Employee Details column in the Batch Payments form. For more information, see the in-product help or PrismHR Payroll Overrides Guide.
PD-20141, PD-20142, PD-20143, and PD-20144 Payroll Enhancements to Payments Pending Form The following enhancements now reside on the Payments Pending form: - You now have better visibility into the wire processing status when a payroll is in WT.PEND status, so you can stay informed about the progress and status of this process. The payroll still resides in WT.PEND status, but it will have a secondary status to help you understand whether the file has been created for the bank. As part of this updated process, the secondary status changes to “Created” after users create a file during ACH processing. - Four new fields, File Status, Transfer Type, Client ID, and Cost Center, now display. For example: [Image: screenshot] These new fields display the following information: - File Status: Displays the wire processing status, which is either Created or Pending. (Only wire transfers display Pending.) - Transfer Type: The transfer method for ACH information as configured on the Billing tab in the Client Details form, which is either Wire Transfer or Reverse Wire. - Client ID: The ID for the client that displays in the Client Name field. - Cost Center: The description for the cost center created in the Client Details form. - The Display Invoice button no longer displays because now you can simply select a Payroll number and the invoice displays. - You can now select multiple payments to process and mark as received by selecting each Payroll line item or select all payments by clicking the new checkbox next to the Payroll column and then click Mark Received. (Previously, you could only select one payment at a time to mark as received.) - Note: After making the selection and clicking Mark Received a message displays, “Are you sure you want to mark these payments as received?” Click Yes to continue. (This updates the batch Status so the payroll processor can continue to process the payroll batch.) For more information, see the in-product help or PrismHR Payroll Processing Guide.
PD-20146 Payroll Enhancement to SuperBatch Form A new icon, [Image: screenshot] , now displays in the SuperBatch form when you create a wire file. For more information, see the in-product help, PrismHR Payroll Processing Guide, or Understanding the SuperBatch Status Icons task sheet.
PD-20148 and PD-20153 Payroll Enhancement to Scheduled Payments Form A new field, Phase, is now available on the Time Sheet Allocation form, which you can access by selecting the Edit Employee Details icon on the Scheduled Payments form. For example: [Image: screenshot] Note: You must enable the SCHEDULED-PAYMENTS-CHANGE-DEFAULTS custom feature code to display the Edit Employee Details icon. You can enter or select a Phase that is valid for the current client, which is applied during payroll processing to any payments made to the specified employee. Note: The Phase field does not display if the Project with phase option is not set up as a Detail Time Sheet Field on the Time Sheet tab in the Client Details form. For more information, see the in-product help or PrismHR Payroll Overrides Guide.
PD-20149 Payroll Enhancement to Employee Scheduled Payments Report Two new columns, Proj and Phase, now display in the output after running the Employee Scheduled Payments Report. For example: [Image: screenshot] For more information, see the in-product help or PrismHRPayroll Reports guide.
PD-20150 and PD-20151 Payroll Enhancement to Payroll Allocation Report Parameters and Payroll Allocation Report Forms You can now sort by phases using the new Allocate/Sort by Phase option in the Primary Sort, Secondary Sort, and Tertiary Sort fields on the Payroll Allocation Report Parameters and Payroll Allocation Report forms. For example: [Image: screenshot] [Image: screenshot] You can use the Allocate/Sort by Phase option to adjust the sort criteria by the project phase. Note: If you do not enable the Sort On Allocation Codes Instead of Descriptions parameter, the system will sort fields by description. In addition, if you enable the Phase option, the system will sort Phase by code (there is no description for phases). For more information, see the in-product help or PrismHR Payroll Reports guide.
PD-20205 Payroll Enhancement to Employee Garnishments Form Information for the following fields on the Employee Garnishments form no longer displays after an employee is deidentified using the Inactive Data Deletion form: - Docket Number - Annotation - Case Identifier For more information, see the in-product help or PrismHR Payroll Administration Guide.
PD-20174, WSP-2825, WSP-2826, WSP-2827, and WSP-2828 Payroll Enhancements to Data Import Tool The following enhancements now reside in the Data Import Tool, which is available on the Operations\ Import Processing menu. New TTO Code Field in Position Codes Import Template You can now import valid TTO codes (Tipped Taxable Occupation Code that applies to an eligible tipped position) while importing positions using the Position Codes import template. For example: [Image: screenshot] Note: The system displays an error during the import process if the TTO Code is invalid, “<TTO Code> is not a valid TTO Code.” New Client Details (Special Delivery) Import Template You can use this import template to import special delivery instructions for the client to reduce the amount of manual work required. For example: [Image: screenshot] The following fields that display on the Client Details (Special Delivery) import template allow you to update existing records or add new records without including the entire list of data: - Replace existing data: Replaces existing data with data included in the file but does not remove data that is not included in the file. For example: - If the system already has a delivery method for location 1 and location 1 is included in the file with changes, the system confirms the changes. - If the system already has a delivery method for location 2 and location 2 is not in the file, then the system keeps the location 2 delivery method data. - Remove existing data (default): Removes existing data that is not included in the file for that client. For example: - If the system already has a delivery method for location 1 and location 1 is included in the file with changes, the system confirms the changes. - If the system already has a delivery method for location 2 and location 2 is not in the file, then the system removes the location 2 delivery method data. - Keep existing data: Prioritizes keeping existing data and adds new data included in the file. (That is, if data exists and is included in the file, the upload skips the value in the file and keeps the existing system values.) For example: - If the system already has a delivery method for location 1 and location 1 is included in the file with changes, the system keeps the existing data, not the data included in the file. - If the system already has a delivery method for location 2 and location 2 is not in the file, then the location 2 delivery method data remains the same in the system. > Note: Note the following: - Users whose user role is set to DENY for the Client Details form cannot import data using the Client Details (Special Delivery) import template and subsequently, the Data Import Tool icon will not display on this form. - Users whose user role is set to INQUIRY for the Client Details form can view the Client Details (Special Delivery) import template, but cannot import data. - Users whose user role is set to INQUIRY for the Data Import Tool can view the form and import template options, but cannot import data. - Users who do not have access to a particular company through client access groups are unable to import data into that company. For more information, see the in-product help or PrismHR Payroll Administration Guide.
RRT-6601 PTO Enhancement to Time Off Setup Workflow Form The warning that displays when you select End of Quarter in the Accrual Frequency field on the Accrual Schedule panel in the Time Off Setup Workflow form was updated to provide more clarity when using this setting. For example: [Image: screenshot] For more information, see the in-product help or PrismHR PTO User Guide.
PD-19883 System Enhancement to ACH Files Effective March 20, 2026, regardless of ACH volume, all Prearranged Payment and Deposit Entry (PPD) Credits for wages and similar compensation now includes the description “PAYROLL” in Position 54-63 in the Company Entry Description field in the ACH file. Note: This standardization helps RDFIs better identify payroll-related transactions and prevent fraud associated with payroll redirections. (The ACH files now reflect this information.) Important! If you are using a Third Party Format in the ACH Originators form for the ACH file this update will not affect those files. For information about ACH files, see the in-product help or PrismHR ACH User Guide.
PP-1986 System UEX Update for Prism Header and Menus The Prism UEX has received a stylistic update to the main header bar, the breadcrumb trail, and the menus. The icons, coloration, and spacing of the UI has been restyled. For example: [Image: screenshot] In addition, the Prism menus now display the category headers on their own lines, with the categories organized into individual sections. In addition, the menus can now display three or four columns based on the available space in the browser window. For example: [Image: screenshot] This enhancement updates the user interface throughout Prism to improve the experience navigating menus and breadcrumb trails. For more information, see the in-product help or PrismHR System Administration Guide.
PP-2036 System Style Updates for Sign In Screens The Sign In form and the Reset Password form have been updated to the current UX standards and maintain consistency across the platform. For more information, see the in-product help or PrismHR System Administration Guide.
PP-2074 System Enhancement to the Employee Portal Configuration Size To support the new drag-and-drop interface for resizing widgets in Employee Portal Configuration Templates and Client Overrides, the Dashboard Configuration form now supports a wider and taller viewport size. For more information, see the in-product help or PrismHR System Administration Guide.
WSP-2789 System Enhancement to User Roles Form You can now obsolete a user role that is no longer in use by enabling Obsolete on the User Roles form. For example: [Image: screenshot] In addition, selecting Role ID displays the User Role Search list, where the new Obsolete column indicates whether the user role is obsolete (Y) or not obsolete (N). For example: [Image: screenshot] > Note: Note the following: - You cannot assign an obsoleted role to a user or obsolete a user role that is currently assigned to users. If this occurs an error message displays, “This role must be removed from all users before it can be obsoleted!” - Once a user role is obsolete, you cannot manually enter an obsoleted role for a user. For more information, see the in-product help or PrismHR System Administration Guide.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-2733 Previously, on the Retirement Register Adjustment form, when you created a new transaction and saved the form without providing any input in the Adjustment Date field, an error with a message stating, Adjustment Date is mandatory was displayed. Upon clicking Ok, the Adjustment Date field was disabled and you could not enter the any value in the required field, which was incorrect. Now, this is fixed. While saving the form for a new transaction, if you miss to fill any required fields, and when you close the warning message, you can now enter the missing required fields and save the form.
WSP-2752 Previously, on the Benefits Eligibility Report form, when you ran a report, in the Benefits Eligibility Summary Report that was displayed, all the applicable benefit rules for a Benefit Group were not displayed. Now, this is fixed.
WSP-2795 Previously, on the Employee Retirement Loans form, when you selected the Loan Number, the Employee ID displayed but the Employee Name did not display automatically. Additionally, when you opened the Employee Retirement Loans form in a modal view, the Close button did not work properly. Now, this is fixed.
WSP-2796 Previously, on different Group Benefit forms, while using the Employee selector, when you searched for an employee in the Employee ID or Name search field, the results displayed the search term which was not within the Employee ID or Name criteria. This was an incorrect behavior. Now, this is fixed.
WSP-2810 Previously, on the Retirement Plan Enrollment form, the warning message validation that appeared when you changed a value in any fields worked for only the elective amount fields. Now, this is fixed. The warning message validation that appeared when you changed a value in any fields now works for all the election fields.
WSP-2835 Previously, on the Employee Dependents form, when a dependent of an employee had a Social Security Number and if the SSN Mask Override field on the Report Print Options form was set to Show Employee ID, then the Social Security Number field for that dependent displayed blank values. Now, this is fixed. When you set SSN Mask Override as Show Employee ID, then on the Employee Dependents form, if an employee has a dependent, the Employee ID is displayed as a read-only text in the Social Security Number field.
WSP-2855 Previously, on the Retirement Plan Enrollment form, after you select an active enrolled Employee, and then under the Retirement Register Adjustments section, when you click the hyperlink value under the Transaction No. column, then on the Retirement Register Adjustment modal form that is displayed, the Cancel button appears on the form, which was not an expected behavior. Now, this is fixed.
WSP-2856 Previously, on the Retirement Plan Enrollment form, the system allowed invalid setups in the Elective Amount field that did not work with the Auto Escalation? field, which lead to potential configuration errors. Now, this is fixed. The Auto Escalation? checkbox can be selected only when: - Elective Type has a value in the Amount field which is greater than 0 and Percent is selected. - Elective Type has a value in the Amount field which is greater than 0 with Percent selected and additional values exist in the Employee Contributions table.
Jira # Issue Summary Resolution
CMP-6930 Previously, on the Positions form, after clicking the Benefit Group hyperlink, you received different errors. Now, this is resolved. On the Positions form, after clicking the Benefit Group hyperlink, you are presented with the benefit groups set up for that client.
CMP-6849 Previously, when the Recalculate Taxes on Vouchers process was run, and an employee had taxable wages with overlimit wages to the SUTA state being processed that had been backed out via tax adjustment before running the utility, the did not recognize the tax adjustments. Now, when the Recalculate Taxes on Vouchers process is run, and an employee has taxable wages with overlimit wages to the SUTA state being processed that have been backed out via tax adjustment before running the utility, the adjustment will continue to occur. Each occurrence will be reported in the processing reports, on-screen process log report, and the Job Control Status report, including the PDF and XLS versions, with the following message stating Employee XXXXXX in company XXXXX has 0.00 Gross Taxable with an Overlimit amount >0.00, resulting in a negative tax amount. Additional adjustment may be required.
CMP-6839 Previously, for the state of Delaware, the system used to report incorrect figures for PFML (DE0000-014) on the MasterTax RTS file. Now, this is resolved. Delaware PFML records on the RTS will be updated to report: - 500 records, DE0000-014 positions 95 - 108 QTD Net Taxable Wages, Gross - Sheltered up to the wage limit (currently correct) - 500 records, DE0000-014 positions 109 - 122 YTD Net Taxable Wages, Gross - Sheltered up to the wage limit (currently correct) - 500 records, DE0000-014 positions 137 - 150 YTD Gross Taxable wages, Gross Wages - Sheltered wages NOT excluding overlimit wages 601 record, DE0000-014, positions 72 - 85 QTD Gross Taxable wages, Gross Wages - Sheltered wages NOT excluding overlimit wages - 500 records, DE0000-014 positions 123 - 136 QTD Gross Taxable wages, Gross Wages - Sheltered wages NOT excluding overlimit wages > Note: Note: This is true with SBEA and NONSBEA versions and w/wo account ID.
CMP-6787 Previously, the 500F records in the MasterTax RTS Schedule R dis not correctly report the YTD values for Q4 for the 00-12TIPs and 00-16TIPS. Now, this is resolved. 00-12TIPS and 00-16TIPS correctly report in the QTD wage amounts (positions 95-108 and 123-136) and YTD wage amounts (positions 109-122 and 137-150) in the 500F records on the Mastertax RTS, Schedule R.
CMP-6747 Previously, when an employee was assigned to a Remote Worksite Location, the FUTA bill rate was getting calculated based upon the FUTA rate applicable to the resident state, like the FUTA accrual. Now, when an employee is assigned to a Remote Worksite Location, the FUTA bill rate will be calculated based upon the FUTA rate applicable to the resident state, like the FUTA accrual.
CMP-6734 Previously, the option to exempt an employee from state withholding was not available for all states on the New Hire Entry form. Now, this is resolved.
CMP-6452 Previously, the Local EFW2 export for the Local EFW2 Code ‘Tax Services PA’ (Jordan Tax Services) was missing the required RT (Total) record. This was causing file upload errors. Now, this is resolved. Local EFW2 export for ‘Tax Services PA’ includes an RT record (total record) for each RE record (Employer record). The RW record is also present, since it is necessary for the RT record.
CMP-6450 Previously, the Local EFW2 Code ‘Tax Services Admin’ (BERKHEIMER) was missing the required employer 6-digit PSD code on the RE record position 222-227. This was causing file upload errors. Now, this is resolved. The Local EFW2 export ‘Tax Services Admin’ (BERKHEIMER) RE record position 222-227 will be zero-filled.

Employee Portal (EP) Fixes

Jira # Issue Summary Resolution
EERT-2911 When a 1099 contractor employee was employed by multiple companies but had the same Employee ID across all organizations, the 1099 form in Employee Portal did not display all pages of their form. This is fixed. If the PDF document being generated has more than one page, the employee will receive the following error message, and no PDF documents will be printed: “Please contact your Service Provider for your 1099 PDF documents”
EERT-2991 When a manager clicked More on the PTO Calendar to display additional PTO requests and there were ten or more requests for that day, the window that displayed included overlapping information that rendered the text illegible. This is fixed.
EERT-3102 When some users read and signed mandatory documents in Employee Portal, the documents still showed the Displayed status for both managers and employees. This is fixed.

Onboarding / Benefits Enrollment (OBE) Fixes

Jira # Issue Summary Resolution
EERT-3023 When a user updated a Handbook document type for Onboarding in Document Management, the document displayed the updated version for that user, but displayed the outdated document version name for employees in their Saved Documents. This is fixed.
EERT-3043 Some users erroneously received Benefits notifications intended for a different user at a different organization. This is fixed. Processes and security settings have been enhanced to prevent this issue from recurring.
EERT-3061 When a user displayed the View/Compare Benefits form during Benefits Enrollment, Spanish language options did not display properly. This is fixed.
EERT-3083 When an employee entered information for a beneficiary incorrectly, the warning message that displayed included incorrect spelling. This is fixed.
EERT-3072 When a user previewed a form in the Form Library that was built using certain default forms, the information that displayed did not match the layout that displayed to employees. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
PD-20001 General An error message that a direct deposit update failed sometimes displayed when users entered a direct deposit on the Deposit tab in the Employee Details form for employees who transferred between clients or were rehired. This is fixed.
PD-20406 General There were times when the Payment Pending form had a slow response time. This is fixed. To improve the performance on the form, Multi-Entity Groups have been removed. In the upcoming release, the indexing will be improved, and the Multi-Entity Groups will be reinstated.
PP-1933 General When a user added a new row in the Local Tax Identifiers subsection of the Employer Details form, the user could add duplicate tax codes. This is fixed.
PP-2016 General When a user made changes to individual records on the Timesheet Detail form, pressing the Enter key did not save the changes. This is fixed.
RRT-6590 General When users exported reports to Excel with a column that contained only a percent sign (%), the export failed and the system displayed an error message. This is fixed.
PD-19033 Payroll The system disregarded tax exemptions at the pay code level in the Check History Import form when users entered a value for a non-taxable payment. The system now honors Pay Code Tax Overrides when non-taxable amounts are imported.
PD-19330 Payroll The system sent a Payroll Finalization email to the Payroll Approver before the payroll was posted/finalized each time a payroll was approved. Worksite managers who are Payroll Approvers now only receive a Payroll Finalization email one time when they approve the same payroll more than once.
RRT-6577 Payroll The system did not include the employee’s ID in the error message, “There is insufficient funds to pay taxes on voucher,” in the warnings and errors when the payroll was calculated even though the issue was related to a particular employee. The system now displays the employee’s ID in the error message, so users can easily determine which employee has insufficient funds.
RRT-6672 Payroll CMP-6747 was generating payroll processing stoppages for some employees stating “Cannot read SUTA accrual rate” due to missing SUI rates. This occurred when that employee had an Override Geocode with an Override End Date set on the Address tab of the Employee Details form. This is fixed.
WSP-2782 Payroll When users imported client commissions using the Client Commissions import template and enabled the Keep existing data and update duplicate field in the Data Import Tool, the system did not honor null values as equivalent in the Salesperson, Based On, Based On Item, and Based On Plan fields and created duplicate entries on the Commissions form. This is fixed.

========================================================================

November (R_202511)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2025/11/whatsnew-R_202511.htm Path: Release-Notes/2025/11/whatsnew-R_202511.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Release Highlights

Highlight — Description

Enhancement to ACH Files (PD-19883) — Effective March 20, 2026, regardless of ACH volume, all Prearranged Payment and Deposit Entry (PPD) Credits for wages and similar compensation now includes the description “PAYROLL” in Position 54-63 in the Company Entry Description field in the ACH file.

Documentation Enhancements

Click a link to read about the documentation enhancements included in this release.

Note: Documentation enhancements will be available on the dates indicated in the Release schedule.

New User Guides

The following new guides were created:

Import Processing Guide: This guide is intended for users who need to import data into PrismHR, including file formats and details on specific imports.

Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

The following task sheets were created or updated:

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202512

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2025/12/Release-Notes-R_202512.htm Path: Release-Notes/2025/12/Release-Notes-R_202512.htm

Release Notes R_202512

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202512 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday December 11, 2025
Wave 2 Friday December 12, 2025
On-Premise Thursday December 15, 2025

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-2800, WSP-2801 Changes to the Benefit Utilities form Under the Benefit Utilities section, after selecting the Auto Escalation utility, when you click Search, a new button named Report has been added in the Results section which allows to generate a report of the search results. [Image: screenshot] While displaying the results, if the threshold is reached, the results are then displayed in batches. When there are multiple batches, and you click Report, a pop-up message is displayed stating, Do you wish to generate a report for the current batch or all batches? - Click Current Batch to display the report for the current batch. - Click All Batches to display the report results for all the batches available in the search results. To update the records displayed in the search results, select the record(s) and click Update. Once the records are updated, you can view the report. For more information, see Benefit Utilities help topic.
WSP-3086 Changes to the Retirement Plan Enrollment form On the Retirement Plan Enrollment form, when you select a plan and provide an effective date, then under the Election Details section, the earlier read-only Retirement HPE Status table has been renamed to Mandatory Roth Catch-up Participant. [Image: screenshot] For more information, see Election Details help topic.
WSP-3111 Temporary logic for Pre-tax Catchup to ROTH Catchup after 402(g) limit selection On the following forms, - Retirement Plans - Benefit Plan Setup when you select the Pre-tax Catchup to ROTH Catchup after 402(g) limit option for the Deemed ROTH field, the system uses the same logic that is used for the No (Default) option. When you select Deemed ROTH as No (Default), then the Pre-tax Catchup contributions is taken as pre-tax until total pre-tax contributions equals the 402G limit. Once the 402G limit is reached, no further Pre-tax or Pre-tax Catchup is taken for contributions. For more information, see Setting Up Basic Information for a Retirement Plan and Setting Up a Benefit Plan help topics.
WSP-2914, WSP-2915. WSP-2916 Functionality of options under the Deemed ROTH field The Secure 2.0 Act includes a mandatory Roth catch-up requirement for Highly Paid Employees (HPE) participating in a 401(k), 403(b), or 457 retirement plan. For the 2026 tax year, employees with $150,000 in prior year, Social Security wages must contribute catch-up on a Roth basis, to the extent they have not previously made Roth contributions during the year. To comply with this Act, we introduced the following options for the Deemed ROTH field on the Retirement Plans form: - No (default) - Pre-tax Catchup to ROTH Catchup after 402(g) limit - Pre-tax Catchup to ROTH Catchup before 402(g) limit - Pre-tax to ROTH and Pre-tax Catchup to ROTH Catchup after 402(g) limit Determining a Highly Paid Employee - An employee is considered to be an HPE only if the corresponding Retirement Year is defined and the HPE Prior Year field is set to Yes on the Mandatory Roth Catch-up Participant table under the Other tab on the Employee Details form. The functionality of the drop-down options for the Deemed ROTH field are listed below: - No (default) - This option is selected by default. Selecting this option signifies that a plan does not have a Deemed ROTH feature. Additionally, this option does not force any amounts to ROTH or ROTH Catchup. However, any elected ROTH and ROTH Catchup contributions will continue until limits are reached. For example, if an employee is an HPE for prior year and the plan offers a ROTH catchup component, then Pretax catchup is taken until the 402G limit is met. Once the Pre-tax and the Pre-tax Catchup contribution hits the 402G limit ($23,500), then the Pre-tax contributions stops, and any elected ROTH and ROTH Catchup contributions can continue up to the limits ($23,500/$7,500). - Pre-tax Catchup to ROTH Catchup after 402(g) limit - This option will be available with the January release. Currently, this selection this option uses the logic of No (default) option. - Pre-tax Catchup to ROTH Catchup before 402(g) limit - This option automatically treats all subject employee Pre-tax catch-up elections as Roth elections regardless of whether the total pre-tax contributions equal the 402(g) limit. It limits the Pretax contributions to $23,500 for HPEs. Note: Please note the following: - This option will not be available when Prohibit Deductions is checked for either of the following on the Retirement Plans form: - Roth Post-Tax Deduction Code - Roth Catch-Up Deduction Code - If an HPE has a retirement Catchup deductions taken as Roth Catchup, the deduction is taken using the Roth Catch-Up Deduction Code assigned under the Deduction/Bill Code Overrides section on the Retirement Plans form. When there is no code on the Retirement Plans form, then the Roth Catch-up Deduction Code assigned at the system level is used as default. - When the deduction is taken using the Roth Catch-Up Deduction Code, the deduction displays as a ROTH catchup on voucher and on the Employee Retirement Plan Register form. - Pre-tax to ROTH and Pre-tax Catchup to ROTH Catchup after 402(g) limit - This option automatically treats subject employee pre-tax elections as Roth elections only after pre-tax contributions reach the standard contribution limit. This means that the Pre-tax elections are limited to $23,500 and if there are any remaining Pre-tax elections, they are taken as Roth elections. Note: Please note the following: - This option will not be available when Prohibit Deductions is checked for either of the following on the Retirement Plans form: - Roth Post-Tax Deduction Code - Roth Catch-Up Deduction Code - If an HPE has a retirement pre-tax or Catchup deductions taken as Roth or Roth Catchup, the deduction is taken using the Roth and Roth Catch-Up Deduction Code assigned under the Deduction/Bill Code Overrides section on the Retirement Plans form. When there is no code on the Retirement Plans form, then the Roth or Roth Catch-up Deduction Code assigned at the system level is used as default. - When the deduction is taken using the Roth or Roth Catch-Up Deduction Code, the deduction displays as a Roth or Roth catchup on voucher and on the Employee Retirement Plan Register form. For more information, see, Setting Up Basic Information for a Retirement Plan and Setting Up a Benefit Plan help topics.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
CMP-6892 Use Employer SUI Rate as Company SUI Bill Rate When the Use ER SUI rate as Bill rate setting is applied, you can use the Client State Tax Bill Rate for PFML State Misc3 ER (-41) codes when a Client State Tax Bill rate record exists. On the Miscellaneous Global Parameters form, if the Use Employer SUI Rate as Company SUI Bill Rate field is checked: - If no Client Bill rate record is set up on the client, Tax Bill rates will use the ER Tax Rate form (or vertex default if missing) - If Client Bill rate record is set up on the client, Tax Bill rates will use the ER Tax Rate form for all taxes (or vertex default if missing) except for tax code XX-41 (Employer PFML Bill Rate) When the Use ER SUI rate as Bill rate setting is applied, to use the client bill rate for State Misc 3 Employer (Paid Family Medical Leave), you must set a 0.00 Client SUI Bill rate. All Client Bill rates will be ignored except for the State Misc 3 for PFML. For more information, see the in-product help or PrismHR System Administration User Guide.
- If no Client Bill rate record is set up on the client, Tax Bill rates will use the ER Tax Rate form (or vertex default if missing)
- If Client Bill rate record is set up on the client, Tax Bill rates will use the ER Tax Rate form for all taxes (or vertex default if missing) except for tax code XX-41 (Employer PFML Bill Rate)
CMP-6329 Updates to Form W-2 build The State Income Tax Account Number on the employee Form W-2 will now be pulled from the Client Details form or the Employer Details form based on the tax deduction code, unless an override exists on the Employer Details form on the SIT Rpt Entity field for that state under the State Tax section. The State Income Tax Account Number on the employee Form W-2 will be: - Client State Tax ID when: - Tax deduction code set to report at Client Level and ER Details, State is set to -select- or Client - Tax deduction code NOT set to report at Client Level, but ER Details, State is set to Client - Employer State Tax ID: - Tax deduction code NOT set to report at Client Level and ER Details, State is set to -select- or Employer - Tax deduction code set to report at Client Level, but ER Details, State is set to Employer > Note: Note: If the State Tax ID is not available on the corresponding reporting entity, the Form W-2 will not build, and an error will appear on the W2 Error Report stating State Employer ID not found for Client # for State XX OR State Employer ID not found for Employer for State XX For more information, see the in-product help or PrismHR Employer Administration User Guide.
- Client State Tax ID when:
- Tax deduction code set to report at Client Level and ER Details, State is set to -select- or Client
- Tax deduction code NOT set to report at Client Level, but ER Details, State is set to Client
- Employer State Tax ID:
- Tax deduction code NOT set to report at Client Level and ER Details, State is set to -select- or Employer
- Tax deduction code set to report at Client Level, but ER Details, State is set to Employer
CMP-6825 Changes to the EFW2 and EFW2C Download file The Address tab on the Employee Details form auto-populates the State field once you enter the ZIP Code field. However, you can change it manually. In case, the lower case is used for the State field, the EFW2 Download file used to pick up that lower case which resulted in filing failures. The same applies to the use of tilde in the employee’s name, etc. From now on, to avoid filing failures, the EFW2 and EFW2C Download file will: Will only accept any of the following; all other characters will be excluded: - - Uppercase letters (A-Z) (If the state is in proper case, the export will translate it to upper case) - Numbers (0-9) - Space - Hyphen (-) - Period (.) For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-6856, CMP-6822 Qualified Tips & Overtime (New Form) Use the Qualified Tips and Overtime form to update the annual data for qualified overtime and qualified tips to report them in the employee Form W-2 for the tax year This option is provided to support federal reporting and compliance requirements supporting the One Big Beautiful Bill Act (OBBBA). For more information, please visit the article named OBBBA No Tax Setup Guide on the Customer Resource Center. If an employee works for multiple clients in a tax year, this form will report information for the activeclient only. If an employee works for multiple clients in the same employer, then Box 14 will have combined amounts when built on the employer. W2 data will be aggregated by employer if applicable. If an employee works between multiple positions, you should determine a single TTO Code for reporting purposes. Box 14 of the employee Form W-2 reports the qualified tips and overtime dollar amounts against the following applicable designations for SBEA and employer builds: - Approx Qualified OT - TTOC <TTO Code1>; Cash Tips If an employee works for multiple clients in the same employer, then Box 14 will have combined amounts when built on the employer. [Image: screenshot] You will not be able to access this form via the search bar. To access this form for an employee, select the employee in the Employee Details form. From the Actions menu, select the Qualified Tips and Overtime form for the employee for the client. Note: This information can also be added via the Data Import Tool. Please see the PD Release Notes. To report qualified overtime and tips for an employee for an active client: 1. Complete the following fields: Field Name — Description Employee ID — This field is auto-populated with the Employee ID from the Employee Details form. Client ID — This field is auto-populated with the active Client ID. Employer ID — If the employee has more than one employer for the active client in the tax year, select the Employer ID for the list of employer IDs available in the drop-down. This list will populate the main employer for the client and any alternate employer assigned to the client. Entity ID — If the active client is set up to have a Client Federal Entity, it will display here. Note: If the client was cloned from another client prior to the option to clone the Client Federal Entity on the utility, you may see a federal entity when there should not be. If this occurs you should remove the entity on the client by following the steps listed here. Year — Select the tax year. TTO Code — Enter the TTO Code (Tipped Taxable Occupation Code) manually, or you can click the TTO Code hyperlink and select it from the TTO Codes dialog. TTOC Tip Amount — Enter the TTOC Tip Amount for the corresponding TTO Code. Premium OT Amount — Enter an approximate premium portion of overtime, if applicable. 2. Click Save to save the record. 3. Click Cancel to clear the form. Changes made to this form will be removed, but the auto-populated fields will display as is. 4. Click Delete to delete the record. 5. Click Close to close this form at any time. For more information, see the in-product help or PrismHR Human Resources User Guide.
- Approx Qualified OT
- TTOC <TTO Code1>; Cash Tips
1. Complete the following fields:
Field Name Description
Employee ID This field is auto-populated with the Employee ID from the Employee Details form.
Client ID This field is auto-populated with the active Client ID.
Employer ID If the employee has more than one employer for the active client in the tax year, select the Employer ID for the list of employer IDs available in the drop-down. This list will populate the main employer for the client and any alternate employer assigned to the client.
Entity ID If the active client is set up to have a Client Federal Entity, it will display here. Note: If the client was cloned from another client prior to the option to clone the Client Federal Entity on the utility, you may see a federal entity when there should not be. If this occurs you should remove the entity on the client by following the steps listed here.
Year Select the tax year.
TTO Code Enter the TTO Code (Tipped Taxable Occupation Code) manually, or you can click the TTO Code hyperlink and select it from the TTO Codes dialog.
TTOC Tip Amount Enter the TTOC Tip Amount for the corresponding TTO Code.
Premium OT Amount Enter an approximate premium portion of overtime, if applicable.
2. Click Save to save the record.
3. Click Cancel to clear the form. Changes made to this form will be removed, but the auto-populated fields will display as is.
4. Click Delete to delete the record.
5. Click Close to close this form at any time.
CMP-6837, CMP-6924, CMP-6946 Minnesota Employer Tax for Paid Family and Medical Leave To support the new Minnesota PFML tax deductions, significant changes will be effective 1.1.26; State Misc 3 ER (-41), which has historically also been used to support the employer PFML portion, but is currently being used for the Minnesota Additional Assessment Fee. To support the separation of the Minnesota Admin Assessment fee from the employer PFML tax logic, we have introduced a new State Misc 4 Employer Tax Identifier, -54. For pay dates on or after 1.1.26, tax code 24-41will be used for employer contributions to Minnesota PFML. The Minnesota Additional Assessment tax will be reassigned to tax code 24-54. To prepare for this transition, the following updates will be required: 1. Tax Code & Report Settings - Update the description of the existing tax code 24-41 and add the description to tax code 26-54. - Tax Code 24-41 : Minnesota Paid Family Medical Leave (Employer). - Tax Code 24-54: Minnesota Additional Assessment or Minnesota Admin Assessment. 2. PrismHR Tax & MasterTax Mapping - Update the tax code mapping for PrismHR Tax & MasterTax imports to reflect the new identifier. 3. Rate Overrides - Migrate any existing rate overrides for the Minnesota Admin Assessment fee to State Misc4. - Use State Misc3 for Minnesota Employer PFML rate overrides. 4. Tax Suppression Review - Remove any suppression that may interfere with the new tax code functionality. - For the state of Minnesota, the employer portion for Paid Family and Medical Leave tax amounts for tax code 24-41 will appear on check stubs in the Employer Contribution section as MN PFML, showing accurate current and year-to-date tax amounts for pay dates on or after January 1, 2026. [Image: screenshot] - When tax code 24-41 is redirected to an alternate tax deduction code, for the state of Minnesota, the employer portion for Paid Family and Medical Leave tax amounts will appear on check stubs in the Employer Contribution section as MN PFML Private, displaying accurate current and year-to-date tax amounts for pay dates on or after January 1, 2026. [Image: screenshot] For more information, see the in-product help or PrismHR Employer Administration User Guide.
1. Tax Code & Report Settings
- Update the description of the existing tax code 24-41 and add the description to tax code 26-54.
- Tax Code 24-41 : Minnesota Paid Family Medical Leave (Employer).
- Tax Code 24-54: Minnesota Additional Assessment or Minnesota Admin Assessment.
2. PrismHR Tax & MasterTax Mapping
- Update the tax code mapping for PrismHR Tax & MasterTax imports to reflect the new identifier.
3. Rate Overrides
- Migrate any existing rate overrides for the Minnesota Admin Assessment fee to State Misc4.
- Use State Misc3 for Minnesota Employer PFML rate overrides.
4. Tax Suppression Review
- Remove any suppression that may interfere with the new tax code functionality.
- For the state of Minnesota, the employer portion for Paid Family and Medical Leave tax amounts for tax code 24-41 will appear on check stubs in the Employer Contribution section as MN PFML, showing accurate current and year-to-date tax amounts for pay dates on or after January 1, 2026.
- When tax code 24-41 is redirected to an alternate tax deduction code, for the state of Minnesota, the employer portion for Paid Family and Medical Leave tax amounts will appear on check stubs in the Employer Contribution section as MN PFML Private, displaying accurate current and year-to-date tax amounts for pay dates on or after January 1, 2026.
CMP-6791, CMP-6845, CMP-6846 Changes to the Tax Deductions form The Tax Deductions form has a new field named Form W2 Box 14 Override. [Image: screenshot] \ Field Name \
Field Name Description
Form W2 Box 14 Override Select one of the following options: - – Select – : There is no override for the specified tax code. - Suppress from Box 14 : The specified tax code will not be included in the Form W-2 though the tax will be withheld. - Include in Box 14 : The specified tax code will be included in the Form W-2. > Note: Note: The Tax Deduction code W2 override is intended to support W2 reporting requirements for Private State PFML Plans when the standard tax deduction is redirected to a unique tax code. While this can be extended to other tax codes, there are a few limitations when the overrides do not apply. Following are some examples: - NYC borough which is translated to a single NYC Code. - Colorado Occupational Privilege Tax codes - Oregon Transit tax codes
- – Select – : There is no override for the specified tax code.
- Suppress from Box 14 : The specified tax code will not be included in the Form W-2 though the tax will be withheld.
- Include in Box 14 : The specified tax code will be included in the Form W-2.
- NYC borough which is translated to a single NYC Code.
- Colorado Occupational Privilege Tax codes
- Oregon Transit tax codes
Box 14 Description Override This field only displays if Include in Box 14 is selected above. Enter the description of the specified tax code that you want to display on the Form W-2.
CMP-6900 Changes to the EFW2 Download for Maine The 2025 Maine EFW2 download will contain the required updates: - RS record: - EE PFML contribution amounts as reported in Box 14 of the W-2 in positions 308 - 317 - Blank filled in positions 318 - 512 - RT record: - Positions 10 - 24 report the Total of State taxable wages from the RS records (positions 276-286) for the ER, right-justify, and zero-fill. - Positions 25 - 39 report the Total of State income tax withheld from the RS records (positions 287-297) for ER, right-justify, and zero-fill. - Fill positions 40 - 512 with blanks For more information, see the in-product help or PrismHR Employer Administration User Guide.
- RS record:
- EE PFML contribution amounts as reported in Box 14 of the W-2 in positions 308 - 317
- Blank filled in positions 318 - 512
- RT record:
- Positions 10 - 24 report the Total of State taxable wages from the RS records (positions 276-286) for the ER, right-justify, and zero-fill.
- Positions 25 - 39 report the Total of State income tax withheld from the RS records (positions 287-297) for ER, right-justify, and zero-fill.
- Fill positions 40 - 512 with blanks
CMP-6831, CMP-6959, API-8438 ACA Transmission File update for 2025 For the year 2025, the SoftwareId on the manifest will be 25A0023083 when the file is run for original, replacement, correction, additional clients, etc. For the year 2024, the SoftwareId it will continue to display 24A0019620. Note: This does not apply to the California e-file. This update will be available following the 2025 December release on Monday 12/22/2025. For more information, see the in-product help or PrismHR ACA User Guide.
CMP-6824 Reporting changes to Form WH-347 Please note the following changes regarding Form WH-347; [Image: screenshot] [Image: screenshot] [Image: screenshot] [Image: screenshot] [Image: screenshot]

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-9580, EP-9581, EP-9582, EP-9583 Year-End Tax Forms Now Available Year-end tax forms are now available to view in Employee Portal. These include the W-2, W-2C, 1099, and 1095C forms. For more information, see the in-app help.
EP-9705, EP-9776, EP-9777 ROTH Banner for Highly Paid Employees Employees who are flagged as Highly Paid Employees (HPE) on the Other tab of the Employee Details form will now see a banner regarding their eligibility for catch-up deductions on retirement plans. Clients can customize this banner using a new option on the Configuration Template and Client Override forms. Select the Custom HPE Roth Banner option to display custom text boxes for both English and Spanish versions of the banner. Clients can use this feature to comply with the new SECURE 2.0 regulations regarding highly paid employees at their organizations. For more information, see the in-app help.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
PD-20315 and WSP-2941 Human Resources Enhancements to Employee Fields Import Form - Two new fields, Qualified OT Exempt and Qualified OT Exempt As Of, now display on the Select Field list when you select Field Code in the Fields to Update panel. For example: [Image: screenshot] > Note: Note the following: - These fields reside in the Miscellaneous panel on the Other tab in the Employee Details form. - The Qualified OT Exempt As Of field is required if the Qualified OT Exempt field is set to Yes, Y, or y. - You can now import the HPE Retirement Year and HPE Prior Year fields in the following scenarios: - The client does not have a retirement plan. - The client has a retirement plan, but it is not set up for the year being imported. - The employee is not enrolled in a retirement plan. For more information, see Performing Employee Fields Import.
PD-20316 Payroll Enhancement to Data Import Tool A new import template, Tip OT Register, is now available in the Data Import Tool. For example: [Image: screenshot] You can use the Tip OT Register import template to import employee tips and overtime data. Note: This import template is associated with the new Qualified Tips & Overtime form, which generates the annual and quarterly data for Qualified Overtime and Qualified Tips for reporting them on the employee Form W-2 for the tax year for the client. (To access this form, select the employee in the Employee Details form, then select Qualified Tips & Overtime on the Actions menu. You cannot access this form using the search bar.) For more information, see Importing Tips and Overtime Data.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-3167 Previously, on the Retirement Plans form, when a Highly Paid Employee (HPE) was enrolled in a retirement plan setup with Deemed ROTH option as Pre-tax to ROTH and Pre-tax Catchup to ROTH Catchup after 402(g) limit, then while calculating the payroll, the employee’s Roth Catchup election did not stop even after meeting the catchup limit (while not meeting contribution or pretax threshold). Now, this is fixed.
WSP-3170 Previously, on the Retirement Plans form, when the Deemed ROTH option was set to No (Default) for an HPE with Catch-Up Starts At Limit flagged on the Retirement Plan Enrollment form, then the employee was unable to contribute Pre-Tax Catchup until Elective and Pre-Tax Catchup contribution reached 402g limit, or catchup limit even if they did not reach the 402g limit. This issue was primarily dependent on the wages paid to the employee. If the employee was paid higher gross wages, then the Catch-up contribution amount reflected in the system. Now, this is fixed.
WSP-3171 Previously, in some scenarios, when an HPE was enrolled in a retirement plan setup with Deemed ROTH option as Pre-tax to ROTH and Pre-tax Catchup to ROTH Catchup after 402(g) limit, then after calculating the payroll, on the Employee Voucher form, negative Roth Catch-Up amount was displayed for deductions, which was incorrect. Now, this is fixed.

Compliance (CMP) Fixes

Jira # Issue Summary Resolution
CMP-4587 Previously, both on the Global ACA Parameters form and the Client ACA Parameters (Overrides) form, the Starts First the Month field for both new and ongoing employees were placed incorrectly. Now, this is resolved. On the Global ACA Parameters form and the Client ACA Parameters (Overrides) form, the Starts First the Month field for both new and ongoing employees now relates to the Stability Period.
CMP-6412 Previously, for both SBEA and non-SBEA clients, for the same tax year, if an employee was paid by two employers or two client federal entities, both having the same numerical values for their Employer IDs except one ad a leading zero, then on the Form W-2 of the employee, Box 12 retirement codes were overstated by the second employer. Now, this is resolved. Now, for both SBEA and non-SBEA clients, for the same tax year, if an employee was paid by two employers or two client federal entities, both having the same numerical values for their Employer IDs except one ad a leading zero, then on the Form W-2 of the employee, Box 12 retirement codes will accurately break out the data by the correct employer.
CMP-6594 Previously, when an employee was paid in more than one client under the same employer for the NY Metro Commuter tax, the P (PEO EMPLOYER) level record was overstated by the Client level information that was pulling in the wages for the employee from both clients. Now, on the P Record - the total reported is the combined total of all underlying C records.
CMP-6654 Previously, for an employee who lived in the state of Maryland, but was assigned to any other work state, and the Suppress Work State Tax field was checked on the Positions form for the employee’s position, then the State Income Tax for Maryland was not withheld correctly by the system. Now, for an employee who lives in the state of Maryland, but is assigned to any other work state, and the Suppress Work State Tax field is checked on the Positions form for the employee’s position, then the State Income Tax for Maryland is withheld correctly by the system.
CMP-6887 Previously, if employees from the state of Wisconsin updated their tax forms while filling up their Form WT-4 or Form WT-4A in the Employee Portal, it did not display in PrismHR as an unhandled tax. Now, this is fixed.
CMP-6889 Previously, for the state of Colorado, the Employer Quarterly SUTA Tax Export was missing the 12th of the month indicator in positions 212, 213, and 214 of the S records in MasterTax RTS. This caused fatal errors when uploading to the state, as these positions must contain a 0 or 1 per the ICESA File Format. Now, the Employer Quarterly SUTA Tax Export file for Colorado will report a 0 or 1 in the S records, positions 212, 213, and 214 indicating if the employee worked in a pay period that included the 12th of the applicable month during the quarter.
CMP-6932 Previously, if an employee had filed a Form W-8 BEN and was paid using a Supplemental Pay Code, and the custom feature code VSUPPLEMENTAL was not enabled in the System Parameters form, then the taxable earnings for Federal Income Tax displayed as $0.00 on the employee payroll voucher. Now, when an employee has an employee type for example W8 where the Tax Exemption field is set to Suppress All But Federal Income Tax on the Employee Types form, and is paid using a Supplemental Pay Code, the taxable earnings will report correctly on the employee payroll voucher with or without the custom feature code VSUPPLEMENTAL enabled in System Parameters form.

Employee Portal (EP) Fixes

Jira # Issue Summary Resolution
EP-9872 When some users accessed Document Management, a message banner displayed indicating an error fetching the ruleset for a client. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
PP-2112 General When a user viewed the Retirement Exports form, the names of the Client ID field and the Employer field did not display properly. This is fixed.
PD-20341 Payroll The system incorrectly calculated the Pay Schedule and Pay Group setup for the Period Start date when users processed a semi-monthly payroll, which caused the payroll to fail and displayed an error when they ran the Pay Schedule Report. This is fixed.
PD-20449 Payroll The system displayed an incorrect Pay Date for Monthly pay schedules with the Pay Day “1” day of the Month with the Pay Period End set to EOM after the Pay Date. When a Pay Schedule is set up Monthly with the Pay Day “1” day of the Month with the Pay Period End set to EOM after the Pay Date, the system creates payrolls for the Pay Group that are paid on the first of the month, where the period starts on the pay date and ends on the last day of that same month.
PD-20452 Payroll The system displayed an error message during a Position Codes import when an import contained related TTO and SOC Codes. This is fixed.

========================================================================

December (R_202512)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2025/12/whatsnew-R_202512.htm Path: Release-Notes/2025/12/whatsnew-R_202512.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202601

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/01/Release-Notes-R_202601.htm Path: Release-Notes/2026/01/Release-Notes-R_202601.htm

Release Notes R_202601

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202601 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday January 22, 2026
Wave 2 Friday January 23, 2026
On-Premise Thursday January 29, 2026

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-1820 New Reporting Section on the Group Benefit Plans form On the Group Benefit Plans form, the fields related to reporting from different sections have been moved to the newly created Reporting section which is now available below the Carrier Code Maintenance section. This section displays for all insurance class plans. [Image: screenshot] For more information, see Configuring Reporting Options help topic.
WSP-2517, WSP-2674 Changes to the Benefit Plan Setup form When you select HSA Contribution in the Plan Class field on the Benefit Plan Setup form, then the Use Benefit Groups field is enabled. Additionally, under the Company HSA Contribution section a new drop-down option named Dollar Match has been added to the Contribution Calculation Method field. [Image: screenshot] When you select the Dollar Match drop-down option, the Contribution Applies To fields defaults to a read-only Contributing Employees Only option. Additionally, the conditional section displays with the header name HSA Dollar Match Contribution with a Maximum Contribution Amount field that you can edit. For more information, see Setting Up a Benefit Plan help topic.
WSP-2675 Changes to the Payroll Process logic When an employee is allocated to the Company’s HSA Contribution as Dollar Match, then during payroll processing, the system matches the same HSA contribution to the employee’s contribution. Note: If the Maximum Contribution Amount is set for Company HSA Contribution on the Benefit Plan Setup form, then the total company contributions in a Plan Year does not exceed the amount set in the Maximum Contribution Amount field. For more information, see the in-product help.
WSP-2583 Adding HSA Creation to Audit Log On the Benefit Plan Setup form, when you set an HSA benefit plan with Company HSA Contribution setup for All HDHP Employees and the Employee is enrolled in an HDHP medical plan, then on the Employee Flexible Spending Accounts form, when you click Audit under the Actions menu, new Flex Spending Account record is created and is also tracked in the audit log. [Image: screenshot] For more information, see the in-product help.
WSP-2695 Changes to the Retirement Plans form On the Retirement Plans form, when you update an existing Retirement Plan that have active enrollments, a warning message stating Critical Warning! This Retirement Plan has active employee enrollments and should not be updated. Making changes to the plan setup can cause serious changes or disruptions to the employee deferrals. Do you still wish to update this plan? is displayed while saving the form. For more information, see the in-product help.
WSP-2874 Functionality of Pre-tax Catchup to ROTH Catchup after 402(g) limit option for Deemed ROTH field Selecting the Pre-tax Catchup to ROTH Catchup after 402(g) limit option for the Deemed ROTH field on the Retirement Plans form signifies that Pretax catchup may be taken to the point when the 402G limit is met. Any further catchup must be taken as a ROTH catchup contribution. For example, if an employee is an Highly Paid Employee (HPE) for prior year, then pretax contributions must be limited to $23,500 with any remaining Catchup contributions taken as ROTH Catchup for the following year. [Image: screenshot] For more information, see Setting Up Basic Information for a Retirement Plan help topic.
WSP-2922 Changes to the Group Benefit Plans form When you select a Benefit Plan, then under the Age Parameters section, for the Age Calculation (Month/Day) field, the Day field is now a drop-down field and is conditionally displayed only when a valid Month (January-December) is selected. [Image: screenshot] For more information, see Configuring Age Parameters help topic.
WSP-3029 Changes to the Retirement Plans form After selecting a retirement Plan ID, when you navigate to the Deduction/Bill Code Overrides section, the checkbox for Prohibit Deductions is now selectable for the Employee Loan Deduction Code row. [Image: screenshot] Additionally, when the Employee Loan Deduction Code row is checked for prohibition, then on the Employee Retirement Loans form, when you set up a retirement loan, (Prohibited) text is displayed next to the plan name in the Retirement Plan drop-down options. Note: If a loan exists for a retirement plan with Prohibit Deductions checkbox flagged for the Employee Loan Deduction Code row, then while running a payroll, the system does not take the loan deductions. For more information, see Setting Up Deductions and Bill Codes Overrides help topic.
WSP-3074, WSP-3075, WSP-3088, WSP-3089 Changes to the Group Benefit Plans form When you select a Benefit Plan, then under the Other Processing Parameters section, the Pay Rate Month and Day field has now become an optional field. However, if you enter any value for the Month field, then the Day field becomes mandatory. [Image: screenshot] Under the Other Processing Parameters section, the earlier LTD/STD Based on Salary Instead of Coverage Amount field has been renamed to Premium Based on and is now a drop-down field. Additionally, the conditional field LTD/STD Salary Limit has also been renamed to Weekly Salary Limit/Monthly Salary Limit. [Image: screenshot] Note: Please note the following: If you select a benefit plan with Offer Type as Short Term Disability (STD), then the options in the Premium Based on drop-down field are: - Calculated Coverage - This is the default option. - Rate x Weekly Salary - When you select this option, the conditional field, Weekly Salary Limit is displayed. If you select a benefit plan with Offer Type as Long Term Disability (LTD), then the value in the Premium Based on drop-down are: - Calculated Coverage - This is the default option. - Rate x Monthly Salary - When you select this option, the conditional field, Monthly Salary Limit is displayed. When you select a benefit plan with Offer Type as Life Insurance, then under the Other Processing Parameters section, a new hyperlink named View Tax Rates is added next to the Non-taxable Limit field, which redirects you to Tax Rates for Taxable Life Coverage modal form. [Image: screenshot] After you select a benefit plan with Offer Type as Life Insurance, then under the Age Reduction Schedule, the earlier Reduce coverage and premium checkbox field has been renamed to Reduce and is now a drop-down field with the following options: - Coverage Only - Coverage and Premium [Image: screenshot] For more information, see Maintaining Group Benefit Plans help topic.
WSP-3124 Changes to the Client Benefit Plan Import form On the Client Benefit Plan Import form, two new optional columns have been added for Client Plan Renewal Month and Client Plan Renewal Day fields. The sample header file is also updated to include these two newly added fields. For more information, see the in-product help.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
CMP-6095 Changes to the W2 Error Report Previously, the W2 Error Report did not include a message if an employee had a negative amount for Social Security Tips during the W2 build. Now, the W2 Error Report will indicate when an employee has a ‘Negative amount of Social Security Tips’ during the W2, or W2c builds for both SBEA and Non-SBEA clients. The FormW-2 will not be created and the NO FORM GENERATED column is indicated with an asterisk. For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-6913 Changes to the Deduction Codes form On this form, when you select the Deduction Type field as Voluntary, then under the Voluntary Classifications section, a new field named 403(b) Retirement appears as you can see from the screenshot below: [Image: screenshot] Now, you have a voluntary deduction type to support a 403(b) tax-sheltered annuity plan. The deduction amount will be exempt from Federal Withholding and resident State Withholding. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
CMP-6921 Changes to the Pay Codes form On this form, under the Processing Options section, a new field named Exclude from Qualified Tip Reporting has been added as you see from the screenshot below: [Image: screenshot] This field is unchecked by default. Check this field if you want to exclude the pay code from Qualified Tip Reporting. This field has no functionality within payroll processing, but it will be used in future recalculation and reporting options related to OBBBA. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
CMP-6974 Changes to the Update Employee W-2 Forms form Previously, on the Tax Deductions form, if for a redirected tax deduction code, the Form W2 Box 14 Override field was set to Include in Box 14, but the Box 14 Description Override field was blank, then on the Update Employee W-2 Forms form, under the Federal Form W-2 section, that tax was not included in the Other grid and was not included on the employee’s Form W-2. Now, under the same circumstances, on the Update Employee W-2 Forms form, under the Federal Form W-2 section, that redirected tax code will display under the Other grid. The Description field in the grid will use the Pay Stub Name (if available), otherwise it will use the Tax Description of that redirected tax code on the Tax Deductions form and will be included on the employee’s Form W-2. For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-7010 CMP-7032 Updates to EFW2 specifications Updates to EFW2C specifications The RE (Employer) record on the EFW2 files are updated to include: - Employer Contact Name: Positions 222 - 248 - Employer Contact Phone Number: Positions 249 - 263 (numerical characters only without dashes) - Employer email address: Positions 279 - 318 (symbols allowed) The RE (Employer) record on the EFW2C files are updated to include: - Employer Contact Name: Positions 228 - 254 - Employer Contact Phone Number: Positions 255 - 269 (numerical characters only without dashes) - Employer email address: Positions 285 - 324 (symbols allowed) For more information, see the in-product help or PrismHR Employer Administration User Guide.
- Employer Contact Name: Positions 222 - 248
- Employer Contact Phone Number: Positions 249 - 263 (numerical characters only without dashes)
- Employer email address: Positions 279 - 318 (symbols allowed)
- Employer Contact Name: Positions 228 - 254
- Employer Contact Phone Number: Positions 255 - 269 (numerical characters only without dashes)
- Employer email address: Positions 285 - 324 (symbols allowed)
CMP-7012 Flat Sum Bonus overtime for multiple pay codes The Flat Sum Bonus Overtime calculation logic has been updated to allow for multiple pay codes to be assigned to a single Flat Sum pay code. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-1827 Update Employee Address from Employee Details Managers can now update an employee’s address using the Employee Details form. Simply click the Edit buttons in the Addresses section on the Personal Info tab to edit the Resident, Mailing, or W-2 addresses. Updating this information in Employee Portal also updates the corresponding Prism record. For more information, see the in-app help.
EP-8578 Accessibility Enhancement for Skip to Content A new Skip to Content button has been added for users who can only access Employee Portal via a keyboard and need a way to skip over repetitive content. The Skip to Content button is hidden by default, but pressing the tab key for the first time on a form displays the Skip to Content button. Users can click this button to skip directly to the main content section of each form and directly to the first element in that section. For more information, see the in-app help.
EP-9550 Job Candidate Information Synchronized with Prism When a job candidate has a Date of Birth and/or SSN and is hired via Employee Portal, this information is now updated on their corresponding New Hire record in Portal and passed to Prism. For more information, see the in-app help.
EP-9637, EP-9720, EP-9721, EP-9727 Time Off Form Redesign The Time Off tab has undergone a redesign for both the employee’s My Time Off form and the manager’s My Employees Time Off tab. [Image: screenshot] The employee My Time Off tab now features an Overview tab, as well as separate tabs to view the details for each PTO plan. Current PTO requests display on the Planned tab, while past requests display on the History tab. Employees can submit PTO requests using the Request Time Off button. This button now displays a separate window, where all the PTO information can be added directly and easily. In addition, they can use the Estimate Time Off link to access a tool to estimate the amount of PTO they will have at another time. This design now matches the Time Off tab on the manager’s My Employees form. Managers can use this form to review and send PTO requests for their employees. For more information, see the in-app help.
EP-9643, EP-9644, EP-9645, EP-9646 Improved HR Actions Modals The HR Actions available to managers have been enhanced with buttons to initiate the process that open a new window with additional information. For example, to rehire an employee, click the Start Rehire Process button. A new window displays, where you can enter all the employee’s required information in a clear and straightforward process. This process is now used for the Leave of Absence, Rehire, Return to Work, and Termination HR Actions. For more information, see the in-app help.
EP-9694 Additional Filters for New Hire Dashboard The New Hire Dashboard can now be filtered by the Hire Date, Start Date, and Hired By fields. Managers can use these new filters to search for specific employees more easily. For more information, see the in-app help.
EP-9709 Enhancement to the Time Off Calendar The Employee and Type options on the Time Off Calendar now always display, and cannot be deselected using the Columns button. These fields now always display to prevent any confusion using this calendar. For more information, see the in-app help.
EP-9743, EP-9744 Standard Options for Gender and Pronoun Designations The Gender Designation field and Preferred Pronoun field now feature a standard list that matches the options available in Prism. These fields are now synchronized with Prism, allowing the standard options selected to update the corresponding record. However, custom options for these fields are no longer supported. For more information, see the in-app help.
EP-9750 View Taxable Wages on Paystub Employees can now view their taxable wages directly on their paystub on the Pay History screen. The Taxable Wages column on the Taxes Withheld tab of the Pay History form now displays the total amount of their wages that were taxable, which can then be compared to the amount of taxes withheld. For more information, see the in-app help.
EP-9882 New Dashboard Configuration Experience The Dashboard Configuration form in Prism has been redesigned to combine the Edit Content and Edit layout modes into one cohesive design. This mode is now in beta, and the old functionality is still available. [Image: screenshot] The new Dashboard Configuration experience allows Service Providers to change the content and layout of the dashboard simultaneously. Service Providers can add widgets, then resize and reposition these widgets while adding additional content without having to switch modes back and forth. In addition, widget content such as titles, data sources, and settings can be changed directly from this form. Changes to the Dashboard Configuration are saved automatically to provide a seamless experience setting up the dashboard. For more information, see the in-app help.

Identity and Access Management (IAM) Enhancements

Ticket Description Summary Help Content
IAM-2436 Enhancement to Authenticator App Name The authenticator app now displays the client name of the user’s organization instead of PrismHR Auth. For more information, see the in-app help.

Onboarding (OB) Enhancements

Ticket Description Summary Help Content
OBE-7544 Select Effective Date Calculation for Life Events Service Providers can now override the eligibility date for a Life Event on the Life Event Maintenance form. When Use Benefit Rule is selected in the Source of Effective Date field, select an option in the Eligibility Date Used From Override field to use this selection in place of the benefit rule’s eligibility date. Options for this field include: - 1st of Month after Calculated date - If Calculated is 1st of month, use that else next 1st of month - Calculated Eligibility Date For more information, see the in-app help.
OBE-7881 Benefit Enrollment Reminder Message Template Service Providers can now set up a reminder message to be used for Benefits Enrollment reminders on the Message Templates form. Simply enter BEEMPLOYEEDASHBOARDREMINDER in the Message ID field to access and edit the message template for the Benefit Enrollment Employee Dashboard. When a service provider uses the Send Reminder action on the dashboard, the email message is automatically sent using this template. For more information, see the in-app help.
OBE-9033 Generate Benefits Adjustments During Bulk Plan Termination When Service Providers conduct a bulk termination on the Terminate Benefit Plan form, the benefit adjustments are now generated automatically. This enhancement helps ensure that employees collect the full premium from their benefit plans after a bulk plan termination. For more information, see the in-app help.
OBE-9034 Suppress Benefit Calculation During Bulk Termination Service Providers can now select an option to suppress the benefit adjustments calculation on the Terminate Benefit Plan form. Suspending this option during a bulk termination of benefit plans can increase performance and make the process more efficient. For more information, see the in-app help.
OBE-9086 Send Reminder on Benefit Enrollment Plan Dashboard Service Providers can now use the Send Reminder action on the Benefit Enrollment Plan Dashboard to send reminders to employees to submit their benefit plan elections. This action uses the reminder message template set up on the new Message Templates feature for Benefits Enrollment. For more information, see the in-app help.
OBE-9349 Updated I-9 Form The most recent version of the I-9 form, edition 01/20/25 with an expiration date of 05/31/2027, is now available. This version updates the language for work authorization in Section 1 and the descriptions of certain List B documents. This new form will be made available on 1/23/26. For more information, see the in-app help.
OBE-9490 Gender Designation for Dependent Form Employees can now select a dependent’s gender using the Gender Designation field on the Edit Dependent form. This field displays as long as the Hide Gender Designation setting is not selected on the configuration template or client override. This information uses a standard list of options from Prism, and updating the Dependent form also updates the corresponding record in Prism. For more information, see the in-app help.
OBE-9491 Preferred Pronoun for Dependent Form Employees can now select a dependent’s pronoun using the Pronoun field on the Edit Dependent form. This field displays as long as the Hide Pronoun setting is not selected on the configuration template or client override. This information uses a standard list of options from Prism, and updating the Dependent form also updates the corresponding record in Prism. For more information, see the in-app help.
OBE-9508 Enhancement to Voluntary Coverage Amount When an employee accesses the Voluntary Benefit Summary form, the Coverage Amount for the employee now always displays. Previously, the coverage amount displayed based on the selection for the Include Employer Cost in Employee Self Service option on the configuration template. With this enhancement, employees can always view their coverage amount to verify their information on voluntary benefit plans. For more information, see the in-app help.
OBE-9626 Select Primary Care Provider Validation Format Service Providers can now select a format for validating an employee’s Primary Care Provider on a Group Benefit Plan. [Image: screenshot] Select Edit on the PCP Validation Format field on the Online Enrollment form to access the Edit PCP Validation Format form, which can be used to define a format template to validate physician information. Instructions for this formatting are provided on the Edit PCP Validation Format form. For more information, see the in-app help.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
WSP-3003 Accounting Enhancement to Auto Check Reconciliation Load Form A new option, Escheated Check Import, is now available in the Bank Media Format field on the Auto Check Reconciliation Load form. For example: [Image: screenshot] You can use the Escheated Check Import option to import a list of payroll checks as “Escheated,” so you can efficiently and accurately update the status of multiple checks at once (imports will accept files with the .csv format). Note: After selecting Escheated Check Import, the system disables the Checking Account Number and Exclude Account # fields. For more information, see Importing Auto Reconciliation Data.
WSP-3030 Accounting Enhancement to Unreconcile a Check Form You can now reverse check reconciliation on a check that is in the S - Stale Dated Check status code, as this feature currently functions for checks in the R - Reconciled status code. (This feature is useful for correcting issues with inappropriately reconciled records.) For more information, see Reversing Check Reconciliation.
PD-19904 Billing Enhancement to Billing Rules (Bundled) Form Two new columns, Rule Start Date and Rule End Date, now display in the Existing Bundled Rules panel on the Billing Rules (Bundled) form. For example: [Image: screenshot] The Rule Start Date and Rule End Date columns display the date when the existing bundled rule begins and ends. For more information, see Using Bundled Billing Rules.
PD-17943 Client Enhancement to Invoices Form You can now access payroll voucher details directly on the Payroll Summary form by clicking the payroll number in the Payroll column on the Invoices form. For example: [Image: screenshot] > Note: Note the following: - Users whose user role is set to FULL for the Payroll Summary form can view and update payroll voucher details. - Users whose user role is set to INQUIRY for the Payroll Summary form can only view payroll voucher details. - Users whose user role is set to DENY for the Payroll Summary form and click a payroll number will view an error message, “User does not have access to this form.” For more information, see Reviewing Invoice Information.
PD-19603 and PD-20266 Client Enhancements to Custom Features Form The following enhancements are now available on the Custom Features form: - The VARSALMETHOD global custom feature code is now available as a client-level custom feature code, VARSALMETHOD-C, in the Select Available Feature Codes list. (You can access the Custom Features form by selecting Custom Features on the Actions menu in the Client Details form.) For example: [Image: screenshot] Note: Custom feature codes are only available for service providers. Enabling the VARSALMETHOD-C custom feature code displays the Variable Salary option in the Pay Method field on the PTO Auto-Enrollment Rules Maintenance form. (You can access this form by clicking New Rule in the PTO Auto Enroll Rules form.) When enabled, the Variable Salary option lets you track the hours that salary-exempt employees actually work. - A new client-level custom feature code, BATCH-PAYMENTS-CHANGE-DEFAULTS-C, is now available in the Select Available Feature Codes list to allocate batch payments. For example: [Image: screenshot] Note: You must set the BATCH-PAYMENTS-CHANGE-DEFAULTS (system level) and BATCH-PAYMENTS-CHANGE-DEFAULTS-C (client level) custom feature codes to view the Edit Employee Details column on the Batch Payments form. For more information, see Specifying Client Custom Feature Codes and Entering Multiple Fixed, Pre-calculated Payments.
PD-20289 Client Enhancement to Client Details Form The Employee Numbers Used field, which displays in the New Hire/Employee Detail Controls panel on the Control tab in the Client Details form, now displays as Employee Number Required for EP NH. For example: [Image: screenshot] For more information, see Setting Client Control Parameters.
PD-20423 Client Enhancement to Auto Holiday Pay Form Previously, the FLSA Exempt? column name on the Auto Holiday Pay form was spelled incorrectly. This column name now displays correctly. For example: [Image: screenshot] For more information, see Adding Auto Holiday Pay.
WSP-2434, WSP-2435, WSP-2436, and WSP-2438 Client Enhancement to PTO Auto-Enrollment Rules Maintenance Form Two new fields, Trigger Rule On and Archive existing register?, now display on the PTO Auto-Enrollment Rules Maintenance form. (You can access this form by clicking New Rule in the PTO Auto Enroll Rules form.) For example: [Image: screenshot] These new fields do the following: - Trigger Rule On: Select an option to determine which event triggers the re-assessment of a rule. For example, when Trigger Rule On is set to Status/Type Change, the rule triggers during an employee status/type change process and, if criteria are met, the system enrolls that employee in the indicated plan. - Archive existing register?: Indicate whether to archive existing PTO registers when the rule is invoked based on the re-assessment of the rule. Note: You must select an option. Otherwise, an error message displays. Click OK to continue. For more information, see Specifying Time Off Auto-enroll Rules.
- You cannot use a rule trigger option more than once. If you try to reuse a trigger an error message displays, “Trigger already listed for this rule.” Click OK to continue. In addition, you can view existing PTO Auto-enrollment rules, but you cannot make any updates to them.
- Using future-dated status/type changes and position changes triggers a re-evaluation of the PTO auto-enroll rules and executes the enrollment based on the employee’s Status/Type Change or Position Change at the time the change takes effect.
- If the rule is set to archive the prior PTO Register:
- Any existing PTO Registers that share the same class as the PTO Register assigned to the affecting rule are archived.
- The system sends a notification about register archival to the user on the Status Type Change form.
- The system creates a new enrollment/register for the employee’s new plan.
- If the rule is not set to archive the prior PTO Register and no PTO Class conflicts exist with the employee’s existing register, the system creates a new enrollment/register for the employee’s new plan.
- If the rule is not set to archive the prior PTO Register and a PTO Class conflict exists, the system does not update the PTO Register and does not make any changes.
- If the change date matches or is prior to the system date and there are required approvals.
- If the change date is future-dated and there are required approvals.
- If the change date is future-dated and there are no required approvals.
- If the rule is set to archive the prior PTO Register:
- Any existing PTO Registers that share the same class as the PTO Register assigned to the affecting rule are archived.
- The system sends a notification about register archival to the user on the Position Change form.
- The system creates a new enrollment/register for the employee’s new plan.
- If the rule is not set to archive the prior PTO Register and no PTO Class conflicts exist with the employee’s existing register, the system creates a new enrollment/register for the employee’s new plan.
- If the rule is not set to archive the prior PTO Register and a PTO Class conflict exists, the system does not update the PTO Register and does not make any changes.
- If the change date matches or is prior to the system date and there are required approvals.
- If the change date is future-dated and there are required approvals.
- If the change date is future-dated and there are no required approvals.
WSP-2437 Client Enhancement to PTO Auto Enroll Rules Form The system now re-evaluates PTO auto-enroll rules and executes enrollments in the PTO Auto Enroll Rules form for current or past-dated Status/Type and Position changes that require approvals, which is helpful to users managing PTO enrollments. When an approval is approved for an applicable change, if the change date matches the system date or a prior date the following occurs: - If an employee meets the criteria for a rule and the rule is set to archive in the prior PTO Register, the system archives existing PTO Registers that share the same class as the PTO Register assigned to the affected rule. Note: In this scenario a message displays, “A type change has taken place that will archive this employee’s PTO plan.” - If an employee meets the criteria for a rule and the rule is not set to archive the prior PTO Register and no PTO Class conflicts exist with the employee’s existing register, the system creates a new enrollment/register for the employee’s new plan. - If an employee meets the criteria for a rule and the rule is not set to archive the prior PTO Register and a PTO Class conflict exists, the system does not update the PTO Register. - If an employee does not meet the criteria for any rule, the system does not update the PTO Register. > Note: Note the following: - If applicable, a new PTO Register enrollment occurs. - If archiving PTO Registers is configured, the system archives the PTO Register as part of the PTO re-enrollment process. - When a user approves an approval for a future-dated change, the system does not re-evaluate the PTO auto-enroll rule. For more information, see Specifying Time Off Auto-enroll Rules.
WSP-2489 Client Enhancement to PTO Auto-Enrollment Rules Import Form In association with the new fields that display on the PTO Auto-Enrollment Rules Maintenance form (see Enhancement to PTO Auto-Enrollment Rules Maintenance Form), two new columns, Trigger Rule On and Archive Existing Register, now display in the import spreadsheet on the PTO Auto-Enrollment Rules Import form. These new columns indicate the following: - Trigger Rule On: Determines which event triggers the re-assessment of a rule. For example, when Trigger Rule On is set to Status/Type Change in the PTO Auto-Enrollment Rules Maintenance form, the rule triggers during an employee status/type change process and, if criteria are met, the system enrolls that employee in the indicated plan. - Archive Existing Register: Indicates whether to archive existing PTO registers when the rule is invoked based on the re-assessment of the rule. > Note: Note the following: - The system validates that the Trigger Rule On value is not used more than one time per rule. - The system reports the import status of the new fields in the Transaction Report along with any error messages. For more information, see Importing Time Off Auto-enrollment Rules.
- Trigger Rule On: Determines which event triggers the re-assessment of a rule. For example, when Trigger Rule On is set to Status/Type Change in the PTO Auto-Enrollment Rules Maintenance form, the rule triggers during an employee status/type change process and, if criteria are met, the system enrolls that employee in the indicated plan.
- Archive Existing Register: Indicates whether to archive existing PTO registers when the rule is invoked based on the re-assessment of the rule.
- The system validates that the Trigger Rule On value is not used more than one time per rule.
- The system reports the import status of the new fields in the Transaction Report along with any error messages.
WSP-2829 Client Enhancement to PTO Benefit Plans Form The system now expires carryover expiration hours set in the PTO Benefit Plans form using year-end date functionality. Therefore, time off hours used after the expiration date do not count towards the carryover balance. (Previously, carryover expiration hours only expired when the system processed the payroll with the pay period start date included.) For more information, see Defining Time Off Plans.
PD-18333, PD-20426, and WSP-2917 Human Resources Enhancements to Employee Details Form The following enhancements are now available on the Employee Details form: - A new field, Contact if arrested/detained?, now displays in the Emergency Contact panel. For example: [Image: screenshot] Note: This enhancement was created in association with the new requirement for California employers, that as of March 2026, employers must allow employees to indicate whether an emergency contact should be notified if they are arrested or detained on their worksite. To ensure an employee’s emergency contact is contacted in case of an employee’s arrest/detainment on the worksite, select Yes in the Contact if arrested/detained? field. (The default is –Select–.) - The system now displays –Select– as the default option in the Non-Res Cert Filed field on the Tax tab when you create an employee. (Previously, the Non-Res Cert Filed field defaulted to No, resulting in users having to reset the option to –Select– to perform new employee imports.) For example: [Image: screenshot] With the default set to –Select– in the Non-Res Cert Filed field, you can now add the State Tax Non-Res Cert Filed field during a New Employee Import. - The display for all the Form I-9 ID Authority fields in the Employee Verification panel has been enhanced, so it’s easier to view manual entries. Specifically, these fields were enlarged and moved to the left side and the description was repositioned. For example: [Image: screenshot] For more information, see Maintaining an Employee’s Personal Information and Establishing Employee Tax Information.
PD-20280 Human Resources Enhancement to Employee Details and Employee Voucher Forms Information for the following fields on the Employee Details and Employee Voucher forms no longer displays after an employee is deidentified using the Inactive Data Deletion form: Deposit tab on Employee Details form: - Suppress Account Number Print - Pay Types to Deposit - DD Exclude Amt Banking tab on Employee Voucher form: - Bank Account - Check Number - Check Amount - ACH Check Account - Void Reason - Transit Number - Account Number - Status - Amount For more information, see Depositing All or Part of Employee’s Net Payment and Reviewing Banking Tab Details.
PD-20438 Human Resources Enhancement to Emergency Contact Report A new column, Contact If Arrested/Detained, now displays in the output after running the Emergency Contact Report. For example: [Image: screenshot] The Contact If Arrested/Detained column indicates whether the employee’s emergency contact will be contacted in case of the employee’s arrest/detainment on the worksite. (This option is set in the Contact if arrested/detained? field on the Personal tab in the Employee Details form.) For more information, see Emergency Contact Report.
WSP-3062 Human Resources Enhancement to Approvals Pending Form The system no longer cuts off long comments and now ignores carriage returns and wraps text that displays in the Comments field when you open a pending approval on the Approvals Pending form. For more information, see Working with Pending Approvals.
WSP-2839, WSP-2840, WSP-2841, WSP-2842, WSP-3162, and WSP-3163 New Employee Import Enhancement to New Employee Import Dashboard Six new options, Shift, Pay Group, Citizenship Status, I9 Identification Document, I9 Eligibility Document, and 2nd Form I-9 ID Document, are now available in the Table field on the Employee Import Code Translation Tables form, which you can access by selecting Code Translation Tables on the New Employee Import dashboard. For example: [Image: screenshot] These options do the following: - Shift: Set up a translation table for shift codes, so you can use this translation table to change the import file code to an accepted PrismHR code. - Pay Group: Set up a translation table for pay group codes, so you can use this translation table to change the import file code to an accepted PrismHR code. - Citizenship Status: Set up a translation table for citizenship status codes, so you can use this translation table to change the import file code to an accepted PrismHR code. - I9 Identification Document: Set up a translation table for I9 identification document status codes, so you can use this translation table to change the import file code to an accepted PrismHR code. - I9 Eligibility Document: Set up a translation table for I9 eligibility document status codes, so you can use this translation table to change the import file code to an accepted PrismHR code. - 2nd Form I-9 ID Document: Set up a translation table for 2nd form I-9 ID document status codes, so you can use this translation table to change the import file code to an accepted PrismHR code. For more information, see Managing Code Translations and Import Field Mappings.
PD-18969 Payroll Enhancement to Pay Period PTO Report Form The warning message that displays when you access the Pay Period PTO Report form now displays as follows: For example: [Image: screenshot] Note: This warning message helps remind users that they must run the most recent payroll to ensure the system posts accurate data in this report. For more information, see Pay Period Time Off Report.
PD-19014 Payroll Enhancement to Billing Voucher Detail Form The Project Phase now displays on the Client Accounting panel on the Billing Voucher DetailVoucher tab when Project Phase tracking is in use and Overtime hours are reported separately using the Premium Pay Code and the Double Time Premium Pay Code, which is set up in the FLSA Ruleset used by the client. Note: You can access the Voucher tab by selecting a Voucher on the Payroll Billing Summary form. After selecting the Voucher, the Billing Voucher Detail form displays. Expand the Client Accounting panel to view the information. For more information, see Voucher Tab and FLSA Ruleset.
PD-19024 and PD-19027 Payroll Enhancement to Time Sheet Audit Report Form The Time Sheet Audit Report form, which you can access by selecting Audit on the Actions menu in the Time Sheet Entry form, now displays the following updates: - Initial manual entries in a timesheet: When users enter hours for an employee (with no current timesheet hours), the Time Sheet Audit Report now reflects that change. - Auto-accept leaves: An auto-accept leave displays as made by the “Background Process” user instead of the first user who opened the timesheet when the auto-accept leave was created. - By column update: The user ID now displays in the By column instead of the user’s last name, first initial. - Tiime Sheet Imports: The user ID and time when a Time Sheet Import is processed now displays in the By and When columns. For example: [Image: screenshot] For more information, see Restoring Recently Changed Information.
PD-19596 Payroll Enhancement to Client Allocation Formats Form The Header Column that displays when you select Add Column and update header lines in the Client Allocation Formats form now reflects the correct value. (Previously, the system sometimes overwrote the prior column header when users added a new column to a client allocation format.) For more information, see Setting Client Allocation Formats.
PD-19681 Payroll Enhancement to Add Employees to Payroll Form A new link, Quick Load, now displays on the Add Employees to Payroll form. For example: [Image: screenshot] Note: You can access the Add Employees to Payroll form by selecting Add Employees to Payroll on the Actions menu in the Payroll Control form. Selecting Quick Load opens the new Regular Payroll Control Quick Load form, where you can add multiple employees to a pay group at once. (See New Regular Payroll Control Quick Load Form.) For more information, see Adding Employees to a Payroll.
PD-19999 and PD-20000 Payroll Enhancements to Pay Codes Form The following enhancements now reside on the Pay Codes form: - The Include in Variable Salary Pay field now displays in the Processing Options panel, regardless of whether the VARSALMETHOD custom feature code is enabled at the Global or Client level. For example: [Image: screenshot] You can enable the Include in Variable Salary Pay field to include the pay code in the employee’s Variable Salary pay. Note: The Unpaid Variable Salary Time field only displays when the Include in Variable Salary Pay field is enabled. - A new tool tip icon ( [Image: screenshot] ) now displays next to the Include in Variable Salary Pay field. Clicking the tool tip icon displays a message, “The VARSALMETHOD custom feature code must be enabled to use this option.” For more information, see Working with Pay Codes.
PD-20145 and PD-20407 Payroll Enhancement to Payments Pending Form New filters are now available on the Payments Pending form to help you narrow the search for payments you need to process. For example: [Image: screenshot] > Note: Note the following: - Select Find Payments to display the payments matching the selected criteria. - If you enter an invalid value for the Client ID, Multi Entity Group, or Cost Center, an error message displays. For example, “<XXX> is not a valid Client ID.” - > Note: Note the following when using the Multi-Entity Group filter: - These groups do not display for a client if the service provider does not have access to that client. - The name of the multi-entity group created in the Multi-Entity Groups form displays. - Note: If there is more than one multi-entity group, they display as listed in the Client Details form, which are truncated if necessary. For more information, see Listing Pending Payments.
PD-20248, PD-20250, and PD-20266 Payroll Enhancements to Batch Payments Form The following enhancements are now available on the Batch Payments form: - A new field, Recalculate Overtime, is now available, which is useful when you need overtime recalculated when the payroll is calculated. (Previously, you could only set this feature in the Payroll Options form.) For example: [Image: screenshot] > Note: Note the following: - Enabling this field automatically enables the Recalculate Overtime field on the Payroll Options form. - You can access the Payroll Options form by selecting Options on the Actions menu in the Payroll Control form after selecting a Payroll Number. - If the system cannot update the Recalculate Overtime field on the Payroll Options form an error message displays, “Recalculate Overtime cannot be updated for Payroll <number>.” - The Recalculate Overtime field does not display for payrolls set to the Regularly Scheduled payroll type on the Payroll Control form. - After saving the Batch Payments form: - If you do not enable Recalculate Overtime, the Recalculate Overtime field on the Payroll Options form is also not enabled in the Payroll Control record for the Batch Payments Payroll Number. - If you enable Recalculate Overtime, the Recalculate Overtime field on the Payroll Options form is also enabled in the Payroll Control record for the Batch Payments Payroll Number. - After enabling Recalculate Overtime a message displays, “The Recalculate Overtime checkbox on the Payroll Options form for Payroll Number <number> has been updated.” - Two new custom feature codes, BATCH-PAYMENTS-CHANGE-DEFAULTS (system level) and BATCH-PAYMENTS-CHANGE-DEFAULTS-C (client level), are now available to allocate batch payments. Note: If you do not set these custom feature codes at the system and client levels, the Edit Employee Details column does not display in the Batch Payments form. For more information, see Entering Multiple Fixed, Pre-calculated Payments.
PD-20331 Payroll Enhancement to SuperBatch Form The text “Wire transfer created” now displays when you cursor over the [Image: screenshot] icon in the SuperBatch form. For example: [Image: screenshot] For more information, see Using SuperBatch and Understanding the SuperBatch Status Icons.
PD-20338 Payroll Enhancement to Detail Time Sheet Entry Form The system now recognizes when the parameters for a Position are set to Service Provider for the User Access and the Hidden option is set to Yes on the Time Sheet tab in the Client Details form, so worksite managers and worksite trusted advisors are now unable to view or update an employee’s Position Code in the Detail Time Sheet Entry form. For more information, see Making Detail Time Sheet Entries.
PD-20368, WSP-3011, and WSP-3040 Payroll Enhancements to Payroll Options Form The following enhancements are now available on the Payroll Options form: - The status that you set for the Recalculate Overtime field on the now automatically displays on the Recalculate Overtime field on the Batch Payments form. For example, if you enable the Recalculate Overtime field on the Payroll Options form for a payroll and then enter or select that Payroll Number in the Batch Payments form, the Recalculate Overtime field displays as enabled after the data loads. Note: You can access the Payroll Options form by entering or selecting a Payroll Number in the Payroll Control form and then select Options from the Actions menu. - A new field, Force PTO Accruals, now displays, which you can enable to override standard PTO accrual functionality for payrolls that are not yet initialized and are set to the Manual or Special/Unscheduled payroll type on the Payroll Control form. For example: [Image: screenshot] - The system now displays the Special Message, which is set by enabling Deliver Message Override, with the correct line return formatting so the text that displays on the Delivery Sheet no longer appears jumbled within the message. For more information, see Setting Special Processing Options.
PD-20430 and PD-20431 Payroll Enhancements to Data Import Tool The following enhancements now reside in the Data Import Tool: - A new field, State Misc4 Rate, is now available on the State Tax Rates (SUTA) import template. For example: [Image: screenshot] Note: The system populates imported State Misc4 Rate information to the associated field that sets employer tax rates for tax codes 24-54 (Minnesota) on the State Tax Rates (SUTA) form. - A new field, State Misc4 Rate, is now available on the State Tax Bill Rates (SUTA) import template. For example: [Image: screenshot] Note: The system populates imported State Misc4 Rate information to the associated field that sets employer tax rates for tax codes 24-54 (Minnesota) on the State Tax Bill Rates (SUTA) form. For more information, see Importing State Tax Bill Rates (SUTA).
WSP-2905 and WSP-3020 Payroll Enhancements to Payroll Check Register Form The following enhancements are now available on the Payroll Check Register form: - A new status code, S - Stale Dated Check, now displays. For example: [Image: screenshot] The Stale Check Reconciliation process now recognizes this new S - Stale Dated Check status code when you update checks as “stale” using the Stale Date and Stale By value. - A new field, Stale Dated?, now displays. For example: [Image: screenshot] The information that displays in the Stale Dated? field clearly identifies which payroll checks the system recognizes as “stale” (regardless of status code), so you can easily address outstanding check issues. For more information, see Viewing Payroll Check Register.
WSP-3051 and WSP-3052 Payroll Enhancement to Client Check Register Report Form Two new options, Escheated and Stale-dated, now display in the Check Status field on the Client Check Register Report form. For example: [Image: screenshot] These options do the following: - Escheated: The system recognizes unclaimed money in a deposit account or other property that is turned over to the state. - Stale-dated: The Stale Check Reconciliation process recognizes the S - Stale Dated Check status code when you update checks as “stale” using the Stale Date and Stale By value. (The system generates results only for checks with the indicated status code for the given time period.) Note: This enhancement does not alter previously stale-dated records in the client’s databases. (Payroll check registers stale-dated prior to this enhancement will still use status code R, but will display Stale dated = Y.) In association with these new options, a new field, Include Stale-dated Checks, now displays when you select the Reconciled option in the Check Status field. For example: [Image: screenshot] You can enable Include Stale-dated Checks to include stale-dated checks when you run a reconciled check report. For more information, see Client Check Register Report.
PD-19409 PTO Enhancement to Add Time Off Type Form The Delete button no longer displays on the Add Time Off Type form, which is part of the Time Off Setup Workflow process. For example: [Image: screenshot] Note: The Delete button isn’t necessary because you cannot delete an existingTime Off Type Code. (If you need to update an existing type, click the pencil icon ( [Image: screenshot] ).) For more information, see Setting Time Off Plan Type.
PD-20212 PTO Enhancement to Confirmation Form When there are no First Year prorated amounts, the message that displays in the Accrual field in the Plans panel on the Confirmation form, which is step 3 in the Time Off Workflow Setup process, was updated to provide more clarity, “The plan has <number of rows in multi-value grid> seniority tiers and does not have prorated amounts for the first year.” For example: [Image: screenshot] For more information, see Confirming Time Off Plan Settings.
PD-20214 PTO Enhancement to Time Off Setup Workflow Form A link to proceed to the time off plan’s current step now displays in the Status column on the Time Off Setup Workflow form. For example: [Image: screenshot] Clicking a link in the Status column proceeds to the step in the Time Off Setup Workflow process based on the plan’s setup progress: - If the user is on step 1, proceeds to the Time Off Type form. - If the user is on step 2, proceeds to the Accrual Schedule panel on the Set Up Plans form. - If the user is on step 3, proceeds to the Confirmation form. For more information, see Setting Up Time Off Plans.
WSP-3069 PTO Enhancement to PTO Accrual Recalculation Form A new note now displays on the PTO Accrual Recalculation form. For example: [Image: screenshot] This note warns that using the accrual recalculation tool might adversely impact employees who have forced PTO accrual on manual or special batches, so you can make an informed decision on whether to use this tool. Important! At this time, the note is a preparatory warning because the system functionality to force PTO accruals on manual or special payrolls will be included in a future release. For more information, see Recalculating Time Off Accruals.
PD-18101 System Enhancement to PTO Absence Codes and Time Off Setup Workflow Forms Previously, an issue occurred when an employee was enrolled in two registers and an absence code was not set up correctly, but the employee had leave on a timesheet for a different PTO Register with an absence code that was setup correctly. To resolve this issue, enhancements were made in the following scenarios, so users cannot save entries on the PTO Absence Codes form or proceed to step 3, Confirmation, in the Time Off Setup Workflow process, as confirmed by the error message that displays: - When the Leave Pay Code entered on the PTO Absence Codes form or Portal Configuration in the Time Off Setup Workflow process is the same as a Leave Offset Pay Code for a different absence code (different forms) an error message now displays, “Leave Pay Code PAYCODE is already used for a Leave Offset Pay Code. Use a different Leave Pay Code or update the Leave Offset Pay Code for PTO Absence Code ABSENCE CODE.” - When the Leave Offset Pay Code entered on the PTO Absence Codes form or Portal Configuration in the Time Off Setup Workflow process is the same as the Leave Pay Code for a different absence code (different forms) an error message now displays, “Leave Offset Pay Code PAYCODE is already used for a Leave Pay Code. Use a different Leave Pay Code or update the Leave Offset Pay Code for PTO Absence Code ABSENCE CODE.” - When the Leave Pay Code entered in the PTO Absence Codes form or Portal Configuration in the Time Off Setup Workflow process is the same as the Leave Offset Pay Code for the same absence code (same form) an error message now displays, “Leave Pay Code PAYCODE is already used for the Leave Offset Pay Code.” For more information, see Creating Time Off Absence Codes and Confirming Time Off Plan Settings.
PD-18439 System Enhancement to Role Maintenance Form The system now recognizes case structure when creating a new user role in the Role Maintenance form, which compares new role entries against existing roles. For example, you cannot create or copy the user role glsp if the user role GLSP already exists. If you try to create or copy a new user role using a different case structure of an existing role, an error message now displays. For example: [Image: screenshot] Note: You can access the Role Maintenance form by selecting New Role on the Actions menu in the User Roles form. For more information, see Creating a New Role.
PD-18854, PD-19685, and PD-20266 System Enhancements to System Parameters Form The following enhancements are now available on the System Parameters form: - A new field, Disallow On Demand Check Processing for Prior Year, now displays. For example: [Image: screenshot] Enabling the Disallow On Demand Check Processing for Prior Year field prevents users from processing an on-demand check from the previous year. When you enable this field and enter an on-demand check from the previous year in the Check Date field on the On Demand Check Processing form: - An error message displays, “You are unable to submit on-demand checks for the prior year.” - The Print Check and Calculate Totals buttons are disabled. However, when you enter a check date in the current year, these buttons are enabled. (Note that Print Check is disabled until the system finishes Calculate Totals.) - A new system-level custom feature code, BATCH-PAYMENTS-CHANGE-DEFAULTS, is now available on the Select Feature Code list to allocate batch payments. For example: [Image: screenshot] Note: You must set the BATCH-PAYMENTS-CHANGE-DEFAULTS (system level) and BATCH-PAYMENTS-CHANGE-DEFAULTS-C (client level) custom feature codes to view the Edit Employee Details column on the Batch Payments form. - The Feature Description for the ALLOWWMNEWHIREALTEMP custom feature code now displays as “Allow New Hire Alternate Employers for WS managers” in the Custom Feature Codes panel. (Previously, this description incorrectly displayed “Employees” instead of “Employers.”) For example: [Image: screenshot] For more information, see Setting General System Parameters and Using Custom Feature Codes.
PD-20022, PD-20023, and PD-20024 System Enhancement to Email Services Form A new email template type, Leave Approval, is now available on the Email Services form. For example: [Image: screenshot] You can use the Leave Approval template type to create an automatic email message that an employee’s leave is ready for approval. > Note: Note the following: - When an employee requests leave using Employee Portal (EP), the message is sent to the appropriate approver(s). - If the Leave Approval template type is not configured on the Email Services form but the HR Actions Approval template type is configured, the system uses the HR Actions Approval template type as the default message. - If neither of the Leave Approval or HR Actions Approval template types are configured on the Email Services form, the system uses the following default message instead: For example: [Image: screenshot] > Note: Note the following about the default message: - A new substitution variable, <<LEAVE.DATESANDHOURS>>, displays the leave date(s) and hours in the Leave Approval email notification in the MM/DD/YYY (N Hours) format. If there is more than one date, all dates and hours display. For example: HTML Content Type 10/07/2025 (8 Hours) 10/09/2025 (8 Hours) 10/10/2025 (8 Hours) TEXT Content Type 10/07/2025 (8 Hours) 10/09/2025 (8 Hours) 10/10/2025 (8 Hours) - When multiple leave dates are requested at the same time, all dates and hours display in the email. For more information, see Setting Up Automated Email Messages.
PD-20245 System Enhancement to User Roles Report Form A new field, Include Custom Process IDs, now displays on the User Roles Report form. For example: [Image: screenshot] Enabling Include Custom Process IDs includes all custom process IDs assigned to the User Roles on the report. For more information, see Determining User Role Details Display.
PP-2050 System Enhancement to Search Results Style The search results for the main Prism search bar have been updated to be consistent to other search styles throughout the software. For more information, see the in-app help.
WSP-2899 System Enhancement to Print Service Global Check Parameters Form A new field, Auto-Stale Date Checks After (Days), now displays on the Print Service Global Check Parameters form. For example: [Image: screenshot] Note: This feature is only available for service providers. You can use the Auto-Stale Date Checks After (Days) field to configure, at the system level, the number of days before the system automatically updates a Payroll Check to the status of Stale-Dated. For more information, see Setting Up Default Global Check Printing Parameters.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-2921 Previously, on the Retirement Plan Enrollment form, under the Election Details section, when you deleted an Effective Date, the system deleted the prior records data available for employee contributions. Now, this is fixed.
WSP-2932 On the Benefit Plan Setup form, when you set a benefit plan for an employee with the One Month Prepay and the Auto Enrollment fields checked, then the system created Benefit Adjustments records, which was an incorrect behavior. Now, this is fixed.
WSP-2937 Previously, while using the Next Gen FSA/HSA Enrollment Posting Import Definition Template on the Benefits Import form, the importing of an election update caused the system to overwrite the Plan Year To Date Deductions and Funded Balance from one account to the other account on the Employee Flexible Spending Accounts form. Now, this is fixed.
WSP-2938 Previously, on Retirement Match Rules form, there was some confusion with the logic for calculation of Matching Contribution displayed on the employee’s payroll voucher. Now, this is fixed. A help text icon now displays explaining the Match Layers logic next to the Layered Match Rules section on the Retirement Match Rules form when the Match Logic Type is selected as Layered.
WSP-2997 Previously, the Retirement Plan Enrollment form had tab order issues. This is fixed. The tab order now flows through each section in the correct sequence. Additionally, the tab order does not go to the hyperlink form buttons of Import Retirement Plan Adjustments and View Employee Retirement Plan Register.
WSP-2998 Previously, on the Retirement Plan Enrollment form, the Effective Date under the Election Details section was not displayed when the browser was resized down. Now, this is fixed.
WSP-3028 Previously, there were issues while importing benefit rules to a benefit group for specific plans that were added to the benefit groups. Now, this is fixed.
WSP-3066 Previously, on the Group Benefit Plans form, when you expanded all the sections for a benefit plan and then tried creating a new plan, the sections remained expanded, which was an incorrect behavior. Now, this is fixed.
WSP-3067 Previously, when an employee had an existing pre-tax retirement plan election and the Employee Deferral Deduction Code was flagged to Prohibit Deductions then while running a payroll, the payroll warning was not triggered. Now, this is fixed.
WSP-3107 Previously, on the Benefit Adjustments form, the Benefit Plan ID changed while adjusting an existing benefit adjustment. Now, this is fixed.
WSP-3142 Previously, when you entered a future dated Benefit Salary where current day was prior to the Benefit Salary change and the pay date was after the future dated Benefit Salary, then the payroll process did not automatically create a new coverage detail Effective Date. Additionally, for Benefits Enrollment, if the Open Enrollment effective date was equal to or after the future dated Benefit Salary, then the system displayed incorrect rates. However, if the current day was equal to or after the future dated Benefit Salary, the payroll process updated the existing coverage detail effective date with the correct coverage and premium amounts. Now, this is fixed.
WSP-3257 Previously, on the Group Benefit Plans form, when you selected a Benefit Plan, then under the Age Parameters section, in the Age Calculation (Month/Day) field, when you selected non-Month/Day option, the system displayed an error message, which was an incorrect behavior. Now, this is fixed. The validation message is displayed only if you select a valid month (January-December) and do not select a Day against the selected month.

Compliance (CMP) Fixes

Ticket Issue Summary Resolution
CMP-3696 Previously, when an employee who was not a resident of the District Of Columbia submitted the D-4A Certificate of Nonresidence, it did not update the information on the Tax tab on the Employee Details form. Now, an employee who is not a resident of the District Of Columbia when submits a D-4A Certificate of Nonresidence in the District of Columbia, this information will populate in PrismHR both during onboarding as well as in Employee Portal.
CMP-4770 Previously, when Form W-2s were generated before tax adjustments were applied, then the Form W-2 had to be manually deleted because the Create W2 process did not update to zero. Now, previously created Form W-2s will update to zero when all taxable earnings and tax amounts are reduced to zero.
CMP-6203 Previously, PrismHR was not correctly recalculating billing taxes on vouchers for the Miscellaneous Taxes when the tax rate is less than, equal to, or greater than 1.00. Now, this is resolved.
CMP-6577 Previously, when an override rate was entered at the Employer or Client Level for PFML, it did not populate in the PTS file on the 210 records, positions 71-76 for CT, DC, MA and MN. Now, this is resolved.
CMP-6836 Previously, the system did not treat Group-Term Life Insurance wages as taxable for Detroit like any other Michigan local taxes. Now, Group-Term Life Insurance wages will be taxable for Detroit like any other Michigan local taxes under the following Michigan local tax codes: - 213630380-31 (Detroit City Income Tax) - 213630380-39 (Detroit Resident City Income Tax)
Jira # Issue Summary Resolution

Employee Portal (EP) Fixes

Jira # Issue Summary Resolution
EERT-3044 When two or more employees were added to a payroll in Prism and a manager manually added their time using the Time Sheet Entry form in Portal, an error occurred when a service provider attempted to calculate the payroll and the Charge Date field would display as blank. This is fixed.
EERT-3080 When an employee viewed their benefits contributions in Employee Portal, the Limited FSA and Dependent Care FSA contributions did not always display correctly. This is fixed.
EERT-3123 When a manager accessed the View My Employees form in Employee Portal, sometimes employee names displayed as undefined, even though they displayed correctly on the home screen and employee records. This is fixed.
EP-3227 If an employee attempts to add a 100% account on the Direct Deposit form in Employee Portal and already had a Remainder account, the system produced an error message indicating that the accounts sum to greater than 100% and did not save the change. This message has been fixed to indicate that the employee cannot have a Remainder account record and another account with 100% at the same time.
EP-9545 When an employee changed their retirement contributions status to Inactive, the Retirement Summary form in Employee Portal still displayed their original retirement contribution amounts. This is fixed.
EP-9877 When a user viewed the Template History form for a Configuration Template, changes made on the new dashboard layout did not display on the audit log properly. This is fixed.
EP-9903 When a user attempted to access their documents, and no override or template had been assigned to their client, some document folders did not display correctly. This is fixed.

Identity and Access Management (IAM) Fixes

Jira # Issue Summary Resolution
IAM-2153 When a user had multiple profiles, including a Service Provider profile with an IP restriction, the user could not log in using their non-Service Provider profiles, even if the other profiles did not include an IP restriction. This is fixed.
IAM-2474 When an employee registered through Employee Portal, they would sometimes receive an empty error message. This is fixed.
IAM-2496 When an employee went through the Forgot Password process, typed in the verification code, and clicked the Verify Code button, next page in the process did not load, and the Forgot Password process could not be completed. This is fixed.

Onboarding (OB) Fixes

Jira # Issue Summary Resolution
EERT-2966 When the system generated I-9 reminder notification emails, the emails were sent in a single batch all at once instead of over a period of time. This is fixed.
EERT-2967 When a user clicked Get Employees on the Download Enrollment Statements form and no batch ID was selected, an error occurred. This is fixed.
EERT-3071 When an employee set their Preferred Language to Spanish, the Per Pay Period Amount on the Benefits Enrollment Confirmation Statement displayed the Per Month value instead of the Per Pay Period value. This is fixed.
EERT-3089 When employees reviewed onboarding documents, documents which did not belong to the client would erroneously display. This is fixed. When workflow is created, trace should display either formId and rulesetId, with passes result, or error message, or formId no rule and ‘Passes’.
EERT-3096 When an employee finished their I-9 record and the manager approved it, the status still displayed as Onboarding In Progress on certain forms. This is fixed.
EERT-3127 If an error occurred on the I-9 Section 1 form and the employee refreshed the page, the employee was erroneously given the option to continue. If they clicked Continue, the I-9 Section 2 form did not display properly. This is fixed.
EERT-3169 When a user made changes to a new hire record on the Client Details form, an invalid record would sometimes be created. This is fixed.
OBE-8456 When an employee elects the same FSA amount as was previously elected during a Life Event and also elects to enroll in a new Flexible Spending Account type, an error occurred. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
PD-19217 General The Tax Calculation Override link did not display on the Tax tab in the Employee Details form when there were Suppressed Taxes, but there were no Income Tax Overrides. The Tax Calculation Override link now displays when the employee has at least one record in the Suppress Taxes form or when the Income Tax Override has at least one active override.
PD-19238 General The system did not display the correct description of the Contact Type for the assigned contact in the Type field in the Contact Information panel on the Account tab in the Client Details form. This is fixed.
PD-19417 General When users enrolled an employee in a PTO Benefit Plan in the PTO Benefit Plans form with a calculation basis of Hours Worked (by Hours) or Hours Worked (by Months), a message displayed even when there was a value for Max per Year, “Warning: no additional hours will be accrued because the initial amount is equal to the maximum accrual of 0.00 hours set up in the PTO benefit plan.” The following now happens in these scenarios: - When enrolling an employee in a PTO Benefit Plan with a calculation basis of Hours Worked (by Months): – If the difference between the Benefit Start Date and Calculated Thru date is less than the initial “After Months” worked for Seniority Level 1 a warning message now displays, “Warning: no initial hours will be accrued because the time between the benefit start date and calculated thru date is less than the After Months required to begin accruing.” – If the difference between the Benefit Start Date and Calculated Thru date is not less than the initial After Months worked for Seniority Level 1, a warning message now displays, “Warning: no additional hours will be accrued because the initial amount is equal to the maximum accrual of N hours set up in the XXX benefit plan.” - When enrolling an employee in a PTO Benefit Plan with a calculation basis of Hours Worked (by Hours): – If the difference between the hours the employee has already worked from the Employee Payroll Register hours is less than the initial After Hours worked for Seniority Level 1, a warning message now displays, “Warning: no initial hours will be accrued because the employee has worked less hours than the After Hours required to begin accruing.”
PP-2072 General When a user performed a search in the Prism menu, the search did not return results that appeared in parentheses. For example, searching for “unbundled” would not return the Billing Rules (Unbundled) form. This is fixed.
PP-2101 General When a user accessed the demo version of the PrismHR UI, the background color of the home screen obscured the version number. This is fixed.
PP-2102 General When a user accessed the Actions menu on the Code Descriptions Overrides form, two options labeled “Audit” displayed. In addition, clicking either of these options without any audits selected on the form produced an error message. This is fixed.
PP-2117 General When a user had access to only one account, the Account Selection logo still displayed on the PrismHR menu. This is fixed. The logo is now transparent when the user has access to only one account.
PP-2125 General When a user had 0 messages or approvals, the Messages icon and the Approvals icon would show a red “0” notification on the PrismHR menu. This is fixed. When the user has zero messages or approvals, the corresponding icons do not display a red notification.
RRT-6666 General When users selected the Tiered Per Employee Per Pay Period option as the Unbundled Billing rule basis in the Billing Rules (Unbundled) form, the system did not count employees with a status classification of Active in the employee count to determine the Tier Level rate per employee. This is fixed.
WSP-1653 General When users navigated between clients while on the PTO Auto Enroll Rules form and then clicked New Rule, the system displayed the last-used existing rule instead of creating a new rule. In this scenario, clicking New Rule now opens the PTO Auto-Enrollment Rules Maintenance form, which displays blank fields.
WSP-2906 General When users removed checks with the MVG “x” in a row while using the Stale Check Reconciliation form to load checks into the MVG, the system incorrectly updated the Checks Total calculation. The system now accurately reduces the Checks Total to reflect the total amount of the Check Amount column for all rows in the MVG when users remove rows from the Stale Check Reconciliation MVG.
WSP-2929 General The system sorted payroll numbers on the Batch Number (left-justified) by default on the Select Payroll Number list in the Benefits Billing Detail Report form. (The Select Payroll Number list displays when you select Payroll Number after choosing Select Batch ID in the Defined Ranges field.) The system now sorts payroll numbers by Pay Date, descending from most recent, by default in the Select Payroll Number list.
WSP-3128 General Users sometimes experienced long delays waiting for the system to generate results when they ran the ACH Journal Edits Audit Report and the ACH Journal Hold/Release Report. The ACH Journal Edits Audit Report and the ACH Journal Hold/Release Report now use an updated process, so they run more efficiently.
PD-19066 Payroll The system included empty columns in the XLS output produced by the Labor Distribution Report. This is fixed.
PD-19610 Payroll The system did not include the right angle bracket (>) in the STDMEMO column in the Global Accounting Custom Layout on the PEO Client Accounting and System Parameters forms. (When the file was created, the system populated this type with < instead of resolving to the standard name.) The following now happens: - STDMEMO data option populates as <> in the Custom Layout on the PEO Client Accounting and System Parameters forms. - < resolves to the correct entry when an External Journal posts and the system generates and regenerates PEO Client Accounting.
PD-20422 Payroll The system did not display the void reason on the adjustment voucher when a voucher with a direct deposit was reclassified using the Reclassify Direct Deposit form. This is fixed.
PD-20504 Payroll The system displayed an error message when users tried to import 2025 year records using the Tip OT Register import template in the Data Import Tool. Users can now import information in the Qualified Tips and Overtime form and create a 2025 year record using the Tip OT Register import template in the Data Import Tool.
WSP-2865 Payroll When users configured an ACH Maximum Global Approval Policy that exceeded the ACH Maximum Amount, the system did not enforce the approval policy during the initialization step. The system now enforces the approval policy during the initialization step and stops the payroll until the approval is processed.
WSP-3157 Payroll When users selected the Plan Comparison Data import template in the Data Import Tool and then selected an Offer Type, during import the system did not import the plan information on the Benefits Enrollment Plan Details form. This is fixed.

========================================================================

January (R_202601)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/01/whatsnew-R_202601.htm Path: Release-Notes/2026/01/whatsnew-R_202601.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

New Features

We would like to bring your attention to the following list of new features for PrismHR.

List of New Features

Click a link to display the detailed release notes for the new feature

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Release Highlights

Highlight — Description

RRT-6666 — When users selected the Tiered Per Employee Per Pay Period option as the Unbundled Billing rule basis in the Billing Rules (Unbundled) form, the system did not count employees with a status classification of Active in the employee count to determine the Tier Level rate per employee. (This is fixed.)

Documentation Enhancements

Click a link to read about the documentation enhancements included in this release.

Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202602

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/02/Release-Notes-R_202602.htm Path: Release-Notes/2026/02/Release-Notes-R_202602.htm

Release Notes R_202602

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202602 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday February 26, 2026
Wave 2 Friday February 27, 2026
On-Premise Thursdays March 5, 2026

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-3172, WSP-3380 Enhancements to the HSA Contribution The HSA Match YTD reporting has been corrected for HSA plans with non calendar (mid year) plan years. The Paystub for an employee will now always display the employer HSA Match Year to Date based on the calendar year totals regardless of the HSA plan year configuration. Additionally, on the Employee Flexible Spending Accounts form, under the Override Calculations section, when you enter $0.00 for Match Override, then for the 1st payroll of the calendar year, the paystub will not display HSA Match contribution record under Employe Contributions section.
WSP-3208, WSP-3209 Changes to the Benefits Billing Detail Report form On the Benefits Billing Detail Report form, under the Report Filters section, a new multi-value filter selector named Offer Type has been added, which will allow you to run reports to filter results based on Offer Typem. The filter selector has the following columns: - Offer Type - You can manually type in the Offer Type into the row(s) or select multiple Offer Types from the Select Offer Type selector. - Offer Type Description - On selecting a valid Offer Type, the system auto-populates this field. [Image: screenshot] For more information, see Benefits Billing Detail Report help topic.
WSP-3210, WSP-3226 Changes to the Benefits Billing Detail Report form On the Benefits Billing Detail Report form, when you run reports using the Primary Sort and Secondary Sort options with Report Type set as Detail to get the following detailed report: - Benefits Billing Detail By Plan By Employee Report - Benefits Billing Detail By Employee By Plan Report - Benefits Billing Detail By Department By Employee Report - Benefits Billing Detail By Department By Plan Report - Benefits Billing Detail By Location By Employee Report - Benefits Billing Detail By Location By Plan Report then on the reports that the system displays, Offer Type indicator now displays next to the Plan ID. [Image: screenshot] Similarly, when you run reports using the Primary Sort and Secondary Sort options with Report Type as Summary to get the following summary report: - Benefits Billing Summary By Plan By Employee Report - Benefits Billing Summary By Employee By Plan Report - Benefits Billing Summary By Department By Employee Report - Benefits Billing Summary By Department By Plan Report - Benefits Billing Summary By Location By Employee Report - Benefits Billing Summary By Location By Plan Report then on the summary reports that the system displays, Offer Type indicator now displays next to the Plan ID. [Image: screenshot] For more information, see Benefits Billing Detail Report help topic.
WSP-3261 Validation added to the Employee Retirement Loans form On the Employee Retirement Loans form, when you select a Retirement Plan that has Prohibit Deductions flagged for Employee Loan Deduction Code on the Retirement Plans form, then while saving a record, the system displays an error message stating, Retirement Loan Deductions prohibited by this plan. Record cannot be updated.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
CMP-3152 FSA Support Non-Standard calendar year plan For plan years beginning in 2025, a cafeteria plan may not allow salary reduction contributions for a health Flexible Spending Account in excess of $3,300. PrismHR now supports non-standard calendar years plans for a health Flexible Spending Account. Taxable billing with shelters will follow the FSA mid-plan year and match the employer’s tax-accrual sheltered amounts. For more information, see the in-product help or PrismHR Benefits Administration User Guide.
CMP-4099 & CMP-7025 Changes to the State Rules form PrismHR payroll system now supports state-specific annual exempt salary minimums to accurately record and maintain state-specific annual exempt salary minimums in compliance with regulatory requirements. On the State Rules form, in the Minimum Wage Rates grid, an additional column named Minimum Exempt Salary Amount has been added. This field is not mandatory. Enter the annualized rate only for Minimum Exempt Salary Amount. You can only enter numeric values up to 2 decimal places. Note: On the New Hire form, for an FLSA exempt new hire, if the annual salary (entered or calculated) in the Pay Rate field under the Pay Details section, is lower than the Minimum Exempt Salary Amount on the State Rules form for that state for the latest entered year, and you try to save the form, then you will receive a warning stating The employee has been assigned a pay rate that is below the [State Abbreviation] Minimum Exempt Salary Rate of [Amount]. This is a warning only. Continue? - Click Yes to save the change. - Click No to return to the Pay Rate field. Note: Additional logic to support pay rate changes & payroll calculation warnings to follow in upcoming release. For more information, see the in-product help or PrismHR System Administration User Guide.
- Click Yes to save the change.
- Click No to return to the Pay Rate field.
CMP-7048 State Specific Fields added to the PrismHR Tax Quarterly JSON The PrismHR Tax Quarterly JSON file has been updated to include additional State Specific Fields. These fields will appear in the Employee Wage Details section of the Quarterly JSON for SUTA tax codes as required. For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-6326 & CMP-6854 Changes to the Update Employee W-2 Forms form As a service provider, you can now review the associated client wage data when Form W-2s are built on the PEO Employer level. This will not be applied to W2 records built on the Client Federal Entity Register (SBEA build). A new Client Inquiry section has been added to this form. This section will only populate for tax year 2025 and onwards. When the Form W-2 data is built on the Employer and the associated client information is added to the build, the Client ID, Company Name, and Federal Taxable Wages will appear as read only on this new form. This information cannot be edited by the user. If an employee is associated with multiple clients, each client appears as a separate row with an accurate federal taxable wage allocation. Only users with permission to view/update employee Form W-2s can access the Client Inquiry section. This data will only display on 2025 + W-2s built after the January release. The data will optionally be available to print on the Employee W-2 as a later enhancement in 2026. For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-7089 MasterTax RTS is updated to V49 On the MasterTax Interface Parameters form, the Mastertax RTS Import File Version has been updated to V49 in PrismHR. If the MasterTax RTS Import File Version field is set to Version 48 or earlier, you will receive the following error message when you are running the RTS: You are running an older version of the mastertax RTS file download []. You must be on version 49 in order to generate the RTS file out of Prism. Your current version can be edited on the Mastertax Interface Parameters. The header on the MasterTax RTS file now also reflects 49 in Line 1 in the 000 record in positions 57-58, with or without the Schedule R Breakout field selected. Note: Support for MN SUI exempt reporting in RTS V49 to follow in a future release. For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-6925 GTL Pay Code exemption added to MN Admin Assessment For Minnesota Admin Assessment, beginning in 2026, Group Term Life (GTL) earnings are now treated as exempt for the employer tax calculation. What changed? - The payroll tax calculation has been updated so that: - The MN Admin Assessment tax is exempt on GTL earnings. - The exemption is applied to the system-assigned GTL pay code configured in System Parameters. - The exemption applies to both billing and accrual calculations. - This change is implemented as an earnings-based exemption, not via a pay code level tax exemption entry. Why this matters? Previously, MN Admin Assessment could not be correctly exempted for GTL because the pay code itself could not be exempted for this tax. This update ensures that GTL is excluded from the MN Admin Assessment tax base, aligning with Minnesota requirements and preventing over‑taxation on GTL amounts. Setup / Usage notes - Ensure your GTL pay code is correctly assigned on the System Parameters form. - Once configured, GTL amounts will automatically be treated as exempt for the MN Admin Assessment tax during payroll processing; no separate Tax Exemptions pay code setup is required. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
- The payroll tax calculation has been updated so that:
- The MN Admin Assessment tax is exempt on GTL earnings.
- The exemption is applied to the system-assigned GTL pay code configured in System Parameters.
- The exemption applies to both billing and accrual calculations.
- This change is implemented as an earnings-based exemption, not via a pay code level tax exemption entry.
- Ensure your GTL pay code is correctly assigned on the System Parameters form.
- Once configured, GTL amounts will automatically be treated as exempt for the MN Admin Assessment tax during payroll processing; no separate Tax Exemptions pay code setup is required.
CMP-6998, CMP-6999, CMP-7000, CMP-7001 & CMP-7110 CA Pay Data - Tax Year 2025 reporting updates The updated export including the newly added data points and MENA classification will be released shortly after the standard 2026 February release. For tax year 2025 and later, the California Pay Data Reporting specifications have changed. To align with the updated state requirements, we have updated the EEO-1 Build, Import and CSV templates. The California Pay Data CSV export ( EEO Processing / EEO-1 Processing / Client EEO-1 & Pay Data Files (CA Payroll Employee Report) ) updates remain in development for Tax Year 2025. Note: These changes affect only tax year 2025 and forward; tax year 2024 and prior remain unchanged. Here is the California Pay Data Reporting link. - CSV template modified for CA Pay Data employees & Labor Contractor reporting - New data points added to CA Pay Data Build - To support 2025 California Pay Data Reporting requirements, we’ve enhanced the standard EEO-1 build and Export to include additional data points for California employees. These changes make it easier to classify employees correctly and to calculate weeks worked for the reporting year. ### What’s New ##### 1. Exemption Status For California employees, based on the FLSA status on the employee’s home position as of the voucher “as of” date, the EEO‑1 build now includes an Exemption Status field that indicates whether the employee is: - Exempt (Y) - Non‑exempt (N) The exemption status is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 2. Employment Type Based on the employee’s type from the voucher “as of” date, the EEO‑1 build now classifies each California employee into one of three Employment Types: - F=Full‑time (derived from internal employee type codes and type classification) - P=Part‑time (derived from internal employee type codes and type classification) - S=Intermittent (assigned when the employee’s type is flagged as Seasonal = Y) This employment type is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 3. Weeks Worked in Reporting Year The EEO‑1 build now calculates the total number of weeks worked for each California employee during the reporting year, summing all vouchers within the selected date range (the reporting tax year). This will be indicated as a whole number greater than zero without decimal places. The calculated Weeks Worked is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 4. MENA Ethnicity For employees belonging to the MENA (Middle Eastern or North African) ethnic type: - For the Import EEO-1 Data form, the import file can now contain M for the Race/Ethnicity field. - When you generate the EEO‑1 Export file using the Client EEO-1 & Pay Data Files form, these employees will be further subdivided into the following categories under the Race/Ethnicity/Sex column: - B70 = Non-Hispanic/Non-Latino - Male - Middle Eastern or North African - C70 = Non-Hispanic/Non-Latino - Female - Middle Eastern or North African - D70 = Non-Hispanic/Non-Latino - Non-Binary - Middle Eastern or North African For more information, see the in-product help or PrismHR System Administration User Guide.
- CSV template modified for CA Pay Data employees & Labor Contractor reporting
- New data points added to CA Pay Data Build - To support 2025 California Pay Data Reporting requirements, we’ve enhanced the standard EEO-1 build and Export to include additional data points for California employees. These changes make it easier to classify employees correctly and to calculate weeks worked for the reporting year.
- Exempt (Y)
- Non‑exempt (N)
- F=Full‑time (derived from internal employee type codes and type classification)
- P=Part‑time (derived from internal employee type codes and type classification)
- S=Intermittent (assigned when the employee’s type is flagged as Seasonal = Y)
- For the Import EEO-1 Data form, the import file can now contain M for the Race/Ethnicity field.
- When you generate the EEO‑1 Export file using the Client EEO-1 & Pay Data Files form, these employees will be further subdivided into the following categories under the Race/Ethnicity/Sex column:
- B70 = Non-Hispanic/Non-Latino - Male - Middle Eastern or North African
- C70 = Non-Hispanic/Non-Latino - Female - Middle Eastern or North African
- D70 = Non-Hispanic/Non-Latino - Non-Binary - Middle Eastern or North African
CMP-7121 Weighted Average using Flat Sum OT calculation Enhancement to weighted average overtime rate calculations when employee pay includes flat sum bonus pay items (for example, CA meal premiums and CA sick pay). What Changed When the weighted average pay code parameters are: - Method = Work Week and - No Lookback Period is defined, the system now: 1. Calculates the regular rate excluding pay codes with a flat sum condition. 2. Calculates the regular rate for flat sum pay codes (using the same approach already used for flat sum OT: flat sum pay divided by regular hours only). 3. Adds the results of steps 1 and 2 to determine the final weighted average pay rate. This logic applies to both Legacy and Restartable payrolls. Why This Matters Previously, when flat sum pay items (such as CAHOUSING and CARENT) were included, the weighted average overtime base rate could be understated because the flat sum component was not properly blended into the weighted average rate. Now: - Flat sum bonuses are divided only by regular hours to get their regular rate. - That flat sum regular rate is added to the regular rate from all other applicable pay codes. - The resulting combined rate is used as the overtime base rate for weighted average pay codes. - This provides a more accurate and compliant overtime rate when flat sum bonus pay is present. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
- Method = Work Week and
- No Lookback Period is defined,
1. Calculates the regular rate excluding pay codes with a flat sum condition.
2. Calculates the regular rate for flat sum pay codes (using the same approach already used for flat sum OT: flat sum pay divided by regular hours only).
3. Adds the results of steps 1 and 2 to determine the final weighted average pay rate.
- Flat sum bonuses are divided only by regular hours to get their regular rate.
- That flat sum regular rate is added to the regular rate from all other applicable pay codes.
- The resulting combined rate is used as the overtime base rate for weighted average pay codes.
- This provides a more accurate and compliant overtime rate when flat sum bonus pay is present.

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-1095 Print Multiple Pay Stubs Employees can now print multiple pay vouchers at one time on the Pay History form in Employee Portal. Up to thirty payroll vouchers can now be printed at a time by selecting vouchers individually or using the Select All checkbox. Employees can download the vouchers as a single pdf. Employees can use this feature to quickly print multiple vouchers when they need several months of payroll stubs, such as for financial applications or loans. For more information, see the in-app help.
EP-9679, EP-9683, EP-9684 ZayZoon Support for the My Pay Widget Companies that use ZayZoon integrations can now include those features in Employee Portal more easily. Clients can add the standard ZayZoon widget or menu item on a Configuration Template or Client Override, and can also add the Get Paid Early feature from ZayZoon to the My Pay widget using its configuration options. For more information, see the in-app help.
EP-1837, EP-1838, EP-1872, EP-9154, EP-9923 View Employee Pay Details Managers can now view detailed information about an employee’s pay data on the Pay tab on the Employee Details form in Employee Portal. This tab contains multiple forms detailing aspects of your employee’s paystubs, payroll history, and total compensation. Information that displays on the Pay tab is secured based on the manager’s role and permissions. The Pay History tab displays information for individual paystubs. Managers can search for specific paystubs or filter by year. A column selector is also available to display additional information. Select View Paystub to display the Pay History: Paystub form, which displays information about the net pay, earnings, taxes withheld, and deductions. Select View Check on this form to display a pdf of the paycheck, which can then be downloaded or printed. The Payroll Inquiry tab displays general information for a selected year. Select the Earnings, Taxes Withheld, or Deductions tabs to display the information of that tab for the selected year. In addition, select the Pay History tab on the inquiry to display information regarding changes in the employee’s pay rates. The Total Compensation tab displays information about the employee’s salary, benefits, and taxes. The Overview tab displays a breakdown of the employee’s net pay and tax withholdings, plus a graph of their compensation breakdown. The Pay tab displays their pay information and breaks down their payment into hours and entitlements. The Benefits tab shows the amount of their paycheck allocated to benefits, and the Taxes tab displays the employee and company contributions to taxes. Using this new form, managers with the appropriate permissions can review detailed information regarding employee pay directly from Employee Portal. This data can be used to review paychecks, monitor past changes in pay rates, and verify compensation, benefits, and tax breakdowns for employee paychecks. For more information, see the in-app help.

Identity and Access Management (IAM) Enhancements

Ticket Description Summary Help Content
IAM-2044 Enhancement to My Login Settings Form When a user with multiple accounts exits the My Login Settings form, the user is now directed back to PrismHR. Previously, users were directed to a form that requested they reselect which account to log in with. For more information, see the in-app help.
IAM-2546 Enhancement to PrismONE ID Settings When a client is configured to access PrismONE ID via an external identity provider with its own Multifactor Authentication and passwords, MFA and password information are now hidden on the PrismONE ID Settings form. In addition, a banner message informs users that their accounts are using a third-party authentication source to sign in. For more information, see the in-app help.

Onboarding (OB) Enhancements

Ticket Description Summary Help Content
OBE-7361 HSA Employer Match on Benefit Confirmation Statement The Benefit Confirmation Statement now displays the HSA Employer Match amount and annual contribution limits. A disclaimer also displays to inform the employee that this is a projected match which may change based on circumstances such as pay periods, eligibility, and plan details. For more information, see the in-app help.
OBE-9656, OBE-9825 Override Offer Type Rules by Payee ID A new configuration option is now available on the Life Event Maintenance form to allow Service Providers to override the offer type rules for a life event by Payee ID. This option becomes available when Use Benefit Rule is selected in the Source of Effective Date field. When the option is selected, eligibility is overridden from benefit rules or group benefit plans at the Offer Type level for selected Payees. Select which date is used in the Eligibility Date Used From Override field. > Note: Note: When this option is selected, initial eligibility still takes priority. Using this option, Service Providers can ensure that certain payees override the normal benefit rules or group benefit plans for their offer types. For more information, see the in-app help.
OBE-9780 Enhancement to Primary Care Physician Form Employees can now mark the Current Patient field on the Primary Care Physician form to indicate that they are currently seeing this physician. This information is synchronized with the corresponding field on the Employee Benefits Enrollment form in Prism. For more information, see the in-app help.
OBE-9835 Set Decision Support Access for Specific Clients Service Providers can now disable decision support tools for specific clients. On the Client Controls tab of the Client Details form, select an option in the Decision Support field in the Enrollment/Onboarding Controls section to enable or disable decision support tools. With this enhancement, Service Providers can provide decision support capabilities to their clients more selectively. For more information, see the in-app help.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
PD-20066 and PD-20067 ACH Enhancement to ACH Originators Form A new option, ISO, is now available in the Bank Name field on the ACH Originators form. Important! You must test this new file format with your banking institutions before processing a live file. Not all banks may accept this format, so you must complete testing before payroll runs using the ISO format. For example: [Image: screenshot] When you select the ISO XML file format, the system creates a payroll payment in ISO file format for clients set up for reverse wire transfers. For more information, see Using ACH Originators.
PD-20505 Client Enhancement to Inactive Data Deletion Form The system now recognizes an employee’s last termination status month, day, and year and the current month, day, and year, so employees now display in the Inactive Data Deletion list when their last termination status date is more than the selected number of Years Terminated from the current date. For more information, see Removing Inactive Customer Data.
WSP-3220 Client Enhancement to Client Details and Payments Pending Forms A new option, Real Time Payment, now displays in the Transfer Type field on the Client Details and Payments Pending forms. For example [Image: screenshot] [Image: screenshot] Use the Real Time Payment option as follows: - You can set the Real Time Payment option on the Billing tab in the Client Details form to categorize and track a client’s billing setup for Real Time Payments (RTP). - You can set the Real Time Payment option on the Payments Pending form to filter pending payment results for Real Time Payments (RTP). For more information, see Specifying Client Billing Options and Listing Pending Payments.
WSP-3164 New Employee Import Enhancement to New Employee Import Dashboard A new option, 3rd Form I-9 ID Document, is now available in the Table field on the Employee Import Code Translation Tables form, which you can access by selecting Code Translation Tables on the New Employee Import dashboard. For example: [Image: screenshot] You can use the 3rd Form I-9 ID Document option to set up a translation table for 3rd form I-9 ID document codes, so you can use this translation table to change the import file code to an accepted PrismHR code. For more information, see Managing Code Translations and Import Field Mappings.
PD-19202, PD-20419, and PD-20519 Payroll Enhancements to Data Import Tool The following enhancements now reside on the Data Import Tool form: - A new import template, Position Classification, is now available. For example: [Image: screenshot] Note: The Position Classification import template is only available for service providers. You can use the Position Classification import template to import state and workers compensation classes for existing position classifications. > Note: Note the following: - Users whose user role is set to DENY for the Position Classifications form cannot import data using the Position Classification import template and subsequently, the Data Import Tool icon will not display on this form. - Users whose user role is set to INQUIRY for the Position Classifications form can view the Position Classification import template, but cannot import data. - Users whose user role is set to INQUIRY for the Data Import Tool can view the form and import template options, but cannot import data. - The State must be a valid state code. Otherwise, an error message displays. - If your template lists the same state twice, the system uses the first instance but ignores the second instance. - Worksite managers and worksite trusted advisors can now access the Tip OT Register import template in the Data Import Tool when they have FULL access to the Qualified Tips and Overtime form. (Previously, the system wasn’t allowing these users to access the Tip OT Register import template even when they had FULL access.) Note: To access the Qualified Tips and Overtime form for an employee, select the employee in the Employee Details form. From the Actions menu, select the Qualified Tips and Overtime option. - A new field, Payee, is now available on the Employee Loans import template. For example: [Image: screenshot] The Payee field indicates the payee associated with the employee loan. > Note: Note the following: - The payee must be an existing payee and have a Payee Type set to Loans on the Payees form. - You can only use payees whose Third Party Format for the Processor ID associated with the Payroll Check Account is set to Cachet or –Select– on the ACH Originators form. - An error message displays if the Deduction Code does not have the Deduction Type set to Employee Loan Payment on the Deduction Codes form or if the Deduction Code is obsolete. For more information, see Importing Position Classifications, Importing Tips and Overtime Data, and Importing Employee Loan Data.
PD-20037 and PD-20038 Payroll Enhancement to Deduction Codes Form A new option, % of Earnings with Included Pay Codes, now displays in the Calculation Method field on the Deduction Codes form. For example: [Image: screenshot] You can use the % of Earnings with Included Pay Codes option to associate a non-qualified deferred compensation (NQDC) plan that the client set up with another company, where a percentage of the commissions is deferred, reducing taxable earnings. (This deduction code functions similar to a pre-tax deduction.) > Note: Note the following: - You must set the Deduction Type to either Voluntary or Pre-Tax Retirement Contribution to use the % of Earnings with Included Pay Codes option. (If you select another option an error message displays.) - Setting a deduction code with a calculation method of % of Earnings with Included Pay Codes and enabling the Voluntary deduction type deducts the amount applied to the pay code and treats the deduction as pre-tax when you enable 409(a) Retirement in the Voluntary Classification panel. - Setting a deduction code with a calculation method of % of Earnings with Included Pay Codes and enabling the Voluntary deduction type deducts the amount applied to the pay code and treats the deduction as post-tax when you do not enable when you enable 409(a) Retirement in the Voluntary Classification panel. - The onlyVoluntary Classification you can enable with the % of Earnings with Included Pay Codes option is 409(a) Retirement. (If you select another option, an error message displays.) When you select the % of Earnings with Included Pay Codes option, a new Pay Codes panel displays. For example: [Image: screenshot] > Note: Note: You must enter or select at least one pay code or an error message will display when you click Save. For more information, see Maintaining Global Deduction Codes.
PD-20414 and PD-20415 Payroll Enhancement to Payees Form A new option, Loans, is now available in the Payee Type field on the Payees form. For example [Image: screenshot] You can use the Loans option to designate payees specifically for employee loans. In association with the Loans option, a new panel, Loan EFT Parameters, now displays in the Payees form when you select Loans as the Payee Type. For example: [Image: screenshot] You can enter EFT details specific to loan payees in the Loan EFT Parameters panel: - Transit Number: The financial institution where the state disbursement unit maintains the account. - Bank Account Number: The account number of the receiving financial institution. Note: You can enter numeric characters 0-9, the dash (-) character, and alphabetic characters in this field, which can be combined. For example, CSP-98765 is an allowed Bank Account Number. For more information, see Setting Up Vendors to Receive Payments.
PD-20417, PD-20507, and PD-20508 Payroll Enhancements to Employee Loans Form - A new field, Payee, is now available on the Employee Loans form. For example [Image: screenshot] You can use the Payee field to enter or select the payee for an employee loan. Note: Only payees who have the Loans payee type on the Payees form display in the Select Payee list. Also, you can only enter or select a Payee whose Third Party Format for the Processor ID associated with the Payroll Check Account is set to Cachet or –Select– on the ACH Originators form. - A new column, ACH Reference, now displays in the Payments panel. For example: [Image: screenshot] The system displays the following information: - ACH information in the ACH Reference column, such as garnishments. - The employee loan deduction amount in the ACH file, which includes the routing and account number, client ID, and employee ID. For more information, see Setting Up and Tracking Employee Loans.
PD-20491 and WSP-3243 Payroll Enhancements to Bank Accounts Form The following enhancements now reside on the Bank Accounts form: - A new field, Account Type, now resides on the Bank Account form. For example [Image: screenshot] You can use the Account Type field to categorize new and existing bank accounts by the type of ownership, PEO Master, Client Owned, or Demo. - If a bank Account ID has already been used to process a transaction, you cannot delete it when one or more of the following conditions exist: - The system created an ACH file with the bank Account ID. - The system processed cash receipts using the bank Account ID. For more information, see Maintaining Bank Accounts.
WSP-3280 Payroll Enhancement to Void and Reissue Checks Form The system now prevents you from voiding and reissuing escheated checks on the Void and Reissue Checks form. If you try to void and reissue an escheated check, an error message displays. > Note: Note the following: - You cannot enter or select a check with a status code of E (escheated). - You cannot enter a voucher number for a voucher that contains a check with a status code of E (escheated). For more information, see Voiding Payroll Batch or Voucher.
PD-20454 System Enhancement to Pay Schedules Form A new option, On this Day of the Following Month, is now available in the second Pay Period Ends field on the Pay Schedules form. For example: [Image: screenshot] Important! The following options in these fields must be set to display the On this Day of the Following Month option: - Pay Period field: Select Monthly. - Pay Day field: Select End Of Month. - Pay Period Ends field: Enter EOM. Note: If you try to select On this Day of the Following Month without setting the fields listed above, the following error message displays: [Image: screenshot] When you apply a pay schedule to a pay group for monthly payrolls with the On this Day of the Following Month option enabled, the system calculates the period end date as the last day of the following month. For example, if the pay date is 7/31/2025 and the pay period start date is 8/1/2025, then the period end date would equal 8/31/2025. For more information, see Establishing Pay Schedules.
PD-20489 System Enhancement to User Roles Form Worksite managers are now restricted from accessing the forms mentioned below, so service providers can no longer add these process IDs to a worksite manager’s user role in the User Roles form: - GLOBAL.PARAMS1095C.ELECT: 1095C Election Configuration form - GLOBAL.PARAMSCASH.TYPES.MAINT: Cash Types form - GLOBAL.PARAMSCOBRA.CREDIT.MAINT: Cobra Credit Parameters form - GLOBAL.PARAMSCONFIG: Global Configuration form - GLOBAL.PARAMSCONTACT.TYPES.MAINT: Contact Types form - GLOBAL.PARAMSCORP.MAINT: Global Parameters Corporate Edition form - GLOBAL.PARAMSCOVID.CLIENT.MAINT: COVID-19 Emergency Processing Parameters Client Overrides form - GLOBAL.PARAMSCOVID19.MAINT: COVID-19 Emergency Processing Parameters form - GLOBAL.PARAMSDOC.CONFIG.MAINT: Document Services form - GLOBAL.PARAMSEMAIL.MAINT: Email Services form - GLOBAL.PARAMSGLOBAL.ENROLL.MAINT: Enrollment Options form - GLOBAL.PARAMSGLOBAL.NH.FIELDS.MAINT: New Hire and Dependent Required Fields (Global) form - GLOBAL.PARAMSHRPS.V1.GL.ENTRY: HRPS Version 1 GL Account Entry form - GLOBAL.PARAMSLOGO.PATH.MNT: Logo Path Maintenance form - GLOBAL.PARAMSMAINT.HOLIDAYS: Payroll Holidays form - GLOBAL.PARAMSMISC.MAINT: Miscellaneous Global Parameters form - GLOBAL.PARAMSMVQUERY.IMAGE.MAINT: Global mvQuery Image Path Maintenance form - GLOBAL.PARAMSNUMBER.MAINT: Global Parameters Next Number Maintenance form - GLOBAL.PARAMSPREHIRE.CONFIG.MAINT: PrismHR Onboarding Services form - GLOBAL.PARAMSSSO.SERVICES.MAINT: SSO Services form - GLOBAL.PARAMSSTD.VISION.MASTER.MAINT: Global Payroll Reports form - GLOBAL.PARAMSSUFFIX.LIST: Employee Suffix form - GLOBAL.PARAMSSYSTEM.CONTROL.MNT: System Parameters form - GLOBAL.PARAMSTAX.RATE.MNT: Tax Rate Maintenance form - GLOBAL.PARAMSTERM.MAINT: Global Parameters Termination Parameters form - GLOBAL.PARAMSUSER.AUTHENTICATION: Authentication Services form - GLOBAL.PARAMSW2.ELECT: W-2 Election Configuration form - GLOBAL.PARAMSWSU.PENDING.APPROVAL.EMAILS: Pending Approval Emails form - HRP.USERSIP.RESTRICTIONS: IP Restrictions form - HRP.USERSIP.RESTRICTIONS.MANAGER.USER.SETUP: IP Restrictions form - HRP.USERSMAINT: Users form - HRP.USERSMAINT.PRISMONE: PrismONE Users form - HRP.USERSSECURITY.MAINT: Data Security form - HRPY.WORKROLE.MAINT: Role Maintenance form - HRPY.WORKSECURITY.MAINT: User Roles form - WEB.SERVICE.USERSMAINT: Web Service User form Note: This enhancement does not apply to these process IDs already added to worksite manager user roles. For more information, see Defining User Roles.
- GLOBAL.PARAMS*1095C.ELECT: 1095C Election Configuration form
- GLOBAL.PARAMS*CASH.TYPES.MAINT: Cash Types form
- GLOBAL.PARAMS*COBRA.CREDIT.MAINT: Cobra Credit Parameters form
- GLOBAL.PARAMS*CONFIG: Global Configuration form
- GLOBAL.PARAMS*CONTACT.TYPES.MAINT: Contact Types form
- GLOBAL.PARAMS*CORP.MAINT: Global Parameters Corporate Edition form
- GLOBAL.PARAMS*COVID.CLIENT.MAINT: COVID-19 Emergency Processing Parameters Client Overrides form
- GLOBAL.PARAMS*COVID19.MAINT: COVID-19 Emergency Processing Parameters form
- GLOBAL.PARAMS*DOC.CONFIG.MAINT: Document Services form
- GLOBAL.PARAMS*EMAIL.MAINT: Email Services form
- GLOBAL.PARAMS*GLOBAL.ENROLL.MAINT: Enrollment Options form
- GLOBAL.PARAMS*GLOBAL.NH.FIELDS.MAINT: New Hire and Dependent Required Fields (Global) form
- GLOBAL.PARAMS*HRPS.V1.GL.ENTRY: HRPS Version 1 GL Account Entry form
- GLOBAL.PARAMS*LOGO.PATH.MNT: Logo Path Maintenance form
- GLOBAL.PARAMS*MAINT.HOLIDAYS: Payroll Holidays form
- GLOBAL.PARAMS*MISC.MAINT: Miscellaneous Global Parameters form
- GLOBAL.PARAMS*MVQUERY.IMAGE.MAINT: Global mvQuery Image Path Maintenance form
- GLOBAL.PARAMS*NUMBER.MAINT: Global Parameters Next Number Maintenance form
- GLOBAL.PARAMS*PREHIRE.CONFIG.MAINT: PrismHR Onboarding Services form
- GLOBAL.PARAMS*SSO.SERVICES.MAINT: SSO Services form
- GLOBAL.PARAMS*STD.VISION.MASTER.MAINT: Global Payroll Reports form
- GLOBAL.PARAMS*SUFFIX.LIST: Employee Suffix form
- GLOBAL.PARAMS*SYSTEM.CONTROL.MNT: System Parameters form
- GLOBAL.PARAMS*TAX.RATE.MNT: Tax Rate Maintenance form
- GLOBAL.PARAMS*TERM.MAINT: Global Parameters Termination Parameters form
- GLOBAL.PARAMS*USER.AUTHENTICATION: Authentication Services form
- GLOBAL.PARAMS*W2.ELECT: W-2 Election Configuration form
- GLOBAL.PARAMS*WSU.PENDING.APPROVAL.EMAILS: Pending Approval Emails form
- HRP.USERS*IP.RESTRICTIONS: IP Restrictions form
- HRP.USERS*IP.RESTRICTIONS.MANAGER.USER.SETUP: IP Restrictions form
- HRP.USERS*MAINT: Users form
- HRP.USERS*MAINT.PRISMONE: PrismONE Users form
- HRP.USERS*SECURITY.MAINT: Data Security form
- HRPY.WORK*ROLE.MAINT: Role Maintenance form
- HRPY.WORK*SECURITY.MAINT: User Roles form
- WEB.SERVICE.USERS*MAINT: Web Service User form
PP-1948 System Enhancement to Payroll Reversal Form Users can now sort results on the Payroll Reversal form by name. In addition, users can click Select All and Deselect All to quickly select or deselect all results. For more information, see the in-app help.
PP-2134 System Change to URL Endpoint Dependency The .asp section of the URL is no longer necessary for clients running an SSO configuration. For example, “htpps://your.website.com/site/dweb.asp?a=SSOIN&dbcgm=1” no longer requires the .asp section to be compatible with the SSO configuration, and could be shortened to “https://your.website.com/sit/a=SSOIN”. For more information, see the in-app help.
PP-2143 System Enhancement to Help Documentation The URL for help documentation on the PrismHR platform has been changed. Clients who link to the help directly will need to update their bookmarks. For more information, see the in-app help.
PP-2157 System Enhancement to Pendo Name and ID For clients who integrate Pendo into their system, the peoName and peoID fields have been updated to provide the user’s PEO name and PEO ID to Pendo when they access Prism. For more information, see the in-app help.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-2889 Previously, for a client set up with Departments Restrict Eligibility option selected for Eligible Benefits Determinant field on the Benefits tab of the Client Details form, the Benefits Eligibility Report displayed blank results even if Departments were set up with eligible benefits. Now, this is fixed.
WSP-2934, WSP-3330 Previously, on the Employee Benefits Enrollment form, COBRA Fee under the Coverage Details section were displayed only when you set the Status to COBRA and then saved the form. Now, this is fixed. COBRA Premiums and COBRA Fee are now populated immediately after you set the participant’s Status to COBRA. Additionally, the system recalculates the Total Premium contribution to 100% Participant Contribution of Premium (with COBRA fee, if applicable) and the Employer Contribution is displayed as net $0.00.
WSP-2935 Previously, during a payroll calculation process, if a Coverage Detail Effective Date is automatically created, then the system did not create audit log on the Benefit Detail Audit screen for that Effective Date. Now, this is fixed.
WSP-2969 Previously, on the Employee Benefits Enrollment form, under the Coverage Details section, when you selected a new Existing Effective Date, then the Updated Carrier field was automatically checked, which was an incorrect behavior. Now, this is fixed.
WSP-2970 Previously, on the Employee Benefit Rule Overrides form, Worksite Managers were able to manually enter an Employee ID and create an Employee Benefit Rule Override even for employees whose access were restricted for the Worksite Managers. Now, this is fixed.
WSP-3194 Previously, on the Employee Benefits Enrollment form, saving an employee benefits enrollment record required you to click the Save button twice. Now, this is fixed.
WSP-3225 Previously, on the Group Benefit Plans form, when you set a plan for Do Not Allow EE Contribution and then when you add Plan Type for that plan on the Benefit Rules form, then the informational text under the Contribution Rules section displayed twice. Now, this is fixed.
WSP-3242 Previously, on the Employee Details form, under the Work tab, the Benefit Group selector included Retirement Only benefit group, which was an incorrect behavior. Now, this is fixed. The Benefit Group selector has been updated to use the new selector and benefit groups defined as Benefit or Both are now only displayed.
WSP-3291 Previously, in certain circumstances, the system displayed blank Premium and Contribution amounts on the Employee Benefits Enrollment form. Now, this is fixed.
WSP-3315 Previously, on the Client Assigned To form, when you selected a client from the client list, the system displayed incorrect client name on the Benefit Plan Setup modal form. Now, this is fixed.

Compliance (CMP) Fixes

Jira Number Issue Summary Resolution
CMP-5923 Previously, after a Global PTO Benefit Plan was deleted and the corresponding the Global PTO Register is archived, even if there is no state plan associated, the subsequent payroll incorrectly reflected the PTO accrual if the timesheet location matched the deleted Global PTO Benefit Plan. Now, this is fixed.
CMP-6751 Previously, when an employer had a tax basis set for California State Income Tax (CA SIT), the S-Corp Benefit Tax Adjustments did not report the correct tax basis. Now, when an employer sets State Income Tax reporting to ‘Client,’ the S-Corp Benefit Tax Adjustments will have a tax basis of ‘C’ for the SIT. Conversely, if the employer sets the reporting to ‘Employer,’ the tax basis will be ‘P.’
CMP-6886 Previously, for both SBEA and non-SBEA clients, with and without Mastertax account id, when OR PFML tax code 38-40 was redirected on the Client Details form, RTS 501 record, statistic 1 (positions 67-80) and statistic 2 (positions 81-94) were not zero filled. Now, for both SBEA and non-SBEA clients, with and without Mastertax account id, when OR PFML tax code 38-40 is redirected on the Client Details form, RTS 501 record, statistic 1 (positions 67-80) and statistic 2 (positions 81-94) are be zero filled.
CMP-6904 Previously, the MasterTax RTS file C records did not correctly report the PA Work State flag on the Client file when the locality was Client Report, C tax basis. Now, this is resolved.
CMP-7038 Previously, for California employees with a Health Savings Account (HSA) match, the system incorrectly did not include the HSA employer match to calculate the taxable wages for California Employment Training Tax (tax code 05-26). This resulted in the CA SUTA (tax code 05-24) wages being different from the CA ETT (tax code 05-26) wages. Now, this is resolved. For California employees with a Health Savings Account (HSA) match, the CA SUTA wages are the same as the CA ETT.
CMP-7047 Previously, the WH347 report (both January 2025 and December 2008 versions) did not generate a zero report for certified projects that lacked payroll data for the specified week ending date. Now, the WH347 report (both January 2025 and December 2008 versions) generates a zero report for certified projects that lack payroll data for the specified week ending date.
CMP-7066 Previously, when processing a tax adjustment using the Tax Adjustments form, when the Adjust Client Tax Register field was selected, the employer reported tax code 24-54 (MN - Additional Assessment) was reporting a Tax Basis P instead of C on the employee payroll voucher. Now, when processing a tax adjustment using the Tax Adjustments form, when the Adjust Client Tax Register field was selected, any employer reported tax code will report a Tax Basis of C on the employee payroll voucher.
CMP-7077 Previously, while building the Quarterly Tax JSON Export, the job progress window incorrectly stated Building MasterTax Reconciliation Reports. Now, this is resolved.
CMP-7080 Previously, for the state of Minnesota, when payroll included Additional Assessment tax, the employer contribution billing amount (tax code 24-54) was not reported under the Employer Contribution on the Payroll Check Journal Report. Now, for the state of Minnesota, when payroll includes Additional Assessment tax, the employer contribution billing amount (tax code 24-54) will be reported in the Employer Contribution on the Payroll Check Journal Report.
CMP-7130 Previously, when an employee was assigned to a Worksite Location in Minnesota, and was paid in a timesheet in a worksite location other than Minnesota, the system incorrectly withheld STATE MISC4 EMPLOYER tax for that work state (non-existing tax code XX-54) creating errors. Now, when an employee with an assigned worksite location in the state of Minnesota is paid in a timesheet in a worksite location other than Minnesota, the system correctly withholds tax code 24-54 (MN - Additional Assessment) and no other XX-54 tax codes will be present.
CMP-7156 Previously, when an employee was assigned to a remote location in a state that was different from their resident state, and the employee went over the SUTA wage base limit, the billing portion did not correctly recognize the over-limit wages. Now, when an employee is assigned to a Remote Location in a state that is different than their resident state, the wage basis is accurate from payroll to payroll, with or without a wage base override, and the bill amount is also correct.

Document Management (DM) Fixes

Jira # Issue Summary Resolution
> Note: Note: The items in this release will be deployed with the Wave 3 update for all clients.
DM-1911 After updating their SSO Services URL, when users attempted to access the Manage Documents form, an error occurred. This is fixed.
DM-1924 When a user attempted to print a document from the Document Management Viewer, an error occurred. This is fixed.
DM-1965 When a user attempted to cancel a bulk download from Document Management, an error occurred. This is fixed.

Employee Portal (EP) Fixes

Jira # Issue Summary Resolution
EERT-3103 When an employee was terminated, the employee record still displayed on the manager’s My Employees widget. This is fixed.
EERT-3132 When an employee set up a new direct deposit in Employee Portal, the audit log did not display the previous and new bank names properly. This is fixed.
EERT-3155 When certain managers attempted to access the Hire New Employee form on the New Hire Dashboard in Employee Portal, an error occurred. This is fixed.
EERT-3182 When an employee accessed Employee Portal, their manager’s preferred name did not display in the Manager field or PTO Approver field. This is fixed.
EP-9884 When a user viewed the Payroll Inquiry or Pay History forms in Employee Portal, the Taxable Wages field did not subtract out the Taxable Over Limit amounts, resulting in overstated taxable wages in some cases. This is fixed.
EP-9951 After a payroll voucher was voided, the Taxable Wages field on the Payroll Inquiry and Pay History forms did not update properly. This is fixed.
EP-9978 If the Date of Birth field was set to today’s date on the New Hire form, the user was unable to edit or clear the field and enter a correct value, resulting in a repeating warning message. This is fixed.
EP-100003 When a user attached a segment to a widget on the Enhanced Dashboard of the Configuration Templates form, the segment did not work as expected. This is fixed.

Identity and Access Management (IAM) Fixes

Jira # Issue Summary Resolution
IAM-2615 When a user logged in to PrismHR, the list of linked applications did not display a scroll bar on the My Login Settings form. This is fixed.
IAM-2668 When a user accessed the My Login Settings form, some applications did not display properly in the My Linked Applications section. This is fixed.
IAM-2685 When a user navigated to the Forgot Password screen and entered a username of a disabled account, the screen became unresponsive. This is fixed.

Onboarding (OB) Fixes

Jira # Issue Summary Resolution
EERT-2957 The Create Enrollment Statements form did not properly select batches to generate or download enrollment statements. This is fixed.
EERT-3115 When an employee edited a Dependent record, additional offer type forms displayed during Benefits Enrollment. This is fixed.
EERT-3118 When no coverage amount was elected by the employee for Life Coverage Amount, the employee coverage incorrectly posted based on the salary multiplier. This is fixed.
EERT-3139 When an employee was hired through the Employee Portal New Hire Dashboard and completed their onboarding process, the New Hire Dashboard form still displayed the employee status as In Progress. This is fixed.
EERT-3147 When Benefits Enrollment notifications were disabled, users still received notifications throughout that day. This is fixed.
EERT-3149 When a user downloaded their Benefits Enrollment Statement, the Dependent Care FSA values did not display properly. This is fixed.
EERT-3150 Users could receive Benefits Enrollment notifications even though there were no items in their Client Workflow Grid if there were items in the System Workflow Grid. This is fixed.
EERT-3153 When a user accessed the Edit Document Set form, the Business Rule column fields expanded and could not be minimized. This is fixed.
EERT-3154 After the Web Enrollment Configuration End Date field was updated, notifications were still triggered on the original Web Enrollment Configuration End Date. This is fixed.
EERT-3159 Event Based notifications were not sent properly to users from the System Workflow Grid. This is fixed.
EERT-3187 When an employee submitted their I-9 Section 1 form as part of the Onboarding process, the approval displayed on the Onboarding Tasks by Status form and the Approvals Dashboard. However, when the manager attempted to access the form to approve it, an error occurred. This is fixed.
OBE-9872 When the user submitted a Benefits Enrollment workflow and changed the Current Patient field on the form to be unchecked, the corresponding field on the Employee Benefit Enrollment form was not changed to be unchecked. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
RRT-6718 General The system allowed users to archive PTO registers in the Employee PTO Register form that had outstanding future leave requests. This is fixed.
WSP-3057 General The Field Name on the File Audit form, which is accessed by selecting Audit on the Actions menu in the Payroll Control form, incorrectly displayed as “Testing Field” instead of “Payroll Status.” This is fixed.
WSP-3193 General Users were able to enter duplicate codes in the Imported Code column in the Employee Import Code Translation Tables form. (The system translated the first entry listed in the table for duplicate imported codes, which caused confusion and unexpected results.) When creating or updating an existing code set, the system now validates whether duplicates exist in the Import Code column when users click Save.
PD-19939 Payroll The system did not count all terminated employees within the beginning and ending dates range in the Turnover Dashboard. This is fixed.
PD-20358 Payroll Users were able to access Payroll Approval Reports for posted payrolls in the Payroll Reports form. This is fixed.
PD-20442 Payroll The system incorrectly displayed a warning message in the Payroll Validation Report when an employee was paid below minimum wage because the calculation was based on Hours Paid instead of on Hours Worked. The system now calculates Gross Pay divided by Hours Worked to determine if an employee was paid minimum wage.
PD-20541 Payroll Users were able to enter an obsolete pay code in a timesheet (that is, it had an obsolete date in the past). This is fixed.
RRT-6620 Payroll The system included pay codes that used units and had Include Amount Paid Only in Overtime Calculation field enabled on the Pay Codes form in the hours paid calculation that determines the overtime due when overtime was calculated. The system now does the following: - When no fields are enabled, the system uses the default Hours/Units Paid. - When the Include Hours/Amount Paid in Overtime Calculation field is enabled, the system uses Hours Worked. - When the Use Hours Paid Instead of Hours Worked in Overtime Calculation field is enabled, the system uses Hours/Units Paid. - When the Include Amount Paid Only in Overtime Calculation field is enabled, the system uses Hours Worked.
- When no fields are enabled, the system uses the default Hours/Units Paid.
- When the Include Hours/Amount Paid in Overtime Calculation field is enabled, the system uses Hours Worked.
- When the Use Hours Paid Instead of Hours Worked in Overtime Calculation field is enabled, the system uses Hours/Units Paid.
- When the Include Amount Paid Only in Overtime Calculation field is enabled, the system uses Hours Worked.
PP-2151 System When the Geocode lookup for an address did not match the entered value in the City field, the employee’s entry in the City field was overridden automatically. This is fixed. The employee’s entry in the City field now takes priority when the Geocode doesn’t precisely match.
PP-2154 System Web extensions added on the Web Extensions form were not working properly for certain customers. This is fixed.

========================================================================

February (R_202602)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/02/whatsnew-R_202602.htm Path: Release-Notes/2026/02/whatsnew-R_202602.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

Documentation Enhancements

Click a link to read about the documentation enhancements included in this release.

Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202603

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/03/Release-Notes-R_202603.htm Path: Release-Notes/2026/03/Release-Notes-R_202603.htm

Release Notes R_202603

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202603 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday March 26, 2026
Wave 2 Friday March 27, 2026
On-Premise Thursday April 2, 2026

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-2832 Changes to the Max Days Back Dating Validation The Max Days Back Dating field validations are now triggered for the following scenarios: - When auto populating a Coverage Starts date on a new record. - When manually updating the Coverage Starts date on an existing record on the Employee Benefits Enrollment form. - When changing the Status of a record to Active on the Employee Benefits Enrollment form. For more information, see the in-app help.
WSP-3318 Changes to the Benefits Eligibility Report form The Benefits Eligibility Report now correctly displays eligibility for Group Benefits when using Departments, Divisions, or Worksite Locations as Eligible Benefits Determinants. Additionally, when a determinant value has no associated eligible benefits, the report now shows NA instead of All, which was displayed earlier. [Image: screenshot] For more information, see the in-app help.
WSP-3325 Changes to the Group Benefit Plans form Under the Group Benefit Plans section, a new checkbox field, 3rd Party COBRA, has been added. [Image: screenshot] This field allows plans to be flagged when COBRA administration is handled by third party, supporting downstream API and reporting use while leaving existing COBRA functionality unchanged. For more information, See Establishing Basic Parameters for Group Benefit Plans help topic.
WSP-3339, WSP-3342, WSP-3344, WSP-3345, WSP-3346, WSP-3357, WSP-3361, WSP-3362 Changes to the Client Benefits Overview form - On the Client Benefits Overview form, the system now displays all the Primary Plan IDs in Bold format. Additionally, the system displays the Secondary Plan IDs in normal text format along with all the data for that Plan ID even when you click on a header to sort the data. Note: The system displays the same format of Primary Plans in Bold and the Secondary Plans in normal text after you select the View plans past end date and the View rules that are not found checkboxes. - The column order on this form have now been updated and is displayed in the following order: - Plan ID - Plan Description - HDHP Plan - Rate Group - Group/Rules - Template - Start Date - End Date Note: There is no change in the existing functionality with the Plan ID and Group/Rules hyperlinks. - On this form, the four new columns have now been added: - Section 125 Eligible - Deduction Code - If Section 125 Eligible column is flagged with Y value, then the Deduction Code for that record will be displayed as 125 Deduction Code. However, if Section 125 Eligible column is flagged with N value, then the normal Deduction Code for that record will be displayed. - Rebate Bill Code - The value displayed in the Rebate Bill Code column is based on the value displayed for 125 Deduction Code or Deduction Code. If Rebate Bill Code is not assigned for a record, then the system displays N/A. - Bill Code - On this form, when you sort data and then open a modal form by clicking any of the hyperlink from the Plan ID or Group/Rules column, the system now preserves your existing sort selections after you close the Plan ID or Group/Rules modal. - On this form, two new checkbox fields have been added. - Include retirement only benefit groups - This field allows you to filter Benefit Groups data that are flagged as Retirement only. - View benefit groups past stop all use on date - This field allows you to filter and view the data of Benefit Groups past the Stop All Use On date. - A new button named, Report has also been added towards the bottom of the form. Click this button to run a report on the Client Benefits Overview form and export the data. [Image: screenshot] For more information, See Displaying the Client Benefits Overview help topic.
WSP-3343 Changes to the Benefit Plan Setup form On the Benefit Plan Setup form, when you select Plan Class as Group Benefit and choose a Plan ID, then after clicking the View Deduction/Bill Codes hyperlink, following changes have been made to the earlier Plan Deduction and Billing Codes modal form that was displayed: - Section 125 Eligible field is now displayed as a checkbox. - The Deduction and Billing Codes are now displayed in a grid format. - The column headers now include Code, Description, Deduction Type, and Rebate Bill Code. [Image: screenshot] Note: All the information displayed on this modal form is in read-only format. For more information, See Setting Up a Benefit Plan help topic.
WSP-3359, WSP-3360 Changes to the Benefits Billing Detail Report The system now displays an Offer Type indicator to the right of the Plan ID while running a Benefits Billing Detail Report by clicking the Download Report button from the Billing History section on the following forms: - Employee Benefit Overview - Employee Benefits Enrollment [Image: screenshot] For more information, See Displaying an Employee’s Benefit Plans and See Manually Enrolling an Employee in a Benefit Plan help topic.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
CMP-7026 Validations added for Minimum Exempt Salary Amount To help you ensure exempt employees meet the state minimum exempt salary requirements, from now on during payroll processing (including Superbatch), the system now checks an exempt employees’ pay against the State Rules – Minimum Exempt Salary Amount for their work state. If an exempt employee’s earnings for the pay period are below the configured state minimum exempt salary, a soft warning message is displayed so you can review and adjust pay as needed. > Note: Note: Payroll can still be processed. Figure 4 - State Rules form [Image: screenshot] Figure 5 - Warning - Process Payroll Menu [Image: Warning in Process Payroll Menu] Figure 6 - Warning - Superbatch Menu [Image: screenshot] For more information, see the in-product help or PrismHR System Administration User Guide.
CMP-7001 CA Pay Data - Tax Year 2025 reporting updates For tax year 2025 and later, the California Pay Data Reporting specifications have changed. To align with the updated state requirements, we have updated the EEO-1 Build, Import and CSV templates. The California Pay Data CSV export (EEO Processing / EEO-1 Processing / Client EEO-1 & Pay Data Files (CA Payroll Employee Report)) updates are now complete for Tax Year 2025. The updated export including the newly added data points and MENA classification were released on March 12, 2026 via a hotfix. Note: These changes affect only tax year 2025 and forward; tax year 2024 and prior remain unchanged. Here is the California Pay Data Reporting link. - CSV template modified for CA Pay Data employees & Labor Contractor reporting - New data points added to CA Pay Data Build - To support 2025 California Pay Data Reporting requirements, we’ve enhanced the standard EEO-1 build and Export to include additional data points for California employees. These changes make it easier to classify employees correctly and to calculate weeks worked for the reporting year. ### What’s New ##### 1. Exemption Status For California employees, based on the FLSA status on the employee’s home position as of the voucher “as of” date, the EEO‑1 build now includes an Exemption Status field that indicates whether the employee is: - Exempt (Y) - Non‑exempt (N) The exemption status is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 2. Employment Type Based on the employee’s type from the voucher “as of” date, the EEO‑1 build now classifies each California employee into one of three Employment Types: - F=Full‑time (derived from internal employee type codes and type classification) - P=Part‑time (derived from internal employee type codes and type classification) - S=Intermittent (assigned when the employee’s type is flagged as Seasonal = Y) This employment type is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 3. Weeks Worked in Reporting Year The EEO‑1 build now calculates the total number of weeks worked for each California employee during the reporting year, summing all vouchers within the selected date range (the reporting tax year). This will be indicated as a whole number greater than zero without decimal places. The calculated Weeks Worked is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 4. MENA Ethnicity For employees belonging to the MENA (Middle Eastern or North African) ethnic type: - For the Import EEO-1 Data form, the import file can now contain M for the Race/Ethnicity field. - When you generate the EEO‑1 Export file using the Client EEO-1 & Pay Data Files form, these employees will be further subdivided into the following categories under the Race/Ethnicity/Sex column: - B70 = Non-Hispanic/Non-Latino - Male - Middle Eastern or North African - C70 = Non-Hispanic/Non-Latino - Female - Middle Eastern or North African - D70 = Non-Hispanic/Non-Latino - Non-Binary - Middle Eastern or North African For more information, see the in-product help or PrismHR System Administration User Guide.
- CSV template modified for CA Pay Data employees & Labor Contractor reporting
- New data points added to CA Pay Data Build - To support 2025 California Pay Data Reporting requirements, we’ve enhanced the standard EEO-1 build and Export to include additional data points for California employees. These changes make it easier to classify employees correctly and to calculate weeks worked for the reporting year.
- Exempt (Y)
- Non‑exempt (N)
- F=Full‑time (derived from internal employee type codes and type classification)
- P=Part‑time (derived from internal employee type codes and type classification)
- S=Intermittent (assigned when the employee’s type is flagged as Seasonal = Y)
- For the Import EEO-1 Data form, the import file can now contain M for the Race/Ethnicity field.
- When you generate the EEO‑1 Export file using the Client EEO-1 & Pay Data Files form, these employees will be further subdivided into the following categories under the Race/Ethnicity/Sex column:
- B70 = Non-Hispanic/Non-Latino - Male - Middle Eastern or North African
- C70 = Non-Hispanic/Non-Latino - Female - Middle Eastern or North African
- D70 = Non-Hispanic/Non-Latino - Non-Binary - Middle Eastern or North African
CMP-7169 Mastertax V49 file updates MN SUI Exempt PFML MasterTax v49 now reports Minnesota Paid Family and Medical Leave (MN PFML) for clients and employees who are MN SUTA (24‑24) exempt and therefore did not generate MN SUI 600 records earlier. For SUTA‑exempt scenarios, MasterTax v49 will now generate a separate MN PFML reporting record so that these wages are properly included even when no MN SUI record exists. For MN SUTA‑exempt employees in MasterTax v49: - A 600‑block RTS record will be created for tax code MN0000‑P27 when: - The employee has QTD or YTD wages under payroll code 24‑40 or 24‑41, and - The employee does not have a corresponding 24‑24 (MN SUTA) record in YTD. - The gross and taxable wages in the 600 block will report the higher of Payroll code 24‑40 in position 72-85 or Payroll code 24‑41 in position 86-99. This logic ensures MN PFML reporting is generated even when MN SUI 600 records are not created due to SUTA exemption. > Note: Note: For joint account employees (MN0000‑P27), only summarized totals are required. MasterTax will accept 500‑record level reporting, and 601 records are not required for these employees. For more information, see the in-product help or PrismHR Employer Administration User Guide.
- A 600‑block RTS record will be created for tax code MN0000‑P27 when:
- The employee has QTD or YTD wages under payroll code 24‑40 or 24‑41, and
- The employee does not have a corresponding 24‑24 (MN SUTA) record in YTD.
- The gross and taxable wages in the 600 block will report the higher of Payroll code 24‑40 in position 72-85 or Payroll code 24‑41 in position 86-99.
CMP-7163 CMP-7164 Change to the Employee Details form Previously, for employees having creditor garnishment (and potential other garnishments excluding child support) who were paid on a daily basis, for less than 5 pay periods per week, the system could not accurately calculate the daily minimum net pay cap for garnishment amount correctly. As a result, garnishments were being blocked when they should partially apply. To mitigate this, on the Employee Details form, on the Pay tab, under the Compensation section, only for employees with a daily pay period, a new optional field named Pay Periods Per Week has been introduced. [Image: screenshot] - The field appears only when the employee’s pay period is daily. - Values can be entered as a whole number from 1 to 7 or left blank. This field lets you define how many times per week a daily employee is expected to be paid (1–7), which supports more accurate daily garnishment minimum net pay calculations when employees are paid fewer than five times per week. - Changing from a daily to a non-daily pay period requires this field to be cleared; you’ll be prompted to remove the value before completing the change. - Updating this field affects garnishment minimum net pay calculations on a go‑forward basis; existing garnishment amounts are not automatically recalculated. For more information, see the in-product help or PrismHR Human Resources User Guide.
- The field appears only when the employee’s pay period is daily.
- Values can be entered as a whole number from 1 to 7 or left blank. This field lets you define how many times per week a daily employee is expected to be paid (1–7), which supports more accurate daily garnishment minimum net pay calculations when employees are paid fewer than five times per week.
- Changing from a daily to a non-daily pay period requires this field to be cleared; you’ll be prompted to remove the value before completing the change.
- Updating this field affects garnishment minimum net pay calculations on a go‑forward basis; existing garnishment amounts are not automatically recalculated.
CMP-7185 Change to the Quarterly Tax JSON Export In the Quarterly Tax JSON Export file, in the “YtdToDate” object, the “TotalTaxableWage” object has been renamed to “TotalTaxable”. Everything else, including functionality remains unchanged. For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-7196 Change to the PrismHR Tax Client Setup File Previously, both the standalone client setup and the periodic setup (with the Include PrismHR Tax Agency Export option selected) JSON export files always included AgencyInfo records for tax codes 00-10 (Federal Income Tax) and 00-17 (FUTA Employer) for all client report taxes, even when there were no tax liabilities. These AgencyInfo records are now omitted when there are no tax liabilities, which better reflects actual tax usage and simplifies client setup for clients whose taxes roll up to a PEO. For more information, see the in-product help or PrismHR Employer Administration User Guide.
WSP-3389 Support Manual or Special Batches Before Regular Payroll in Garnishment Capping Previously, enhanced capping logic depended on a processed regular payroll batch to establish the pay period. As a result, garnishment deductions taken in manual/special batches run before the regular batch were not included when the regular payroll batch was processed later. This caused duplicate garnishment deductions within the same pay period. Enhanced garnishment capping now correctly includes manual and special payroll batches processed before the regular payroll in a pay period, preventing duplicate Child Support, Spousal Support, and State Tax Levy deductions when the Enhanced Garnishment Capping field is enabled on the System Parameters form. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-8356, EP-8357 Automatically Populate Timesheet with Default Hours During the New Hire process, managers can now set an employee to have their time sheet automatically populated using default hours. To enable this option, select Auto Populate Default Hours on the New Hire Form. The Default Time Sheet Hours field displays, where the default hours to be automatically added to each time sheet can be set. These values correspond to the Auto Time Sheet and Default Time Sheet Hours in Prism. For more information, see the in-app help.
EP-9886 Enhancement for Emergency Contact for California Compliance An additional option is now available for the Emergency Contact form to comply with California regulations. If an employee’s resident state or worksite location is in California, the employee can now select which contact(s) should be notified if they are arrested or detained at work. For more information, see the in-app help.
EP-10012 New Dashboard Configuration Exits Beta The New Dashboard Configuration is no longer in beta, and the banner has been updated accordingly. Users can still switch between the new and legacy dashboard configurations using the option on the banner. For more information, see the in-app help.

Identity and Access Management (IAM) Enhancements

Ticket Description Summary Help Content
IAM-2409 Enhancement to Email Address Change When a user changes their email address for PrismONE, the Sign In Email field now updates immediately and displays as unverified. An email message is sent to the user at the new email address with a pin number to verify the email address the next time the user logs in. For more information, see the in-app help.
IAM-2536 Enhancement to Password Reset and MFA Security To increase security, users can no longer perform a password reset and set up multi-factor authentication in the same session. To perform a password reset, the user must already have MFA set up within the system. If a user without MFA information must reset their password, they must contact an administrator for a temporary password. For more information, see the in-app help.
IAM-2664 Security Enhancement for External Logins When a user logs in to the system through an external SSO, that user is blocked from using the PrismONE ID forms. For more information, see the in-app help.

Onboarding (OB) Enhancements

Ticket Description Summary Help Content
EERT-3160 Enhancement to HSA Employer Contribution Wording The wording for the HSA Employer Contribution during Benefits Enrollment has been updated to be consistent across all forms. For more information, see the in-app help.
EERT-3742 Enhancement to Metadata Editor The Benefits Enrollment Confirmations form has been enhanced with support for the User.Label metadata attribute for additional document integrations. For more information, see the in-app help.
OBE-9784 Enhancement for Emergency Contact for California Compliance During the Onboarding process, an additional option is now available for emergency contacts to comply with California regulations. If an employee’s resident state or worksite location is in California, the employee can now select to notify the contact if they are arrested or detained at work. For more information, see the in-app help.
OBE-9857 Additional Medical Offer Type A new offer type, Additional Medical (MDA), is now available for grouping together similar medical plans. This offer type allows Service Providers to group MDA benefits under one form. Employees can only select one plan for this offer type. A prebuilt Additional Medical form is now available in the Workflow Library, which can be copied into a Benefits Enrollment workflow to provide MDA benefits. > Note: Note: The Additional Medical offer type does not integrate with HSA options. For more information, see the in-app help.
OBE-9889 Enhancement to Decision Support Field The Decision Support field on the Control tab of the Client Details form is now set to Disabled by default if no previous changes by the client have been saved. If the client had made any changes to the field, the client’s saved value is retained. For more information, see the in-app help.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
WSP-3195 Client Enhancement to Positions Form A new field, Remote Position Classification, now displays on the Positions form. You can use the Remote Position Classification field to designate an alternative position classification for remote employees of the same position. > Note: Note the following: - Entering a valid Remote Position Classification displays the position’s FLSA Exempt, EEO Position Group, and EEO Position Class details, if they apply to the remote position. - Users with FULL access to the Positions form can use the Remote Position Classification field to designate an alternative position classification for remote employees of the same position. - Users with INQUIRY access to the Positions form can view the Remote Position Classification field, but cannot designate an alternative position classification for remote employees of the same position. For more information, see Defining Positions.
WSP-3196 Client Enhancement to Clone Client Form A new field, Retirement Plan Setup, now displays on the Clone Client form. You can enable the Retirement Plan Setup field when cloning a client to include the retirement plan Benefit Plan Setup information and Company Match Rules. (The default is enabled.) For more information, see Cloning a Client.
WSP-3197 Client Enhancement to the Clone/Copy Client Process When creating a new client or copying client setup records using the Clone Client or Copy Client Settings forms, you can now conditionally include or exclude the Retirement Plan Setup records. For example, if you enable the Company Benefits or Benefit Rules field and disable the Retirement Plan Setup field on the Copy Client Settings form, then during the client clone or copy client process, the system will not clone the following client configuration records: - The records available when you select Plan Class as Retirement or Employer Match on the Benefit Plan Setup form. - All the records available on the Retirement Match Rules form. However, if you enable the Retirement Plan Setup field, the system will include the retirement-related records during the clone process. For more information, see Cloning a Client and Copying Client Settings.
WSP-3201 Client Enhancement to Copy Client Settings Form A new field, Retirement Plan Setup, now displays on the Copy Client Settings form. You can enable the Retirement Plan Setup field when copying client settings to include the retirement plan Benefit Plan Setup information and Company Match Rules. (The default is enabled.) For more information, see Copying Client Settings.
WSP-3289 and WSP-3418 Client Enhancements to Client Details Form The following enhancements are now available: - A new field, Inactivation Reason, now displays on the Detail tab. This field displays the reason supplied when the client was inactivated. Note: This field only displays for Inactive clients. - A warning message now displays if you click Save without entering a client’s Federal Employer ID Number (FEIN) on the Tax tab in the Client Details form, “Client Tax Federal Employer ID Number is blank. Continue?” Click Yes to save updates to the form without supplying the FEIN. Note: Issues could occur later in this process if you do not provide the FEIN. For more information, see Maintaining Client Information and Setting Client Tax Parameters.
PD-20630 Employer Administration Enhancement to Employer Details Form The system now restricts creating an Employer ID in the Employer Details form that is a duplicate of an existing Employer ID but uses leading zeros. For example, you cannot create Employer ID 042 when Employer ID 42 already exists. Note: If you enter an existing Employer ID and include leading zeros in that ID an error message displays, “Employer IDs must be unique, excluding leading zeros. New Employer ID <new client ID> cannot be created because Employer ID <existing client ID> already exists.” For more information, see Setting Employer Details.
PD-15561 Human Resources Enhancement to Employee Termination Form If you try to terminate an employee who has a scheduled payment, a warning message now displays. For example: [Image: screenshot] Note: You can choose to continue the termination process or cease the process and return to the termination form. For more information, see Establishing Scheduled Payments and Terminating an Employee.
PD-17798 Human Resources Enhancement to Planned Time Off Requests Form Worksite managers and worksite trusted advisors with the PTO Administrator H/R Role can now view and approve leaves in the Planned Time Off Requests form for any employees who have access via Data Entity Security, not just those users where the WSM/WTA is listed as the PTO Approver for an employee. Important! The system circumvents leave approval security configurations and workflows for users with access to this form, which can result in unexpected behavior. Please note the following security used by this form: - Users with the PTO Administrator H/R Role and access to Manage Planned Time Off Requests can update leave for all employees in the client regardless of their Data Security access or the assigned PTO Approver. - Users without the PTO Administrator H/R Role and with access to Manage Planned Time Off Requests can update leave only for employees where the user has access via Data Security, regardless of the assigned PTO Approver. For more information, see Working with Planned Time Off Requests.
WSP-2983 Human Resources Enhancement to Employee Fields Import Form The system now enforces the standards of entry using the Employee Fields Import form, which allows you to assign PTO Approver and Manager users from clients other than the Client where the Employee record is located. For more information, see Performing Employee Fields Import.
WSP-3249 and WSP-3432 Human Resources Enhancements to Employee Details Form The following enhancements are now available: - When an employee is terminated and the If ACH, Turn Off ACH? field is enabled on the Employee Termination form, the system now sets all records for the employee’s direct deposit to inactive in the Employee Details form. - The W/C Class now reflects the appropriate W/C class based on the employee’s Remote Location, which is enabled on the Worksite Locations form, and their Remote Position Classification on the Positions form. > Note: Note the following: - If the Remote Location field is not enabled on the Worksite Locations form and there is no Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is not enabled on the Worksite Locations form but there is a Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is enabled on the Worksite Locations form and there is no Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is enabled on the Worksite Locations form and there is a Remote Position Classification configured on the Positions form, the system uses the Remote Position Classification to determine the W/C class. In association with the enhancement detailed above, the system now uses the correct variable when determining the W/C state, which is based on the employee’s state of residence in the Employee Details form. The configuration includes setting the Calculation Options field to Resident State Based on the Benefits tab in the Client Details form and one of the following settings: - Tax Geocode Override Option field on the Other tab in the Employee Details form set to Override Work Geocode with Resident Geocode - Remote Location field enabled on the Worksite Locations form > Note: Note the following: - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is not enabled on the Worksite Locations form, where any option, except the Override Work Geocode with Resident Geocode option, is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Worksite WC State to determine the W/C state. - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is not enabled on the Worksite Locations form and the Override Work Geocode with Resident Geocode option is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Resident WC State to determine the W/C state. - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is enabled on the Worksite Locations form and the –Select– option is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Resident WC State to determine the W/C state. - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is enabled on the Worksite Locations form and the Override Work Geocode with Resident Geocode option is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Resident WC State to determine the W/C state. For more information, see Depositing All or Part of Employee’s Net Payment and Defining Employee Name and Contact Information.
WSP-3250 Human Resources Enhancement to Employee Master Report With the introduction of the Remote Position Classification field to designate an alternative position classification for remote employees of the same position, which is set on the Positions form (see Enhancement to Positions Form for more information), the Employee Master Report now displays this designation to ensure that the accurate W/C Class code displays when you run this report. For example: [Image: screenshot] > Note: Note the following that occurs in the Worksite Locations form: - If the Remote Location field is not enabled on the Worksite Locations form and there is no Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is not enabled on the Worksite Locations form but there is a Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is enabled on the Worksite Locations form and there is no Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is enabled on the Worksite Locations form and there is a Remote Position Classification configured on the Positions form, the system uses the Remote Position Classification to determine the W/C class. > Note: Note the following that occurs in the Client Details form: - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is not enabled on the Worksite Locations form, where any option, except the Override Work Geocode with Resident Geocode option, is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Worksite WC State to determine the W/C state. - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is not enabled on the Worksite Locations form and the Override Work Geocode with Resident Geocode option is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Resident WC State to determine the W/C state. - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is enabled on the Worksite Locations form and the –Select– option is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Resident WC State to determine the W/C state. - If the Calculation Options field is set to Resident State Based on the Benefits tab in the Client Details form and the Remote Location field is enabled on the Worksite Locations form and the Override Work Geocode with Resident Geocode option is set in the Tax Geocode Override Option field on the Other tab in the Employee Details form, the system uses the Resident WC State to determine the W/C state. For more information, see Employee Master Report.
WSP-3258 Human Resources Enhancement to Approvals Pending Form You can now approve or deny approvals for the new Late Payroll Posting Approval Policy in the Approvals Pending form. (Users with FULL access to the Global Approval Policies and Approval Policies forms can configure a Late Payroll Posting approval policy at the global or client level by selecting this Approval Type.) > Note: Note the following: - When a Late Payroll Posting pending approval is approved: - The associated payroll batch status updates from POSTPEND > INITCOMP. - The Approval status is Approved. - Starting Payroll Finalization again after receiving the approval completes the finalization process without disruption, assuming there are no changes to the timesheet or recalculations have occurred in the payroll. - If you update the timesheet or recalculate the payroll, the approval must be resubmitted. - When a Late Payroll Posting pending approval is denied: - The associated payroll batch status updates from POSTPEND > INITCOMP. - The Approval status is Denied. - When you attempt Payroll Finalization again after the approval is denied, the system generates a new Late Payroll Posting Approval for the payroll. For more information, see Working with Pending Approvals.
WSP-3396 and WSP-3415 Human Resources Enhancement to Manage Pending Approvals Form Users with FULL access to the Manage Pending Approvals form can now do the following: - View and reassign pending ACH Maximum and Late Payroll Posting Approvals for the selected client. - Filter pending approvals for ACH Maximum and Late Payroll Posting Approvals. Users with INQUIRY access to the Manage Pending Approvals form are now restricted as follows: - Can only view pending ACH Maximum and Late Payroll Posting Approvals for the selected client. - Cannot filter the form results. Note: Worksite managers and worksite trusted advisors are now required to limit user access to approvals for only those employees/payrolls where they are granted appropriate security access. For more information, see Managing Pending Approvals.
PD-20232 Payroll Enhancement to Payroll Variance Analysis Dashboard The system now analyzes and updates the Payroll Variance Analysis dashboard when you enter or select a payroll number in the Compare to Payroll field that meets the following criteria: - The comparison Payroll Pay Date is within 180 days of the initialized Payroll. - The comparison Payroll Type is Regular or Special. - The comparison Payroll Number is a valid payroll. - The comparison Payroll is finalized. - The comparison Payroll includes the same Pay Group. For more information, see Payroll Variance Analysis.
PD-19660, PD-19778, and PD-20640 Payroll Enhancements to Data Import Tool The following enhancements are now available: - A new import template, Client Details (Tax), is now available. You can use the Client Details (Tax) import template to import taxes for the client into the state tax setup on the Client Details form at once to reduce the amount of manual work required. (This is helpful when maintaining tax IDs for various agencies.) - A new import template, Employee Benefits Per Hour, is now available. You can use the Employee Benefits Per Hour import template to import the employee benefits per hour at once to reduce the amount of manual work required. Important! This update does not display in the Benefits Per Hour field on the Pay tab in the Employee Details form. - A new field, Override Work Geocode, now resides on the Worksite Locations import template in column 36, and in the downloadable sample header file. You can indicate the Override Work GeoCode setting as appropriate: - Use Worksite Location GeoCode (no value) - Override with Resident GeoCode (R) - Override with Home Location GeoCode (H) - Override T/S GeoCode with Resident GeoCode (T) Note: The system only applies the override if there are no overrides set at the system, client, or employee level. Typically, this is used to create “worksite locations” for remote employees. For more information, see Importing Client Taxes, Importing Employee Benefits Per Hour, and Importing Worksite Locations.
WSP-970, WSP-1208, and WSP-1210 Payroll Enhancement to Global Approval Policies and Approval Policies Forms A new option, Late Payroll Posting, is now available as an Approval Type in the Global Approval Policies and Approval Policies forms. Selecting Late Payroll Posting stops payrolls from being posted on or after the ACH Late Payroll Posting date and time during the finalization process, which prevents the payroll from finalizing until it is approved by a user in accordance with the applicable Approval Policy configuration. (After selecting Late Payroll Posting, the system displays any existinglate payroll posting steps.) > Note: Note the following: - To stop a payroll from finalizing, the client must have ACH billing configured on the Billing tab on the Client Details form by selecting one of the following statuses in the ACH Status field, Active, ACH by Division, or ACH by Location. In addition, the approval observes the positive or negative value in the Adjust to ACH Bill Day field, which adjusts the processing of the ACH if it is different from the employee pay date. - Users with FULL access to the Global Approval Policies form can configure a Late Payroll Posting approval policy at the global level by selecting this Approval Type. - Users with INQUIRY access to the Global Approval Policies form can access existing Late Payroll Posting approval policies in read-only format using the Service Type and Approval Type but cannot update the policy setup. For more information, see Setting Global Approval Policies and Setting Approval Policies.
WSP-3063 Payroll Enhancement to Client Allocation Formats Form An error message now displays if you enter a duplicateAllocation Code in a client allocation format in any of the columns in the Report Columns panel in the Client Allocation Formats form. For example: [Image: screenshot] For more information, see Setting Global Approval Policies and Setting Approval Policies.
WSP-3251 Payroll Enhancement to Employee Voucher Form With the introduction of the Remote Position Classification field to designate an alternative position classification for remote employees of the same position, which is set on the Positions form (see Enhancement to Positions Formfor more information), the Workers Comp tab on the Employee Voucher form now displays this designation to ensure that the accurate Class Code displays. For example: [Image: screenshot] > Note: Note the following that occurs in the Worksite Locations form: - If the Remote Location field is not enabled on the Worksite Locations form and there is no Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is not enabled on the Worksite Locations form but there is a Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is enabled on the Worksite Locations form and there is no Remote Position Classification configured on the Positions form, the system uses the standard Position Classification to determine the W/C class. - If the Remote Location field is enabled on the Worksite Locations form and there is a Remote Position Classification configured on the Positions form, the system uses the Remote Position Classification to determine the W/C class. > Note: Note the following that occurs in the Client Details form: - If the Calculation Options field is set to Select or Resident State Based on the Benefits tab in the Client Details form, the system recognizes the Remote Location field setting for the employee’s assigned Worksite Location set on the Work tab in the Employee Details form. - If the Calculation Options field is set to Time Sheet Location Based on the Benefits tab in the Client Details form, the system recognizes the Remote Location field setting for the employee’s time sheet detail entry/entries locations. For more information, see Reviewing Workers Comp Tab Details.
PP-1635 System Enhancement to CC File Storage CC.FILES older than seven years will be deleted from the system. Carriers will still retain copies of the files on their own storage devices.
PP-1668 System Enhancement to Approvals Dashboard Performance Improvements have been applied to the Approvals Dashboard to significantly improve performance, especially for clients with a large number of employees. For more information, see the in-product help.
PP-2148 System SSO Support for Employee Navigator An external SSO option has been added for integration for upcoming features. For more information, see the in-product help.
PP-2166 System Enhancement to Report Search When clients search for the PEO Client Accounting G/L Detail Report using the search function, only the proper report now displays in the Reports section of the results. Previously, another extraneous report displayed when performing the same search. For more information, see the in-product help.
PP-2173 System Enhancement to PrismONE ID Support Added support for PrismONE ID outbound SSO over OIDC. Please refer to the Establishing SSO Services help form for the table of values for this integration. For more information, see the in-product help.
WSP-3244 System Enhancement to Email Services Form A new email template type, Late Payroll Posting Approval, is now available on the Email Services form. Note: You can access the Email Services form by selecting Email Services in the Actions menu on the System Parameters form. You can use the Late Payroll Posting Approval template type to create an automatic email message that prevents s payroll from being posted on or after the Late Payroll Posting date and time during the finalization process, which prevents the payroll from finalizing until it is approved by a user in accordance with the applicable Approval Policy configuration. Note: Template types are maintained in the Message Templates form. In addition, a new standard message template, LATEPAYROLLPOST, is now available as the default for the Late Payroll Posting Approval template type by selecting Template, which displays the Search Message Templates list. In association with the new LATEPAYROLLPOST message template, the system uses four substitution variables, <<COMPANY.NAME>>, <<CLIENT.NAME>> (includes client ID), <<PAYROLL.NUMBER>>, and <<PAY.DATE>>, for billing purposes. For example: [Image: screenshot] For more information, see Setting Up Automated Email Messages.
WSP-3287 System Enhancement to Client Status Change Form A new (required) field, Client Inactivation Reason, now displays in the Client Status Change form when the New Status field is set to Inactive. You can enter or select a corresponding reason code associated with the client’s inactive status in the Client Inactivation Reason field. (If you select this field, only reasons matching Inactive display in the Search Inactive Reason list.) In addition, only applicable reasons now display in the Select Term Reason list when you select the Client Termination Reason field (required). (The New Status field must be set to Terminated to display this field.) For more information, see Changing the Client Status.
WSP-3288 System Enhancement to Client Term Reasons Form A new field, Valid Status Uses, is now available on the Client Term Reasons form. You can select a Valid Status Uses option for the following client statuses: - Termination Only - Inactivation Only - Both For more information, see Setting Up Automated Email Messages.
PD-19430, PD-20590, PD-20591, PD-20592, PD-20593, PD-20595, PD-20596, PD-20597, PD-20615, PD-20616, PD-20617, and PD-20618 Time Off (formerly PTO) PTO Terminology Update To ensure consistent naming conventions are used across the PrismHR platform, the legacy PTO terminology described below now aligns with the recently updated Time Off Workflow terminology. Note: In association with this terminology update, the PTO User Guide now displays as the Time Off User Guide. The following legacy PTO forms have been renamed to reflect the updated Time Off Workflow terminology, as documented in the Client Administration Guide and the Time Off User Guide (formerly Paid Time Off User Guide): - PTO Absence Codes = Time Off Pay - PTO Auto-Enrollment Rules Import = Time Off Auto-Enrollment Rules Import - PTO Auto Enroll Rules = Time Off Auto Enroll Rules - PTO Auto-Enrollment Rules Maintenance = Time Off Auto-Enrollment Rules Maintenance - PTO Auto Register Enrollment = Time Off Auto Register Enrollment - PTO Benefit Plans = Time Off Plans - PTO Classes = Time Off Types - PTO Register Types = Time Off Accrual Schedules Note: This adjustment was made in the breadcrumb paths, on-screen form names, global searches, menu structures, user role process descriptions, Work Centers (except for the Time Off Auto-Enrollment Rules Maintenance form), Related Actions Links, and in any error messages or warning messages that pertain to these legacy forms. The following legacy center names in the “Time Off” category on the Work Centers page now display as follows: - PTO Adjustments and Maintenance = Time Off Adjustments and Maintenance - PTO Plan Setup and Enrollment = Time Off Plan Setup and Enrollment - PTO Reporting = Time Off Reporting - PTO Work Center = Time Off Work Center Note: This update also displays in the user role process description, the menu structure, and the dashboard. The following legacy field names were updated: - Accrue on Arrears = Accrue On Arrear Voucher - Add to Balance On First Accrual = Add Hours To Balance on First Accrual - Auto-enroll Through-Date is Day Before Start Date = Auto-enroll Thru Date is Day Before Start Date - Calculation Basis = Accrual Method - Class Code = Time Off Type Code - Class Description = Type Description - Date to use as the PTO Start Date… = Date to use as the Time Off Start Date… - Display a Warning if Employee Uses More Hours Than Available = Payroll Warning if More Hours Used Than Available - Display Used Amt on Check Stub Memo = Display Used Amount on Pay Stub - Fiscal End Month/Day = Last Day of Fiscal Year - Global PTO = Use Global PTO - Lifetime Maximum Carryover = Lifetime Carryover - Negative Carryover = Allow Negative Carryover - Pay Stub Name = Description for Pay Stub - Plan Description = Description - Plan Expires = Obsolete Date - Plan ID = Time Off Plan - Print On Check = Print On Pay Stub - PTO Benefit Plan = Time Off Plan - PTO Class = Time Off Type - PTO Plan = Plan Code - PTO Register Type = Accrual Schedule - PTO Type Code = Schedule Code - Register Types = Accrual Schedule - Stop Init If Exceed Limit = Display Payroll Warning when Maximum Usage Limit Exceeded - Suppress Print Period = Suppress Pay Stub Printing For - Trigger Date = On - Trigger Method = Accrual Frequency - Updates PTO Register = Updates Time Off Register - Year End Basis = Plan Year Based On For more information, see Accessing Time Off Plan Setup and Enrollment Forms, Creating Time Off Absence Codes, Creating Time Off Accrual Schedules, Defining Time Off Plans, Fields Included in Each Import, Processing Time Off Auto Register Enrollment, Using the Time Off Work Center, and the Understanding Time Off Setup Workflow Process Terminology article on the CRC.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-1975 Previously, on the Employee Deduction Arrears form, when you selected an employee who had at least one existing deduction arrear and then selected the checkbox for any record, the system did not display the checkbox as selected when the browser was resized down. Additionally, the Change Status and the Convert to Adjustment button overlapped. Now, this is fixed.
WSP-2936 Previously, for an employee who had the HDHP Not Required field enabled on the Employee Flexible Spending Accounts form along with HSA Match Override amount entered, then the system allowed HSA Match to pull and exceed annual specified limits. Now, this is fixed.
WSP-3217 Previously, when you ran a Benefits Billing Detail Report with multiple filters and selection criteria (like Employee ID, Benefit Plan ID, Insurance, Department, Division, Location, and so on), then the report displayed these information as the report header name, which lead to formatting issues. Now, this is fixed. The report header now displays the count of plans or employees, for example, “Report for 5 Benefit Plans”, “Report for 2 Employee”, and so on.
WSP-3354 Previously, on the Benefits Billing Detail Report form, when you ran a report with Defined Ranges selected as Prior 2 Months, the system calculated the date range incorrectly. Now, this is fixed.
WSP-2889 Previously, for a client set up with Departments Restrict Eligibility option selected for Eligible Benefits Determinant field on the Benefits tab of the Client Details form, the Benefits Eligibility Report displayed blank results even if Departments were set up with eligible benefits. Now, this is fixed.
WSP-3409 Previously, when you opened the Retirement Plan Enrollment modal form, the Import Retirement Plan Adjustments button had alignment issues. Now, this is fixed.
WSP-3410 Previously, on the Benefit Rules form, the system did not display the Import Benefit Rules quicklink button. Now, this is fixed.
WSP-3411 Previously, on the Carrier Plan Billing Report form, when you enter a future date in the As of Date field and run the report, the system displayed today’s date in the Coverage Start Date column on the report. Now, this is fixed.

Compliance (CMP) Fixes

Jira # Issue Summary Resolution
CMP-7142 Previously, clients with New York Metropolitan Commuter Transportation (NY MCT, tax code -37) liability reported to an Alternate Employer (Alternate ER), were not included on the NY Form MTA-305 tax reporting file. In some client-reporting scenarios with NY MCT wages for an Alternate Employer, the NY MTA-305 download file was not generated at all. Now, this is resolved. The NY Form MTA-305 reporting logic has been updated so that: - When NY MCT (-37) tax liability is present for an Alternate Employer, the associated client is now correctly included in the NY Form MTA-305 file for that Employer. - The file generation process for NY MCT client reporting now properly handles wages associated with Alternate Employers, ensuring a file is produced when valid NY MCT wages exist. - The NY Form MTA-305 download now aligns with the underlying tax data, reducing discrepancies between taxes billed and calculated liability.
Jira # Issue Summary Resolution
DM-2106 When a user attempted to preview a Word or Excel file in Document Management, an error occurred. This is fixed.

Employee Portal (EP) Fixes

Jira # Issue Summary Resolution
EERT-3059 If a client did not have any positions set up in the system, the Position field did not display on the New Hire form, but was still set as required and produced an error message. This is fixed.
EERT-3062 When an employee was ineligible for one of their forms on the Taxes form in Employee Portal and attempted to view the Taxes summary form, an error occurred. This is fixed.
EERT-3067 When some employees attempted to access the Direct Deposit form in Employee Portal, an error occurred. This is fixed.
EERT-3074 When an employee added a new direct deposit account with the Remaining method in Employee Portal, the inactive Remaining method direct deposits were correctly removed, but a blank line was left behind on the Employee Details record in Prism. This is fixed.
EERT-3140 Certain special characters were allowed in Prism passwords, but these characters were not allowed in Employee Portal passwords, which caused a password to be incorrectly flagged as invalid when an employee attempted to reset their password in Employee Portal. This is fixed.
EERT-3188 When an employee attempted to log in to the Employee Portal and their worksite location did not have a State listed in the record, an error occurred. This is fixed.
EERT-3190 When a manager with access to over a thousand employee records accessed the View My Employees form in Employee Portal, sometimes employee names displayed as undefined, even though they displayed correctly on the home screen and employee records. This is fixed.
EP-10042 When a Worksite Manager with access to multiple clients viewed information for a client where they were not an employee, the manager could not view Total Compensation reports for any employees in that client. This is fixed.
EP–10048 Users with an assigned manager role that did not have access to view paystub details were still able to click View Paystub on the Pay History form and view an employee’s paystub. This is fixed.
EP-10932 When an employee attempted to update their Tax Forms via the Life Event workflow in Portal, the system attempted to update the forms in a frame on the existing page and produced an error instead of navigating to the correct form. This is fixed.

Identity and Access Management (IAM) Fixes

Jira # Issue Summary Resolution
IAM-2402 When users viewed the mandatory signup message for PrismONE in Employee Portal, refreshing the page allowed the users to bypass the signup message. This is fixed.
IAM-2521 Users who already had a Worksite Trusted Advisor account linked to their PrismOne ID were unable to register their account through Employee Portal. This is fixed.
IAM-2888 Users with time-based one-time password (TOTP) set to their phone number for multi-factor authentication were unable to use the Forgot Password workflow. Resetting a password via phone required SMS messaging set up as the MFA method. This is fixed. SMS and TOTP are now both valid MFA options for resetting a password.

Onboarding (OB) Fixes

Jira # Issue Summary Resolution
EERT-3189 When a client set up a vanity URL, this URL did not display on certain updates and notifications. This is fixed.
EERT-3191 When an employee viewed the Employee Confirmation Statement during Benefits Enrollment, the wrong HSA Plan displayed on the form. This is fixed.
EERT-3192 When an employee’s I-9 Section 2 was approved and the WSM marks the approval that the documents were examined remotely, the Remote Verification box was not updated correctly in Prism. This is fixed.
EERT-3738 Clients were unable to remove all forms from a workflow. This is fixed.
OBE-9834 When an employee viewed the Benefits Enrollment Summary form and the Benefits Confirmation form, several lines of text displayed inconsistently. These included the employer contribution displaying as monthly when it was set to yearly, displaying a flat fixed amount instead of “up to” that amount, and the employee contribution displaying as yearly when it was set to monthly. These issues have been fixed.
OBE-9859 When users viewed the I-9 form, the text on the form displayed in bold and did not wrap properly. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
PD-19601 General When users selected the User ID filter on the Worksite User Data Security Download form and then selected User ID in the panel that displayed, the Select Users list did not apply to user IDs and instead only returned results that matched the User Name. The selector filter criteria now applies to the User ID and the User Name when users select User ID on the Worksite User Data Security Download form.
PD-20379 General When the HIDE-SUPPORT-TEAM custom feature code was enabled for one client and users navigated to another client, the system sometimes populated the information on the Client Details form with the date from the first client. This is fixed.
PD-20499 General The system did not display an error message when users manually entered a Benefit Group or a Retirement Benefit Group in the New Hire form that had the Stop All Use On and/or Stop New Use On date configured in the past. An error message now displays if users manually enter a Benefit Group or Retirement Benefit Group that has a Stop All Use On and/or Stop New Use On date that is in the past. In addition: - Users cannot manually enter a Benefit Group that is only for a Retirement plan. - Users cannot manually enter a Retirement Group that is only for Benefit plans.
PD-20561 General The linked accrual amount at the end of the fiscal year did not transfer to the balance account in the Employee PTO Register form. This is fixed.
PD-20601 General When users cloned a client in the Clone Client form with leading zeros that used the same client number that did not use leading zeros, the system created duplicate records, including benefit plans, worksite locations, and divisions. The system now restricts cloning a client using a new client number that includes leading zeros, which is the same as an existing client number. In addition an error message now displays, “Client IDs must be unique, excluding leading zeros. New Client ID cannot be created because Client ID already exists.”
PD-20627 General When users created an employer in the Employer Details form using “0” or all zeros as the Employer ID, it caused issues downstream. An error message now displays if users try to create an Employer ID that only contains zeros, “Employer ID cannot contain only zeros.”
WSP-3430 General When a user role was configured with field security for the Last Pay Period Hours field on the Employee Termination form set to Hidden or Disabled, the system still displayed that field. The following now occurs: - When the Last Pay Period Hours field is set to Hidden, the field does not display. - When the Last Pay Period Hours field is set to Disabled, the field displays but is not editable.
PD-19878 Payroll The EE Arrears Received field name in the Non-Bill Accounting panel on the PEO Client Accounting form was misspelled. This is fixed.
PD-20018 Payroll When users created a voucher in the Check History Import form that included FSA deductions and then subsequently deleted that voucher and the register was rebuilt, the system continued to display the FSA deductions in the employee’s Flexible Spending Account. This is fixed.
PD-20585 Payroll When an employee had approved leave, the system auto-accepted it in the timesheet and then if the employee requested additional time in that same pay period, the system produced incorrect leave amounts. This is fixed.
PP-2155 System When a client searched for a bank account on the Bank Accounts form, the Previous button could only be clicked on the right side of the button icon. This is fixed.
PP-2170 System When a client used a custom background color and an employee saved a change and returned to the dashboard, the custom background color did not display properly between the dashboard panels. This is fixed.

========================================================================

March (R_202603)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/03/whatsnew-R_202603.htm Path: Release-Notes/2026/03/whatsnew-R_202603.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

Documentation Enhancements

Click a link to read about the documentation enhancements included in this release.

Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202604

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/04/Release-Notes-R_202604.htm Path: Release-Notes/2026/04/Release-Notes-R_202604.htm

Release Notes R_202604

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202604 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday April 23, 2026
Wave 2 Friday April 24, 2026
On-Premise Thursday April 30, 2026

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-3436 Changes to the Cafeteria Plan Contribution form While accessing the Cafeteria Plan Contribution form via the Actions menu on the Employee Benefits Enrollment form, the form now displays the Cafeteria Plan Contributions set on the Benefit Groups form in read-only format to the right of the current Cafeteria Plan Contributions section. For example: [Image: screenshot] - On the Employee Benefits Enrollment form, if you do not select an employee and then try to access the CAFE Contribution from the Actions menu, then the system displays an error message stating, Enter a Valid Employee Id first. - On the Cafeteria Plan Contribution form, under the Benefit Group Cafeteria Plan Contribution section, a hyperlink button for Benefit Group is now available that allows the users to select available Benefit Groups. - The Benefit Group displayed is default to the employee’s assigned Benefit Group as of today’s date. For more information, see the Defining Cafeteria Plan Contributions help topic.
WSP-3886 Changes to the Employee Benefit Overview form On the Employee Benefit Overview form, after you select an employee, then under the Employee Benefit Overview table, the Coverage Level column now displays the Type Code instead of earlier Type Description for any benefit plan that uses the group benefit plan types. For example, for a plan type of Family, the Coverage Level column earlier displayed Family, but now it displays the Family Type Code, FAM. You can find the Type Code for a benefit plan on the Group Benefit Plan Types form. [Image: screenshot] For more information, see the Displaying an Employee’s Benefit Plans help topic.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
CMP-7003 & CMP-7004 Updates to Illinois Pay Data Report To support Illinois Pay Data reporting requirements for tax year 2024 (Reporting Year 2025) , the IL Pay Data export template has been updated. This report now includes three new reporting elements and supports the EEO Ethnic Code category Middle Eastern or North African. The export now reports: - Column N: PaidHS (Reports whether the employee is salary or hourly) - Column O: BaseHourlyRate (Reports the employees hourly rate when Column N = H. When Column N = S, the rate reported is 0) - Column P: CBAYN: Is the employee covered by a CBA? This field will report as N. For more information, see the in-product help or PrismHR System Administration User Guide.
- Column N: PaidHS (Reports whether the employee is salary or hourly)
- Column O: BaseHourlyRate (Reports the employees hourly rate when Column N = H. When Column N = S, the rate reported is 0)
- Column P: CBAYN: Is the employee covered by a CBA? This field will report as N.
CMP-7101 & CMP-7205 CA Pay Data - Tax Year 2025 reporting updates For tax year 2025 and later, the California Pay Data Reporting specifications have changed. To align with the updated state requirements, we have updated the EEO-1 Build, Import and CSV templates. The California Pay Data CSV export (EEO Processing / EEO-1 Processing / Client EEO-1 & Pay Data Files (CA Payroll Employee Report)) updates are now complete for Tax Year 2025. The updated export including the newly added data points and MENA classification were released on March 12, 2026 via a hotfix. Note: These changes affect only tax year 2025 and forward; tax year 2024 and prior remain unchanged. Here is the California Pay Data Reporting link. - CSV template modified for CA Pay Data employees & Labor Contractor reporting - New data points added to CA Pay Data Build - To support 2025 California Pay Data Reporting requirements, we’ve enhanced the standard EEO-1 build and Export to include additional data points for California employees. These changes make it easier to classify employees correctly and to calculate weeks worked for the reporting year. ### What’s New - California Labor Contractor Pay Data Report ##### 1. Exemption Status For California employees, based on the FLSA status on the employee’s home position as of the voucher “as of” date, the EEO‑1 build now includes an Exemption Status field that indicates whether the employee is: - Exempt (Y) - Non‑exempt (N) The exemption status is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 2. Employment Type Based on the employee’s type from the voucher “as of” date, the EEO‑1 build now classifies each California employee into one of three Employment Types: - F=Full‑time (derived from internal employee type codes and type classification) - P=Part‑time (derived from internal employee type codes and type classification) - S=Intermittent (assigned when the employee’s type is flagged as Seasonal = Y) This employment type is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 3. Weeks Worked in Reporting Year by Labor Contractor Location The EEO‑1 build now calculates the total number of weeks worked by Labor Contractor location for each California employee during the reporting year, summing all vouchers by Labor Contractor location within the selected date range (the reporting tax year). This will be indicated as a whole number greater than zero without decimal places. The calculated Weeks Worked is included in the EEO‑1 Build and the EEO‑1 Export file. ##### 4. MENA Ethnicity For employees belonging to the MENA (Middle Eastern or North African) ethnic type: - For the Import EEO-1 Data form, the import file can now contain M for the Race/Ethnicity field. - When you generate the EEO‑1 Export file using the Client EEO-1 & Pay Data Files form, these employees will be further subdivided into the following categories under the Race/Ethnicity/Sex column: - B70 = Non-Hispanic/Non-Latino - Male - Middle Eastern or North African - C70 = Non-Hispanic/Non-Latino - Female - Middle Eastern or North African - D70 = Non-Hispanic/Non-Latino - Non-Binary - Middle Eastern or North African For more information, see the in-product help or PrismHR System Administration User Guide.
- CSV template modified for CA Pay Data employees & Labor Contractor reporting
- New data points added to CA Pay Data Build - To support 2025 California Pay Data Reporting requirements, we’ve enhanced the standard EEO-1 build and Export to include additional data points for California employees. These changes make it easier to classify employees correctly and to calculate weeks worked for the reporting year.
- Exempt (Y)
- Non‑exempt (N)
- F=Full‑time (derived from internal employee type codes and type classification)
- P=Part‑time (derived from internal employee type codes and type classification)
- S=Intermittent (assigned when the employee’s type is flagged as Seasonal = Y)
- For the Import EEO-1 Data form, the import file can now contain M for the Race/Ethnicity field.
- When you generate the EEO‑1 Export file using the Client EEO-1 & Pay Data Files form, these employees will be further subdivided into the following categories under the Race/Ethnicity/Sex column:
- B70 = Non-Hispanic/Non-Latino - Male - Middle Eastern or North African
- C70 = Non-Hispanic/Non-Latino - Female - Middle Eastern or North African
- D70 = Non-Hispanic/Non-Latino - Non-Binary - Middle Eastern or North African
CMP-7183 Changes to the Tax Deductions form On this form a new field named Suppress PrismHR Tax Client Setup Reporting Only has been introduced as you can see below. [Image: screenshot] - This option is not available if you have already selected the Suppress Reporting to PrismHR Tax & Mastertax field. - When this field is: - Unchecked (Default) - The tax deduction will continue to be included in the PrismHR Tax Agency setup files. - Checked - The standalone Client Setup File & the setup file that can be generated during the daily JSON generation will not include these tax codes in the agency setup records. This will continue to report on the daily and quarterly JSON exports. For more information, see the in-product help or PrismHR System Administration User Guide.
- This option is not available if you have already selected the Suppress Reporting to PrismHR Tax & Mastertax field.
- When this field is:
- Unchecked (Default) - The tax deduction will continue to be included in the PrismHR Tax Agency setup files.
- Checked - The standalone Client Setup File & the setup file that can be generated during the daily JSON generation will not include these tax codes in the agency setup records. This will continue to report on the daily and quarterly JSON exports.
CMP-7781 Employer PFML Pickup Contribution Taxation The IRS released further guidance on the requirements of Revenue Ruling 2025-04. This rule requires that when an employer voluntarily pays part of the employee’s required PFML contribution, this amount is treated as additional compensation to the employee. This requires that the excess contribution amounts are included in the employee’s gross income and wages for federal employment tax purposes. PrismHR is releasing new functionality to calculate the employer contribution amounts retroactively to 1/1/26. The April release includes the necessary system configuration UI components including: ## Changes to the System Parameters form On this form, in the Global Codes Setup section, under the Benefits group, a new field named PFML ER Pickup Fringe Pay Code has been introduced as you can see below. [Image: screenshot] You can click the hyperlink and select a pay code with a pay class of non‑cash fringe benefit from the Select fringe benefit dialog box or you can manually enter a valid pay code with a pay class of non‑cash fringe benefit here. If you manually enter an invalid (non‑fringe or non‑existing) pay code here, and click Save, you will receive an error message stating is not a non-cash fringe benefit. The invalid value will be cleared from this field. ## Changes to the State Tax Rates (SUTA) form On this form, in the Rate Breakdown section, a new field named PFML Employer Pickup has been introduced. [Image: screenshot] This field will display only if the field named PFML ER Pickup Fringe Pay Code on the Systems Parametrs form as been defined. This field is optional. Enter the amount the employer is contributing in excess of their mandatory contribution amount here. You can only enter numeric values with decimals. For example, if the State PFML rate is .8 with a 50% split between Employee and Employer, and the employer contributes the full .8% with the employee contributing 0%, you will enter .4 in this field. Note: The payroll calculation process will be released in the upcoming 2026 May release. You will not see any changes within payroll until the 2026 May release is complete. For more information, see the in-product help or PrismHR System Administration User Guide.
RRT-6847 Quarterly Reporting File Format updated for Michigan (MI) to meet the new EFW2 Specifications The State of Michigan has released updated specifications for quarterly reporting. Michigan requires employers and agents filing quarterly wage data to adhere strictly to its EFW2 file format. In line with that, we have updated the Michigan (MI) Quarterly Wage Report to use the EFW2 file format required by the Michigan UIA. The previous MiWAM layout is no longer supported by the state, and this change ensures files generated from Prism continue to be accepted. - The MI Quarterly report now generates an EFW2‑compliant file instead of the legacy MiWAM format. - The file includes the RE (Employer) and RS (Employee) Wage records required by Michigan, aligned with the MiUI EFW2 File Format v1 specification: For more information, see the in-product help or PrismHR System Administration User Guide.
- The MI Quarterly report now generates an EFW2‑compliant file instead of the legacy MiWAM format.
- The file includes the RE (Employer) and RS (Employee) Wage records required by Michigan, aligned with the MiUI EFW2 File Format v1 specification:

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-9893 Enhancement to My Approvals Form When a manager approves or denies an item on the My Approvals form, and that item is on a later page, the session now remains on the same page the manager just reviewed. For example, if the manager is reviewing an item on Page 3, approving or denying the item will no longer return the manager to the first page. If the reviewed item is the last item on the last page, the session will go one page back rather than returning to the first page. This enhancement makes it easier to go through several items on the later pages of the My Approvals form. For more information, see the in-app help.
EP-10062 Client Controls for Redirecting to Onboarding A new option has been added to allow managers to use the new version of Onboarding in Portal to enter in New Hires via the New Hire Dashboard button. > Note: Note: This feature has been added to support a future Onboarding release, and is not currently active. The functionality is described here for future reference. If the Client Controls Onboarding Version option is set to New, clicking the New Hire Dashboard button directs the manager to the new Onboarding system on a new tab in their browser. If the Client Controls Onboarding Version option is set to Legacy, clicking the New Hire Dashboard button directs the manager to the New Hire Dashboard in Employee Portal. > Note: Note: The new Onboarding system is not available for Trusted Advisors. If the options is selected to redirect to Onboarding and a Trusted Advisors clicks the New Hire Dashboard button, a message displays indicating Trusted Advisor access to Onboarding is unavailable. > Note: Note: I-9 Approvals are not supported in Employee Portal at present, and must be completed in Onboarding. For more information, see the in-app help.
EP-10939 New Hire Dashboard Security for Worksite Managers Security access to the New Hire Dashboard has been improved to honor Worksite Manager data security settings in Prism. Worksite Managers can now only view new hires that align with their security settings for divisions, locations, departments, and other restrictions within the organization. The dropdown options available when entering a new hire also align with these security restrictions. For example, if a Worksite Manager only has security access to a single department within the company, that manager can only see new hires for that department on the New Hire Dashboard and can only select new hires from that department on the New Hire Entry form. > Note: Note: Once the employee has an employee record in the system, security access is then evaluated based on the employee record. For more information, see the in-app help.

Identity and Access Management (IAM) Enhancements

Ticket Description Summary Help Content
IAM-2031 Enhancement to My Login Settings Form Users can now change their first and last name on the My Login Settings form. Simply click Change next to your name in the Account Settings section to access the Change Your Name form. For more information, see the in-app help.
IAM-2539 Enhancement to Password Reset Process When an administrator views a user record on the User Administration form, if the user has no MFA factors set up, a message now displays letting the admin know that the user will not be able to reset their own password. For more information, see the in-app help.
IAM-2630 User Management Form Service Providers can now delegate PrismONE ID maintenance tasks to support representatives through the new User Management form. This form can be used to securely change user addresses and mobile numbers, send password reset messages, create temporary passwords, and set the user’s status. A new process ID, HRP.USERS*USER.MANAGEMENT.PRISMONE, is now available to grant access to this form. Security access to the User Management form is separate from other user security fields, so administrators can provide lower-tier support representatives with access to this form to safely delegate login support tasks. The User Management form can be accessed through the Actions menu on the Employee Details form. If a user hasn’t completed their PrismONE ID registration, the action item displays as User Management (Pending Registration). If the user does not have a PrismONE ID account or is missing a user record, a message displays on the form indicating which steps a user must take to complete registration. > Note: Note: Please fully read the documentation fully to make sure you understand the capabilities of this item before granting access to this feature. For more information, refer to See PrismONE ID – PrismHR User Admin Access Action Menu.
IAM-2700 Improved PrismONE ID Security for Shared Machines The PrismONE ID system has been enhanced to better detect when a user is on a shared machine and force MFA to improve security for users who forget to fully log out before closing their browser. For more information, see the in-app help.
IAM-2711 Enhancement to Changing User’s Email Address When an administrator attempts to change a user’s email address on the User Management form and enters an email address that already exists in the system, a message displays indicating that an account using this email already exists. For more information, see the in-app help.

Onboarding (OB) Enhancements

Ticket Description Summary Help Content
OBE-9697 Enhancement to Life Event Workflows When Decision Support Tools are enabled on the Enrollment Options form, the selected decision support tool can now display during the Life Event workflow. When a user proceeds to the Life Event portion of Benefits Enrollment, the Decision Support form displays. For more information, see Maintaining Life Event Codes.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
PD-20629 Client Enhancement to Contacts Form You can now enter or select multipleContact Type IDs in the Contacts form. (After entering or selecting the Contact Type ID, the associated Contact Type displays.) Note: The list of Contact Type IDs that displays is configured in the Contact Types form. For more information, see Maintaining Company Contacts.
WSP-3427 Client Enhancement to Transfer Employee to New Client Form A new mandatory field, To Benefit Group, now displays on the Transfer Employee to New Client form. For example: [Image: screenshot] You can use the To Benefit Group field to assign a benefit group to an employee when transferring to a new client. Note: The system prepopulates the To Benefit Group field if an employee has a benefit group from their old client that matches a benefit group in the new client. Also, if you select this field, the Select Benefit Groups list that displays contains only valid benefit groups for the destination client. For more information, see the in-product help.
PD-20013 Human Resources Enhancement to Approvals Processed Form Users who process an H/R Action approval that failed (Approval Status is “F”) now receive an email that provides the following information, which the system stores in the APPROVALS record: - Message Subject: <HR Action> Approval Error for Employee <employee> - Message Body: Due to a technical issue the <HR Action> for Employee <employee> will need to be resubmitted. Error: <include the error stored in the new field in the approval record>. For more information, see Reviewing Processed Approvals.
PD-23694 Human Resources Enhancement to Planned Time Off Requests Form When you mark an approved leave request as Paid on the Planned Time Off Requests form, the system now displays the updated warning message, “Marking an item Paid does not update the Employee Time Off Register. You will need to enter an Employee Absence Entry in order to update the Time Off Register. Do you wish to continue?” For more information, see Working with Planned Time Off Requests.
PD-14516 New Employee Import Enhancement to New Employee Import Form The New Employee Import form now supports an optional Benefit Salary field, allowing you to load this value during import so the system can calculate benefits eligibility and costs correctly without manual updates. > Note: Note the following: - The system does not import any value when the Benefit Salary field is left blank. - The system displays an error message, “Benefit Salary must be a numeric value,” when you enter a non‑numeric value in the Benefit Salary field. - The system displays the Benefit Salary field on the Pay tab of the Employee Details form when it imports a new employee with a Benefit Salary value. - The system stores the Benefit Salary field with the employee’s pay details and the Prism-Expanded Import file also includes the Benefit Salary field at the end of the file on the Import Field Mapping form. For more information, see Using the New Employee Import Dashboard (Batch Management).
WSP-3311, WSP-3312, WSP-3446 Payroll Enhancement to Payroll Options Form A new field, Delivery Method Override, now replaces the earlier Delivery Method on the Payroll Options form, which you can access by selecting Options from the Actions menu on the Payroll Control form. > Note: Note the following: - You can manually enter or choose a delivery method by selecting from the Select a Delivery Method dialog box. - The system tracks and maintains an audit for any changes that you make to the Delivery Method Override field. You can view the audit details by selecting Audit from the Actions menu on the Payroll Control form. - By default the system displays a null value in the Delivery Method Override field whenever you create a new payroll batch. - When you select Clone Last Batch from the Actions menu on Payroll Control form, the system copies the Delivery Method Override value from the selected batch into the new batch. - The payroll program logic is updated to improve the application of delivery sheets, allowing for a Delivery Method override on individual batch control. The system now logically assess delivery methods, prioritizing the new Delivery Method Override field on the Payroll Options form, followed by Location-specific Special Delivery, All Locations Special Delivery, the historical Delivery Method field, and finally, the Client Detail Delivery Method. This will ensure predictable and logical application of delivery sheets. - Additionally, the payroll program billing logic is updated to treat the new Delivery Method Override field on the Payroll Control form as a true override for the entire batch and when the override is set, no other delivery fees are applied. For more information, see the in-product help.
PD-20609, PD-20610, PD-20611, PD-20612, PD-20613, PD-20631, PD-20632, PD-20633, PD-20634, PD-20635, PD-20636, PD-20637, PD-20638, PD-20639, PD-20644, PD-20645, PD-20646, PD-23651, PD-23681, and PD-23718 Time Off PTO Terminology Update To ensure consistent naming conventions are used across the PrismHR platform, the legacy PTO terminology described below now aligns with the recently updated Time Off Workflow terminology. Note: In association with this terminology update, the PTO User Guide now displays as the Time Off User Guide. The following legacy PTO forms/reports have been renamed to reflect the updated Time Off Workflow terminology, as documented in the Client Administration Guide, Human Resources User Guide, Payroll Administration Guide, Payroll Reports guide, and the Time Off User Guide (formerly Paid Time Off User Guide): - Eligible PTO Hours Report = Eligible Time Off Hours Report - Eligible PTO Report = Eligible Time Off Report - Employee PTO Accruals Report = Employee Time Off Accruals Report - Employee PTO Detail Report = Employee Time Off Detail Report - Employee PTO Register Adjustment = Employee Time Off Register Adjustment - Employee PTO Register Inquiry = Employee Time Off Register Inquiry - Employee PTO Register = Employee Time Off Register - Employee PTO Summary = Employee Time Off Summary - Mass Archive Employee PTO Registers = Mass Archive Employee Time Off Registers - Mass Delete Employee PTO Registers = Mass Delete Employee Time Off Registers - Pay Period PTO Report = Pay Period Time Off Report - PTO Accrual Recalculation = Time Off Accrual Recalculation - PTO Approval Report = Time Off Approval Report - PTO Carryover Loss Report = Time Off Carryover Loss Report - PTO Hours Taken Report = Time Off Hours Taken Report - PTO Register Adjustment Import = Time Off Register Adjustment Import - PTO Register Enrollment = Time Off Register Enrollment Note: This adjustment was made in the breadcrumb paths, on-screen form names, global searches, menu structures, user role process descriptions, Work Centers (except for the Eligible Time Off Report and Employee Time Off Accruals Report forms), Related Actions Links, and in any error messages or warning messages that pertain to these legacy forms. The following legacy tab name was updated on the Employee Voucher form: - PTO = Time Off The following legacy field/option names were updated: - Absence Code = Time Off Pay - Benefit Plan = Time Off Plan - Class Description = Description - Display PTO Comments = Display Time Off Comments - No PTO Details are recorded for this employee = No Time Off Details are recorded for this employee - PTO Absence Code = Time Off Pay Code - PTO Absence Summary Detail Report = Time Off Absence Summary Detail Report - PTO Absence Summary Report by Department = Time Off Absence Summary Report by Department - PTO Absence Summary Report with Accrual Level = Time Off Absence Summary Report with Accrual Level - PTO Absence Summary Report with Accrual Level by Location = Time Off Absence Summary Report with Accrual Level by Location - PTO Absence Summary Report with Buyback = Time Off Absence Summary Report with Buyback - PTO Absence Summary Report with Buyback by Department = Time Off Absence Summary Report with Buyback by Department - PTO Absence Summary Report with Buyback by Location = Time Off Absence Summary Report with Buyback by Location - PTO Absence Summary Report with Buyback by Pay Group = Time Off Absence Summary Report with Buyback by Pay Group - PTO Benefit Plan = Time Off Plan - PTO Class = Time Off Type - PTO Code = Time Off Type - PTO Date = Time Off Date - PTO Detail = Time Off Detail - PTO Payroll Equivalent Report For Current Year = Time Off Payroll Equivalent Report For Current Year - PTO Payroll Equivalent Report For Previous Year = Time Off Payroll Equivalent Report For Previous Year - PTO Plan Delimiter = Time Off Plan - PTO Register Type = Accrual Schedule - PTO Start Date On Or After = Time Off Start Date On Or After - PTO Start Date On Or Before = Time Off Start Date On Or Before - PTO Status = Time Off Status - PTO Type = Accrual Schedule - PTO YTD Absence Report by Hours Used = Time Off YTD Absence Report by Hours Used - PTO YTD Detail Report = Time Off YTD Detail Report - Register Type = Accrual Schedule - Register Type Year End Date = Year End Date - Stop PTO Accruals = Stop Time Off Accruals - Trigger Method = Accrual Frequency For more information, see Performing an Employee Time Off Register Inquiry, Deleting Mass Employee Time Off Registers, Working with Planned Time Off Requests, Reviewing Time Off Tab Details, Processing Time Off Auto Register Enrollment, Adjusting Accrued or Carryover Hours for Employees, Archiving Mass Employee Time Off Registers, Recalculating Time Off Accruals, Importing Time Off Adjustment Information, Time Off Approval Report, Viewing Employee Time Off Register, Employee Time Off Detail Report, Time Off Hours Taken Report, Eligible Time Off Hours Report, Obtaining Time Off Carryover Loss for Employees, Employee Time Off Accruals Report, Employee Time Off Summary Report, Pay Period Time Off Report, and the Understanding Time Off Setup Workflow Process Terminology article on the CRC.
PD-23671 Work Centers Enhancement to Time Off Work Center In association with the PTO Terminology Update introduced in a previous release, PTO Reporting now displays as Time Off Reporting in the Time Off Work Center list. For example: [Image: screenshot] For more information, see Accessing Time Off Reporting Forms.
PP-1702 General Enhancement to COBRA Participant Record Form When searching for an enrollee on the COBRA Participant Record form, users can now choose to search for enrollees with a status date within a certain time frame. Simply select 30 days, 60 days, 90 days, or All in the Status Date Less than field to searching within that time frame. This enhancement improves performance of the search results, especially for companies with a large number of employees. For more information, see the in-app help.
PP-1964 General Enhancement to Organization Chart The Organization Chart now supports unlimited depth to improve downloading and printing options for the chart. In addition, the chart now features improved performance. For more information, see the in-app help.
PP-2572 General User Management Form Service Providers can now delegate PrismONE ID maintenance tasks to support representatives through the new User Management form. This form can be used to securely change user addresses and mobile numbers, send password reset messages, create temporary passwords, and set the user’s status. A new process ID, HRP.USERS*USER.MANAGEMENT.PRISMONE, is now available to grant access to this form. Security access to the User Management form is separate from other user security fields, so administrators can provide lower-tier support representatives with access to this form to safely delegate login support tasks. The User Management form can be accessed through the Actions menu on the Employee Details form. If a user hasn’t completed their PrismONE ID registration, the action item displays as User Management (Pending Registration). If the user does not have a PrismONE ID account or is missing a user record, a message displays on the form indicating which steps a user must take to complete registration. > Note: Note: Please review the in-app documentation for this form, the actions it provides, and the security implications before granting access to users. For more information, see the in-app help.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-3388 Previously, on the Employee Benefits Enrollment form, when you save a benefit enrollment record with Status as Eligible prior to completing the actual enrollment, the system created an enrollment reference record for that plan. Additionally, when the Benefits Enrollment Post process was run later, the system detected the enrollment reference record and interpreted it as an existing enrollment rather than a new one. Now, this is fixed. The process now checks for existing adjustments for the plan/period and only generates new adjustments when none exist, preventing missed first-time adjustments while still avoiding duplicate entries.
WSP-3445 Previously, on the Flexible Spending Accounts Reimbursement form, you could manually enter an Employee ID in the Employee field even if you did not have access to that employee. Now, this is fixed.
WSP-3895 During payroll processing, a system background process was incorrectly updating employee recurring deduction records even when no manual changes were made. These system-generated updates triggered the Employee Recurring Deductions Audit and appeared on the Employee Change Report as if deductions were being added or removed. Now, this is fixed.
WSP-4080 Previously, there was an issue where payroll calculation failed with a No Benefit Rule date found for coverage date error message when an employee’s benefit group with Life Insurance benefit plan was changed to a group whose Benefit Rules did not have an effective date on or before the employee’s original coverage start date. Now, this is fixed.

Compliance (CMP) Fixes

Jira # Issue Summary Resolution
CMP-3801 Previously, the Employee Misc Taxes recalculation utility in PrismHR was ignoring the selected employer filter on the Recalculate Taxes on Vouchers form and generated a report for all employers. Now, this is resolved.
CMP-7056 Previously, PrismHR did not calculate the Oregon (OR) Transit Tax (tax code 38-27) consistently on vouchers for all employees with a OR worksite location. Now, this is resolved.
CMP-7174 Previously, when creating tax adjustments or importing tax adjustments for employee‑paid tax deductions (for example tax codes 24‑40, 06‑40, 39‑22), the system did not honor the Adjust Client Register setting on the Tax Adjustments form. Instead, the Tax Basis defaulted to the tax code setup (for example tax codes configured to calculate/report at the client level), causing the Tax Basis on the employee payroll voucher to be set to “C” even when the adjustment was intended to be processed as “P”. Now, Tax Adjustments entry and Tax Adjustment Import have been updated to correctly honor the Adjust Client Register flag for employee‑paid tax codes and the Tax Basis on the employee payroll voucher reflects it correctly.
CMP-7817 Previously, for employer-paid local taxes such as NY County (-37) and Scranton, PA (-38), when an employee had “Other payments” (e.g., GTL) and was in a remote work state/location (WSL), PrismHR was applying an incorrect taxable limit. The tax was accrued but not billed correctly, causing mismatches between employer tax accruals and billed amounts on the billing voucher and invoice for taxable billing (with and without shelters). Now, this is resolved.
CMP-7850 Previously, in some cases in the PrismHR Quarterly Tax JSON Export the subject wage amount differed between the Client Report and the Employer Report for tax code 05-24. Now, this is resolved. The reports now display a consistent subject wage amount across both outputs.

Document Management (DM) Fixes

Jira # Issue Summary Resolution
DM-2131 When a user accessed Document Management from the Documents tab on the Employee Details form, the download option did not display. This is fixed.
DM-2138 When a user accessed Document Management from the Documents tab on the Employee Details form and attempted to upload documents, no document categories displayed. This is fixed.

Employee Portal (EP) Fixes

Jira # Issue Summary Resolution
EERT-3201 When multiple SSO hyperlinks were included in a custom widget, only the first hyperlink in the widget worked properly. Clicking on the other links produced an error. This is fixed.
EERT-3735 When a Worksite Manager viewed the My Employees form or the Paid Time Off form and reduced the size of the screen, some of the filter options were cut off and could not be selected. This is fixed.
EERT-3737 When managers viewed the Personal Info tab of the Employee Details form in Portal, the Birthdate (Age) field rounded up the employee’s age for some employees. This is fixed.
EERT-3752 When clients used a substitution variable for the employee’s position title, the title did not display with the proper case in the welcome email to the new employee. This is fixed.
EERT-3757 When an employee or service provider attempted to view the Pay History form or the Payroll Inquiry form and the hire date was missing on the employee record, an error occurred. This is fixed. A message now displays to the employee that their hire date information is missing, and that they must contact the service provider. Service providers can update the Original Hire Date field on the employee record.
EERT-3759 When a user entered line breaks in the Details field on the Client Events form in Prism, then viewed the client event in Employee Portal, the line breaks would not display properly. This is fixed.
EERT-3773 When employees attempted to access or download their pay vouchers in Employee Portal through certain browsers, an error occurred. This is fixed.
EP-10018 When employees clicked a link in Portal that was meant to single sign on (SSO) into another system, the system sometimes returned users to the Portal dashboard instead of sending them to the intended third‑party application. This is fixed. The SSO process now works even if they already have an active Portal session.
EP-10952 Clients who had not made selections on the “Employees Ability to Cancel PTO” toggle on the Configuration Template had the value default to False, when it should have defaulted to True. This is fixed.
EP-10980 When a manager viewed reports in Payroll History in Portal, some report types such as the PEO Client Accounting report did not display. This is fixed.

Identity and Access Management (IAM) Fixes

Jira # Issue Summary Resolution
IAM-2899 When a user logged in to Employee Portal and attempted to link their account with PrismONE ID or register for PrismONE ID, an error occurred. This is fixed.
IAM-2926 When a user attempted to reset their password, pressing the Enter key would disable the Submit button under certain circumstances. This is fixed.
IAM-2954 When a new user hadn’t completed PrismONE ID registration, the user could not reset their password in the system. This is fixed.

Onboarding (OB) Fixes

Jira # Issue Summary Resolution
EERT-3145 During Onboarding and Benefits Enrollment workflows, notifications were sent with a type that did not match the types allowed in Notification Template. This is fixed.
EERT-3750 When employees viewed the Employee Confirmation form during Benefits Enrollment, the Cost Basis displayed per period when it should display as per month. This is fixed.
EERT-3756 When clients set up a life insurance plan and set the GI Rounding Method field to round up to an increment, the Guaranteed Issue Limit on the plan rounded down instead. This is fixed. In addition, the GI Rounding Method field will now only allow valid rounding methods. For example, if the amounts are entered in thousands, only the rounding methods for thousandths can be selected. If an invalid selection is selected on a current plan, the Invalid text will display next to the selection, but the rounding method will still apply. Customers with AutoDecide selected should reselect a new rounding method.
EERT-3761 When a Group Benefit Plan had special characters in the plan name, the characters displayed with improper formatting on the Confirmation Statement. This is fixed.
EERT-3765 When a future-dated Benefit Group Change was scheduled for an employee, a Critical Illness as Life plan with Guaranteed Issue did display on Offer Type (CRL) during Benefit Enrollment. This is fixed.
EERT-3769 When a client attempted to load or edit Custom Forms for Onboarding that included inline images, an error occurred. This is fixed.
EERT-3807 During Benefit Enrollment, the system displayed the Per Period Cost incorrectly for the minimum Coverage Amount for life plans when using a salary multiplier. This is fixed.
EERT-3816 Life Events time notifications were not generating consistently. This is fixed.
OBE-10325 When Decision Support tools were enabled on the System Parameters form but disabled on the Client Details form, the Client Details setting took priority and disabled the Decision Support tools. This is fixed. The System Parameters setting now takes priority when determining if Decision Support tools should display.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
PD-20300 General Service providers who proxied in as a worksite trusted advisor were unable to view all employees that a worksite trusted advisor, who was a PTO Approver or Manager, was able to access when their data security was based on Manager Direct Reports, Manager Full Hierarchy, PTO Approver Direct Reports, or PTO Approver Full Hierarchy. Service providers who proxy in as a worksite trusted advisor are now able to view all employees that a worksite trusted advisor is able to access when their security is based on PTO Approver Direct Reports.
PD-20695 General The system displayed an employee’s election details on the Retirement Plan Enrollment form when that employee was enrolled in a retirement plan and then was transferred to another client who did not have a retirement plan using the Transfer Employee to New Client form. This is fixed.
PD-23736 General If a client was cloned from another client and the Client ID contained leading zeroes, saving or tabbing out of the Client ID field would drop the leading zeroes. For example, a Client ID of “001530” would become “1530”. This is fixed.
WSP-3910 General While using Remote Position Classification feature on the Positions form, the system did not correctly reflect the remote position classification for Position EEO Code and the FLSA Exempt on the Employee Details form. In the Employee Details form, the Position EEO Code and the FLSA Exempt status now correctly reflect the employee’s Remote Position Classification, if used, ensuring that remote roles display the appropriate Position EEO Code and Exempt/Non-Exempt flag instead of defaulting to the standard position classification.
WSP-4082 Payroll Previously, manual payroll batches were skipping the “ready to ship” stage in superbatch and disappeared instead. This is fixed. Manual payroll batches now remain on the Superbatch screen, and does not disappear once the “ready to ship” step is reached.
PD-20600 Payroll Loan deductions were taken from newer loans before older loans when there were insufficient gross wages to cover the deductions. This is fixed. Loan deductions are now taken from the older loans first in the order of the deduction sequences.
PD-20733 Payroll When clients chose to hide restricted invoices, users without permission to access all employees in a payroll batch could still infer the pay rates of restricted employees if they had access to all but one employee on the invoice. This is fixed. If a user does not have access to all employees on a payroll batch, the Invoice row is hidden to prevent them from inferring information about restricted employees. If the user has access to all employees on a payroll batch, the Invoice row displays normally.
PD-23625 Payroll When employees added to a payroll were part of a different pay group and only had Supplemental Pay Codes on the timesheet, the voucher did not calculate properly. Adding a Regular Pay type pay code with a value of 0 caused the voucher to calculate correctly. This is fixed. When an employee from a different pay group only has Supplemental Pay Codes on the timesheet, the voucher now calculates as expected.
PD-23725 Payroll When a payroll included a retroactive payment for a pay code that included a Shift Differential, the system calculated an incorrect negative amount, resulting in an incorrect deduction. This is fixed. Retroactive payments for shift differentials are now applied correctly to the payroll.
PP-2011 System When a user accessed a form that displayed a list of employees and ran a report on that form, the employee list could no longer be selected, and would sometimes no longer display. This is fixed.
PP-2013 System When a user first navigates to the Client Workflow grid on the Time Sheet Entry form, the custom height of the table caused it to overlap with the buttons used to save and finalize changes, preventing the user from saving changes properly. This is fixed.
PP-2534 System When an employee made entries on the Cafeteria Plan Contribution form, the first value entered in the Effective Date field did not save properly. This is fixed.
PP-2539 System When the approvals record for a prehire returned a null value, the Approvals form produced an error that locked the prehire record. This is fixed.
PP-2556 System When a user updated the Notes field for a change to the Client Details form, adding the reason for the change generated an audit log on the File Audit form. This is fixed.
PP-2560 System When a user who did not have access to view employee benefits accessed employee details on the Enhanced Dashboard, the employee could view the Employee Benefit Enrollments section of the At a Glance form on the dashboard and access information for individual employees. This is fixed. The Enhanced Dashboard now properly applies security permissions for employee benefits information. The employee must have access to the Employee Benefits Overview form to view benefits information on the chart.
PP-2567 System When a user accessed employee information on the Enhanced Dashboard, the Hire Date field sorted by month instead of by year. This is fixed.

========================================================================

April (R_202604)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/04/whatsnew-R_202604.htm Path: Release-Notes/2026/04/whatsnew-R_202604.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

PrismHR Release Highlights

The release highlights consist of the following enhancements, which consist of helpful updates to the current functionality and security improvements:

Release Highlights

Highlight — Description

PD-20300 — Service providers who proxied in as a worksite trusted advisor were unable to view all employees that a worksite trusted advisor, who was a PTO Approver or Manager, was able to access when their data security was based on Manager Direct Reports, Manager Full Hierarchy, PTO Approver Direct Reports, or PTO Approver Full Hierarchy.

Documentation Enhancements

Click a link to read about the documentation enhancements included in this release.

Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202605

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/05/Release-Notes-R_202605.htm Path: Release-Notes/2026/05/Release-Notes-R_202605.htm

Release Notes R_202605

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202605 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday May 28, 2026
Wave 2 Friday May 29, 2026
On-Premise Thursday June 4, 2026

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
RRT-6876 Enhancement to Retirement Plans Form A warning message now displays when you update an existing Deduction Code Override and click Save. A prompt displays asking you to acknowledge this update (click Yes to save the update). After clicking Yes, an on-screen report displays the affected employees, with each employee record, deduction type, and code change (original > updated), which requires you to once again confirm this update in the Retirement Plan and its downstream impacts to Recurring Deduction records: - Clicking Yes: Updates all associated records and provides a list of affected employee enrollments. Once updated, the corresponding Deduction Code displays on the Recurring Deductions form for each associated employee, which the system pulls into the payroll. - Clicking No: Does not update the Retirement Plan setup or the employee Recurring Deduction records. For more information, see the Setting Up Deductions and Bill Codes Overrides help topic.
WSP-3821, WSP-3887, WSP-3901 Enhancements to the Employee Benefit Overview Form The following enhancements now reside on the Employee Benefit Overview form: - The Employee Benefit Overview grid now displays a green highlighted outline on the row when you place your cursor on it, making it easier to track selections. [Image: screenshot] - The Coverage Level column under the Employee Benefit Overview grid now displays the Benefit Plan Type when you hover on the text. For example, if there is a benefit plan using the Group Benefit Plan Types, then the hover text displays the Type Code and Type Description (FAM - FAMILY). Similarly, for other benefit plans, the hover text displays the Coverage Amount (25,000.00). [Image: screenshot] - Under the Employee Benefit Overview grid, when you click a Plan ID, then the Employee Benefit Details modal form now displays the Plan Type as Type Code instead of Type Description. [Image: screenshot] For more information, see the Defining Cafeteria Plan Contributions help topic.
WSP-4059 Alternate processing when CFC is ON under certain conditions With this enhancement, if the employee’s status classification is not Terminated and the coverage end date falls on the last day of the month, the system now bypasses the legacy deduction stop-date logic and continues standard deduction processing. Deductions are spread normally through the final month of coverage, and no accelerated adjustment is created. For more information, see the in-app help.
WSP-2743 Changes to the Group Benefit Plans Form After you select a Benefit Plan with Insurance Class of Life Insurance, then under the Age Reduction Schedule section, a new field named Dependent Spouse Age Reduction has been added that allows you to include spouse age reduction behavior and schedule. [Image: screenshot] This field has the following drop-down option: - No - Use Employee Schedule - Separate Spouse Schedule When you select the Separate Spouse Schedule option, then the system displays a conditional dependent age reduction multi-value grid where you can add Age and Percentage of Full Coverage for spouse. For more information, see the Maintaining Coverage Amounts help topic.
WSP-2762, WSP-2763 Changes to the Employee Benefits Enrollment Form On the Employee Benefits Enrollment form, a new read-only field named Coverage Basis has been added under the Coverage Details section for Spouse. [Image: screenshot] This field is conditionally displayed when: - Spouse Coverage Basis is not equal to Spouse Coverage Amount. - Dependent Spouse Age Reduction field is set to Use Employee Schedule or Separate Spouse Schedule on the Group Benefit Plans form. The new attribute in the data mapping for EMPLOYEE.BEN.DETAIL for Spouse Coverage Basis will reflect the current Spouse coverage amounts as the Spouse Coverage Basis amount for new enrollments and existing Life Insurance records at the time of release. For more information, see the Manually Enrolling an Employee in a Benefit Plan help topic.
WSP-2764, WSP-2765 Enhancements to Coverage Detail with Spouse Age Reduction While creating an Employee Benefits Enrollment Detail record for an employee configured with Life Insurance plan for Spouse Age Reduction set as Use Employee Schedule, the system considers the following: - The system displays both the Spouse Coverage Basis and the reduced Spouse Coverage Amount in the Coverage Details section of the Employee Benefit Enrollment form. - If spouse coverage amount is entered then the Spouse Coverage Basis must be set equal to Spouse Coverage Amount. - If the spouse does not meet an age threshold for the reduction schedule and a Spousal Coverage Amount is entered, the Spouse Coverage Amount is stored as the initial coverage amount. - If the spouse meets age threshold for the reduction schedule and a Spousal Coverage Amount is entered, then: - the Spouse Coverage Basis is calculated to reflect the age reduction for the spouse’s age. For example, if spouse is 65 years and reduction to 80% is applied at 65, then for an election of $100,000, the calculated Coverage Basis is $125,000. - if an amount is entered that results in the coverage basis exceeding the Spouse Life Coverage End Amount then an error message is displayed. - While using the Benefits Import tool to import new Benefit Detail Record for Voluntary Life elections, if the Spouse Coverage Amount is imported and the spouse is at or above the first reduction age, then the Coverage Basis is calculated to reflect the appropriate reduction as defined on the plan setup. - If a plan is configured with Employee DOB for Spouse Life field enabled on the Group Benefit Plans form, then the above scenarios should use employee age instead of the Spouse age. Similarly, the system considers the above scenarios while creating an Employee Benefits Enrollment Detail record for an employee configured with Life Insurance plan for Spouse Age Reduction set as Separate Spouse Schedule. For more information, see the Manually Enrolling an Employee in a Benefit Plan help topic.
WSP-2768, WSP-2772, WSP-3352 Enhancement to Payroll Program to Detect Spouse Age Reduction Threshold The payroll process has now been enhanced so that, when a spouse covered under an employee life plan crosses a configured Dependent Spouse Age Reduction threshold, the system now automatically creates a new Life Insurance benefit detail record with the correct Effective Date and reduced coverage amount, using the existing employee age-reduction logic. Please note the following: - The above enhancement applies whether spouse age is calculated from spouse Date of Birth (DOB) or, when configured, from the employee DOB, and continues to respect plans where Dependent Spouse Age Reduction is set to No under the Age Reduction Schedule section on the Group Benefit Plans form. - The Voluntary Life premium calculations is also enhanced so that when a plan is configured to Reduce Coverage and Premium and Dependent Spouse Age Reduction is enabled with either Use Employee Schedule or Separate Spouse Schedule under the Age Reduction Schedule section on the Group Benefit Plans form, then the spouse premiums are reduced in line with the spouse coverage reduction for manual enrollments. - Additional enhancements to the Voluntary Life premium calculations include that when a plan is configured with Reduce Coverage and Premium and Dependent Spouse Age Reduction is enabled with either Use Employee Schedule or Separate Spouse Schedule under the Age Reduction Schedule section on the Group Benefit Plans form, then the spouse premiums are reduced in line with the spouse coverage amount. Please note that when Reduce Coverage and Premium is not selected, then the spouse premiums remain unreduced even when a spouse age reduction schedule is configured. For more information, see the Manually Enrolling an Employee in a Benefit Plan help topic.
WSP-3338 Changes to the Employee Benefits Enrollment Form On the Employee Benefits Enrollment form, under the Coverage Details section, a new tool-tip is added to the Age and Coverage Basis fields for Spouse if you select Dependent Spouse Age Reduction as Use Employee Schedule or Separate Spouse Schedule under the Age Reduction Schedule section on the Group Benefit Plans form. [Image: screenshot] [Image: screenshot] For more information, see the Manually Enrolling an Employee in a Benefit Plan help topic.
WSP-3975 Changes to the Slavic 401K Import Form On the Slavic 401K Import form, the import process is now updated to accept Post-Tax Elections (P) in the import file. Please note the following while importing new retirement plan elections on this form: - You can now import elections for Post Tax deferral types when Post Tax elections are not prohibited by the Retirement Plan setup. - You can now import elections for standard pre-tax deferrals when Employee Catch-up Deduction Code is flagged as prohibited. Please note that no Catch-up amount for pre-tax elections are recorded. - You can now import elections for Roth deferrals when Roth Catch-up Deduction Code is flagged as prohibited. Please note that Catch-up amount for Roth elections are recorded. - However, you cannot import elections for Post Tax deferral types when Post Tax elections are prohibited by the Retirement Plan setup. For more information, see the Performing Slavic 401K Imports help topic.
WSP-4013 Changes to the Benefit Plan Setup Form On the Benefit Plan Setup form, two new read-only fields, Insurance Class and Offer Type has now been added, which displays the information associated with the selected Benefit Plan. [Image: screenshot] Please note the following: - These two new fields are only displayed when you select Plan Class as Group Benefit. - The values displayed in these fields are the same that you enter on the Group Benefit Plans form. For more information, see the Setting Up a Benefit Plan help topic.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
WSP-3989 & WSP-3990 Changes to the Employee Garnishments form A new Federal Poverty Guideline field has been added to the Employee Garnishments form as you can see below. [Image: screenshot] - This field is optional. - This field is only available when configuring a State Tax Levy garnishment, allowing you to enter the Federal Poverty Guideline amount for the employee’s pay frequency. - The field accepts numeric values and rounds to two decimal places. When calculating garnishment withholdings for a State Tax Levy during payroll processing, the Federal Poverty Guideline (FPG), if present, is enforced to ensure that the garnishment is not withheld in excess of the employee’s Gross Wage - FPG amount. Note: There is a Known Issue regarding State Tax Levy wherein the subsequent Gross Pay is not always correctly adhering to the Garnishment Calculation Logic for the new Federal Poverty Guideline. This is expected to get fixed in the next 2026 June Release. For more information, see the in-product help or PrismHR Payroll Administration and Processing User Guide.
- This field is optional.
- This field is only available when configuring a State Tax Levy garnishment, allowing you to enter the Federal Poverty Guideline amount for the employee’s pay frequency.
- The field accepts numeric values and rounds to two decimal places.
WSP-3390 Enhanced Garnishment Capping Now Supports Daily Pay Schedules Previously, the Enhanced Garnishment Capping functionality did not handle “Daily” scheduled payroll batches. The Enhanced Garnishment Capping feature now correctly enforces weekly flat-amount garnishment caps for employees on daily pay schedules. The system now determines the workweek based on the Work Week Ends On setting (Pay Group takes priority; Client Details is used as a fallback) and cumulatively tracks garnishment deductions across all daily payroll runs within that workweek. Supported garnishment types include a flat amount Creditor Wage Garnishment, Child Support, Spousal Support or a State Tax Levy. If no Work Week Ends On value is configured, garnishment deductions will not be taken for daily-scheduled employees. This applies to both Legacy and Restartable payroll, and works across regular, manual, and special batches processed in any order within the same workweek. For more information, see the in-product help or PrismHR System Administration User Guide.
RRT-6863 Building the Wisconsin Download Use this form to create the electronic SUTA file for uploading data to the state of Wisconsin. > Note: Note: Client Access Group Security is enabled on this form. [Image: screenshot] To build the Wisconsin download: 1. On the Work Centers panel, select Tax > Quarterly Tax Processing > Government Exports >Quarterly SUTA Tax Processing (Client Reported)> Wisconsin 2. Complete these fields as required: In this field — Enter this Report Year — The year for the download. Quarter — The quarter for the download. Defaults to the previous quarter based on the current date. Client ID — Leave blank to select all clients or click the link to make a selection from the Select Client list. The list shows the Client ID, Client Name, Legal Name, Service Type, Employer, and Status. You can filter the list by Client ID or Client Name, Service Type, Status, or Employer. Close the window when finished. 3. Click Build. If errors occur, fix them and then rebuild the download. 4. Click Close when the process is complete to return to the Wisconsin page. 5. Click the Download link to download the file. For more information, see the in-product help or PrismHR Employer Administration User Guide.
1. On the Work Centers panel, select Tax > Quarterly Tax Processing > Government Exports >Quarterly SUTA Tax Processing (Client Reported)> Wisconsin
2. Complete these fields as required:
In this field Enter this
Report Year The year for the download.
Quarter The quarter for the download. Defaults to the previous quarter based on the current date.
Client ID Leave blank to select all clients or click the link to make a selection from the Select Client list. The list shows the Client ID, Client Name, Legal Name, Service Type, Employer, and Status. You can filter the list by Client ID or Client Name, Service Type, Status, or Employer. Close the window when finished.
3. Click Build. If errors occur, fix them and then rebuild the download.
4. Click Close when the process is complete to return to the Wisconsin page.
5. Click the Download link to download the file.
CMP-6863 Texas Employer Quarterly SUTA Tax Export supports ICESA The Employer Quarterly SUTA Tax Export (ICESA format) for the state of Texas has been updated to align with the new file specifications published by the Texas Workforce Commission (TWC) in preparation for the Texas Unemployment System (TxUS) launch on June 1, 2026. For full details on the new TxUS file specifications, refer to the TWC TxUS announcement. You fill find this option for the State Texas for File Format TEXAS [SUTA] on the Employer Quarterly SUTA Tax Export form. - The ICESA (Interstate Conference of Employment Security Agencies) export file layout has been restructured to match the updated TWC specifications, including revised field positions across multiple record types. - A Tax Contact Email address field has been added to the export, sourced from Employer / Change / Employer Details. - Employer Excess Wages (taxable overlimit wages) are now included in the file. - Record B has been removed from the file, as per the updated TWC requirements. - The CSV format option remains available for backwards compatibility. ### Details of the updates - Record A - Positions 2 - 5 filled w/ spaces - Positions 15 - 23 filled w/ spaces - Positions 208 - 247 Tax Contact email address, Left justified: use Employer / Change / Employer Details, Tax Contact Email - Positions 248 - 275 filled with spaces - Record B - removed - Record E - Moved Zip to positions 149 - 153 (currently starts in 154) - Moved ZiP ext to positions 154 -158 - Positions 159 - 166 filled w/ spaces - Positions 191 - 275 filled w/ spaces (current CR is at 209) - Record S - Positions 78 - 146 filled w/ spaces - Positions 162 - 211 filled w/ spaces - Record T - Positions 9 - 26 filled w/ spaces - Positions 41 - 54 ER Excess Wages (taxable overlimit wages) - Positions 69 -81 filled w / spaces - Positions 82 - 87 last month of the QTR and the Year - Positions 248 - 275 filled w/ spaces - Record F - Positions 13 - 40 filled w/ spaces - Positions 56 - 275 filled w/ spaces For more information, see the in-product help or PrismHR Employer Administration User Guide.
- The ICESA (Interstate Conference of Employment Security Agencies) export file layout has been restructured to match the updated TWC specifications, including revised field positions across multiple record types.
- A Tax Contact Email address field has been added to the export, sourced from Employer / Change / Employer Details.
- Employer Excess Wages (taxable overlimit wages) are now included in the file.
- Record B has been removed from the file, as per the updated TWC requirements.
- The CSV format option remains available for backwards compatibility.
- Record A
- Positions 2 - 5 filled w/ spaces
- Positions 15 - 23 filled w/ spaces
- Positions 208 - 247 Tax Contact email address, Left justified: use Employer / Change / Employer Details, Tax Contact Email
- Positions 248 - 275 filled with spaces
- Record B - removed
- Record E
- Moved Zip to positions 149 - 153 (currently starts in 154)
- Moved ZiP ext to positions 154 -158
- Positions 159 - 166 filled w/ spaces
- Positions 191 - 275 filled w/ spaces (current CR is at 209)
- Record S
- Positions 78 - 146 filled w/ spaces
- Positions 162 - 211 filled w/ spaces
- Record T
- Positions 9 - 26 filled w/ spaces
- Positions 41 - 54 ER Excess Wages (taxable overlimit wages)
- Positions 69 -81 filled w / spaces
- Positions 82 - 87 last month of the QTR and the Year
- Positions 248 - 275 filled w/ spaces
- Record F
- Positions 13 - 40 filled w/ spaces
- Positions 56 - 275 filled w/ spaces
CMP-6955 Changes to the Periodic Tax JSON Export form On this form, you now have the ability to “Limit to” or “Exclude From” multiple employers or clients instead of only one earlier. [Image: screenshot] All other functionalities remain unaltered. For more information, see the in-product help or PrismHR Employer Administration User Guide.
CMP-7797 Employer PFML Pickup Contribution Calculation The IRS released further guidance on the requirements of Revenue Ruling 2025-04. This ruling requires that when an employer voluntarily pays part of the employee’s required PFML contribution, this amount is treated as additional compensation to the employee. This requires that the excess contribution amounts are included in the employee’s gross income and wages for federal employment tax purposes. During our 2026 April release, we introduced the following two new fields without any functionality at that time: - On the System Parameters form, in the Global Codes Setup section, under the Benefits group, a new field named PFML ER Pickup Fringe Pay Code was added. - On the State Tax Rates (SUTA) form, in the Rate Breakdown section, a new field named PFML Employer Pickup was added. With this 2026 May release, PrismHR released new functionality to calculate the employer contribution amounts retroactively to 1/1/26. During payroll calculation, PrismHR uses your configured PFML Employer Pickup percentage for the state as defined on the State Tax Rates (SUTA) form and PFML ER Pickup Fringe Pay Code as defined on the System Parameters form to calculate the employer paid PFML amount and automatically posts it as a taxable non-cash fringe income to the employee’s payroll voucher under Other Payments, provided both values are valid. If either value is missing or invalid, no taxable fringe income is posted. The employer paid employee PFML amount is calculated as: (YTD net taxable) multiplied by (PFML ER Pick up Rate) minus (YTD PFML Fringe Pay) > Note: Note: The calculation does not include the PFML wages on the current voucher. For more information, see the in-product help or PrismHR Billing User Guide.
- On the System Parameters form, in the Global Codes Setup section, under the Benefits group, a new field named PFML ER Pickup Fringe Pay Code was added.
- On the State Tax Rates (SUTA) form, in the Rate Breakdown section, a new field named PFML Employer Pickup was added.
CMP-7810 Updates to the Quarterly Tax JSON Export The Quarterly Tax JSON Export now supports Michigan State Unemployment Insurance (SUI) tax (tax code 23-24). For both SBEA and non-SBEA clients, this JSON export now provides the following new state specific fields for the state of Michigan when reporting State Unemployment Insurance (SUI) tax: - Owner/Officer Indicator - Seasonal Employee Indicator For more information, see the in-product help or PrismHR System Administration User Guide.
- Owner/Officer Indicator
- Seasonal Employee Indicator
CMP-7815 Changes to the PrismHR Tax Client Setup Export form The following are the new options available on this form as you can see from the screenshot below: [Image: screenshot] \ Field Name \
Field Name Description
Date Range Select this option to limit the setup to a specific date range. Complete the following fields which will only display if you select this option: - Tax Date Start - Enter the starting tax date of the group of clients to be included in the client setup files. - Tax Date End - Enter the ending tax date of the group of clients to be included in the client setup files. > Note: Note: We suggest using a period that does not exceed a single quarter for each setup export.
- Tax Date Start - Enter the starting tax date of the group of clients to be included in the client setup files.
- Tax Date End - Enter the ending tax date of the group of clients to be included in the client setup files.
Limit To Client ID Select this option only if you want to limit the setup to certain clients. Complete the following fields which will only display if you select this option: - Client ID - Enter the Client IDs here or click the Client ID link and select them from the Select Clients list. - Client Name - This field auto-populates based on the input above.
- Client ID - Enter the Client IDs here or click the Client ID link and select them from the Select Clients list.
- Client Name - This field auto-populates based on the input above.
Limit To Employer ID Select this option only if you want to limit the setup to certain employers. Complete the following fields which will only display if you select this option: - Employer ID - Enter the Employer IDs here or click the Employer ID link and select them from the Select Employer list. - Employer Name - This field auto-populates based on the input above.
- Employer ID - Enter the Employer IDs here or click the Employer ID link and select them from the Select Employer list.
- Employer Name - This field auto-populates based on the input above.
CMP-7828 MasterTax v49 now supports NM Workers’ Compensation From April, 2026, the state of New Mexico introduced a separate reporting requirement for Workers’ Compensation Fee (NM0000-132). MasterTax v49 RTS 601 record now supports this as follows: - New Mexico Workers’ Compensation tax amounts from tax codes 32-23 and 32-26 are included in NM0000-132 and reported in the MasterTax v49 RTS 601 record in positions 100 - 113. - The existing MasterTax v49 RTS 601 record for New Mexico SUTA (tax code 32-24) reporting is not modified and continues to produce the same output as before this change. This update ensures MasterTax v49 compliance with the new state requirement by reporting New Mexico Workers’ Compensation tax amounts on its own dedicated record, distinct from New Mexico SUTA. For more information, see the in-product help or PrismHR Employer Administration User Guide.
- New Mexico Workers’ Compensation tax amounts from tax codes 32-23 and 32-26 are included in NM0000-132 and reported in the MasterTax v49 RTS 601 record in positions 100 - 113.
- The existing MasterTax v49 RTS 601 record for New Mexico SUTA (tax code 32-24) reporting is not modified and continues to produce the same output as before this change.

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-10051 Multifactor Authentication for Direct Deposit Service providers utilizing PrismONE ID can now enable multifactor authentication for the Direct Deposit form in Portal. This option can be selected on the Configuration Template form or the Client Override form when the Direct Deposit component is added to Portal. When an employee accesses the Direct Deposit form in Portal, the system prompts the employee for an Authenticator app code. Once the correct code is submitted, the employee is then navigated to the Direct Deposit form. Using this option, service providers can add an additional layer of security to the payment forms of their configuration templates and client overrides. For more information, refer to the in-app help.

Identity and Access Management (IAM) Enhancements

Ticket Description Summary Help Content
IAM-2748 PrismONE ID UEX Update The PrismONE forms have been updated with the PrismHR UEX style. These include the Registration, Sign In, Forgot Password, and My Settings forms, and include the following changes: - The show/hide feature for passwords now displays as an icon. - Required fields are now marked with an asterisk. - Buttons have been restyled to match the UEX standard. For more information, see the in-app help.
IAM-2894 Navigate to Administrator App from My Login Settings Administrators who have access to the System Administration console can now link to the app directly from the My Login Settings form. When the administrator accesses the form, the system checks their application permissions. If the user have access to the administrator console, the System Administration link displays, which can be used to access the console application. For more information, see the in-app help.

Onboarding (OB) Enhancements

Ticket Description Summary Help Content
OBE-9880 Disabled Notifications for Submitted Workflows Time Based Notifications now exclude employees who have submitted their workflows for Onboarding and Benefits Enrollment from receiving further reminder notifications. This update helps prevent confusion from employees sending in their workflows and still receiving reminders. This change affects current workflows on the Notification Templates form where the Trigger Type field is set to Time Based. Service Providers can set a template to retain the previous behavior of sending out reminders to all employees on the template by selecting the X Days before due date (include submitted) option in the Trigger Condition field for a template. By selecting this option, this template will continue sending reminder notifications to all employees at the specified number of days before the due date. For more information, refer to Notification Templates.
OBE-10352 Send Same-Day Notifications from Client Workflow Grid Service Providers can now send notifications directly from the Client Workflow Grid for open enrollment workflows matching certain criteria. A letter icon displays next to the line item to send the same-day notification when the following criteria are met: - The line item has an effective date. - An open enrollment workflow is present. - The OBE Start Date is set to today’s date or changed to today’s date. Click the letter icon to display a confirmation window, where the user can select to send notifications for the open enrollment workflow. Using this system, service providers can send notifications directly from the Client Workflow Grid without restarting the notification system or accessing any other forms. For more information, refer to Client Workflow Grid.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
PD-20340 Client Administration Enhancement to Projects Form The Other W/C Coverage In Place field only displays now if you enable specific custom suffix codes. For more information, see Maintaining Projects.
PD-23664 Human Resources Enhancement to Employee Details Form When you update the cell phone number in the Cell Phone field under the Employee Address tab on the Employee Details form, the system now automatically syncs the updated cell number to the Mobile Phone field for the corresponding user record on the Users form. This update applies to both standard and PrismONE ID User forms. For more information, see Establishing and Maintaining Employee Address Information.
PD-23709 Employer Administration Enhancement to Employer W/C Accrual Modifiers Form You can now view audit logs in the Employer W/C Accrual Modifiers form by selecting Audit on the Actions menu after entering or selecting the record. Note: An audit log is only available after modifying/saving the Discount/Debit or Modifier fields. For example: [Image: screenshot] For more information, see Setting Employer W/C Accrual Modifiers.
PD-23724 and PD-23829 Import Processing Enhancement to Data Import Tool A new import template, Third Party Sick Pay Adjustment, is now available in the Data Import Tool. You can use this import template to import third-party sick pay adjustments to create adjustment vouchers and client bill pendings for each record to reduce the amount of manual work required. For more information, see Importing Third Party Sick Pay Adjustments.
PD-23832 Import Processing Enhancement to Third Party Sick Pay Adjustment Form and Import Template The system now validates the following: - Whether the Employer on the Third Party Sick Pay Adjustment form is assigned to the Client or as an Alternate Employer for the Client: If not, an error message now displays, Invalid Employer ID,” and you cannot save the information in the form. - Whether the Employer ID in a row in the import file for the Third Party Sick Pay Adjustment import template is assigned to or is an Alternate Employer for the Client ID in the same row: If not, an error message now displays, “Must be a valid Employer ID for the client,” and the row does not import. For more information, see Adjusting Third Party Sick Pay Records and Importing Third Party Sick Pay Adjustments.
PD-23833 Import Processing Enhancement to Third Party Sick Pay Adjustment Form A link to the new Third Party Sick Pay Adjustment import template (see above) now displays on the Third Party Sick Pay Adjustment form. For example: [Image: screenshot] For more information, see Adjusting Third Party Sick Pay Records.
PD-23713 and PD-23714 Payroll Enhancement to Payroll Employer Tax Report Form The Payroll Employer Tax Report form now displays as Payroll Tax Report. Note: The system automatically displays the renamed form if you enter Payroll Employer Tax Report in the search box. In addition, a new field, Tax Type, now displays, so you can specify whether to view Both Employer & Employee, Employer Only, or Employee Only tax types in the report. (Selecting Employer Only or Employee Only is dependent on the associated option set in the Paid By field on the Tax Deductions form.) For example: [Image: screenshot] For more information, see Payroll Tax Report.
PP-1316 Payroll Enhancement to Export Email Information Notification emails for the Periodict Tax JSON Export form and MasterTax RTS File Build form now include information about the year of the build and any limits the Employers or Clients included in the build. For more information, see Periodic Tax JSON Export.
PP-2171 System Workflow Maintenance Row Highlights Row highlights have been added to improve the readability of the Search Results section on the Workflow Maintenance form. For more information, see the in-product help.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-3433 Previously, on the Slavic 401K Import form, when you performed the Slavic 401k Import process, the system incorrectly removed existing Post-Tax (non-Roth) elections when the Carry Forward Existing Amounts if NOT in the Import? field was enabled. Now, this is fixed.
WSP-4071 Previously, if you selected an employee and a benefit plan on the Employee Benefits Enrollment form and then canceled the selection by clicking the Cancel button, the Cafeteria Plan Contribution form remained accessible without an Employee ID, which was an incorrect behavior. Now, this is fixed. The Cafeteria Plan Contribution form on the Employee Benefits Enrollment screen now consistently requires a valid Employee ID before it can be accessed. If you do not provide a valid Employee ID, the system displays an error message.
WSP-4075 Previously, when an employee with a Life Insurance plan was configured with Calculate as of 1st month of employee’s birthday in the Age Calculation (Month/Day) field under the Age Parameters section of Group Benefit Plans form, the system displayed the spouse’s age incorrectly on the Employee Benefits Enrollment form while manually enrolling the employee. Now, this is fixed.

Compliance (CMP) Fixes

Jira # Issue Summary Resolution
CMP-7076 Previously, for both SBEA and non-SBEA clients, for employees in Guam, the system did not correctly report their federal income tax withholding for tax code 66-10 on the MasterTax RTS 601 record, if any for the quarter. Now, this is resolved.
CMP-7799 Previously, for employees who live and work in Martins Ferry, Ohio, and another location, and when Martins Ferry OH was entered as the second work location in the timesheet (with another state as the first location), the system did not calculate or withhold the Martins Ferry local tax. Now, this is resolved.
CMP-7809 Previously, in some instances, the Form W-2C did not report the updated information in the “Correct Information” columns for Box 18, 19 and 20. Now, this is resolved.
CMP-7845 Previously, CA pay data report was producing incorrect total numbers and establishment information. Now, this is resolved.
CMP-7849 Previously, in some cases, the Periodic JSON file was including payroll records that were included in a processed PTS which is incorrect resulting in over-reporting and wage discrepancies. Now, this is resolved.
CMP-7860 Previously, when an Employer PHR Tax ID override existed, the setup file both with and without tax journal records were ignoring the override. Now, when an Employer PHR Tax ID override exists, the setup file both with and without tax journal records correctly uses the following logic: - The PrismHR Tax Identifier Number is replaced with the Employer PHR Tax ID override. - The Override Employer Suffix Code is appended to the end since there is an override. - The override client ID reflects the Employer Override ID, Employer ID and the Override Employer Suffix Code. - The interface setting includes the PHR Tax ID based on configuration. When disabled, the Override ID only reports the Employer ID & Override Employer Suffix Code. When a new employer has no payroll data, the JSON setup creates a shell with the information available for that employer excluding the agency information.
Jira # Issue Summary Resolution
DM-2149 When users previewed documents in Document Management, the Print icon did not display. Users could still download the file and print it from their device, but could not print the document directly. This is fixed.

Employee Portal (EP) Fixes

Jira # Issue Summary Resolution
EERT-3770 When managers accessed the My Employees form in Portal, the Name field sometimes displayed as First Name, and no Last Name field displayed. This is fixed.
EERT-3776 When a user opened their California W4 form, the employee’s tax ID did not prefill properly onto the form. This is fixed.
EERT-3805 When an employee attempted to register for Portal via their Onboarding email link, an error occurred. This is fixed.
EERT-3839 The system temporarily locked certain records for extended periods, which prevented updates and blocked downstream operation. This is fixed.
EP-11032 When a manager user viewed the Portal dashboard, the Recently Viewed section of the My Employees widget did not display photos of the employees. This is fixed.
EP-11038 When some employees attempted to download their pay stub, the process took long enough for the request to time out, preventing the download. This is fixed.
EP-11079 When an employee with a worksite location in California selected to have an emergency contact notified if they were detained, the flag for this option did not display for the employee’s manager. This is fixed.

Identity and Access Management (IAM) Fixes

Jira # Issue Summary Resolution
IAM-2968 When a user registered for PrismONE and entered a Mobile field number, the country code did not populate properly. If the user entered the country code manually, the process would stall, and the user could not complete registration. This is fixed.

Onboarding (OB) Fixes

Jira # Issue Summary Resolution
EERT-3101 When a user created a business rule for a client, that rule required a Client ID as a rule, but the user could remove the Client ID as a requirement. This is fixed.
EERT-3739 When a user was enrolled in a Family-Rated Age-Banded Medical Plan and a Life Event should have prompted them with an option to unenroll in the plan, the medical form for un-enrollment did not display properly on the life event. This is fixed.
EERT-3744 When a new hire’s Hire Date took place before the Benefit Enrollment Plan Detail Effective Date, the employee would see the default terms and conditions when viewing the Benefit Summary Form instead of the client’s customized terms and conditions. This is fixed.
EERT-3767 When an employee viewed the Benefit Summary form during benefits enrollment, the HSA Employer Contribution amount did not display correctly. This is fixed.
EERT-3774 When the tax forms page was configured to hide the navigation header, the My Progress sidebar did not display properly and had text cut off. This is fixed.
EERT-3775 When an employee attempted to access their Benefits Enrollment via Portal, an error occurred. This is fixed.
EERT-3776 When a user opened their California W4 form, the employee’s tax ID did not prefill properly onto the form. This is fixed.
EERT-3782 When a user viewed the Benefits Enrollment Detail form for an employee, the employee’s beneficiaries did not display properly on the form. This is fixed.
EERT-3807 During Benefit Enrollment, the system displayed the Per Period Cost incorrectly for the minimum Coverage Amount for life plans when using a salary multiplier. This is fixed.
EERT-3816 Life Events time notifications were not generating consistently. This is fixed.
OBE-10335 When a disabled Decision Support tool was set to Enabled for a client, the DEC form did not display when an employee accessed their benefits workflow. This is fixed.
OBE-10393 Automatic Open Enrollment did not launch properly for clients. Clients could fix the problem manually by restarting the Notification Control Panel by resetting the OE Notify date, stopping the process, saving, and starting the process again. This is fixed. The Automatic Open Enrollment now launch properly without the clients having to manually reset the process.
OBE-10402 When the same-day feature was enabled for Notifications in Onboarding and Benefits Enrollment, noneligible employees erroneously received notifications. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
PD-20353 General The system incorrectly displayed “Paid” on the Planned Time Off form for the current voucher for leave requests that were approved after payroll calculation, even though those hours were not present on the voucher or the Employee Time Off Register form. The following now occurs: - Only leave requests included in the payroll/voucher are marked as “Paid” on the Planned Time Off form. - Leave requests approved after payroll calculation remain in “Approved” status. - The Employee Time Off Register only reflects time off that was actually paid.
- Only leave requests included in the payroll/voucher are marked as “Paid” on the Planned Time Off form.
- Leave requests approved after payroll calculation remain in “Approved” status.
- The Employee Time Off Register only reflects time off that was actually paid.
PP-2566 General When a user changed the size of the Enhanced Dashboard, the dashboard reloaded. This is fixed.
PP-2574 General When a user selected the View All Employees option on the Enhanced Dashboard, the columns would no longer sort when selected. This is fixed.
RRT-6935 General When the system routed an HR-action approval (such as a Leave Request, Pay Rate Change, or Termination) to an assigned approver (Manager/PTO Approver) and that approver is later teminated and the pending approval was not reassigned, the approval became “orphaned.” (A nightly batch auto-processed it and, on failure, emailed a notification to an arbitrary, cross-client user who had no access to that employee.) The system no longer sends orphaned-approval “failure/resubmit” emails and now processes orphaned approvals.
WSP-3987 General When users ran the Clone Client process with the Retirement Plan Setup field disabled, the system created retirement plans for the new client on the Benefits tab in the Client Details form without setting up the Retirement Plans on the Benefit Plan Setup form. This is fixed.
PD-20083 Payroll In the Workers’ Compensation -Wage Detail Report, the system reported Expense Reimbursement Pay Class payments as Exempt Wages for every WC Code, regardless of under which position it was paid. Pay Codes that are not subject to workers compensation are only reported under Exempt Wages for the WC Code of the position under which it was paid.
PD-20400 Payroll The system did not enable the Suppress Allocation field correctly when users imported a batch payment file on the Batch Payments form. For example, if users set the Suppress Allocation field to Yes, the system set this field to No after processing the import. This is fixed.
PD-20544 Payroll An error message displayed when users selected an employee in the Employee ID field on the Time Sheet Entry form and then clicked the down arrow intermittently, “This is the last employee on the list,” even though additional employees were still available in the payroll. Users can now navigate successfully through the employees list without triggering the incorrect “last employee” error message.
PD-23669 Payroll When a manager approved PTO for multiple employees and processed a payroll to pay only a group of those employees, all employees with approved PTO would display their PTO as paid on the Planned Time Off Requests form. This is fixed.
PD-23717 Payroll When a salaried employee entered leave hours (for example, Time Off or Holiday), the system did not reduce their regular (REG) hours accordingly in the timesheet on the Time Sheet Entry form. Instead, the reduction calculation was performed incorrectly, especially when multiple pay codes with different rate classes (“Straight” versus “Other”) were involved. This is fixed.
PD-23767 Payroll When a client suppressed the Client Approval for a reverse wire client in the SuperBatch form, the system did not update the wire file during ACH processing. This is fixed.
PP-1783 Payroll When a user sorted the Timesheet Report by the Pay Code field, the Grand Totals field would sometimes not display. This is fixed.
PP-2544 Payroll When a user created a new Service Provider user record and added Payroll Representative in the Account Management Roles section, the Suppress Payroll Warnings section displayed under the User Roles section instead of under the Account Management Roles section. This is fixed.
PP-2568 Payroll When a user cleared selections on the Pay Period Accrual Thresholds section of the Time Off Plans form, selected a Pay Period again, and entered an accrual threshold, the Pay Period field would revert back to the default Select state. This is fixed.
RRT-6846 Payroll When an employee had multiple loans being deducted in one payroll and the employee had Supplemental Pay in that payroll, the system made a deduction for a loan that was fully paid on the Regular voucher in the same payroll, which caused an over-deduction for the loan total. This is fixed.
WSP-3927 Payroll Users were able to add a code to multiple columns in the Client Allocation Formats form. An error message now displays when users try to add a code to multiple columns, “Allocation Code cannot be used more than once in the report columns.”
WSP-4336 Payroll The system did not post the deduction import amounts in the Time Sheet Deduction Import form for all employees in the import. In addition, the payroll vouchers posted these values as a lesser amount, with the decimal point over-adjusted two places to the left. This is fixed.
PP-2522 System On the Time Off Auto-Enrollment Rules Import form, the section border at the top of the form displayed incorrectly. This is fixed.
PP-2543 System When a user created a user record on the PrismONE Users form and selected a User Type, an erroneous entry “HRP OB/BE Administrator” displayed as a User Type option. This is fixed.
PP-2547 System When the record for a PrismONE ID user was completed and saved, the system would still display PrismONE ID selections on the blank Users form. This is fixed.
PP-2548 System When a user created a new DUC user record and filled out fields on the PrismONE Users form, resizing the browser window changed the Registration Status to Pending. This is fixed.
PP-2549 System When a DUC user resized the screen on the PrismONE Users form, the User ID field, Employee fields, and Current Access section disappeared, and the User Type menu displayed. This is fixed.
PP-2550 System When a DUC user accessed the Password and Recovery form and clicked No on the Save message, the Password and Recovery section disappeared. This is fixed.
PP-2551 System When a DUC user attempted to select fields on the Users form with the tab key, the fields were not selected in sequential order. This is fixed.
PP-2553 System When a user opened the browser dev tools while viewing the Users form, several fields on the Users form disappeared. This is fixed.
PP-2582 System In the File Audit, the After Value field in a Discount/Debit Amount did not display a decimal point. This is fixed.
PP-2592 System When a user received a PrismONE registration code, the expiration time for the code was set to four hours instead of the time set in the system configuration settings. This is fixed.
PP-2598 System When an administrator viewed an existing, non-PrismONE User ID on the PrismONE Users form and entered an email address to initiate the PrismONE ID registration process, the Save button was not enabled properly. This is fixed.

========================================================================

May (R_202605)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/05/whatsnew-R_202605.htm Path: Release-Notes/2026/05/whatsnew-R_202605.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

New Features

We would like to bring your attention to the following list of new features for PrismHR.

List of New Features

Click a link to display the detailed release notes for the new feature

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202606

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/06/Release-Notes-R_202606.htm Path: Release-Notes/2026/06/Release-Notes-R_202606.htm

Release Notes R_202606

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202606 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday June 25, 2026
Wave 2 Friday June 26, 2026
On-Premise Thursday July 2, 2026

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-3926, WSP-3968, WSP-3969, WSP-3978 Enhancements to the Participant ID selector New Filters and Columns have now been added to the Participant ID selector on the following forms for better user experience: - COBRA Participant Record - COBRA Participant History Record - COBRA Transaction Entry - Generate / Print COBRA Payment Coupons [Image: screenshot] The newly added Filters and Columns are: - Enrollee Type - Assists with identifying whether the participant is an Employee or Dependent. If you select an Employee, the no message is displayed below the Participant ID field indicating that the Enrollee selected is an Employee. - Client ID - All the clients are displayed by default. However, you can select the Client IDs with a COBRA Participant Record associated with them. - COBRA Status - Indicates the COBRA Status assigned to the COBRA Participant Record. - Qualifying Event - All is displayed by default. For more information, see the Maintaining COBRA Participant Records help topic.
WSP-3967 Changes to the COBRA Participant Record Form When you select a Participant ID, then under the COBRA Participant Record section, a new drop-down menu, Or Use has been added with additional address options to the right of the Billing Address field. [Image: screenshot] For more information, see the Maintaining COBRA Participant Records help topic.
WSP-3977 Enhancements to the Enrollee ID selector New Filters and Columns have now been added to the Enrollee ID selector on the following form for better user experience: - Generate / Post COBRA Invoices [Image: screenshot] The newly added Filters and Columns are: - Enrollee Type - Assists with identifying whether the participant is an Employee or Dependent. - Client ID - All the clients are displayed by default. However, you can select the Client IDs with a COBRA Participant Record associated with them. - COBRA Status - Indicates the COBRA Status assigned to the COBRA Participant Record. - Qualifying Event - All is displayed by default. For more information, see the Generate / Post COBRA Invoices help topic.
WSP-4143, WSP-4144, WSP-4145, WSP-4146, WSP-4147 Transition To Single Selector ### Retirement Plan field on the Retirement Match Rules form In order to provide a consistent and contextual customer experience on the Retirement Match Rules form, we have changed the Retirement Plan drop-down to a selector on this form. [Image: screenshot] - You can enter a Plan ID or Name to narrow down the search. - This selector has the following columns: - Plan ID - Plan Name - Plan Status - You can click on any column header in the list, for example, Plan ID or Plan Name and so on to sort the list accordingly. - You can click the Reset Search and Filters button to reset the search results. ### Plan ID field on the Employee Retirement Plan Register form In order to provide a consistent and contextual customer experience on the Employee Retirement Plan Register form, we have changed the Plan ID drop-down to a selector on this form. [Image: screenshot] - You can enter a Plan ID or Name to narrow down the search. - This selector has the following columns: - Plan ID - Plan Name - Plan Status - You can click on any column header in the list, for example, Plan ID or Plan Name and so on to sort the list accordingly. - You can click the Reset Search and Filters button to reset the search results. ### Benefit Plan field on the Employee Benefit Rule Overrides form In order to provide a consistent and contextual customer experience on the Employee Benefit Rule Overrides form, we have changed the Benefit Plan drop-down to a selector on this form. [Image: screenshot] - You can enter a Benefit Plan ID or Name to narrow down the search. - This selector has the following filters: - Insurance Class - High Deductible Plan (HDHP) - Terminated - Offer Type - Payee ID - This selector has the following columns: - Plan ID - Plan Name - Insurance Class - Offer Type - HDHP - Payee ID - Termination Date - You can click on any column header in the list, for example, Benefit Plan ID or Name and so on to sort the list accordingly. - You can click the Reset Search and Filters button to reset the search results. ### Filter By Plan field on the Benefit Adjustments form In order to provide a consistent and contextual customer experience on the Benefit Adjustments form, we have changed the Filter By Plan drop-down to a selector on this form. [Image: screenshot] - You can enter a Benefit Plan ID or Name to narrow down the search. - This selector has the following filters: - Insurance Class - High Deductible Plan (HDHP) - Terminated - Offer Type - Payee ID - This selector has the following columns: - Plan ID - Plan Name - Insurance Class - Offer Type - HDHP - Payee ID - Termination Date - You can click on any column header in the list, for example, Benefit Plan ID or Name and so on to sort the list accordingly. - You can click the Reset Search and Filters button to reset the search results. ### Benefit Plan field on the Benefit Rules form In order to provide a consistent and contextual customer experience on the Benefit Rules form, we have changed the Benefit Plan drop-down to a selector on this form. [Image: screenshot] - You can enter a Benefit Plan ID or Name to narrow down the search. - This selector has the following filters: - Insurance Class - High Deductible Plan (HDHP) - Terminated - Offer Type - Payee ID - This selector has the following columns: - Plan ID - Plan Name - Insurance Class - Offer Type - HDHP - Payee ID - Termination Date - You can click on any column header in the list, for example, Benefit Plan ID or Name and so on to sort the list accordingly. - You can click the Reset Search and Filters button to reset the search results. For more information, see the in-app help.
WSP-4205, WSP-4213, WSP-4222, WSP-4224 Enhancements to the Employee Benefit Overview form The following enhancements now reside on the Employee Benefit Overview form: - On the Employee Benefit Overview form, after you select an employee, then under the Employee Benefit Overview table, a new column, Pending Ben Adj is now added. - The column displays the pending benefit adjustments count. - If the column has a value greater than 0, then a hyperlink is available. Click the count hyperlink to open the Benefit Adjustments modal form with the selected Benefit Plan prepopulated in the Filter By Plan field. [Image: screenshot] - On the Employee Benefit Overview form, a new read-only field, Benefit Group is now added which displays the as of date value. [Image: screenshot] - The FLSA Exempt field now does not display any value if you do not select an Employee ID or click the Cancel button. - On the Employee Benefit Overview form, after you select an employee, then under the Employee Benefit Overview table, a new column, Employer Contribution is now added. The value displayed in the Employer Contribution is the same value that is displayed for the Employer Contribution under the Monthly column on the Employee Benefits Enrollment form. Additionally, the earlier Contribution column is now renamed to Employee Contribution. [Image: screenshot] For more information, see the Displaying an Employee’s Benefit Plans help topic.
WSP-4263 Changes to the Client Benefits Overview form On the Client Benefits Overview form, the Plan ID column is now widened to display up to 20 characters, reducing the need to hover over truncated values. [Image: screenshot] For more information, see the in-app help.
WSP-3309, WSP-4279 Changes to the Employee Retirement Plan Register form On the Employee Retirement Plan Register form, the earlier pie charts have now been replaced with interactive bar charts to visualize employee earnings, contributions, and employer contributions against applicable IRS limits. Once you select an Employee ID, Plan ID, and Plan Year, then the new bar charts displays Year-to-Date totals up to four charts: - 401K Earnings vs. Annual Compensation - Employee Contributions - HPE Employee Contributions - It is displayed only for HPE employees only - Total EE & ER Contributions Each chart displays actual values alongside the applicable limit. You can hover over a section to view the detailed breakdown of all contribution types and totals. Selecting any bar opens a detail view with an itemized chart and access to the underlying voucher list. [Image: screenshot] For more information, see the Displaying Employee Retirement Plan Totals help topic.
WSP-3988 Enhancement to ROTH Deferral Catch-Up Rollover ROTH deferral amounts exceeding the deferral limit now correctly rolls over to ROTH Catch-Up on the payroll where the limit is hit. This is now consistent with the existing Pre-Tax Catch-Up rollover behavior. For more information, see the in-app help.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
CMP-6799 Enhanced Additional Medicare Reporting in RTS for U.S. Territories Previously, when a US territory employee’s Medicare wages exceeded $200,000, the Additional Medicare amounts were included within the standard US territory Medicare record rather than being broken out into a separate line — requiring manual adjustments in MasterTax. Now, when processing payroll for employees in Guam, the Virgin Islands, or with AG/W8 classifications, you will no longer need to manually adjust Additional Medicare amounts in MasterTax. The Reconciliation Tax Summary (RTS) file in MasterTax is now fully compliant for high-income US territory employees. ### What changed? - Territory-specific Additional Medicare records — The system now generates dedicated Additional Medicare records for applicable US territories and worker classifications: - 00-11GUADD — Guam - 00-11VIADD — Virgin Islands - 00-01AGADD — Agricultural workers (American Samoa) - 00-11W8ADD — W8 employees - Consistent with federal reporting — US Territory Additional Medicare reporting now mirrors the standard federal Medicare / Additional Medicare structure (codes 00-11 and 00-11ADD), ensuring a uniform approach across all employee classifications.
- Territory-specific Additional Medicare records — The system now generates dedicated Additional Medicare records for applicable US territories and worker classifications:
- 00-11GUADD — Guam
- 00-11VIADD — Virgin Islands
- 00-01AGADD — Agricultural workers (American Samoa)
- 00-11W8ADD — W8 employees
- Consistent with federal reporting — US Territory Additional Medicare reporting now mirrors the standard federal Medicare / Additional Medicare structure (codes 00-11 and 00-11ADD), ensuring a uniform approach across all employee classifications.
CMP-7176 MA PFML Employee State Specific Fields Added to Quarterly Tax JSON Export The Quarterly Tax JSON Export now includes State Specific Information within the Employee Wage Details for the Massachusetts Paid Family & Medical Leave (MA PFML tax code 22-40), as required by the APTM V5.1 file specification. When a quarterly unemployment filing includes the MA PFML Employee tax code, the JSON export will now populate a StateSpecificInformation object under the EmployeeWageDetails array containing: - Family Leave Contribution Rate — A 3-character numeric string (left zero-filled, range 0–100) representing the employee’s percentage share of the total Family contribution rate of 0.18%. For example, if the employee contributes the full 0.18%, the value is 100; if split equally with the employer, the value is 050. - Medical Leave Contribution Rate — A 2-character numeric string (left zero-filled, range 0–40) representing the employee’s percentage share of the total medical contribution rate of 0.70%. For example, if the employee contributes the maximum 40% (0.28%), the value is 40; if the employer covers the full amount, the value is 00. These rates are calculated per employee based on actual withholdings relative to the applicable state rule form rates for the quarter and apply to both SBEA and Non-SBEA clients.
- Family Leave Contribution Rate — A 3-character numeric string (left zero-filled, range 0–100) representing the employee’s percentage share of the total Family contribution rate of 0.18%. For example, if the employee contributes the full 0.18%, the value is 100; if split equally with the employer, the value is 050.
- Medical Leave Contribution Rate — A 2-character numeric string (left zero-filled, range 0–40) representing the employee’s percentage share of the total medical contribution rate of 0.70%. For example, if the employee contributes the maximum 40% (0.28%), the value is 40; if the employer covers the full amount, the value is 00.
CMP-7793 & CMP-7794 Changes to the Employee Tax Form The system now supports dedicated fields for capturing employee visa classifications and their associated pay date ranges, ensuring tax rules are applied accurately based on an employee’s eligibility period. On the Employee Details form, on the Tax tab, under the Federal Tax Filing section, three new fields have been added. See from the screenshot below. [Image: screenshot] - Eligible Visa Category - Select one of the applicable eligible visa categories from the following drop-down. If you select any option other than –Select–, you will have to enter a Visa Starting Pay Date and a Visa Ending Pay Date. - –Select– - Select this option if there is no eligible visa category to be applied - F-1 Student - J-1 Student - J-1 Scholar - H-2A Agricultural Worker - Visa Starting Pay Date - Enter the visa starting pay date for the selected eligible visa category above. This date cannot be later than the Visa Ending Pay Date. You cannot enter this date unless you have selected an eligible visa category above. If you have selected an eligible visa category above, you must enter this field. - Visa Ending Pay Date - Enter the visa ending pay date for the selected eligible visa category above. This date cannot be earlier than the Visa Starting Pay Date. You cannot enter this date unless you have selected an eligible visa category above. If you have selected an eligible visa category above, you must enter this field. ### Automated FICA and FUTA Tax Suppression for Eligible Visa Holders The payroll system now automatically suppresses FICA and FUTA taxes for employees with eligible visa types when the pay date falls within their defined eligibility period. This enhancement ensures tax compliance by automating exemptions that previously required manual oversight or were limited to FICA only. #### Key Details - Automated Tax Suppression: When an employee has an eligible visa type and the payroll check date falls on or between the visa’s start and end dates, the system will fully suppress FICA (Employee and Employer) and FUTA taxes. - Full Suppression vs. Blocking: Unlike “blocked” taxes, this logic entirely suppresses the tax codes and taxable wages, meaning they will not appear on the payroll voucher. - Standard Processing: If the payroll check date falls outside the eligibility range, or if a visa type is selected without defined dates, FICA and FUTA taxes will be withheld as usual. - Broad Compatibility: This logic applies to various payroll processes, including backdated or future-dated payrolls and different batch types, for both certified and non-certified employers. > Note: Note: - This feature is currently supported by the restartable payroll engine. - Retroactive adjustments are not automated; if a visa flag or eligibility dates are updated after a payroll is finalized, manual adjustments may be required for previous pay periods.
- Eligible Visa Category - Select one of the applicable eligible visa categories from the following drop-down. If you select any option other than –Select–, you will have to enter a Visa Starting Pay Date and a Visa Ending Pay Date.
- –Select– - Select this option if there is no eligible visa category to be applied
- F-1 Student
- J-1 Student
- J-1 Scholar
- H-2A Agricultural Worker
- Visa Starting Pay Date - Enter the visa starting pay date for the selected eligible visa category above. This date cannot be later than the Visa Ending Pay Date. You cannot enter this date unless you have selected an eligible visa category above. If you have selected an eligible visa category above, you must enter this field.
- Visa Ending Pay Date - Enter the visa ending pay date for the selected eligible visa category above. This date cannot be earlier than the Visa Starting Pay Date. You cannot enter this date unless you have selected an eligible visa category above. If you have selected an eligible visa category above, you must enter this field.
- Automated Tax Suppression: When an employee has an eligible visa type and the payroll check date falls on or between the visa’s start and end dates, the system will fully suppress FICA (Employee and Employer) and FUTA taxes.
- Full Suppression vs. Blocking: Unlike “blocked” taxes, this logic entirely suppresses the tax codes and taxable wages, meaning they will not appear on the payroll voucher.
- Standard Processing: If the payroll check date falls outside the eligibility range, or if a visa type is selected without defined dates, FICA and FUTA taxes will be withheld as usual.
- Broad Compatibility: This logic applies to various payroll processes, including backdated or future-dated payrolls and different batch types, for both certified and non-certified employers.
- This feature is currently supported by the restartable payroll engine.
- Retroactive adjustments are not automated; if a visa flag or eligibility dates are updated after a payroll is finalized, manual adjustments may be required for previous pay periods.
CMP-7814 Changes to Resident PSD code reporting for Pennsylvania employees Previously, when an employee worked in the state of Pennsylvania but lived in another state, we used to leave the Resident PSD code field blank in the Periodic Tax JSON Export and the Quarterly Tax JSON Export. We had to manually enter 880000 for the ResidentPSDCode field in the json file for these during the quarter end processes. Now, when an employee works in the state of Pennsylvania but lives in another state, in both the Periodic Tax JSON Export and the Quarterly Tax JSON Export, the ResidentPSDCode field in the JSON file will report 880000. No manual intervention will be required.
CMP-7865 Changes to the Client Quarterly SUTA Tax Export - Kentucky Kentucky’s Unemployment Insurance Portal (KUIP) requires quarterly wage and tax files to be submitted in ICESA fixed-length format. Accordingly, we have updated our Client Quarterly SUTA Tax Export for Kentucky so that the produced file meets KUIP’s ICESA requirements, including record length, field positioning, padding/justification rules, and validation expectations. KUIP processes only: - E-Record – Employer Header Record - S-Record – Employee Detail Record Any other record types (A, B, T, F, etc.) are disregarded by KUIP. File Specification (from “Kentucky Unemployment Insurance Portal (KUIP) ICESA File Format Reference Guide”) General File Specifications - File Extension: .txt only. - Record Length: Each record (line) must be exactly 275 characters (including trailing spaces). - Format: Fixed-length ICESA. - Only E and S records are produced for the KUIP ICESA export - KEIN = Client Details, KY - State Unemployment Insurance ID - Use Worksite Location, Worksite ID from employee’s assigned Worksite Location - Population rule: All fields must be populated to their exact length using spaces and/or zero-fill as specified. - Left-justify where specified; pad with spaces. - Right-justify where specified; pad with spaces or zeroes per specification.
- E-Record – Employer Header Record
- S-Record – Employee Detail Record
- File Extension: .txt only.
- Record Length: Each record (line) must be exactly 275 characters (including trailing spaces).
- Format: Fixed-length ICESA.
- Only E and S records are produced for the KUIP ICESA export
- KEIN = Client Details, KY - State Unemployment Insurance ID
- Use Worksite Location, Worksite ID from employee’s assigned Worksite Location
- Population rule: All fields must be populated to their exact length using spaces and/or zero-fill as specified.
- Left-justify where specified; pad with spaces.
- Right-justify where specified; pad with spaces or zeroes per specification.
CMP-7871 Changes to the Employer Quarterly SUTA Tax Export - Kentucky Kentucky’s Unemployment Insurance Portal (KUIP) requires quarterly wage and tax files to be submitted in ICESA fixed-length format. Accordingly, we have updated our Employer Quarterly SUTA Tax Export for Kentucky so that the produced file meets KUIP’s ICESA requirements, including record length, field positioning, padding/justification rules, and validation expectations. KUIP processes only: - E-Record – Employer Header Record - S-Record – Employee Detail Record Any other record types (A, B, T, F, etc.) are disregarded by KUIP. File Specification (from “Kentucky Unemployment Insurance Portal (KUIP) ICESA File Format Reference Guide”) General File Specifications - File Extension: .txt only. - Record Length: Each record (line) must be exactly 275 characters (including trailing spaces). - Format: Fixed-length ICESA. - Only E and S records are produced for the KUIP ICESA export - KEIN = Employer Details, KY - State Unemployment Insurance ID - Use Worksite Location, Worksite ID from employee’s assigned Worksite Location - Population rule: All fields must be populated to their exact length using spaces and/or zero-fill as specified. - Left-justify where specified; pad with spaces. - Right-justify where specified; pad with spaces or zeroes per specification.
- E-Record – Employer Header Record
- S-Record – Employee Detail Record
- File Extension: .txt only.
- Record Length: Each record (line) must be exactly 275 characters (including trailing spaces).
- Format: Fixed-length ICESA.
- Only E and S records are produced for the KUIP ICESA export
- KEIN = Employer Details, KY - State Unemployment Insurance ID
- Use Worksite Location, Worksite ID from employee’s assigned Worksite Location
- Population rule: All fields must be populated to their exact length using spaces and/or zero-fill as specified.
- Left-justify where specified; pad with spaces.
- Right-justify where specified; pad with spaces or zeroes per specification.
CMP-7876 Changes to the Periodic Tax JSON Export form On the Periodic Tax JSON Export form, a new subsection named Periodic JSON Export History has been added beneath the build controls as you can see from the screenshot below. This feature helps customers and Support teams quickly locate and re-download previously generated Periodic Tax JSON/PTS export files, reducing the likelihood that processed files are lost. Previously, you had to navigate to Transfer Downloads to PC to retrieve periodic JSON exports. The export history is now available directly on the Periodic Tax JSON Export form. If no historical exports exist, the Periodic JSON Export History subsection displays an empty state message stating No export history found. [Image: screenshot] This subsection renders a table with the following columns (left to right) : - Date/Time - The date and time the file was generated. - Created By - The username of the user who initiated the build. - File Name - The JSON file name is displayed as a hyperlink. Please note that the PTS files are deleted after 60 days. - Audit Report - Click the View hyperlink to access the audit report associated with the export history entry.
- Date/Time - The date and time the file was generated.
- Created By - The username of the user who initiated the build.
- File Name - The JSON file name is displayed as a hyperlink. Please note that the PTS files are deleted after 60 days.
- Audit Report - Click the View hyperlink to access the audit report associated with the export history entry.
WSP-4024 Changes to the W/C Classification Rates form On the W/C Classification Rates form, only for the State of Washington, a new field named Time sheet based WC tax calculations will appear. This field is a checkbox which is unchecked by default. [Image: screenshot] > Note: Note: This is a currently a UI change only. The functional logic is expected to be implemented in an upcoming release.
WSP-4180 Check message enhancement with substitution variables As a service provider user managing client check configuration, you can now use substitution variables in client check messages, so that paychecks can display contextual employee and work-assignment information in the check message on a client-by-client basis. [Image: screenshot] You can enter the following substitution variables either in the Message Text section on the Check Massages form or in the Memo section on the Payroll Control form: - Worksite Location - {{HOME.LOCATION}} - Position - {{HOME.POSITION}} - Division - {{HOME.DIVISION}} - Department - {{HOME.DEPARTMENT}} - Work Shift - {{HOME.WORK.SHIFT}} - Project - {{HOME.PROJECT}} - Work Group - {{HOME.WORK.GROUP}} - Client Name - {{CLIENT.LEGAL.NAME}} > Note: Note: The Client Name comes from the Client Details form, while the other variables come from the Employee Details form.
- Worksite Location - {{HOME.LOCATION}}
- Position - {{HOME.POSITION}}
- Division - {{HOME.DIVISION}}
- Department - {{HOME.DEPARTMENT}}
- Work Shift - {{HOME.WORK.SHIFT}}
- Project - {{HOME.PROJECT}}
- Work Group - {{HOME.WORK.GROUP}}
- Client Name - {{CLIENT.LEGAL.NAME}}

Document Management (DM) Enhancements

Ticket Description Summary Help Content
DM-1574 Update to Bulk Import File Conventions The file format for bulk imports have been improved for convenience. The file name has only one requirement for the Client ID, and uses the following conventions. - Ignore the first grouping (before the 1st dash) - Ignore the numbers before the C/E in the middle grouping - The numbers following the C or E WILL BE THE CLIENT ID - Ignore the underscore and everything after it For example, if the file ID was “C12-34E4567_890”, the system would read this file as belonging to Client ID 4567. For more information, see the in-app help.

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-3449 Additional Document Permissions Service Providers can now set more specific document permissions on Configuration Templates and Client Overrides. The document permissions now display as a multi-select field, allowing service providers to select or deselect separate options for Delete, Edit, Move, Rename, and Upload. By using these additional permission options, Service Providers can control document permissions more precisely across templates and client overrides. For more information, See Managing Configuration Templates.
EP-10915 Portal Rebranding Throughout the System The system for employee and manager logins has been rebranded to Portal. Instances where it previously displayed Employee Portal have been changed to simply display Portal.

Identity and Access Management (IAM) Enhancements

Ticket Description Summary Help Content
IAM-2985 Federated User Authentication Federated Users can now link an external user ID to their current account. This allows these users to link their legacy accounts to their current PrismONE ID. During the linking process, the user is redirected to their external identity provider to authenticate for the linking process. For more information, see the in-app help.
IAM-3028 Privacy Policy Branding from Portal When a user accesses the PrismONE login and the Portal form is configured with a custom privacy policy for the client’s configuration template, the custom privacy policy now displays on the PrismONE forms. For more information, see the in-app help.

Onboarding (OB) Enhancements

Ticket Description Summary Help Content
OBE-9376 Enhancement to I-9 Supporting Documents Explanation The instructions for the I-9 Supporting Documents section has been improved for remote employees. When the Remote Verification option is enabled for the employee’s Worksite Location, the explanation of the opt-out flag has been updated to read “I will present documentation to my employer or authorized representative in person.” When the Remote Verification option is not enabled for the employee’s Worksite Location, the system now displays the following message: “You can upload supporting documents using the form below. In person, physical documentation verification may still be required.” In addition, the opt-out flag has been updated to read “I will be presenting documentation in person only.” For more information, see the in-app help.
WSP-4247 Hover Over Description in Client Workflow Grid When the Workflow Description on the Client Workflow grid is too long to display in a single cell, employees can now hover over the field to display the text of the full name. For more information, see See Assigning Workflows at the Client Level.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
PD-23966, PD-23985, and PD-23987 Client Administration Enhancements to User Defined Fields Import Form The following enhancements now reside on the User Defined Fields Import form: - The text that displays in the Import Data panel on the User Defined Fields Import form now displays as follows: [Image: screenshot] - If your user role does not have access to the form/file listed in the import file, the import fails. - You must upload the most-recent version of the import file before performing an import so the field column headers match the field’s current type and required status. (If a field is duplicated, the system uploads the last value.) Otherwise, an error message displays, “INVALID COLUMN HEADER: download the latest import file.” For more information, see Importing User-Defined Fields.
PD-17422 Human Resources Enhancement to Employee Types Form You can now quickly perform a global search for “Employment Type,” which opens the Employee Types form where you can establish employee types that are used to define employee employment type. (Searching for “Employee Type” also displays the Employee Types form.) For more information, see Establishing Employee Types.
WSP-3980, WSP-3982, and WSP-4043 Human Resources Enhancement to Employee Details Form A new field, International Employee, now displays on the Address tab in the Employee Details form. For example: [Image: screenshot] Note: This feature is only available for service providers. To use this feature, you must enable the system-level INTLEMPLOYEE custom feature code on the System Parameters form. To waive requiring a US-based resident address for an international employee, select International Employee. > Note: Note the following: - After clicking Save a warning displays if the employee was paid in the past (that is, the Last Pay Date contains a date), “Warning: Employee records with pay data cannot be saved as International Employees.” - After clicking Save a warning displays if the employee was not paid in the past (that is, the Last Pay Date is blank), “Warning: International Employees cannot be processed in a payroll batch, as they do not have a resident address. Would you like to proceed?” Click Yes to proceed. The record saves without requiring Resident Address information. (If appropriate, select International Address and enter the employee’s international address in the Mailing Address panel.) - After selecting International Employee, data in the Address, ZIP Code, City, State, County, and Geocode fields clear. - International employees cannot process payrolls and should be placed in a placeholder Pay Group to avoid work stoppage issues during payroll. - When the following occurs during payroll processing: - An employee has hours on a calculated payroll - The employee record is then updated to an International Employee - The calculated payroll is finalized without recalculation The system displays a payroll error message and stops payroll finalization, then one of the following scenarios occurs: - If you disable the International Employee field from the employee record and attempt finalizing the payroll again, the system allows the payroll finalization process to complete successfully. - If you remove the International Employee pay from the timesheet, the system allows you to recalculate and refinalize the payroll successfully (assuming there are no other errors). - If you recalculate the payroll with the International Employee field enabled, the system displays a calculation error because there is no resident address for the International Employee and payroll finalization is no longer an available option in the payroll process. For more information, see Establishing and Maintaining Employee Address Information.
- An employee has hours on a calculated payroll
- The employee record is then updated to an International Employee
- The calculated payroll is finalized without recalculation
- If you disable the International Employee field from the employee record and attempt finalizing the payroll again, the system allows the payroll finalization process to complete successfully.
- If you remove the International Employee pay from the timesheet, the system allows you to recalculate and refinalize the payroll successfully (assuming there are no other errors).
- If you recalculate the payroll with the International Employee field enabled, the system displays a calculation error because there is no resident address for the International Employee and payroll finalization is no longer an available option in the payroll process.
PD-23636, PD-23679, and PD-23792 Import Processing Enhancements to Data Import Tool The following enhancements now reside in the Data Import Tool: - A new import template, Project (Certified Pay Rates), is now available in the Data Import Tool. You can use this import template to import certified pay rates (that is, position code, position title, base rate, fringe rate, and prevailing wage rate) for projects to reduce the amount of manual work required. - Several new categories, rows 13 through 42, are now available for import using the Projects/Cost Codes import template in the Data Import Tool. (These new categories represent the rest of the fields not originally included that reside on the Projects form, where you can set project information.) Note: You can use the Projects/Cost Codes import template to import changes to projects and cost codes to reduce the amount of manual work required. - Request: Update the Worksite Locations import template in the Data Import Tool to include additional fields that are critical for tax filings and E-Verify compliance. New fields being added (columns 37–41, all optional, appended to the end of the existing template): - 37: Worksite Federal EIN. - 38: Worksite ID - 39: Federal Entity ID - 40: Exclude this location from E-Verification - 41: Enable Remote Verification for this Location Fields are located under Client → Change → Worksite Locations (Other Parameters section). The template lives at Operations → Import Processing → Data Import Tool. The Sample Header File also needs updating. No security changes are required. In short, this is a template enhancement to allow bulk import of tax-related identifiers and E-Verify settings for worksite locations. For more information, seeImporting Certified Pay Rates for Projects Importing Project and Cost Codes, and Importing Worksite Locations.
- 37: Worksite Federal EIN.
- 38: Worksite ID
- 39: Federal Entity ID
- 40: Exclude this location from E-Verification
- 41: Enable Remote Verification for this Location
PD-20492 Payroll Enhancement to Net to Gross Calculator Form The Net to Gross Calculator form now accurately includes garnishment deductions when you enable the Supplemental pay voucher type. This enhancement ensures net pay estimates provided by the calculator align with actual payroll batch results. In addition, the following now occurs: - Accurate Supplemental Pay Estimates: The calculator now identifies and includes active garnishment deductions for Supplemental pay vouchers, provided no suppressions are active. - Arrears Handling: For Supplemental pay voucher types, the calculator specifically includes applicable arrears amounts to match standard payroll processing behavior. - Improved Visibility: Garnishment deduction line items now display in the NTG results table when you enable the Supplemental pay voucher type, maintaining consistency with Regular and Vacation voucher types. - Enhanced Calculation Logic: These updates ensure the final Net Pay result reflects all applicable deductions, providing you with a more reliable estimate for Supplemental payroll processing. For more information, see Net-to-Gross Calculator.
PD-23738 and PD-23739 Payroll Enhancement to Client Allocation Formats Form A new button, Copy, now displays on the Client Allocation Formats form. For example: [Image: screenshot] You can click the Copy button to duplicate an existing format code. (The Copy button is disabled until you enter or select a format code.) The Copy Client Allocation Format form displays, where you can save a new format code. Note: If you enter an existing format code in the Copy Client Allocation Format form an error message displays, “Format code already exists. Please choose a different code.” For more information, see Setting Client Allocation Formats.
PD-23743 and PD-23744 Payroll Enhancement to Payroll Allocation Report Add “Exclude Non-Cash Pay Codes from Allocation Base” checkbox to Payroll Allocation Report Parameters UI What it does: The Payroll Allocation Report currently has an “Include Non-Cash Pay Codes” toggle, but clients who want non-cash pay lines to appear on the report while keeping them out of the tax allocation base have no way to do that. Note: The new functionality only activates when both “Exclude Non-Cash from Alloc Base” and “Include Non-Cash Pay Codes” are checked. All other combinations behave the same as today. This story adds a new “Exclude Non-Cash Pay Codes from Allocation Base” checkbox to two forms: - Client / Change / Payroll Allocation Report Parameters (saved parameters) - Payroll / Report / Payroll Allocation Report (on-the-fly parameters) Key requirements: - Checkbox defaults to unchecked - Should be placed below the existing “Include Non-Cash Pay Codes” toggle - When checked on the Parameters form, the Report form reflects the same value - Existing saved parameter sets must not be affected — the new field defaults to off For more information, see Payroll Allocation Report.
PD-23785, PD-23786, and PD-23977 Payroll Enhancement to Deduction Codes Form A new Calculation Method, % of Gross Earnings (less Deduction Types), is now available on the Deduction Codes form. Note: When using the % of Gross Earnings (less Deduction Types) option, you can enable the 403(b) Retirement option and select multiple voluntary classifications in the Voluntary Classifications panel. However, observe the following when making these selections: - You cannot enable more than one “retirement” voluntary classification. - You cannot enable bothSection 125 and Section 132. After you select % of Gross Earnings (less Deduction Types), the Exclude Ded. Type Code panel displays where you can exclude pre-tax benefit deduction types for plans that require contributions to be calculated as a percentage of gross earnings, such as COPERA. For more information, see Maintaining Global Deduction Codes.
PP-1395 Payroll California Data for Certified Payroll XML Download Report California certified pay data can now be downloaded directly from Prism using the Certified Payroll XML Download Report. To include California data, the fields for California must be configured in the Certified Payroll Details section of the Projects form. Data from timesheets that include California employees can then be accessed by running the Certified Payroll XML Download report. For more information, see Certified Payroll XML Download Report.
PP-2602 Payroll Enhancement to Export Email Information Notification emails for the Periodic Tax JSON Export form now include information about export details such as selected reports and build status, consistent with the existing Quarterly Tax JSON Export email. For more information, see Periodic Tax JSON Export.
WSP-3858 Payroll Enhancement to SuperBatch Form SuperBatch Filter Updates — New Delivery Method and Delivery Date Filters The SuperBatch filter modal now includes two new filter options: Delivery Method and Delivery Date. These filters appear beneath the existing Pay Date filter. With these additions, you can narrow your SuperBatch results to show only payrolls that match a specific delivery method or delivery date, making it easier to group and process like delivery activities together. For payrolls with multiple delivery methods — such as those with location-based special delivery settings — the batch will appear in the filter results for each applicable method. For more information, see Using SuperBatch.
WSP-3981 New Employee Import Enhancement to Import Field Mapping Form A new field, INTERNATIONAL.EMPLOYEE, now displays on the Import Field Mapping form that allows you to import a new International Employee in the New Employee Import form. For example: [Image: screenshot] You can include the International Employee column in the import file (with valid values as Y/Yes, N/No, or blank). Additionally, employees flagged as international can be imported without US-based resident address information. Note: When the INTLEMPLOYEE CFC is not enabled, the field is unavailable for import and resident address remains required. For more information, see Creating and Editing Import Mappings.
RRT-6871 Payroll Enhancement to Client Allocation Formats Form To ensure the system now displays 401k non-elective match amounts with no bill code in the Client Allocation Report for clients who have their own 401k plans, a new Allocation Code, 401KALL, is now available. You can use 401KALL to combine amounts for the following contributions: - Matching Contribution - PEO Matching Contribution - Safe Harbor Type One Match - Safe Harbor Type Two Match For more information, see Setting Client Allocation Formats.
WSP-3983 Payroll Enhancement to Payroll Control Form In association with the new field, International Employee (see WSP-3980, WSP-3982, and WSP-4043), you cannot enter or select any International Employees in the Employee panel on the Payroll Control form, which ensures that these employees are not included in the payroll batch. (If you enter an International Employee an error message displays, “International Employees cannot be added to a payroll batch.”) For more information, see Establishing Information for Processing Payrolls.
PD-23759, PD-23760, and PD-23824 Time Off Enhancement to Time Off Plans Form A new field, Linked Accruals Maximum Balance, now displays in the Time Off Plans form. For example: [Image: screenshot] You can use the Linked Accruals Maximum Balance field to define the maximum number of hours the plan is allowed to hold, which the system will use to limit how many hours are transferred from the linked Accrual Register each year based on the Balance Plan’s Annual Carryover. (Leaving the Linked Accruals Maximum Balance field blank indicates that any amount can be transferred.) > Note: Note the following: - If you Copy from another plan that contains a Linked Accruals Maximum Balance amount, the system populates that field in the duplicated plan. - If you configure a Balance Time Off Plan with a Linked Accruals Maximum Balance limit and the employee’s current balance is below that limit, when the system processes a Linked Accrual transfer only the hours needed to bring the balance up to (but not exceeding) the stop balance are transferred. - If you configure the Balance Time Off Plan with a Linked Accruals Maximum Balance limit and the employee’s current balance is already at or above that limit, when the system processes a Linked Accrual transfer no hours are transferred to the Balance Time Off Plan. - If you configure a Balance Time Off plan with no Linked Accruals Maximum Balance limit, when the system processes a Linked Accrual transfer the system applies the full transfer amount with no change to current behavior. For more information, see Defining Time Off Plans.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-3879 Previously, on the Benefits Billing Detail Report form, when you run a report with Primary Sort set as Benefit Plan under the Sort Parameters section, the XLS export missed the Selection Criteria column in the Column C. This issue affected both the Summary and Detail Report Types. Now, this is fixed.
WSP-3916 Previously, on the Benefit Rules form, when you selected a Benefit Plan or an existing Effective Date, then the Total Contribution columns displayed incorrect values. Now, this is fixed.
WSP-4030 Previously, on the Retirement Plan Enrollment form, under the Election Details section, when you entered a value in the Not to Exceed % of Pay field, then the percentage values entered in the field were not stored correctly, which lead to incorrect payroll deductions. For example, when you entered a value of 10 (intended as 10%), then the system stored this value in a way that caused payroll to interpret it as a much smaller percentage (10% was processed as 0.10%). Now, this is fixed. The input and display for this field now correctly handles percentage values. All new entries are now stored and interpreted accurately by payroll as the intended percentage. All the existing records that were affected by this issue (entries made between January 2025 and the June 2026 release) will not be automatically updated. The form will now display these values in a way that reflects how payroll has been processing them.
WSP-4162 Previously on the Group Benefit Plans form, fields under the Guaranteed Issue (GI) Limits section were required across all sections (Employee, Spouse, Dependent) when data was entered in any one section, which was incorrect. Now, this is fixed. GI Limits fields are now only required for sections that have corresponding Coverage Amounts data. For example, a Spouse-only Life Insurance plan no longer triggers a validation error when Employee and Dependent GI Limits fields are left blank.
WSP-4200 Previously, on the Employee Flexible Spending Accounts form, when you clicked the Plan Year hyperlink, the system displayed incorrect plan year. Now, this is fixed.
WSP-4258 Previously, when you ran a Slavic Import with the SEQSLAVICIMPORT custom feature code enabled, then the system cleared an employee’s Retirement Benefit Group when Column H was left blank in the import file. Now, this is fixed.
WSP-4262 On the Client Benefits Overview form, when you viewed the Client Benefits Overview Report, the plans with Network based Benefit Rules displayed special characters. Now, this is fixed.

Compliance (CMP) Fixes

Jira # Issue Summary Resolution
CMP-7813 Previously, the payroll warning for an employee whose salary is below the state minimum exempt salary amount did not display when the Worksite Location Code was not the State Abbreviation. Now, this is resolved. For an employee whose salary is below the state minimum exempt salary amount, the payroll warning will display when the Worksite Location is in the applicable state, regardless of the Worksite Location Code.
CMP-7076 Previously, for both SBEA and non-SBEA clients, for employees in Guam, the system did not correctly report their federal income tax withholding for tax code 66-10 on the MasterTax RTS 601 record, if any for the quarter. Now, this is resolved.
WSP-4227 Previously, when processing a State Tax Levy configured for “Subsequent Gross Pay,” the garnishment calculation was not correctly enforcing the Federal Poverty Guideline (FPG) limit. In certain cases, the Garnishment Check Amount would exceed the allowable threshold of Gross Pay minus the Federal Poverty Guideline Amount, resulting in an incorrect deduction. Now, this is resolved. The garnishment calculation logic has been corrected so that State Tax Levy amounts based on Subsequent Gross Pay now properly cap at the Gross Pay – Federal Poverty Guideline Amount. State Tax Rules continue to take priority where applicable. The FPG enforcement is now accurately reflected in the Garnishment detail record.
RRT-6894 Previously, when calculating retirement contributions for an employee in the state of Massachusetts, the system incorrectly included the Employer 401(k) match contributions in the MA PFML taxable wages when not safe harbor. Now, this is resolved. - Employer 401(k) match contributions (including non‑safe harbor / non‑elective matches) are now correctly excluded from MA PFML taxable wages. - Employee 401(k) elective deferrals (the amount an employee chooses to defer from salary) continue to be correctly included in MA PFML taxable wages.
Jira # Issue Summary Resolution
EERT-3804 The W4 form displayed the Original Hire Date instead of the Last Hire Date for Rehired employees. This is fixed.
EERT-3823 When a manager terminated an employee, the Termination Explanation field was not set as a required field. This is fixed.
EERT-3826 When Employee Statuses and Employee Types were configured on the Client Details form, the types were properly restricted on the New Hire Dashboard in Portal, but the statuses were not properly restricted. This is fixed.
EERT-3829 When an employee made changes to their personal information on the Address form, the banner reminding the employee that these changes might have tax implications did not display. This is fixed.
EERT-3832 Employees who were registered through PrismOne did not receive active alerts upon logging in. This is fixed.
EERT-3838 When an employee edited the custom Privacy Policy and clicked the View HTML icon, the changes to the policy did not save properly. This is fixed.
EERT-3839 The system temporarily locked certain records for extended periods, which prevented updates and blocked downstream operation. This is fixed.
EP-11118 When an employee was part of two or more SMBs and attempted to access Portal using a client-specific URL, if that client was not one of the employee’s SMBs, the session would stall and prevent the employee from accessing the client selector. This is fixed.

Identity and Access Management (IAM) Fixes

Jira # Issue Summary Resolution
IAM-2331 When a user with a registration code did not complete registration and tried again using the same code, a generic error message appeared. This is fixed. A message now displays indicating that the code has expired and that the employee must request a new registration link and PIN from the employer.
IAM-2424 When employees viewed their Account Settings form, and those employees had multiple linked accounts for a single organization, the My Linked Accounts section displayed the organization name multiple times as separate headers. This is fixed.
IAM-2913 When a user clicked a registration link, the New User Registration form did not have the PIN field automatically selected and the Get Started button displayed an erroneous arrow icon. This is fixed.
IAM-3111 When users attempted to log in with their PrismONE ID using a mobile device, an error occurred. This is fixed.

Onboarding (OB) Fixes

Jira # Issue Summary Resolution
EERT-3827 When employees who were terminated tried logging in to the enrollment app were not alerted with a warning message that indicated that there were no active workflow available. This is fixed. If a terminated employee now tries to navigate from the portal to BE, then they would be unable to continue their enrollment process.
EERT-3828 Previously, on the Group Benefit Plans form, fields under the Guaranteed Issue (GI) Limits section were required across all sections (Employee, Spouse, Dependent) when data was entered in any one section, which was incorrect. Now, this is fixed. GI Limits fields are now only required for sections that have corresponding Coverage Amounts data. For example, a Spouse-only Life Insurance plan no longer triggers a validation error when Employee and Dependent GI Limits fields are left blank.
EERT-3830 During the enrollment workflow, the Total Plan Premium displayed on the Life Benefit Plan tile was incorrectly calculated for Voluntary Life and Voluntary AD&D plans. This is fixed.
EERT-3833 When the tax forms page was configured to hide the navigation header, the My Progress sidebar did not display properly and had text cut off. This is fixed.
EERT-3845 When tax forms imported into Onboarding included a blank entry for the last name, an error occurred. This is fixed.
EERT-3857 Certain benefits import programs did not release EMPLOYEE.DED and EMPLOYEE.FLEX.ACCOUNTS record locks when no changes were made. This caused records to remain locked in production, preventing subsequent updates. This is fixed.
OBE-9803 When an employee enrolled in an FSA that was set to allow enrollment, but the Allow Coverage Amount Change field was set to No, the employee could not submit the workflow. This is fixed.
OBE-9885 When a user clicked the Current Patient checkbox for a domestic partner during Benefits Enrollment and navigated to the next form, the entry in the checkbox was not properly saved. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
PD-23849 General When a future termination date was entered for a Worksite Manager (WSM) who had access to multiple clients, the system immediately revoked access to all non-home clients — even though the termination date had not yet been reached. This caused affected managers to lose the ability to log in and work across their assigned clients before their actual last day. The system now correctly maintains a Worksite Manager’s full access to all assigned clients until the specified termination date. Entering a future-dated termination record no longer triggers an immediate change to security permissions. Access is restricted only once the system date reaches the recorded termination date, ensuring uninterrupted workflow through the manager’s final day.
PP-1944 General When managers tried approving New Hire approval, the system consistently displayed error message. This is fixed.
PP-2037 General When a user viewed the Time Sheets header on the Time Sheet Entry form, it remained fixed at its minimum width. This is fixed. The Time Sheets header is now expanded and dynamically resizes to fill the available screen real estate.
PP-2524 General When users searched for clients by name in Prism’s global search, the system displayed only the first 20 matches, which caused clients to appear missing. This is fixed.
PP-2614 General Users experienced significant slowdowns during login and while navigating for clients with large employee counts. This is fixed.
PP-2633 General When employees accessed the Users form, a literal “{1}” placeholder in the password and MFA status messages displayed instead of the configured identity product name. This is fixed.
RRT-6885 General The system stopped running payroll after users updated the default Deduction Code used for all Retirement Plans on the System Parameters form due to multiple type K records that were created in the Recurring Deduction form for all employees with a Retirement Enrollment record, which uses the corresponding default Deduction Code setting. In this scenario, a message now displays acknowledging the change and updates all associated records and provides a list of affected employee enrollments. After updating, the corresponding Deduction Code displays on the Recurring Deductions form for each associated employee, which is pulled into the payroll. If a user selects No in the initial message that displays or in the on-screen updated records that display, the system returns to the main form where the original values are automatically populated. Any Retirement Plans that have a Deduction Code Override for the corresponding Deduction Code being updated remains unchanged. When updating the Deduction Code on the System Parameters form, the Deduction Code only affects enrollments which are using the default Deduction Code assigned within the System Parameters form. > Note: Note the following: - If a user updates the System Parameters Deduction Code for ‘Loan’ and the Retirement Plan has no Deduction Code Override defined for ‘Loan,’ then the system updates all associated Retirement Enrollment records. - If a user updates the System Parameters Deduction Code for ‘Employee Deferral’ and the Retirement Plan has a Deduction/Bill Code Override defined for ‘Employee Deferral,’ then the system does not update the associated Retirement Enrollment records.
- If a user updates the System Parameters Deduction Code for ‘Loan’ and the Retirement Plan has no Deduction Code Override defined for ‘Loan,’ then the system updates all associated Retirement Enrollment records.
- If a user updates the System Parameters Deduction Code for ‘Employee Deferral’ and the Retirement Plan has a Deduction/Bill Code Override defined for ‘Employee Deferral,’ then the system does not update the associated Retirement Enrollment records.
RRT-6935 General When the system routed an HR-action approval (such as a Leave Request, Pay Rate Change, or Termination) to an assigned approver (Manager/PTO Approver) and that approver is later teminated and the pending approval was not reassigned, the approval became “orphaned.” (A nightly batch auto-processed it and, on failure, emailed a notification to an arbitrary, cross-client user who had no access to that employee.) The system no longer sends orphaned-approval “failure/resubmit” emails and now processes orphaned approvals.
WSP-4418 General Users encountered an error stating “There are no Import Field Map Definitions that match your spreadsheet” when attempting to import new employees using the Prism-Expanded field mapping, even when using the correct template and file formats. The New Employee Import has been updated to correctly match import mappings without requiring the “INTERNATIONAL.EMPLOYEE” header in the import file when the “INTLEMPLOYEE” Client Functional Constant (CFC) is not enabled. If the “INTLEMPLOYEE” CFC is enabled, the system now properly validates the mapping to include the “INTERNATIONAL.EMPLOYEE” field.
WSP-4070 Payroll When users created a new payroll batch using the Clone Last Batch option in the Payroll Control form, the system did not clone the information in the Delivery Method Override field on the Payroll Options form. This is fixed.
WSP-4336 Payroll The system did not post the deduction import amounts in the Time Sheet Deduction Import form for all employees in the import. In addition, the payroll vouchers posted these values as a lesser amount, with the decimal point over-adjusted two places to the left. This is fixed.
WSP-4406 Payroll Customers reported that delivery sheets were being automatically generated and printed with payroll reports (such as checks), even when the system was configured not to include them. This occurred specifically when the Paperless Delivery option was set to “all payroll output.” The payroll reporting process has been updated to correctly respect the Paperless Delivery configuration. Delivery sheets will no longer be generated or included in consolidated payroll reports when they are not required by the client’s setup.

========================================================================

June (R_202606)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/06/whatsnew-R_202606.htm Path: Release-Notes/2026/06/whatsnew-R_202606.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

New Features

We would like to bring your attention to the following list of new features for PrismHR.

List of New Features

Click a link to display the detailed release notes for the new feature

Documentation Enhancements

Click a link to read about the documentation enhancements included in this release.

Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Release Notes R_202607

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/07/Release-Notes-R_202607.htm Path: Release-Notes/2026/07/Release-Notes-R_202607.htm

Release Notes R_202607

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Click to view the R_202607 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for PrismHR Professional Services.

Upgrade groups Day of week Tentatively occurs on
Wave 1 Thursday July 30, 2026
Wave 2 Friday July 31, 2026
On-Premise Thursday August 6, 2026

Enhancements

You can download a complete list of enhancements in Excel format.

Click one of the following links to navigate quickly to a section.

Fixes

You can download a complete list of fixes in Excel format.

Benefits Administration (BA) Enhancements

Ticket Description Summary Help Content
WSP-2607 Enhancements to the Data Import Tool Form On the Data Import Tool form, when you import employee dependents, you can now identify employees using their SSN, Employee ID, or Clock Number. This enhancement ensures consistency across import types and provides more flexibility for managing dependent data. [Image: screenshot] For more information, see the Importing Employee Dependents help topic.
WSP-2611 Enhancements to the Benefit Import Maintenance Form While importing data on the Benefit Import Maintenance form, you can now identify employees by Employee ID, SSN, or Clock Number. This enhancement provides greater flexibility and aligns the tool with other import processes. [Image: screenshot] For more information, see the Setting Benefit Import Parameters help topic.
WSP-3018, WSP-4232, WSP-4264 Enhancements to the Cobra Participant Record Form - The COBRA Participant Record form now includes enhanced Social Security Number (SSN) validation for dependents. You will receive specific error messages for invalid formats or restricted number sequences to ensure data accuracy. - The system now prevents the deletion of COBRA Qualifying Event codes that are currently assigned to participant records on the COBRA Participant Record form. When a deletion is attempted, a validation message displays the number of affected records and provides a detailed report of the impacted participants. - With this enhancement, we have fixed the issue in the COBRA Participant Record where the Qualifying Event field failed to update when switching between participants. Additionally, a new ‘Open in new window (print or save)’ hyperlink is now available on HTML messages for improved accessibility and reporting. For more information, see the Maintaining COBRA Participant Records help topic.
WSP-3929, WSP-4419 Enhancements to the Benefit Rules Form The Benefit Rules form now prevents data entry and hides detail sections until the mandatory Benefit Group, Benefit Plan, and Effective Date fields are assigned. This update ensures data integrity and reduces confusion by gating access to contribution, coverage, and eligibility rules until the record is properly identified. [Image: screenshot] Additionally, the Benefit Rules form displays the Benefit Plan description next to the plan code. This restoration helps users quickly verify they are working on the correct plan when making rule adjustments. For more information, see the Setting Up Employee Enrollment Conditions help topic.
WSP-3979 Enhancement to the Purge COBRA Enrollees Form The Purge COBRA Enrollees form now features an enhanced Participant ID multi-selector with new filters for Enrollee Type, Client ID, COBRA Status, and Qualifying Event. This update also resolves an issue where the selector previously failed to display applicable participants. [Image: screenshot] For more information, see the Purge COBRA Enrollees help topic.
WSP-4228, WSP-4423, WSP-4249, WSP-4425 New Column Selector A new header toggle icon is available on the following forms that allows users to customize the on-form report by showing or hiding specific columns: - Employee Benefit Overview - Client Benefits Overview Additionally, a new option, Enable All is available in the column selector. This option appears when one or more columns are deselected, allowing users to quickly restore the full view. [Image: screenshot] For more information, see the Displaying an Employee’s Benefit Plans and the Displaying the Client Benefits Overview help topics.
WSP-4250, WSP-4478 Enhancements to the Employee Benefit Rule Overrides Form The Employee Benefit Rule Overrides form now hides all entry fields, links, and dropdowns until the mandatory Employee, Benefit Plan ID, and Effective Date fields are assigned. This update prevents potential data entry errors and ensures a clearer workflow for administrators. [Image: screenshot] Additionally, the form now displays the Benefit Plan description next to the plan ID. This restoration ensures users can quickly verify they have selected the correct plan when making rule adjustments. For more information, see the Overriding a Client’s Eligibility Rules help topic.
WSP-4409, WSP-4411, WSP-4412, WSP-4413, WSP-4415, WSP-4416, WSP-4417 New Next Pay Date Field A new field, Next Pay Date has now been added on the following forms that helps administrators quickly identify the next regularly scheduled payroll batch date during the enrollment process: - Retirement Plan Enrollment - Employee Benefits Enrollment - Recurring Deductions - Recurring Deduction Overrides - Scheduled Deductions - Scheduled Payments - Employee Deduction Arrears [Image: screenshot] For more information, see the in-app help.
WSP-4316 Enhancement to the Client Workflow Grid Form On the Client Workflow Grid form, you can now hover over a Client ID to view the corresponding Client Name. This enhancement improves visibility and makes it easier to audit enrollment workflows. [Image: screenshot] For more information, see the in-app help.
WSP-4329, WSP-4333 Enhancement to the Post Benefit Enrollments Form On the Post Benefit Enrollments form, you can now filter by Status Class (Active, On Leave, Terminated). Additionally, new columns for Status Class and Status Date have been added to the data table to provide better visibility into employee status. [Image: screenshot] You can also select multiple Client IDs using the new selection modal. [Image: screenshot] For more information, see the in-app help.

Compliance (CMP) Enhancements

Ticket Description Summary Help Content
2026 OBBBA Product Updates To prepare for 2026 reporting required under the OBBBA, multiple product enhancements will be added to the system in upcoming releases. These include: - The ability to recalculate overtime processed using the Straight FLSA Ruleset (which supports CA Daily overtime requirements) to the federal standard. - Automatic qualified tip and overtime calculations and W2 data buiilds. - Updated 2026 Form W-2 and Form 1099 formats.
- The ability to recalculate overtime processed using the Straight FLSA Ruleset (which supports CA Daily overtime requirements) to the federal standard.
- Automatic qualified tip and overtime calculations and W2 data buiilds.
- Updated 2026 Form W-2 and Form 1099 formats.
WSP-4033 Changes to the Washington Workers’ Compensation Classification Rates for Payroll Payroll programs have been updated to calculate Washington State Workers’ Compensation (WC) tax based on the timesheet level WC position. When the “Timesheet based WC tax calculations” flag is enabled on the WA Rate Template, Workers’ Compensation tax is now calculated using timesheet position-level Workers’ Compensation Classification Rates. The Employee Payroll Voucher (EPV) has been enhanced to store Workers’ Compensation hours by position Workers’ Compensation class, Employee Charged Workers’ Compensation Tax Rate, and Employer Charged Workers’ Compensation Tax Rate. For exempt/salaried employees, Workers’ Compensation hours continue to cap at 160 hours per month. When multiple Workers’ Compensation class codes apply on a given charge date, the highest applicable rate is used. Standard WA W/C processing continues when the flag is not enabled. For more information, see W/C Classification Rates
CMP-7792 New Form - Recalculate FLSA Qualified Overtime for OBBBA Payroll administrators can use this form to accurately recalculate and report the Overtime Premium amount on the Form W-2 using federal FLSA guidelines. You can validate the results of the recalculation before finalizing the process. You cannot recalculate payroll data that was entered using Overtime 1.5 or Doubletime 2X calculations at this time. Various filters are provided to specify the scope of the overtime recalculation process. > Note: Note: Client Access Group security is not enabled on this form To access this form, click Back Office. Under the Operations \ Action section, click Recalculate FLSA Qualified Overtime for OBBBA. To Recalculate FLSA Qualified Overtime for OBBBA for employees: Complete the following fields: - Client ID - Enter one or more client IDs for whom you want to recalculate FLSA Qualified Overtime for OBBBA or you can click the Client ID hyperlink and select them from the Select Clients dialog box. - Employer ID - Enter one or more employer IDs for whom you want to recalculate FLSA Qualified Overtime for OBBBA or you can click the Employer ID hyperlink and select them from the Select Employer dialog box. - FLSA Ruleset - Enter FLSA Rulesets with STRAIGHT (S) Reporting method only. - Location Group - This field is optional. Enter one or more location codes. - Pay Group - This field is optional. Enter one or more pay groups. - Year - Select the year from the drop-down. Years prior to 2026 will not be available. - Quarter - This field defaults to the immediate prior quarter. Select the appropriate prior quarter from the drop-down. - Suppress vouchers with FLSA hours = 0 - By default this box is unchecked. Check this box if you do not want to list employee payroll vouchers for the selected quarter which had zero FLSA hours. 1. Click Preview to view the list of recalculated payroll vouchers for employees based on the selections made above. No updates will be made to the actual payroll vouchers at this time. 2. Click Cancel to clear this form at any time. 3. Click the Download hyperlink: 1. after Preview to download the list of payroll vouchers without any updates in a .csv format. 2. after Update to download the updated payroll voucher list in a .csv format. 4. Click Update to update the employee payroll vouchers.
CMP-7889 Mastertax MTS Version 26 On the MasterTax Interface Parameters form, a new Version 26 option is now available for the MasterTax MTS Import File Version field. [Image: screenshot] Once selected, the MTS Header reports 26 in Positions 57–58 when selected. [Image: screenshot] For more information, see MasterTax Interface Parameters
CMP-7892 TTO Codes and SOC Mappings updated for 2026 Reporting TTO (Tipped Trip Occupation) codes and SOC (Standard Occupational Classification) mappings have been updated to align with the 2026 finalized reporting regulations. New TTO Codes Added - 509 – Visual Artists (SOC: 27-1013) - 510 – Floral Designers (SOC: 27-1023) - 810 – Gas Pump Attendant (SOC: 53-6031) SOC Mapping Updated - 201: Removed SOC 39-3013 - 502: Removed SOC 27-1023 - 606: Removed SOC 39-5091; Added SOC 39-5012 - 607: Removed SOC 39-9031; Added SOC 39-5091 - 608: Removed SOC 27-1019; Added SOC 39-9031 - 609: Removed SOC 51-6052; Added SOC 27-1019 - 610: Removed SOC 39-5012; Added SOC 51-6052 - 611: Removed SOC 39-5012; Added SOC 51-6041 - 703: Removed SOC 25-3021; Added SOC 53-2012 - 706: Removed SOC 53-2012; Added SOC 25-3021 Renamed TTO Descriptions - 103: Food or Beverage Servers, Nonrestaurant - 506: Pet and Show Animal Caretakers - 606: Eyebrow and Eyelash technicians - 704: Tour Guides For more information, see Positions
- 509 – Visual Artists (SOC: 27-1013)
- 510 – Floral Designers (SOC: 27-1023)
- 810 – Gas Pump Attendant (SOC: 53-6031)
- 201: Removed SOC 39-3013
- 502: Removed SOC 27-1023
- 606: Removed SOC 39-5091; Added SOC 39-5012
- 607: Removed SOC 39-9031; Added SOC 39-5091
- 608: Removed SOC 27-1019; Added SOC 39-9031
- 609: Removed SOC 51-6052; Added SOC 27-1019
- 610: Removed SOC 39-5012; Added SOC 51-6052
- 611: Removed SOC 39-5012; Added SOC 51-6041
- 703: Removed SOC 25-3021; Added SOC 53-2012
- 706: Removed SOC 53-2012; Added SOC 25-3021
- 103: Food or Beverage Servers, Nonrestaurant
- 506: Pet and Show Animal Caretakers
- 606: Eyebrow and Eyelash technicians
- 704: Tour Guides
RRT-7024 CMP-7946 CMP-7945 CMP-7941 Changes to the Print W-2 Forms On the Print W-2 Forms form, the following two new form types have been added: - SPDF - Simplex, Four-Up, Not Self-Mailer PDF - LBPDF - Legal Size, Simplex, Four-Up, Self-Mailer with address panel on bottom When selected, W-2 forms are generated as fillable PDFs and made available for download from W-2 Processing > W-2 Reporting > W-2 Reports. Existing electronic W-2 suppression logic continues to apply. The W2 batch download process has been enhanced to support larger data sets. Starting in 2025 you have the ability to suppress the instruction page when generating the W2 batch. Customers who print and mail Form W-2s in-house will have an enhanced process for 2026 tax year reporting. To reduce challenges reported by alignment and printer settings, PrismHR will now print the complete 4 quadrant Form W-2 which should be used on Blank W2 stock to replace the prior 4-Quad W2 stock. This blank W2 stock produces the IRS instructions and has 4 blank perforated sections that will print directly from PrismHR. Customers who will be printing Form W-2 in house in 2026 are encouraged to review the enhanced 2025 Form W-2 formats for alignment, data formatting, and functionality prior to printing 2026 Form W-2s at year end. This new functionality currently has the following known issues which will be resolved in an upcoming release prior to Q4. - Printing Form W-2 should ignore electronic Form W-2 employees unless using the reprint - include electronic option – this currently does not work. - Box 14 does not adjust the font size when words fit outside the box and instead cuts off at the box line - this will be fixed. - Control number prints but does not start at 1 and instead starts at 2, this also affects the sort which does not work. - Reprint - Reissued statement does not appear. - When sorting by any option other than name, the generated zip file references the alpha range for names. The 2025 PDF forms have been added to support the current development towards the new 2026 Form W-2 format. Please note the following process change if testing the 2025 W2 PDF forms: - Do not rebuild Form W-2 data as this will reset already processed Form W-2 data - Print W-2 Forms: - Print W2 Form Type S or LB (previously supported format) before printing new PDF form type - Print W2 Form Type SPDF or LBPDF When printing the new PDF form type, if previously supported format is not printed first an error will appear “No W2 Forms selected”. This will be resolved for 2026 Form W-2 year-end printing. For more information, see Print W-2 Forms
- SPDF - Simplex, Four-Up, Not Self-Mailer PDF
- LBPDF - Legal Size, Simplex, Four-Up, Self-Mailer with address panel on bottom
- Printing Form W-2 should ignore electronic Form W-2 employees unless using the reprint - include electronic option – this currently does not work.
- Box 14 does not adjust the font size when words fit outside the box and instead cuts off at the box line - this will be fixed.
- Control number prints but does not start at 1 and instead starts at 2, this also affects the sort which does not work.
- Reprint - Reissued statement does not appear.
- When sorting by any option other than name, the generated zip file references the alpha range for names.
- Do not rebuild Form W-2 data as this will reset already processed Form W-2 data
- Print W-2 Forms:
- Print W2 Form Type S or LB (previously supported format) before printing new PDF form type
- Print W2 Form Type SPDF or LBPDF
CMP-7934 Changes to the PrismHR Quarterly Tax JSON export To support BLS (Bureau of Labor Statistics) reporting in PrismHR Tax, the BLS 3020 Multiple Worksite Report for PEO and ASO clients requires specific quarterly reporting. To support this, the PrismHR Quarterly Tax JSON export now populates the WorksiteCode field under the EmployeeWageDetails array for all SUI tax codes ending in -24. The WorksiteCode for the employee is derived from the Worksite ID field under the Other Parameters section on the Worksite Locations form and is limited to 5 characters. For more information, see Quarterly Tax JSON Export
CMP-7944 Changes to the Miscellaneous Global Parameters On this Miscellaneous Global Parameters form, the Do Not Repeat Data on W-2 PDFs Beginning in field will be auto-applied to 2025 and beyond, so that data will not repeat on subsequent employee W-2 pages unless that information did not fit on the previous page of the form. For more information, see Miscellaneous Global Parameters

Employee Portal (EP) Enhancements

Ticket Description Summary Help Content
EP-11013 Support for International Employee Flag Portal now supports the International Employee flag on the Address tab of the Employee Details form. When this option is enabled via the system-level Custom Feature Code for the client and the employee is flagged as an International Employee, Portal now clears the address and geocode for the displayed employee record and disables editing these fields. The record can still be saved normally when other fields are changed. For more information, see the in-app help.
EP-11056 Spanish Translation Support for W-2 Election Configuration The W-2 Election Configuration form (System Parameters > Actions > W-2 Election Text) now includes Spanish translation fields in the Screen Text section. For each existing text field, a corresponding Spanish field has been added: – W2 Elect Intro (Spanish) – W2 Elect Terms (Spanish) – W2 Elect Disabled Message (Spanish) – W2 Elected Message (Spanish) – W2 Elect Accept (Spanish) When an employee views Portal in Spanish, the system displays the configured Spanish translation for the W-2 election introduction, terms and conditions, disabled and elected status messages, and acceptance text. This enhancement enables organizations to provide a fully localized W-2 election experience for their Spanish-speaking employees. For more information, see the in-app help.
EP-11154 Reports in Portal Managers can now view certain system reports directly through Portal using the new Reports menu item. This menu item can be added using the Configuration Templates form or the Client Override form. The first set of reports available in Portal include the following items: - Employee Time Off Accruals Report - Payroll Employer Tax Report - Payroll Summary Report - Payroll Billing Summary Report - Pay Code Summary Report With this enhancement, managers can view these reports while working in Portal to verify important information more quickly and efficiently. > Note: Note: Managers must have Full access on their user role to view the report. Inquiry access does not grant the ability to view the report. > Note: Note: For payroll-related reports, Managers must have access to all employees within a payroll to view the batch as an option on the report. If managers are restricted from accessing records for one or more employees in a batch, they cannot view that batch. Known Issue: On the Payroll Summary report, the Break Out Expense Reimbursement as Separate Column check box does not function properly, and should not be used. This issue will be fixed in an upcoming release. For more information, see the in-app help.

Identity and Access Management (IAM) Enhancements

Ticket Description Summary Help Content
IAM-2985 Federated User Authentication Federated Users can now link an external user ID to their current account. This allows these users to link their legacy accounts to their current PrismONE ID. During the linking process, the user is redirected to their external identity provider to authenticate for the linking process. For more information, see the in-app help.
IAM-3001 Enhancement to Error Messages When an error message displays from the Identity and Access Management system, the error message now displays the correlation ID from their system request. Users who encounter error messages can include this correlation ID on their support request to help identify the exact cause of their issue. For more information, see the in-app help.
IAM-3017 Support for SSO with SAML 2.0 Identity Providers The Identity and Access Management system can now act as an Identity Provider for Security Assertion Markup Language (SAML) 2.0, allowing Service Providers to SSO into PrismHR products using the SAML workflow. Administrators can register SAML SSO clients using the SSO Services form found in the Actions menu on the System Parameters form. For more information, see the in-app help.

Onboarding (OB) Enhancements

Ticket Description Summary Help Content
OBE-9246 Automatically Archive Benefit Workflows Clients now have the option to automatically archive Benefit Workflows after a certain amount of time has passed. The new Archive unsubmitted enrollment workflows checkbox can be accessed by navigating to the System Parameters form in Prism and selecting Enrollment Options from the Action bar menu. Selecting this option and specifying a number of days enables the automatic archival of enrollment workflows after the designated time period. When this option is enabled, records from employees in all employment statuses are archived automatically. Records can be unarchived if necessary by navigating to Benefit Utilities and selecting the Unarchive Enrollments form. With this enhancement, clients can maintain enrollment workflow records more efficiently through an organized, automated system. For more information, See Setting Enrollment Options.
OBE-10401 Enhancement to Benefit Plan Offerings During Benefits Enrollment, employees now only see plan offerings that are available for their eligibility date. Plan offerings that are only available outside of the date no longer display as options. With this enhancement, employees can now decide on benefit plans without accidentally selecting plans that would result in a gap in coverage. For more information, See Defining Enrollment Plans.

Prism (PD) Enhancements

Ticket Category Description Summary Help Content
PD-23737 ACH Enhancement to ACH Journal Edit/Entry Form ACH Journal Entry Validation Enhancement To ensure data integrity and prevent processing failures, the system now validates transaction amounts during ACH Journal entries. This update prevents negative values from being included in ACH files, which previously caused errors during the Build Review Report process. - Negative Amount Prevention: The ACH Journal Edit/Entry form no longer accepts values less than zero. - Real-time Error Messaging: If a negative amount is entered, the system will display the error message: “Transaction amount cannot be less than zero.” - Data Integrity: Users are prevented from saving the form until a valid, non-negative amount is provided, ensuring that ACH files remain compliant with processing requirements. For more information, see Creating or Modifying an ACH Journal.
WSP-4280 ACH Enhancement to ACH Originators Form PrismHR now supports the use of a custom Header Trace Number in ACH files. This enhancement allows you to meet the specific formatting requirements of certain financial institutions, such as credit unions, by providing greater control over the NACHA file header and batch control records. What’s New - Custom Trace Number Field: A new, optional Header Trace Number field is available on the ACH Originators form (System > Change > ACH Originators). - Specific Formatting: This field accepts numeric values exactly 8 characters in length. - Automated File Integration: When populated, the custom number is automatically included in positions 80-87 of both the Company/Batch Header and Company/Batch Control records within the NACHA file. - Standardized Support: This feature applies to standard NACHA formats, ensuring compatibility where it’s needed most without affecting third-party formats or reverse wires. Customer Benefit This update provides the flexibility needed to comply with diverse banking requirements. By allowing for a custom Header Trace Number, you can ensure your ACH files are accepted by all participating financial institutions, reducing the risk of file rejections and streamlining your electronic payment processes. For more information, see Using ACH Originators.
RRT-7008 Benefits Administration Enhancement to the Client Benefit Overview Form Improved performance when loading Benefit Plan Setup from the Client Benefit Overview form. For more information, see Displaying the Client Benefits Overview.
WSP-4211 Benefits Enrollment Enhancement to Proxy Login Form PrismHR now allows authorized users to proxy into the Employee Portal for terminated employees. This enhancement ensures that you can provide better support to former staff and verify their portal experience directly. What’s New - Terminated Employee Proxy: The restriction that prevented proxying into the Employee Portal for employees with a “Terminated” status has been removed. - Seamless Support Access: You can now launch the portal proxy window for any terminated employee without encountering validation blocks. Customer Benefit This update improves your ability to assist former employees who still have access to the portal. By allowing you to proxy into their accounts, PrismHR enables you to quickly troubleshoot issues, confirm discrepancies, and ensure a smooth post-employment experience for your users. For more information, see Logging in as an Employee.
RRT-6953 Billing Enhancement to the Billing Events Form You can now configure custom comment templates for Third Party Sick Pay (TPSP) adjustments via a new field on the Billing Events form. These templates support dynamic placeholders for employee and billing details. If no template is defined, the system continues to use the standard default comment. For more information, see Establishing Billing Events.
PD-23997 Client Enhancement to Transfer Employee to New Client Form PrismHR now includes enhanced validation for benefit groups when transferring employees to a new client. This update ensures that only active and appropriate benefit groups can be selected or automatically populated during the transfer process, preventing the use of retired or restricted plans. What’s New - Restricted Plan Selection: When using the Transfer Employee to New Client form (Operations > Action > Transfer Employee to New Client), you can no longer select benefit groups that are designated only for retirement plans. - Active Status Enforcement: Benefit groups with a “Stop New Use” or “Stop All User” date that has already passed or occurs on the current date are now excluded from selection. - Improved Pre-population Logic: If an employee is being transferred to a client that has the same benefit group as their current one, the system will only automatically populate that group if it is still active. If the group has reached its stop date at the new client, it will not be pre-populated. - Manual Entry Validation: These same restrictions apply to manual data entry, ensuring consistency across all methods of assigning benefit groups during a transfer. Customer Benefit This enhancement improves data integrity and reduces administrative errors by ensuring employees are only assigned to valid, active benefit groups during a client transfer. By automatically filtering out retired and retirement-only plans, PrismHR helps you maintain accurate benefit enrollments and simplifies the employee transition process. For more information, see Transferring Employees to New Clients.
RRT-6956 Client Enhancement to the Carrier Plan Billing Report Form PrismHR has improved the performance of the Carrier Plan Billing Report form by reducing per-record overhead and optimizing security checks for service providers. These changes result in faster report generation, particularly when running the report for all clients, while maintaining identical output and data accuracy. For more information, see Carrier Plan Billing Report.
WSP-4183 Client Enhancement to Clone Client Form We have updated the Clone Client process to ensure that system-generated Client IDs are only consumed when a clone is successfully completed. What’s New? Previously, opening the Clone Client form would automatically increment the next available Client ID in the system, even if you didn’t finish the cloning process. This could lead to “gaps” in your Client ID numbering. With this update: - Smart Pre-population: The form still suggests the next available Client ID for your convenience. - Conditional Incrementing: The system now only officially “claims” and increments the Client ID once you click Clone and the process succeeds. - Duplicate Prevention: We’ve added a validation step that double-checks the availability of the Client ID at the moment of cloning. If the ID is already in use, you’ll receive a warning and the form will refresh with the latest available ID. Why It Matters This enhancement provides cleaner data management by preventing skipped Client IDs and ensuring your numbering remains sequential and accurate. It also adds a layer of protection against accidental overwrites, giving you more confidence when setting up new clients. How to Use Navigate to Client > Action > Clone Client. The system will handle the ID validation and incrementing automatically behind the scenes. For more information, see Cloning a Client.
WSP-4260 and WSP-4281 Client Enhancements to Client Details Form The following enhancements now reside on the Client Details form: Expanded Options for Tracking Client Payment Methods PrismHR now offers expanded options for tracking client payment methods within the Billing Setup. This enhancement allows for more granular categorization and improved reporting on how clients transfer funds. What’s New Expanded Transfer Type Options: The Transfer Type dropdown on the Client Detail / Billing panel now includes the following additional options: - Check Deposit - ACH Transfer - Cash Deposit - International Wire Customer Benefit These new options provide a more comprehensive way to categorize client billing preferences. By capturing these specific payment methods, you can easily generate detailed reports and gain better visibility into your billing operations. Support for International Banking Requirements We have enhanced the Client Detail and Billing sections to better support international banking requirements. What’s New? - International Client field: A new International Client checkbox is now available on the Detail tab (located directly below the NAICS code). - Dynamic Field Labeling: When a client is flagged as an “International Client,” the Routing Number field on the Billing tab automatically updates its label to Swift Code. - Flexible Data Entry: For international clients, the Swift Code field allows manual entry of up to 11 characters and bypasses standard ABA routing number validation. Why It Matters This update provides a clear way to identify international clients and ensures that their specific banking information is captured accurately. By dynamically relabeling the field and adjusting validation rules, we’ve made it easier to manage global client setups without compromising the data integrity of your domestic clients. How to Use 1. Navigate to the Client Detail tab and check the International Client box for the relevant client. 2. Go to the Billing tab to enter the Swift Code. 3. For domestic clients, leave the field unchecked to continue using standard ABA/Routing Number validation. For more information, see Specifying Client Billing Options and Maintaining Client Information.
RRT-6955 Employer Administration Enhancement to the W2 Batch Download Form The W2 Batch Download process has been updated to utilize a new fillable PDF service. This change improves the efficiency and reliability of generating W2 forms. For more information, see Setting Up Form W-2 Batch Download.
RRT-7083 Enhanced Dashboard Enhancement to Enhanced Dashboard Security PrismHR has enhanced the security and configuration logic for the Enhanced Dashboard to ensure that Service Provider access remains consistent and unaffected by restrictions intended for other user types. This update also clarifies the precedence of security settings for Worksite Managers (WSMs) and Trusted Advisors (WTAs). What’s New - Service Provider Access Integrity: The Dashboard Access form (Global Configuration > Access Dashboard) has been updated to ensure that settings chosen for WSMs and WTAs no longer inadvertently restrict access for Service Provider users. Service Providers will now maintain their full intended access regardless of these configurations. - Refined WSM/WTA Dashboard Logic: Dashboard access for WSMs and WTAs now correctly updates based on the options selected in the Access Dashboard panel. - Security Precedence: To ensure robust data protection, user role-level security now takes precedence over dashboard-specific settings. For example, the Employee Benefit Enrollment option will remain visible for WSMs and WTAs if their assigned user role permits access to the Employee Benefit Overview form, even if the option is unchecked on the Access Dashboard panel. Customer Benefit This enhancement provides more reliable and predictable dashboard behavior. By ensuring that Service Provider access is preserved and that role-based security remains the primary authority, PrismHR allows you to configure dashboard views for your clients with greater precision and confidence. For more information, see Using the Enhanced Dashboard.
PD-23946 Human Resources Enhancement to Employee Details Form We have expanded the Preferred Language options in the Employee Details section to better support diverse workforces. What’s New? You can now select the following languages from the Preferred Language dropdown (HR > Change > Employee Personal): - Mandarin (MAN) - Portuguese (POR) - Vietnamese (VIE) - Arabic (ARA) - Korean (KOR) - Russian (RUS) - Hindi (HIN) Why It Matters This update allows for more accurate employee record-keeping. Please note that these new options are currently for informational purposes only and do not change the supported languages for the Employee Portal, Onboarding, or automated system notifications. How to Use The new languages are available immediately in the UI dropdown and are supported via the Employee Import and Update APIs using their respective three-letter codes. For more information, see Maintaining an Employee’s Personal Information.
PD-24071 Human Resources Enhancement to Position Change Approval Form PrismHR now provides approvers with more comprehensive information when reviewing position change requests. By surfacing key classification fields directly in the approval workflow, this update ensures that decisions are made with full context and without the need to navigate away from the approval form. What’s New Enhanced Approval Details: The Detail panel of the Position Change approval form now includes three additional rows sourced from the new position record: - New Position Classification: Displays the classification assigned to the target position. - New FLSA Exempt: Indicates the exempt status of the new position as Yes or No. - New Remote Position Classification: Shows the remote classification for the new position (remains blank if no value is set). - Strategic Placement: These new fields appear immediately after the “New Position” row, maintaining a clear and logical layout for reviewers. Customer Benefit This enhancement streamlines the approval process and improves decision-making accuracy. Approvers no longer need to manually look up position details on separate screens, reducing friction and ensuring that critical factors like FLSA status and position classification are always visible during the review. For more information, see Changing an Employee’s Position.
PD-19994 and PD-19996 Payroll Enhancements to Redirect Direct Deposit Form The following enhancements now reside on the Redirect Direct Deposit form: Specifying Different Dates for Offset and Redirect Adjustment Vouchers PrismHR now allows you to specify different dates for offset and redirect adjustment vouchers when redirecting a direct deposit. This ensures that accounting and banking records accurately reflect when funds were returned and reissued. What’s New - New Offset Date Field: A new Offset Date field is now available on the Redirect Direct Deposit form. - Independent Date Control: You can now set a specific date for the offset voucher (which reverses the original transaction) that is different from the redirect voucher date (which reissues the payment). - Automated Posting: When an Offset Date is provided, the system automatically uses it for the offset voucher’s pay date and General Ledger (GL) posting date. The redirect voucher continues to use the Redirect Deposit Date. Customer Benefit This enhancement eliminates the need for manual journal adjustments to correct date discrepancies. By aligning adjustment vouchers with actual banking transaction dates, you can maintain more accurate financial records and streamline your reconciliation process. Capturing and Tracking the Reason for Redirecting a Direct Deposit PrismHR now allows you to capture and track the reason for redirecting a direct deposit. This enhancement ensures that adjustment vouchers include clear reference information, making it easier to match them with original transactions and understand the business cause for the change. What’s New - Redirect Reason Field: A new, optional Redirect Reason field has been added to the Redirect Direct Deposit form (Payroll > Change > Redirect Direct Deposit). This free-text field allows for approximately 60 characters. - Voucher Note Integration: When a reason is entered, it is automatically included in the notes of both the offset and redirect adjustment vouchers, prefixed with “Reason:”. - Enhanced Visibility: You can view the captured redirect reason on the Banking tab of the resulting vouchers. Customer Benefit This update improves auditability and simplifies payroll reconciliation. By providing a dedicated space to document why a direct deposit was redirected—such as a bank return or closed account—PrismHR eliminates the need for manual cross-referencing and ensures that your financial records are comprehensive and easy to navigate. For more information, see Redirecting Direct Deposit Amounts.
PD-23750 Payroll Enhancement to Payroll Control Form To help prevent scheduling conflicts and potential ACH or funding issues, the system now alerts payroll administrators when a manual or special payroll batch is assigned a pay date that falls on a recognized holiday. This enhancement ensures that users can verify the intended check date before committing the batch. - Automated Holiday Detection: When entering a pay date for a manual or special batch, the system automatically checks the date against the client’s specific holiday list and standard bank holidays. - Confirmation Prompt: If a conflict is detected, a warning dialog appears, allowing the administrator to either confirm the date and proceed or cancel to adjust the entry. - Streamlined Workflow: Once a holiday date is acknowledged and confirmed, the warning will not reappear on subsequent saves of that specific batch. - Non-Intrusive Validation: If the entered date does not fall on a holiday, the batch creation process continues without interruption. For more information, see Establishing Information for Processing Payrolls.
PD-23805 Payroll Enhancement to Pay Check Calculator Form The Pay Check Calculator has been streamlined to focus exclusively on Net Pay calculations. The Manual Check option has been removed from this form to ensure a more consistent and error-free user experience. What Changed? - Simplified Calculation Types: The dropdown menu for Calculation Type has been removed. - Net Pay Focus: The calculator now defaults to Net Pay as the sole calculation method. - Interface Cleanup: The field previously used to select between calculation types is now read-only or removed to prevent navigation to unsupported options. - Legacy Cleanup: Removed the legacy Manual Check option, so you can now access that functionality in the Payroll\ Action\ Manual Check Entry form. Why It Matters Previously, selecting the Manual Check option within the Pay Check Calculator could lead to errors. By focusing the tool on its primary purpose—calculating Net Pay—we have improved the reliability of the tool and simplified the workflow for payroll administrators. Customer Benefit Users can now perform pay calculations more quickly and with greater confidence, knowing that the tool is optimized for accurate Net Pay results without the risk of triggering legacy error messages. For more information, see Calculating Net Pay.
PD-23856 and PD-23857 Payroll Enhancement to PEO Client Accounting Form New Option to Exclude Non-Cash Pay Codes from Tax Allocation Base PrismHR has introduced a new configuration option in the PEO Client Accounting Template to provide greater control over tax allocation calculations. Users can now choose to exclude non-cash fringe benefit pay codes from the tax allocation base, ensuring that $0 allocation lines are not included in processing. Customer Benefit This enhancement provides greater control over how taxes are allocated across different pay types. By excluding non-cash items from the allocation base, you can ensure that your GL output more accurately reflects cash-based tax liabilities, leading to cleaner and more precise financial reporting. Key Benefits - Improved Accuracy: By excluding non-cash items from the allocation base, you can ensure that tax allocations more accurately reflect cash-based payroll costs. - Cleaner Reporting: Enabling this option prevents the generation of unnecessary $0 allocation lines, leading to more concise and relevant accounting data. - Flexible Configuration: This setting is managed at the template level, allowing you to apply different allocation logic to different clients as needed. How It Works A new checkbox, Exclude Non-Cash Pay Codes from Tax Allocation Base, has been added to the PEO Client Accounting Template screen (located at Client > Change > PEO Client Accounting). - Default Setting: The checkbox is unchecked by default for all new and existing templates. - Usage: When checked, the system will identify non-cash fringe benefit pay codes and exclude them from the tax allocation base during downstream processing. For more information, see Working with PEO Client Accounting.
WSP-3858 Payroll Enhancement to SuperBatch Form SuperBatch Filter Updates — New Delivery Method and Delivery Date Filters The SuperBatch filter modal now includes two new filter options: Delivery Method and Delivery Date. These filters appear beneath the existing Pay Date filter. With these additions, you can narrow your SuperBatch results to show only payrolls that match a specific delivery method or delivery date, making it easier to group and process like delivery activities together. For payrolls with multiple delivery methods — such as those with location-based special delivery settings — the batch will appear in the filter results for each applicable method. For more information, see Using SuperBatch.
WSP-3882 and WSP-3883 Payroll Enhancements to Payroll Options Form The following enhancements now reside on the Payroll Options form: Control Over Time Off Accruals PrismHR now provides more granular control over time off accruals for manual and special payroll batches. You can now select specific time off plans to include in these batches, ensuring accruals are only forced for the plans you choose. What’s New - Granular Accrual Control: When processing a manual or special batch, you can now select specific time off plans for accrual rather than applying it to all plans. - New Selection Field: A new “Time Off Plans” multi-value grid is available on the Payroll Options form (Payroll Control > Action > Options). This field appears when the “Force Time Off Accruals” checkbox is selected. - Updated Terminology: The “Force PTO Accruals” checkbox has been renamed to Force Time Off Accruals to align with current system conventions. Customer Benefit This enhancement offers greater flexibility for payroll processors, allowing for more precise management of time off accruals during non-standard payroll runs. By selecting only the necessary plans, you can avoid unnecessary accrual calculations and maintain more accurate time off records. Time Off Calculations During Off-cycle Runs Payroll administrators can now ensure Time Off is calculated during off-cycle runs using the new “Force Time Off Accruals” field in Payroll Control. What’s New? - Automated Accruals: Manual and special payroll batches can now trigger accruals automatically, treating them as scheduled runs. - Bypass Restrictions: Override standard “same period” checks for specific Time Off plans to ensure benefits are processed correctly. - Data Integrity: Includes safeguards to prevent forced accruals for previous years, protecting your rollover logic. How to Use: Enable the Force Time Off Accruals field and select the relevant plans in the Payroll Control/Options menu. This update applies to all calculation methods. For more information, see Setting Special Processing Options.
PD-23846 System Enhancement to W-2 Election Configuration Form Spanish Translation Support for W-2 Election Configuration The W-2 Election Configuration form (System Parameters > Actions > W-2 Election Text) now includes Spanish translation fields in the Screen Text section. For each existing text field, a corresponding Spanish field has been added: - W2 Elect Intro (Spanish) - W2 Elect Terms (Spanish) - W2 Elect Disabled Message (Spanish) - W2 Elected Message (Spanish) - W2 Elect Accept (Spanish) When an employee views the portal in Spanish, the system displays the configured Spanish translation for the W-2 election introduction, terms and conditions, disabled and elected status messages, and acceptance text. This enhancement enables organizations to provide a fully localized W-2 election experience for their Spanish-speaking employees. For more information, see Creating W-2 Election Text.
WSP-3807 and WSP-3808 System Enhancement to System Parameters Form A new Starting At field has been added to the System Parameters form (System > Change > System Parameters), allowing Service Provider users to define the starting number for auto-assigned client IDs. Previously, auto-assigned IDs followed an implied sequence; this enhancement gives administrators control over the starting value. Key details: - The Starting At field is available when Auto Assign Company ID is enabled. When Auto Assign Company ID is unchecked, the field is not editable. - Accepts integer values up to the maximum character length defined in your system configuration. - Validates that the entered value is not already in use. If a duplicate is detected, an error message displays the next available client ID. - Leading zeros are treated as insignificant (e.g., 002885 and 2885 are considered the same value). - The field is optional — the form can be saved with or without a Starting At value. For more information, see Setting General System Parameters.
WSP-4383 System Enhancement to User Roles Form PrismHR now offers more flexibility when retiring user roles by allowing you to obsolete roles that are no longer assigned to any active users. This update ensures that roles can be easily managed and retired without being blocked by inactive user assignments. What’s New - Refined Role Obsoletion Logic: The validation on the User Roles form (System > Change > User Roles) has been updated. You can now mark a user role as “obsolete” even if it is still assigned to inactive users. - Active User Protection: To maintain system integrity, the system still prevents you from obsoleting any role that is currently assigned to one or more active users. - Clearer Error Messaging: If you attempt to obsolete a role assigned to active users, a clear error message will now appear: “This role must be removed from all active users before it can be obsoleted!” Customer Benefit This enhancement simplifies user role management by removing unnecessary barriers to retiring old roles. By focusing only on active user assignments, PrismHR allows you to keep your role list clean and up-to-date while still providing a guardrail to prevent accidental disruption for active staff. For more information, see Defining User Roles.
WSP-4384 System Enhancement to Client Status Change Form PrismHR now includes a final confirmation guardrail when terminating a client record. This enhancement ensures that critical actions, such as deleting payroll batches and updating employee benefits, are double-confirmed to prevent accidental data loss. What’s New - Termination Confirmation Pop-up: When changing a client’s status to Terminated on the Client Status Change form (Client > Action > Client Status Change), a new warning message now appears after clicking Save. - Detailed Warning Message: The pop-up alerts you that terminating a client affects multiple records—including payroll batches, employee benefits, and deductions—and that these actions cannot be reversed. - Execution Control: You must explicitly click Yes on the warning message to proceed with the termination. Clicking No will return you to the form without making any changes. - Targeted Validation: This new confirmation step specifically applies to the “Terminated” status and does not affect other status changes. Customer Benefit This update provides an essential layer of protection for your data. By requiring a final confirmation, PrismHR helps prevent the accidental termination of client records, ensuring that such a significant and irreversible action is only taken when intended and after all necessary payroll processes are complete. For more information, see Changing the Client Status.

Fixes

Benefits Administration (BA) Fixes

Jira # Issue Summary Resolution
WSP-3212 Previously, Dependent Care (DEP) deduction amounts on employee pay vouchers were not displaying as clickable blue hyperlinks. This occurred for midyear Dependent Care FSA plans when the account used a legacy offer type that was not recognized after the introduction of the new DEPFSA offer type. Now, this is fixed.
WSP-3799 Previously, there was no validation while copying a benefit plan on the Group Benefit Plans form. Now, this is fixed. We have now added a validation to the Copy Benefit Plan feature to prevent copying a plan to itself. This prevents billing rates from being inadvertently deleted when the source and destination IDs are identical.
WSP-4226 Previously, on the Employee Benefits Enrollment form, the eligible benefit enrollment records failed with a “CANNOT FIND PLAN TYPE” error when family-rated premiums were flagged alongside age-banded medical rates. Now, this is fixed.
WSP-4238 Previously, the Benefit Rules form did not collapse all subsections after saving or deleting a record. Now, this is fixed. The Benefit Rules form now correctly collapses all subsections after saving or deleting a record. This ensures the form returns to its default state, consistent with the Employee Benefit Rule Overrides form.
WSP-4299 Previously, the Employee Retirement Plan Register form defaulted focus to the Plan ID field upon initial load. Now, this is fixed. The form now correctly defaults to the Employee ID field, as all other selections depend on the selected employee.
WSP-4321 Previously, on certain Benefit related forms, the system allowed to proceed when you provided a plan that was not assigned to the client. Now, this is fixed. We have now added validation to the Benefit Plan ID field to ensure only plans assigned to the client can be manually entered. This update affects Benefit Rules, Benefit Rule Overrides, Retirement Match Rules, and Benefit Adjustments forms.
WSP-4353 Previously, on the Employee Benefit Rule Overrides form, the Medical, Dental, and Vision plans with associated networks did not appear. Now, this is fixed.
WSP-4370 Previously, on the Benefit Rules form, the Existing Effective Date drop-down field did not clear after saving, deleting, or canceling a record. Now, this is fixed.
WSP-4371 Previously, on the Employee Benefit Rule Overrides form, the existing Effective Date drop-down field did not clear after deleting or canceling a record. Now, this is fixed.
WSP-4394 Previously, on the Client Workflow Grid form, the system displayed the client name even after clicking ‘Clear’ or ‘Cancel’. Now, this is fixed.
WSP-4459 Previously, on the Employee Benefit Rule Overrides form, the ‘Percent of Gross Wages’ field remained visible after saving, deleting, or canceling an override. Now, this is fixed.
WSP-4477 Previously, on the Benefit Billing Detail Report form, users could manually enter benefit plan IDs that were not assigned to the client. Now, this is fixed.

Compliance (CMP) Fixes

Jira Number Issue Summary Resolution
CMP-7039 Previously, the Common Pay Agent data from the latest year listed in Employer Details did not automatically populate in the EES Puerto Rico export file. You had to manually update the Common Pay Agent data for each year. Now, this is resolved. The Common Pay Agent data from the latest year listed in Employer Details now automatically populates in the EES Puerto Rico export file, without requiring to manually update the Common Pay Agent data for each year.
CMP-7861 Previously, the “Work Out of State” flag was missing from the MasterTax (MTS) 500 and 601 records for Pennsylvania (PA), even when the “Include Pennsylvania Work State Flag (Y/N)” field was selected on the MasterTax Interface Parameters form. Now, this is resolved.
CMP-7911 Previously, for employees in the state of Oregon, the Paid Family and Medical Leave (PFML) wages were not reported on the MasterTax 601 record positions 428-441 of the RTS file when PFML tax codes were redirected to alternate codes for example 38-40 to 38-22 and 38-41 to 38-35 for both Employer and Client reported tax basis. Now this is resolved.
CMP-7933 Previously, the system generated a garbled payroll error when calculating the KY County and School District Taxes and payed a larger amount of cash tips. Now, this is resolved.
CMP-7947 Previously, the non-Schedule R version of the Quarterly Tax JSON export incorrectly doubled Q1 tip amounts in the Year-to-Date calculation, resulting in inflated YTD wage and tax totals. Now, this is resolved.
CMP-7948 Previously, the non-schedule R version of the Quarterly JSON export was incorrectly reporting Subject YTD wages as taxable $7,000 for employees who had already exceeded the taxable wage limit but received no pay in the current quarter. The Schedule R version of the Quarterly JSON export was dropping the employees from the tax record block all together. Both versions were significantly under-reporting YTD Subject wage amounts. Now, Non-Schedule R exports now accurately include over-limit wages in the Subject wage calculation, and Schedule R exports no longer omit unpaid employees from the tax record block.
CMP-7950 Previously, the non-Schedule R version of the Quarterly Tax JSON export, incorrectly overstated tipped wages for 00-16TIPS by carrying forward prior-quarter tips on top of YTD totals, and for 00-12TIPS dropped employee records when no tipped wages existed in the current quarter even if they had tips in a prior quarter and should still appear in the YTD record for the tax year. Now, this is resolved. Both Non-Schedule R and Schedule R files now correctly report YTD and QTD tip wage amounts for all applicable employees.
RRT-6910 Previously, when an employee was employed in more than one client under the same employer in the state of Connecticut, the employee portion of CT PFML tax (tax code 07-40) incorrectly displayed an employer‑level tax record even when CT PFML was reported at the client level only. Now this is resolved. If you have employees paid under multiple clients and use client reported CT PFML, then: - CT PFML taxes reported with a tax basis of Client now display only at the client level on the Employee Tax Summary. - No employer‑level record is shown if the tax was never calculated at the employer level. - The display is now consistent and accurate for both employee (EE) and employer (ER) CT PFML taxes 07‑40 and 07‑41, including cases where an employee is paid under multiple clients for the same employer.
Jira # Issue Summary Resolution
EERT-3846 When a worksite manager accessed the I-9 Approval form using a mobile device, the signature acknowledgement section did not wrap properly, preventing the manager from viewing the full acknowledgement. This is fixed.
EERT-3870 When a manager viewed the My Employees form in Portal, if there were more than 99 pages of employees assigned to the manager, page numbers with more than two digits were partially cut off. This is fixed.
EERT-3906 When a manager’s User Role was set to hide Emergency Contact fields, the manager could still see these fields in Portal. This is fixed.
EP-11144 When a timesheet in Portal included non-productive hours, opening the timesheet in Prism displayed those hours as productive. This is fixed.

Identity and Access Management (IAM) Fixes

Jira # Issue Summary Resolution
IAM-3128 When some users attempted to remove the Authentication app using the My Login Settings form in Portal, an error occurred and the app was not removed. This is fixed.

Onboarding (OB) Fixes

Jira # Issue Summary Resolution
EERT-3840 When an employee viewed the Employee Confirmation Statement, English and Spanish text displayed properly based on the employee’s settings. However, when the employee downloaded the Enrollment Statement, the text did not correctly display in the employee’s selected language. This is fixed.
EERT-3851 When a user created or edited a business rule in the Business Rules Library, the rule could be saved even when no operator was selected a the Choose Operator field. This is fixed.
EERT-3862 When additional gender options beside the default Male and Female were enabled on the System Parameters form, these options did not display properly in the Personal Information section of the onboarding workflow. This is fixed.
EERT-3863 When an employee was currently enrolled in a High Deductible Health Plan (HDHP) medical plan and an HSA request message was attached to the plan, when the employee clicked Next the HSA message did not display. This is fixed.
OBE-10407 When an onboarding plan included a Zero Days From Start message, the email message was sent every day after the start day. This is fixed.

Prism (PD) Fixes

Jira # Category Issue Summary Resolution
RRT-7023 Billing Billing rules with invoice minimums did not calculate correctly when using a billing code other than ADMIN or blank. This is fixed. The system now ensures that minimum invoice amounts are properly applied to all specified billing codes.
PD-23822 General When a client record was removed using the Inactive Data Deletion Utility, historical COBRA records associated with that purged client remained in the system. For employees cross-hired with the purged company, these orphaned records triggered a warning during termination in their active client, stating that a new COBRA record would not be created and requiring manual intervention to proceed. The Inactive Data Deletion Utility was updated to ensure that all associated COBRA Participant Records (COBRA.ENROLLEE and COBRA.ENROLLEE.HISTORY) are fully purged when a client is deleted. This prevents orphaned records from interfering with termination processes for cross-hired employees in active clients.
PD-23969 General Worksite Managers (WSMs) and Worksite Trusted Advisors (WTAs) were unable to assign a WSM from a related company as a PTO Approver or Manager on the Employee Details form. Previously, the system allowed this assignment with a warning, but recent updates caused a hard error that prevented saving and reverted the field to the previous value. The validation logic for the PTO Approver and Manager fields on the Employee Details form was updated. WSMs and WTAs can now assign a WSM from a different company as a PTO Approver or Manager, provided the user has access to both the employee and the assigned WSM through Data Entity Security, and the assigned WSM also has access to the employee.
RRT-6925 General While using the Bulk Change Retirement Plan form to migrate employees to a plan using system-default deduction codes, recurring deduction records were not updated and deductions did not pull during payroll. This is fixed.
RRT-6927 General Users without full access to the Employee Benefit Overview form could still view and modify benefit enrollment workflows from the dashboard. This is fixed. The Benefit Enrollments by Status option now correctly requires full permissions for Service Providers, Worksite Managers, and Worksite Trusted Advisors on both the Enhanced and Legacy Dashboards.
RRT-6957 General Data Retriever reports generated special characters instead of numbers. This is fixed. The system now ensures that report data, including critical 401k information, is displayed accurately.
WSP-4054 General After importing a new Time Off Auto-Enrollment Rule, clicking the “New Rule” button incorrectly opened a form pre-populated with the data from the newly imported rule instead of a blank form. This occurred because the system’s in-memory counter for rule sequence numbers was not refreshed after the background import process completed. The Time Off Auto-Enrollment Rule Maintenance form has been updated to refresh the highest sequence number from the database before calculating the next rule number. This ensures that clicking “New Rule” always opens a blank form for rule creation, regardless of whether the previous rule was created manually or via import.
WSP-4418 General Users encountered an error stating “There are no Import Field Map Definitions that match your spreadsheet” when attempting to import new employees using the Prism-Expanded field mapping, even when using the correct template and file formats. The New Employee Import has been updated to correctly match import mappings without requiring the “INTERNATIONAL.EMPLOYEE” header in the import file when the “INTLEMPLOYEE” Client Functional Constant (CFC) is not enabled. If the “INTLEMPLOYEE” CFC is enabled, the system now properly validates the mapping to include the “INTERNATIONAL.EMPLOYEE” field.
PD-20360 Payroll Timesheet Detail Display Correction This update resolves a display issue in the Timesheet Detail screen that occurred when deleting specific pay entries. Previously, deleting a “Units” pay code (such as “Other”) would cause the system to incorrectly populate the “Hours Paid” field of the remaining entries with the pay rate value, leading to potential confusion during payroll review. - Improved Deletion Logic: Deleting a pay entry now correctly resets the entry form, ensuring that subsequent lines display accurate hours and pay rates. - Accurate Data Visualization: The review screen now maintains the correct “Hours Paid” values for remaining entries after a deletion, preventing misleading information from appearing before saving. - Enhanced Workflow Reliability: While the underlying payroll data remained secure, this fix ensures the visual interface consistently matches the stored records, reducing the need for manual verification. This is fixed.
PD-20628 Payroll The regenerated accounting file displayed the literal <> text instead of the expected DB/CR indicator value. The regenerated file now correctly resolves the token, matching the behavior of the original accounting file generation. We resolved an issue where the <> custom heading in PEO Client Accounting templates did not display correctly when using the Regenerate & Repost Accounting function.
PD-20737 Payroll Users encountered a payroll initialization error when a global voluntary deduction code was marked as obsolete, even if the employee’s recurring deduction record already had a stop date set before the obsolete date. The system was updated to recognize when an employee’s deduction is already stopped. If the employee’s recurring deduction has a stop date that occurs before the pay date, the system will no longer trigger a hard stop error during payroll calculation, even if the global deduction code has been obsoleted. This allows users to maintain historical records for voluntary employee recurring deductions without causing payroll processing issues.
PD-24079 Payroll The “% of Gross Earnings (less Deduction Types)” deduction method (PGDT) was not subtracting all qualifying excluded-type deductions from gross earnings if those deductions were positioned after the PGDT deduction in the employee’s deduction sequence. The payroll calculation logic was updated to ensure that all deductions of the excluded type are subtracted from gross earnings before the percentage is applied, regardless of their position in the employee’s deduction sequence. This ensures accurate calculation of the PGDT deduction base.
RRT-7002 Payroll Previously, on the Process Payroll and Time Sheet Entry forms, resizing the browser window caused the screen to go blank, requiring a manual page refresh to restore the data. Now, this is fixed. Additionally, the Time Sheet form requires a minimum browser form width. If the browser width is insufficient to render the time sheet correctly, an error message, “This process cannot be completed because the screen width is too small. Please increase the screen width and try again.” is displayed to inform the user.
WSP-4121 Payroll When a user role was set to Inquiry access for the Payroll History form, the system automatically protected all input fields, which incorrectly blocked the user from adjusting the year or using other filter options. The Payroll History form has been updated to allow interaction with the year selector, filters, and line chart dropdown even when the user role is set to Inquiry access. Access to individual payroll summaries continues to be governed by the user’s specific role security.
WSP-4160 Payroll Users processing multiple payroll batches in the superbatch encountered an issue where clicking the “Print all” button caused batches to automatically ship and disappear from the superbatch view, even when the Auto Mail field in System Parameters was empty. This prevented users from selecting the “Shipped” icon to run reports and print checks manually. The superbatch “Print all” functionality was updated to correctly respect the Auto Mail settings in System Parameters and the Paperless delivery settings in Client Details. The process now correctly determines whether to skip the “ship” step based on these configurations, ensuring that batches only auto-ship when intended and remain visible in the superbatch for manual shipping when required.
WSP-4252 Payroll The payroll process was not correctly respecting the FLSA exempt status for employees assigned to a remote position classification. When a position was configured with a remote position classification that was FLSA exempt, but the standard position classification was non-exempt, the payroll engine incorrectly applied non-exempt rules (such as half-pay calculations) to the remote employee. The payroll calculation logic was updated to ensure that the FLSA exempt status assigned to a remote position classification is appropriately respected during payroll processing, even if the standard position classification on the same position setup is non-exempt.
WSP-4336 Payroll The system did not post the deduction import amounts in the Time Sheet Deduction Import form for all employees in the import. In addition, the payroll vouchers posted these values as a lesser amount, with the decimal point over-adjusted two places to the left. This is fixed.
WSP-4406 Payroll Customers reported that delivery sheets were being automatically generated and printed with payroll reports (such as checks), even when the system was configured not to include them. This occurred specifically when the Paperless Delivery option was set to “all payroll output.” The payroll reporting process has been updated to correctly respect the Paperless Delivery configuration. Delivery sheets will no longer be generated or included in consolidated payroll reports when they are not required by the client’s setup.
RRT-7009 System Users with custom URLs intermittently encountered a “Nonce mismatch” error or were incorrectly redirected to the legacy login screen. This is fixed. The login process now correctly redirects to the PrismONE ID landing page by default.
WSP-4577 System When a client was terminated and the option to terminate active employees was selected as Yes, the system was not inactivating the employees as part of the client termination process. This issue occurred even after a warning message was displayed and confirmed by the user. The client termination process was updated to ensure that active employees are correctly terminated when the corresponding option is selected during the client termination workflow.

========================================================================

July (R_202607)

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/2026/07/whatsnew-R_202607.htm Path: Release-Notes/2026/07/whatsnew-R_202607.htm

Welcome

PrismHR software is specifically designed to help Professional Employer Organizations (PEOs) and Administrative Services Organizations (ASOs) reduce risk, be more efficient, expand business, and be more profitable.

When you choose PrismHR, you are choosing more than just a software platform. You are partnering with a team of professionals who are deeply invested in the PEO and ASO industry and dedicated to providing the best technology and services possible. You are also partnering with other professionals in the industry in the sense that we all learn from each other.

To view release notes for PrismHR, click any of the links in the Table of Contents. Each release is represented with a book that features the month and year. Click these books to expand product names and version numbers for the release. The most recent documents are at the top of the list. Use the Search feature to look for a specific keyword or phrase. Open any PDFs for Download book to view and print release notes documents from the past year.

Documentation Enhancements

Click a link to read about the documentation enhancements included in this release.

Task Sheets

To provide a better customer experience, new or improved task sheets are available in the in-product Help. In the table of contents, you can select the Task Sheets topic (located just below User Guide PDFs) to display a list of the most current task sheets. For example:

[Image: screenshot]

Release Notes: Enhancements and Fixes

You can view release notes in a variety of formats. You can:

========================================================================

Accounting Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Accounting_Enhancements.htm Path: Release-Notes/Shared-Files/Accounting_Enhancements.htm

Accounting Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Before You Begin

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Before_You_Begin.htm Path: Release-Notes/Shared-Files/Before_You_Begin.htm

Before You Begin

Note: Note: For the best experience, refresh your browser or clear your history to ensure that you see the latest features, styles, images, and in-product help in PrismHR.

Note: NOTE FOR USER ADMINISTRATORS

When there are new forms in this release, you must add the forms manually to user roles to grant users access to them. This ensures security because users do not get automatic access to new forms.

  1. Open User Roles (found in the Back Office menu [Image: screenshot] under System|Change).

  2. Open the user role.

  3. Click Add. The maintenance form opens, listing new forms and those that were previously removed from the role.

  4. Select only the forms that are appropriate for the role.

  5. Click Accept.

  6. Click Save.

See the Release Features for the newest forms and features in PrismHR.

========================================================================

Benefits Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Benefits_Enhancements.htm Path: Release-Notes/Shared-Files/Benefits_Enhancements.htm

Benefits Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

For the best experience, clear your cache

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Best_Experience_Refresh.htm Path: Release-Notes/Shared-Files/Best_Experience_Refresh.htm

Important! Always refresh your browser or clear your cache to ensure that you see the latest features, styles, images, and in-product help in PrismHR.

To clear your Chrome cache:

========================================================================

Billing Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Billing_Enhancements.htm Path: Release-Notes/Shared-Files/Billing_Enhancements.htm

Billing Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Client Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Client%20Enhancements.htm Path: Release-Notes/Shared-Files/Client Enhancements.htm

Client Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Documentation Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Documentation_Enhancements.htm Path: Release-Notes/Shared-Files/Documentation_Enhancements.htm

Documentation Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Employer Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Employer_Enhancements.htm Path: Release-Notes/Shared-Files/Employer_Enhancements.htm

Employer Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Enhancements.htm Path: Release-Notes/Shared-Files/Enhancements.htm

Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

HR Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/HR_Enhancements.htm Path: Release-Notes/Shared-Files/HR_Enhancements.htm

HR Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Known Issues

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Known_Issues.htm Path: Release-Notes/Shared-Files/Known_Issues.htm

Known Issues

Click a link to learn about the known issues in this release.

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Other%20Enhancements.htm Path: Release-Notes/Shared-Files/Other Enhancements.htm

Other Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Other Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Other_Enhancements.htm Path: Release-Notes/Shared-Files/Other_Enhancements.htm

Other Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Payroll Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Payroll_Enhancements.htm Path: Release-Notes/Shared-Files/Payroll_Enhancements.htm

Payroll Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

PTO Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/PTO_Enhancements.htm Path: Release-Notes/Shared-Files/PTO_Enhancements.htm

PTO Enhancements

Click a link to read about the enhancements included in this release.

========================================================================

Release Features

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Release_Features.htm Path: Release-Notes/Shared-Files/Release_Features.htm

Release Features

Click a link to read about the features included in this release.

========================================================================

Release Highlights

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/Release_Highlights.htm Path: Release-Notes/Shared-Files/Release_Highlights.htm

Release Highlights

Click a link to read about the enhancements included in this release.

========================================================================

System Enhancements

Source: https://tech-docs.prismhr.com/SP_help/Content/Release-Notes/Shared-Files/System_Enhancements.htm Path: Release-Notes/Shared-Files/System_Enhancements.htm

System Enhancements

Click a link to read about the enhancements included in this release.