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 & Budget Reporting - Ticket(s) Closed? [Mod Note: Keep Thread Open]

Dom1

At least two tickets have been closed related to the infamous "Everything Else" category appearing on budget reports with bogus figures. Is there still a particular ticket that is open related to this issue or has Quicken decided it's not worth fixing in a timely manner if at all? Well, actually, a timely manner has come and gone.

Thanks,

Find more posts tagged with

Budgets

Reports

Known Issues

Windows

CTP

Comments

bmciance

If you are talking about posts on this site being closed, these are not support "tickets". This is a user to user discussion forum. There are some Quicken employees here also and if they spot a major issue in the discussions they may submit it to support. The fact that a discussion is closed just means that the Quicken moderators believe the discussion has run its course. If you want to submit a "ticket" for the issue you should contact Quicken support.

Dom1

Thanks, I'm aware of this. Other people had opened actual support tickets that to my knowledge didn't resolve the issue (I know I'm still experiencing it). I was a little surprised that the tickets were closed without any update from a Quicken moderator so wanted to make sure there wasn't another ticket still open and to mildly express my frustration.

auga

Quicken Team and Fellow Users,

It's now been months since the "Everything Else" budget report bug first appeared (shortly after R61.17 rolled out in early February 2025). In that time, dozens of users have documented its behavior, posted screenshots, explained reproducible patterns, and even suggested potential causes.

Yet here we are, in August, with:

No confirmed fix
No clear ETA
Closed forum discussions and tickets without resolution

It bears repeating: this isn’t an obscure edge case. This is a persistent, reproducible error in one of Quicken's core functions—the budget reporting tool that many of us rely on for important financial decisions, presentations to boards/councils, and our own financial planning. Every time this phantom category appears, it undermines trust in the accuracy of the reports.

Why does this matter so much?

The bug inserts a fabricated “Everything Else” line into budget reports, often with nonsensical budgeted amounts.
It confuses report recipients (e.g., church councils, spouses, finance committees) and forces users to waste time explaining that the line is meaningless.
It’s existed across multiple updates—with even saved, previously correct reports now showing the error after the update that introduced it.

User Community Contributions:

TB63 and others have done deep analysis to help identify patterns in how the erroneous total is being calculated.
Multiple users have submitted problem reports with logs and sanitized data to aid debugging.
Temporary workarounds have been shared (selecting all subcategories for budgeting) but they are clumsy and don’t fix the root cause—especially in scenarios where the bug appears despite all subcategories being selected.

What We’re Asking For:

Acknowledgement – A current, official confirmation that this bug is still tracked internally under an active ticket. Closing discussions/tickets without explanation leaves the impression the issue was dismissed.
Transparency – Even if there’s no ETA, we need to know if a fix is planned, in testing, or deprioritized.
Priority – Given this affects core financial reporting integrity, it should be treated with urgency. It’s not just a cosmetic glitch—it impacts user confidence in Quicken data outputs.
Communication – If there were multiple tickets and some were closed, explain why, and whether any active ticket remains.

We—the paying subscription customers—are not asking for instant magic. We’re asking for clear communication, confirmation that the issue is still a priority, and evidence that progress is being made.

Many of us chose Quicken over building and maintaining spreadsheets precisely because we wanted trusted, automated, accurate reporting. But accuracy is non-negotiable; without it, the product’s value is diminished.

It’s time to get this fixed. We’ve been patient. Now we need commitment and clarity.

If you agree this bug deserves an active fix and better communication, please reply here so it can’t quietly disappear from attention.

Dom1

Commenting as requested. Nice posthttps://community.quicken.com/profile/auga

Quicken Kristina

Hello @auga,

Thank you for sharing your feedback. We do have a Community Alert for this known issue:

https://community.quicken.com/discussion/7960466/ongoing-3-13-25-everything-else-now-shows-up-in-budget-reports-no-option-to-remove

Ticket #11616921/CTP-12275 are open and in work. There aren't any new updates yet, but if you haven't already done so, I recommend bookmarking the alert, since any updates, once available, will be posted there.

Thank you!

auga

For anyone new to this discussion – here’s the background on the “Everything Else” budget report issue:

This problem started right after Quicken Windows Subscription update R61.17 hit in early February 2025.
Dozens of us quickly discovered our Budget vs Actual reports suddenly had a phantom category called “Everything Else” — sometimes as a standalone line, sometimes under a group — showing a budgeted amount we never entered.

Original thread:

Key facts from the original (now closed) discussion:

Not in our budgets: The category doesn’t appear in Budget Planning view, only in the reports.
Nonsense totals: Often it’s the sum (or negative sum) of unrelated categories; does not usually affect report totals, but it clutters and confuses.
Appears in saved reports too: Reports created before the update now display the phantom line when re-run.
Inconsistent behavior: For some, it shows in “Budgeted Only” mode; for others, also in “Non-Zero Actual/Budget” mode.
User analysis: Member TB63 reverse-engineered how Quicken is summing “standalone” categories plus parts of a group to create this bogus line.
Workarounds: Selecting all subcategories – even unused “Other” subcategories – sometimes hides it, but not for everyone.
Quicken’s stance: Moderators said it was escalated internally (Ticket #11616921 / CTP-12275) and asked people to submit problem reports… but months passed with no ETA.
Status before close: By mid-July, the bug was still present. The original thread was closed without a fix, despite repeated user requests for updates.

Why this second thread exists:
The closure of that main thread and (reportedly) some related support tickets has left many wondering if Quicken still considers this an active issue.
This July 28 thread was started to confirm whether any open ticket remains — and to continue advocating for a fix to what is still a core reporting accuracy problem.

For long-time Quicken users, accuracy in budget reporting is non-negotiable. This issue isn’t cosmetic — it undermines trust in the tool’s primary purpose.

If you’re still seeing “Everything Else” in your budget reports, please chime in here. More voices = more visibility.

https://community.quicken.com/discussion/7959975/everything-else-in-budget-reports

auga

Hello Quicken Team,

It’s now been 10 days since I posted a summary of the history of the “Everything Else” budget reporting bug (linking back to the original discussion). Since then, there’s been no moderator response or user activity here.

I’m concerned this thread could be closed automatically for “inactivity.” I’d like to request that it remain OPEN, because:

This bug is still present in the current release.
The original discussion was closed without a resolution.
Closing this one too, without a fix or a committed update, risks burying the issue and leaving users without a clear place to follow progress.

What we need from Quicken at this point:

A status update – Is there still an active ticket for this issue?
Confirmation that this bug remains on the roadmap for a fix.
Acknowledgement that accuracy in budget reports is a core feature of Quicken, and that this issue has not yet been resolved.

Please don’t let silence + auto-closing threads become the default “resolution.” Many of us actively depend on accurate budget reports, and this phantom “Everything Else” category undermines user trust in the product.

Thank you

Quicken Anja

Hi @auga,

Thank you for following up and for laying out your concerns so clearly—we absolutely understand how important accurate budget reporting is. I want to reassure you that this issue has not been forgotten. The ticket for the “Everything Else” budget reporting bug is still open and actively being worked on by the team.

I don’t have any further details or timelines to share at the moment, but I can confirm it’s on the radar and under investigation. We’ll provide updates as soon as there’s new information.

It is standard for posts to be closed after 30 days of inactivity. However, since you’d like this thread to remain open, I’ve edited the title to indicate this so that myself and my fellow moderators will know to keep it open once the 30-day mark is reached.

Thank you for your patience and for continuing to bring visibility to this issue!

Strike

Hello @Quicken Anja, I think we are all looking for an update on this as it is very frustrating to continually see Everything Else show up on our reports with $0 on it as well as showing up as the last line of our report with the budget of our last category. This has been going on now for about 10 months and no resolution in sight and many of the threads that have Everything Else in the title are closed and unresolved. Can you give us an update and do we all get a reduced subscription since this issue was introduced in January and has yet to be fixed?

Thank you

Trevor

Dom1

As I was starting my budget process this weekend this issue was front and center with the "everything else" appearing in the 2026 budget. Is there no one at Quicken in a position of authority that can address this issue, whether with a real update or fix? Your response from 08/20 (over 3 months ago) stating it's being actively worked on doesn't appear to have shown any results.

I know there was a later comment in October on another ticket but that ticket has been closed, thus the august reference from this thread.

Quicken Anja

Hello All,

Thank you all for your detailed posts and for continuing to share your experiences with the “Everything Else” issue in budget reports. We completely understand how frustrating this is and how important accurate reporting is to your workflow.

I want to confirm the following:

The ticket for this issue (Ticket #11616921 / CTP-12275) is still open, and the team is actively investigating.
The Community Alert for this issue is still live, and any updates or fixes will be posted there first.

At this time, we do not have any new information or timelines to share. If new details become available, they will be posted in the Alert to update the Community as soon as possible.

I can reach out internally to check on the status, but I cannot guarantee when or if we’ll receive additional information. In the meantime, keeping this thread active is helpful for visibility, and we encourage you to continue sharing observations.

Thank you all for your patience and for helping us maintain visibility on this issue.

Steve Florida

This has been going on for too long. Please get this fixed. I noticed that you were very efficient at collecting renewal fees. In early discussions with your support team I had asked about monetary compensation for failure to maintain support while still collecting fees.

Dom1

I was hoping that this fix might be under the tree this year. Unfortunately, the only thing I received was a lump of coal.

Pedro504

https://community.quicken.com/discussion/comment/20530059#Comment_20530059

I got Everything Else

auga

Well, here we are again. Another month has passed, and that “Everything Else” line is still haunting our reports like a ghost that refuses to take a hint.

@Quicken Anja, we appreciate the moderator check-ins, but let’s talk about the suggested "Strategy" of selecting every single sub-category (and the "Other" category) to make this go away. To put it bluntly: it isn't working, and it isn't a solution.

For those of us who use Parent Categories to keep our registers clean, this "fix" is a nightmare. I shouldn't have to drown my budget in 50 unused sub-categories just to hide a reporting error. A budget is supposed to be a tool for clarity, not a cluttered junk drawer of $0 entries.

More importantly, the math is still total nonsense. As TB63 pointed out months ago, this isn't just about unbudgeted items—the report is literally hallucinating. It’s grabbing standalone lines like "Groceries," adding them to unrelated groups, and spitting out a "sum" that belongs in a Dadaist poem, not a financial ledger.

It’s now been over 14 months since R61.17 dropped this bug on us. We’ve gone through the whole cycle:

The "Official Recognition" (Feb 2025)
The "Internal Escalation"
The "Active Investigation"
The endless requests for "Continued Patience"

As a programmer, I find this particularly painful to watch. We aren’t talking about a cosmetic glitch or a fringe feature; we’re talking about the core math of a budget report. If a financial app can’t handle basic addition and hierarchical grouping after 14 months of "prioritized" work, what are we even doing here?

At this point, the community has moved past frustration and into a state of quiet resignation. We’ve written poems to keep from screaming, we’ve done the free QA work for the dev team, and we’ve waited through update after update only to be told to "check the alert."

The "Everything Else" bug isn't an "issue under review" anymore—it’s becoming a permanent monument to technical neglect. We’re not even angry anymore; we’re just tired of waiting for a fix that clearly isn't coming. Trust in a financial tool is built on math you don't have to second-guess. Right now, Quicken is making us do the math by hand just to see if the software is lying to us.

Is anyone actually at the wheel on this one, or should we just start planning the bug’s second anniversary party?

Dom1

well said ✊

Strike

I agree with the above post. We have been waiting for a true fix on this for far to long. This issue and the repeated connection issues with multiple banks have me thinking that Quicken no longer care about its customers. We need some real feedback here and an understanding of what Quicken is doing to address these issues.