We are using the "lock return" feature. Return is prepared, reviewed, printed and locked. When we e-file that locked return, it is rejected. Every time. Every type of return. We have to unlock the return, rerun the review, save and lock it. Then it can be efiled. HOWEVER, as soon as we unlock it, we expose the data file to potential changes by the ProSeries program changes. Are we doing something wrong or is ProSeries not doing something right?
Hi Ali, So you can efile returns that are locked as long as you are not OPENING the client file to do so. For example, if you're efiling from the EF Center with the return just highlighted you *should* be able to efile while the return is locked. https://proconnect.intuit.com/community/help-articles/help/e-filing-locked-returns-in-proseries/00/6...
Ashley, I agree that I *should* be able to. However, with the file closed and locked, from the EF center, we e-file and it's immediately rejected. Is anyone else having this issue? If not, what might we be doing wrong?
Yes, it's the same no matter what type of return we are filing (1040, 1041, 1120, etc.) We are told to unlock the file, review, save, re-lock and efile. We do this because we have to e-file the return. When we open the file, there are no errors and when we run review, there are no changes that are made.