Arkansas 2022 Tax Table Updates

The Department of Finance and Administration of Arkansas updated the withholding methods of the state. The new withholding formula takes effect October 1, 2022. The following are the updates:

• The highest tax rate used decreased from 5.5% to 4.9%, and the tax brackets used were adjusted.

• The formula’s standard deduction increased from $2,200 to $2,270.

• The withholding instructions were updated to decrease the supplemental withholding rate to 4.9%.

This release updates the following screens to support the new withholding formula and latest tax updates of Arkansas:

• Manage Payroll Records

• Compute Payroll

Attention: For more information, refer to:

• Withholding Formula: https://www.dfa.arkansas.gov/images/uploads/incomeTaxOffice/whformula.pdf

• Withholding Instructions: https://www.dfa.arkansas.gov/images/uploads/incomeTaxOffice/withholdInstructions.pdf

Note: This enhancement requires patch dbc_810_10983.

Florida 2022 SUTA Electronic Filing

The Florida Department of Revenue published the reemployment tax XML specifications package, which provides enhancements that include the ability to file reports with no employees.

The following requirement to report at least one employee has been removed in XML schema v2022 1.0:

• At least one employee must be reported. If there are no employees to report, enter “Jane Doe”, with a Social Security number of “999999999”.

To support the state requirements, the Create Quarterly SUTA Tax File screen can now generate an XML file with no employees.

Attention: For more information, refer to:

• Florida Dept. of Revenue - Software Developer Information and Specifications

• Reemployment Tax XML Package

Virginia 2022 Tax Table Updates

Virginia updated their withholding methods to implement an increase to the standard deduction from $4,500 to $8,000. The new withholding methods take effect on October 1, 2022. The withholding formula was otherwise unchanged except for the increase to the standard deduction.

This release applies updates to the following screens:

• Manage State Taxes

• Manage State Standard Deductions

• Manage State Tax Tables

• Manage State Tax Withholding Adjustments

Attention: For more information, refer to the Income Tax Withholding Guide for Employers: https://www.tax.virginia.gov/sites/default/files/vatax-pdf/employer-withholding-instructions.pdf

Note: This enhancement requires patch dbc_810_10995.

Washington Q3 2022 SUTA Electronic Filing

The ICESA Washington Bulk Format Specification indicated several updates beginning Q3 2022 filing, which includes changes in the data needed for amendment filing. Starting fourth quarter 2022, all employers are required to report SOC codes.

Multiple Costpoint applications were updated to comply with the following changes to ICESA Washington Reporting:

• In multiple records, the ESD Numbers are now 12 digits long.

• In the employee record:

• Columns 46-63 are now blank.

• Columns 106-107 are used for indicating the reason for an employee having wages but zero hours.

• Columns 108-113 are used for providing the six-digit SOC code corresponding to the employee’s occupation.

• Columns 136-137 are used for indicating the reason for amending the employee wage record.

• Columns 171-209 are used for reporting out-of-state wages.

• For exempt corporate officers, the S record position 210 will now be blank (since corporate exempt officers will not be reported in the S record).

• In the total record, columns 201-216 are used for the adjustment credit indicator and amount for amendment filing only.

• In the final record, columns 159-178 are used for the adjustment credit indicator and amount for amendment filing only.

Attention: For more information, refer to:

• ICESA Filing: https://esd.wa.gov/employer-taxes/EAMS-bulk-filing

• ICESA Q3 2022 Specifications: https://media.esd.wa.gov/esdwa/Default/ESDWAGOV/employer-Taxes/EAMS_Bulk_Filing_Spec_September_2022.pdf

• SOC Codes: https://esd.wa.gov/employer-taxes/about-soc

Note: This enhancement requires patch dbc_810_10992.

 

Manage Employee Taxes (PRMETAX)

The Manage Employee Taxes screen features the following updates:

• The Occupational/SOC Code field now applies to WA (Washington). The field label now reflects the state.

• The list of SOC Codes in the Occupational/SOC Code lookup was updated.

• A warning message displays if the SUTA State is WA and there is no SOC Code assigned to the employee.

Note: These updates also apply to the Taxes tab of the Manage Employee Information screen.

 

Manage SUTA Tax File Data (PRMSMM)

The screen now enables the Pay Types Excluded in Hours Worked subtask if you entered WA in the SUTA State field.

 

Manage SUTA Quarterly Reporting Data (PRMQRD)

The Manage SUTA Quarterly Reporting Data screen provides the following new/updated fields:

Field	Description
Incorrect SSN Reported	Enter the employee’s incorrect SSN reported for the payroll year and quarter.
Zero-hour Reason Code (WA)	From the drop-down list, select the reason for when a wage is reported but the employee has zero hours. Valid options are: Sick leave payout Severance/ Separation Pay/ Settlement Tips/Gratuities Commercial Fishing Back Pay Royalties/ Residuals Bonus Cafeteria Plan/401K Plan Commission Multiple of the reasons listed None
Exempt Corporate Officer Earnings Amount (WA)	If the employee is an Exempt Corporate Officer, enter the QTD wages earned for the Payroll Year/Quarter. This amount is reported in Washington’s SUTA file. This field was previously labeled WA Exempt Officer Earnings/Exercised Stock Options. The amount of dollars represented by any exercised stock options is no longer indicated in the updated ICESA file layout.

The reason for amending employee wage record codes is now inserted in the Adjustment Reason Code for Washington.

 

Create Quarterly SUTA Tax File (PRPSMM)

The ICESA file layout was updated to comply with the changes to ICESA Washington Bulk Format Specification for Q3 2022 reporting, which include the following:

• ESD Number is now 12 digits in records E and S.

• Reasons for amending employee wage records and for employees with zero hours were added.

• Employee's SOC code is now reported in record S.

The hours associated with pay types that were listed to be excluded from employee hours worked on the Manage SUTA Tax File Data screen will not be included in the employee's total hours for the quarter.

An error message will display for the following conditions:

• If there is at least one employee in the file with no SOC Code assigned on the Manage Employee Taxes screen.

• If there is at least one employee in the file with zero hours and a non-zero wage but with no Zero-hour Reason Code specified in Manage SUTA Quarterly Reporting Data for the Payroll Year/Quarter.

The Create Quarterly SUTA Tax File screen provides the following new/updates fields:

Field	Description
Original Total Amount	If the amount remitted for this quarterly report was amended, enter the original total amount due. This field is enabled if State is WA (Washington).
Report Penalty / Underpayment / Prior Balance	Enter the total previous underpayment amounts (including previously due penalty and interest) that are included on the magnetic media file. This field is enabled if State is WA (Washington). The previous label of this existing field was Report Penalty / Underpayment.
Overpayment / Prior Credit	Enter the previous overpayment being applied to the balance due that is included in the magnetic media file. This field is enabled if State is WA (Washington). The previous label of this existing field was Overpayment.

 

Print Data Dictionary Report (SYRDD)

The Print Data Dictionary Report was updated to reflect the following:

• The following columns were added to the SUTA Quarterly Reporting Data (SUTA_QTR_RPT_DATA) table:

• Zero-hour Reason Code (ZERO_HR_RSN_CD)

• Incorrect Social Security Number Reported (INCORRECT_SSN_ID)

• The description of the database table and columns that store the SOC Codes was updated to refer not only to Alaska Occupational Codes, but also to the Standard Occupational Classification (SOC) Codes.

 

Database Changes

This release applies the following changes to the database in Costpoint:

• The SOC Codes in Alaska Occupational Codes or SOC Codes (S_AK_OCC_CD) table was updated with the following:

• The description of SOC Codes 53-3099.51 and 53-3099.52 was corrected.

• The SOC Codes for Military Specific Occupations was added.

• The following columns were added to the SUTA Quarterly Reporting Data (SUTA_QTR_RPT_DATA) table:

• Zero-hour Reason Code (ZERO_HR_RSN_CD)

• Incorrect Social Security Number Reported (INCORRECT_SSN_ID)

• The Reason for Amending Employee Wage Record codes shall be inserted into the S_SUTA_ADJ_RSN_CD table.

Password validation for the sa/SYSTEM user has been changed to use native tools—SQLCMD/SQL Plus—for consistency.

Prior to this release, you were able to print Form 1094-C and 1095-C on pre-printed forms from recommended vendors only. In this release, Costpoint adds the ability to print both Form 1094-C and 1095-C in PDF template files. You could use the PDF files to print forms on plain paper. This feature will prevent alignment problems that occur when you use pre-printed forms.

This new feature adds to the existing functionality of printing ACA forms using vendor-provided forms. The current functionality of printing 1094-C and 1095-C data on vendor-provided forms shall be retained in the meantime.

You will be able to print/process Form 1094-Cs and 1095-Cs for the current form and previous three calendar years. Costpoint provides a notification if the IRS PDF file template for the calendar year is not yet available.

 

Print 1094-Cs (HBR1094C)

The Print 1094-Cs screen adds the Print 1094-C Forms with Data option to the Process menu. When you run this process, the application will save Form 1094-C(s) as PDF file(s) in the specified location.

To support this new functionality, the Print 1094-Cs screen also provides the following new fields:

Field	Description
PDF File Options	Select how 1094-Cs will be saved as PDF files. Options are: One PDF File for all Taxable Entities: Select this option if you want to have a single PDF file for one or more 1094-C forms. For example, if the selected taxable entities for calendar year 2021 are T001 and T002, and the date-time is 06/13/2022 4:23 PM, then the application will create one PDF with the file name “1094C_2021_20220613T162300.pdf“. One PDF File per Taxable Entity: Select this option if you want to have a separate PDF file for each 1094-C form. For example, if the selected taxable entities for calendar year 2021 are T001 and T002, and the date-time is 06/13/2022 4:23 PM, then the application will create two PDF files with the file names “T001_1094C_2021_20220613T162300.pdf” and “T002_1094C_2021 _20220613T162300.pdf”.
File Location	Enter the location where Form 1094-Cs will be saved. If you run the Print 1094-C Forms with Data process, the application will save Form 1094-Cs as PDF files in the specified file location. If you selected the One PDF File for all Taxable Entities option, the application will include the selected 1094-Cs in a single PDF file. The format of the file name will be 1094C_<Calendar Year>_<Timestamp>.pdf. If you select the One PDF File per Taxable Entity option, each 1094-C will have a separate PDF file. The format of the file names will be <Taxable Entity ID>_1094C_<Calendar Year>_<Timestamp>.pdf.

The layout of the screen and existing fields were updated to accommodate the new fields.

 

Print 1095-Cs (HBR1095C)

The Print 1095-Cs screen adds the Print 1095-C Forms with Data option to the Process menu. When you run this process, the application will save Form 1095-C(s) as PDF file(s) in the specified location.

Note: You can only generate/print Form 1095-Cs with user data (PDF files) in a landscape orientation.

To support this new functionality, the Print 1095-Cs screen also provides the following new fields:

Field	Description
PDF File Options	Select how 1095-Cs will be saved as PDF files. Options are: One PDF File for all Employees: Select this option if you want to have a single PDF file for one or more 1095-C forms. For example, if the selected employees for calendar year 2021 are EMP1 and EMP2, and the date-time is 06/13/2022 4:23 PM, then the application will create one PDF file with the file name “1095C_2021_20220613T162300.pdf“. One PDF File per Employee: Select this option if you want to have a separate PDF file for each 1095-C form. For example, if the selected employees for calendar year 2021 are Jane Williams and John Smith, and the date-time is 06/13/2022 4:23 PM, then the application will create two PDF files with the file names “EMP1_1095C_2021_20220613T162300.pdf” and “EMP2_1095C_2021_20220613T162300.pdf”.
File Location	Enter the location where Form 1095-Cs will be saved. If you run the Print 1095-C Forms with Data process, the application will save the Form 1095-Cs as PDF files in the specified file location. If you selected the One PDF File for all Employees option, the application will include all selected 1095-Cs in a single PDF file. The format of the file name will be 1095C_<Calendar Year>_<Timestamp>.pdf. If you selected the One PDF File per Employee option, each 1095-C will have a separate PDF file. The format of the file names will be <Employee ID>_1095C_<Calendar Year>_<Timestamp>.pdf.

Based on Pennsylvania Act 18 of 2018, when reporting a Pennsylvania Local Tax, the W-2/W-2C Box 20 should be populated with the employee’s six-digit Worksite PSD Code concatenated with a dash (-) and then the first two digits of the local tax’s District PSD Code from the Manage Local Taxes screen. This Costpoint release will apply changes to multiple applications to report the correct Pennsylvania local tax value and format. The updates will also allow you to edit the Box 20 values in W-2s and W-2cs.

Prior to this release, Costpoint populates the W-2 Box 20 Locality Name with the PSD Code that is assigned to the local tax on the Manage Local Taxes screen. This may not be the same PSD code as the employee’s Worksite PSD Code. The application also did not concatenate the 2-digit district code. Since the value of Box 20 was not stored in W-2 or W-2c, you were not able to edit it.

 

Create W-2 Table (PRPCW2)

The Create W-2 Table application can now perform the following:

• Report all applicable worksite PSD codes on the W-2/W-2c.

• Store the Locality Name (Box 20) value in the following columns:

• LOCAL_NAME in the Local W-2 Information (LOCAL_W2_FILE) table

• PREV_LOCAL_NAME in the Local W-2c Information (LOCAL_W2C_FILE) table

• LOCAL_NAME in the Local W-2c Information (LOCAL_W2C_FILE) table

• Populate Box 20 with the Worksite PSD Code and first two digits of the Jurisdiction Code (SCHOOL_CD column on the LOCALITY table)

 

Manage W-2s (PRMW2)

The Manage W-2s application features the following updates:

• The following columns were added to the LOCAL_W2_FILE database table:

• Secondary Locality Code (SUB_LOCAL_CD): This hidden field functions as a secondary local code. It was added to the existing composite primary key. If the local code is linked to Pennsylvania and it is not for Philadelphia, this field stores the worksite PSD code.

• Locality Name (Box 20) (LOCAL_NAME): This field stores the locality name, which was not editable previously.

• You are able to edit the Locality Name (Box 20) value.

• The application populates Box 20 with the Worksite PSD Code and first two digits of the Jurisdiction Code (SCHOOL_CD column in the LOCALITY table).

• Populate the secondary local code (SUB_LOCAL_CD) in the Local Withholding (LOCAL_W2_FILE) table based on the following conditions:

• If the Costpoint local tax code (LOCAL_CD) in the Local Withholding (LOCAL_W2_FILE) table is not linked to Pennsylvania, the value of the secondary local code will be the same as the Costpoint local tax code.

• If the Costpoint local tax code (LOCAL_CD) in the Local Withholding (LOCAL_W2_FILE) table is linked to Pennsylvania and it is not for Philadelphia (PA_LOCAL_CD column is N in the LOCALITY table), the secondary local code shall be the employee’s Worksite PSD Code.

• If the Costpoint Local Tax code (LOCAL_CD) in the Local Withholding (LOCAL_W2_FILE) table is linked to Pennsylvania and it is for Philadelphia (PA_LOCAL_CD is Y in the LOCALITY table), the secondary local code shall be PHILLY.

 

Manage W-2Cs (PRMW2C)

The Manage W-2Cs application features the following updates:

• The following fields were added to the Local W-2c Information (LOCAL_W2C_FILE) database table:

• Secondary Locality Code (SUB_LOCAL_CD): This hidden field functions as a secondary local code. It was added to the existing composite primary key. If the local code is linked to Pennsylvania and it is not for Philadelphia, this field stores the Worksite PSD code.

• Previous Locality Name (Box 20) (PREV_LOCAL_NAME): This field will now store the previously reported locality name, which was not editable previously.

• Locality Name (Box 20) (LOCAL_NAME): This field stores the correct locality name, which was not editable previously.

• You are able to edit following fields:

• Previously reported 20 Locality name

• Correct information 20 Locality name

• The application populates Box 20 with the Worksite PSD Code and first two digits of the Jurisdiction Code (SCHOOL_CD column on the LOCALITY table).

• The application populates the secondary local code (SUB_LOCAL_CD) in the Local W2C Information (LOCAL_W2C_FILE) table based on the following conditions:

• If the Costpoint local tax code (LOCAL_CD) in the Local Withholding (LOCAL_W2C_FILE) table is not linked to Pennsylvania, the value of secondary local code will be the same as the Costpoint local tax code.

• If the Costpoint local tax code (LOCAL_CD) in the Local Withholding (LOCAL_W2C_FILE) table is linked to Pennsylvania and it is not for Philadelphia (PA_LOCAL_CD is N in the LOCALITY table), the secondary local code shall be the employee’s Worksite PSD Code.

• If the Costpoint local tax code (LOCAL_CD) in the Local Withholding (LOCAL_W2C_FILE) table is linked to Pennsylvania and it is for Philadelphia (PA_LOCAL_CD is Y in the LOCALITY table), the secondary local code shall be PHILLY.

 

Print W-2s (PRRW2)

The Print W-2s application features the following updates:

• The value of Box 20 now comes from the LOCAL_NAME column in the LOCAL_W2_FILE table for the W-2 report.

• The value of previously reported Box 20 now comes from the PREV_LOCAL_NAME column in the LOCAL_W2C_FILE table for the W-2c report.

• The value of correct Box 20 information now comes from the LOCAL_NAME column in the LOCAL_W2C_FILE table for the W-2c report.

 

Print W-2 Summary Report (PRRW2R)

The application now gets the value of Box 20 from the LOCAL_W2_FILE or LOCAL_W2C_FILE table. The following are the details:

• The value of Box 20 now comes from the LOCAL_NAME column in the LOCAL_W2_FILE table for the W-2 summary report.

• The value of previously reported Box 20 now comes from the PREV_LOCAL_NAME column in the LOCAL_W2C_FILE table for the W-2c report summary report.

• The value of correct Box 20 information now comes from the LOCAL_NAME column in the LOCAL_W2C_FILE table for the W-2c report summary report.

 

Export Payroll Taxes (PRPEXTAX)

The Export Payroll Taxes application features the following updates:

• New fields were added for locality name (Box 20).

• Field 44 (Local Pennsylvania PSD Code) is now populated with the worksite PSD code if the State is PA. Otherwise, this field will be set to a NULL value. Previously, this was populated with the district PSD Code.

• Field 45 (Employee Resident PSD Code) is now populated with the resident PSD code if the State is PA. Otherwise, this field will be set to a NULL value. Previously, this was populated with the resident PSD Code regardless if the State is PA or not. This is also a NULL value in the W-2c record.

• Field 84 (Previously Reported Tax Code) is not being used to report the value of W-2c Box 20. To reflect this, "(W-2c Box 20)" was removed from the field name.

• For the W-2c file, the amounts in the following fields are now grouped by the SUB_LOCAL_CD column in the LOCAL_W2C_FILE table:

• Field 28 (W-2 Box 18)

• Field 35 (W-2 Box 19)

• Field 79 (Previously Reported W-2c Box 18)

• Field 80 (Previously Reported W-2c Box 19)

 

Print Data Dictionary Report (SYRDD)

The Print Data Dictionary Report now provides updated information for the following tables:

• LOCAL_W2_FILE

• LOCAL_W2C_FILE

W-2s (ESMELECW2)

The Box 20 locality name now comes from the LOCAL_NAME column in LOCAL_W2_FILE table for both the screen and report.

From the Charge Favorites subtask, you will now be able to assign charge codes a number to control the order in which they display on your timesheet.

If the charge codes are left unnumbered, the display order is based on current functionality.

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

When you add a charge code to your Favorites, it will automatically load on the next timesheet.

You can still clear the Load checkbox on the Charge Favorites subtask if you do not want to load a charge on future timesheets.

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

Defect 1736089: When you executed a Validate Pay When Paid process, the statuses of Pay When Paid vouchers with Cash Receipt Amount totals that are less than their Total Bill Amount and Amount of Voucher Billed were updated to HOLD. This caused partially settled Pay When Paid Vouchers to be released for payment.

Defect 1750085: Costpoint hung when you pasted more than 10 rows of Excel data in the Manage Purchase Orders application.

Defect 1757912: Under certain conditions, timesheet lines did not load when you opened the Timesheet application.

Defect 1763583: On the Batch Mode screen for a job, the queue in the Job Queue field did not default to the queue defined in Configure Application Batch Job Settings.

Defect 1745576: When you ran Material Requirements Planning (MRP) and clicked the gear icon when the process was on Phase 4, the process did not complete successfully.

Defect 1742025: When you generated a transfer inventory reservation and moved from one warehouse to another, the detailed part schedule displayed supply and demand in one warehouse instead of separating them.

Defect 1751113: The application did not drive the correct Material Requirements Plan (MRP) demand for an inventory transfer reservation.

Defect 1748890: The text codes did not correctly autoload to puchase orders and purchase requisitions.

Defect 1739378: When you cloned a simple requisition with an approval process, the cloned record had no approval process and was disabled. You were also unable to save the record.

Defect 1790646: When you reloaded the Manufacturing Order (MO) Need date and you used lead time offset from the bill of materials, Costpoint set an incorrect Need date.

Defect 1754000: When you set the unit of measure and the U/M conversion, the entered quantities did not round up the value.

Defect 1748395: The application validated for Billing Cycle even though it was not enabled and the SO line was set to Inventory. Validation for Billing Cycle is required only when using RECURRING type.

Defect 1722429: When you processed an XML in Web Integration Console (WIC) and queried the same record in Manage Sales Orders, the Destination Country information was not included in the record.

Defect 1750035: Salary caps were applied to timesheet corrections for employees who did not meet the salary cap criteria.

Defect 1758642: The application should generate an O (Owner) record for supervisor groups if you select the Supervisor from Salary Setup option as the Supervisor Source.

Defect 1753472: When you cleared the Changes since last export checkbox to perform a full data download that included SFT, MES_MO, and MES_EMPL data, the process ran for a long time (for example, 24 hours). The process was stuck on downloading MO issues.

Defect 1683743: You encountered a system error when you saved a timesheet that had a blank labor cost. This issue occurred if the line type was L (Leave Memo).

Defect 1687032: The application did not display an error/warning message when you added a timesheet line with insufficient leave and then saved the timesheet. This issue occurred when the leave type’s Floor Edit Method was set to Error or Warning.

Defect 1720371: Before the application applied the ceiling to the non-qualifying deduction, it subtracted the non-qualifying deduction amounts from the base of the qualifying deduction amounts.

Defect 1744733: The employee name was blank in the Create W-2 Table Error Report when employees who had the same first name and last name were included in the report.

Defect 1755821: You encountered a pay type validation error when an employee had a salary record with a date that fell after the pay period end date and before the check date.

Defect 1816975: The Update State Filing Statuses screen must be added back to the Costpoint menu. This update reverses the menu change in MR 8.1.12.

Defect 1750059: You encountered issues in using alphanumeric fiscal years when FY_CD modification was not yet allowed.

Defect 1760190: You encountered issues during refresh because VEND_PLC was pulling vendor rate schedules for all projects.

Defect 1751219: With Indirect Toggle selected, system errors occurred when you executed the labor analysis reports.

Defect 1754465: There was no option to select either Home Org or Timesheet Org. This resulted in inaccurate computation of burdened cost for employees who were not in the Home Org.

Defect 1754463: There was no option to select either Home Org or Timesheet Org. This resulted in inaccurate computation of burdened cost for employees who were not in the Home Org.

Defect 1319209: Advanced Search did not contain ID lookups for some Planning applications. Descriptions were added to criteria ID lookups to resolve the issue.

Defect 1743333: BI Report tables were multiplying Revenue/Costs due to different PAG codes between Project Budgets and New Business Budgets.

Defect 1751649: An hourly rate was not calculated for Labor K entries during budget creation.

Defect 1762162: The PY_DIFF line in the Burdened Cost link of a newly created EAC displayed incorrect amounts.

Defect 1746877: There was no option to select either Home Org or Timesheet Org. This resulted in inaccurate computation of burdened cost for employees who were not in the Home Org.

Defect 1749924: Costpoint treated burden cost ceilings as fixed/override when the Current Period Rates option was selected on the Corporate Settings subtask of the Configure Project Settings screen.

As a workaround, you can manually edit the bill. Alternatively, you can temporarily set the ceiling rate equal to the current period provisional rate if the ceiling rate is higher than the current period provisional rate.

Note: If the ceiling rate is lower than the current period provisional rate, the issue does not exist.

Defect 1753499 and 1758614: Performance tuning has been conducted for a merge statement that was taking a long time to process.

Defect 1753490: Costpoint excluded the OTH_FEE_AMT value from ceiling calculations when you computed revenue using the ITD Fee on Cost (ITDCPFC) revenue formula.

Defect 1760200: A critical system error occurred when you ran this application for projects that use the ITD Fee on Cost (ITDCPFC) revenue formula and have organization changes.

Defect 1750106: Actual Hours displayed on the Smart AI Resource Mgmt Dashboard were doubled. This defect affects you if you have multiple GLCs and/or PLCs in Costpoint Planning.

Defect 1750205: The EAC column in the Burden Labor Costs report in Costpoint BI did not match with the Burden Cost Breakdown report in Costpoint Planning. This defect affects Costpoint Planning users.

Defect 1754783: An error occurred when the Employee UDEFs data set was refreshed.

Defect 1761340: The Modifications section of the Project Reporting Package did not include English names.

Defect 1765819: You could not use the Employee package with an Oracle database.

Defect 1756321: When Time & Expense was configured to use Project Long Name, the long version autoloaded at the branch level but not at the charge code level. It therefore did not display the long name when it was saved to Charge Favorites.

Defect 1744824: New indexes were added to support the importation of Employee Groups and Employee Leave.

Defect 1736983: When you saved a work assignment as a Favorite from the timesheet, that same charge displayed under Charge Favorites in the Expense Report, even though it was designated as a labor charge.

Defect 1760198: When you entered meals allowance into an expense report for multiple dates and then added entertainment with attendees for one meal, you received a notification that all meals were already claimed even though they were not.

Defect 1763234: Timesheets rejected by Costpoint due to errors remained unavailable for editing or correction.

Defect 1741998: The Approve button was enabled on a processed timesheet even though the logged-in user had previously approved it.

Defect 1714080: Workflow sent the email for the leave request approval only to the Primary Supervisor role, even though more than one role was listed in the workflow event.

Defect 1757086: When Time & Expense was configured to use Project Long Name, the long name was displayed at the branch but not at the charge level. In Charge Lookup, it was displayed, but when the charge was saved to Favorites, the original description was used.

Defect 1751239: Timesheet notifications sent to employees included an unselected status. For example, under Notify For, Missing and Signed were the only options selected, but notifications were also sent for Open timesheets.