why does the budget default to one payee?

doverjohnson Member ✭✭
my budget will default to one particular payee in different categories. For example, it will use one payee as the history for several different types of payees. Any idea as to why one payee seems to the linked to the account of many other payees?


  • UKR
    UKR SuperUser ✭✭✭✭✭

    What version, edition level (Starter, Deluxe, etc.) and release (R xx.xx) of Quicken are you using?
    US, Canadian or other country version?
    Is your subscription expired or still active?
    Click Help / About Quicken (Mac: Quicken / About Quicken) to get this information.
    What version of Windows or Mac OS are you using?

    Sometimes a picture is worth a thousand words …
    Can you please capture one or more images of the parts of your Quicken window showing the issue, sensitive information blacked out as necessary to protect your privacy but annotated to describe the situation, and attach the image(s) here?


    Please save images to files of file type PNG, JPG, or GIF only. They're easier to work with than PDF files.

  • doverjohnson
    doverjohnson Member ✭✭
    Thank you for your suggestions. In researching each occurrence, I discovered that the default only occurs in the "Everything Else" category. It is also tied to the reminder function. I deleted the reminder and then it disappeared from every "Everything Else". Thanks.
  • UKR
    UKR SuperUser ✭✭✭✭✭
    Without seeing what exactly you have or had defined, I'm still somewhat in the dark as to what you're referring to.
    Based on what you told me, you created a Scheduled Reminder which was associated with a category or subcategory. This category is not explicitly defined in your Budget. Therefore it appears in a catch-all-category, "Everything else". Read more about budgets and "Everything else" here: https://help.quicken.com/display/WIN/Work+with+a+budget
    In the budget, when option "Include Reminders" is enabled, the impact of reminder instances on future months will show in the Actual columns as if the reminder had already executed.
This discussion has been closed.