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

[Feature] Schedule transaction amount based on account balance #839

New Issue
Closed
opened 2026-02-28 19:21:33 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:21:33 -06:00
Owner
Copy Link

Originally created by @jasonmichalski on GitHub (Dec 31, 2023).

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 credit card accounts that are used for daily spending, and the balance on these cards are paid in full each month. The amount, however, can vary significantly from month to month so the currently implemented scheduled amount options are insufficient to represent this. I would like to be able to create a scheduled transaction with the amount calculated based on the account balance.

Describe your ideal solution to this problem

Ideally there would be a way to create a recurring scheduled transaction, and the amount would be dynamically calculated based on the running balance of a particular account. For the credit card scenario, it could be useful to capture the balance on a specific date (i.e. the amount might be the balance on January 10th, but the scheduled transaction / due date might be February 10th).

This feature would also tie in nicely with https://github.com/actualbudget/actual/pull/2126, forecasting cash flow, as the scheduled amount would update as more spending was added to a credit card.

Teaching and learning

This would probably be self evident in the rule creation page by creating a new option for Amount.

Originally created by @jasonmichalski on GitHub (Dec 31, 2023). ### 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? I have credit card accounts that are used for daily spending, and the balance on these cards are paid in full each month. The amount, however, can vary significantly from month to month so the currently implemented scheduled amount options are insufficient to represent this. I would like to be able to create a scheduled transaction with the amount calculated based on the account balance. ### Describe your ideal solution to this problem Ideally there would be a way to create a recurring scheduled transaction, and the amount would be dynamically calculated based on the running balance of a particular account. For the credit card scenario, it could be useful to capture the balance on a specific date (i.e. the amount might be the balance on January 10th, but the scheduled transaction / due date might be February 10th). This feature would also tie in nicely with https://github.com/actualbudget/actual/pull/2126, forecasting cash flow, as the scheduled amount would update as more spending was added to a credit card. ### Teaching and learning This would probably be self evident in the rule creation page by creating a new option for Amount.
GiteaMirror added the needs votesfeature labels 2026-02-28 19:21:33 -06:00
GiteaMirror commented 2026-02-28 19:21:34 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 31, 2023):

✨ 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 (Dec 31, 2023): :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.
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 needs votes
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#839
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?