Scenario: Your site uses Form 8888. The preparer selects the return type of E-file: Direct Deposit
The preparer then scrolls down the Taxpayer Bank Account section in e-file and enters the full amount of the refund in the paper allocation section:
This results in a validation error because IRS MeF efile does not allow this situation
Solution: Change the Federal return type to: E-file: Paper Check and transmit the return again
Scenario: The taxpayer wants to have their refund split between a paper check. You complete the 8888, select the appropriate savings bonds and allocate the remainder of the refund in the paper allocation box. In this scenario, there is no direct deposit of any funds to a bank account
Problem: The return receives the following validation error:
Solution: We will fix this in an update. You will want to hold the return until this is resolved. This should be resolved within the next 48 hours
blog posted 02/07/2018
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.”
This does include prior year returns transmitted prior to 2/2/2018. For 2016 returns, to determine if your “transmitted”r return falls into this situation; select the Client Rejects button on the Welcome page, switch to 2016 and select Validation errors from the drop down. If the 2016 return is not on the validation list, it is impacted by this issue
For 2015 returns, to determine if your “transmitted” return falls into this situation, navigate to Reports >> Validation Errors and run the report. If the 2015 return is not on the validation list, it is impacted by this issue
Scenario: You have transmitted a prior year e-file and the return is still in transmitted status and you are not showing any validation errors. These appear to be returns submitted after 2/1/2018. Issue ID 1001
Current Status: We are actively researching this and will update this post when we have a resolution or additional information.
Blog posted 02/07/2018
New Mexico has reached out to vendors to acknowledge they will be a little delayed in processing acknowledgements of individual NM returns. New Mexico indicated they are throttling the processing of incoming individual returns to ensure they are able to respond more easily to any technical issues that may arise. This means that it may take longer than usual to issue acknowledgements.
Q: What should sites do that have not received acks for transmitted NM returns?
A: Nothing. If your site has transmitted NM returns and they have not been accepted or rejected, continue to wait as NM is currently working through their backlog to issue acknowledgements. They should start coming in over the next several days.
We will be putting the returns in maintenance on Tuesday, February 6th at 5:00am ET for a series of updates.
Just as a heads up to sites that were preparing returns over the weekend (2/3 – 2/4), there were roughly 1,000 acknowledgements (Federal and state) that were delayed. They should start appearing at your sites throughout the morning.
The client list has a new status that you can filter returns on: “State Only”
Yes
When you have electronically filed a state WITHOUT filing the federal return
Updated 2/21: Yes, the status will change to the final status of the state only return. Accepted or Rejected
Blog posted 02/05/2018