Year-Old Confirmed Bug: Incorrect Account Balances in Investment Reports (Still Unresolved)

Question

I am writing to request a status update on a critical bug that has remained unresolved for over a year.

Issue: Incorrect account balances appearing in the Account Balances Report for Investments.

Reference Discussion: I reported this bug over a year ago. In May 2025 I took the time to meet directly with the development team to demonstrate this issue. Subsequently, I confirmed in June with the team that they identified the underlying cause and stated it would be resolved. Their response "We have been able to reproduce the issue in the file you shared and will soon be prioritizing it for upcoming/future patch release of Quicken Desktop Product for Windows."

Despite this confirmation and the passage of time the bug persists in the current release.

Accuracy in investment reporting is a core function of Quicken. It is incredibly frustrating to provide direct, 1-on-1 feedback to the developers only to have the fix stall for a year.

My Current Environment:

* Product: Quicken Classic Deluxe
* Version: R65.29
* Build: 27.1.65.29

Can a Moderator please escalate this thread? Is a fix is actually in the pipeline or why a "confirmed" resolution has not been implemented.

@Quicken Anja

https://community.quicken.com/discussion/7958012/bug-report-incorrect-account-balances-in-account-balances-report-for-investments

bobandsherry82 · Answer

rjsle1 - I had worked with development to track down the cause of my issue.  It was due to options (calls and puts) not being properly shown in the account balances (expired calls and puts still had a value shown which obviously is wrong) while the balances shown in the account listing was correct.  Not sure how a report differs from the 'ledger', and why it takes a year to undo what Quicken messed up in a release.  But here we are.  Do you have any calls and puts (now expired) in your investments?  If not, then this may be a different issue for you.

bobandsherry82 · Answer

Thanks for responding Quicken Anja.  It is disappointing that a year has passed, and what took Quicken one update to break, remains unresolved — despite the developer informing me that the issue had been found and was awaiting integration to a release.

Quicken Anja · Answer

Hello @rjsle1,

Thanks for reporting that you’re seeing this issue as well. As mentioned previously—this is a known bug that the team is actively working on (CTP-11685/QWIN-24438), though there’s no ETA for a fix yet.

We appreciate your patience while the development team continues working on a resolution!