nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New Q Mac 7.0.3 update broke bill categories!

Brian83

Ever since the latest update to 7.0.3, when marking bills as paid in Bills & Income, it will enter the transaction into my register but totally kicks out the category and marks every one as "uncategorized", so I have to edit the transaction in the register and set the category back. For example, "Home - Renter's Insurance" or "Bills & Utilities - Electricity" etc etc. This also happens to my income reminders where I have splits set up for my deductions. It kicks all of those out and marks my deposit in the register as "uncategorized" so I have to go through and re-add all of the splits for my deductions. Not sure why this is broken now but PLEASE FIX!! This adds a lot more time I need to spend to make sure everything is entered correctly!

Find more posts tagged with

Comments

Quicken Anja

Hello @Brian83,

Thank you for reaching out to the Community about your issue, though I am sorry to hear that you are experiencing this.

Do you have a recent pre-update backup you can restore? To start with, I suggest restoring a backup file that was saved prior to when this issue started to see if the same issue occurs in the restored file. If needed, please, review this support article. Scroll down and open the blue dropdown section(s) titled Restore Quicken data and/or Restore an automatic backup for instructions on how to restore a backup.

Let us know how it goes!

QuickT

Release 7.03 has some form of bug in Income reminders. If you select the Income payroll item and use …. Edit and Mark as Deposited, the split edits do not transfer to the transaction in the register, the transaction becomes an uncategorized transaction. Please could you check this introduced apparent bug and suggest ways to resolve?

[Merged Post]

Brian83

The same issue occurs after restoring from a backup. It's something that's wrong with this specfic update.

jacobs

@QuickT @RickO What exactly are you doing in processing this deposit, because I haven't seen this behavior. In my checking register, I just clicked on a scheduled paycheck deposit and marked it Deposited; it changed to an active transaction with all the splits intact. Then I went to the Bills & Income screen, clicked on the Income tab, selected the next paycheck deposit, clicked the ••• icon and selected Mark as Deposited. Again, the transaction posted in the checking account register with all splits intact.

[Merged Post]

jacobs

@Brian83 Is your issue the same one reported by another user in this other thread?

If so, perhaps we can get a moderator can break these related comments into their own thread and report it to the Mac development team.

QuickT

@RickO @jacobs I have kept everything up to date and this feature that I use every week broke when I updated to 7.03

If you do not edit the Payroll income reminder, then no issues. If you open it and say Mark as deposited, no issues. It is only when one edits the splits and then save(i.e. … Edit and Mark as Deposited) the splits disappear to a uncategorized transaction. For payroll items there is always some small difference in tax deductions - or possibly income earned, so the need to edit the split occurs. I do this 4 times a month so that is why I immediately noticed the errant behavior.

Perhaps I missed an update, but pretty sure this bug was delivered in the last patch. For now, I will simply Deposit the item 'as is" THEN edit it in the Transaction register to adjust tax amounts etc. until a fix is released.

[Merged Post]

jacobs

@QuickT @RickO Thanks for clarifying the very specific action needed to trigger this bug. Until the bug is fixed, the workaround of first marking the transaction as Deposited and then editing the transaction splits makes sense, and fortunately isn't too painful.

[Merged Post]

Quicken Kristina

Hello All,

Thank you for taking the time to visit the Community to report this issue, though we apologize that you are experiencing this.

We have forwarded this issue to the proper channels to have this further investigated. In the meantime, we request that you please navigate to Help > Report a problem and submit a problem report with log files attached and (if you are willing) a sanitized copy of your data file in order to contribute to the investigation.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.

We apologize for any inconvenience!

Thank you.

(CTP-6795)