ATX program change?

[neilbrink]

I noticed earlier this week after an ATX update, that a change had occurred with Returns that were being held for efiling. When those return files were opened when in the "created" state previously, they then showed up as "rejected" when the file was closed and stayed that way until the efile process was performed again. Now, when the return is opened, and saved, the efile status does not change. It still stays at the "created" category. The purpose of the previous "rejected" category was to alert us to the fact that when the return file was opened, we needed to check the return to determine whether any changes had been made before we efiled. Has anyone else noticed this change? Or has anyone seen any notice from ATX that this was going to happen?

Thanks.

Neil

[JRS]

I noticed this earlier this week, but now, it seems to have changed back. Thankfully.

[bstaxes]

I create e-file, print, close. It is rejected, so I just create again. Pain but I am getting used to it.

[mcb39]

Print first before you create. Saves the step of having to re-create. It's actually a nice safety net because if you make the slightest change after creating, it will reject.

[grandmabee]

Print first before you create. Saves the step of having to re-create. It's actually a nice safety net because if you make the slightest change after creating, it will reject.

but then the 8879 does not have the dnc numbers on it

[kcjenkins]

Yeah, you have to create the efile to have the DCN inserted, and also to check that there are no efile errors that the regular check did not see, but that affect the efile. I create, print, then create again, every time.

[Cathy]

I do the same as KC. Having the file showing up as a reject is a good reminder that a client needs to come in and sign or whatever. It also helps to prevent me from forgetting that I need to e-file the return. Once a day I check my rejects to make sure all available files for e-filing have been e-filed. Oh well, it makes sense to me anyway.

Cathy

[HV Ken]

Due to past client letter issues with the program, I developed the practice to generate the e-file (for DCN, to find and correct errors, etc.), then add the client letter and print. Adding the client letter after causes the save which moves the e-file back to reject. I have never ended up with a return in the e-file manager in the created state when it really wasn't ready to be e-filed following this simple practice.