The Site Production Reports are missing data from 2/8 through 2/11. We are replaying the returns to populate the reporting database for the Management Reports
Blog Posted 02/15/2018
2/10/18 – 6:20om ET
The issue has been resolved and sites can now transmit returns from the Transmission menu at this time.
2/10/18 – 5:55pm ET
No additional update to report. Continue to e-file returns from the Submission page of E-file.
2/10/18 – 5:17pm ET
No additional update to report at this time.
2/10/18 – 4:49pm ET
We are still investigating at this time. Continue to e-file returns from the Submission page of E-file.
2/10/18 – 4:20pm ET
We are receiving reports of users receiving an “Error Page – An unexpected error has occurred.” From what we have been able to gather, this appears to be occurring transmitting returns from the Transmission menu from the sites Welcome screen. We are currently investigating.
We recommend transmitting returns from the Submission page at this time.
Scenario: You have submitted your MNPR returns, but have not received an acknowledgement on it. The screenshot below indicates what it looks like from Pro Online 2017 Client Status
Problem: We have received the acks from MN, but they are not being successfully applied.
Solution: We are working on a solution, please do not resend your MNPR returns that you have not received an acknowledgement for.
Blog posted: 02/09/2018 8:49 am EST
We have resolved the issue with returns not being transmitted to the IRS. We are in the process of sending them. They should all be out to the IRS by 11:00 am EST
We are currently researching why a batch of returns are still pending transmission to the IRS. These returns will appear in the “Transmitted” status on your side. This seems isolated to a certain point in time yesterday, as returns sent later in the evening and this morning are being transmitted to the IRS.
Blog Posted 02/09/2018 7:11 am EST
As of 2/7/18, we have started seeing a string of Kansas and Rhode Island returns being rejected for the below reasons. We have opened #1065 (Kansas) and #1067 (Rhode Island) with development to review these rejects. For any impacted KS and RI returns with the below reject codes, please hold on resubmitting until an update is provided on this post.
2/10/18
The issue has been resolved where the LC-142 was not generating in the VT return when completed. For any potentially impacted VT returns, we recommend opening each return from the Client List to allow the current calculations/updates to be applied prior to submitting these VT returns.
2/7/18
An issue has been identified (assigned Issue #1055) with the 2017 Vermont Landlord Certificate, LC-142, pertaining to the Renters Rebate claimed on a VT return. The LC-142 is not generating in the PDF when completed in the VT program, potentially restricting the taxpayer(s) from receiving the renter rebate assuming other qualifications are met. The reason a taxpayer may not be receiving the renter rebate, if LC-142 is completed in the program), is due to the allocable rent from Line 9 not carrying to PR-141, Line 3. We will update this post once this issue has been resolved.
RESOLVED 2/16/18 – Prior Year AZ returns rejected for this reason can be resubmitted at this time
If your site has transmitted a 2015 or 2016 Arizona return and it has received the below reject code, please hold on to these returns and do not resubmit until notified. We are working to resolve the issue causing this AZ state reject code. Note: This DOES NOT impact 2017 Arizona submissions.
“AZ Reject Code: 500 – The ‘stateSchemaVersion’ attribute is invalid – The value ‘AZIndividual2016v1.3’ is invalid according to its datatype ‘String’ – The Enumeration constraint failed.; Return failed Schema Level Validation.”
Update 6:07 pm EST: We pulled 1 server out of rotation that was generating this error.
We are experiencing sporadic “Unexpected server errors”. If you get this, close the instance of your browser, and open a new browser (not just your tab). We are actively looking at this.