[Feature] Tracking budget should treat Savings and Investments differently #1538

Closed
opened 2026-02-28 19:46:44 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @valeriocost on GitHub (Oct 24, 2024).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

In the Budget section, each categories balanced is colored in red if it exceeds the budget and white otherwise.
For Savings and Investments, however, the logic should be inverse. If I "spent" more in these categories I should be rewarded (green color?) and if I spent less the color should be red.

Moreover, I would exclude those transactions from the Expenses pie chart at the top.

Describe your ideal solution to this problem

Add a property to a category (or group of categories) with the inverse logic.

Teaching and learning

No response

Originally created by @valeriocost on GitHub (Oct 24, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [X] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? In the Budget section, each categories balanced is colored in red if it exceeds the budget and white otherwise. For Savings and Investments, however, the logic should be inverse. If I "spent" more in these categories I should be rewarded (green color?) and if I spent less the color should be red. Moreover, I would exclude those transactions from the Expenses pie chart at the top. ### Describe your ideal solution to this problem Add a property to a category (or group of categories) with the inverse logic. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 19:46:44 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 24, 2024):

Thanks for sharing your idea!

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Oct 24, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Author
Owner

@rodrigost23 commented on GitHub (Jun 13, 2025):

I would love this. Is there any workaround for now?

@rodrigost23 commented on GitHub (Jun 13, 2025): I would love this. Is there any workaround for now?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1538