[GH-ISSUE #2669] [Feature] Over budgeted templated category should defund on next template apply #15298

Closed
opened 2026-04-14 18:13:01 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @slimslickner on GitHub (Apr 26, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2669

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?

If a category is a one-time spend item, like a vacation, with a template like this: #template 2500 by 2024-07 spend from 2024-05, an over-budget amount will decrease over time instead of immediately.

With the example above, if my current budgeted amount in April 2024 is $3000, then I apply my template to May 2024, the budgeted total will decrease by 1/3 (May, June, July remaining to achieve the template total), or $167.67. It would do the same in June, and again in July (assuming no spending during the allowed months).

This example might be complicated but my ask is ultimately this: If a templated category is over-funded, the next template apply would take the budgeted amount all the way down to the expected total immediately, rather than spreading that decrease over the number of months remaining.

Describe your ideal solution to this problem

I think if the delta between current balance and target balance is a positive (current > target) then applying the template should remove all funds to get to the targeted template balance immediately. If the delta between current balance and target balance is negative (current < target) then applying the template should add the funds in the currently method (splitting remaining amount between the remaining months).

Teaching and learning

I know the template is still in beta testing, having a UI would help, as would this issue.

I do not believe specific documentation would be necessary.

Originally created by @slimslickner on GitHub (Apr 26, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2669 ### 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? If a category is a one-time spend item, like a vacation, with a template like this: `#template 2500 by 2024-07 spend from 2024-05`, an over-budget amount will decrease over time instead of immediately. With the example above, if my current budgeted amount in April 2024 is $3000, then I apply my template to May 2024, the budgeted total will decrease by 1/3 (May, June, July remaining to achieve the template total), or $167.67. It would do the same in June, and again in July (assuming no spending during the allowed months). This example might be complicated but my ask is ultimately this: **If a templated category is over-funded, the next template apply would take the budgeted amount all the way down to the expected total immediately, rather than spreading that decrease over the number of months remaining.** ### Describe your ideal solution to this problem I think if the delta between current balance and target balance is a positive (current > target) then applying the template should remove all funds to get to the targeted template balance immediately. If the delta between current balance and target balance is negative (current < target) then applying the template should add the funds in the currently method (splitting remaining amount between the remaining months). ### Teaching and learning I know the template is still in beta testing, having a UI would help, as would [this issue](https://github.com/actualbudget/actual/issues/1006). I do not believe specific documentation would be necessary.
GiteaMirror added the needs votesfeature labels 2026-04-14 18:13:01 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Apr 26, 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:2079361562 --> @github-actions[bot] commented on GitHub (Apr 26, 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 -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#15298