[Feature] Add option for simplified scheduled and repeated transactions #2360

Closed
opened 2026-02-28 20:11:51 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @Backspaze on GitHub (Aug 5, 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?

This is not about removing or replacing the existing powerful features for adding scheduled and repeated transactions. This is about adding support for an optional and simplified way of adding scheduled and repeated transactions, with nYNAB as the model.

I will refer to nYNAB as YNAB below.

Coming from YNAB, I was a bit stumped when I stumbled upon the complexity of adding scheduled and repeated transactions in Actual. As scheduled and repeated transactions are not imported (#5455) when importing from YNAB, you have to add them again manually, and this requires quite a lot of work compared to YNAB.

Adding a scheduled transaction in YNAB

Image

Adding a scheduled repeated transaction in YNAB

Image

Trying to add a scheduled transaction à la YNAB in Actual

Image

When I try to enter the transaction with a future date in Actual, the same way as in YNAB, the transaction is not scheduled. Instead, it's entered as if it has already occurred, and the amount is withdrawn from the balance. Notice in YNAB how it's automatically added as a scheduled transaction which has not yet occurred, and the amount is not withdrawn from the balance.

In the account register in Actual, when you add a transaction, there's no option to make it a repeated transaction by just choosing a frequency under the date picker.

For reference, here is a link to YNAB's support documentation - Scheduled Transactions

In YNAB, adding a scheduled transaction, or a scheduled repeated transaction, is done in seconds, while in Actual, it's more like minutes. It feels a bit like "Oh! This has to be added as a scheduled transaction!" vs "Sigh! This has to be added as a scheduled transaction...".

Describe your ideal solution to this problem

My ideal solution for this issue is to add an option to make it possible to add scheduled and repeated transactions just as easy as it is in YNAB. This could be added as a checkbox in the settings, so that those who don't want to use it don't have to.

A related part of this feature is that it would fix the weird handling of transactions with a future date. The fact that they get added as if they've already occurred, and are withdrawn from the balance, is just wrong in my opinion. YNAB's way of automatically adding them as scheduled transaction, seems way more logical.

Teaching and learning

If this feature is implemented, the documentation for scheduled transactions need to be updated. I'd also suggest adding tooltips or pop-ups with info on first use of the feature.

Originally created by @Backspaze on GitHub (Aug 5, 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? This is **not** about removing or replacing the existing powerful features for adding scheduled and repeated transactions. This is about adding support for an optional and simplified way of adding scheduled and repeated transactions, with nYNAB as the model. I will refer to nYNAB as YNAB below. Coming from YNAB, I was a bit stumped when I stumbled upon the complexity of adding scheduled and repeated transactions in Actual. As scheduled and repeated transactions are not imported (#5455) when importing from YNAB, you have to add them again manually, and this requires quite a lot of work compared to YNAB. ## Adding a scheduled transaction in YNAB ![Image](https://github.com/user-attachments/assets/e14ec6b6-6ae2-431c-9252-56c70bfe4353) ## Adding a scheduled repeated transaction in YNAB ![Image](https://github.com/user-attachments/assets/cb9f8843-0ca8-44a9-abb1-0484851b0868) ## Trying to add a scheduled transaction à la YNAB in Actual ![Image](https://github.com/user-attachments/assets/7e40f6d1-54da-43ae-a8ad-08e31f571da2) When I try to enter the transaction with a future date in Actual, the same way as in YNAB, the transaction is not scheduled. Instead, it's entered as if it has already occurred, and the amount is withdrawn from the balance. Notice in YNAB how it's automatically added as a scheduled transaction which has not yet occurred, and the amount is not withdrawn from the balance. In the account register in Actual, when you add a transaction, there's no option to make it a repeated transaction by just choosing a frequency under the date picker. For reference, here is a link to YNAB's support documentation - [Scheduled Transactions](https://support.ynab.com/en_us/scheduled-transactions-a-guide-BygrAIFA9) In YNAB, adding a scheduled transaction, or a scheduled repeated transaction, is done in seconds, while in Actual, it's more like minutes. It feels a bit like "Oh! This has to be added as a scheduled transaction!" vs "Sigh! This has to be added as a scheduled transaction...". ### Describe your ideal solution to this problem My ideal solution for this issue is to add an option to make it possible to add scheduled and repeated transactions just as easy as it is in YNAB. This could be added as a checkbox in the settings, so that those who don't want to use it don't have to. A related part of this feature is that it would fix the weird handling of transactions with a future date. The fact that they get added as if they've already occurred, and are withdrawn from the balance, is just wrong in my opinion. YNAB's way of automatically adding them as scheduled transaction, seems way more logical. ### Teaching and learning If this feature is implemented, the [documentation for scheduled transactions](https://actualbudget.org/docs/schedules/) need to be updated. I'd also suggest adding tooltips or pop-ups with info on first use of the feature.
GiteaMirror added the needs votesfeature labels 2026-02-28 20:11:51 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 5, 2025):

Thanks for sharing your idea!

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 (Aug 5, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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#2360