Add Note and Category to Scheduled Transactions #2261

New Issue

GiteaMirror · 2026-02-28T20:08:19-06:00

GiteaMirror commented

2026-02-28 20:08:19 -06:00

Originally created by @siyual on GitHub (Jul 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?

I'm encountering an issue with scheduled transactions where there are multiple scheduled payments for the same payee, but I want to distinguish them in the ledger with a note denoting which particular one it's for.

I originally tried to fix the issue by editing the schedule as a rule and applying a Note and Category, but I noticed this is just running the rule to match it and applying the notes and categories to the first match it finds.

In most all cases this is fine, but I have cases where there are two scheduled transactions that are from the same payee, on the same day of the month, for the exact same dollar amount. This shows up in the ledger with the same note and looks like a duplicated transaction, but they are actually separate ones and should have both notes.

This is how I have my scheduled transaction set up:

And the rule for it:

There is also a PBS Kids scheduled transaction that has the same day of month, same payee, and exact same payment amount. But when I look at the upcoming transactions, it looks like this:

There are supposed to be two transactions, but one is supposed to say PBS Kids and the other is for Curiosity Stream. However, the rule matching is identifying them both as the same one and applying PBS Kids to both.

Describe your ideal solution to this problem

Using rules to modify the scheduled transaction does not seem like a good way to solve this. Instead, I think a more suitable solution would be to add support for adding Notes and Categories to the Scheduled Transaction template to automatically apply them without the need to rely on rule matching.

Specifically, this screen here:

Teaching and learning

I think it would be self-explanatory in usage and purpose.

Originally created by @siyual on GitHub (Jul 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? I'm encountering an issue with scheduled transactions where there are multiple scheduled payments for the same payee, but I want to distinguish them in the ledger with a note denoting which particular one it's for. I originally tried to fix the issue by editing the schedule as a rule and applying a Note and Category, but I noticed this is just running the rule to match it and applying the notes and categories to the first match it finds. In most all cases this is fine, but I have cases where there are two scheduled transactions that are from the same payee, on the same day of the month, for the exact same dollar amount. This shows up in the ledger with the same note and looks like a duplicated transaction, but they are actually separate ones and should have both notes. This is how I have my scheduled transaction set up: <img width="752" height="602" alt="Image" src="https://github.com/user-attachments/assets/7ca29613-5471-479d-84ba-03e969359b9b" /> And the rule for it: <img width="916" height="656" alt="Image" src="https://github.com/user-attachments/assets/5709f470-6dea-4c24-be2a-28c6f8c39b5a" /> There is also a PBS Kids scheduled transaction that has the same day of month, same payee, and exact same payment amount. But when I look at the upcoming transactions, it looks like this: <img width="1056" height="78" alt="Image" src="https://github.com/user-attachments/assets/30020c1b-f55d-475b-9bc9-fc47345d65af" /> There are supposed to be two transactions, but one is supposed to say PBS Kids and the other is for Curiosity Stream. However, the rule matching is identifying them both as the same one and applying PBS Kids to both. ### Describe your ideal solution to this problem Using rules to modify the scheduled transaction does not seem like a good way to solve this. Instead, I think a more suitable solution would be to add support for adding Notes and Categories to the Scheduled Transaction template to automatically apply them without the need to rely on rule matching. Specifically, this screen here: <img width="752" height="602" alt="Image" src="https://github.com/user-attachments/assets/b9a7a1eb-d2cf-48b4-90da-62aa7d4cbec7" /> ### Teaching and learning I think it would be self-explanatory in usage and purpose.

GiteaMirror added the bug schedules labels 2026-02-28 20:08:19 -06:00

GiteaMirror commented

2026-02-28 20:08:19 -06:00

@github-actions[bot] commented on GitHub (Jul 6, 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 (Jul 6, 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 👍!

GiteaMirror commented

2026-02-28 20:08:20 -06:00

@siyual commented on GitHub (Jul 6, 2025):

Required comment.

@siyual commented on GitHub (Jul 6, 2025): Required comment.

GiteaMirror commented

2026-02-28 20:08:20 -06:00

@youngcw commented on GitHub (Jul 6, 2025):

Moving to bug report

@youngcw commented on GitHub (Jul 6, 2025): Moving to bug report