We will be placing the site in maintenance on Tuesday, November 6th at 5:00am ET to release back-end updates.

Returns will be placed in maintenance on Thursday, November 1st at 5:00am ET to release series of internal and back-end updates.

We will be placing the site in maintenance on Tuesday, October 30th at 5:00am ET to release a series of updates.

CLIENT SEARCH

• When Client List switches to the “100 Most Recent Returns” search view, the default search value will be Last 4 of SSN instead of Full SSN.
• At the Site Level, allow the Site Administrator to determine when Client List switches to “100 Most Recent Returns” view (previously the default was 499 returns)
  • The new default is 999 before the Client List view switches but can be configured within Office Setup
• Add checkboxes for “Do Not Show Accepted Returns” and “Do Not Show Deactivated Returns” to the “100 Most Recent Returns” view

WEB REPORTS

• Add “State Tax Liability” field to Site Production State Summary Report within Management Reports

*Click here to download a PDF of our Cumulative Release Notes.

We will be placing the site in maintenance on Thursday, October 18th at 5:00 to release some updates.

MICHIGAN

• Detroit city return access menu (currently in Miscellaneous Forms) will be moved to the main Michigan menu for easier access

MISSISSIPPI

• Correct an issue where Unemployment Compensation was carrying to the wrong column when Married Filing Joint and Interest Penalty not included when Married Filing Combined (Issue #2160)

*Click here to download a PDF of our Cumulative Release Notes.

We received the below message from the Alabama Department of Revenue, MeF Coordinators office:

“We are experiencing a backlog of returns being processed. We are aware of the issue and we are processing returns as rapidly as possible.”

Alabama acknowledgements are being returned but at a slower pace. If your site has any outstanding Alabama state acknowledgements, we ask that you be patient as AL DOR works through their backlog of returns.

We will be placing the site in maintenance on Tuesday, October 16th at 5:00am ET to release a few updates but primarily back-end maintenance.

ARIZONA

• Correct an issue where AZ Form 202 was generating in error (Issue #2150)

REJECTED CLIENTS MENU

• Correct an issue where the rejected clients menu was not removing a previous reject for the same taxpayer

*Click here to download a PDF of our Cumulative Release Notes.

We will be placing the site in maintenance on Tuesday, October 2nd at 5:00am ET to release a series of updates.

Client Search

• Adding a Return Tag Filter labeled “No Tag” to allow sites to filter Client List for all returns with no return tag associated. Now, when filtering using the “Any Tag” filter, only returns with an associated Return Tag will display.

Management Reports

• Correct an issue with attempting to view the Extension Report was throwing an unexpected error (Issue #2117)

Rejected Clients Menu

• Inside the Reject Clients menu when viewing a reject code, the “Additional Information” value of the reject code, if applicable, has been added to the display. For example, if a return is rejected for a SSN mismatch, the “Additional Information” will show you the specific SSN that caused the reject. This will allow your sites to more efficiently manage all rejected returns from the Rejected Clients menu.
• Adding the Telephone Number, Notes Icon, and Return Tag icon to the Rejected Clients menu
• Adding the ability to sort columns inside the Rejected Clients menu

*Click here to download a PDF of our Cumulative Release Notes.

10/3/18 – 3:15pm ET

Issue #2149 has been resolved and new 2014 returns can now be prepared once again. We apologize for the inconvenience this may have caused at your sites.

9/27/18 – 10:40pm ET

We have opened Issue #2149 where users are receiving the “An unexpected error has occurred” message when clicking “Start Return” after entering a Taxpayer SSN. This is only impacting the creation of new 2014 returns. Existing 2014 returns can still be accessed from Client Search. We will update this post once this issue has been resolved.