Wrong Saved Reports

Prairie Primrose

I have Quicken Classic Deluxe which I've used for many years on Windows, and I keep both updated. Last month I created two reports for year-to-date housing expenses and mortgage payments and saved them in a folder for 2025 taxes. Today I tried to open these reports: The correct titles are listed in the folder, but when I open the reports they are completely irrelevant reports of different kinds and dated 20 years ago! What in the world is going on? I've read the information on the help board about making sure I am logged in correctly, have the right data file open, etc., but I am the only user and I have only one data file. As it is now, all I can do is recreate each report from scratch each time I want to update it, and then print or save a copy outside of Quicken, knowing that the next time I will have to do it all over again. Useless!

Quicken Kristina

Hello @Prairie Primrose,

Thank you for sharing your experience. To help troubleshoot this issue, please provide more information. Does this issue happen every time you create a saved report, or was this a one-time occurrence with those two saved reports? Which reports did you use to create these two saved reports (for example a Transaction report, an Itemized Category report, etc.)?

I look forward to your response!

Janny Kuman

That definitely sounds frustrating! I've experienced a similar situation before where saved reports in Quicken were suddenly pulled in data completely unrelated. In my case, it was due to the report customization not saving properly after a program upgrade. You might try this approach: recreate one of the reports, then go to Reports > Memorized Reports > Edit and save with a new name. Of course, you want to double-check that an auto-backup of your data file isn't set to an older version — Quicken sometimes relies on report settings of an older backup. If that doesn't fix it, you may want to consider validating your file (File → Validate & Repair). It resolved some weird behavior for me too.

Quicken Kristina

Hello @Janny Kuman,

Thank you for sharing your experience!

Hopefully it helps others encountering similar issues!

Prairie Primrose

Thank you for your suggestions. I still have the same problem. Here are details of my latest attempt:

Today I deleted all the reports I'd saved in my 2025 Tax Reports folder and started over.

I created a new file from scratch by right-clicking on one of my mortgage payments in the register and then selecting "Payments made to (my mortgage company)". It created the correct Payee Report - Year to Date. I changed the name to "2025 Mortgage Payments YTD" and saved it in the 2025 Tax Reports folder. I closed the report and went to My Saved Reports, checked the file and the correct title was listed. But when I opened the saved report, instead of my mortgage payment report, I got a "2005 Estimated Tax Payments" report—just like before, a 20-year-old report! It makes no sense. I recreated the other report, Housing Expenses from an Itemized Category report form, and had the same result. When I tried to open the saved file with the proper name, I got that same wrong file, "2005 Estimated Tax Payments." Saving this draft for now….

LATER: I accidentally made a discovery. If from the Reports menu I go directly to My Saved Reports & Graphs and then to the folder and file, I get the wrong file. If instead, from the Reports menu I open the Reports & Graphs Center and from there select the folder from the My Saved Reports list, I get the correct file! They are named correctly in both instances, but only one path opens the correct file. I hope that makes sense to somebody. At least I now have a work-around to open the correct report.

Quicken Kristina

Thank you for your reply,

I'm glad to hear that you found a work around.

I haven't been able to replicate the issue in my Quicken. I tried with the Spending by Payee report and with the Itemized Payee report, but I couldn't get Quicken to open the wrong report when I opened the saved reports again.

Because of this, I suspect the issue may be a file-specific issue. If you already followed @Janny Kuman's suggestion to validate, then the next step is restoring a file from before this issue started, and testing to see if that resolves the issue.

I hope this helps!