To join in on this discussion, you must first log in.

Discussion:Individual Pin Numbers in ProSeries Professional

From TaxAlmanac, A Free Online Resource for Tax Professionals
Note: You are using this website at your own risk, subject to our Disclaimer and Website Use and Contribution Terms.

From TaxAlmanac

Jump to: navigation, search

Discussion Forum Index --> Tax Questions --> Individual Pin Numbers in ProSeries Professional


Tilt53 (talk|edits) said:

11 January 2007
Grrr. Despite having checked the box to have the program generate pin numbers based on social security numbers - this ONLY works on new clients. On all transfered clients you have to go check the box manually on the info worksheet.

Now I realize that doesn't take an extrordinary amount of time, but with over 800 clients it's a PITA. Tech support says that they can report it but programming won't do something about a patch unless a lot of people complain. Let's get on it, folks.

JR1 (talk|edits) said:

January 11, 2007
I use only one pin number for all clients...would that help?

Tilt53 (talk|edits) said:

11 January 2007
Thanks, but I would still have to go in and enter it manually. It's just frustrating that what is supposed to be a time-saving measure, now requires extra time.

Beengel (talk|edits) said:

January 11, 2007
I believe you can go into the forms and modify the info worksheet to automatically check that box. You may need to re-import your clients this year, not sure. I did this for the telephone tax box, and it worked great. Now I just have to uncheck those that are not eligible for this credit.

Deback (talk|edits) said:

January 11, 2007
I just did this: Tools/Options/Electronic Filing and clicked the box to Automatically Generate a Taxpayer PIN equal to the last 5 digits of the SSN (I think I did this before I transferred all of my clients, and actually, I don't remember if I had to check that box or not..it was a week or so ago).

Then I did this: Tools/Options/Transfer and clicked to overwrite clients' files. Then I transferred the client on the top of the list. When hitting ctrl-E after opening that client's file, I'm told I have to enter the client's PIN.

So, this appears to be a major bug in the program and one that I really, really hope is fixed soon, because it will prove to be very time-consuming. I won't mind transferring all of my clients again. I hope I'm missing something that can be done to fix this on my own.

Death&Taxes (talk|edits) said:

11 January 2007
Since only 50-60% of my clients efile, manually entering this just means one more step on a checklist of 'did I do everything right.' Far more vexing to me is the elimination of year of birth on the information worksheet for dependents, so that if 2005 only had a year, you now have nothing entered there because Proseries wants full birthdate. Maybe they are going to send the children birthday greetings. It certainly seems to have no other usage.

Deback (talk|edits) said:

January 11, 2007
I'm also told I need to enter the date the PIN was entered.

Tim, these problems really need to be fixed, unless there's something we can do to fix them on our own. Thanks.

Deback (talk|edits) said:

January 11, 2007
Yup, the birthdate will be a major problem, too. I have no idea how many of my clients had just the year entered previously, but I know it's going to be a big time-consuming problem for me.

Jdugancpa (talk|edits) said:

11 January 2007
D&T, Deb, I don't understand the issue here. I am looking at the 2006 Info Worksheet and it shows a bdate of mm/dd/yyy for t/p, spouse and kids. Looking at the 2005 program I don't see any change.

Death&Taxes (talk|edits) said:

11 January 2007
I always had t/p and spouse birthdates, but only a year for children. Even when TP birthdates were required for efiling, I only needed the kid's Social Security numbers, not their exact ages. The only time d.o.b made a difference was for child care the year child turned 13, and for sure the Proseries 2441 never asked that question. In fact up to this year, you could enter child care for a 15 year old and the software would never notice. Has that changed?


  "Billy is 11, I think, Kim is 9 and Jimmy just turned 6."  "Do you mean turned 6 this year, or in 2005?"  "In January this year."  Since I do most of my work by mail, I am not about to email or call to get birthdates.  I will keep 2005 open and have them all born on April 1st.  There is a very easy reason to prefer entering a year and that is speed.  If I enter 02/12/1994 or the like, I will be that one of out five times, I will type wrong and get a message to enter a valid date.

DZCPA (talk|edits) said:

12 January 2007
I do not think Lacerte had those problems. Just starting to play around with 2006 program.

Deback (talk|edits) said:

January 12, 2007
JD - If you ever entered only the year of birth for any dependents in a prior year's software, the birthdate field will be blank in the 2006 clients' files. At some time in the past, the software would only allow the year born, so I know I will have several that will need to have the full birthdate entered, and that means I'll have to waste time calling clients to ask for birthdates.

Jdugancpa (talk|edits) said:

12 January 2007
I'm sure I must have some, but wouldn't know which clients they would be until they come up. If prior years I know the year I think one solution might be to enter 1/1/YY. I spent all day today printing organizers. Maybe I'll flip through them tomorrow to look to see any that might be missing birthdates. Thanks for the heads up.

Deback (talk|edits) said:

January 12, 2007
Sure. I think you might want to use 1/2/YY, though. Something about senior citizens' age on 1/1...too tired to check that out right now. I might use 7/1 and see what happens, unless Intuit fixes the problem soon. If I can efile using 7/1, I'll probably not bother to ask clients the actual birthdates, unless they're sitting in front of me.

Death&Taxes (talk|edits) said:

12 January 2007
I've had clients call to cancel their appointments because "I forgot, that's my wife's birthday." If I need real dates, I prefer the wife to be there.

I guess it ticks me off because I don't see what child's d.o.b. adds to the functionality of the software. It's like the interplay between Sch A and 6251 on home equity interest. The smart worksheet is on the 6251, not the Sch A, which is ass-backwards, and means you might have to toggle between forms. The last time I did a demo of Lacerte, the computation of that interest was done on Sch A. This is why I always say that you have to KNOW taxes to use Proseries.

Deback (talk|edits) said:

January 26, 2007
>>Despite having checked the box to have the program generate pin numbers based on social security numbers - this ONLY works on new clients. On all transfered clients you have to go check the box manually on the info worksheet.


I haven't had to check the "Automatically generate PIN equal to last 5 digits of taxpayer(s) SSN" for the last several returns I've prepared. Looks like this might been fixed in one of the recent upgrades.

AHH (talk|edits) said:

27 January 2007
Last week I swear Proseries was creating the PIN for me because I had the automatic box checked in the options menu. NOW it's not doing that. Something must have changed as a result of one of the last updates. I've prepared no new clients so it's not just that. It's quite annoying.

Death&Taxes (talk|edits) said:

27 January 2007
I do not transfer clients in bulk, but of the ones I transferred that filed electronically last year, their last five is filled in on the information sheet. Naturally I must fill in a new date, but I would expect to do that.


I haven't filed an individual return yet, and have not added any new efilers, but I did check that 'generate 5 digit' under options.

Deback (talk|edits) said:

January 27, 2007
That's weird, AHH. Last week and earlier this week, I was having to check the "automatically" box for all clients I had transferred and not for new clients. After the last upgrade, I no longer have had to check the box. I've had the setting in Options set to automatically check the PIN box ever since I installed the program and before I transferred the clients (which I did twice, just in case the problem had been fixed in the program after I first transferred them--the second transfer didn't fix the problem, but the upgrade earlier this week did). So, I don't know what to tell ya, except double check your setting in Options and check for recent upgrades online.

Sw (talk|edits) said:

January 27, 2007
I had been having to manual check the block for transferred clients. But it seems to be fixed now. If they could just fix the DOB thing that would be great.

Deback (talk|edits) said:

January 27, 2007
Good. Another annoyance I've been having sometimes, but not all the time, is having to reopen a client's file and save the return using alt-F and S, because sometimes after printing and closing the file, the status is still "Return Transferred for EF" and not "Return Marked for EF." If I don't take this extra step, I can't efile the return, so ProSeries is saving the return when printing, but it isn't changing the status correctly.

Deback (talk|edits) said:

January 27, 2007
And it would be nice if the program would automatically enter today's date for the date the PIN was entered. (I know...I should go to the Intuit forum to post these things, but for some reason, I've been avoiding going there this year. So I just put up with these annoyances and post them here.)

Death&Taxes (talk|edits) said:

27 January 2007
Sad thought, SW, once you transfer the files, they can't fix the DOB thing....that is why I transfer one at a time, or if I am seeing seven people in a day, just those seven.

Deback (talk|edits) said:

January 27, 2007
I can only think of one year, when I had to transfer all clients for a 2nd time in order to fix a prior bug that had been fixed by Intuit.

Deback (talk|edits) said:

January 27, 2007
The Michigan update received today fixed the problem with entering a PIN for city returns, when there is no city return involved. But now I have to enter my phone number and PIN number for any who have a city return (and I can't even efile any city returns in Michigan). Extra steps......

Death&Taxes (talk|edits) said:

27 January 2007
I am so glad you are the 'first in the barrel' Now I will know what to expect, like I did not know of the extra Status steps for efiling. You are a saint, milady!

Deback (talk|edits) said:

January 27, 2007
D&T - Check this out: hehe


EFILE will not work on some clients

Death&Taxes (talk|edits) said:

27 January 2007
I read that earlier! I thought, 'there she goes again.' That forum is mostly for kvetchers....is that the word? Your reply was one reason I started the process of canonization.


cute family story. We had a call last December. Pam's son was taking his family for their annual tour of NYC Christmas sights....they were in St. Patrick's Cathedral. He called from there, laughing his eyes out. His son 15 year old Chris asked his wife, Nicole, 'Mom, what's canonized mean?' "Oh that's when they shoot them out of cannons."

FSteinCPA (talk|edits) said:

27 January 2007
what's the difference between this forum and the intuit proseries forum? just wondering

Death&Taxes (talk|edits) said:

27 January 2007
Lot faster answers here....the interface is poor there, hard to read, and worse, when you open a discussion you are at the beginning, not the last answer. But it is where I found out first about the Form 8283 changes.

Tdoyle (talk|edits) said:

January 27, 2007
FStein:

The focus is also different. The forums there are product focused (how to use the software, defects, etc.) TaxAlmanac is a tax research resource, designed to focus on tax-related research and discussions, no matter what software you happen to be using.

Deback (talk|edits) said:

January 28, 2007
FStein - This forum is more fun and much more addicting. But you can catch up with the other forum at Intuit pretty quick, since there aren't many posts over there.

Death&Taxes (talk|edits) said:

28 January 2007
But don't hit the Proseries vs Lacerte post there....first entries are from 2004.

AHH (talk|edits) said:

28 January 2007
Deb, in case you are still having trouble w/ the "Return Marked for EF" error message, I figured that out last week.(sorry I have just now caught up on this thread or I would have answered early) AnyWho...to prevent this message, go to Options, Electronic Filing, and there's a box to uncheck for this. Hope I'm not too late to help you :0)

Deback (talk|edits) said:

January 28, 2007
AHH - Yea, thanks, I unchecked that box about two weeks ago. The problem I mentioned above is for a defect in the program, which is not related to the check box you mentioned in Options. I've copied the text below, in case you want to read about the problem again. (I believe you are referring to "Only transmit returns when status is set to Return Ready to EF.")


Another annoyance I've been having sometimes, but not all the time, is having to reopen a client's file and save the return using alt-F and S, because sometimes after printing and closing the file, the status is still "Return Transferred for EF" and not "Return Marked for EF." If I don't take this extra step, I can't efile the return, so ProSeries is saving the return when printing, but it isn't changing the status correctly.

To join in on this discussion, you must first log in.
Personal tools