INTUIT FAILS TO PROVIDE PROSERIES WITH A COMPLETED RETURN LOCKING FEATURE/TOGGLE SWITCH (AGAIN)

This is the most requested feature by users on this forum for the last 5 years. We have had many discussions on this subject with Intuit personnel (including the product manager). 

It is generally regarded as a Best Practice for Tax Preparers to protect completed files and returns from being accidentally changed. It is not only protection from users accidentally changing a return, but we have seen multiple occurrences in past years that INTUIT will provide an update that will change previously filed returns without our knowledge. This is entirely unacceptable.

A similar feature has been available for LaCerte users for at least 6 years and is included on most other professional tax preparation software packages. 

@Product Manager and Developers: We consider this a PRODUCT DEFECT.  

Following are only a handful of the threads, comments, and complaints on this subject. 

https://accountants-community.intuit.com/questions/778125-locking-down-prior-year-returns

https://accountants-community.intuit.com/discussions/lounge/878243-file-locking-again

https://accountants-community.intuit.com/discussions/lounge/789072-file-locking

https://accountants-community.intuit.com/questions/774986-why-won-t-proseries-allow-prior-year-retur...

https://accountants-community.intuit.com/discussions/lounge/1394475-toggle-switch-date-lock

https://accountants-community.intuit.com/questions/1153123-more-whining-about-file-locking

https://accountants-community.intuit.com/discussions/lounge/1205121-eureka-a-solution-to-the-toggle-...

17 additional answers

No answers have been posted

More Actions

People come to Accountants Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:

  1. Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
  2. Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
  3. Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
  4. Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
  5. Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.

Select a file to attach: