nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Everything Else" Bug Thread Closed Without Update: Requesting Accountability and Transparency

auga

To Quicken Moderators and Team,

This bug has now been open for over 8 months — first reported on February 8, 2025, after the release of Quicken US Version R61.17, Build 27.1.61.17. The community has thoroughly documented the issue and its ongoing impact, including two major threads that have both been closed without resolution or substantive update.

References:

Closed thread #1 (original discussion):
- "Everything Else" in Budget reports OP: @GTmem
Closed thread #2 (recently closed):
- Everything Else & Budget Reporting - Ticket(s) Closed? [Mod Note: Keep Thread Open] OP: @Dom1
Recent related posts without any ties to main threads or the ongoing Community Alert:
- "Everything Else" - can it be removed from budget OP: @John, Version R64.30
- Eliminating "Everything Else" from Budget Reports OP: @Rocket1

Key Points:

No solution has been provided, and the last official update to the Community Alert post was in March 2025.
The bug randomly inserts an “Everything Else” line in budget reports, severely undermining the accuracy of report data for subscribers.
Moderator Anja previously edited thread #2 to indicate “[Mod Note: Keep Thread Open]”, yet this thread was nevertheless closed without explanation or substantive update.
Recent moderator replies on new posts never reference this known issue or link back to the Community Alert/tracking ticket.
Users continue to report, troubleshoot, and offer workarounds that only partially address or obscure the error.

We Need:

Clarity on why thread #2 was closed despite explicit moderator assurances, continued impact, and recurring user posts.
A visible, substantive update regarding the current status of the ticket.
A renewed commitment to keep open threads and alerts for high-impact, unresolved issues, so users can follow progress and share information.
Moderators and support should actively connect new posts and user complaints with the central threads/tracking links.

For 8 months, users have waited for communication and resolution. Closing active threads and failing to acknowledge the problem only deepens frustration and undermines trust in Quicken’s support. Please reopen the discussion, provide a current update, and keep all relevant channels open until the issue is actually resolved.

Thank you,
Auga

I'm copying all the prior posters for these threads:

@GTmem @Pedro504 @Chris_QPW @Steelpirate @jagshead @RK7 @spreeter @Lans Rothfusz @dan_cowan7711 @bmackey55 @Bananabowl @djruiz15 @Strike @Dom1 @bfranz4 @bsantelli @Richard Schreyer @Ron7 @bmciance @John, Version R64.30 @Rocket1

Find more posts tagged with

Comments

Dom1

Yes, quite ridiculous.

Pedro504

Please reopen the discussion, provide a current update, and keep all relevant channels open until the issue is actually resolved.

Jim_Harman

@auga and others, did you try the fixes recommended in the newer discussions that you referenced? Maybe one of them will resolve your issue.

Please let us know the result.

If you see new discussions on an older issue, you should be able to click on "Flag" at the bottom. There you can request that the Moderators merge the discussions. Be sure to include a link to the earlier discussion in your request.

I think the closing of inactive discussions is a semi-automated process, so the Moderators may have missed the note to leave your discussion open.

One way to keep a discussion open even if no one else has commented is to add a comment about once per month with any fresh information that you have. That will bring your discussion back to the top of the recent discussions, making it easier to find, and it lets everyone know if the issue is still occurring for you.

Bananabowl

I also think it's ridiculous that no explanation can be given for this error. I ran the same budget reports for probably over 20 years until this issue came up earlier this year. They changed something that produces obvious errors and can't give any accounting for why.

Dom1

https://community.quicken.com/discussion/comment/20516354#Comment_20516354

Thanks for your insights on how this forum works (not sarcasm). Upon your post, I did reread Bill West's solution (not sure if there are others) and the various subsequent responses.

I did try Bill's suggestion this morning and as I selected categories certain Everything Else listings disappeared while others showed up that weren't there before. Kinda like whack a mole. It also looks like there are various trade offs from others who tried this none of which are welcome.

I'm just frustrated with how this issue has been handled or the lack thereof

Thanks again

Pedro504

https://community.quicken.com/discussion/comment/20516354#Comment_20516354

Yes, I tried all, to date nothing has solved the problem.

I have also enlisted a highly experienced Quicken user to review my reports in person and he was not successful.

auga

Thank you, @Jim_Harman.

Regarding the idea to “flag” new threads for merging:
When I attempted to flag the thread, the forum prompted me to provide details about “abuse.” Since there is absolutely no abuse involved in these posts, that didn’t seem like the right path—so I backed out.

Keeping the thread alive with periodic comments is a helpful idea and one I may use going forward. However, if you look at the ‘second’ thread (now closed), moderator Anja had explicitly added a note in the title instructing that the thread remain open—implying that user “bumps” shouldn’t be required when Quicken acknowledges an issue is unresolved and high-impact. Unfortunately, even that thread was closed automatically, with no further updates from the team or moderation.

Lastly: As a SuperUser, are you able to reproduce this bug in your own Quicken setup, and if so, have you tried any of the suggested workarounds? Firsthand confirmation (or refutation) from experienced community members like yourself would add useful clarity to the many user reports regarding the bug’s persistence and the inconsistent success of temporary “fixes.”

Thank you again for your time and suggestions.
—Auga

https://community.quicken.com/discussion/comment/20516354#Comment_20516354

Jim_Harman

@auga Sorry, I did not realize that not everyone has the same options under Flag.

I see an "Everything Else" line at the bottom of my Current Budget report. This corresponds to two situations:

payments that use a Subcategory where the main Category was not included in the budget.
payments that use a main Category with no subcategories, where the main Category was not included in the budget.

I agree it is hard to tell what is being lumped into the Everything Else line. But if I go to the Planning > Budgets page and select the graph view and Yearly, there is an Everything Else line at the bottom of each Category Group that shows the spending for each Category that is not included in the budget.

Does that match what you are seeing, or is your problem different?

I like your poems BTW.

auga

Thank you, @Jim_Harman, for taking the time to confirm what you’re seeing and for offering that detailed description.

Your explanation makes sense for how “Everything Else” is intended to behave—essentially summarizing transactions in categories that haven’t been explicitly included in the budget. However, the ongoing issue reported by multiple users (starting with the release of R61.17 in February 2025) is a bit different. In this case, “Everything Else” is appearing where it shouldn’t, often within category groups that already have all subcategories budgeted, or as a completely separate line that repeats or mis-sums totals from unrelated categories.

The result is not a “catch-all” subtotal—it’s effectively a phantom entry that distorts reports, even though it doesn’t impact the grand totals. It’s also inconsistent: for many users, it behaves differently from what appears in the Graph or Annual Budget view. That mismatch is what distinguishes this as a post-update bug, not a normal function of Quicken budgeting.

Thanks again for engaging on this and for helping users maintain visibility on a bug that continues to affect reports across several versions.

— Auga

auga

🎃 The Phantom of the Budget Sheet (Halloween Edition)

It starts with calm—a tidy plan,
Each dollar placed by careful hand.
But click “Report” and there it dwells—
The dread, unnamed “Everything Else.”

It copies sums from far and near,
Amounts I swear were never here.
No poets could invent such math—
It laughs along my budget path.

I’ll toggle views, I’ll click and sort,
Still phantom lines invade the report.
Are ghosts of spreadsheets haunting me?
Or is this Quicken’s mystery?

Perhaps one day, by code divine,
A patch will ban this spectral line.
Till then, I’ll sip my fiscal tea—
And toast to ghostly currency.

Jim_Harman

@auga

You mention "category groups." To be clear, I think you mean main Categories that have subcategories, rather than what Quicken calls Category Groups, which are groups of main Categories, like Personal Income, Personal Expenses, etc. If you go to Tools > Category List, the built in Category Groups are listed in the grey area at the left, and you can add your own. Do I have that right?

Also I think I see what you are talking about in the attachments that have been posted earlier. When I run the default Current Budget report from the Reports > Spending menu, the only place I see "Everything else" is at the very bottom of the report. I don't see "Everything Else" lines interspersed inside the report. I seem to recall that the Current budget report accessed via the Reports drop-down on the Budgets page is not quite the same as the one on the Spending menu.

Do you see the problem with the Current Budget report on the Spending menu?

To avoid confusion when describing problems to the Quicken folks and others, it is best to use the exact Quicken terminology, and if possible to reproduce the problem in one of the built-in reports, not one that you have customized and saved.

auga

Thank you, Jim—your clarification on terminology and your approach to troubleshooting are genuinely helpful for making this conversation productive for everyone.

It’s probably also worth highlighting that Quicken has already acknowledged this bug and noted it’s under active investigation. At this point, hearing directly from Quicken staff—such as whether they’re able to reliably reproduce the issue and any updates on progress—would be most helpful to users still running into this problem.

On your side:

If your recent testing has started to turn up the “phantom” Everything Else line (appearing mid-report or duplicating/merging sums in strange places), it would be great to hear details or see any examples.
If not, your continued attempts to reproduce it could help pin down when and for whom this bug appears.

It’s encouraging to see both community users and SuperUsers like yourself digging into the details. Hopefully, with some input from Quicken’s end, we’ll have more clarity and a workable fix soon.

Thanks again for your assistance and engagement!

— Auga

auga

Thanks, Jim—and to answer your direct question:
Yes, I do see the “phantom” Everything Else line(s) appear in the default Current Budget report accessed from the Spending menu. This matches the issues documented in the previous threads—with the bug showing up even in standard, uncustomized reports.

Appreciate your continued engagement!

— Auga

Jim_Harman

@auga Please be aware that this is primarily a user to user forum. There are over 100 posts per day and only a few Moderators.. There is no guarantee that the Moderators will see your posts here.

I will tag @Quicken Kristina and @Quicken Anja, who responded in your earlier discussions, in hopes that it will get their attention.

auga

Thank you, Jim—really appreciate you tagging the moderators and continuing to help keep the conversation moving forward.

Just as context for others following along: both @Quicken Kristina and @Quicken Anja have already been active contributors to these discussions . For example:

Kristina provided official replies and updates regarding the status of this bug in February and March 2025 in both the initial and follow -up threads.
Anja responded with moderator notes and status confirmation in May and August 2025 , including the promise in August to keep the now-closed thread open for continued updates.

It's great to have their attention again. Hopefully with renewed visibility, this thread will yield either a substantive progress update or at least confirmation that the current reports and user examples are seen by the right people.

Thanks again for your efforts and for drawing moderator attention to the ongoing discussion!

— Auga

auga

Just checking in for visibility:
The “Everything Else” budget report issue is still present as of October 31, 2025.
No replies or new updates since 10/21/25, even after moderator tags.
Requesting any progress report or next steps from the Quicken team.
Thanks all—issue still ongoing.

Dom1

just a casual query

are you familiar with the everything else issue taking place on the quicken community

That is a very well-known and common topic on the Quicken Community, specifically related to budgeting and reports in Quicken Classic for Windows.

`💰 What the "Everything Else" Issue Is`

The "Everything Else" line is a phantom category that frequently appears in Budget Reports and sometimes the Budgeting View in Quicken, often with a seemingly random or incorrect budgeted amount.

It typically arises due to how Quicken handles the relationship between parent categories and their subcategories, especially when you are selectively budgeting.

The general consensus from the community is that it's a bug or an unintended result of a recent program update (as of early-mid 2025).

`🐛 Common Causes & Workarounds`

Here are the most common reasons users have identified for the "Everything Else" category appearing, along with the suggested workarounds:

`Cause`	`Description`	`Community Workaround/Fix`
`Inconsistent Budgeting`	`Budget amounts are included for` `both` `the main` `parent category` `and its` `subcategories, and the subcategory totals don't equal the parent category budget.`	`Only budget at the subcategory level` `(the lowest level). Deselect the parent category in your "Select Categories to Budget" list.`
`Partial Subcategory Selection`	`You have selected` `some, but not all, of the subcategories under a parent category for budgeting.`	`In` `Planning > Manage Budget Categories > Select Categories to Budget, ensure you` `check all subcategories` `(including "Other") for the relevant parent category, even if you don't plan to use them.`
`Transactions to Parent Category`	`A transaction has been categorized directly to a` `parent category` `that also has subcategories (instead of to a subcategory).`	`Change the transaction's category to a relevant subcategory.`

`🚨 Current Status`

The issue has been widely reported and escalated internally by Quicken moderators (Ticket #11616921/CTP-12275).
As of the last updates, Quicken is aware of the problem but has not yet provided a definitive fix or an ETA for the resolution. Users are advised to "bookmark" the main community discussion for updates.

Would you like me to find the main Quicken Community discussion thread about the "Everything Else" issue so you can follow its status or see more specific user-reported solutions?

Quicken Anja

Hello All,

We understand the continued frustration around this issue and truly appreciate everyone’s patience. The ticket is still open and actively being worked on by our escalation team.

However, they do not provide an estimated timeframe for when fixes will be released. In the meantime, please continue to refer to the existing Community Alert for any and all updates.

We recognize there hasn’t been an update since March, but there’s no new information to share beyond what’s already been posted. Any further updates or developments will be added to the alert as soon as they become available.

We apologize for any inconvenience in the meantime!

As for this thread here—I apologize that it was closed. It should not have been given the Mod Note I placed in the title. I went ahead and reopened it once again, and will send a reminder to my moderator team to pay attention to the Mod Note in the title to ensure it's kept open moving forward.

Thank you!