github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Template schedule with an increasing % amount #1745

New Issue
Closed
opened 2026-02-28 19:53:39 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:53:39 -06:00
Owner
Copy Link

Originally created by @MattFaz on GitHub (Jan 6, 2025).

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?

Some recurring yearly transactions such as insurance, land rates, etc. increase per year. However the increase amount is often unknown until closer to the date.

As an example you may need to pay Car Insurance on March 01. Typically you'd receive a renewal email ~30-60 days prior, and it generally will have gone up by an amount that was not known until this date.

Currently only options are to update the amount once you know, which may result in you having to allocate far more funds the 1-2 months prior to transaction than you have rest of the year, or add a second template for wiggle room (after manually calculating a % increased amount).

I'd like the templates feature in budgets to be able to accept a percentage increase to try and cover this scenario.

Describe your ideal solution to this problem

#template schedule {SCHEDULE NAME} {INCREASE PERCENTAGE}

As an example, if I have a schedule for "Insurance" and last transaction was $100.

I'd like to be able to write the template as #template schedule Insurance 10% and it will budget for $110.
Whilst I don't know what the amount will be, I know generally costs increase by x% per year.

Teaching and learning

Documentation could easily be added to the currently templates table on this page: https://actualbudget.org/docs/experimental/goal-templates/

I can't think of a scenario where we'd expect a drop in the amount _(e.g. #template schedule Insurance -10%) but it may need to be considered.

Originally created by @MattFaz on GitHub (Jan 6, 2025). ### 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? Some recurring yearly transactions such as insurance, land rates, etc. increase per year. However the increase amount is often unknown until closer to the date. As an example you may need to pay Car Insurance on March 01. Typically you'd receive a renewal email ~30-60 days prior, and it generally will have gone up by an amount that was not known until this date. Currently only options are to update the amount once you know, which may result in you having to allocate far more funds the 1-2 months prior to transaction than you have rest of the year, or add a second template for wiggle room _(after manually calculating a % increased amount)_. I'd like the templates feature in budgets to be able to accept a percentage increase to try and cover this scenario. ### Describe your ideal solution to this problem `#template schedule {SCHEDULE NAME} {INCREASE PERCENTAGE}` As an example, if I have a schedule for "Insurance" and last transaction was $100. I'd like to be able to write the template as `#template schedule Insurance 10%` and it will budget for $110. Whilst I don't know what the amount will be, I know generally costs increase by x% per year. ### Teaching and learning Documentation could easily be added to the currently templates table on this page: https://actualbudget.org/docs/experimental/goal-templates/ I can't think of a scenario where we'd expect a drop in the amount _(e.g. `#template schedule Insurance -10%`) but it may need to be considered.
GiteaMirror added the feature label 2026-02-28 19:53:39 -06:00
GiteaMirror commented 2026-02-28 19:53:40 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 6, 2025):

✨ 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 (Jan 6, 2025): :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-02-28 19:53:41 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 23, 2025):

added by #4089

@youngcw commented on GitHub (Apr 23, 2025): added by #4089
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1745
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?