Connecticut 2022 SUTA Electronic Filing

The Connecticut Department of Labor (CTDOL) will launch the new tax and benefit system, ReEmployCT, on July 5, 2022.

The first quarter of the 2022 tax and wage return will be the last return filed in their current system. Beginning July 5, 2022, employers will file their second quarter 2022 returns and any outstanding returns for previous quarters in the ReEmployCT system.

CTDOL has provided a new file format for Unemployment Wage and Tax Reporting. ReEmployCT will allow employers to securely log in to the ReEmployCT system and directly upload their files for processing. Employers will no longer use the File Transfer Protocol (FTP).

The following is an overview of the new file format for ReEmployCT:

• The new file must be a 276-character fixed length text file, which must have a .txt extension.

• Each file that contains wages must contain one “S” record for each reportable employee followed by a “T” record for each employer.

• If a “zero wage tax report” is being submitted, each file must contain a single “T” record for the employer. Do not submit any “S” records. Zero wage tax reports can be included in the same file with employers reporting wages.

• All numbers, including dollar amounts, may not contain decimals, commas, or dollar signs. Example: $12,345.67 must appear as 1234567.

According to Connecticut Department of Labor (CTDOL), for those employers who were assigned a 7-digit Employer Account Number, three zeros will be added to the end of their existing registration number. All Employer Account Numbers issued in the new system will be a unique 10-digit number. All communication issued by CTDOL on or after July 5, 2022 will include the 10-digit Employer Account Number.

For Costpoint users, if you have an existing record for Connecticut on the Manage SUTA Tax File Data screen, you need to update your 7-digit Reporting ID/UI Account Number to 10-digit by adding three trailing zeros. If in case you were not able to update your employer account number, trailing zeros will be automatically added if it is fewer than 10 digits when you generate your quarterly SUTA tax file.

Attention: For more information, refer to:

• ReEmployCT Page: https://portal.ct.gov/DOLUI/reemployctemployerinfo

• New File Format Requirements for FTP Filers starting July 2022: https://www.ctdol.state.ct.us/uitax/FTPFileFormatforReEmploy.pdf

 

Manage SUTA Tax File Data

The screen adds a validation to ensure that the Reporting ID/UI Account Number must be 10 digits for Connecticut.

 

Create Quarterly SUTA Tax File

The file layout for Connecticut was updated to contain S and T records in order to comply with the Q2 2022 reporting in the new ReEmployCT system. Previously, the records included in the file were E, S, and F records.

You can now opt to post or not post L (Leave Memo) type timesheet lines to the General Ledger (GL). To support this new functionality, this release updates multiple applications.

 

Configure Labor Settings (LDMLABOR)

Costpoint adds the following check box on the Timesheet Options tab of the Configure Labor Settings screen:

Field

Description

Post Leave Memo Timesheet Lines to the General Ledger

Select this check box to enable the system to post L (Leave Memo) type timesheet lines to the GL. When you clear this check box, the L type timesheet lines will not be posted to the GL, but they will still be posted to the Leave History, Employee Leave Balance, and Timesheet Line History tables. The posting will not be out of balance since L timesheet lines have no associated labor cost but have data that is related to tracking of leave hours used.

 

Post Timesheets (LDPLDJ)

The Post Timesheets process was updated to use the new Post Leave Memo Timesheet Lines to the General Ledger setting, which dictates whether to post L type timesheet lines to the GL.

 

Set Up Company (SYPCOMP)

When you set up new companies, the Post Leave Memo Timesheet Lines to the General Ledger check box setting of the company selected to be copied will be set as the default value for the new company.

Defect 1683308: This screen has been updated to enable you to access the Identification section and Edit Voucher Payment Status table window when the Pay When Paid subtask is open.

Defect 1669099: You were unable to access the Import GovWin IQ Vendor Data application because it was not added to the Application Rights table window of the Application Rights subtask in Manage Users. This occurred even when you were assigned the correct module rights.

Defect 1680980: When you selected vouchers for payment using the Select process, Costpoint updated the status of Pay When Paid vouchers to PAY even if the Cash Receipt Amount on the Pay When Paid subtask of the Edit Voucher Payment Status screen is 0. Likewise, when you ran the procedure using the Validate Pay When Paid process, Costpoint also updated the status of Pay When Paid vouchers to HOLD even if the Cash Receipt Amount for the voucher is 0.

Defect 1684140: When you reprocessed and selected the Delete Existing Unposted Accrual check box, the system did not delete the unposted journal entry.

Defect 1315994: You could not edit and change the letter case in Group header lines in My Menu, specifically in the Manage Users and Manage User Interface Profiles applications. You received an error stating duplicates are not allowed.

Defect 1673896: A "Duplicate Group Names could not be assigned" error occurred when you changed the My Menu title of a group header.

Defect 1674441: In Approval Workflow Models, the CP_CURRENT_DATE would not save in the System Value field on the Updates subtask in the Edit Activity window. Upon save, the selected System Value reverted to None.

Defect 1694202: The Monitoring tool reported the wrong WebLogic version as mismatching.

Defect 1627387: When a condition is applied to an activity within a workflow (Approval Workflow (NEW) » Approval Workflow Models), the system will validate that the condition is met before the record can be approved. If the workflow update is processed before the condition, the new value must be used for condition evaluation.

Note: Direct changes to the approval record are not permitted – the record is set as read-only. Any changes to the same data from outside of the application will not be registered by the workflow nor considered in the condition evaluation.

Defect 1635413: You might have received the following error when you tried to access an extension: "Fatal Error(s) Remote Access to this application has been denied."

Patch dba_810_10891 is required.

Defect 1677519: Fields that should have been hidden in Manage Vendors for the DLTKSMB user profile were still visible.

Defect 1678419: The cursor moved to the end of the variable entered in a field when you tried to modify the variable.

Defect 1681953: When you tried to delete a resource that you just assigned, Costpoint stalled and the resource was not removed, which caused you to close Costpoint.

Defect 1682630: There was an Auto Positioning issue in the Contracts module (Manage Contracts, Manage Opportunities, Manage Subcontracts, and Manage Contract Management Vendor Info).

Defect 1683050: Costpoint would hang after you reopened the Business Intelligence application.

Defect 1693631: Page Setup did not print reports in the Default Font for the company as indicated on the Configure System Settings screen. When there were recent changes to a company's default font, the other companies were also printed in that font, even though these companies' default settings were not changed.

This defect affects you if you have multiple companies with different default fonts.

As a workaround, you can manually change the font on the Page Setup dialog box or use a report parameter before printing.

Defect 1650516: Costpoint did not support URL rewriting. When your VPN was configured where there is text between "/cpweb/" and "masterPage.htm" in the browser URL, many Costpoint features (Query, Dashboards) did not work.

URL example: https://server.com/cpweb/.DanaInfo=DELTEKCP.id=78685555./masterPage.htm?6257362513761

Defect 1682687: Costpoint repeatedly suggested to subscribe to push notifications.

Defect 1675667: The application has been modified to add SUB_KEY and expose it on the View Serial/Lot Information screen so that it can be included in the linked fields for Customer Managed Inventory (CMI).

Defect 1675588: When you loaded a manufacturing order (MO) from the Material Requirements Plan (MRP) routing lines, the loaded routings did not have start and end dates.

Defect 1681021: When you ran the Update Material Requirements Plan option and manufacturing orders (MO) have inventory allocations for components, the system locked all of the inventory from allocating to future orders.

Defect 1680418: When you created purchase orders (POs) with amounts set to under the buyer's limit, the POs created were set to Pending status.

Defect 1672738: When you ran the query through the backend, you encountered this error: "Duplicate-Price_Catlg_Cd / Invalid S_PROD_LN_TYPE_CD combo box (NONE)"

Defect 1673693: When you changed shifts or deleted lines in the Shop Floor calendar, you encountered this error: "If these dates are deleted a gap will exist in the calendar."

Defect 1680971: When you tried to update the routing sequence number on the Routings subtask, you encountered the following system error: "Column CLONE_FL not found in row set."

Defect 1651563: When you ran Manage Inventory Abbreviation Peggings for the first bill of materials (BOM), you encountered an error when a buy part in the BOM had a part classified as restricted.

Defect 1685086: When you entered a new manufacturing order (MO), the operationalized bill of materials (BOM) created duplicate requirements on MOs when you pegged the manufacturing bill of materials (MBOM) part.

Defect 1675665: When you previewed or imported a purchase order (PO) from the input file, the following occurred:

• You encountered the following error:

Warning: This PO or PO line exceeds the buyer's authorization limit. The status of this PO will be set to pending for additional approval.

• The buyer’s maximum authorization amounts were treated as transactional currency instead of functional currency.

Defect 1672816: The Obsolete check box for MES routings has been enabled and a warning message displays when this check box is selected.

Defect 1627800: You encountered a critical error when you uploaded employee data. The error indicates the following: SQLIntegrityConstraintViolationException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Cannot insert the value NULL into column 'VEND_GRP_CD', table 'TESTCP3.DELTEK.VEND'; column does not allow nulls.

Defect 1646590: When you imported employee data that did not have work hours in a year and annual hours, the default values did not come from the home organization.

Defect 1626921: A system error displayed when you saved a record on the Manage Employee Information screen if only the Employee History subtask had values.

Defect 1494468: The Login ID on the Resource Information screen in Time and Expense was different from the User ID value entered on the Manage Employee Information screen. Dot (period) symbols were removed from the Login ID value on the Resource Information screen.

Defect 1600796: You were able to import a timesheet even when there was no exchange rate available for the selected currency code combination, date, and rate group ID. An error message displayed in the report, but the timesheet was still imported successfully.

Defect 1600798: When you imported a correcting timesheet and the transaction currency of the reference timesheet was USD (U.S Dollar), the following error message displayed: “There is no Exchange Rate available for the selected Currency Code combination, Date, and Rate Group ID.”

Defect 1673577: When you imported a manufacturing order (MO) line that had no project, the application defaulted to an MO project. However, the application did not validate the defaulted MO project. As a result, there was no error even if the defaulted MO project was not valid.

Defect 1698856: A system error displayed when you saved a new pay type restriction record. This occurred when the synthetic key value in the database (SEQ_GENERATOR.LAST_KEY) was more than 4 digits.

Defect 1682680: The application did not compute leave for employees who used leave in a period if the Compute Method was Unit of Hours Worked.

Defect 1683414: The Compute Leave Accruals screen did not calculate leave for employees who used leave in a period if the Compute Method was Unit of Hours Worked. The Reconcile Leave Balances screen needed updates in order for the Compute Leave Accruals screen to work properly.

Defect 1686917: In the Organization Type section of Org Job Summary, only Owning Org was being used. Options were added to run the application using either Owning Org, Performing Org, or Employee Org.

Defect 1682697: The Outlook Rate reports did not reflect the uploaded Actuals in Leave Accounts.

Defect 1681387: The Time Collection Hours application did not return data when you ran it on Org side, regardless of Org ID used.

Defect 1674665: Critical system errors occurred when you ran the Utilization Analysis application. The execution process was also taking too long and resulted in memory error.

Defect 1684444: There was a system error when duplicate period end dates in the ESUB_PD table occurred in multiple applications.

Defect 1645891: When importing Budgets/EACs from Excel, users did not have the option to specify into which Budget or EAC version the data will be uploaded. As a solution, an item was added into the Import Budget/EACs from Excel application to allow selection of either Budget or EAC as an upload option.

Defect 1684293: When importing Budgets/EACs from Excel, users did not have the option to specify Burden (Yes or No) and Revenue (Yes or No) on the import template. To allow this, two new columns, Burden and Revenue, were added to the Project Budget/EAC import template.

Defect 1547564: The fixed revenue amounts did not populate correctly for the closed periods.

Defect 1678554: Advanced Search in the Budget By Resource application was disabled after you used the Add Resources and Save Team functions. A system error also occurred after you clicked the Lightning Bolt icon while the Advanced Search screen was still open and disabled.

Defect 1646637: This application stopped responding at 0% when:

• the ACRN calculation method used for the project being processed was Proration,

• the invoice amount was less than 0, and

• there was a rounding error in allocating ACRN amounts.

Defect 1677509: The Over Cost Ceiling, Over Fee Ceiling, and Over Total Ceiling amounts were overstated when ceilings were set below the billing level.

As a workaround, you can manually edit the over ceiling amounts on the Manage Standard Bills screen.

Defect 1678253: To get the total billing currency sales tax amount, the application was multiplying the functional sales tax amount by the invoice date’s exchange rate, rather than multiplying the multicurrency bill amount by the sales tax rate.

As a workaround, you can edit the bills on the Manage Standard Bills screen.

Defect 1680150: The multiplier rate on the printed bill was incorrect for the following formulas when the Use Transactional Currency Billing check box was selected on the Manage Project Billing Information screen:

• CIMR (Labor Cost Times Multiplier Plus Non-Labor Times Multiplier (Hours))

• COSTIMR (Labor Cost Times Multiplier Plus Non-Labor Times Multiplier (Cost))

• RSMNLM (Rate Schedule Times Multiplier Plus Non-Labor Times Multiplier)

The calculated bill amounts, on the other hand, were correct.

Defect 1681665: The multicurrency amounts for indirects and fee were incorrect for the following formulas when the Use Transactional Currency Billing check box was selected on the Manage Project Billing Information screen:

• RSBFNLBF (Loaded Labor Rate W/Burden W/Fee Plus Non-Labor w/Burden W/Fee)

• LLRFNLBF (LLR W/Fee Plus Non-Labor W/Burden W/Fee)

As a workaround, manually edit the indirect and fee amounts for the bill on the Manage Standard Bills screen.

Defect 1681833: When FUNC_S_CRNCY_CD was equal to S_CRNCY_CD and RPT_ONLY_FL was N, MUX_TRN_TO_EUR_RT was populated with other values instead of just 1.

Defect 1681968: BILL_RT_AMT, ORIG_BILL_RT_AMT, and MU_ORIG_BILL_RT_AMT all displayed 4 decimal places, but MU_BILL_RT_AMT displayed only 2 even though the field data type is Number (19,4).

Defect 1682007: Retainage was not included in the bill in a database with the Multicurrency setting turned off.

As a workaround, select the following check boxes before calculating bills, and then manually edit the Retainage Amount on the Detail subtask of Manage Standard Bills:

• Allow User to Edit Bills check box (on the Proj Bill Info subtask of the Manage Project User Flow screen)

• Create Zero Retainage and Over-Ceiling Rows check box (on the Calculate Standard Bills screen)

Defect 1682758: BILL_FM_RETRO_NO was being updated incorrectly when there were both current and prior year retroactive amounts. For retroactive amounts for a prior fiscal year, Costpoint assigned a separate BILL_FM_RETRO_NO for that line. For current year retroactive amounts, on the other hand, the system used the same BILL_FM_RETRO_NO for records that have both COMBO_RETRO_RT_FL set to Y and N.

Defect 1683206: Records were populated for columns BD, CR, DA, and DD. In some instances, however, ORIG_BILL _RT and MU_ORIG_BILL_RT were not populated with rates.

Defect 1687346: You encountered deadlock errors when running this application.

Defect 1690247: When the functional currency was the same as the billing currency and MUITD = 0, the following records had a NULL value (instead of 1) for MUX_TRN_TO_EUR_RT in the BILL_EDIT_DETL table:

• OC (Over Cost Ceiling)

• OF (Over Fee Ceiling)

• OT (Over Total Ceiling)

• R (Retainage)

• WH (Withholding)

• WHR (Withholding Release)

Defect 1690320: The ORIG_BILL_RT_AMT and MU_ORIG_BILL_RT_AMT fields were not populated in some records when hours ceilings were reached.

Defect 1678540: Unused records have been deleted from work tables.

Defect 1683425: When you copied data from Microsoft Excel and pasted it on this screen, the Allowable Hours field value was overwritten with the Hours field value.

Defect 1669086: Errors occurred upon saving when you changed a Rate value on the Vendor Labor Details subtask and there were multiple records/lines on the Vendor Labor subtask.

Defect 1594656: Executive Dashboard: The outstanding Accounts Receivable (AR) balance by customer found on the View AR and DSO tab did not match the breakdown on the AR Header. The displayed AR values were from only the primary customer of the project.

Defect 1672518: Employee Model: The displayed data of query results based on security settings did not display the expected number of records.

Defect 1672526: Labor Model: Security settings were not applied when queries were run. Employees from a different organization were included in the query.

Defect 1684549: When importing charges, you encountered slow system performance. This was corrected through improvements to the Rebuild Group Cache functionality.

Defect 1682190: When the UDT03/UDT09 link on the UDT Options tab of General Settings was selected as None, you received a critical system error after you ran the Set Co-Deployed Data option in the UDT02 application.

Defect 1682892: You were unable to approve all selected tasks at the same time.

Defect 1684472: You encountered slow system performance when sending a high volume of employee notifications.

Defect 1679497: When you applied hours to a holiday, you received an error message even though your company does not track leave balances.

Defect 1679689: When you copied Start/Stop details, the timesheet did not clear.

Defect 1684267: When Start Time was clear, you received an error after you saved.

Defect 1691296: When you clicked the Total Hours link to view hours from the previous period, the application did not display the entire timesheet.

Defect 1693426: When you submitted your timesheet, you received an error message indicating that hours for a week over 40 must be recorded as level one.