mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 03:32:54 -05:00
Set Schedule to Account Balance #1613
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1613
Reference in New Issue
Block a user
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?
Originally created by @epikaan on GitHub (Nov 24, 2024).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
I would like to set a scheduled transaction to match the balance of my credit card so I can see quickly when and how much money will be transferred from my checking account to my credit card.
Describe your ideal solution to this problem
Ideally when you set the schedule amount you would have a fourth option which is equal to the balance of an account, so that it dynamically updates. I know the date when my CC automatic payment is so only the amount would have to be dynamic.
Teaching and learning
No response
@github-actions[bot] commented on GitHub (Nov 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 👍!
@mullermn commented on GitHub (Feb 2, 2026):
I think this needs to be a little more sophisticated.
Most the time the transaction to settle the card lags some way behind the transactions on the card - eg, the transactions in January total £1000 and this money is taken from an account on the 15th of February. However, by the 15th of February half of the transactions for February will now be on the credit card with the total balance at £1500.
To do this properly you would have to handle this date offset in the schedule - I think this would be a really nice enhancement though.
@StephenBrown2 commented on GitHub (Feb 2, 2026):
There is a balance function in the formula options, could you have the schedule run on the statement date and create a transaction with the balance that way?
@youngcw commented on GitHub (Feb 2, 2026):
Interesting. Have a schedule run on the statement date, edit the underlying rule to change the date of the transaction to be the payment date. That probably would work. It would be a transaction instead of a schedule, but that could be ok.
@mullermn commented on GitHub (Feb 2, 2026):
This actually works! It's a bit fragile (had Actual crash multiple times while playing with these templates) but it does work.
I set up this schedule on the credit card (ie, the account that should receive the transfer):
Then I customised the associated rules:
And this has resulted in a future scheduled transaction on the bank account (that will eventually settle the debt), on the correct future date on which the payment will be made, with an amount that reflects the credit card's correct running balance as of today (uncleared+cleared).
Pretty cool that this works, but I think it would still be valuable to wrap all of this up in an easy UI for the user, as settling of credit card debts is going to be a common use case and this is relatively complex to set up.
@youngcw commented on GitHub (Feb 2, 2026):
I think the best thing long term would be to make a formula function that gets the balance on a specific day, that way you can skip the date shenanigans and have a regular schedule
@StephenBrown2 commented on GitHub (Feb 2, 2026):
But, that would mean that formulas would have to be enabled in the initial Amount field, right? Maybe add a dropdown option:
@youngcw commented on GitHub (Feb 2, 2026):
It could be in the "set" section just like the example above. It would be nice to have that option from the beginning but not required
@tgehrs commented on GitHub (Feb 24, 2026):
@mullermn in your successful test do you have the "Upcoming Length" set in schedules at all? When I tried to follow the steps you indicated (see first screenshot, only change is add 1 month instead of 13 days), I am seeing two upcoming transactions for today's balance with the date set for one month from today. This makes sense as the "date" in the conditions must be the date of the transaction, not the current date.
Interestingly too while the date is set as the rule determines, the chronology in the account still has it on the original date, not the date that is updated in the "set" action (see second screenshot).
I'm only a few months into Actual and haven't dug into the code yet, so wanted to hear more about your solution to this issue before going too far into it. Thanks