401K contribution not recorded in 401k register

Jim32
Jim32 Member ✭✭
edited January 2019 in Investing (Windows)

I do not contribute to the 401k, but my company does contribute on my behalf.  Up until April 2017 this was not a problem. Employee contribution was 0.00 and Employer Contribution as $$$.  There was 1 line recorded in the 401k for $$$.  However, something must have changed in Quicken starting May 2017.  Since then, the Employer Contribution will not record into the 401K at all.  If I put a placeholder of $1 in the Employee Contribution, it records fine in the 401k as $1.  However, the Employer Contribution will not record.


This is causing a huge deficit on the 401k.  Please help! 

Comments

  • NotACPA
    NotACPA Quicken Windows Subscription SuperUser ✭✭✭✭✭
    edited October 2018
    More info needed.  What Q product are you running?  What Build/Release (do HELP, About Quicken for this info)?  What country?
    AND, how are you recording those 401k contribs in Q?  Also, were you contributing to the 401k prior to April 2017?

    Q user since February, 1990. DOS Version 4
    Now running Quicken Windows Subscription, Business & Personal
    Retired "Certified Information Systems Auditor" & Bank Audit VP

  • Unknown
    Unknown Member
    edited July 2018
    I am having the same type of issue with a 401k loan repayment. I have no pre-tax contributions but do have an after-tax loan repayment. From May 2017 entries to now, when I enter a paycheck, the contribution shows in the register but later disappears. If I go back into the paycheck and hit enter, I can get the contribution to show back up in the register, but it will later disappear when I re-open the file. 

    There is another thread about this error: https://getsatisfaction.com/quickencommunity/topics/disappearing-401-k-contributions-from-paycheck
    Support acknowledged the issue, but no timetable for a resolution.

    I am using Quicken Premier 2018 Version R9.34 Build 27.1.9.34
  • Tom39
    Tom39 Member ✭✭✭
    edited January 2019
This discussion has been closed.