The budget feature is not working.

Options
amt606
amt606 Member

I have the Windows version R51.12 build 27.1.51.12 of Quicken. The budget feature is buggy. I created a budget for 2023. Now, when I open the planning window, the budget does not have the same numbers I that I entered to create the budget. It has come up with numbers all on it's own making the whole budget program useless. After I correct the budget and close the program, the errors reappear when I reopen the program. This has been going on for several weeks. The program was poorly designed to begin with. I have been a customer for decades and this is the worst defect I have seen. Users are entitled to a refund on this software for 2023. I will not be renewing my subscription if this isn't fixed asap.

Answers

  • JLF Blessed
    JLF Blessed Member ✭✭
    Options

    Are you using the sync feature for the mobile app? I have been having problems with the budget also messing up and finally after looking at past issues it seems there is an issue with the sync. I have turned sync off, which is a bummer since now we can't use the mobile app.

  • Quicken Kristina
    Options

    Hello All,

    Thank you for taking the time to report this issue to the Community, although we apologize for any frustration or inconvenience experienced.

    This issue is a bug that has been reported to our Development and Product teams for further investigation and resolution. Though we do not currently have an ETA, once a solution is created it will be made available as part of a future release.

    Thank you!

    (CTP-6291)

    Quicken Kristina

    Make sure to sign up for the email digest to see a round up of your top posts.

  • JLF Blessed
    JLF Blessed Member ✭✭
    Options

    Kristina -

    Are these known issues listed somewhere? I looked through all the posts in the "Alerts, Online Banking and Product Issues" section, but could not find this. Also, will this specific fix be listed somewhere that I can monitor so I'll know when I can use the mobile app again?

This discussion has been closed.