Anytime I edit either the contribution amount or the employer
contribution amount within my Spouse's paycheck, the category for the
employer contribution changes from _401EmployerContribSpouse to
_401EmployerContrib.

Unfortunately, it is not possible to go back and set the category back
to _401EmployerContribSpouse since it is not apparently possible to
set the category for this particular item within the Paycheck form.

Note: The above behavior is seen only if you EDIT a paycheck
transaction that is already entered into any register. If you edit an
scheduled transaction PRIOR to accepting it into a register, the above
will NOT happen.

You can recreate the issue by doing the following:

* Create a new file in Quicken 2004 or 2005
* Create a Checking account
* Create 401k account for Spouse
* Setup a paycheck for Spouse; Make sure to setup employer's
contribution.
* Accept one of the Spouse's paychecks
* Generate a Cash Flow report; Reports -> Cash Flow -> Itemized
Categories; Confirm that the _401EmployerContribSpouse is one of the
listed categories with a non zero dollar amount.
* Now go and EDIT the accepted Spouse paycheck in the Checking
account. Change either the Employee Contribution and/or Employer
Contribution amount and save the changes.
* Go back to the Itemized Categories Report. The
_401EmployerContribSpouse category has now changed to
_401EmployerContrib.

Anyone have any idea on how to reassign the category (short of
deleting the affected transactions and recreating them from scratch;
not something that I am looking forward to doing!)?

I noticed something similar... even though the paycheck dialog has an entry for
my 401k contribution that should be catagorized as _401kContrib, my budget
reports that I never have anything in that category. I'm talking about the
report I have on the main page that shows the top 5 or 6 categories that are off
budget. I've tried all sorts of things, and have never gotten that to work.

Jay

I had the exact same problem - discovered it when I ran a report for
2004 contributions to spouse's 401K. The paycheck in question was
edited, so I agree is it a bug related to that. I also have spent
several hours trying to fix this with no success.

Judy

Jay Baker wrote:
Your problem does not sound like the op's to me.

And I don't see your problem at all; I have a test file for
Q2004 and I see _401kContrib showing in the Top-Out-of-Budget
report there ... with the correct actual amount. I don't want
to appear to be stating the obvious, but if you have budgeted
for the correct amount of 401k contributions, then _401kContrib
should not show in the out-of-budget report on the home page.
If you want to satisfy yourself that _401kContrib will show if
it is in the top-out-of-budget categories, temporarily modify
your budget for _401kContrib to be zero. (Q2004 H&B for
Windows, US).

--
John Pollard
First initial underscore Last name at mchsi dot com
Please reply to newsgroup

I just tried to duplicate your results in Q2004 H&B for Windows,
US and could not. Not sure what I did wrong. :(

The only difference I know of is that I didn't start with a
"new" file because I already had a test file and I didn't create
a new checking account because I already had one. But I created
a new spouse 401k, and a new spouse paycheck, Entered the
paycheck in the checking account register, modified - at
separate times - both the employer and employee contributions
.... the category for _401EmployerContribSpouse remained
unchanged.

Did you duplicate your results in a new Quicken file, or have
you only seen it in your regular file? And was that regular
file converted from a previous version of Quicken, and/or was
the 401k account converted to a 401k account from a tax-deferred
Brokerage account. (I'm just fishing for possibilities that
might explain our different results).

I could not find anyway to modify the categories that Quicken
assigns to 401k contributions, so I can't help you there.

Why are you finding it necessary to change paycheck transactions
after they are in the register? Can you avoid the problem by
not entering them in the register until you have the correct
breakdown of deductions?

Also, you might not have to recreate the transactions from
scratch; I'm just thinking aloud now. Assuming that the only
thing that changed from paycheck to paycheck were the 401k
contributions, can you create a second scheduled Paycheck for
your spouse; and plan to use that to re-generate paychecks that
were modified in the register? You can modify just the 401k
contributions, then modify the next scheduled date, then "Enter"
the transaction. You would delete the old paycheck transactions
of course; pretty easy in Q2005, I think.

--
John Pollard
First initial underscore Last name at mchsi dot com
Please reply to newsgroup

I have the problem with my regular file and have been able to create
the problem within a new "test" file on both my main computer (which
has the main data file) and my laptop. Of course, I did the "test"
files only with Q2005. My regular file has data going back 14 years
(Windows 3.1 days! :-) ) and it has been though various Quicken
upgrades since then.

The reason for my editing the paychecks "after the fact" is that my
spouse is paid hourly and the paycheck is not a set amount everytime.
Also since she is also part time, it sometimes takes a few days before
she gets the actual paystub home. The anal side of me wants the
transaction in the register once the funds hit the bank account :-)
Regardless of my reason, I do think that this is a bug that does need
to be verfied and corrected.

I did correct all of the affected transaction by editing the scheduled
date on the existing paycheck and entering the transactions again (and
deleting the "erroneous" entries.

I just wanted to comment that I have the same exact error. When replacing some old check entries for my wife, I noticed on my reports that those entries had the incorrect category for 401k transactions.

I solved this by deleting the entire check out of Quicken and posting a new transaction (thus not using the Paycheck transaction type).

Does anyone know if this got logged as a bug with Quicken.

This is not fixed since Quicken 2006 r2.