Alabama 2022 Tax Updates

Alabama increases the maximum standard deductions by $1,000 for individuals who are married filing jointly and by $500 for other filing statuses.

The state also changes the thresholds for the dependent exemptions, allowing:

• An exemption of $1,000 per dependent if an individual’s annual income is up to $50,000 (previously, this amount was up to $20,000)

• An exemption of $500 per dependent if an individual's annual income is more than $50,000 and up to $100,000 (previously, this amount was more than $20,000 and up to $100,000)

For more information, see: https://revenue.alabama.gov/wp-content/uploads/2021/08/whbooklet_42722.pdf.

Connecticut 2022 SUTA Electronic Filing: New Format Starting July 5, 2022

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; they will no longer use the File Transfer Protocol (FTP).

ReEmployCT new format overview:

• The new file must be a 276-character, fixed-length text file. It 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 you submit a "zero wage tax report," 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, must not contain decimals, commas, or dollar signs (for example, $12,345.67 must appear as 1234567).

For more information, see:

• • 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 

Vantagepoint has been updated to accommodate these requirements. 

Defect 1505407: The issues below apply for projects with phases and tasks (work breakdown structure levels 2 and 3) that have sub-level billing terms entered for the phases and tasks.

Issue 1:

This issue occurred when you entered a different description in the Description field on the Format tab in Billing Terms for each WBS level of a project, starting with level 1 and ending with level 3.

When you opened the project in Billing » Interactive Billing, the Invoice Description field on the General tab for WBS level 1 correctly displayed the description that you entered in the Description field for WBS level 1 on the Format tab in Billing Terms. However, the Invoice Description field was blank for WBS levels 2 and 3.

Issue 2:

This issue occurred when you entered a different description in the Invoice Description field on the General tab in Hubs » Projects » Draft Invoice Approvals for each WBS level of a project, starting with level 1 and ending with level 3.

When you returned to WBS level 1 in Draft Invoice Approvals, the Invoice Description field on the General tab incorrectly displayed the invoice description from WBS level 3.

Defect 1542922: This issue applies in Interactive Billing for invoices that are part of a billing group and the Consolidate All Posting option is set to No for that billing group.

When you accepted an invoice for the main project of the billing group, and on the Invoice Accept dialog box you copied an item in the Project Detail grid that was associated with a sub-project of the billing group, the project number in the Project field for the new item in the grid was incorrectly changed from the project number of the sub-project to the project number of the main project.

Defect 1697218: This issue occurred when you selected a labor transaction with a Bill status on the Labor tab in Interactive Billing and held a partial amount of the transaction. If you then selected the remaining portion of the transaction with the Bill status and clicked Modify, you received a "Row changed by another user" error message.

Defect 1681951: This issue occurred if you selected the ClieOp option in Bank Settings and then, while creating an employee payment run, selected the Create Checks Instead of EFT transactions for this Run option on the New Payment Run form. When you processed the payment run, Vantagepoint printed non-negotiable payments instead of checks.

Defect 1696520: This issue applies to the Contacts hub, Firms hub, and Projects hub. When you created a new record and then entered values that were similar to the name of an existing record, you did not receive a warning message about potential duplicate records.

Defect 1693442: When you clicked Actions » Close on the Purchase Orders form, you received a random alphanumeric error message If you then navigated to Hubs » Projects » Project Review and, on the Purchasing tab of the Project Review form, checked the Purchase Orders on File grid for the project linked to the purchase order, the grid showed the purchase order with the vouchered amount.

Defect 1697693: This issue applies if you use a multicompany database. On the AP Invoice Approvals form, when you clicked the Total Tax Amount field of an AP voucher item, Vantagepoint displayed tax codes from your active company instead of tax codes that belonged to the company in which the AP invoice approval record was created.

Defect 1572980: AP vouchers did not post to the account that was defined by the corresponding liability code.

Defect 1502437: This issue occurred when you entered details in a cash receipt transaction record or file. If you selected the Invoice Lookup without first entering or selecting a project in the Project Information grid, you received an "Internal Server Error" message.

Defect 1679377: This issue occurred if you posted multiple vendor payments in a single posting run and combined two vendor records from that payment posting run on the Combine Records tab. The records were combined, but you received an error message and an "orphaned" vendor record was created in the database.

Defect 1686691: This issue occurred when you tried to convert a large batch of project records in a single company database or for other companies in a multicompany database. When you ran the Projects' Organization Key Conversion utility to combine records, you received the following error message: "The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request."