District of Columbia SUTA Electronic Filing - ICESA record types A, E, and S updates in DCETS

The Department of Employment Services (DOES) will transition to their modernized tax system, District of Columbia Employer Tax System (DCETS), for UI Tax program services. The new system will replace the existing Employee Self Service Portal (ESSP) in January 2023 according to the state. The SUTA file updates for the District of Columbia will be reflected if the system date in Costpoint is from January 2023.

The following will be implemented in the new system:

• Employers will be allowed to report out-of-state quarterly taxable wages submitted to U.S. states other than the District of Columbia (Including the 50 U.S. States, Puerto Rico, and the U.S. Virgin Islands).

• Employers will be required to report the state to which any reported Out-of-State Taxable Wages are paid.

• Within the Wage Amendment Process, employers will be required to select a reason for the amendment at the employee level and provide a narrative description when “Other” is reported as the reason. The new requirements are detailed within the individuated sections for each file type.

According to DOES, the requirements for the following have been updated:

• Employer ICESA Record Type A: Fields 208-275

• Employer ICESA Record Type E: Fields 149-158

• Employer ICESA Record Type S: Fields 135-275

Attention: Please see the DCETS Wage File Format Specifications for the complete ICESA file layout, and the file layouts of other available file types (EFW2, XML, and CSV).

 

Manage SUTA Quarterly Reporting Data (PRMQRD)

The Manage SUTA Quarterly Reporting Data screen features the following updates:

• The screen provides the following new fields:

Field	Description
Adjustment SUTA State	Enter, or click lookup to select, the state to which you will report the amendment.
Adjustment Reason Description	This field displays the description of the code you entered in the Adjustment Reason Code field.

• This release adds a SUTA State Code (SUTA_STATE_CD) column to the SUTA Adjustment Reason Code (S_SUTA_ADJ_RSN_CD) system table. Data for District of Columbia was added in the S_SUTA_ADJ_RSN_CD system table.

• The lookup function in the Adjustment Reason Code field was updated based on the Adjustment SUTA State.

• The screen displays an error if the explanation text exceeds 25 characters for District of Columbia.

 

Manage SUTA Tax File Data (PRMSMM)

The Manage SUTA Tax File Data screen provides the following validations for the District of Columbia:

• An error displays when the value for location exceeds three characters. The field Location/Unit (S 162-164) has a length of only 3 characters in the Employer ICESA file layout.

• An error displays when the E-mail field is blank.

 

Create Quarterly SUTA Tax File (PRPSMM)

The Create Quarterly SUTA Tax File screen was updated to support the updated ICESA records A, E, and S for the District of Columbia.

Twilio for SMS Notifications

 

You can now use Twilio, a third-party SMS messaging service, for Costpoint text message notifications. Connect to a Twilio account using the new Twilio Integration tab in the Manage System Integration Accounts application. To connect to Twilio, you have to specify the following parameters:

• Twilio account SID

• API key

• API key secret

• From phone number

These four parameters are available in your account in the Twilio Console in the API Keys and Tokens section. In Twilio, click Create API Key to get the parameter values for Costpoint.

 

Note: You must run Rebuild Global Settings to implement the update.

The Costpoint MR installer now includes support for SSL between a WebLogic admin node and database server.

Prior to this release, the computation of the Health Savings Account (HSA) deduction amount was not accurate when an employee changes election types (for example, from Single to Family) during the year. This occurred if the previous and new election had different deduction codes assigned.

To address this issue, the Manage Pay Periods screen will feature a new setting, FSA/HSA Deduction Method, which allows you to set the basis of the FSA/HSA deduction calculation. When you run the update deductions process in related Costpoint applications, the new FSA/HSA Deduction Method setting will be used to calculate the deduction amount based on the check date or pay period end date.

 

Manage Pay Periods (PRMPRPD)

The Manage Pay Periods screen provides the following new field:

Field

Description

FSA/HSA Deduction Method

Use this drop-down list to specify how FSA/HSA premiums will be calculated for employees in this pay cycle. Costpoint's Update Employee Package Deductions application will use this setting to ensure the FSA/HSA deductions will be calculated correctly based on the selected date and the amount previously deducted for that year: Calculate based on the pay period end date: Select this option if you want to calculate the FSA/HSA premium based on the YTD previously deducted based on the open pay period end date. Calculate based on the check date: Select this option if you want to calculate the FSA/HSA premium based on the YTD previously deducted based on the current check date. Note: This drop-down list is available if you are licensed for Costpoint Human Resources (HR) - Benefits.

 

Update Employee Package Deductions (HBPAPDED)

The Update Employee Package Deductions application features the following updates:

• The Pay Period Setup group box provides a field that displays the assigned FSA/HSA Deduction Method for the pay period.

Field

Description

FSA/HSA Deduction Method

This disabled field displays the value from the FSA/HSA Deduction Method field for the selected pay period. It replaces the Base FSA/HSA on Check Date check box so the logic can be set at the pay period level. The options displayed are: Calculate based on the check date: If Calculate based on the check date is displayed, the Update Employee Package Deductions application will use the remaining number of check dates that fall within the Medical FSA Plan Year to determine the deduction amount. For example: Medical FSA Election Amount = 1,000.00 Number of Remaining Check Dates in the 2018 Plan Year = 5 (08/07/18, 09/07/18, 10/07/18, 11/07/18 & 12/07/18) Deduction Amount = 1,000.00 / 5 = 200.00 Calculate based on the open pay period end date: If Calculate based on the open pay period end date is displayed, the FSA/HSA deduction amount will be based on the number of pay period end dates remaining in the FSA/HSA plan year (rather than using the number of checks remaining in the FSA/HSA plan year). For example, you have a new employee that elects Medical FSA as of 07/13/2018, your Medical FSA plan year is from 01/01/2018 to 12/31/2018, and your pay periods are as follows (using monthly pay frequency for simplicity): Start Date End Date Check Date 01/01/2018 01/31/2018 02/07/2018 02/01/2018 02/28/2018 03/07/2018 03/01/2018 03/31/2018 04/07/2018 04/01/2018 04/30/2018 05/07/2018 05/01/2018 05/31/2018 06/07/2018 06/01/2018 06/30/2018 07/07/2018 07/01/2018 07/31/2018 08/07/2018 08/01/2018 08/31/2018 09/07/2018 09/01/2018 09/30/2018 10/07/2018 10/01/2018 10/31/2018 11/07/2018 11/01/2018 11/30/2018 12/07/2018 12/01/2018 12/31/2018 01/07/2019 The Update Employee Package Deductions application will use the remaining number of Pay Period End Dates that fall within the Medical FSA Plan Year to determine the deduction amount. Medical FSA Election Amount = 1,000.00 Number of Remaining Pay Periods in the 2018 Plan Year = 6 (07/31/18, 08/31/18, 09/30/18, 10/31/18, 11/30/18 & 12/31/18) Deduction Amount = 1,000.00 / 6 = 166.67

• The Base FSA/HSA on Check Date check box was removed.

• The application includes all HSA deductions when calculating the election limits and YTD amount deductions. This allows you to ensure that employees do not go over the HSA limit if they change election types part way through the year. Each election type may have a different yearly limit, and all HSA contributions should count towards that limit.

• Elections that were ended through a life event and processed through the Activate Pending Benefit Elections screen are also ended by the Update Employee Package Deductions process.

• The Deductions Contributions Timing field is now the Benefit Deduction Method field.

• The error report will display a warning if any data exists in the HB_HSA_ELEC_DUPLICATES table.

 

Life Events/New Hires (ESMLIFEEVENT)

When the update deduction process is run, the application will use the new FSA/HSA Deduction Method on the Manage Pay Periods screen to calculate the deduction amount based on either the check date or pay period end date. This functionality applies to the HSA, Dependent FSA, and Medical FSA tabs.

In addition, the HSA tab features the following new validations:

• A new validation was added to ensure that the employee is or will turn 55 by the end of the HSA year. If the HSA election type selected is either Single with Catch-Up or Family with Catch-Up, the application will use the employee’s birth date in the EMPL table to ensure that the employee will be 55 or older during the calendar year.

• A new validation was added to ensure that if an employee changes an HSA election type mid-year, the deduction amounts are correctly calculated and the employee does not go over the yearly limit. The different election types may or may not use the same deduction, but the system should consider either situation when calculating limits.

 

Benefits Enrollment (ESMBENENROLL)

When the update deduction process is run, the application will use the new FSA/HSA Deduction Method on the Manage Pay Periods screen to calculate the deduction amount based on either the check date or pay period end date. This functionality applies to the HSA, Dependent FSA, and Medical FSA tabs.

In addition, the HSA tab features a new validation that was added to ensure that the employee is or will turn 55 by the end of the HSA year. If the HSA Election Type selected is either Single with Catch-Up or Family with Catch-Up, the application will use the employee’s Birth Date in the EMPL table to ensure that the employee will be 55 or older during the calendar year.

 

Manage Employee HSA Elections (EMMEHSA)

The Manage Employee HSA Elections screen features the following updates:

• When the update deduction process is run, the application will use the new FSA/HSA Deduction Method on the Manage Pay Periods screen to calculate the deduction amount based on either the check date or pay period end date.

• A new validation was added to allow only positive amounts for the election amount since negative numbers are not allowed for the HSA election amount.

• A new validation was added to ensure that the employee is or will turn 55 by the end of the HSA year. If the HSA election type selected is either Single with Catch-Up or Family with Catch-Up, the application will use the employee’s Birth Date and election date to ensure that the employee will be 55 or older before the end of the calendar year. This will vary based on whether the plan year covers two calendar years or one.

• A new validation was added to ensure that if an employee changes an HSA election type mid-year, the deduction amounts are correctly calculated and the employee does not go over the yearly limit. The different election types may or may not use the same deduction, but the system should consider either situation into account when calculating limits.

• The database keys in the HB_HSA_ELEC table were changed to EMPL_ID and EFFECT_DT. The previous database keys were EMPL_ID, PLAN_YR_NO, and HSA_TYPE.

• If there are any records in HB_HSA_ELEC table where the EMPL_ID and EFFECT_DT are identical to another record, the application will leave the record with the most recent timestamp in HB_HSA_ELEC table. Other identical records will be deleted from HB_HSA_ELEC and inserted into the HB_HSA_ELEC_DUPLICATES table.

Note: The application provides validations that will not allow you to enter duplicate EMPL_ID and EFFECT_DT records on the screen (front end). This situation will only occur if you add duplicate data to the database (back end). When you run the Update Employee Package Deductions process, you will receive a warning message about the duplicate data.

 

Manage Employee Dependent Care FSA Elections (HBMEFSA)

When the update deduction process is run, the application will use the new FSA/HSA Deduction Method on the Manage Pay Periods screen to calculate the deduction amount based on either the check date or pay period end date.

 

Manage Employee Medical Care FSA Elections (HBMMFSA)

When the update deduction process is run, the application will use the new FSA/HSA Deduction Method on the Manage Pay Periods screen to calculate the deduction amount based on either the check date or pay period end date.

 

Manage Open Enrollment Elections (AOMESSBE)

A new validation was added to ensure that the employee is or will turn 55 by the end of the HSA year. If the HSA election type selected is either Single with Catch-Up or Family with Catch-Up, the application will use the employee’s birth date on the EMPL table to ensure that the employee will be 55 or older during the calendar year.

 

Manage Life Event Elections (AOMESSBL)

The Manage Life Event Elections screen features the following new validations:

• A new validation was added to ensure that the employee is or will turn 55 by the end of the HSA year. If the HSA election type selected is either Single with Catch-Up or Family with Catch-Up, the application will use the employee’s birth date in the EMPL table to ensure that the employee will be 55 or older during the calendar year.

• A new validation was added to ensure that if an employee changes an HSA election type mid-year, the deduction amounts are correctly calculated and the employee does not go over the yearly limit. The different election types may or may not use the same deduction, but the system should consider either situation when calculating limits.

 

Activate Pending Benefit Elections (AOPESSUE)

The primary keys of the HB_HSA_ELEC table were changed to EMPL_ID and EFFECT_DT. The previous primary keys were EMPL_ID, PLAN_YR_NO, and HSA_TYPE. The Activate Pending Benefit Elections screen was updated to support the primary key changes.

 

Print Data Dictionary Report (SYRDD)

The Print Data Dictionary Report now provides information for the new field (HBPAPDED_FHSA_MTHD_CD) to the Pay Period (PAY_PD) table.

This release applies changes to timesheet, leave, and pay period screens in Costpoint for improved usability.

 

Manage Timesheet Periods (LDMTSPD)

The Manage Timesheet Periods screen features the following updates:

• The screen layout was updated for consistency with other period screens in Costpoint.

• The group box for the Timesheet Cycle Code and Description fields were removed.

• The Details group box was removed. Existing fields remain on the screen.

• The Timesheet Cycle Code field is now the Timesheet Cycle field.

• The Compute Last End Date button was removed and replaced with automatic defaulting.

• The Add Periods button is now the Add Timesheet Periods button.

• The Timesheet Periods link was removed and the existing Timesheet Period table now displays on the main screen.

 

Manage Leave Periods (LDMLVPD)

The Manage Leave Periods screen features the following updates:

• The screen layout was updated for consistency with other period screens in Costpoint.

• The Leave Cycle Code and Description fields are no longer in a group box.

• The Leave Cycle Code field is now the Leave Cycle field.

• The Details group box was removed. Existing fields remain on the screen.

• The screen provides the following new fields:

Field	Description
Open Leave Period Start Date	This field displays the start date of the leave cycle's open leave period. If you manually change the open leave period on the Leave Periods subtask, this value will be updated. If there is no open leave period, this field will be blank.
Open Leave Period End Date	This field displays the end date of the leave cycle's open leave period. If you manually change the open leave period on the Leave Periods subtask, this value will be updated. If there is no open leave period, this field will be blank.

• The Compute Last End Date button was removed and replaced with automatic defaulting.

• The Leave Periods subtask link was removed and the Leave Periods table now displays on the main screen.

• When you select the Open check box of a leave period in the Leave Periods table, the application clears the check boxes of other periods in the table.

• The screen will not allow you to change the leave year when used or accrued leave has been posted to it.

 

Manage Pay Periods (PRMPRPD)

The Manage Pay Periods screen features the following updates:

• The screen provides new fields that will allow you to set up default check dates when you add new pay periods. The screen also provides fields that display the start and end date of the open pay period.

Field	Description
Check Date (Days following pay period end date)	If you would like to default the check dates when you click the Add Pay Periods button and new pay periods are added, enter the number of days after the pay period end dates on which the check dates will fall. For example, if your check dates are normally five days following the end of the pay period, enter 5 in this field. If the pay period end date is Sunday, 5/1/2022 and you specify that the check date is 5 days following the pay period end date, the check date would be Friday, 5/6/2022. You may also opt to override the calculated check date if it falls on a weekend day so that the check date is set to the preceding Friday. After adding pay periods, you may edit the check dates in the Pay Periods table. If you leave this blank, no check date will default.
Use prior Friday if check date falls on a weekend	If you are defaulting the check date when adding new pay periods, select this check box if you want to exclude weekends (Saturday and Sunday) when determining the check date. Note: This check box is visible only if you enter a value in the Check Date (Days following pay period end date) field. If you select this check box and the calculated check date falls on a weekend (Saturday or Sunday), the check date will be set to the Friday preceding the weekend. For example, if the pay period end date is Tuesday, 3/15/2022, and you specify that the check date is 4 days following the pay period end date, the calculated check date would be Saturday, 3/19/2022. If you select this check box, the calculated check date would instead be set to 3/18/2022 since it is the Friday that precedes the weekend on which the calculated check date fell. You may still edit the check dates in the Pay Periods table if you select this check box.
Open Pay Period Start Date	This field displays the start date of the pay cycle's open pay period. If you manually change the open pay period in the Pay Periods table, this value will be updated. If there is no open pay period, this field will be blank.
Open Pay Period End Date	This field displays the end date of the pay cycle's open pay period. If you manually change the open pay period in the Pay Periods table, this value will be updated. If there is no open pay period, this field will be blank.

• The existing Update Employee Package Deductions-Deduction/Contribution Timing options are now available in the Benefit Deduction Method drop-down list.

• The Pay Cycle, Description, and Frequency fields are no longer in a group box.

• The FSA/HSA Deduction Method options are now in a drop-down list.

• The Payroll Year to be Added field is now the Payroll Year field.

• The screen now adds the ability to set a default value in the Last End Date field automatically. Prior to this release, the field was never populated.

• The Compute Last End Date button was removed and replaced with an automatic defaulting functionality.

• The ADD button is now the Add Pay Periods button.

• The Pay Cycle Schedule subtask link was removed. The existing table on the subtask was renamed to “Pay Periods” and transferred to the main screen.

• The Open Flag check box is now the Open check box. When you select the Open check box for a pay period, the application clears the check box for all other periods in the table.

• The screen layout was updated to be able to accommodate new fields and for consistency with other period screens in Costpoint.

Costpoint now provides the ability to track employee vaccinations. You may use this new functionality for the following purposes:

• To monitor the vaccination of your employees for certain diseases

• To ensure required vaccines are up-to-date for employees who are travelling overseas

This feature allows employees to update their vaccination details as well as upload file attachments for the verification of their vaccination status or vaccination exemption.

 

Manage Vaccine Types (EMMVACCINE)

The new Manage Vaccine Types screen allows you to add vaccine types for your company. You can then assign these vaccine types to an employee record. Each vaccine type must be unique. For example, you could add records for COVID19, Shingles, Influenza, and others.

 

Manage Employee Vaccinations (EMMEVACCINE)

The new Manage Employee Vaccinations screen allows you to track and verify employees' vaccination status or vaccination exemption. This screen displays the vaccine information that employees enter on the Employee Vaccinations screen in Costpoint Employee Self Service. Each vaccine record has a verification check box that can be selected after the employer verifies the vaccine information.

 

Employee Vaccinations (ESMEVACCINE)

Employees can use the new Employee Vaccinations screen to enter details for each of their vaccinations or exemptions for vaccinations. Employees can attach multiple files for the approval of their vaccination status or vaccination exemption.

 

Manage Custom Text (ESMCUSTTXT)

You can now select the Employee Vaccinations option from the Screen/Application drop-down list. This allows you to enter custom instructions for employees, which will display on the Instructions subtask of the Employee Vaccinations screen.

 

Configure Labor Settings (LDMLABOR)

The Configure Labor Settings screen provides the following new field:

Field	Description
Vaccine Info Storage Location	Enter, or click lookup to select, the default storage location when an employee uploads files with vaccination information on the Employee Vaccinations screen.

 

Set Up Company (SYPCOMP)

When you set up a new company, the Vaccine Info Storage Location field value of the company selected to be copied will be the default value for the new company.

 

Print Data Dictionary Report (SYRDD)

The Print Data Dictionary Report was updated to reflect the databases changes for this feature.

The Commonwealth of Pennsylvania requires employers to withhold local earned income tax (EIT) from employees who work and/or live in Pennsylvania. The local EIT will be based on the EIT rates for the political subdivision (PSD) where the employee works and/or lives. If an employee both works and lives in Pennsylvania, the employee pays the local taxes based on the higher EIT.

To determine the EIT tax rate that an employee owes, the employer must do the following:

• Determine the political subdivision (PSD) in which the employee lives and/or works.

• Determine the earned income tax rate for the Resident PSD and/or the Worksite PSD.

• Determine the tax collection district where to remit the taxes.

There are roughly 70 tax collection districts in Pennsylvania, and there are thousands of political subdivisions in Pennsylvania. Instead of setting up local tax codes for each political subdivision, this enhancement allows employers to set up a local for each tax collection district.

Since there can be several different PSD earned income tax rates within one tax collection district, Costpoint provides the ability to assign the earned income tax rate to the employee. For this purpose, Costpoint adds a new Override Percent field on the Local Taxes subtask of the Manage Employee Taxes screen.

Data Setup Instructions for Employers with Pennsylvania Employees

For employers with employees who live and/or work in Pennsylvania, Deltek recommends using the following data setup:

1. On the Manage Local Taxes screen, set up a Local Tax for each Pennsylvania tax collection district to which taxes will be paid.

2. On the Local Taxes subtask of the Manage Employee Taxes screen, perform the following:

• Assign the Local Tax to the employees whose taxes will be paid to the tax collection district.

• Enter the employee’s EIT rate in the Override Percent field.

• Enter the employee’s Pennsylvania Resident PSD Code.

• If the employee also works in Pennsylvania, enter the employee’s Pennsylvania Worksite PSD Code.

 

Manage Local Taxes (PRMLTI)

The Manage Local Taxes screen features the following updates:

• The City / County / School / PSD Code field is now the Jurisdiction Code field. In Form view, the screen displays the following labels for the corresponding states:

• County Code (IN): This is the field label if you select IN (Indiana) as the state.

• City Code (MI): This is the field label if you select MI (Michigan) as the state.

• School District (OH): This is the field label if you select OH (Ohio) as the state and School District Income Tax or City Income tax as the tax type.

• District PSD Code (PA): This is the field label if you select PA (Pennsylvania) as the state.

• The fields on the W-2 Reporting subtask were transferred to the main screen. The subtask link was removed.

• The Disability Insurance Type group box is now a drop-down list.

• The Family Leave Insurance Type group box is now a drop-down list.

• The Character Code field was removed.

• Error and warning messages were updated.

• The layout of the Tax ID/Reference Numbers/Vendor Information subtask was updated.

• The State field on the Local Taxes subtask was removed.

 

Manage Employee Taxes (PRMETAX)

The Local tab was removed and replaced with a new Local Tax subtask. The subtask allows you to assign more than five local taxes to an employee. Prior to this release, you can assign only five local taxes to an employee.

In addition to the existing local tax fields, the Local Tax subtask provides the following new fields:

Field	Description
State	This field displays the state assigned to the specified local tax code on the Manage Local Taxes screen. This value is not stored in the database.
Override Percent	To override the system-calculated amount and use a different tax withholding percentage, enter the amount in this numeric field. Costpoint will multiply this override percentage by the local taxable wages to determine the local tax withholding each pay period. This percentage will be used in place of the local tax tables.
Priority	Enter a value between 1 and 9999 in this field to establish the order in which the local tax will be withheld when payroll is computed. One (1) represents the highest priority, and 9999 represents the lowest priority. Numbers do not have to be consecutive but must be unique for a given employee (cannot duplicate the same priority number for the same employee). This value will be used only on the Compute Payroll application.
Start Date	Enter, or click the Calendar icon to select, a date for the local tax to start. This date is normally the pay period start date. If the start date is later than the pay period end date, the local tax starts in the following pay period. Leave this field blank to indicate that the local tax withholding should start immediately.
End Date	Enter, or click the Calendar icon to select, a date through which the local tax must be withheld. This date is normally the pay period end date. Leave this field blank to indicate that this local tax should continue indefinitely.
Pennsylvania Resident PSD Code	Enter the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee lives. If an employee lives in Pennsylvania, you must populate this field. If the employee both lives and works in Pennsylvania, you must withhold the higher of the two EIT Rates, as well as the Local Services Tax (LST), and make remittances to the local tax collector(s) for the worksite location(s). If the employee lives in but physically works outside of Pennsylvania, the DCED states, "As an out-of-state employer, you are NOT required to complete the Residency Certification Form or withhold the local Earned Income Tax (EIT) for a PA resident employee. However, the PA resident employee will still be subject to and owe the "Total Resident EIT Rate" based on their PA home municipality. Therefore, as an out-of-state employer, you may withhold the 'Total Resident EIT Rate' as a courtesy to your PA resident employee and make remittances to the local tax collector for their PA home municipality. If you choose not to withhold and remit, then please notify your PA resident employee that they will be responsible for making quarterly estimated payments on their own directly to the local tax collector(s) for their PA home municipality." According to the Pennsylvania DCED, the Resident PSD Code will be 880000 for an employee that works in but lives outside of Pennsylvania. This field is editable only if the local tax is linked to the state of Pennsylvania (PA) on the Manage Local Taxes screen.
Pennsylvania Worksite PSD Code	Enter the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee works. If the employee lives in but physically works outside of Pennsylvania, you may leave this field blank. According to the Pennsylvania Department of Community and Economic Development, "As an out-of-state employer, you are NOT required to complete the Residency Certification Form or withhold the local Earned Income Tax (EIT) for a PA resident employee. However, the PA resident employee will still be subject to and owe the 'Total Resident EIT Rate' based on their PA home municipality. Therefore, as an out-of-state employer, you may withhold the 'Total Resident EIT Rate' as a courtesy to your PA resident employee and make remittances to the local tax collector for their PA home municipality. If you choose not to withhold and remit, then please notify your PA resident employee that they will be responsible for making quarterly estimated payments on their own directly to the local tax collector(s) for their PA home municipality." This field is editable only if the Local Tax is linked to the state of Pennsylvania (PA) on the Manage Local Taxes screen.
Pennsylvania Local Tax PSD Code	If the local code is linked to the state of PA (Pennsylvania), this field displays the PSD Code assigned to the local code. This value is not stored in the database.

 

View Employee Taxes (PRQETAX)

The Local tab was removed and replaced with a new Local Tax subtask. In addition to the existing local tax fields, the Local Tax subtask provides the following new fields:

Field	Description
State	This field displays the state assigned to the specified local tax code on the Manage Local Taxes screen.
Priority	This field displays a value between 1 and 9999. This establishes the order in which the local tax will be withheld when payroll is computed.
Override Percent	This field displays the employee's local tax override percent as of the transaction date/time. Costpoint will multiply this override percentage by the local taxable wages to determine the local tax withholding each pay period. This percentage will be used in place of the local tax tables.
Start Date	This field displays the date when the local tax starts. This date is normally the pay period start date. If the start date is later than the pay period end date, the local tax starts in the following pay period. If the field is blank, the local tax withholding should start immediately.
End Date	This field displays the date through which the local tax must be withheld. This date is normally the pay period end date. If this field is blank, this local tax continues indefinitely.
Pennsylvania Resident PSD Code	This field displays the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee lives. This field is populated if an employee lives in Pennsylvania.
Pennsylvania Worksite PSD Code	This field displays the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee works, if applicable. If the employee lives in but physically works outside of Pennsylvania, this field may be blank.
Pennsylvania Local Tax PSD Code	If the local code is linked to the state of PA (Pennsylvania), this field displays the PSD Code assigned to the local code. This value is not stored in the database.

 

Compute Payroll (PRPCPR)

The Compute Payroll screen features the following updates:

• The application now uses the data in the EMPL_TAX_LOCAL table as basis of the employee’s local tax setup. Prior to this release, the Compute Payroll process uses the local tax columns in the EMPL_TAX table.

• In order to maintain a history of the employee’s political subdivision codes, the application stores the following values when the EMPL_PAYROLL record is generated:

• The employee’s Pennsylvania Resident PSD Code (PA_PSD_CD value from the EMPL_TAX_LOCAL table)

• The employee’s Pennsylvania Worksite PSD Code (PA_WORK_PSD_CD value from the EMPL_TAX_LOCAL) table

• The local tax code’s Jurisdiction Code from the Manage Local Taxes screen (SCHOOL_CD value from the LOCALITY table)

• When populating the EMPL_PR_LOCAL table, the application stores the following data:

• Local Tax

• State

• Priority

• State

• Filing Status

• Exemptions

• Dependents

• Credit

• Override Amount (per pay period)

• Override Percent

• Additional Amount (per pay period)

• Pennsylvania Resident PSD Code

• Pennsylvania Worksite PSD Code

• Pennsylvania Local Tax PSD Code

 

Manage Payroll Records (PRMPTF)

The Manage Payroll Records screen features the following updates:

• The Local subtask provides the following new fields:

Field	Description
State	This field displays the state assigned to the specified local code on the Manage Local Taxes screen.
Override Percent	This field displays the Override Percent assigned to the employee and local code on the Local Taxes subtask of the Manage Employee Taxes screen. If the override percentage is specified, Costpoint will multiply this by the local taxable wages to determine the local tax withholding each pay period. This percentage will be used in place of the local tax tables.
Priority	This field displays the priority in which the local tax was withheld. This is based on the Priority assigned to the employee's Local Tax code on the Manage Employee Taxes screen. If a row is manually entered on the Local Taxes subtask of the Manage Payroll Records screen, this field will remain blank.
Pennsylvania Resident PSD Code	This field displays the Pennsylvania political subdivision (PSD) Code assigned to the municipality in which the employee lives. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Resident PSD Code from the Local Tax subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Worksite PSD Code	This field displays the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee works. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Worksite PSD Code from the Local Tax subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Local Tax PSD Code	If the local code is linked to the state of PA (Pennsylvania), this field displays the PSD Code assigned to the local code This field is populated when payroll is computed or when the record is recalculated. The source of the data is the jurisdiction code assigned to the local code on the Manage Local Taxes screen.

• If Edit Payroll audit tracking is enabled for the login company, the application stores the following values from the EMPL_PR_LOCAL to the EMPL_PR_LOCAL_ADT table when a record is added, updated, or deleted:

• PA_RESIDENT_PSD_CD

• PA_WORK_PSD_CD

• PA_LOCALITY_PSD_CD

• STATE_CD

• PRIORITY_NO

 

View Payroll Edit Table (PRQPTF)

The Local subtask provides the following new fields:

Field	Description
State	This field displays the state assigned to the specified local code on the Manage Local Taxes screen.
Priority	This field displays the priority in which the local tax was withheld. This is based on the Priority assigned to the employee's Local Tax code on the Manage Employee Taxes screen. If a row is manually entered on the Local Taxes subtask of the Manage Payroll Records screen, this field will remain blank.
Pennsylvania Resident PSD Code	This field displays the Pennsylvania political subdivision (PSD) Code assigned to the municipality in which the employee lives. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Resident PSD Code from the Local Taxes subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Worksite PSD Code	This field displays the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee works. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Worksite PSD Code from the Local Taxes subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Local Tax PSD Code	If the local code is linked to the state of PA (Pennsylvania), this field displays the PSD Code assigned to the local code This field is populated when payroll is computed or when the record is recalculated. The source of the data is the jurisdiction code assigned to the local code on the Manage Local Taxes screen.

 

Post Payroll Journal (PRPPPCLS)

The Post Payroll Journal process was updated to populate the new columns in the EMPL_EARN_LOCAL table.

 

Manage Employee Earnings History (PRMERF)

The Manage Employee Earnings History screen features the following updates:

• The Local subtask provides the following new fields:

Field	Description
State	This field displays the state assigned to the specified local code on the Manage Local Taxes screen.
Override Percent	This field displays the Override Percent assigned to the employee and local code on the Local Taxes subtask of the Manage Employee Taxes screen. If the override percentage is specified, Costpoint will multiply this by the local taxable wages to determine the local tax withholding each pay period. This percentage will be used in place of the local tax tables.
Priority	This field displays the Priority assigned to the specified local tax code. This value indicates the order in which the local tax was withheld.
Pennsylvania Resident PSD Code	This field displays the Pennsylvania political subdivision (PSD) Code assigned to the municipality in which the employee lives. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Resident PSD Code from the Local Taxes subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Worksite PSD Code	This field displays the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee works. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Worksite PSD Code from the Local Taxes subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Local Tax PSD Code	If the local code is linked to the state of PA (Pennsylvania), this field displays the PSD Code assigned to the local code. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the jurisdiction code assigned to the local code on the Manage Local Taxes screen.

• If Employee Earnings audit tracking is enabled for the login company, the application stores the following values from the EMPL_EARN_LOCAL table to the EMPL_E_LOCAL_ADT table when a record is added, updated, or deleted:

• PA_RESIDENT_PSD_CD

• PA_WORK_PSD_CD

• PA_LOCALITY_PSD_CD

• STATE_CD

• PRIORITY_NO

• The Type field is now disabled. When you enter a new record, the value defaults to Z, which is the only valid type for new records on this screen.

• If you entered a Z record for an employee, the employee’s local tax values will default from the EMPL_TAX_LOCAL table. The local taxes assigned to the employee in EMPL_TAX_LOCAL will be automatically calculated for the employee.

• When you enter a new record and you change the Employee ID, the application will mark any existing Local Tax rows as deleted and calculate local taxes based on the employee’s EMPL_TAX_LOCAL records.

• If you add a new row on the Local Taxes subtask, the PA Resident PSD Code, PA Worksite PSD Code, PA Local Tax PSD Code, State, and Priority Number values will default from the employee’s EMPL_TAX_LOCAL and LOCALITY setup.

• When a Local Tax record is recalculated, the PA Resident PSD Code, PA Worksite PSD Code, PA Local Tax PSD Code, State, and Priority Number values will not default from the employee’s EMPL_TAX_LOCAL and LOCALITY setup.

 

View Employee Earnings (PRQERF)

The Local subtask provides the following new fields:

Field	Description
State	This field displays the State assigned to the specified local tax code.
Override Percent	This field displays the Override Percent assigned to the employee and local code on the Local Taxes subtask of the Manage Employee Taxes screen. If the override percentage is specified, Costpoint will multiply this by the local taxable wages to determine the local tax withholding each pay period. This percentage will be used in place of the local tax tables.
Priority	This field displays the Priority assigned to the specified local tax code. This value indicates the order in which the local tax was withheld.
Pennsylvania Resident PSD Code	This field displays the Pennsylvania political subdivision (PSD) Code assigned to the municipality in which the employee lives. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Resident PSD Code from the Local Taxes subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Worksite PSD Code	This field displays the Pennsylvania political subdivision (PSD) code assigned to the municipality in which the employee works. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the Pennsylvania Worksite PSD Code from the Local Taxes subtask on the employee's Manage Employee Taxes screen.
Pennsylvania Local Tax PSD Code	If the local code is linked to the state of PA (Pennsylvania), this field displays the PSD Code assigned to the local code. This field is populated when payroll is computed or when the record is recalculated. The source of the data is the jurisdiction code assigned to the local code on the Manage Local Taxes screen.

 

Void/Replace Posted Paychecks (PRPAVCK)

The Void/Replace Posted Paychecks screen features the following updates:

• When a V record is generated, the application copies the following values from the voided earnings record in the EMPL_EARN_LOCAL table to the V payroll record in the EMPL_PR_LOCAL table:

• Pennsylvania Resident PSD Code (PA_RESIDENT_PSD_CD)

• Pennsylvania Worksite PSD Code ( PA_WORK_PSD_CD)

• Pennsylvania Local Tax PSD Code (PA_LOCALITY_PSD_CD)

• State (STATE_CD)

• Priority (PRIORITY_NO)

• When a W record is generated, the application copies the following values from the voided earnings record in the EMPL_EARN_LOCAL table to the W payroll record in the EMPL_PR_LOCAL table:

• Pennsylvania Resident PSD Code (PA_RESIDENT_PSD_CD)

• Pennsylvania Worksite PSD Code (PA_WORK_PSD_CD)

• Pennsylvania Local Tax PSD Code (PA_LOCALITY_PSD_CD)

• State (STATE_CD)

• Priority (PRIORITY_NO)

• The application was updated to allow you to void/replace multiple checks at one time. Prior to this release, you could void and replace only one check at a time. For this purpose, the screen provides the following new/updated fields:

Field	Description
Selection Method	Select the method that will be used to select paychecks for processing. Selection Ranges: Select this option to use the fields in the Selection Ranges group box to select paychecks. Non-Contiguous Paycheck List: Select this option to specify a non-contiguous paycheck list. Specify the checks that you want to process on the Non-Contiguous Paychecks subtask.
Record Type	From the drop-down list, select the type of paycheck record to be voided. The options are: R B X Y You can process only one record type at a time. This field is editable only if the Selection Method is Selection Ranges.
Employees	From the drop-down list, select the type of range that will be used to select employees for processing. You have the following options: All: Select this option to include all employees that have paychecks that meet the other selection criteria. One: Select this option to void paychecks for a specific employee. Range: Select this option to void paychecks for a range of employees. The process will include employees with IDs that are greater than or equal to the starting employee value and less than or equal to the ending employee value. This field is editable only if the Selection Method is Selection Ranges.
Employee Range Type	From the drop-down list, select the type of range that will be used to select employees for processing. You have the following options: All: Select this option to include all employees that have paychecks that meet the other selection criteria. One: Select this option to void paychecks for a specific employee. Range: Select this option to void paychecks for a range of employees. The process will include employees with IDs that are greater than or equal to the starting employee value and less than or equal to the ending employee value. This field is editable only if the Selection Method is Selection Ranges.
Starting Employee	If your employee range type is One, enter, or click lookup to select, the employee to be processed. If your range selection is Range, enter, or click lookup to select, the starting employee for the range. This data field is not editable if the employee range type is All.
Ending Employee	Enter, or click lookup to select, the ending employee ID for the range you want to include in the processing. This field is available only if you select an employee range type of Range.
Check Number Range Type	From the drop-down list, select the type of range that will be used to select check numbers for processing. You have the following options: All: Select this option to include all check numbers. One: Select this option to void paychecks for a specific check number. Range: Select this option to void paychecks for a range of check numbers. The process will include check numbers that are greater than or equal to the starting check number value and less than or equal to the ending check number value. This field is editable only if the Selection Method is Selection Ranges.
Starting Check Number	If your check number range type is One, enter, or click lookup to select, the check number to be processed. If your range type is Range, enter, or click lookup to select, the starting check number for the range. This data field is not editable if the check number range type is All.
Ending Check Number	Enter, or click lookup to select, the ending check number for the range you want to include in the processing. This field is available only if you select a check number range type of Range.
Check Date Range Type	From the drop-down list, select the type of range that will be used to select check dates for processing. You have the following options: All: Select this option to include all check dates. One: Select this option to void paychecks for a specific check date. Range: Select this option to void paychecks for a range of check dates. The process will include check dates that fall within the specified starting check date and ending check date.
Starting Check Date	If your check date range type is One, enter, or click lookup to select, the date of the paycheck to be processed. If your range type is Range, enter, or click lookup to select, the starting check date for the range. This data field is not editable if the check date range type is All. The format for this field is MM/DD/YYYY.
Ending Check Date	Enter, or click lookup to select, the ending check date for the range you want to include in the processing. This field is available only if you select a check date range type of Range.

• A new Non-Contiguous Paychecks subtask allows you to enter criteria for non-contiguous ranges of paychecks for processing.

Field	Description
Employee	Enter, or click lookup to select, the ID of the employee to be processed. The employee's name displays in the adjacent, unlabeled field.
Employee Name	This field displays the display name assigned to the specified employee.
Record Type	From the drop-down list, select the type of paycheck record to be voided. The options are: R B X Y Only one type can be processed at a time. This field is editable only if the Selection Method is Selection Ranges.
Check Date	Enter, or click lookup to select, the date of the paycheck to be processed. The format for this field is MM/DD/YYYY.
Check Number	Enter, or click lookup to select, the check number to be processed.
Taxable Entity	This field displays the taxable entity assigned to the specified paycheck.
Pay Cycle	This field displays the pay cycle assigned to the specified paycheck.
Pay Cycle End Date	This field displays the pay cycle end date assigned to the specified paycheck.

 

Export Payroll Taxes (PRPEXTAX)

The source for the following fields for Local Tax records were updated:

• Field 44 - Local Pennsylvania PSD Code (Periodic / Quarterly / Annual): The value for this field in the Periodic, Quarterly, and Annual files will be based on the value stored in the EMPL_EARN_LOCAL/EMPL_PR_LOCAL tables. If the value is not in those tables, the application will use the value in the EMPL_TAX table.

• Field 45 - Employee Resident PSD Code (Periodic / Quarterly / Annual): The value for this field in the Periodic, Quarterly, and Annual files will based on the value stored in the EMPL_EARN_LOCAL/EMPL_PR_LOCAL tables. If the value is not in those tables, the application will use the value in the EMPL_TAX table.

 

Create State W-2 File (PRPW2S)

Updates were applied to the computation of the sum of the Local Wages (LOCAL_WAGES_AMT) and Local Withholding Amount (LOCAL_WH_AMT) in the Local Withholding (LOCAL_W2_FILE) table for the PA (Pennsylvania) file. Philadelphia reporting will be based on a Y value, instead of P, in the Pennsylvania W-2 Reporting (PA_LOCAL_CD) column in the LOCALITY table.

If PA Local Tax Data is Philadelphia (the local tax code’s PA_LOCAL_CD value is Y on the LOCALITY table), the application will apply the following:

• Include only RA, RE, RW, and RS

• Include data in the following RS fields:

• Tax Type Code (308)

• Local Taxable Wages (309-319)

• Local Income Tax Withheld (320-330)

• State Control Number (331-337)

 

Update State Filing Statuses (PRPUSFS)

This Update State Filing Statuses utility is currently no longer necessary and the application will not be available on the Costpoint menu starting with this release.

 

Print Data Dictionary Report (SYRDD)

The Print Data Dictionary Report was updated to include the fields that were added and updated for this feature.

When the timesheet displays, the cursor now automatically positions in the cell of the current day on the first line of the timesheet.

This enhancement is related to a Timesheet improvement initiative described in KB Article 109655.

The web version of Time & Expense was updated to ensure that when leave requests are submitted from Mobile T&E, the supervisor responsible for approving leave is the only one to receive the task notification when the employee is assigned more than one supervisor.

For users who are licensed only for Time or ESS (Employee Self Service), the Timesheet application (Time » Timesheets » Timesheet) now displays by default following logon, unless the user designates, or has previously designated, a different default value in Application on the Costpoint logon screen.

This enhancement is related to a Timesheet improvement initiative described in KB Article 109655.

Defect 1699768: When you entered and posted a multicurrency cash receipt with multiple lines (for example, one invoice line and four cash lines) in the Cash Receipt Details table window, the functional currency total debit and credit amounts were out of balance.

Defect 1709816: You encountered an error when you clicked the Vendor lookup on the Vendor Labor subtask. This occurred when you:

1. Created or queried a journal entry.

2. Entered a new record on the Vendor Labor subtask and selected a Vendor using the lookup.

3. Modified the Project on the Details subtask using the lookup.

4. Clicked the Vendor lookup on the Vendor Labor subtask.

Defect 1729102: When you selected GLQAACTI (View Account Activity) in the Application field of the Manage Application/Content Links screen, COMPANY_ID does not display in the result set for GLQAACTI.

Defect 1729098: When you selected GLQINQ (View General Ledger Activity) in the Application field of the Manage Application/Content Links screen, COMPANY_ID does not display in the result set for GLQINQ.

Defect 1716668: When you imported daily exchange rates without entering an End Date and clicked Preview or Print, you encountered an error.

Defect 1732973: When you entered a value in the Cobra Master Project field, a critical system error displayed. This issue occurred after you upgraded to Costpoint MR 8.1.10.

Defect 1682011: When a Cobra mapping value was added to a lower-level project, the Cobra Project check box was not selected automatically at the lower levels upon saving. As a result, you could not map at the lower levels in the Manage Cobra Project Mapping application.

Defect 1729135: You received the following error when you tried to save an edit to an MRP Action message: "Error ORA-02089: COMMIT is not allowed in a subordinate session in Manage MRP Action Message".

Defect 1732297: When the approval workflow was escalated to another role, the exclude by role filter did not apply, and all users with the Escalate role received a notification.

Defect 1736788: Hey Deltek did not respond to half-hour increments on the timesheet, like "point 5", "half hour", or "30 minutes".

Defect 1737694: Some rows did not display the employee names and IDs from a queried set of over a thousand records, but the rows displayed when you printed the report.

Defect 1742261: When a Costpoint Employee Name included a special character and was exported to Talent Management, the special character was replaced with a question mark in Talent Management.

Defect 1721457: When you tried to delete a bill of materials (BOM), you were unable to do so even if there were no transactions made against the parts.

Defect 1732874: You were able to preview from the screen, but you randomly received an error when you clicked the gear icon.

Defect 1732946: When you scrolled through the ECN part window, Costpoint displayed random popups about attempting to set an invalid value to a combobox. This error presented randomly when multiple ECNs were queried at once, but the same ECNs did not repeat when pulled up individually.

Defect 1737589: When you reversed an inventory transfer that moved serialized material to a new warehouse, the reversal action did not auto-populate the serial number on the original transfer.

Defect 1722311: When you entered counts, the Reconciled and Counted fields were autopopulated even though the Reconciled field should be blank.

Defect 1731211: When you clicked the Auto Count and Auto Reconcile buttons, the Reconciled By field populated with a User ID instead of an Employee ID.

Defect 1744703: Costpoint did not validate the serial/lot data when you changed the variance quantity to zero (0).

Defect 1732318: The application has been modified to improve its performance.

Defect 1736114: When you generated a sales order (SO) with the Allow Substitutions check box selected on the Configure Sales Order Defaults screen, the Material Requirements Plan (MRP) created substitutions for all lines.

Defect 1736590: When you re-ran Materials Requirements Plan (MRP), Costpoint regenerated a reschedule order for the manufacturing order, which suggested the previous date.

Defect 1715066: When you selected Submit for Approval and clicked Save, the purchase requisition status was not updated.

Defect 1725312: When you cloned a Manage Request for Quotes by Vendor record, the quality requirements were not cloned correctly.

Defect 1738601: When you combined two requisitions, the project for the second line changed to the project of the first line.

Defect 1717791: When you generated a requisition, the application included a part's inventory row associated to a project with a different MRP option code and Include Common Inventory Projects check box value.

Defect 1735811: In Web Integration Console (WIC), you encountered a validation error when the TAXABLE_FL value was not provided in the PO_LN result set and the item type default taxable status was set to "Y".

Defect 1727530: When you printed the change order report, it did not display the Ship Via and Deliver To information.

Defect 1736382: When you processed an input file where Line 1 was Inventory and Line 2 was Non-Inventory, Costpoint displayed the default Planner ID even though the Planner ID should only display if the line type is Inventory.

Defect 1716431: The user’s email address on the Manage Users screen was not updated when you imported the email information from the Import Employee Data screen.

Defect 1728429: The Show Limited Purpose FSA check box in Medical FSA check box is now the Allow selection of a limited purpose FSA along with an HSA check box. The label was updated to allow users to better understand the function of the check box. When you select this check box, employees may specify a limited purpose FSA and an HSA when they select a high deductible health plan (HDHP). If you clear this check box, employees may select only an FSA or an HSA, but not both. 

Defect 1740109: When you selected the Supervisor from Salary Setup option as the Supervisor Source, the application populated the group code (field 3 in the group record) with the SPVSR_NAME column value from the EMPL_LAB_INFO table. Field 3 should be populated with the value from the SPVSR_EMPL_ID column in the EMPL_LAB_INFO table.

Prior to this fix, employees were grouped by the supervisor’s name. With this fix, they will be grouped by the supervisor’s employee ID. To ensure that your employees will be properly grouped under the supervisor’s employee ID, you can perform the following steps:

1. Run a full download of the supervisor groups from Costpoint.

2. Review your old supervisor groups (the ones where the name is part of the code) and add any other functional roles to new groups (the ones where the supervisor ID is part of the code).

3. Delete old groups (the ones where the name is part of the code).

Defect 1736202: The process took a long time to complete when you previewed the report.

Defect 1742054: The work table (Z_LDPUPET_INPUT) used by the application retained all data in between the runs, which resulted in performance degradation. This issue also caused false data in the confirmation work table (Z_LDPUPET_CNFRM).

Defect 1495848: Negative recast lines caused the following hard error: "The Negative Timesheet line would cause the unrelieved amount balance for the total MO to go negative."

Defect 1495843: Negative recast lines caused the following hard error: "The Negative Timesheet line would cause the unrelieved amount balance for the total MO to go negative."

Defect 1736239: When the labor location and GLC did not exist in the input XML file, the application always calculated based on the employee's salary rate and never used the wage determination rate. This issue occurred you used web services, SFT, or application validation mode.

Defect 1730393: Employee names with different font case types were not sorted alphabetically in the report. The application sorted the employee names based on the font case type and disregarded the alphabetical order. For example, the application sorted the uppercase employee names first, the title case employee names next, and the lowercase employee names last.

Defect 1726555: The screen required the following updates:

• The Find functionality on the screen header should allow you to specify the Frequency value in the Search Criteria.

• The Employee Benefit Deductions Updated field label update should be reflected in the Query functionality on the header.

• The Find functionality in the Leave Period table should allow you to specify the following in the Search Criteria:

• Start Date

• End Date

• Leave Year

Defect 1708885: The earnings amount did not reflect the proper payroll salary. This issue occurred when there was a reversed timesheet, a Reversing timesheet, and a regular timesheet.

Defect 1742989: According to the file layout for the Export Payroll Taxes screen, column 40 on the ET LCER (enclosed) should be the local tax type from the Contribution setup. However, in the Export Payroll Taxes file, column 40 was populated with ORWER, which generated an error according to Ceridian. This defect affects you if you use Ceridian for payroll.

Defect 1726522: The screen required the following updates:

• The Employee Package Deductions Processed field should be the Employee Benefit Deductions Updated field. This change applies to the options in the Query functionality.

• The Find and Query functionality should allow you to enter the following in the Search Criteria:

• Frequency

• Enable Multi-State Tax Withholding

• Benefit Deduction Method

• FSA/HSA Deduction Method

• The Find functionality on the Pay Period table should allow you to enter the following in the Search Criteria:

• Start Date

• Check Date

• Payroll Year

• Open

Defect 1671383: When you created a new record and then entered an employee ID, the application automatically added the state and local tax lines if the information did not exist. However, if you changed the employee ID, the application did not delete the state and local lines of the previously entered employee. This issue resulted in problems with FIT/FICA adjustments.

Defect 1691235: When you voided a payroll direct deposit check, the application set the following incorrect values in the columns of the record in the Bank Transaction History (BANK_TRN_HS) table:

• The Transaction Number (TRN_NO) column was set to 0.

• The Transaction Name (TRN_NAME) column was set to 0 - 0.

Defect 1692952: The application set the Medicare Employer Taxable Wages to 0.00 even if there was a negative deduction computed after you recalculated for adjustment records, such as X or Y.

Defect 1708871: The computed amount for Basic Life Contribution/Deduction was incorrect.

Defect 1749981: Errors related to raw cost occurred during calculations of annual salary amounts for part-time employees.

Defect 1727689: When you used the query function in Manage Users, the system did not query the data correctly.

Defect 1738730: When you tried to create a project budget, you encountered the following system error: "Cannot insert the value NULL into column DISTRIBUTED_REV table."

Defect 1731863: When you created a new business budget set to Working status, revenue lines duplicated or multiplied and affected Revenue Setup/Ceilings items.

Defect 1732958: EALC_YTD values were omitted from Profit and Loss reports, resulting in variances.

Defect 1744740: Future years routine created duplicates in the ESUB_PD table.

Defect 1715978: You encountered problems in Batch Mode processing of Import Budget/EACs from Excel, and the application did not communicate with View Action and Report Status.

Defect 1728417: When you used the Overwrite complete Budget/EAC option in Import Budget/EACs from Excel, the revenue adjustments from the budget's previous version were not included in the imported version of the budget.

Defect 1737675: The Project Labor Categories (PLCs) linked to the project were not populated when you created a budget through the Import Budget/EACs from Excel application.

Defect 1699876: The Employee Schedule did not reflect the correct available hours for part-time employees.

Defect 1725439: NULL values that should not have been allowed were saved in the Project Budget Table and caused duplications in succeeding versions of EAC.

Defect 1726205: Invalid Project Labor Categories (PLCs) were saved into a project.

Defect 1736626: Planning timed out when you created a budget and an EAC for an indirect project.

Defect 1740085: You encountered unknown values that affected OVER CEILING - FUNDING calculations.

Defect 1635833: An error occurred when you ran this application even if an alphanumeric Fiscal Year and Period for Rates combination exists in the ACCTING_PD table.

As a workaround, you can enter the Period for Rates value first before entering the alphanumeric End Fiscal Year.

Defect 1738591: You encountered intermittent performance issues while running this application, which could fluctuate between a few minutes to more than two hours. 

Defect 1700054: When you calculated consolidated retroactive bills for multiple years (for example, 2020 and 2021), the Prior Year Indirect lines displayed correctly in Manage Standard Bills. However, when you printed the invoice, only one Prior Year Indirect line was printed as net of 2020 and 2021.

As a workaround, you can separately run the invoice for each year. Alternatively, you can separate the pools in the billing format.

Defect 1713250: A critical system error occurred when you ran this application for all projects and there were more than 1,000 generic billing formats in your database.

As a workaround, run this application for a range of projects.

Defect 1737761: You encountered intermittent performance issues while running this application, which could fluctuate between a few minutes to more than two hours.

Defect 1740383: There was a missing condition on the first-level PROJ_ID segment. Performance tuning has been conducted on this application.

Defect 1707278: Costpoint displayed a warning message even though the accounting period that you entered was within the period of performance date range indicated on the Manage Project User Flow screen.

As a workaround, on the Configure Project Settings screen, clear the Show Period of Performance Warning Message check box.

Defect 1721487: Costpoint now allows you to have a zero (0) value in Number of Units for service centers with a YTD allocation method.

Defect 1723367: Non-labor costs were duplicated in the report's ITD Cost Incurred column.

Defect 1723397: Costpoint duplicated the labor hours on the billing worksheet when a correction was made to the vendor labor and that vendor labor record has no vendor employee. When a voucher has no vendor employee and you entered a correcting voucher (moving the hours off the vendor and adding the hours to the vendor employee), the billing worksheet displayed only the positive hours charged to the voucher without the vendor employee. The billing worksheet did not include the correcting voucher.

Defect 1739372: When you used the ITD Fee on Cost (ITDCPFC) revenue formula, Costpoint included the Other Fee amount from previous periods into the current period. In addition, the Other Fee from prior periods remained at the revenue level and did not get reversed in the current period when using ITDCPFC. This resulted to twice the amount in Other Fee than you should have.

Defect 1727827: When you used a project type with the Default to Owning Org check box selected, and then you entered a new record using Paste Data from Excel, the value of the check box became cleared on the pasted data.

Defect 1636643: When you ran Create Subcontractor Invoices with Effective Billing Date set to Subperiod End Date, the Vendor Labor subtask of the Manage Subcontractor Invoices screen displayed an incorrect Effective Billing Date for the last weekly timesheet.

Defect 1707371: Errors occurred upon saving when you replaced the Rate field with the same value in all labor sub lines on the Vendor Labor Details subtask, and both the Vendor Labor and Vendor Labor Details subtasks had multiple records/lines.

As a workaround, edit Rate one record at a time before saving.

Defect 1707712: You could not run the Effective User Rights report in Costpoint BI. As a workaround, use the Effective User Rights report available in Costpoint, located at Admin » Security » Security Reports/Inquiries » Print Effective User Rights Report.

Defect 1720433: The rolled-up Total Funded value on the Revenue Summary Report Template was incorrect. As a workaround, you can generate the report and use project level 1 to get the correct funding amounts.

Defect 1736557: An error occurred when you ran the Real Time Project Status Report consecutively. This defect affects you if you use Costpoint Planning.

Defect 1746132: The records that displayed in the User Group Rights Report were incomplete.

Defect 1750029: An error occurred when you opened the drill-through in the Summary BI Report Usage report. This error affects Costpoint BI cloud users only.

Defect 1740476: When Time & Expense was no longer co-deployed and you clicked Query, you received an error stating that there were unsaved changes even though no changes had been made. This issue also affected other applications.

 

Affected Applications	Defect No.
UDT01	1740477
UDT02	1740478
UDT03	1740480
UDT04	1740481
UDT05	1740482
UDT06	1740483
UDT07	1740484
UDT08	1740485
UDT09	1740486
UDT10	1740488
UDT11	1740489

Defect 1739377: A General Exception error occurred in co-deployed systems if Wildcard links were enabled for link12.

Defect 1739600: When Time & Expense was co-deployed, you encountered slow system performance during charge tree import.

Defect 1743277: A General Exception error occurred in co-deployed systems if Wildcard links were enabled for link29.

Defect 1743279: A General Exception error occurred in co-deployed systems if Wildcard links were enabled for link27.

Defect 1705154: In systems co-deployed with Costpoint, the PLC Required (UDT07) check box was updated so that it is now editable, even if the Link Project/PLC (link 27) field (located on the UDT Options tab in General Settings) is set to Direct. This allows you to require PLCs without linking to all PLCs in Costpoint.

Defect 1680159: When you generated timesheets, some were generated based on different timesheet class information instead of the latest employee history.

Defect 1729943: When you opened a Time In/Out subtask and clicked Apply, you were prompted to provide a revision explanation even though no changes were made.

Defect 1740591: When you copied start and stop entries from one employee's timesheet into another employee's timesheet, the employee ID was also copied, causing duplication of lines on the source timesheet.

Defect 1696061: A backend update was made to improve query performance related to linked views with Costpoint tables.

Defect 1737585: When Start/Stop Time was enabled but revision explanations were not required, hours were not recalculated after a row was deleted on the Start/Stop Times subtask.

Defect 1737849: You encountered system performance issues related to querying linked UDT02s.

Defect 1741915: When overtime was calculated automatically, it did not include leave hours that were configured to count towards overtime if the timesheet was weekly and the work week was Monday through Sunday.

Defect 1739234: Even though the timesheet class was correctly configured for start/stop time entry modes, the related subtask in the Timesheet application did not display on newly created timesheets.

Defect 1741994: A misspelled word in the instruction text was corrected.