github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-11-12 03:42:19 -06:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #2330] Create a burn-up report to manage daily, discretionary expenditure #42571

New Issue
Closed
opened 2026-04-26 02:31:50 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-26 02:31:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @TheBlueCircle on GitHub (Feb 4, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2330

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?

I have a budget group for fixed costs (like bills) and one for discretionary spend. I'd like to better manage my discretionary spend by providing visual guides and breakdown of spend by day.

Describe your ideal solution to this problem

I suggest a simple, intuitive graph that shows me my budget for day-to-day spending for the month in the form of a burn-up chart. Monzo bank has a similar function in the US and the UK, which looks like this (some small edits for privacy)

Screenshot_20240204_153443_Monzo

In this example, the dotted line is the burn down chart showing the average spend per day for the selected categories if you are to spend your whole budget (which Monzo calls a target). The heavy line is the actual spend. If the heavy line is below the dotted one you are overspending; if it is above you are underspending.

I suggest that we don't replicate this chart as-is because it has a few fundamental issues. It is not immediately intuitive (probably because it is burn down target than burn up, and there could be better use of colour to show what is good and what is bad) and it suggests that a budget is a target for spending that you should meet (rather than a maximum figure to stay within).

That said, the concept is useful and could be very powerful in Actual to help manage daily, discretionary spend. I suggest we take inspiration from a burn chart, but make it better. Specifically:

  • Create a burn-up report (rather than a burn down one)
  • Allow this to be driven from the budget assigned to any combination of categories (or category groups)
  • Provide helpful psychological nudges (such as the graph being in green if within budget or red if above the budget).
  • Have dynamically updated text that shows for the current day a) the maximum you can spend per day to remain on budget, b) how much you've spent so far on that day, c) how much you're within or above budget.

This would be particularly powerful if available on mobile.

This could provide the basis for more sophisticated burn charts (for example, the guide line could be non-linear to include expected future transactions or bills) - but it would be helpful to test if this would be a useful addition and, if so, develop the basics and test response to it before considering additional PRs.

Teaching and learning

Done right, this should be an intuitive and helpful addition to Actual and could helpfully sit alongside the existing reports.

It shouldn't create any additional learning overhead over and above existing reports, however additional documentation would likely be required (I can contribute to that).

Originally created by @TheBlueCircle on GitHub (Feb 4, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2330 ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I have a budget group for fixed costs (like bills) and one for discretionary spend. I'd like to better manage my discretionary spend by providing visual guides and breakdown of spend by day. ### Describe your ideal solution to this problem I suggest a simple, intuitive graph that shows me my budget for day-to-day spending for the month in the form of a burn-up chart. Monzo bank has a similar function in the US and the UK, which looks like this (some small edits for privacy) ![Screenshot_20240204_153443_Monzo](https://github.com/actualbudget/actual/assets/153461238/42ab5c48-6cf2-4c2b-bd4a-7e68313ed5a6) In this example, the dotted line is the burn down chart showing the average spend per day for the selected categories if you are to spend your whole budget (which Monzo calls a target). The heavy line is the actual spend. If the heavy line is below the dotted one you are overspending; if it is above you are underspending. I suggest that we don't replicate this chart as-is because it has a few fundamental issues. It is not immediately intuitive (probably because it is burn down target than burn up, and there could be better use of colour to show what is good and what is bad) and it suggests that a budget is a target for spending that you should meet (rather than a maximum figure to stay within). That said, the concept is useful and could be very powerful in Actual to help manage daily, discretionary spend. I suggest we take inspiration from a burn chart, but make it better. Specifically: * Create a burn-up report (rather than a burn down one) * Allow this to be driven from the budget assigned to any combination of categories (or category groups) * Provide helpful psychological nudges (such as the graph being in green if within budget or red if above the budget). * Have dynamically updated text that shows for the current day a) the maximum you can spend per day to remain on budget, b) how much you've spent so far on that day, c) how much you're within or above budget. This would be particularly powerful if available on mobile. This could provide the basis for more sophisticated burn charts (for example, the guide line could be non-linear to include expected future transactions or bills) - but it would be helpful to test if this would be a useful addition and, if so, develop the basics and test response to it before considering additional PRs. ### Teaching and learning Done right, this should be an intuitive and helpful addition to Actual and could helpfully sit alongside the existing reports. It shouldn't create any additional learning overhead over and above existing reports, however additional documentation would likely be required (I can contribute to that).
GiteaMirror added the feature label 2026-04-26 02:31:51 -05:00
GiteaMirror commented 2026-04-26 02:31:53 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 4, 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 👍!

<!-- gh-comment-id:1925804060 --> @github-actions[bot] commented on GitHub (Feb 4, 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 -->
GiteaMirror commented 2026-04-26 02:31:53 -05:00
Author
Owner
Copy Link
Copy Source

@jsehnoutka commented on GitHub (Apr 19, 2024):

#2622 will implement this

<!-- gh-comment-id:2067265497 --> @jsehnoutka commented on GitHub (Apr 19, 2024): #2622 will implement this
GiteaMirror commented 2026-04-26 02:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@youngcw commented on GitHub (Oct 18, 2024):

Added by #2622

<!-- gh-comment-id:2422975673 --> @youngcw commented on GitHub (Oct 18, 2024): Added by #2622
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No labels feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#42571