New Category I didn't create has appeared

Quicken Windows Subscription Member ✭✭✭
edited March 11 in Reports (Windows)

I'm on Quicken Premier for Windows, R61.17 Build 27.1.61.17

Went to pull a report and got the message that new categories had been created and did I want to add them to the report. When I viewed the Category name, it was odd. ACCT_118a0. Ran a report to find the associated transaction, and there's nothing. I used all dates, all accounts including hidden. No transaction is associated with this category. How would this have gotten created? Is there any downside to just deleting it?

Best Answer

  • Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓

    Those sorts of notations that start with ACCT seem to be associated with temporary Accounts that Quicken creates when downloading information and should be removed by the program at some point. If you've accepted all transactions that came with the latest download and everything otherwise looks to be good in your file, I'd think that deleting them would not be a problem. You might want to run a file Validate & Repair here.

Answers

  • Quicken Windows Subscription SuperUser ✭✭✭✭✭

    While it shows up in the category list, it is actually an account and is in the list for possible use when making a transfer.

    Check your Account List. It may have been created during a One Step Update and then deleted/renamed.

    -splasher using Q continuously since 1996
    - Subscription Quicken - Win11 and QW2013 - Win11
    -Questions? Check out the Quicken Windows FAQ list

  • Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓

    Those sorts of notations that start with ACCT seem to be associated with temporary Accounts that Quicken creates when downloading information and should be removed by the program at some point. If you've accepted all transactions that came with the latest download and everything otherwise looks to be good in your file, I'd think that deleting them would not be a problem. You might want to run a file Validate & Repair here.

This discussion has been closed.