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 1651843: You encountered an error when you imported a vendor employee with a blank Vendor Employee Name, and their last and first names, when combined, totaled to more than 25 characters. As a workaround, enter a first and last name that totals to 25 characters or less, and manually update the record on the Manage Vendors or Manage Vendor Employees screen.

Defect 1680847: 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 1681758: 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 1694201: The Monitoring tool reported the wrong WebLogic version as mismatching.

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

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

Defect 1672850: 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 1682883: When you ran the material requirements plan (MRP), the system allocated inventory to sales orders (SO) after inventory was required for planned orders with need dates prior to the SO need date.

Defect 1621181: When you ran the material requirements plan (MRP), the system allocated inventory to sales orders (SO) after inventory was required for planned orders with need dates prior to the SO need date.

Defect 1687022: When you opened the Other Cost WS subtask and the inventory abbreviation used for the part was more than 10 characters, you encountered a system error.

Defect 1690102: When you opened the Other Cost WS subtask, you encountered a system error. This happened when the inventory abbreviation you used for a part had more than 10 characters.

Defect 1679286: 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 1672096: 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 1690021: When you created a shipping transaction and then created an invoice, the system doubled the unit cost amount when there were two issue locations.

Defect 1687764: When you created a shipping transaction and an invoice, the sales order (SO) journal posted duplicate inventories.

Defect 1687726: When you posted a sales order journal and then accessed it via the View Sales Order Status Information screen, the system displayed duplicate inventories on the report.

Defect 1598132: 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 1598134: 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 1670594: 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 1689521: You were not able to recreate reversing timesheets after you deleted them.

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

Defect 1683413: 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 1687783: The Outlook Rate reports did not reflect the uploaded Actuals in Leave Accounts.

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

Defect 1681941: 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 1685028: When the Recalculate Detail Rows check box was not selected on the Configure Billing Settings screen, MU_SALES_TAX_AMT was not calculated on fee for the following formulas:

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

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

• CPFH (Fee on Hours Plus Cost Incurred)

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

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

Defect 1691180: 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 1691248: 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 1691372: 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 1687653: You were unable to change the owning organization via web services. When you tried to make the same change in Manage Project User Flow, Costpoint displayed the Org History subtask. This subtask was read-only unless you modify the Owning Org field on the Basic Info tab.

Part of the fix for this defect is enabling the New button on the Org History subtask. Note, however, that you still have to edit the Owning Org field on the Basic Info tab (which automatically updates the New Owning Organization field in Org History) if you want to modify the project's owning organization.

If you need to make an organization change in the Costpoint Web Interface Console (WIC), the system now requires a new <PJMBASIC_ORGHIST> so that the owning organization changes in <PJMBASIC_PROJ> will be allowed to proceed. Here is a sample WIC input:

<?xml version='1.0' encoding='UTF-8'?>

<pjmbasic_end xmlns='http://www.deltek.com/enterprise/integration/pjmbasic_end' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>

<PJMBASIC_PROJ tranType='UPDATE'>

                  <ORG_ID>1.2</ORG_ID>

                  <PROJ_ID>ED02</PROJ_ID>

                  <PJMBASIC_ORGHIST tranType='INSERT'>

                                <PD_NO>1</PD_NO>

                                <PJMBASIC_ORGHIST_FY_CD>2021</PJMBASIC_ORGHIST_FY_CD>

                                <RETRO_FL>Y</RETRO_FL>

                                <SUB_PD_NO>1</SUB_PD_NO>

                  </PJMBASIC_ORGHIST>

</PJMBASIC_PROJ>

</pjmbasic_end>

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

Defect 1672551: When you edited the frequent location, the default location was changed to a new one for that Expense Authorization.

Defect 1693597: When abbreviations were enabled, the ABBREV ID displayed instead of the UDT ID, which caused errors related to invalid links.

Defect 1672547: When you edited the frequent location, the default location was changed to a new one for that Expense Report.

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

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

Defect 1680521: When you attempted to save a charge line to Favorites where the UDT10 was blank, the charge line could only be saved first and not after other UDT10s were saved on the same charge.